So, a month or 2 ago, I followed some instructions on here to unlock bootloader using ez-unlock, then just a few days ago, JB update came out and after a few days I decided to wipe my phone and start fresh, now I want to relock the boot loader as I don't plan on using any roms, I was just curious.
now, when i try to run ez-lock, it comes up to a white screen and won't load fully or locks up the phone
i need some help re-locking. any ideas?
Have you already flashed the JB update or taken the OTA update? I have you then your bootloader is already locked again. If you haven't flashed any of the updates, I would check and make sure that you still have working root access. If you don't you will need to re-root. If you have root you could try a different version of EZ-Unlock. 1.2 is usually the best, but you could try 1.3.
Bootloader
BigErnM said:
Have you already flashed the JB update or taken the OTA update? I have you then your bootloader is already locked again. If you haven't flashed any of the updates, I would check and make sure that you still have working root access. If you don't you will need to re-root. If you have root you could try a different version of EZ-Unlock. 1.2 is usually the best, but you could try 1.3.
Click to expand...
Click to collapse
I did update to JB when it came out. the reason i think it's still unlocked is redbox put out a new app, and apparently it's not working with rooted devices and it comes up on mine stating there is an error and the article says the error is due to unlocked bootloader.
i just tried 1.2 and same, either comes up to white screen or locks up my phone and I have to pull battery
How did you update to JB? If you took the OTA your bootloader is definitely locked. If you followed one of the guides in the development section it may or may not be locked. Since you want to start fresh you could just flash the factory JB image and that will wipe everything, remove root and lock the bootloader. See section 5 in this guide: http://forum.xda-developers.com/showthread.php?t=1762709.
BigErnM said:
How did you update to JB? If you took the OTA your bootloader is definitely locked. If you followed one of the guides in the development section it may or may not be locked. Since you want to start fresh you could just flash the factory JB image and that will wipe everything, remove root and lock the bootloader. See section 5 in this guide: http://forum.xda-developers.com/showthread.php?t=1762709.
Click to expand...
Click to collapse
When I reboot the phone, on the first screen it shows a lock and says "custom", what is that telling me?
And yes, it was OTA.
That is telling you that your bootloader is locked. If you were unlocked you wouldn't see the message. The app error you are seeing must be coming from something else. You could still try what I posted above to get a totally clean start or you could try doing a factory reset on your phone.
BigErnM said:
That is telling you that your bootloader is locked. If you were unlocked you wouldn't see the message. The app error you are seeing must be coming from something else. You could still try what I posted above to get a totally clean start or you could try doing a factory reset on your phone.
Click to expand...
Click to collapse
The icon shows it unlocked and did a factory reset yesterday.
The icon it shows has a picture of an unlocked lock, but trust me your bootloader is locked. An unlocked bootloader will not show the word custom or that icon. You also probably do not have root access anymore which is why EZ-unlock won't load. You should try flashing the factory image I linked to above. That will almost certainly fix your issue, unless it is just a problem with the app.
BigErnM said:
The icon it shows has a picture of an unlocked lock, but trust me your bootloader is locked. An unlocked bootloader will not show the words custom or that icon. You should try flashing the factory image I linked to above. That will almost certainly fix your issue, unless it is just a problem with the app.
Click to expand...
Click to collapse
Hmm.. ok
Please read forum rules before posting
Rule 15 tells you where to post if you are confused
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
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.
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.
Hi All:
I was having some signal quality issues and Verizon had my apply the newest software update available. I was rooted, but after the update i lost root. It said the update failed, but it also says my phone is up to date. Now when I reboot the phone one of the screens says "Samsung Custom" with a a picture of an un-locked lock (i don't believe it showed that before).
1) Can i go through the process of rooting again without screwing up my phone? Do i need to do anything prior to rooting again if I can root again?
2) What does that screen on the reboot menu mean?
3) Should i bother to do Verizon software updates in the future?
Sorry if this has been covered elsewhere, I couldn't find a thread in my search. Thanks for your help!
This has been discussed to death, especially in the thread that YOU read to root your phone. You NEVER take an OTA update when rooted. You will most defiantly lose root with the possibility of locking your bootloader and never being able to root again or unlock the bootloader. Since you are this deep, you can do 1 of 2 things. 1. Sit tight and see what is figured out. 2. Odin to a pre-rooted image, restore your backup, and wait to see what the devs say about it.
HHF2 said:
This has been discussed to death, especially in the thread that YOU read to root your phone. You NEVER take an OTA update when rooted. You will most defiantly lose root with the possibility of locking your bootloader and never being able to root again or unlock the bootloader. Since you are this deep, you can do 1 of 2 things. 1. Sit tight and see what is figured out. 2. Odin to a pre-rooted image, restore your backup, and wait to see what the devs say about it.
Click to expand...
Click to collapse
Well I guess I forgot that little bit of valuable information. So does that reboot screen just mean my bootloader is locked? Also, my backup was deleted somehow during the update process. I tried to go into recovery and load my backup, but it is no longer available.
If you have an unlocked lock, I would thing that would mean unlocked, right? Do you still have your custom recovery?
fillyo said:
If you have an unlocked lock, I would thing that would mean unlocked, right? Do you still have your custom recovery?
Click to expand...
Click to collapse
I have ROM Manager, which i used to access CWM. But if i try to boot into recover from a power off state it says "System Software not authorized by VZW has be found on your phone. Please turn off your phone and go to the nearest VZW store for help." At the top of that screen in red it says "Secure Fail: Kernel." So that leads me to believe I don't have a custom recovery anymore, correct?
irl5fan said:
Well I guess I forgot that little bit of valuable information. So does that reboot screen just mean my bootloader is locked? Also, my backup was deleted somehow during the update process. I tried to go into recovery and load my backup, but it is no longer available.
Click to expand...
Click to collapse
Follow the steps here to root the new OTA: http://forum.xda-developers.com/showthread.php?t=2046439. The unlocked lock and custom when you boot up actually does mean that your bootloader has been relocked. Strange way to show it though. You could wait until mrRobinson updates his no wipe odin factory images but that might be a couple days. I always use that method instead.
BigErnM said:
Follow the steps here to root the new OTA: http://forum.xda-developers.com/showthread.php?t=2046439. The unlocked lock and custom when you boot up actually does mean that your bootloader has been relocked. Strange way to show it though. You could wait until mrRobinson updates his no wipe odin factory images but that might be a couple days. I always use that method instead.
Click to expand...
Click to collapse
Ok yeah I'll check that out if he updates this week. Do I need to do a factory reset or anything or just leave my phone as is for now?
Sent from my SCH-I535 using xda app-developers app
You don't have to reset anything if you don't want to. You can flash the full wipe or no wipe version. Everybody has their own preferences, I like the no-wipe versions. I usually avoid taking the Verizon OTAs directly by disabling the software update service with Titanium Backup Pro since they screw up root and the bootloader. I wait until there is an ODIN flashable image of it. Others prefer to take the OTA and root using the guide above, or flash the odex or deodex versions in recovery like the ones here: http://forum.xda-developers.com/showthread.php?t=2177798.
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Hey everyone so i have a XT926
System version 9.18.79.XT926.Verizon.en.US
Android version 4.1.2
Build 9.8.1Q-79
Boot Mode 10.9B
AP Fastboot flash (device is locked status code 0
So about 6 months ago i tried to root and unlock phone, i rooted fine but messed up on the unlock. And the phone was stuck in boot loop. anyways i was able with help from here on XDA get it out of boot loop and working. My issue is a couple things.
1. Can it be unlocked (i have read and read and dont believe its possible)
2. It wont do a factory hard reset it errors out and just reboots.
3. I try to do the OTA and it just get the android guy with the red triangle and then reboots.
4. when i hold volume up and power and get the factory reset, normal boot etc options, any i select just reboot phone.
I would like to do 1 of the following things. and would prefer 1.:
1. if possible unlock and install custom rom.
2. Do the OTA update and have a fresh install
3. Do a factory wipe and sell phone.
Please any help would be great, as the phone has gotten super slow and i usualy like to do a factory reset every 4-5 months to wipe it.
thanks
#1= not possible on your build. you can only install safestrap roms which are limited and most commonly found over on razr forum.
to clean it up and go back to stock you could either, use rsd to reflash stock, or grab the one click utility from the dev forum to do the same. the one click utility is the easiest of the 2, just be sure to get the build that matches your system version or newer. you can flash the same version or newer only, trying to flash an older version will just result in a boot loop.
bweN diorD said:
#1= not possible on your build. you can only install safestrap roms which are limited and most commonly found over on razr forum.
to clean it up and go back to stock you could either, use rsd to reflash stock, or grab the one click utility from the dev forum to do the same. the one click utility is the easiest of the 2, just be sure to get the build that matches your system version or newer. you can flash the same version or newer only, trying to flash an older version will just result in a boot loop.
Click to expand...
Click to collapse
Are you talking about DROID RAZR HD Utility 1.21 - Windows/Mac/Linux
soloblazer said:
Are you talking about DROID RAZR HD Utility 1.21 - Windows/Mac/Linux
Click to expand...
Click to collapse
for your build you would need version 1.33 found here http://forum.xda-developers.com/showpost.php?p=46269380&postcount=1
1.21 would bootloop because of the locked bootloader.
bweN diorD said:
for your build you would need version 1.33 found here http://forum.xda-developers.com/showpost.php?p=46269380&postcount=1
1.21 would bootloop because of the locked bootloader.
Click to expand...
Click to collapse
Ok, i will give it a shot in the morning after full battery charge, i will let you know,,
thanks for your help.
bweN diorD said:
for your build you would need version 1.33 found here http://forum.xda-developers.com/showpost.php?p=46269380&postcount=1
1.21 would bootloop because of the locked bootloader.
Click to expand...
Click to collapse
Everything went smooth with the #1 option and doing a factory reset etc.
thanks for your help.
soloblazer said:
Everything went smooth with the #1 option and doing a factory reset etc.
thanks for your help.
Click to expand...
Click to collapse
happy to help, glad you got it fixed.
Hi, I have a question.
I had a hard time getting any of the utilities to work initially. Booting up was just scrambled and broken. Anyway, I used v1.34 and it's made progress. It worked it's way through writing system and such. Now the phone is stuck on a bootloop. The phone cannot make it passed the red M before rebooting.
When the phone is plugged in and on an inescapable bootloop, is it charging? My battery was hovering above empty before the v1.34 utility brought me here.
soloblazer said:
Everything went smooth with the #1 option and doing a factory reset etc.
thanks for your help.
Click to expand...
Click to collapse
So now that the OTA for kitkat is out, i tried to do it and it fails now. what do you suggest to get the newest OTA with kitkat?
thanks
soloblazer said:
So now that the OTA for kitkat is out, i tried to do it and it fails now. what do you suggest to get the newest OTA with kitkat?
thanks
Click to expand...
Click to collapse
Are you rooted? If so, that is why.
Did you freeze or remove any apps? If so, that's another reason why.
In either case, you will have to FXZ back to stock, unrooted to take the OTA. However, you WILL lose root and there is no root exploit for Kit Kat unless you have an unlocked bootloader, which you already found out you can't have based on the version your phone was at (9.18.X). And, there is NO way to carry root over the OTA. Voodoo doesn't work with Kit Kat at all, and there is just no other way to keep root on locked bootloaders, period.
So, either hold off on the Kit Kat update and pray someone finds a way to root it for locked bootloaders, or else if you can't wait, then realize you may never see root on this phone again.
iBolski said:
Are you rooted? If so, that is why.
Did you freeze or remove any apps? If so, that's another reason why.
In either case, you will have to FXZ back to stock, unrooted to take the OTA. However, you WILL lose root and there is no root exploit for Kit Kat unless you have an unlocked bootloader, which you already found out you can't have based on the version your phone was at (9.18.X). And, there is NO way to carry root over the OTA. Voodoo doesn't work with Kit Kat at all, and there is just no other way to keep root on locked bootloaders, period.
So, either hold off on the Kit Kat update and pray someone finds a way to root it for locked bootloaders, or else if you can't wait, then realize you may never see root on this phone again.
Click to expand...
Click to collapse
I am the one that started this thread, and i used DROID RAZR HD Utility to get my phone updated via the last update. i have not frooze or removed any of the stock apps. and i dont think i am still rooted. I dont care about having root anymore, so just would like to flash the newest OTA>
iBolski said:
Are you rooted? If so, that is why.
Did you freeze or remove any apps? If so, that's another reason why.
In either case, you will have to FXZ back to stock, unrooted to take the OTA. However, you WILL lose root and there is no root exploit for Kit Kat unless you have an unlocked bootloader, which you already found out you can't have based on the version your phone was at (9.18.X). And, there is NO way to carry root over the OTA. Voodoo doesn't work with Kit Kat at all, and there is just no other way to keep root on locked bootloaders, period.
So, either hold off on the Kit Kat update and pray someone finds a way to root it for locked bootloaders, or else if you can't wait, then realize you may never see root on this phone again.
Click to expand...
Click to collapse
I am the one that started this thread, and i used DROID RAZR HD Utility to get my phone updated via the last update. i have not frooze or removed any of the stock apps. and i dont think i am still rooted. I dont care about having root anymore, so just would like to flash the newest OTA>
soloblazer said:
I am the one that started this thread, and i used DROID RAZR HD Utility to get my phone updated via the last update. i have not frooze or removed any of the stock apps. and i dont think i am still rooted. I dont care about having root anymore, so just would like to flash the newest OTA>
Click to expand...
Click to collapse
My bad for not realizing that.
Are you still getting the dead Andy screen after applying the OTA? If so, then you need to go back into the recovery as you did before and then apply the OTA again. This is a two-step process, especially if you applied the OTA manually rather than taking it automatically.
It's still waiting to continue the update for the OTA. So, go back into recovery and navigate to where you stored the OTA zip file on your external SD card and then apply it again and you should be good to go.
iBolski said:
My bad for not realizing that.
Are you still getting the dead Andy screen after applying the OTA? If so, then you need to go back into the recovery as you did before and then apply the OTA again. This is a two-step process, especially if you applied the OTA manually rather than taking it automatically.
It's still waiting to continue the update for the OTA. So, go back into recovery and navigate to where you stored the OTA zip file on your external SD card and then apply it again and you should be good to go.
Click to expand...
Click to collapse
So just to be clear.
I go to settings/aboutphone/system update. It says checking for update. Update Available/ then i hit download, it downloads it. I click install now. Phone reboots and i see the android man, status bar starts going and gets about 1/3 the way and then get the red triangle in the stomach of the android man. and then phone reboots.
soloblazer said:
So just to be clear.
I go to settings/aboutphone/system update. It says checking for update. Update Available/ then i hit download, it downloads it. I click install now. Phone reboots and i see the android man, status bar starts going and gets about 1/3 the way and then get the red triangle in the stomach of the android man. and then phone reboots.
Click to expand...
Click to collapse
At that point when it reboots, it should continue on and you should see the android picture again as it continues on installing. This is the second stage of the install and can take up to 15 minutes to complete.
Are you saying it just keeps rebooting at that point and never completes? If so, then you need to go here and follow SamuriHL's directions to the letter to get you up and running -> http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
iBolski said:
At that point when it reboots, it should continue on and you should see the android picture again as it continues on installing. This is the second stage of the install and can take up to 15 minutes to complete.
Are you saying it just keeps rebooting at that point and never completes? If so, then you need to go here and follow SamuriHL's directions to the letter to get you up and running -> http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
Click to expand...
Click to collapse
No after the android guy with the red triangle, it just does a complete reboot back into android. and then says update failed.
soloblazer said:
No after the android guy with the red triangle, it just does a complete reboot back into android. and then says update failed.
Click to expand...
Click to collapse
Were you rooted at any point in time? If so, did you flash back to stock? Just uninstalling root will not work.
Your phone must be completely stock with no evidence of it being modified in order for the OTA to work. Rooting is one thing that will modify it to where an OTA will not take.
I had explained earlier that if you rooted and/or froze/removed any system/stock apps, you must use an FXZ image to put your phone back to stock. The link I supplied you with in that previous post will give you a stock Kit Kat image to flash to your phone. That is what you must do.
soloblazer said:
So now that the OTA for kitkat is out, i tried to do it and it fails now. what do you suggest to get the newest OTA with kitkat?
thanks
Click to expand...
Click to collapse
the razr utility has been updated since you started this thread, to KK.
just go back to the utility post from before, and you will see the new KK version at the bottom.
use it the same way you used the old one and you will be on stock KK. its the same as taking the ota update.
Hi there:
I've been following this thread, as I'm in a similar situation. I'm pretty sure I'm stuck with either rooted JB or unrooted KK, but just wanted to confirm.
Here's what I have:
-Phone: Razr HD
-System version: 9.18.94.XT926 (VZW US)
-Android: 4.1.2
-Rooted
-Locked bootloader
I'd love some clarifications/confirmations on the following, if anyone has them:
-There is no way to downgrade the system version to an unlockable version (like 9.16). Not even with flashing back to stock everything with the Droid Razr HD Utility.
-There is currently no way to root KK without an unlocked bootloader.
-If I unroot (flash back to stock) and upgrade, I will lose root and likely not get it back.
-The only way for me to currently keep root is to stay on JB.
I'm not interested in custom ROMs, just root.
Thanks in advance.
phraxen said:
Hi there:
I've been following this thread, as I'm in a similar situation. I'm pretty sure I'm stuck with either rooted JB or unrooted KK, but just wanted to confirm.
Here's what I have:
-Phone: Razr HD
-System version: 9.18.94.XT926 (VZW US)
-Android: 4.1.2
-Rooted
-Locked bootloader
I'd love some clarifications/confirmations on the following, if anyone has them:
-There is no way to downgrade the system version to an unlockable version (like 9.16). Not even with flashing back to stock everything with the Droid Razr HD Utility.
-There is currently no way to root KK without an unlocked bootloader.
-If I unroot (flash back to stock) and upgrade, I will lose root and likely not get it back.
-The only way for me to currently keep root is to stay on JB.
I'm not interested in custom ROMs, just root.
Thanks in advance.
Click to expand...
Click to collapse
-no, cant be done
-correct
-correct
-correct
So i got the notif to update to the latest OTA today and when i tried to i got an error....
i checked superSU and it said that my phone was no longer rooted... and now when i try to do over the rooting process, i.e unlock the bootloader and root... its not working, im using the oneplus one toolbox version 3, i had originally used 2....
when i click unlock bootloader, all the phone does is reboot... which is strange seeing as i know it basicall factory resets the phone after unlocking... anyone have this problem? need help
If you were rooted before, you don't need to re-unlock your bootloader as its already unlocked.
Just go into recovery and flash SuperSU.
Stop using toolkits. Its pretty obvious that you aren't aware of what you're doing and you're just pressing buttons hoping stuff will work.
zephiK said:
If you were rooted before, you don't need to re-unlock your bootloader as its already unlocked.
Just go into recovery and flash SuperSU.
Stop using toolkits. Its pretty obvious that you aren't aware of what you're doing and you're just pressing buttons hoping stuff will work.
Click to expand...
Click to collapse
um, no, you couldnt be farther from the truth.. as i have rooted devices already manually.
Also, please disregard this post, i switched the usb port i was using and everything is working now, my front port is faulty...apparently.
JohanXDash said:
um, no, you couldnt be farther from the truth.. as i have rooted devices already manually.
Also, please disregard this post, i switched the usb port i was using and everything is working now, my front port is faulty...apparently.
Click to expand...
Click to collapse
If you were already previously rooted, your phone doesn't magically relock its bootloader. The only way for that to happen is if you manually relocked the bootloader which is bad practice if you're relocking your bootloader when its already unlocked. It serves no purpose to relock your bootloader if you did relock it, just leave it unlocked.
You don't have to go through the whole rooting process if your bootloader was already unlocked. All you had to do was flash SuperSU in recovery to reobtain root.
And don't use toolkits, you honestly don't learn anything at all but to click a button and hope it works. Because there is a chance that it will not work and then consequences will be set in place and then you'll have to rely on users who manually input commands on their phone via fastboot because you're not sure how to do it.