I have a huge mess - Verizon Samsung Galaxy S III

Ok, so I finally got my replacement phone from Verizon after the last one's power IC crashed. Anyway, I'm eager to get it back to normal. I first unlocked, rooted, and flashed CM 10.1 within recovery with this thread: http://forum.xda-developers.com/showthread.php?t=2046439 For some reason, I didn't see the "Disable recovery flash" when I rebooted to the system. Anyway, CM10.1 boot looped. Re-flashing from recovery didn't work, so I followed this thread: http://forum.xda-developers.com/showthread.php?t=1840030 I struggled with that, but I finally managed to get to the last step where it flashes "stock.vzw_root66.tar" That failed for whatever reason, so I couldn't move on. Then I did a whole bunch of things, so I can't really remember. I think one point I might have actually flashed something in the bootloader part of ODIN when it was supposed to be in the PDA part (that didn't really seem to have an affect on anything after that though for whatever reason). My phone had VRBMB1 and 4.12 when I first got the device and I didn't accept the latest OTA update. I try flashing a bootloader and then a recovery image like this: http://rootzwiki.com/topic/29256-tutorial-rootrecoverybootloader-unlockicsjb-verizon-galaxy-s-iii/ and this http://www.w0lfdroid.com/2013/04/how-to-lockunlock-bootloader-for.html but the dumb "System software not autorized by Verizon Wireless has been found on your phone" keeps popping up whenever I go into recovery (I flash CWM). I can go into ODIN and flash stuff, but I'm currently blocked by that Verizon message. In the end, I would like an unlocked bootloader, with root, and CM 10.1. From there I can TB to my old device. Any help would be greatly appreciated. Thank you!

LOL
Ya Im wondering if your screwed or if your phone got verizon analed ?????

He can't even remember what he did to the phone and you are wondering if Verizon screwed him???
Just ODIN back to OEM ROM stock unrooted and start over and be sure to follow root and unlock steps precisely.
Make sure you are following a thread which matches the OEM version you are using.
You may need to follow a " return to stock unrooted" thread.

Thanks for your reply. Could you give me a thread that could take me through that experience? Also, what does OEM version mean? Thanks again.

OEM means Original Equipment Manufacturer, aka whatever comes with said item unmodified. In this case, stock, unrooted, locked firmware.
http://forum.xda-developers.com/showthread.php?t=2334876
Pm this guy. He has the latest firmware in Odin (PDA slot only for clarification) flashable format.
Flash that, and you'll be stock. If you want to unlock and flash again, I'll find you the guide and break it down for you when I get home. However I'd advise you to do some more reading before you go crack flashing again in the hopes of saving you headaches and prolonging your devices' longevity.
Sent from my SCH-I605 using xda app-developers app
---------- Post added 11th July 2013 at 12:05 AM ---------- Previous post was 10th July 2013 at 11:19 PM ----------
zerofighter1 said:
OEM means Original Equipment Manufacturer, aka whatever comes with said item unmodified. In this case, stock, unrooted, locked firmware.
http://forum.xda-developers.com/showthread.php?t=2334876
Pm this guy. He has the latest firmware in Odin (PDA slot only for clarification) flashable format.
Flash that, and you'll be stock. If you want to unlock and flash again, I'll find you the guide and break it down for you when I get home. However I'd advise you to do some more reading before you go crack flashing again in the hopes of saving you headaches and prolonging your devices' longevity.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1974114
This guide should get you back to rooted/unlocked/recovery. If you have any questions, post them here and I'll do what I can to guide you through the process. Good luck.

I managed to get back to stock. From there I unlocked and rooted. After that, I try to flash Cyanogenmod CM 10.1.1 from recovery, but it bootloops again. I'm not sure what is causes that bootloop. Thanks.

Dillon610 said:
I managed to get back to stock. From there I unlocked and rooted. After that, I try to flash Cyanogenmod CM 10.1.1 from recovery, but it bootloops again. I'm not sure what is causes that bootloop. Thanks.
Click to expand...
Click to collapse
Are you wiping data?

I just did before you said that. I *finally* (after countless hours) have everything the way I want it. Thank you so much everybody for the help!

Related

Locked out by Verizon after cm10 flash

