Related
I got the 2.3.5 Update OTA on my One-click-root Nexus and applied the update, but now I'm stuck on the android/exclamation point screen.
What do I do??
gnuf99 said:
I got the 2.3.5 Update OTA on my One-click-root Nexus and applied the update, but now I'm stuck on the android/exclamation point screen.
What do I do??
Click to expand...
Click to collapse
That's the stock recovery - hold power and hit vol up to get the menu.
I've been doing that, but nothing happens.
I did a battery pull, and it rebooted in 2.3.4
So what am I doing wrong? Do I need to change something before trying the update again?
Hold power and slide from volume down to volume up. But that wont do u any good you need to flash a custom recovery and reflash super user.
Sent from my Nexus S 4G using Tapatalk
So I goofed something up on my phone?
Is there a way to do this without losing all my app info/game saves?
I was going to run a TItanium backup.
And sorry, I'm a total noob with this.
ROM Manager, would I flash an older ROM or the ClockworkMod Recovery?
At that point could i just install the update and re root with Shabby Penguin's one click and then get all my app data back from Titanium backup?
gnuf99 said:
So I goofed something up on my phone?
Is there a way to do this without losing all my app info/game saves?
I was going to run a TItanium backup.
And sorry, I'm a total noob with this.
ROM Manager, would I flash an older ROM or the ClockworkMod Recovery?
At that point could i just install the update and re root with Shabby Penguin's one click and then get all my app data back from Titanium backup?
Click to expand...
Click to collapse
Nothing is goofed up if you rebooted into 2.3.4.
The update did not apply. Did you receive the OTA or download it manually?
If you are unlocked just flash CWM via fastboot and apply it from there.
If you are locked then you can go back into the stock recovery, hold power down and hit vol up (in that order) to get the menu and apply the update. You may want to ensure it is in the root of the sdcard and named update.zip.
The OTA does not wipe nor is a wipe necessary, so you shouldn't be losing any data/apps.
I got the update OTA, but not it's not asking me if I want to apply it.
I'm sorry I'm such a noob here, but step wise.
If I boot up with Vol UP, I can then go to Recovery and get to ClockWork Recovery.
From there do I just hit update from SD card?
gnuf99 said:
I got the update OTA, but not it's not asking me if I want to apply it.
I'm sorry I'm such a noob here, but step wise.
If I boot up with Vol UP, I can then go to Recovery and get to ClockWork Recovery.
From there do I just hit update from SD card?
Click to expand...
Click to collapse
Yeah, choose apply update. Choose your zip from the SD card and apply.
It will go through a series of asserts and then apply if it passes. If you've modified any of the checked system files, boot image or kernel it's likely going to fail.
Well, I didn't alter any of them on purpose
I used Shabby Penguin's one click root so I could use Titanium Backup only. (Although now I'll probably add tethering to the list) So I don't think I changed any kernel files.
It's saying it can't find the file. Whatever downloaded must have gotten deleted somehow. I may just download the update and do it myself like everyone else.
Just to clarify. I place the update.zip in the root and select apply update on the ClockWorkMod Recovery, and that's it?
I was waiting to just get the update OTA organically hoping it would avoid these problems, lol.
gnuf99 said:
Well, I didn't alter any of them on purpose
I used Shabby Penguin's one click root so I could use Titanium Backup only. (Although now I'll probably add tethering to the list) So I don't think I changed any kernel files.
It's saying it can't find the file. Whatever downloaded must have gotten deleted somehow. I may just download the update and do it myself like everyone else.
Just to clarify. I place the update.zip in the root and select apply update on the ClockWorkMod Recovery, and that's it?
I was waiting to just get the update OTA organically hoping it would avoid these problems, lol.
Click to expand...
Click to collapse
In CWM use the choose zip file from SD card option, then you can pick the file regardless of it's name.
That's it - if you are stock (other than rooting) it should apply without any issues.
You may need to reflash CWM and delete /etc/install-recovery.sh to keep CWM installed. I haven't looked at the update itself to see if it is installing the script to reflash the stock recovery.
I had this problem too. I rebooted and its back to 2.3.4. I will attempt to go to 2.3.5 today once I have more time and post my findings here. If anyone has any success please keep updating this thread.
It looks like I have to reflash CWM in order to restore Super User.
My bootloader is still unlocked, but it won't let me run/install CWM. How do I do this?
Jagar, I did finally figure this out after reading through the code in the rooting .bat that Shabby Penguin put together.
basically his file has the Clockwork Recovery image that you need.
Boot up in bootloader.
then type
fastboot flash recovery ______.img whatever image you have.
Then select RECOVERY on the bootloader menu and now you can install the superuser.zip file to re-root.
you might wanna just run the new one click again, make sure its version 2.0.. it will do teh dirty work for ya
Seriously Shabby, big props to you for automating that process. I learned much more from your code than reading through all those other posts
@gnuf99 although you succeeded in getting root , please do read the guides abt adb and fastboot. This will be always handy for you, indifferent of the device you'll use later.
Sent from my Transformer TF101 using Tapatalk
this forum is here to help people and spread knowledge, not so we can talk down to those less experienced then us. everyone starts somewhere...
removed. unnecessary comment by me .
shabbypenguin said:
you might wanna just run the new one click again, make sure its version 2.0.. it will do teh dirty work for ya
Click to expand...
Click to collapse
*REMOVED* Looking on another thread.
Hey all,
I rooted my HOX (1.73, 4.0.3) with the kpenn ne-Click a few days after I got it for the Tether and to de-bloat. Since then I haven't read anything on the One X till I heard Jelly Bean coming along. Anyhoo my question is what the upside of getting the new OTA (4.0.4) would be and how I would go about it if I wanted to (I've never updated before and ATT has stopped asking me to update, also I get nothing when I try to check for an update).
I've been reading around and it seems like most people are on to 1.85 and are flashing 4.1/2.2. My primary uses of my phone are for the media applications/web browsing and I haven't noticed any real drop in performance but I have heard the new updates have sped up the HOX considerably which is something I'm always interested in.
Thanks!
DON'T flash any OTA you will lose your root and will lose your ability to re root because there is no boot loader unlock for the new base. If you want to update and flash a new ROM and want to stick to sense, look at clean rom or xi40. Both are updated on the new base and are heaps and bounds better than the original ATT software :thumbup:
Shaddy-Z. said:
DON'T flash any OTA you will lose your root and will lose your ability to re root because there is no boot loader unlock for the new base. If you want to update and flash a new ROM and want to stick to sense, look at clean rom or xi40. Both are updated on the new base and are heaps and bounds better than the original ATT software :thumbup:
Click to expand...
Click to collapse
i one-clicked unrooted my phone earlier and freaked out (and the new updates didn't work out on my phone anyway). i ended up getting kpenn's one click again and putting SU back into my phone. Do you have any links that can take me on a step by step process of unlocking my phone and flashing those roms on it? I just love being able to control my phone and pushing it to its absolute limits.
Sigh. I followed the tutorial but I made a few mistakes...
1) I unlocked my phone way earlier than I should have so I wiped everything before I could make a back-up..
2) Re-locked accordingly to see if I could keep updating. I did manage to get to 1.85 like the tutorial said but.....
3) Since I didn't have a custom recovery I wasn't sure how to proceed. I couldn't get the root to flash so I tried using the 1-click 1.85 root since my phone was running 1.85.
....This ended up updating to 2.2 so now I have an unlocked HOX 2.2/4.0.4. With all the bloat.
Dumb dumb dumb. Ugh.
Pbdeng said:
Sigh. I followed the tutorial but I made a few mistakes...
1) I unlocked my phone way earlier than I should have so I wiped everything before I could make a back-up..
2) Re-locked accordingly to see if I could keep updating. I did manage to get to 1.85 like the tutorial said but.....
3) Since I didn't have a custom recovery I wasn't sure how to proceed. I couldn't get the root to flash so I tried using the 1-click 1.85 root since my phone was running 1.85.
....This ended up updating to 2.2 so now I have an unlocked HOX 2.2/4.0.4. With all the bloat.
Dumb dumb dumb. Ugh.
Click to expand...
Click to collapse
it's UNLOCKED?
you're lucky then.
just push a recovery like twrp then push root. Then you can debloat.
Yep, it's still unlocked. That was around the 4-7th reset I did (I messed up a lot). Do you have a link that shows me how to do that? I'm actually not as bummed about going to 2.2 since it runs so much faster than 1.73 did.
Pbdeng said:
Yep, it's still unlocked. That was around the 4-7th reset I did (I messed up a lot). Do you have a link that shows me how to do that? I'm actually not as bummed about going to 2.2 since it runs so much faster than 1.73 did.
Click to expand...
Click to collapse
make sure you have your unlock token and then go to http://www.htcdev.com/bootloader/unlock-instructions/page-4/
and follow the directions.
after that look at this thread to install twrp http://forum.xda-developers.com/showthread.php?t=1777773
then this one to re-root
http://forum.xda-developers.com/showthread.php?t=1673935
I notice one of the links is for 1.85. Does that mean that I'll go from 2.2 back to 1.85? I just wanted to make sure since my impression from the forums is that there is no 2.2 root yet unless it was flashed.
Pbdeng said:
I notice one of the links is for 1.85. Does that mean that I'll go from 2.2 back to 1.85? I just wanted to make sure since my impression from the forums is that there is no 2.2 root yet unless it was flashed.
Click to expand...
Click to collapse
no those pages just tell you how to manually install root and recovery.
your bootloader is still unlockable
unlock it
then install a recovery
then install root via that recovery
Ahh, thanks a bunch man.
Sorry if this is repetitive....
So I've checked my phone and currently it states that it is
"Re-locked"
I downloaded a recovery so it's currently on my phone. Furthermore I all ready had a copy of SU sitting in my phone's download folder.
Does this mean that I'm going to...
- Unlock bootloader (that is currently relocked) and have everything erased again.
- Reboot from recovery (of the evita 2.2.img I just downloaded with TWRP)
- Then flash the SU root I all ready have on my phone?
Pbdeng said:
Sorry if this is repetitive....
So I've checked my phone and currently it states that it is
"Re-locked"
I downloaded a recovery so it's currently on my phone. Furthermore I all ready had a copy of SU sitting in my phone's download folder.
Does this mean that I'm going to...
- Unlock bootloader (that is currently relocked) and have everything erased again.
- Reboot from recovery (of the evita 2.2.img I just downloaded with TWRP)
- Then flash the SU root I all ready have on my phone?
Click to expand...
Click to collapse
yeah unlock the boot loader. set up the phone again
then install the recovery then root.
to make your unlock stick, turn off fastboot in power options, then power down phone completely then restart it to the bootloader.
Hmm, so my phone is definitely unlocked now. I installed the recovery and I manually flashedthe new SuperSU in that link you posted for me. As far as I can tell nothing is happening.
Note: It says that it installs the recovery but there is no reboot that occurs. I've done this both with the android app and manually and nothing is happening.
I don't see SuperSU and rootchecker is confirming that my phone isn't rooted yet.
so you reboot to recovery, choose the superSU package to install then what happens?
I know this works I've done it quite a few times myself.
Presently I installed the latest img file with TWRP with the app. There is not reboot that occurs (unless I'm suppose to reboot on my own?). If that's the case then I've been a total idiot.
I've just been installing the openrecovery and then I press "Flash Roms" to flash the supersu. I get a little notification that says "Preparing to Flash" and then nada.
After you install twrp recovery you reboot. Then you boot to recovery and flash the super su zip manually
Wooh! I got it to work! Thank you so much!
Pbdeng said:
Wooh! I got it to work! Thank you so much!
Click to expand...
Click to collapse
No problemmo.
Does this also mean that I can flash any ROMs I want on my phone now?
Yes. But you will have to flash kernels aka boot.img separately using fast boot.
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.
Hi,
I have this AT&T one x, (I m using on NON AT&T network), so cant have an ota update.
Looking at few forums, downloaded the OTA version on XDA (631 Mb)
Saw people writing, that just rename the file to update.zip and then go to recovery and choose install from internal memory.
That dint work for me.
Error: not able to mount sd mem
Then few people wrote to choose install from external mem.
That dint work either.
Error: not able to mount sd mem
Then saw few people saying that I need to root my device and unlock bootloader.
I dint that, and tried from bootlaoder to install from zip.
That also dint work.
Now saw, I few wrote that i need to be S - OFF.
Which I tried doing it, but i m not able to do s-off for myself.
Pls pls pls.... can any of you EXPERTs out here help me.
Waited like for AT&T to release the update, now when it is out, i m not able to make it through.
Your step by step instruction would be highly appreciable.
Be aware, that if you have the AT&T version, and you are rooted, then you probably have SuperCID (in fact, you must have SuperCID, unless it was already changed back). If you have SuperCID you must S-off (or return to the AT&T CID) before applying the OTA, or you will brick your phone!
I am not all that familiar with the process to install using OTA.zip (and haven't done it myself), but it was discussed in these threads:
http://forum.xda-developers.com/showthread.php?t=2180408
forum.xda-developers.com/showthread.php?t=1701460
redpoint73 said:
Be aware, that if you have the AT&T version, and you are rooted, then you probably have SuperCID (in fact, you must have SuperCID, unless it was already changed back). If you have SuperCID you must S-off (or return to the AT&T CID) before applying the OTA, or you will brick your phone!
I am not all that familiar with the process to install using OTA.zip (and haven't done it myself), but it was discussed in these threads:
http://forum.xda-developers.com/showthread.php?t=2180408
forum.xda-developers.com/showthread.php?t=1701460
Click to expand...
Click to collapse
How to S Off ATT HOX???
Thats the big question.
I have rooted my phone through one click TWRP Toolkit.
abhishek jain said:
How to S Off ATT HOX???
Thats the big question.
Click to expand...
Click to collapse
No, that is a very small question. Or at least a very easy one to answer.
Take 5 minutes to look around before asking "big" questions: http://forum.xda-developers.com/showthread.php?t=1671237
http://forum.xda-developers.com/showthread.php?t=2136172
If you would read my first post, I have already posted that I tried doing that was not able to do.
On the third comment that we need push in , where it given an error 92 or something like that, I dint got that.
Tried many times and then it became a "big" for me.
We all are born not experts in every field.
So before comenting pls try to know what's behind it
Sent from my HTC One X using xda app-developers app
Lol it doesn't take an expert to read and take five mins..this is probably one if the easiest s off methods you'll see for awhile... You probably didn't set up your adb fastboot environment up right
a box of kittens said:
Lol it doesn't take an expert to read and take five mins..this is probably one if the easiest s off methods you'll see for awhile... You probably didn't set up your adb fastboot environment up right
Click to expand...
Click to collapse
Changed my laptop and tried again.
Now I am S-OFF
THough I applied the same comments on three different machine.
4th Time it worked.
Now how to install this OTA updated which I have downlaoded
abhishek jain said:
Changed my laptop and tried again.
Now I am S-OFF
THough I applied the same comments on three different machine.
4th Time it worked.
Now how to install this OTA updated which I have downlaoded
Click to expand...
Click to collapse
Anyone to help me out in this case:
I am S OFF
Rooted
Unlocked bootloader
AT&T HOX on non AT&T network
631 mb update.zip
Looking top update
Rename file update.zip and copy to internal storage.
Reboot to bootloader and enter recovery.
Push power+ vol up when recovery screen appears to enter recovery dialog.
Ignore errors.
Select install from internal storage
Select update.zip
Phone will reboot a couple of times.
iElvis said:
Rename file update.zip and copy to internal storage.
Reboot to bootloader and enter recovery.
Push power+ vol up when recovery screen appears to enter recovery dialog.
Ignore errors.
Select install from internal storage
Select update.zip
Phone will reboot a couple of times.
Click to expand...
Click to collapse
I tried this method couple of time before : unlocking, rooting and S-off ing
In this case , do i need to relock my bootloader and stock recovery?
If yes, where can i find stock recovery, i have deleted it.
By "i deleted it" do you mean you installed a custom recovery? If so, yes you need to get stock recovery back on.
Only way I know of to reinstall stock recovery is to run the 2.20 ruu. Since you're s-off, you don't need to relock; just run it.
iElvis said:
By "i deleted it" do you mean you installed a custom recovery? If so, yes you need to get stock recovery back on.
Only way I know of to reinstall stock recovery is to run the 2.20 ruu. Since you're s-off, you don't need to relock; just run it.
Click to expand...
Click to collapse
I am not a techie but as far as i know, i have not installed a custom recovery.
I did TWRP tool kit, rooting and unlocking bootloader.
How can see if i am custom recovery or stock
abhishek jain said:
I am not a techie but as far as i know, i have not installed a custom recovery.
I did TWRP tool kit, rooting and unlocking bootloader.
How can see if i am custom recovery or stock
Click to expand...
Click to collapse
You probably have a custom recovery. Reboot to bootloader and select recovery and see what you get. If it's TWRP, you'll get a teamwin splash screen and then some options. Stock recovery will just show a screen with a green circle.
iElvis said:
You probably have a custom recovery. Reboot to bootloader and select recovery and see what you get. If it's TWRP, you'll get a teamwin splash screen and then some options. Stock recovery will just show a screen with a green circle.
Click to expand...
Click to collapse
Then I have custome recovery.
Could you gimme a link for stock recovery image
I do not know if one is available. I have never seen one posted. Running a ruu will put it back on.
iElvis said:
I do not know if one is available. I have never seen one posted. Running a ruu will put it back on.
Click to expand...
Click to collapse
Yes now i have got my phone updated with the OTA update
abhishek jain said:
Yes now i have got my phone updated with the OTA update
Click to expand...
Click to collapse
Please click "Thanks" if anyone in the thread helped you.
iElvis said:
Please click "Thanks" if anyone in the thread helped you.
Click to expand...
Click to collapse
I have already done that.
And now in case anyone needs help, i can help those people out.
Coz the method is simple, but it is not at all explained clearly in any of the threads.
It has come in bit and pieces.
I have noticed one thing.
That after installing the update and again unlockin the bootloader and rooting, I am not able to see "TAMPERED" being written in the boatloader.
Also, now when I am rooted and also have SU permission, I m not able to switch on my WiFi tether with the files mentioned in the thread
http://forum.xda-developers.com/showthread.php?t=1677261
The "TAMPERED" flag goes away when you're s-off and flash a new hboot.
I believe wifi tether is blocked on the new AT&T base. You can flash a custom rom on the 3.17 base and it should work.
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.