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 have a rooted, unlocked SG3 running stock ROM and as of a couple weeks ago, continue to get prompted to install the OTA update (VRAGL7 I believe). Unsurprisingly the install fails when I try to apply it.
My question is, do I have to restore in order to apply this update? And if so, is it possible to instead defer the update indefinitely (since I dont want to restore and there doesnt appear to be anything useful in this update according to their site).
Im also sure someone else must have asked this before, but after browsing the last few pages and searching, I couldnt find anything. Feel free to direct me to a previous response if I missed it.
Thanks in advance!
This has been covered numerous times, but, here you go. If you want to take the update, lock your bootloader, Odin back to stock, take the OTA update, reroot, unlock, etc.
If you don't want to do that, freeze SDM 1.0 with Titanium and the message will stop. One thing though, you will not be able to update OTA until you restore SDM. Which, you shouldn't be updating a rooted phone to begin with unless you want a world of problems.
Good luck!
Sent from my SCH-I535 using xda premium
So to be clear, absolutely no way to apply the update without going back to stock first, correct?
Sorry for posting up whats probably been asked 100 times, but really couldnt track it down with a search and browse of the last few pages.
Thanks again.
timofcourse said:
So to be clear, absolutely no way to apply the update without going back to stock first, correct?
Sorry for posting up whats probably been asked 100 times, but really couldnt track it down with a search and browse of the last few pages.
Thanks again.
Click to expand...
Click to collapse
I did not have to do all that...
I used Mobile Odin Pro to Pre-Inject Root into the OTA Update before flashing it, then I flashed the latest modem immediately after flashing the OTA update.
I didn't lose Root or Unlocked Bootloader status..
Best part of it was... I didn't need my PC to do any of it...
The following thread is the one you should read in detail..
http://forum.xda-developers.com/showthread.php?t=1887741
Perfect. Exactly what I was looking for.
Thanks again.
timofcourse said:
Perfect. Exactly what I was looking for.
Thanks again.
Click to expand...
Click to collapse
Glad to help..
tekrhino said:
I did not have to do all that...
I used Mobile Odin Pro to Pre-Inject Root into the OTA Update before flashing it, then I flashed the latest modem immediately after flashing the OTA update.
I didn't lose Root or Unlocked Bootloader status..
Best part of it was... I didn't need my PC to do any of it...
The following thread is the one you should read in detail..
http://forum.xda-developers.com/showthread.php?t=1887741
Click to expand...
Click to collapse
Make sure that you read it and pay attention very carefully. I tried to do the same exact thing and had problems. Had to Odin back to stock. I think my problem was that I was running a custom kernel. Anyway I got the unauthorized software message and could only get into stock recovery and download mode.
Guess I will read the thread myself and see where I screwed up at.
Sent from my SCH-I535 using xda premium
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
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
I just got the OTA update yesterday to 4.4.4 KitKat. I downloaded the "L" developer preview and was going to flash it on my phone. I rebooted into recovery only to find a droid with a red exclamation mark on it's head. I went into Titanium Backup and it said I didn't have root access.
I tried going onto GooManager and installing a recovery, and TWRP, all failed. I guess I'm going to have to use the CF-Auto Root kit again, but I have one question.
Is there any way to tell if my bootloader is still unlocked? Or will doing this wipe my entire phone out? I have a lot of stuff on here I cannot afford to lose, but also don't want to transfer nearly 30 gigs of stuff to a hard drive. D;
If it matters, when I turn my phone on, it shows a "lock key" and it's "unlocked". I cannot remember that ever being there until after I rooted and stuff when I got the phone. Does this mean my bootloader is still unlocked? Or will I need to unlock everything again.
I learned my lesson. Never again doing OTA update.
OTA removes root and flashes stock recovery. It does not relock your bootloader. The padlock signifies unlocked.
Sent from my Nexus 5 using Tapatalk
Ugh, thank you rootSU! ^.^ I'll use the Auto-Root tool and re-root the darn thing lol
snappycg1996 said:
Ugh, thank you rootSU! ^.^ I'll use the Auto-Root tool and re-root the darn thing lol
Click to expand...
Click to collapse
No. Fastboot flash recovery then root from recovery.
Sent from my Nexus 5 using Tapatalk
i guess you arent one for searching, as this has literally been answered hundreds of thousands of times.
you WILL lose root by updating an official rom, be it via ota or manual. the stock rom is NOT rooted, you can not assume that your root will carry over. it will also replace your custom recovery with the stock recovery. this has been known since the very first android update in 2008. do yourself a favor, search, read, educate yourself.
what you need to do is flash a custom recovery via fastboot, then flash the latest supersu in your newly flashed recovery. then reboot, thats it.
snappycg1996 said:
I just got the OTA update yesterday to 4.4.4 KitKat. I downloaded the "L" developer preview and was going to flash it on my phone.
<Snip>
I have a lot of stuff on here I cannot afford to lose, but also don't want to transfer nearly 30 gigs of stuff to a hard drive. D;
<Snip>
I learned my lesson. Never again doing OTA update.
Click to expand...
Click to collapse
I am just curious why you are flashing a Developer Preview that has not been tested, no threads as of right now from anyone who has flashed it and above all without backing up your stuff? We haven't broken down the preview yet to see what is in there, so if I, and this is just me here, were going to flash something that had high potential for "problems", I would back up or at the very least send all the important things up to the cloud.
OTA was not the problem/lesson to be learned here. I would suggest you read some of the inevitable threads that will pop up with all the answers that you are looking for.