thanky you to anyone ahead of time for reading this post. I really could use some help.
I have a Verizon galaxy s3 which I rooted 3 weeks ago when i got it. I know it was rooted as i had super user permissions, and deleted many bloatware apps. I waited until cm10 came out to flash a new rom and after doing so last night my phone now boots up with this message "System software not authorized by verizon wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
So I tried to boot it in to recovery mode but when I did, the same message came up, only this time it said "recovery booting" in small blue writing in the top left corner.
I followed the directions to a T from a page entitled "Jelly Bean for Verizon Galaxy S3: Unofficial CyanogenMod 10 (CM10) Nightlies Available for Flashing!
From what I understand, the bootloader was somehow never unlocked by kexec. because I cant get in to recovery mode, I was wondering if there was a way to disable the bootlock by installing kexec via odin.
Also, whether it was a good idea or not, I re flashed the stock rom via oden last, which was successful but, nothing has changed still the same response all boot ups. Download boot obviously works though as I have been able to mess with it in odin.
any insight on this would be graciously appreciated.
Lembro said:
thanky you to anyone ahead of time for reading this post. I really could use some help.
I have a Verizon galaxy s3 which I rooted 3 weeks ago when i got it. I know it was rooted as i had super user permissions, and deleted many bloatware apps. I waited until cm10 came out to flash a new rom and after doing so last night my phone now boots up with this message "System software not authorized by verizon wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
So I tried to boot it in to recovery mode but when I did, the same message came up, only this time it said "recovery booting" in small blue writing in the top left corner.
I followed the directions to a T from a page entitled "Jelly Bean for Verizon Galaxy S3: Unofficial CyanogenMod 10 (CM10) Nightlies Available for Flashing!
From what I understand, the bootloader was somehow never unlocked by kexec. because I cant get in to recovery mode, I was wondering if there was a way to disable the bootlock by installing kexec via odin.
Also, whether it was a good idea or not, I re flashed the stock rom via oden last, which was successful but, nothing has changed still the same response all boot ups. Download boot obviously works though as I have been able to mess with it in odin.
any insight on this would be graciously appreciated.
Click to expand...
Click to collapse
Okay, first, If you did follow the directions for that thread, i'm sure it would of worked, I'm pretty sure you are missing something here and i'm pretty sure from reading your post that I think you didn't unlock your bootloader. kexec was a workaround for the locked bootloader, it doesn't unlock it. I would follow droidstyle's guide to unlocking the bootloader, http://forum.xda-developers.com/showpost.php?p=28530409&postcount=2 after you unlocked it, i'm pretty sure you forgot that step. But the issue when flashing back to stock via odin and still showing up its a custom rom, I don't know why that would happen but I suggest reading section 2 of droidstyle's guide on flashing back to stock. http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
So first, I suggest to return to stock, then root, then unlock bootloader, and then install the rom of your choice, preferably without kexec, if you don't want the triple reboot.
RyanW114 said:
Okay, first, If you did follow the directions for that thread, i'm sure it would of worked, I'm pretty sure you are missing something here and i'm pretty sure from reading your post that I think you didn't unlock your bootloader. kexec was a workaround for the locked bootloader, it doesn't unlock it. I would follow droidstyle's guide to unlocking the bootloader, http://forum.xda-developers.com/showpost.php?p=28530409&postcount=2 after you unlocked it, i'm pretty sure you forgot that step. But the issue when flashing back to stock via odin and still showing up its a custom rom, I don't know why that would happen but I suggest reading section 2 of droidstyle's guide on flashing back to stock. http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
So first, I suggest to return to stock, then root, then unlock bootloader, and then install the rom of your choice, preferably without kexec, if you don't want the triple reboot.
Click to expand...
Click to collapse
Agreed! Op, do more reading and less flashing before you end up with a 600.00 paperweight!
Like he says above you have not unlocked your bootloader . Restore nandroid or recover to stock. Then unlock your bootloader and try again
Sent from my SCH-I535 using xda premium
Get rid of the Verizon screen of death
I got the same error msg after flashing a nightly of d2hacker's unofficial cm10, after I had flashed a few nightly's before of the same ROM w/ no problems. I had to
1. Flash a stock bloated unrooted ROM via odin (lemme know if you need a link to one)
2.boot into droid recovery and do a factory reset, and wipe the cache partition also.
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
I haven't re-rooted yet but I'll be trying the official cm10 now that it's up.
MDMoore313 said:
I got the same error msg after flashing a nightly of d2hacker's unofficial cm10, after I had flashed a few nightly's before of the same ROM w/ no problems. I had to
1. Flash a stock bloated unrooted ROM via odin (lemme know if you need a link to one)
2.boot into droid recovery and do a factory reset, and wipe the cache partition also.
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
I haven't re-rooted yet but I'll be trying the official cm10 now that it's up.
Click to expand...
Click to collapse
Refer to my last post
droidstyle said:
Refer to my last post
Click to expand...
Click to collapse
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
Incorrect. It actually means the opposite. The only way to tell if your bootloader is unlocked is to flash a custom rom/kernel and boot up. Please people, do some reading before you turn your phone into a paperweight. That unlocked lock/custom means you're running or were running custom software and it's been detected as such. One possible culprit is your "custom" recovery. If your bootloader is unlocked, you will not have that problem.
MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
refer to post #3 and read this link
http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13
Zalithian said:
Incorrect. It actually means the opposite. The only way to tell if your bootloader is unlocked is to flash a custom rom/kernel and boot up. Please people, do some reading before you turn your phone into a paperweight. That unlocked lock/custom means you're running or were running custom software and it's been detected as such. One possible culprit is your "custom" recovery. If your bootloader is unlocked, you will not have that problem.
Click to expand...
Click to collapse
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
MDMoore313 said:
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
Click to expand...
Click to collapse
I think it has to do with the "degree" of customization. IE a custom ROM or Kernel will get you the verizon screen of death for sure if you're not unlocked. The custom/unlock icon seems more for minor things like a custom recovery, possibly different firmware or tweaking specific settings.
Zalithian said:
I think it has to do with the "degree" of customization. IE a custom ROM or Kernel will get you the verizon screen of death for sure if you're not unlocked. The custom/unlock icon seems more for minor things like a custom recovery, possibly different firmware or tweaking specific settings.
Click to expand...
Click to collapse
That makes more sense, as the nightlys progress and more modifications are being made, overnight the "switch is flipped" so to speak, and if you're not running a custom rom,
MDMoore313 said:
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
Click to expand...
Click to collapse
Could he Odin back to stock through download mode though? Or will the locked bootloader block download mode and recovery mode too when it detects tampering?
MDMoore313 said:
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
Click to expand...
Click to collapse
The secure aboot.img only checks 3 of the 5 system images on boot. Since we can flash a custom recovery to the recovery partition, the secure aboot img lets it ride, but knows it there....hence why you see the custom lock screen, but device still boots. Kexec allowed the bootloader aka secure aboot.img to see the stock kernel(boot.img) and pass signature checks, then side loads the custom kernel. Thats why there was 3 reboots...now that the bootloader is unlocked, we ditch kexec because unsecure aboot is unlocked and not checking signatures.
However, if you flash a kernel thats non kexec and the bootloader is locked, you will get the verizon screen of death since the secure aboot.img is checking signatures. So never lock the bootloader unless your on stock rom/kernel or using kexec.
Deleted
Jesus. All of these people who don't read up on things before they flash something astounds me.
Lol, the exact same thing happen to me as Op, I was unlock (ezrecovery app) and rooted(casual-revision131) but when I flash unofficial CM10 KANG I was lock out by Verizon message.Thanks to DroidStyle awesome GUIDE i just Odin back to stock along with kernel.Thank you to all the cool people here at xda who help and evolve Android:thumbup:
Ezrecovery app must not have work properly even tho it said unlock, so I use Adam casual R131 flash Unsecure Aboot too.
Sent from my SCH-I535 using xda premium
EvoSideHustlAZ said:
Lol, the exact same thing happen to me as Op, I was unlock (ezrecovery app) and rooted(casual-revision131) but when I flash unofficial CM10 KANG I was lock out by Verizon message.Thanks to DroidStyle awesome GUIDE i just Odin back to stock along with kernel.Thank you to all the cool people here at xda who help and evolve Android:thumbup:
Ezrecovery app must not have work properly even tho it said unlock, so I use Adam casual R131 flash Unsecure Aboot too.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
ezrecovery to unlock? What?
MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
No, that just means that it normally has detected some changed files. If you WERE unlocked you would never see that icon.
TAPPED in on my (now unlocked bootloader) Verizon S3
strung said:
Could he Odin back to stock through download mode though? Or will the locked bootloader block download mode and recovery mode too when it detects tampering?
Click to expand...
Click to collapse
Well, step 1 is going Odin back to stock, but if a cache wipe and factory reset aren't done (like in Droidstyle's guide), then it will never completely boot, at least that's what I experienced after my phone sat at that screen for 10+ minutes. It doesn't run the user setup again.

