Related
Hey I hate having to post this but im stumped. i was running cm7 nightly build 21 and wanted to flash back to stock pd15img. i followed the steps but when i went to update all it did was turn s on. now my mytouch gets to the animated MY logo and loops. i can still get to recovery and i have tried restore my backup but i still get the MY animated boot logo. any help or suggestions? thanks.
Did you revert your recovery back to stock or Clockwork 2.x instead of Clockwork 3.x that CM7 requires?
Genocaust said:
Did you revert your recovery back to stock or Clockwork 2.x instead of Clockwork 3.x that CM7 requires?
Click to expand...
Click to collapse
Yep. 2.5.1.2.. I even tried just flashing icedglacier but i still get the animated MYlogo wich continues to loop.
does the phone have to be rooted to fix this? It was prior to flashing the PD15IMG, but like i said when it was done loading the image i clicked update and it just turned s on....
okay so i just made some progress i think. i just flashed icedglacier again and this time it changed the boot logo to the icedglacier boot logo but it still loops.
on the bright side of things i was really tire of seeing the mytouch logo.
theycallmechase said:
Yep. 2.5.1.2.. I even tried just flashing icedglacier but i still get the animated MYlogo wich continues to loop.
does the phone have to be rooted to fix this? It was prior to flashing the PD15IMG, but like i said when it was done loading the image i clicked update and it just turned s on....
Click to expand...
Click to collapse
the PD15IMG is a HBoot flashed image. not via Clockwork's Recovery Manager.
What method did you follow to try and unroot your phone.
We kinda need to know what you did in order to fix it.
If you store the PD15IMG onto the root of the SD card and boot into bootloader it should automatically restore everything to a factory spec.
I unrooted my device by downloading the unroot folder and using visionary and the terminl emulator.
I didnt try to flash pd15img through clockworkmod i just put it on the root of my sd card and let the hboot do the rest once it loaded the image it gave me he update option i chose to update and when my phone came back on in hboot i saw s off and now im stuck in boot loop.
I have to get to work but if you think of anything that could help me out trhat would be awesome thanks guys for reading this in the first place
ps now if i try to load the pd15img it will load the image but there is no update opyion
theycallmechase said:
I unrooted my device by downloading the unroot folder and using visionary and the terminl emulator.
I didnt try to flash pd15img through clockworkmod i just put it on the root of my sd card and let the hboot do the rest once it loaded the image it gave me he update option i chose to update and when my phone came back on in hboot i saw s off and now im stuck in boot loop.
Click to expand...
Click to collapse
Try doing this. Esp. if you did the ./gfree deal.
http://forum.xda-developers.com/showthread.php?t=863899
I also made this mistake, I had to reflash a cm7 rom or miui, downgrade the recovery to 2.5.x (could also adb push) and from there went back to stock and rerooted and flashed ice glacier.
well im downloading sdk now. my internet is super slow.
theycallmechase said:
well im downloading sdk now. my internet is super slow.
Click to expand...
Click to collapse
you are just wanting the ADB you can download and install the drivers for just that. Takes like 5 mins to get up and running.
neidlinger said:
you are just wanting the ADB you can download and install the drivers for just that. Takes like 5 mins to get up and running.
Click to expand...
Click to collapse
cool drivers are installed. so do i just need to be hboot to use the drivers? or is there some sort a software i need?
theycallmechase said:
cool drivers are installed. so do i just need to be hboot to use the drivers? or is there some sort a software i need?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=928370&page=2
neidlinger said:
http://forum.xda-developers.com/showthread.php?t=928370&page=2
Click to expand...
Click to collapse
hahaha thanks bro, love the "(great for noobs)" in the title of the thread. will try as soon as possible.
after reading the guide i have one problem.
5. On your phone go to Settings/Applications/Development and make sure USB debugging is ON and plug it in via the usb..
any suggestions??
theycallmechase said:
hahaha thanks bro, love the "(great for noobs)" in the title of the thread. will try as soon as possible.
after reading the guide i have one problem.
5. On your phone go to Settings/Applications/Development and make sure USB debugging is ON and plug it in via the usb..
any suggestions??
Click to expand...
Click to collapse
Being that you have s=on it's going to be fairly difficult. [sidenote] i still cannot believe the PD15IMG didn't work for you [/sidenote]. but you can try and use the fastboot commands.If s=off you could load a separate recovery image and flash a ROM to get you up and running.
yeah, i knew this would happen to me. when i try to adb in it dosent show my device. i have a thing with best buy where they will mail it in to htc to have it fixed but im not sure since i modded the phone.
theycallmechase said:
yeah, i knew this would happen to me. when i try to adb in it dosent show my device. i have a thing with best buy where they will mail it in to htc to have it fixed but im not sure since i modded the phone.
Click to expand...
Click to collapse
since you are in fastboot you cannot use
adb devices
Click to expand...
Click to collapse
you have to use
.
fastboot devices
Click to expand...
Click to collapse
ok so adb devices gave me a list of devices wich was none.
fastboot devices did not do anything for me.
wait a minute.... it did show something a second time it says sh0bt602653 fastboot....
Ok, that means fastboot has detected your phone. You can flash individual system.img, recovery.img, etc directly from fastboot.
so what do i flash? what commands do i need to use.
C:\adb>fastboot -p sh0b7t602653 update update.zip
Whoops: didn't find expected signature
read_central_directory_entry failed
πmªeΩ▲K¡8|x¥►╬←ì☻²╣⌂ì╒▄╞)ⁿ‼♀÷ta in 'h↑τ‼
íTQ▬á╠4δ/l≤huä╘:ì{îC`╢r◄+m§┌╪é^EÇkm☺ªfR
⌠èc┘↕á(╚αñ-0←♫┌╗ê-UY#è°┌o◄■k┤▐╩_``╠FA∞9 ÄM°c↑Sl░LΩ¥♣⌠q╦è╬5è╖P»ìì_j↑û♦ß‼[Γ╞ö¶¡l∙K
╬@↓%$»}ÅKù⌡ΘP9♂₧▒≤☺■Wm3┴pß|*╩°φ`Dú╞▒m└√±←╓6↓A¬]W,ùa½↓εWX╗ôâ\?o\ö~y╚` ╨%█εç←╚q
¶╩♥&ò⌂M─)_5m8ù╢+'⌠y<BWδ¼
!╩X┘♫■s▐k╗wS";öPôBÇ1Yé↔è_ÿ∟╧♫â`↕á┘h▐]∟-╟;»5
▼Ç↨♥H·ò⌠ƒQ²'►╟Oç∙╗Y∟ì▲67╘%)▐∩╘kO¥▬Θî☼R∟┴¼'
hi all,
Firstly apologies if this is covered somewhere but for the life of me I cannot get to the bottom of this. I have spent 2 weeks on and off trying to get a solution but my Sensation is still boot looping.
The problem occurred when I turned on the camera but was faced with a blank screen. I could return to home screen but the camera would not work each time I launched. So I rebooted the device but then I was stuck in this boot loop.
Device info
HTC Sensation S-OFF RL
HBOOT-1.27.0000
RADIO-11.21.3504.13_2
I was running Insert Coin 2.3.5 ROM for some time without issue
I was hoping I could just do a superwipe and flash a new ROM
FAIL - each time I boot into CWM and select Recovery, it just goes back to bootloop.
I selected Factory Rest from CWM menu
FAIL - it just goes into bootloop
Also cannot use ADB as the device will not connect to the PC. Im using a card reader to put files on the SD card but have not being successful resolving the issue.
Tried an SD card from a stock Sensation, no difference. Booting with no SIM, not working.
Most Bootloop fix's seem to involve super wipes / flashing new ROMs but because my Recovery goes into the bootloop I dont have this option. I wish it was so easy.
Can anybody offer an other ideas.
Thanks for you patience, I am not much of a modder or Android expert. I had just flashed a ROM many months ago to help improve battery life and I was happy with that.
Have you tried re-installing your recovery throught the bootloader?
try different recovery (4EXT) or reinstall recovery again
thanks guys.
I found these flashable recovery files. Both CWM and 4EXT. I have tried both zips and ran the update in HBOOT but am still booting in CWM and if I select RECOVERY is goes too bootloop again.
http://forum.xda-developers.com/showpost.php?p=24345986&postcount=6
I think I might just give up and drop the phone into a phone repair shop and let them try it.
Did both flashes work? What do you mean you're "booting in CWM"? Can you boot into your system and are you using CWM app to boot into recovery, or are you manually booting into your bootloader and selecting recovery?
Sent from my HTC Sensation 4G with Beats Audio using Tapatalk 2
Try this pg58img (it helped me)http://www.wuala.com/LuckyThirteen/Elegancia/Official RUU Sensation/ it will update your sensation to ICS, (you will maintain s-off)
Thanks for that. It flashed fine and I was very hopeful it would work but unfortunately it is still in the boot loop. I feel like crying. Im stuck with an old iphone and I miss my HTC so much.
GROGG88 said:
Did both flashes work? What do you mean you're "booting in CWM"? Can you boot into your system and are you using CWM app to boot into recovery, or are you manually booting into your bootloader and selecting recovery?
Sent from my HTC Sensation 4G with Beats Audio using Tapatalk 2
Click to expand...
Click to collapse
Yes both flashes worked.
What I mean is, I am manually booting with volume down and power button. In the boot menu I select recovery and it enters boot loop.
markmcie said:
Thanks for that. It flashed fine and I was very hopeful it would work but unfortunately it is still in the boot loop. I feel like crying. Im stuck with an old iphone and I miss my HTC so much.
Click to expand...
Click to collapse
Can you please re-flash the stock ics (PG58IMG), look like you have some firmware issues (sometimes you have to flash several time in order to rectify previous mistakes...) Hope it helps, otherwise (in my humble opinion) you have some hardware problem
If you can boot normally into ICS and you are rooted, then get the 4Ext app or the ROM Manager app and flash the recovery through one of those.
dublinz said:
Can you please re-flash the stock ics (PG58IMG), look like you have some firmware issues (sometimes you have to flash several time in order to rectify previous mistakes...) Hope it helps, otherwise (in my humble opinion) you have some hardware problem
Click to expand...
Click to collapse
Ill do this a few times over the weekend and hopefully I can get up and running again. I will let you know how I get on.
Thanks
markmcie said:
Yes both flashes worked.
What I mean is, I am manually booting with volume down and power button. In the boot menu I select recovery and it enters boot loop.
Click to expand...
Click to collapse
Well I'd have to agree with dublinz then...
dublinz said:
Can you please re-flash the stock ics (PG58IMG), look like you have some firmware issues (sometimes you have to flash several time in order to rectify previous mistakes...) Hope it helps, otherwise (in my humble opinion) you have some hardware problem
Click to expand...
Click to collapse
so I gave this a go over the weekend and flashed maybe up to 10 times the ICS IMG.
Unfortunately it hasnt worked and Im left with my device looping.
so its off to the phone shop today and hopefully it can be fixed. Pity I rooted it and flashed the ROM as it should still be under warranty but I have voided that now
markmcie said:
so I gave this a go over the weekend and flashed maybe up to 10 times the ICS IMG.
Unfortunately it hasnt worked and Im left with my device looping.
so its off to the phone shop today and hopefully it can be fixed. Pity I rooted it and flashed the ROM as it should still be under warranty but I have voided that now
Click to expand...
Click to collapse
Flashing the ICS PG58IMG.zip doesn't replace the recovery.
Fix recovery first. Use stock recovery. When you get that working, change to "simple" cwm recovery.
thanks for the advise. It makes perfect sense as it appears it is my stock recovery that is broken.
however, I have searched around and cannot find a stock recovery image that I can flash as PG58IMG.zip.
Any help would be much appreciated.
markmcie said:
thanks for the advise. It makes perfect sense as it appears it is my stock recovery that is broken.
however, I have searched around and cannot find a stock recovery image that I can flash as PG58IMG.zip.
Any help would be much appreciated.
Click to expand...
Click to collapse
before flashing stock recovery...can you try this first
get this recovery image
and flash the recovery via fastboot
steps:
1.go to fastboot in your device and connect it to your pc (after this device should read fastboot usb)
2.get the adb/fastboot setup ready guide here
3.go to your adb folder and place the downloaded recovery.img there
4.type fastboot devices (it should show your device serial number)
5.now to flash type
fastboot flash recovery recovery.img
this should do...if it didnt work then let me know ASAP...then we'll think of other solutions
markmcie said:
thanks for the advise. It makes perfect sense as it appears it is my stock recovery that is broken.
however, I have searched around and cannot find a stock recovery image that I can flash as PG58IMG.zip.
Any help would be much appreciated.
Click to expand...
Click to collapse
EddyOS has them , search that. I'll try to locate them.
I remembered incorrectly, it was only CWM and 4EXt
http://forum.xda-developers.com/showpost.php?p=24345986&postcount=6
But you can find stock recovery in this forum:
http://www.htcsensationforum.com/ht...ota-update-on-rooted-phone/msg76452/#msg76452
scroll down a little bit ...
markmcie said:
thanks for the advise. It makes perfect sense as it appears it is my stock recovery that is broken.
however, I have searched around and cannot find a stock recovery image that I can flash as PG58IMG.zip.
Any help would be much appreciated.
Click to expand...
Click to collapse
Here you go:
http://db.tt/kvTvDblW
It should include all MID's and most CID's that I know of...
GROGG88 said:
Here you go:
http://db.tt/3YSslZVg
It should include all MID's and most CID's that I know of...
Click to expand...
Click to collapse
Link is doing a 404 ...
SanityPreservation said:
Link is doing a 404 ...
Click to expand...
Click to collapse
Fixed...
Ok so I downloaded the filefrom the other thread for my phone and moved it to my SDCARD like always I then reboot and pressed power and vol up key selected recovery, it then went to the android laying down with a ! in a red triangle, I changed the file name to update then tried update.zip then tried update.zip. and do all the same steps but then after a min with the red triangle it reboots itself normally like always, am I missing a step or something, I dont have root or anything....PLZ HELP ME myn is the Fido Nexus S
You can't apply this update with stock recovery. You need to use ClockworkMod Recovery. Read some of the other threads here for more info.
So i have to root my phone and everything if I understand, or I wait until it is pushed to my phone?
No. You just need unlock the bootloader and flash a custom recovery.
Hmuserfriendly said:
So i have to root my phone and everything if I understand, or I wait until it is pushed to my phone?
Click to expand...
Click to collapse
as he said. but be aware that unlocking (with fastboot) will wipe your phone clean !
Hmuserfriendly said:
So i have to root my phone and everything if I understand, or I wait until it is pushed to my phone?
Click to expand...
Click to collapse
Correct. It's either wait for the official push to arrive on your phone, or unlock and install CWM. If you're nervous about it, try something like the Nexus Root Toolkit, which does almost everything for you (unlock, root, CWM, etc). Link to toolkit is: http://www.wugfresh.com/dev/nexus-root-toolkit/
Thank you so much guys for your help
Hi All,
Problem with TF700 with JB, rooted but not unlocked. I cannot enter into stock recovery: after volDown - volUP I have dead droid with red triangle. I think this my mistake: after was rooted in ICS .26, not unlocked, I tryed to install GooManager - after that I cannot enter to recovery in ICS. After that JB OTA installation was no problem, i backup and restore root, but still not have recovery.
So, now I have root in JB and can you point me to answer, how I can return stock recovery without unlock?
Thank you!
--
Roman
rusm said:
Hi All,
Problem with TF700 with JB, rooted but not unlocked. I cannot enter into stock recovery: after volDown - volUP I have dead droid with red triangle. I think this my mistake: after was rooted in ICS .26, not unlocked, I tryed to install GooManager - after that I cannot enter to recovery in ICS. After that JB OTA installation was no problem, i backup and restore root, but still not have recovery.
So, now I have root in JB and can you point me to answer, how I can return stock recovery without unlock?
Thank you!
--
Roman[/QUOTE
Turn off you tab, hold vol down then hold power button, as soon as you see the white text appeared on screen, release power button, then vol down button, tell me what you see on the screen? (how many icons?)
Click to expand...
Click to collapse
buhohitr said:
rusm said:
Hi All,
Problem with TF700 with JB, rooted but not unlocked. I cannot enter into stock recovery: after volDown - volUP I have dead droid with red triangle. I think this my mistake: after was rooted in ICS .26, not unlocked, I tryed to install GooManager - after that I cannot enter to recovery in ICS. After that JB OTA installation was no problem, i backup and restore root, but still not have recovery.
So, now I have root in JB and can you point me to answer, how I can return stock recovery without unlock?
Thank you!
--
Roman[/QUOTE
Turn off you tab, hold vol down then hold power button, as soon as you see the white text appeared on screen, release power button, then vol down button, tell me what you see on the screen? (how many icons?)
Click to expand...
Click to collapse
I can see 4 icons: RCK, dont remember )), usb, and wipe. I try all icons exept wipe: red triangle.
Click to expand...
Click to collapse
rusm said:
buhohitr said:
I can see 4 icons: RCK, dont remember )), usb, and wipe. I try all icons exept wipe: red triangle.
Click to expand...
Click to collapse
That's great, so now what do you try to do?? if you don't have any update zip, it will give you the error, but if you have an update zip in there it will pickup and install. Your red triange is normal.
Click to expand...
Click to collapse
buhohitr said:
rusm said:
That's great, so now what do you try to do?? if you don't have any update zip, it will give you the error, but if you have an update zip in there it will pickup and install. Your red triange is normal.
Click to expand...
Click to collapse
I think it may be the future problem if recovery is broken, i think this red triangle indicate that may be I erase something important.
It is not right, you say this behavior is normal? So, if it is all OK now with device, I will have fun))
Thank you very much!!
--
Roman
Click to expand...
Click to collapse
same problem
buhohitr said:
rusm said:
That's great, so now what do you try to do?? if you don't have any update zip, it will give you the error, but if you have an update zip in there it will pickup and install. Your red triangle is normal.
Click to expand...
Click to collapse
This relates to same problem I have . See cannot open recovery in JB in this same QA forum a little further back. I get the icons and when I pick recovery I get to Red triangle Andy but then no matter what combo of buttons pushed nothing happens. In my thread I was given a solution but I am locked but rooted and I believe had to be unlocked to use it. My question is can you get to recovery with a locked rooted tab to wipe cache etc . I can no longer get to that menu.
Click to expand...
Click to collapse
rusm said:
I think it may be the future problem if recovery is broken, i think this red triangle indicate that may be I erase something important.
It is not right, you say this behavior is normal? So, if it is all OK now with device, I will have fun))
Thank you very much!!
--
Roman
Click to expand...
Click to collapse
Tomv5314 said:
This relates to same problem I have . See cannot open recovery in JB in this same QA forum a little further back. I get the icons and when I pick recovery I get to Red triangle Andy but then no matter what combo of buttons pushed nothing happens. In my thread I was given a solution but I am locked but rooted and I believe had to be unlocked to use it. My question is can you get to recovery with a locked rooted tab to wipe cache etc . I can no longer get to that menu.
Click to expand...
Click to collapse
I think what buhohitr was saying is that RCK is a recovery that you can only boot into when there is an update file waiting to be updated on the microSD card. Otherwise, it does nothing but give you that Android with the Red Triangle.
I can confirm this on JB, never tried it while still on ICS.
johnlgalt said:
I think what buhohitr was saying is that RCK is a recovery that you can only boot into when there is an update file waiting to be updated on the microSD card. Otherwise, it does nothing but give you that Android with the Red Triangle.
I can confirm this on JB, never tried it while still on ICS.
Click to expand...
Click to collapse
It seems that the only solution is to unlock and put a custom recovery on . Unfortunately for me I did not unlock for warranty reasons and I updated to .30 and JB OTA and now it seems I have painted myself into a corner since I did not do nvflash or unlock downloads before accepting .30 and JB OTA. It appears ICS stock recovery is gone. Thanks for responses in this and my other thread Tom
see "Cannot use recovery after JB" in QA section further back
Tomv5314 said:
It seems that the only solution is to unlock and put a custom recovery on . Unfortunately for me I did not unlock for warranty reasons and I updated to .30 and JB OTA and now it seems I have painted myself into a corner since I did not do nvflash or unlock downloads before accepting .30 and JB OTA. It appears ICS stock recovery is gone. Thanks for responses in this and my other thread Tom
see "Cannot use recovery after JB" in QA section further back
Click to expand...
Click to collapse
No, you're not corner, you can easily downgrade from JB to .30 (download full version from Asus site), root your device, install superSU then save root with Voodoo OTA root keeper, then upgrade to JB through OTA, restore root using Voodoo OTA root keeper and you all set.
buhohitr said:
No, you're not corner, you can easily downgrade from JB to .30 (download full version from Asus site), root your device, install superSU then save root with Voodoo OTA root keeper, then upgrade to JB through OTA, restore root using Voodoo OTA root keeper and you all set.
Click to expand...
Click to collapse
I am rooted but locked boot loader. and I did save root with voodoo and do have Super SU.
my problem was no recovery. I am trying to get my other thread merged with this one where the solution I was given appears to be unlock then load CWM custom recovery for JB
Tomv5314 said:
I am rooted but locked boot loader. and I did save root with voodoo and do have Super SU.
my problem was no recovery. I am trying to get my other thread merged with this one where the solution I was given appears to be unlock then load CWM custom recovery for JB
Click to expand...
Click to collapse
If you downgrade back to .30 with full package then upgrade to JB it will fixed the issue.
Yip. I did exactly that.
Sent from my rooted BIONIC running ICS 6.7.247 (!) via Tapatalk 2
buhohitr said:
If you downgrade back to .30 with full package then upgrade to JB it will fixed the issue.
Click to expand...
Click to collapse
OK now I get what you are saying. lol full package upgrade Thanks I am going to redo things the way you have said tomorrow. thanks for the help
i had the same problem i upgraded to jb without unlocking first, i was rooted but couldnt access or install a recovery. read a couple threads and found out that the asus unlock tool works on JB also although it states that its only for ICS on the description. anyways unlocked the tablet and used goo to install twrp and everything works just fine.
My Razr maxx hd (xt926) had been rooted and bootloader unlocked sitting on version 9.16.9 for a while. With KitKat available I downloaded the 9.18.49 rom file and reset the phone flashing it with the Blur_Version.9.30.1.XT926.Verizon.en.US rom and getting everything back to stock. At this point it shows build 9.8.1Q I loaded the KK rom on the SD card and tried to flash from stock recovery.
During verification it aborts, with an error
expects build fingerprint of xt926_verizon/vanquish:4.1.2/9.8.1q-94/56:user release-keys
this device has xt926_verizon/vanquish:4.1.2/9.8.1q-94-1/57:user/r
Any thoughts on how to deal with this?
try this posted by @zachariahpope http://crackflasher.com/blur_version-9-18-94-xt926-verizon-en-us-zip-motorola-droid-razr-hd-cdma-livinginkaos/
billycar11 said:
try this posted by @zachariahpope http://crackflasher.com/blur_versio...zip-motorola-droid-razr-hd-cdma-livinginkaos/
Click to expand...
Click to collapse
That's the file I was trying to flash
Sent from my DROID RAZR HD using Tapatalk
samabuelsamid said:
That's the file I was trying to flash
Sent from my DROID RAZR HD using Tapatalk
Click to expand...
Click to collapse
okay then sorry i was confused try this one.
https://drive.google.com/file/d/0B8pGrRdP0CpyckJnd2JoQklHSjQ/edit
posted by @Sabissimo
billycar11 said:
okay then sorry i was confused try this one.
https://drive.google.com/file/d/0B8pGrRdP0CpyckJnd2JoQklHSjQ/edit
posted by @Sabissimo
Click to expand...
Click to collapse
Bad news. I flashed that one from recovery and it put my phone into a boot loop
Time to start over from scratch
samabuelsamid said:
Bad news. I flashed that one from recovery and it put my phone into a boot loop
Time to start over from scratch
Click to expand...
Click to collapse
I was reading that it rewrites your recovery. Go back into your recovery (should be a new version) and try to I stall again.
Yeah you need to install 2 times.
Did it install the recovery?
billycar11 said:
Yeah you need to install 2 times.
Did it install the recovery?
Click to expand...
Click to collapse
I'll let you know later tonight. I had to reflash back to where I was so I'd have a working phone for my workday.
samabuelsamid said:
I'll let you know later tonight. I had to reflash back to where I was so I'd have a working phone for my workday.
Click to expand...
Click to collapse
Definitely, the reboot during the install back into recovery is what confused a lot of us who were part of the soak test and tried to apply it manually ourselves.
When you first go into recovery and install the OTA, it will reboot. At that point, it will boot back to the recovery screen. There, you must press volume up + power. That is different from the old vol up+ vol down.
Anyways, once you are back in the "hard to read" recovery (why did they reduce the brightness on the new recovery?), you need to go back and install the OTA again. This time it will continue on where it left off and apply the KK update to your system.
Profit!
You might want to go to my post here (
http://forum.xda-developers.com/showpost.php?p=52602576&postcount=1) and read some of the gotchas. Read them BEFORE you take the update so you don't bork your phone:
billycar11 said:
Yeah you need to install 2 times.
Did it install the recovery?
Click to expand...
Click to collapse
iBolski said:
Definitely, the reboot during the install back into recovery is what confused a lot of us who were part of the soak test and tried to apply it manually ourselves.
When you first go into recovery and install the OTA, it will reboot. At that point, it will boot back to the recovery screen. There, you must press volume up + power. That is different from the old vol up+ vol down.
Anyways, once you are back in the "hard to read" recovery (why did they reduce the brightness on the new recovery?), you need to go back and install the OTA again. This time it will continue on where it left off and apply the KK update to your system.
Profit!
You might want to go to my post here (
http://forum.xda-developers.com/showpost.php?p=52602576&postcount=1) and read some of the gotchas. Read them BEFORE you take the update so you don't bork your phone:
Click to expand...
Click to collapse
Thanks, I'll provide an update of how this works!
iBolski said:
Definitely, the reboot during the install back into recovery is what confused a lot of us who were part of the soak test and tried to apply it manually ourselves.
When you first go into recovery and install the OTA, it will reboot. At that point, it will boot back to the recovery screen. There, you must press volume up + power. That is different from the old vol up+ vol down.
Anyways, once you are back in the "hard to read" recovery (why did they reduce the brightness on the new recovery?), you need to go back and install the OTA again. This time it will continue on where it left off and apply the KK update to your system.
Profit!
You might want to go to my post here (
http://forum.xda-developers.com/showpost.php?p=52602576&postcount=1) and read some of the gotchas. Read them BEFORE you take the update so you don't bork your phone:
Click to expand...
Click to collapse
This all worked perfectly and I'm now rocking KitKat
iBolski said:
Definitely, the reboot during the install back into recovery is what confused a lot of us who were part of the soak test and tried to apply it manually ourselves.
When you first go into recovery and install the OTA, it will reboot. At that point, it will boot back to the recovery screen. There, you must press volume up + power. That is different from the old vol up+ vol down.
Anyways, once you are back in the "hard to read" recovery (why did they reduce the brightness on the new recovery?), you need to go back and install the OTA again. This time it will continue on where it left off and apply the KK update to your system.
Profit!
You might want to go to my post here (
http://forum.xda-developers.com/showpost.php?p=52602576&postcount=1) and read some of the gotchas. Read them BEFORE you take the update so you don't bork your phone:
Click to expand...
Click to collapse
One other question: My bootloader is unlocked, I'm trying to find the directions to root again under kitkat by manually sideloading. Anyone have a link?
samabuelsamid said:
One other question: My bootloader is unlocked, I'm trying to find the directions to root again under kitkat by manually sideloading. Anyone have a link?
Click to expand...
Click to collapse
All you need to do is flash CWM and then find a sideloadable SU package to sideload under CWM. That's it.
iBolski said:
All you need to do is flash CWM and then find a sideloadable SU package to sideload under CWM. That's it.
Click to expand...
Click to collapse
Thanks. Just a couple more questions before I do this to make sure I don't send my phone back into oblivion and have to start all over again. Is the CWM recovery specific to any particular version of Android, current one available for XT926 on clockworkmod.com download page is 6.0.4.4. Similarly, does SU need to be specific to this phone/KitKat rom?
I've rooted numerous phones before, always using a script like Razr Hd utility. This is my first attempt at manual root so I appreciate your patience
samabuelsamid said:
Thanks. Just a couple more questions before I do this to make sure I don't send my phone back into oblivion and have to start all over again. Is the CWM recovery specific to any particular version of Android, current one available for XT926 on clockworkmod.com download page is 6.0.4.4. Similarly, does SU need to be specific to this phone/KitKat rom?
I've rooted numerous phones before, always using a script like Razr Hd utility. This is my first attempt at manual root so I appreciate your patience
Click to expand...
Click to collapse
You need to download the new CWM for KK. xt926-KK-CWM-6048.img is the name. You can get it from here: http://forum.xda-developers.com/showpost.php?p=52564336&postcount=1
iBolski said:
You need to download the new CWM for KK. xt926-KK-CWM-6048.img is the name. You can get it from here: http://forum.xda-developers.com/showpost.php?p=52564336&postcount=1
Click to expand...
Click to collapse
good thing I asked first
Update: not rooted on KitKat!
samabuelsamid said:
My Razr maxx hd (xt926) had been rooted and bootloader unlocked sitting on version 9.16.9 for a while. With KitKat available I downloaded the 9.18.49 rom file and reset the phone flashing it with the Blur_Version.9.30.1.XT926.Verizon.en.US rom and getting everything back to stock. At this point it shows build 9.8.1Q I loaded the KK rom on the SD card and tried to flash from stock recovery.
During verification it aborts, with an error
expects build fingerprint of xt926_verizon/vanquish:4.1.2/9.8.1q-94/56:user release-keys
this device has xt926_verizon/vanquish:4.1.2/9.8.1q-94-1/57:user/r
Any thoughts on how to deal with this?
Click to expand...
Click to collapse
I have the same problem, but I'm getting the error message that expects your device. What was the image that you used? I have the vanquish:4.1.2/9.8
1Q-94/56:user.
samabuelsamid said:
good thing I asked first
Update: not rooted on KitKat!
Click to expand...
Click to collapse
Then you cannot use CWM and there is no safe strap for KK.
Also, root is now lost, but SamuriHL is working on a theory that might work. Unfortunately, it requires locked phones that have NOT taken the soak or OTA yet and we have to wait for the official KK FXZ image file before he can continue. If the phone has had the OTA or soak applied to it, then it can't be part of the test.
iBolski said:
Then you cannot use CWM and there is no safe strap for KK.
Also, root is now lost, but SamuriHL is working on a theory that might work. Unfortunately, it requires locked phones that have NOT taken the soak or OTA yet and we have to wait for the official KK FXZ image file before he can continue. If the phone has had the OTA or soak applied to it, then it can't be part of the test.
Click to expand...
Click to collapse
Sorry, that should have read NOW rooted. CWM worked fine as did Koush's superuser
samabuelsamid said:
Sorry, that should have read NOW rooted. CWM worked fine as did Koush's superuser
Click to expand...
Click to collapse
you know what, color me stupid.
I've been helping so many people that when I read "no root", I interpreted it as "locked bootloader".
My bad.