Related
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.
I need to return my phone and ive used the guide to reset my flash counter with triangle away (which was never tripped, just did it for piece of mind), then i used odin and used the stock kernel and stock image to reinstall back to stock. Everything passed but when i boot my phone up right under the samsung logo it still says custom with the unlock logo. How do i get rid of this so i can return my phone back to verizon?
EDIT***** So i re-rooted then installed ez-unlocker and locked the bootloader again. Then reinstalled stock image through odin and all is well now
shortguy088 said:
I need to return my phone and ive used the guide to reset my flash counter with triangle away (which was never tripped, just did it for piece of mind), then i used odin and used the stock kernel and stock image to reinstall back to stock. Everything passed but when i boot my phone up right under the samsung logo it still says custom with the unlock logo. How do i get rid of this so i can return my phone back to verizon?
Click to expand...
Click to collapse
Try locking your bootloader with Ez-Unlock in the play store.
fr8cture said:
Try locking your bootloader with Ez-Unlock in the play store.
Click to expand...
Click to collapse
My phones not rooted so i cant use the app.
I thought using Odin with the stock rom/kernel automatically locks the bootloader?
Sent from my SCH-I535 using xda app-developers app
Jarredw said:
I thought using Odin with the stock rom/kernel automatically locks the bootloader?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I thought so as well but when I restarted my phone it still said custom. I tried to factory wipe data after I reflashed stock and still didn't work. So I dont know what happened
Tap'n
Wish i could help but i have no idea. I guess your gonna have to try your luck.
techgov8 said:
I thought so as well but when I restarted my phone it still said custom. I tried to factory wipe data after I reflashed stock and still didn't work. So I dont know what happened
Tap'n
Click to expand...
Click to collapse
that means your bootloader is indeed locked...look around on the forums a bit! When the custom unlock screen is gone then your unlocked. I believe there is a guide in the dev section that explains this. :angel:
droidstyle said:
that means your bootloader is indeed locked...look around on the forums a bit! When the custom unlock screen is gone then your unlocked. I believe there is a guide in the dev section that explains this. :angel:
Click to expand...
Click to collapse
Well when you first boot up a brand new phone it doesn't have the custom on the samsung screen and that's locked
Tap'n
Need to get rid of custom Samsung bootloader screen
techgov8 said:
Well when you first boot up a brand new phone it doesn't have the custom on the samsung screen and that's locked
Tap'n
Click to expand...
Click to collapse
. I've tried all the guides and their bot working for me on my galaxy s4 d or s anyone know where I can find a step by step guide I'm a noon on rooting
garygnobriga said:
. I've tried all the guides and their bot working for me on my galaxy s4 d or s anyone know where I can find a step by step guide I'm a noon on rooting
Click to expand...
Click to collapse
Wait hold up if you have an s4 why are you on the S3 forums? I am assuming you have at&t , T-Mobile or Sprint go to those threads as it makes much more sense to do that.
Got the yellow triangle with " unauthorized software found on your device. Return to authorized Verizon dealer." I was trying to return this to stock and the directions on Odin said the bootloader had to be locked. I took the EZunlock and locked it back then all hell broke loose. Any ideas?
ergon said:
Got the yellow triangle with " unauthorized software found on your device. Return to authorized Verizon dealer." I was trying to return this to stock and the directions on Odin said the bootloader had to be locked. I took the EZunlock and locked it back then all hell broke loose. Any ideas?
Click to expand...
Click to collapse
where did u read the bootloader had to be locked? all u need to do is odin back to stock, root, unlock bootloader.
All you need to do is download Odin, and and whatever tar file you want, boot phone into download (volume down, home, power), select yes when it asks are you sure, open Odin, select the tar file and start. Easy schmeasy
Sent from my SCH-I535 using xda app-developers app
ergon said:
Got the yellow triangle with " unauthorized software found on your device. Return to authorized Verizon dealer." I was trying to return this to stock and the directions on Odin said the bootloader had to be locked. I took the EZunlock and locked it back then all hell broke loose. Any ideas?
Click to expand...
Click to collapse
You rebooted your phone after locking the bootloader. You shouldn't have done that. Your issue isn't unfixable tho, not by any means. IIRC VRALF2 I'm pretty sure is the only stock image that doesn't re-lock the bootloader(I haven't tested all of them). If you choose VRALG1 that will re-lock the bootloader for you when you flash it, it did for me the other day when I started over.
Just boot into download mode and flash the G1 thru Odin then do a factory wipe and you should be fine. I'm 99% sure you didn't trip the flash counter doing this, someone else chime in on this please?
And make sure you use PDA mode when you use Odin and don't unplug your phone from it until it says finished(even if it says removed, let it continue rebooting and doing its thing before unplugging. The Start and Cancel buttons should 'come back to life' when it's ok)
This might be the source the OP was referring to:
http://forum.xda-developers.com/showthread.php?t=1867253&highlight=odin+to+stock
Although it clearly says to NOT reboot after re-locking your bootloader, it does say that the first step is to lock it before flashing to stock via Odin. Further down in the thread he says he'll remove it from the guide, but I don't think flashing stock via Odin locks the BL so if youre trying to return it to Verizon I would lock it first.
nghtrain88 said:
This might be the source the OP was referring to:
http://forum.xda-developers.com/showthread.php?t=1867253&highlight=odin+to+stock
Although it clearly says to NOT reboot after re-locking your bootloader, it does say that the first step is to lock it before flashing to stock via Odin. Further down in the thread he says he'll remove it from the guide, but I don't think flashing stock via Odin locks the BL so if youre trying to return it to Verizon I would lock it first.
Click to expand...
Click to collapse
Certain stock images do. I've had g1 lock and I've read that he will to.
Don't get me wrong, locking it yourself prior to flashing thru Odin is a good thing to do just to make sure. It's easier than having to re-root just to lock it then flash all over again.
Brian Gove said:
Certain stock images do. I've had g1 lock and I've read that he will to.
Don't get me wrong, locking it yourself prior to flashing thru Odin is a good thing to do just to make sure. It's easier than having to re-root just to lock it then flash all over again.
Click to expand...
Click to collapse
the only stock rom i have found that locks the bootloader is vralhd... are you sure g1 locked your bootloader because i thought we had this conversation already lol? unless your returning the device, why would you even want to lock it back up?
droidstyle said:
the only stock rom i have found that locks the bootloader is vralhd... are you sure g1 locked your bootloader because i thought we had this conversation already lol? unless your returning the device, why would you even want to lock it back up?
Click to expand...
Click to collapse
Yeah, I meant HD, not HE.
We did, but that was when I flashed F2. F2 doesn't lock it, but a week or so ago I had to flash back to stock to start over, used G1 and it re-locked my bootloader on me.
One of these days when I'm bored I'll sit down and try them all just to double check too.
cvbcbcmv said:
Don't over think it. This is simply happening because the bootloader is locked and your trying to run a custom rom. Just restore to stock and you're fine.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I am having the same issue but when I go to restore back to stock Odin says it has completed 100% but when the phone reboots I get the triangle again. Please help.
i get this very same problem with with yellow triangle when i try to flash a rom it happend to me 2 times so i had to odin back any ideas why it happens when i try to flash a rom
Bootloader is locked
Sent from my SCH-I535 using xda app-developers app
Verizon note 2 will not go into download just yellow triangle
Okay bye hope someone can help me I rooted my galaxy note 2 by Verizon with framaroot and didn't realize the boot loader was locked and try to download ROM manager and it locked my phone up all I got was a yellow triangle said that they did not recognize a program then I did Adam's way of returning to stock with casual will not read it so then I found the root66_vzw..... same as stock but rooted and unlock boot loader and I flashed it and the pit file that went with it using Odin. It said pass when everything was done it upload bar on the phone I seen it on the screen and when it went to reset then it come back to the same Verizon yellow triangle and now I can't get it to going to download mode or do anything at all except for when I plug in the cable to my computer the yellow triangle come on. Can someone help?? Please I really we'd love to have my phone back! I would appreciate it very much thank you sincerely
worknman69 said:
Okay bye hope someone can help me I rooted my galaxy note 2 by Verizon with framaroot and didn't realize the boot loader was locked and try to download ROM manager and it locked my phone up all I got was a yellow triangle said that they did not recognize a program then I did Adam's way of returning to stock with casual will not read it so then I found the root66_vzw..... same as stock but rooted and unlock boot loader and I flashed it and the pit file that went with it using Odin. It said pass when everything was done it upload bar on the phone I seen it on the screen and when it went to reset then it come back to the same Verizon yellow triangle and now I can't get it to going to download mode or do anything at all except for when I plug in the cable to my computer the yellow triangle come on. Can someone help?? Please I really we'd love to have my phone back! I would appreciate it very much thank you sincerely
Click to expand...
Click to collapse
We don't have a Note 2 go to the Note 2 forums to get help.
I'm in need of some serious help here guys. Tonight I tried to update my rooted s3 on 4.1.2 to the new update 4.3. I accepted the download and after the download I installed it. My phone booted into the yellow Verizon triangle telling me it noticed I have unauthorized programs on my phone not authorized by Verizon and to turn the phone off and take it into Verizon. I tried to boot into clockwork recovery and it would not let me and booted back to the yellow Verizon triangle.
I have no idea what to do, did I permanently brick my phone or can I get back to 4.1.2 some how? I would greatly appreciate any information pointing in the direction to fix this.
I managed to recover my phone! I pulled the battery and sim card prior to signing up on xda because I read someone having the same issue on a note 2. Once the battery and sim is removed let it set for a half hour then place the sim and battery back into the phone. Once they were back in the phone press the power button ,it should boot right up as it normally would. I'm not saying there isn't more than one way of fixing this issue but this method worked for me and I thought I would share for those who might experience this yellow triangle notification as well. On a side note it did not successfully updated my phone but returned me back to 4.1.2
You need to be 100% stock to take an OTA (unrooted, stock recovery). The easiest way to get to that state is to ODIN a stock factory image. This will delete your internal storage.
Was your bootloader unlocked prior to trying to update to 4.3? I'm assuming so if you were running CWM recovery.
I actually had the same problem and am trying to fix right now. I tried running rootkeeper before the update, but that obviously didn't work. Anyone know where I can get the 4.1.2 image to flash? Also, do i need to do that "Triangle Away"? My custom binary dL says "Yes (4 counts)."
irl5fan said:
I actually had the same problem and am trying to fix right now. I tried running rootkeeper before the update, but that obviously didn't work. Anyone know where I can get the 4.1.2 image to flash? Also, do i need to do that "Triangle Away"? My custom binary dL says "Yes (4 counts)."
Click to expand...
Click to collapse
Triangle Away is free for XDA members. Must be stock rooted to work. Won't work on every rom. May have to odin stock, root run Triangle and then Odin Stock again. Remove tar from MF1 zip to Odin. Once on 4.3 there is no return and no unlock. Can run Saferoot to root. Do not try to unlock or flash custom recovery or device will brick.
Triangle Away- http://forum.xda-developers.com/showpost.php?p=22462960&postcount=1
MF1- http://www.androidfilehost.com/?fid=23134718111254196
BattsNotIncld said:
You need to be 100% stock to take an OTA (unrooted, stock recovery).
Click to expand...
Click to collapse
You sure about that? Seems quite a few people were on 4.1.2 stock + rooted, took the update, and went to 4.3 fine, but lost root.
Quite a few in the main 4.3 thread.
BattsNotIncld said:
You need to be 100% stock to take an OTA (unrooted, stock recovery). The easiest way to get to that state is to ODIN a stock factory image. This will delete your internal storage.
Was your bootloader unlocked prior to trying to update to 4.3? I'm assuming so if you were running CWM recovery.
Click to expand...
Click to collapse
Yes my bootloader is unlocked. I think I'm going to postpone the 4.3 update until I hear better reviews. I have seen posts on here where people are having issues after taking the update. I simply did not know what was going on if I had hard bricked my device or not, luckily I did not and was able to get back to 4.1.2
Rsc25 said:
Yes my bootloader is unlocked. I think I'm going to postpone the 4.3 update until I hear better reviews. I have seen posts on here where people are having issues after taking the update. I simply did not know what was going on if I had hard bricked my device or not, luckily I did not and was able to get back to 4.1.2
Click to expand...
Click to collapse
I updated my wifes Via the OTA and she has had 0 issues. I think most of the issues people are having after the OTA are self inflicted.
stock image
BattsNotIncld said:
You need to be 100% stock to take an OTA (unrooted, stock recovery). The easiest way to get to that state is to ODIN a stock factory image. This will delete your internal storage.
Was your bootloader unlocked prior to trying to update to 4.3? I'm assuming so if you were running CWM recovery.
Click to expand...
Click to collapse
just wonderingim trying to get a stock vrbm1 tar but every link I try is down I did have it on a usb but lost it, originally from dark menace if you know of another source would be great ive downloaded a few but md5 doesn't match
I know this isn't technically the right section for this but I put it here in hopes more people would see it. This is very important for anyone rooting using the dirtysanta method and perhaps other methods as well. It would be nice if this could get a sticky because people need to see this or this problem is going to keep occurring. I'm seeing it all over the threads.
DO NOT FACTORY RESET FROM INSIDE THE ROM. DO NOT USE LG's BUILT IN FACTORY RESET IN THE PHONE OR YOU WILL GET STUCK IN RECOVERY. Use the factory reset option inside of TWRP if you want to do a factory reset.
There have been many people (myself included even though I knew better and told myself not to do it before I did) who have got stuck in recovery because of this and it's not common sense to get out of it. I've been rooting and messing with this stuff for over 5 years and for 2 hours tried every trick I knew and nothing worked. What did finally end up working for me personally is this:
*restore your full stock backup (if you have one)
*after the backup is restored, in TWRP, go to mount, and mount the system. Check the box and press the mount USB storage button
*power off device
*use the button combo to boot into TWRP. It's volume down + power (hold them down), as soon as you see the LG logo let go of power for a brief moment and continue to press and hold both buttons until a white screen comes up. Choose yes for the next two options. This will bring you back into TWRP.
*now go back to mount and check system, and press the mount storage button, and reboot system.
lol this is only because it give you your stock boot.img. So if you factory reset, you have to flash SuperSU, no need to freak out.
If you format /system, you will need to flash a ROM, if the ROM does not flash SuperSU, you will h ave to flash it.
That's all folks!
That said, who wants a VZW Custom ROM and Kernel? Making the thread now. Identical to my H918 5.1 MOD ROM
Tilde88 said:
lol this is only because it give you your stock boot.img. So if you factory reset, you have to flash SuperSU, no need to freak out.
If you format /system, you will need to flash a ROM, if the ROM does not flash SuperSU, you will h ave to flash it.
That's all folks!
That said, who wants a VZW Custom ROM and Kernel? Making the thread now. Identical to my H918 5.1 MOD ROM
Click to expand...
Click to collapse
I tried flashing supersu.zip but that wouldn't work either. I challenge you to factory reset in the rom and then once stuck in recovery flash a new rom and the supersu zip and see if that works. I did this several times and it wouldn't work. I tried it with flashing a rom, and after restoring a backup. What appears to be happening is the system isn't mounting and it doesn't recognise that you have a ROM installed.
Not freaking out either, just trying to let people know not to factory reset inside the rom but use TWRP. There have been many people with this issue.
imucarmen said:
I tried flashing supersu.zip but that wouldn't work either. I challenge you to factory reset in the rom and then once stuck in recovery flash a new rom and the supersu zip and see if that works. I did this several times and it wouldn't work. I tried it with flashing a rom, and after restoring a backup. What appears to be happening is the system isn't mounting and it doesn't recognise that you have a ROM installed.
Not freaking out either, just trying to let people know not to factory reset inside the rom but use TWRP. There have been many people with this issue.
Click to expand...
Click to collapse
Oh, sorry. I overlooked something. That you had in huge bold caps the words IN THE ROM lol, my bad. I've never factory reset from within the ROM.
But my post stands when factory resetting from TWRP.
Tilde88 said:
Oh, sorry. I overlooked something. That you had in huge bold caps the words IN THE ROM lol, my bad. I've never factory reset from within the ROM.
But my post stands when factory resetting from TWRP.
Click to expand...
Click to collapse
Yea I knew better too, that's the bad part. In 5+ years I've never factory reset while in a rom when I have root and TWRP installed. Before I did it I even told myself it was probably a bad idea and I should just use TWRP. But my lazy conscience said "ahhh what the heck! just do it, it's too much trouble to boot into TWRP and besides, it might work ok" I hate my lazy consicence :'(
Exactly what I did and exactly what happened.
Gonna try this in the AM. One question...
If I'm able to flash back to "stock" using a deoxed stock rom, how can I then get rid of the boot warning so I can return this device to T-Mobile?
mrbigdrawsz said:
Exactly what I did and exactly what happened.
Gonna try this in the AM. One question...
If I'm able to flash back to "stock" using a deoxed stock rom, how can I then get rid of the boot warning so I can return this device to T-Mobile?
Click to expand...
Click to collapse
You'll need to return to full stock. I can't verify it works but this thread here claims to have a method for returning to stock.
imucarmen said:
You'll need to return to full stock. I can't verify it works but this thread here claims to have a method for returning to stock.
Click to expand...
Click to collapse
Well pray for me. Downloading now and will try first thing tomorrow.
mrbigdrawsz said:
Well pray for me. Downloading now and will try first thing tomorrow.
Click to expand...
Click to collapse
Did it work for you? Also since there is no t mobile rom there what did you use?
thegameksk said:
Did it work for you? Also since there is no t mobile rom there what did you use?
Click to expand...
Click to collapse
I used this guide https://goo.gl/ZHZPfO and it worked perfectly. Had a little stress when attempting to flash the stock recovery, but after installing two again, I was able to revert back to stock. Locked bootloader and it's as if I never did anything but boot up the stock OS.
Returning to T-Mobile today and just waiting on my Oneplus 3T to ship (granted I'm pissed off because the 128gb version is out of stock).
mrbigdrawsz said:
I used this guide https://goo.gl/ZHZPfO and it worked perfectly. Had a little stress when attempting to flash the stock recovery, but after installing two again, I was able to revert back to stock. Locked bootloader and it's as if I never did anything but boot up the stock OS.
Returning to T-Mobile today and just waiting on my Oneplus 3T to ship (granted I'm pissed off because the 128gb version is out of stock).
Click to expand...
Click to collapse
Glad you got it fixed.
Just for the record, this thread isn't for helping people get back to stock, its main focus is to warn people not to factory reset inside the rom. Then I just shared the method that worked for me to get out of being stuck in TWRP. Not saying you implied any different, I'm just clarifying for anyone that may read in the future. It's awesome return to stock methods are now popping up which are usually good for fixing all sorts of issues.
Enjoy your OnePlus 3T