[Q] Help returning to stock recovery

Hi Guys,
I know this may be frustrating for some of you, but as a complete beginner in using Android, I was wondering whether someone could help me out here. I have tried searching various forums, but my knowledge of androids is limited. I used the tutorial from Rootwiki to successfully unlock my bootloader, install TWRP recovery and root my phone
Does this mean I am not using a stock rom?
Now I sort of regret deciding to do this and would like to return to stock so that I can get any OTA updates without further tampering with my phone. Unfortunately while following the above tutorial, I only made a backup after TWRP was installed and not before, so I need help in going back please.
I can see that there are a few people in my position, so I'm sure others will benefit from this as well.
My software details are:
Android version - 4.2.2.
Software number - 1.33.206.1
HTC SDK API level - 5.41
Network - o2 uk
Can I use any stock recovery file or does it have to be specific to the above?
Can you please provide a step by step guide with a list of files that I will need to download?
or can I simply just factory reset my phone, and everything goes back to normal? I don't mind having to re install apps etc?
Thank you all very much
i have a HTC One mini 4.3 and i am in the exact same situation. i like to get stock recovery but those ive tried hasent been working.
If you didint flash a rom after you installed your recovery, the back up you made is then of stock os
Maybe if you take the ota, it will cancel out ur root and five you stock recovery back, i havent browsed these forums.. Try searching for a RUU and stock recovery, the phone is fairly new, so can take time for someone to put something together
Sent from my HTC6500LVW using xda app-developers app
the stock recovery must match HBOOT /Main-Version....
wich HBOOT do you have?
epolus said:
the stock recovery must match HBOOT /Main-Version....
wich HBOOT do you have?
Click to expand...
Click to collapse
Thank you for your replies, my HBOOT is 2.19.0000
Ok guys, I got the notification for the OTA update today, I have downloaded it but haven't installed it. From a different thread, I found a link for a stock recovery which is about 9.5mb from androidfile host (/?fid=23252070760975668)
can I just flash this recovery and proceed with the update? or will there be compatibility issues with the version I have above?
Thanks
Anyone?
I am getting desperate to the point that I might actually pay HTC to repair it for me
Did u have any look for I'm looking for the same but have an unrooted mini
Sent from my HTC One mini using Tapatalk
nbbcj said:
Did u have any look for I'm looking for the same but have an unrooted mini
Sent from my HTC One mini using Tapatalk
Click to expand...
Click to collapse
not yet, but MirageBlader has been quite helpful and has said the following in a private message to me, which I have yet to try:
"Very easy mate, open your ota and flash the stock recovery from the ota. You can only install it with stock Rom, stock boot and stock recovery. Your bootloader musst be locked and your phone unrooted. s-off is not needed if you already got the ota"
drewkp said:
not yet, but MirageBlader has been quite helpful and has said the following in a private message to me, which I have yet to try:
"Very easy mate, open your ota and flash the stock recovery from the ota. You can only install it with stock Rom, stock boot and stock recovery. Your bootloader musst be locked and your phone unrooted. s-off is not needed if you already got the ota"
Click to expand...
Click to collapse
I'd be very interested to know the results of your attempt to go back to "stock".
Can I ask if you are doing this just to get the 4.3 update? Also, do you plan to root and customise your ROM after the update, or leave it stock?
Thanks, and good luck....
---------- Post added at 01:14 AM ---------- Previous post was at 01:10 AM ----------
nbbcj said:
Did u have any look for I'm looking for the same but have an unrooted mini
Sent from my HTC One mini using Tapatalk
Click to expand...
Click to collapse
If your phone isn't rooted, what exactly is the issue? Do you have a custom recovery installed, and is your bootloader unlocked? If you are looking to upgrade, did you get the OTA download on your phone?
Hi nelvinchi I am trying to get back to android ver 4.2, I have a stock mini it's not been rooted or mod'd in any way. Just had the 4.3 ota that was update automatically just woke up and my phone had updated looking at settings it was set to auto update and install when on charge Grr dam phone so many probs with this ota
Sent from my HTC One mini using Tapatalk
nelvinchi said:
I'd be very interested to know the results of your attempt to go back to "stock".
Can I ask if you are doing this just to get the 4.3 update? Also, do you plan to root and customise your ROM after the update, or leave it stock?
Thanks, and good luck....
---------- Post added at 01:14 AM ---------- Previous post was at 01:10 AM ----------
If your phone isn't rooted, what exactly is the issue? Do you have a custom recovery installed, and is your bootloader unlocked? If you are looking to upgrade, did you get the OTA download on your phone?
Click to expand...
Click to collapse
I haven't got round to trying this out yet, will update this thread once I do, just quite busy this month and can't afford to mess up my phone. Yep, just doing it for the update, I only rooted my phone in the first place to get rid of bloatware, which i realised is a lot more complicated than just rooting, and all the other benefits of rooting don't really appeal to me, or are too much hassle for a beginner such as myself.
Just need to figure out how to unroot and relock my bootloader before I can go ahead with this :s
Hey nelvinchi. You seem to be knowledgeable enough on the matter and have been looking for help with my device. I posted a separate thread yesterday. If you have time/think you can help, could you take a look? Would much appreciate it.
drewkp said:
I haven't got round to trying this out yet, will update this thread once I do, just quite busy this month and can't afford to mess up my phone. Yep, just doing it for the update, I only rooted my phone in the first place to get rid of bloatware, which i realised is a lot more complicated than just rooting, and all the other benefits of rooting don't really appeal to me, or are too much hassle for a beginner such as myself.
Just need to figure out how to unroot and relock my bootloader before I can go ahead with this :s
Click to expand...
Click to collapse
If you have SuperSU installed on your phone, the app has a settings option called "Full unroot" - this will get rid of root. Relocking your bootloader - there are various methods, you could try HTCDEV site (probably how you unlocked originally), or the revone option which will lock the bootloader and remove the "tampered" label. Try a search, but if you are unsure, jusk ask!
2664963463
Got everything sorted with the great help of Nelvin. I had previously gone to the twrp support IRC and after answering a few questions, they just stopped talking... Glad there are people out there still willing to help! He spent a good hour or so with me making sure everything was working.
nelvinchi said:
If you have SuperSU installed on your phone, the app has a settings option called "Full unroot" - this will get rid of root. Relocking your bootloader - there are various methods, you could try HTCDEV site (probably how you unlocked originally), or the revone option which will lock the bootloader and remove the "tampered" label. Try a search, but if you are unsure, jusk ask!
Click to expand...
Click to collapse
Thanks for your reply nelvinchi, can I just confirm whether the SuperSU app you're talking about it the one by Chainfire in the marketplace? And is it just a matter of installing this from the marketplace to unroot my device, or is it a bit more complicated than that?
I'll do some research on relocking my bootloader with revone.
Also do you reckon the above method of getting the stock recovery from my update file will work?
Thanks for your help
drewkp said:
Thanks for your reply nelvinchi, can I just confirm whether the SuperSU app you're talking about it the one by Chainfire in the marketplace? And is it just a matter of installing this from the marketplace to unroot my device, or is it a bit more complicated than that?
I'll do some research on relocking my bootloader with revone.
Also do you reckon the above method of getting the stock recovery from my update file will work?
Thanks for your help
Click to expand...
Click to collapse
If you are rooted then you more than likely have supersu already installed. Check your app drawer.I rooted using HTC DEV and supersu was flashed to the phone with twrp as part of the process
drewkp said:
Thanks for your reply nelvinchi, can I just confirm whether the SuperSU app you're talking about it the one by Chainfire in the marketplace? And is it just a matter of installing this from the marketplace to unroot my device, or is it a bit more complicated than that?
I'll do some research on relocking my bootloader with revone.
Also do you reckon the above method of getting the stock recovery from my update file will work?
Thanks for your help
Click to expand...
Click to collapse
Can I make a suggestion? Given where you are with your phone currently, It would be much simpler, and virtually risk free, to flash tr1gg3r's Stock Sense 5.5 4.3 rooted deodexed rom from the One Mini Android Development forum.
You will get the 4.3 update, and have a fast and very stable ROM. All future updates will be incorporated into a newer ROM version.
Returning to "stock" carries FAR more risk - and you'll never have true stock because it isn't possible. Soon as the bootloader is unlocked, your phone is tampered, and no tool or utility can change that (other than cosmetically!)
It's your choice obviously, but if I was you, I'd stay rooted and enjoy the benefits it brings!
If you still want to try to go back to stock, I'll help..... But I've now helped three members get out of a soft brick after they attempted to go stock.......

