Database Info

[Q] Update Nexus S from 2.3.6 to 4.0.3 manually with a broken power button

Hello everyone
I own a Nexus s I9020 T-mobile. and I'm using it on Vodafone.
My power button stopped working a month back and I'm using widgetlocker lockscreen to unlock.
I did not receive the OTA for ICS last month and i would like to have it on my phone by doing the update manually.
Is there a way to do the update manually with a broken power button ?
Thanks

There is a clockwork recovery with touchscreen interface I can't remember where I saw it though. So you could use that to flash the ota. Or you could flash the boot and system images directly through adb if they have been posted somewhere. You will have to root your phone before you can use these methods
Sent from my Nexus S using Tapatalk

timhl7 said:
There is a clockwork recovery with touchscreen interface I can't remember where I saw it though. So you could use that to flash the ota. Or you could flash the boot and system images directly through adb if they have been posted somewhere. You will have to root your phone before you can use these methods
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
thanks .. but I think the touch based clockwork recovery is only avilable for Galaxy Nexus and more over I dont want to root my phone unless it is absolutely necessary .. because i'll have to re-install all my apps
is there any possible way to do it without rooting ?

The Clockwork Recovery you are looking for is named TWRP (latest is Version 2.0.0). Look at the offical site - http://teamw.in/project/twrp2 - choose your device (NS or NS4G) and install via adb
Good luck

Rallyharry said:
The Clockwork Recovery you are looking for is named TWRP (latest is Version 2.0.0). Look at the offical site - http://teamw.in/project/twrp2 - choose your device (NS or NS4G) and install via adb
Good luck
Click to expand...
Click to collapse
Thanks mate
should my device be rooted for this ?
and after installing clockwork recovery how do I flash the update.zip file via clockwork, any guide ?

I have a new posted guide which should be useful for you, but you have to have it rooted first.

mingkee said:
I have a new posted guide which should be useful for you, but you have to have it rooted first.
Click to expand...
Click to collapse
Thanks mingkee
will try it out .. just hope I don't brick my phone 'coz im going to root my phone for the first time
looks like you have gone back to CM7 from ICS
should I overlook ICS too, coz im pretty happy with GB right now.

You don't need to flash TWRP. In clockwork mod recovery back is back, menu is down, search is select, home is up.
Sent from my SNES

even to flash ClockworkMod or TWRP, first you will need to unlock the bootloader right ?
for this again the need for power button arises..

[Q] Bootlooping and cannot open recovery

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...

How to upgrade to new latest Asus firmware through custom recovery

Check the device firmware type by going to Setting - about tablet - built number
Download the right firmware pack for your device.
http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_Infinity_TF700T/#download
Now extract the zip file and you will have another zip file.
Rename that zip file as "EP201_768_SDUPDATE" and place it to an external sd card if you do not have a custom recovery. If you are rooted and unlocked plus you have a custom recovery you don't need to rename it you can place it in internal sd is well.
Now turn off your device. Hold power button including the volume down button and enter custom recovery. For stock recovery it should detect it automatically and will install. once in custom recovery clear your cache and install the file with the name above or whatever name you have. once installation is complete. reboot the system be patient and you have the latest update.
You can obtain root easily using this method.
Just download the DebugfsRoot_Generic_v2.3.zip file from here
http://forum.xda-developers.com/show....php?t=1706588
extract the content and run RootDebugfs, then follow the on screen instruction and you will have root.
Make sure you have USB debugging on.
To get custom recovery. Download goomanager from playstore and you can install TWRP recovery from the option list. which is Option - install OpenRecoveryScript.
I am not responsible if you mess up your device. do these at your own risk. Nonetheless these steps work perfectly for me.

Renaming is not needed.

lafester said:
Renaming is not needed.
Click to expand...
Click to collapse
Exactly thats for people without custom recovery

Isn't this already covered here? http://forum.xda-developers.com/showthread.php?t=1833212
Sent from my EVO using xda premium

rizanx said:
Exactly thats for people without custom recovery
Click to expand...
Click to collapse
does the update push the stock recovery as well?
and root is lost right?

Yes and yes.
Sent from my HTC One X using xda premium

odeccacccp said:
does the update push the stock recovery as well?
and root is lost right?
Click to expand...
Click to collapse
Yes you will lose root.
But you can obtain root easily using this method.
Just download the DebugfsRoot_Generic_v2.3.zip file from here
http://forum.xda-developers.com/showthread.php?t=1706588
extract the content and run RootDebugfs, then follow the on screen instruction and you will have root.
oh and make sure you have USB debugging on.

sorry for the mix up. yes you do lose recovery. Download goomanager from playstore and you can install TWRP recovery from the option list.

rizanx said:
Through custom recovery stock recovery is not pushed! you will still have custom recovery. You will only lose root.
Click to expand...
Click to collapse
Wrong, flashing an official rom will make you loose the custom recover too, you will have a clean stock rom once you do that. AND also this thread has nothing to share with the development forum.

Pretoriano80 said:
Wrong, flashing an official rom will make you loose the custom recover too, you will have a clean stock rom once you do that. AND also this thread has nothing to share with the development forum.
Click to expand...
Click to collapse
+1 You WILL lose custom recovery with this method. This has all been covered before...
Sent from my EVO using xda premium

Pretoriano80 said:
Wrong, flashing an official rom will make you loose the custom recover too, you will have a clean stock rom once you do that. AND also this thread has nothing to share with the development forum.
Click to expand...
Click to collapse
Thanks for clear up.

MysticMgcn said:
Isn't this already covered here? http://forum.xda-developers.com/showthread.php?t=1833212
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Where in there? Can;t find it?
1) If I am on a custom ROM can I flash the new update or I have to go back to STOCK first?
2) What's the big deal with loosing CWR and Root, it takes like 2 min to put it back, I mean there is another way to not loose it?
Thanks