[FIRMWARE] VRUDNE1 (Android 4.4.2 - Kit Kat) No-Wipe Factory Image

WARNING: I am posting this for development purposes only (and for those of you already on the new locked bootloader)!
If you have an unlocked bootloader or are still on MF1 firmware, DO NOT flash this in ODIN or you will be permanently locked down to the new bootloader with no way of going back!
Those of you who know how to work with this file feel free to use it as you see fit. Otherwise, consider yourself warned!
Download: http://www.androidfilehost.com/?fid=23501681358553154
First!
Hairiest chest?
Can't wait till you guys crack this open for us unlocked folks!
i need to send my phone back into verizon. if i odin this i will be cool right?
Cannot wait for baseband update, hopefully it will be pulled separate soon.
So what does no-wipe mean?
Currently I am on NC1. If I want to odin to NE1 with fresh start, will this no-wipe affect in anyway?
You couldn't just flash the system and kernel partitions?
Sent from my GT-P5110 using Tapatalk 2
ruokuo said:
So what does no-wipe mean?
Currently I am on NC1. If I want to odin to NE1 with fresh start, will this no-wipe affect in anyway?
Click to expand...
Click to collapse
Means it is exactly the same as OTA. Does not wipe data. No difference flashing it and letting Verizon update it except Odin will unroot for you. Must unroot or hide root to take OTA.
kuronosan said:
You couldn't just flash the system and kernel partitions?
Sent from my GT-P5110 using Tapatalk 2
Click to expand...
Click to collapse
Won't boot with 4.3 firmware. It all or nothing for now or we would already have it fixed in dump thread.
Worked like a charm! Now I'll wait and see how to root this baby. I already had the locked bootloader so figured I didn't have anything to lose. Thanks!
gherman222 said:
Worked like a charm! Now I'll wait and see how to root this baby. I already had the locked bootloader so figured I didn't have anything to lose. Thanks!
Click to expand...
Click to collapse
Towelroot works.
Is there a version of this with an unlocked bootloader? I currently am running my S3 rooted and unlocked with 4.1.2. Do I need to run a ROM instead - and if so is there one that is stock 4.4.2 with an unlocked bootloader?
v1ncent said:
Is there a version of this with an unlocked bootloader? I currently am running my S3 rooted and unlocked with 4.1.2. Do I need to run a ROM instead - and if so is there one that is stock 4.4.2 with an unlocked bootloader?
Click to expand...
Click to collapse
They are currently at Work our beloved developers trying to bring us a rooted touch wiz version for those with unlocked bootloader in tact and the very first of it's kind I might add. Do not flash this if your bootloader is of value and be patient as the very best of the best of developers are collaborating to bring it to us.
Sent from my SCH-I535 using XDA Free mobile app
MIKEYSAKZ said:
They are currently at Work our beloved developers trying to bring us a rooted touch wiz version for those with unlocked bootloader in tact and the very first of it's kind I might add. Do not flash this if your bootloader is of value and be patient as the very best of the best of developers are collaborating to bring it to us.
Click to expand...
Click to collapse
Thanks - I have patience and definitely planning on waiting. That's why I still have an unlocked bootloader
prdog1 said:
Means it is exactly the same as OTA. Does not wipe data. No difference flashing it and letting Verizon update it except Odin will unroot for you. Must unroot or hide root to take OTA.
Won't boot with 4.3 firmware. It all or nothing for now or we would already have it fixed in dump thread.
Click to expand...
Click to collapse
Hello, how can i load in this firmware another modem like VRLHD, or there is some other way to install modem ?
P.s i have issue with sms/mms/i-net cuz of stock modem.
leroyinc said:
Hello, how can i load in this firmware another modem like VRLHD, or there is some other way to install modem ?
P.s i have issue with sms/mms/i-net cuz of stock modem.
Click to expand...
Click to collapse
Sounds like you borked your radios. Or your APN is missing. Only thing can do is run that tar. Can try running Verizon Software Updater in repair mode. It will wipe and then flash tar. If don't fix have to get new device from Verizon.
prdog1 said:
Sounds like you borked your radios. Or your APN is missing. Only thing can do is run that tar. Can try running Verizon Software Updater in repair mode. It will wipe and then flash tar. If don't fix have to get new device from Verizon.
Click to expand...
Click to collapse
hmm, i can't ask for new phone cuz im from another country, everything works on 4.2, but whe i updated to 4.3 i done with my phone
but what about Software Updater in repair mode, where is this ?
---------- Post added at 11:29 PM ---------- Previous post was at 11:01 PM ----------
prdog1 said:
Sounds like you borked your radios. Or your APN is missing. Only thing can do is run that tar. Can try running Verizon Software Updater in repair mode. It will wipe and then flash tar. If don't fix have to get new device from Verizon.
Click to expand...
Click to collapse
mms works, didnt know why wont work sms
leroyinc said:
hmm, i can't ask for new phone cuz im from another country, everything works on 4.2, but whe i updated to 4.3 i done with my phone
but what about Software Updater in repair mode, where is this ?
---------- Post added at 11:29 PM ---------- Previous post was at 11:01 PM ----------
mms works, didnt know why wont work sms
Click to expand...
Click to collapse
Make sure you are in Global mode before try any of this. If go with Software updater it is going to update you to 4.4.2. Not sure if can stop after repair or not. If that 4.3 tar in odin don't fix this is about only option I know of. Since bootloader is locked cannot use the fixes we have for this problem.
http://www.verizonwireless.com/support/devices/knowledge_base.html/80200/
open1your1eyes0 said:
WARNING: I am posting this for development purposes only (and for those of you already on the new locked bootloader)!
If you have an unlocked bootloader or are still on MF1 firmware, DO NOT flash this in ODIN or you will be permanently locked down to the new bootloader with no way of going back!
Those of you who know how to work with this file feel free to use it as you see fit. Otherwise, consider yourself warned!
Download: http://www.androidfilehost.com/?fid=23501681358553154
Click to expand...
Click to collapse
Is it safe to flash the modem only, in recovery, with existing mf1 firmware?
Thanks.
Sent from my SCH-I535 using XDA Free mobile app
I am on MF1 rooted and unlocked but I have had the phone since it's release and have no interest in installing AOSP ROMs. I do need root because I have to be able to use root explorer or similar so I can edit the "keys" system files to disable the "WAKE" function of the home key. I keep my phone in my back pocket and it constantly turns on if the home key has wake enabled.
Before I flash this I wanted to confirm that flashing this No-Wipe Factory Image with Odin, I can root with Towelroot and install Root Explorer? Would I also be able to install TW based ROMs like a new Clean Rom if Scott gets one figured out? Would I also be able to create nandroids using Clockwork or TWRP?
Lastly, Since my most recent install of CR 8.2 my phone's behavior has been a bit sketchy (random reboots, laggy, etc). I assume if I flash this stock image it should return my phone to whatever level of performance "stock" yields, without any of my current, likely self imposed, performance issues?
I have never had a phone this long and expect I'll get a new one whenever there really is a "next big thing", but I don't think we're there yet.
Thanks in advance.
Going back to stock
So, if I want to go back to stock, this is the way?
I'm on beanstalked / MF1 rooted and unlocked of course. But I'd like to get the phone back to stock condition so I can sell it here soon.