I also have a question! Will this allow for OTA updates even if our bootloader is unlocked? And will we be able to flash the JB update from ASUS manually if not? Anyone know?

GRIM1337 said:
I also have a question! Will this allow for OTA updates even if our bootloader is unlocked? And will we be able to flash the JB update from ASUS manually if not? Anyone know?
Click to expand...
Click to collapse
No. when you unlocked it clearly stated no more ota updates for you.
Yes. of course you can flash manually just like any other rom.

odeccacccp said:
Where in there? Can;t find it?
1) If I am on a custom ROM can I flash the new update or I have to go back to STOCK first?
2) What's the big deal with loosing CWR and Root, it takes like 2 min to put it back, I mean there is another way to not loose it?
Thanks
Click to expand...
Click to collapse
You don't need to have stock rom. As long as you have the stock kernel your ok. You will of course lose custom recovery but its easy to download again as i have mentioned in my first post.
There is a lengthy way to do this. But why do that when it takes you literally 2 minute to root it with DebugfsRoot .
Hope it went well for you.

[Recovery] Stock HTC One

For Dev's reference
stock recovery here

Onepagebook said:
For Dev's reference
stock recovery here
Click to expand...
Click to collapse
Version: 0.89.997.1 CL144629 test-keys
ro.build.date=六 12月 29 01:11:35 CST 2012

ClockworkMod Recovery! Well whenever the phone gets released. I attempted to build a test version of CWM at http://forum.xda-developers.com/showthread.php?t=2173863
Fingers crossed that it works.
But I will probably need someone to give me these two items once they get a phone to correct the configs.
Post the file /proc/partitions
Post the file /proc/mounts
For the adb commands. "adb shell" then "cat /proc/partitions" and "cat /proc/mounts" Should work.
EDIT: Thank you to he_stheone64 for giving me what I need above. Now I can make a fully working recovery.

To get back on topic, here's the fstab extracted from the recovery
http://pastebin.com/tBzTE4GA

Hey guys.
Nice to see all of you to be getting the HTC One
But lets not turn this to a conversation thread please.
Thread cleaned.
Cheers

Pardon me, but is this the same stock recovery as the AT&T version?

robstunner said:
Pardon me, but is this the same stock recovery as the AT&T version?
Click to expand...
Click to collapse
I'm sure it's not.

mike1986. said:
I'm sure it's not.
Click to expand...
Click to collapse
Darn, accidentally flashed CWM Touch when I was just looking to unlock and root. Oh well, no biggie. Thanks for the quick reply!

mike1986. said:
I'm sure it's not.
Click to expand...
Click to collapse
Looking at this string, my guess it's stock recovery for the M7_U: ro.build.date=六 12月 29 01:11:35 CST 2012

can i use it to flash my htc one dev edition?? im on 1.29.1540.3

so?????????

eltoffer said:
can i use it to flash my htc one dev edition?? im on 1.29.1540.3
Click to expand...
Click to collapse
Why would you use this? Go read some guides and then flash either twrp or cwm.
Sent from my HTC One

ECEXCURSION said:
Why would you use this? Go read some guides and then flash either twrp or cwm.
Sent from my HTC One
Click to expand...
Click to collapse
just curious, to get updates

My device has T-Mobile UK firmware (1.28.61.7) and I will be looking to go back to stock soon to hopefully receive official 1.29 firmware update.
I need the appropriate recovery for my device but am not quite sure what that is. I have a nandroid but this was done in CWM after rooting.
Is the recovery of 1.29 different to 1.28 and do I need a T-Mobile specific recovery or is the generic recovery just the same?
If somebody could point me in the direction of the recovery I require it would be much appreciated.

Onepagebook said:
For Dev's reference
stock recovery here
Click to expand...
Click to collapse
Hi Bro, Do you have STOCK Recovery for ONE Developer Edition ??
Regards,

hi there,
is the recovery can be installed for HTC ONE M7 802W?

mahesh_9j said:
Hi Bro, Do you have STOCK Recovery for ONE Developer Edition ??
Regards,
Click to expand...
Click to collapse
recovery files are all the same

Onepagebook said:
recovery files are all the same
Click to expand...
Click to collapse
Are you 100% sure??
I am trying to return my 1.28.61.7 device to stock using a rooted nandroid which I made without any other modifications. After many trials and tribulations, I managed to unroot by removing SuperSU and binaries but, after installing 'stock' recovery my device still says relocked and tampered and will not boot into recovery.
I am, however, able to perform a full wipe from within android though.
I would really like complete clarity on this if anyone can help me as I need to get back to stock to get an official update when it appears as there are no stock nandroids available or any RUU's for my device.

bobsie41 said:
Are you 100% sure??
I am trying to return my 1.28.61.7 device to stock using a rooted nandroid which I made without any other modifications. After many trials and tribulations, I managed to unroot by removing SuperSU and binaries but, after installing 'stock' recovery my device still says relocked and tampered and will not boot into recovery.
I am, however, able to perform a full wipe from within android though.
I would really like complete clarity on this if anyone can help me as I need to get back to stock to get an official update when it appears as there are no stock nandroids available or any RUU's for my device.
Click to expand...
Click to collapse
no problem, here is the US dev edition stock recovery-signed
http://d-h.st/b5g
Tampered showed @ hboot is because you have "unlocked" before

So If I have clockwork mod touch recovery installed and I want to go back to stock recovery without loosing my app and data I can just flash this in cwm?
Sent from my HTC One using xda app-developers app

[Q] Trouble installing KitKat 9.18.94

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.