S3 stuck on red Verizon boot screen

So I've been working on this all night last night and all day today.
The issue- phone will boot, get to the red Verizon boot screen, sit there for approximately 45-60 seconds, then go to the lock screen. Within a couple of seconds, Then a message pops up that says process com.android.phone has stopped, then the phone reboots.
What I've tried- flashing various Vralec boot strings through Odin 3.2 and 1.3. Also tried five different stock ROMs and a CF Auto Root, in the hopes unlocking the bootloader would allow me to get a ROM to flash. Each and every one of these things has had an AUTH fail in Odin. Can anyone help me please?
I've also googled stuck red verizon screen, verizon s3 boot loop, process com.android.phone has stopped. None of the solutions I've found have been helpful, and are usually what led to the actions tried above. I believe I've encountered this before, but I checked my post history and wasn't able to find a thread, so I assume I found the solution on my own the last time.
Any assistance would be greatly appreciated!
What software version are you running? What baseband?
Sent from my SCH-I535 using Tapatalk
Hybridnoob said:
What software version are you running? What baseband?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
This is a warranty replacement from Verizon. Since I can't get it to boot, is there an alternative method to find those versions?
I have another S3, replaced less than a month ago, so I would assume they are the same software version and basebands, and that one is running 4.4.2 and I535OYUDNE1
The soft bricked, boot loop, S3 belongs to my girlfriend.
Flashing other ROMs on the S3 4.3 and newer will brick it. The bootloader was never unlocked. I'll try to find the thread describing the issue and post it here.
Sent from my SCH-I535 using Tapatalk
---------- Post added at 01:40 PM ---------- Previous post was at 01:37 PM ----------
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Tapatalk
---------- Post added at 01:40 PM ---------- Previous post was at 01:40 PM ----------
I hope that helps.
Sent from my SCH-I535 using Tapatalk
Hybridnoob said:
Flashing other ROMs on the S3 4.4 and newer will brick it. The bootloader was never unlocked. I'll try to find the thread describing the issue and post it here.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Flashing the ROMS through Odin failed every time, and none of that was done until AFTER the phone went in to a boot loop. It was already soft bricked, so I tried various different methods. Now I know, for future reference, that attempting to flash ROMs without unlocking the bootloader will brick it. Good to know.
If I can work around the Odin failed authorization, I believe I can flash a stock ROM to the phone and be all right, OR if someone can tell me how to unlock the bootloader, I should be able to flash a custom ROM, correct? It seems that the boot partition permissions were changed and have now affected the boot process, from what I've been reading.
Hybridnoob said:
Flashing other ROMs on the S3 4.3 and newer will brick it. The bootloader was never unlocked. I'll try to find the thread describing the issue and post it here.
Sent from my SCH-I535 using Tapatalk
---------- Post added at 01:40 PM ---------- Previous post was at 01:37 PM ----------
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Tapatalk
---------- Post added at 01:40 PM ---------- Previous post was at 01:40 PM ----------
I hope that helps.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Reading up on your link now, will let you know result. Thank you!
edit: ok, I looked at the download mode accessible link, and that is one I'd tried before. Flashed the ALL I535 .tar and ran in to the auth fail message on odin. Going to try the other method now.
No one has been able to unlock the bootloader since 4.3. I doubt anyone's really trying now because the phone is older. Sorry man.
Sent from my SCH-I535 using Tapatalk
Hybridnoob said:
No one has been able to unlock the bootloader since 4.3. I doubt anyone's really trying now because the phone is older. Sorry man.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I got towelroot to work to get my S3 to be able to install SuperSU and then Titanium Backup, but haven't found a bootloader unlock either. So, the phone is pretty much bricked?
jester369 said:
I got towelroot to work to get my S3 to be able to install SuperSU and then Titanium Backup, but haven't found a bootloader unlock either. So, the phone is pretty much bricked?
Click to expand...
Click to collapse
Bricked no, if your able to install apps it's far from bricked. He is correct however once the bootloader is locked your pretty much stuck. Replacements directly from verizon are coming back with 4.4.2 installed.
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Unless you can find a fully stock ROM to flash via Odin, you may be in trouble. Unlocking the bootloader isn't an option. Without seeing your phone, I won't say it's bricked though.
Sent from my SCH-I535 using Tapatalk
Hybridnoob said:
Unless you can find a fully stock ROM to flash via Odin, you may be in trouble. Unlocking the bootloader isn't an option. Without seeing your phone, I won't say it's bricked though.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
As I just stated in the post above yours if you can install apps the phone isn't bricked. Bootloader unlocking on the S3 with 4.3 or 4.4 is merely a possibility but probably unlikely
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Hybridnoob said:
No one has been able to unlock the bootloader since 4.3. I doubt anyone's really trying now because the phone is older. Sorry man.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
All right, tried the recover from computer, it's to recover a bricked bootloader. My bootloader isn't bricked, it's the actual ROM that's non functional. So that didn't help. Just need a stock ROM to flash to the phone, can still get to download mode, which connects to Odin, no problem, can also get to stock recovery, Volume Up, Menu, power. Just need a stock ROM that works, or a way to get whatever authorization Odin or the phone wants in order to flash a boot chain and stock ROM. (I do know now not to flash a custom ROM, thank you for that!)
ShapesBlue said:
Bricked no, if your able to install apps it's far from bricked. He is correct however once the bootloader is locked your pretty much stuck. Replacements directly from verizon are coming back with 4.4.2 installed.
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
Sorry, some clarification. I have TWO S3s, MY S3 is fine, and can install apps. The girlfriend's S3 is soft bricked and in a boot loop. Bootloader is fine, download mode is fine. Just hangs on red Verizon boot screen, when it gets to lock screen says process com.android.phone has stopped and reboots.
Hybridnoob said:
Unless you can find a fully stock ROM to flash via Odin, you may be in trouble. Unlocking the bootloader isn't an option. Without seeing your phone, I won't say it's bricked though.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Been trying to find a fully stock ROM and been unsuccessful. Any I've found have failed in Odin and failed to flash in stock recovery mode, something about a certificate failure.
jester369 said:
Sorry, some clarification. I have TWO S3s, MY S3 is fine, and can install apps. The girlfriend's S3 is soft bricked and in a boot loop. Bootloader is fine, download mode is fine. Just hangs on red Verizon boot screen, when it gets to lock screen says process com.android.phone has stopped and reboots.
Click to expand...
Click to collapse
I definitely would not call that soft bricked. Can you get into recovery and try clearing cache and reboot? Worst case, factory reset from recovery and you should be good to go.
Sent from my SCH-I535 using Tapatalk
Hybridnoob said:
I definitely would not call that soft bricked. Can you get into recovery and try clearing cache and reboot? Worst case, factory reset from recovery and you should be good to go.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I can get in to recovery, I've tried clearing cache, factory reset, no dice. Exact same thing.
have you tried using odin or kies to just flash the stock NE1 4.4.2? youll have to reroot with towelroot afterwards but atleast the phone will be functional. as for the bootloader, sounds like its locked anyways so it wont be no worse than the shape youre in already.
4.4 and 4.3 Sticky Roll-Up Thead
http://forum.xda-developers.com/showthread.php?t=2639337
TouchWiz 4.4 Download List
http://forum.xda-developers.com/gal...4-download-list-7-10-14-t2812189/post54062704
VRUDNE1 (Android 4.4.2 - Kit Kat) No-Wipe Factory Image
http://forum.xda-developers.com/showthread.php?t=2795659
-somebody- said:
have you tried using odin or kies to just flash the stock NE1 4.4.2? youll have to reroot with towelroot afterwards but atleast the phone will be functional. as for the bootloader, sounds like its locked anyways so it wont be no worse than the shape youre in already.
Click to expand...
Click to collapse
I have tried that, I believe I haven't been able to find a stock 4.4.2 ROM though. I'm fine with rebooting and re rooting, that's not my concern, even if I can't root, I don't care about that. Could you point me to a solid stock ROM image?
The images I've tried, numerous labeled stock ROMs, and, out of desperation last night, two custom ROMs. Through either recovery mode, or Odin, all failed, through recovery it was a certificate error, and through Odin it was an authorization error. AUTH FAIL, specifically.
jester369 said:
I have tried that, I believe I haven't been able to find a stock 4.4.2 ROM though. I'm fine with rebooting and re rooting, that's not my concern, even if I can't root, I don't care about that. Could you point me to a solid stock ROM image?
The images I've tried, numerous labeled stock ROMs, and, out of desperation last night, two custom ROMs. Through either recovery mode, or Odin, all failed, through recovery it was a certificate error, and through Odin it was an authorization error. AUTH FAIL, specifically.
Click to expand...
Click to collapse
that last link i believe is the actual tar file for NE1 if i remember correctly, i used kies when i updated mine and i didnt encounter any errors. did you delete the .md5 so it was just .tar (not .tar.md5) before trying it in odin? i know most people prefer odin over kies but if youre having this many problems kies is worth a shot.
worst case i can upload the one i have
-somebody- said:
that last link i believe is the actual tar file for NE1 if i remember correctly, i used kies when i updated mine and i didnt encounter any errors. did you delete the .md5 so it was just .tar (not .tar.md5) before trying it in odin? i know most people prefer odin over kies but if youre having this many problems kies is worth a shot.
worst case i can upload the one i have
Click to expand...
Click to collapse
I will try that and report back. Thank you!

T-Mobile h91810i update

For those who haven't rooted and have received the new OTA or updated manually via LG Bridge, have you seen or read of any changes from the update? Of course, other than them patching out the Dirty Santa exploit we've used for root. Speaking of which... (sidebar) manufacturer pushing out exploit patches shortly after root being achieved on a device sounds very Note7-nostalgic to me.
So far root has been a disaster for non devs. Bricks and other problems with stuff not working. I wouldn't root this phone yet, it is not like a Samsung where you can just easily fix everything with Odin. That said, I will not accept an OTA update if all it does is patch the root method. They had better have some useful things like camera focusing faster, battery lasting more than 3 hours, etc. for me to update.
Root is fine and everything world perfect. At least for h918.
hotstocks said:
So far root has been a disaster for non devs. Bricks and other problems with stuff not working. I wouldn't root this phone yet, it is not like a Samsung where you can just easily fix everything with Odin. That said, I will not accept an OTA update if all it does is patch the root method. They had better have some useful things like camera focusing faster, battery lasting more than 3 hours, etc. for me to update.
Click to expand...
Click to collapse
Quite honestly I've only seen a couple of people who have hard bricked their devices - mainly just either one who used the dirtysanta on a phone that was not listed as compatible and the dev of dirtysanta when testing out reverting back to stock per request by users.
Rooting/Unlocking this phone has significantly increased battery and performance especially after installing Tilde88's ROM. Sure for the others who have variants outside of T-Mobile (like me), we have the static boot screen, but considering how minimal the impact is - it's well worth it. To each their own, but I would not say rooting is a disaster for this phone.
Nougat is still really new. Only a handful of phones support it. Hell, if you look at the Pixel forums, I've seen many more bricks there than over here.
twistedvip said:
Quite honestly I've only seen a couple of people who have hard bricked their devices - mainly just either one who used the dirtysanta on a phone that was not listed as compatible and the dev of dirtysanta when testing out reverting back to stock per request by users.
Rooting/Unlocking this phone has significantly increased battery and performance especially after installing Tilde88's ROM. Sure for the others who have variants outside of T-Mobile (like me), we have the static boot screen, but considering how minimal the impact is - it's well worth it. To each their own, but I would not say rooting is a disaster for this phone.
Nougat is still really new. Only a handful of phones support it. Hell, if you look at the Pixel forums, I've seen many more bricks there than over here.
Click to expand...
Click to collapse
I agree with @twistedvip. Definitely not a disaster. I am on @OvrDriVE 's ROM coming from stock rooted h918 and the phone is definitely faster with better battery life. Everything works. Couldn't be happier.
twistedvip said:
Quite honestly I've only seen a couple of people who have hard bricked their devices - mainly just either one who used the dirtysanta on a phone that was not listed as compatible and the dev of dirtysanta when testing out reverting back to stock per request by users.
Rooting/Unlocking this phone has significantly increased battery and performance especially after installing Tilde88's ROM. Sure for the others who have variants outside of T-Mobile (like me), we have the static boot screen, but considering how minimal the impact is - it's well worth it. To each their own, but I would not say rooting is a disaster for this phone.
Nougat is still really new. Only a handful of phones support it. Hell, if you look at the Pixel forums, I've seen many more bricks there than over here.
Click to expand...
Click to collapse
I do have a T-mobile. Is Tilde88's ROM a stock rom with just some tweaks or not Noughat? Also is there a program like Odin that you can flash back to non-rooted whenever you want? Say I want to play PokemonGo, well you can't if rooted. So with Samsung phones you just have supersu unroot, play, and then odin flash root back. It literally takes 1 minutes and nothing ever goes wrong. Is there a program like Odin to do that? If not, then LG phones really aren't ready to be rooted and unrooted to use Android Pay, PokemonGo, and all the other software that you can't use when rooted. And don't get me wrong, I have had and rooted every Samsung phone since the S3. But this is my first LG, and I just don't see an easy way to do things like via Odin. Hell even if you brick a Samsung you can usually just Odin flash stock rom and be back to new. How do you do this with LG?
Unfortunately LG doesn't provide as powerful of a tool as Odin is. They have LG bridge and Uppercut (I believe those are the two names) where you can flash TOTs and KDZ files to be able to restore back to stock completely and flash updates. I believe currently we dont have any way to flash TOT files though and thus are stuck. But for T-Mobile users, you should be able to simply relock your phone and go right back to stock very easily.
As for switching back between root and stock - using this dualboot-patcher you might be able to do what you're looking to do. Just know the root method used is dependent upon the dirtycow exploit. T-Mobiles 10i update has the Dec 5 security update which fixed that exploit. I don't know much about the dualbooting though so it may not be what you're looking for after all.
Too bad lg bridge keeps returning unable to download update error.
Sent from my LG-H918 using XDA Premium HD app
It worked for me but it took forever. Also it failed mid way and I had to pull out the battery, disconnect and reconnect the phone but then it updating without any problems.
The only thing I noticed so far is that it brings the Android security patch up to December 1st, so it's not completely useless.
hotstocks said:
I do have a T-mobile. Is Tilde88's ROM a stock rom with just some tweaks or not Noughat? Also is there a program like Odin that you can flash back to non-rooted whenever you want? Say I want to play PokemonGo, well you can't if rooted. So with Samsung phones you just have supersu unroot, play, and then odin flash root back. It literally takes 1 minutes and nothing ever goes wrong. Is there a program like Odin to do that? If not, then LG phones really aren't ready to be rooted and unrooted to use Android Pay, PokemonGo, and all the other software that you can't use when rooted. And don't get me wrong, I have had and rooted every Samsung phone since the S3. But this is my first LG, and I just don't see an easy way to do things like via Odin. Hell even if you brick a Samsung you can usually just Odin flash stock rom and be back to new. How do you do this with LG?
Click to expand...
Click to collapse
First off, if you don't know about something, you should probably keep your opinions to your self. It took me the ability to read, and twenty minutes to unlock the bootloader and root my LG-H918 (T-Mobile) then when I had to take it back I flashed the stock odexed rom, unrooted, and locked the bootloader in about 20 minutes as well... I'm no developer, but I'm smart enough to read instructions, comprehend them, and follow them to get a desired result... And if you can recover from a brick... Ever, then you aren't hard bricked. Hard bricked means your device is dead, and unrecognizable by any means, or unrecoverable. You are referring to a soft brick. Please learn what you are talking about before posting.
"sometimes it is better to keep one's mouth shut and be thought a fool, than to open it and remove all doubt"
Sent from my LG-H918 using Tapatalk
ZDeuce2 said:
First off, if you don't know about something, you should probably keep your opinions to your self. It took me the ability to read, and twenty minutes to unlock the bootloader and root my LG-H918 (T-Mobile) then when I had to take it back I flashed the stock odexed rom, unrooted, and locked the bootloader in about 20 minutes as well... I'm no developer, but I'm smart enough to read instructions, comprehend them, and follow them to get a desired result... And if you can recover from a brick... Ever, then you aren't hard bricked. Hard bricked means your device is dead, and unrecognizable by any means, or unrecoverable. You are referring to a soft brick. Please learn what you are talking about before posting.
"sometimes it is better to keep one's mouth shut and be thought a fool, than to open it and remove all doubt"
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
Think what you want, but I am also not a dev, but a techie guy. To me it is irrelevant if you have a soft brick if you don't have the tools and knowledge to recover it, which 99.99% of LG V20 users DON'T HAVE. So your soft bricked LG V20 might as well be a hard brick. My point is that 90% of regular Joes can use Odin and recover easily from a soft brick, on the LG V20, NOT SO MUCH. If you think finding LG's cryptic flashing software, learning ADB, and whatever else is needed is something that most users can do, you are greatly mistaken. Sure, one day there might be freely available, easy to use LG V20 flashing software similiar to Odin, but right now there isn't yet. I've rooted and flashed HTCs and Samsungs never with issues, but this LG is a far more complicated beast. I am not saying it can't be done, I am saying that most people can't do it or recover if there is a mistake. Just sayin don't mess with it if you are a newb yet, until there is more mature flashing software.
ZDeuce2 said:
when I had to take it back I flashed the stock odexed rom, unrooted, and locked the bootloader in about 20 minutes as well...
Click to expand...
Click to collapse
what are your steps to return to stock?
Flash stock odexed rom using TWRP
Unrooted - is this a step?
Did you have to flash stock recovery before locking the bootloader?
MidtownHD said:
what are your steps to return to stock?
Flash stock odexed rom using TWRP
Unrooted - is this a step?
Did you have to flash stock recovery before locking the bootloader?
Click to expand...
Click to collapse
I think they took that update out coz everyone is having trouble updating.
I really want to update, there's many bugs right now but I don't want to lose my root
hotstocks said:
Think what you want, but I am also not a dev, but a techie guy. To me it is irrelevant if you have a soft brick if you don't have the tools and knowledge to recover it, which 99.99% of LG V20 users DON'T HAVE. So your soft bricked LG V20 might as well be a hard brick. My point is that 90% of regular Joes can use Odin and recover easily from a soft brick, on the LG V20, NOT SO MUCH. If you think finding LG's cryptic flashing software, learning ADB, and whatever else is needed is something that most users can do, you are greatly mistaken. Sure, one day there might be freely available, easy to use LG V20 flashing software similiar to Odin, but right now there isn't yet. I've rooted and flashed HTCs and Samsungs never with issues, but this LG is a far more complicated beast. I am not saying it can't be done, I am saying that most people can't do it or recover if there is a mistake. Just sayin don't mess with it if you are a newb yet, until there is more mature flashing software.
Click to expand...
Click to collapse
Speak for yourself, you are definitely in the minority, most of us know how to do these things or we wouldn't be here doing them... And I could care less if you want to call it a pb&j, it's still a soft brick...
Sent from my LG-H918 using Tapatalk
---------- Post added at 03:12 PM ---------- Previous post was at 03:07 PM ----------
MidtownHD said:
what are your steps to return to stock?
Flash stock odexed rom using TWRP
Unrooted - is this a step?
Did you have to flash stock recovery before locking the bootloader?
Click to expand...
Click to collapse
Remove root in SuperSU app. And I did not change recovery, just relocked the bootloader
Sent from my LG-H918 using Tapatalk
---------- Post added at 03:14 PM ---------- Previous post was at 03:12 PM ----------
wing_addict_usa said:
I really want to update, there's many bugs right now but I don't want to lose my root
Click to expand...
Click to collapse
NATF's latest rom is the update... On LGH918
Sent from my LG-H918 using Tapatalk
ZDeuce2 said:
Remove root in SuperSU app. And I did not change recovery, just relocked the bootloader
Click to expand...
Click to collapse
What happens after you re-lock the bootloader? does it work well with TWRP installed? or does it replace it automatically with the stock one? and everything becomes "stock"?
MidtownHD said:
What happens after you re-lock the bootloader? does it work well with TWRP installed? or does it replace it automatically with the stock one? and everything becomes "stock"?
Click to expand...
Click to collapse
Honestly, I went back as stock as possible to see if it fixed my speaker distortion problem, (it did not) but just left it that way and locked it before I returned it just so the can't be check for corruption screen didn't appear, it still worked fine, but I never checked whether the stock bootloader overwrote twrp. The corruption screen went away which is what I was trying for.
Sent from my LG-H918 using Tapatalk
Has anyone been able to capture the URL or the zip for the update?
MidtownHD said:
what are your steps to return to stock?
Flash stock odexed rom using TWRP
Unrooted - is this a step?
Did you have to flash stock recovery before locking the bootloader?
Click to expand...
Click to collapse
So if I may join in I flashed a back up and I can't get into my device is there a tool I can't get into recovery for some reason
Sent from my Nexus 6P using Tapatalk
ZDeuce2 said:
Speak for yourself, you are definitely in the minority, most of us know how to do these things or we wouldn't be here doing them... And I could care less if you want to call it a pb&j, it's still a soft brick...
Sent from my LG-H918 using Tapatalk
---------- Post added at 03:12 PM ---------- Previous post was at 03:07 PM ----------
Remove root in SuperSU app. And I did not change recovery, just relocked the bootloader
Sent from my LG-H918 using Tapatalk
---------- Post added at 03:14 PM ---------- Previous post was at 03:12 PM ----------
NATF's latest rom is the update... On LGH918
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
This says M https://forum.xda-developers.com/v20/development/rom-natf-1-00-test-5-debloated-stock-t3509750

Categories

Resources