Related
[GUIDE] Root & recovery WITHOUT oem unlock & wipe (2.3.2 & older, plus now 2.3)
UPDATE #2 - Fitchman has reported successful root and rom flash without unlocking the bootloader by using Ginger Break. Full details in this post: http://forum.xda-developers.com/showpost.php?p=13236136&postcount=135
UPDATE - IMPORTANT: This method does not work with Android 2.3.3. Search the forum or this post in this thread for a way to update to 2.3.3 and root without unlocking if you haven't updated yet.
Alternatively, use this method on 2.3.2 and lower, then use titanium to back up everything, store it on your laptop (along with all your sdcard's data), then do the oem unlock step first and then continue from there with the rest of the guide.
Not my original idea, but a consolidation of a discussion between inakipaz and shrivelfig and myself in another thread and being posted here for easier finding by future root-seekers.
Shrivelfig's tested the method to re-root a previously rooted pone with a re-locked bootloader, and inakipaz has done it on a phone that's never had the bootloader unlocked.
The advantage here is that those who chose not to root when they first got the phone won't lose any app data or sdcard data like the methods that have you unlock the bootloader do. The disadvantage is your bootloader remains locked, which may prevent you flashing certain things in the future.
edit: see ravidavi's posts below; he's shown you can even flash custom roms that are clockwork compatible while having a locked bootloader with this method.
Download these two files:
clockwork recovery v3.0.0.5 or clockwork recovery v3.0.0.5 mirror if above not working
su-2.3.6.1-ef-signed.zip
Koush's blog for the latest clockwork updates (find Nexus S in the list).
Also, if you don't already have the necessary android sdk and drivers on your computer, get them from here: http://developer.android.com/sdk/index.html and install them. Some Windows users report better luck just installing pdanet. There's a decent guide for Windows users on installing the sdk here.
Place the recovery file on your laptop where you can access it while using the sdk fastboot commands.
Place the su zip one in the top level folder of your sdcard.
Put your phone in fastboot mode (power off, then hold volume up and power key at the same time until the phone boots to a white screen).
Use fastboot to boot the phone into the clockwork recovery:
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
If you're not sure how to get fastboot working on your computer, follow the excellent instructions that Allgamer gives in this GUIDE, but don't do the oem unlock command!
Once in clockwork, flash the su file to the phone by following these steps below.
To navigate in the clockwork recovery, you use the volume keys to scroll up/down through the menus, and the on/off button to select what's highlighted.
(note: some report success without these first 3 steps, others don't get a succesful root without, I recommend doing them)
select mounts and storage.
select mount /system
select go back
select install ZIP from sdcard
select choose zip from sdcard
select su-version#-signed.zip file you downloaded earlier
select yes - install su-version#-signed.zip
confirm it says "Install from sdcard complete"
select go back
select reboot
After the phone reboots, you should be rooted, with a locked bootloader, and none of your data erased.
That said, never hurts to have a backup of your precious data on the sdcard that you can copy over to the computer.
This method doesn't install busybox, so go to the Market and download/install busybox directly, or get Titanium Backup and check it's "problems?" button and let it install busybox for you. There's also an app called root checker that supposedly verifies you have a working root on your phone.
Once you have a successful root installed, I'd suggest getting back into clockwork recovery and running a nandroid back up from clockwork's backs and restore menu. Then copy that file from your sdcard (in the /clockwork/backups folder) to your laptop for safe-keeping and an easy full system restore to a known working config.
Usual disclaimers about I'm not responsible for damage to your phone or loss of data apply. Use any rooting method at your own risk.
Thanks and all the real credit go to inakipaz, shrivelfig and allgamer, and of course to koush, and ChainsDD for the superuser apk.
Worked perfectly. I used fastboot from my Mac (outlined in the stickied Mac Root thread). Root checker verifies that I have root.
And by the way, my phone and I are both root/ROM cherry. First android phone, first time rooter. Will work up the guts to flash a ROM soon, but of course there's no chance of doing THAT without unlocking the bootloader.
Thanks to all involved in this!
yeah! good work!
Srsly. Awsom.
Someone sticky this....
Question: When you do the fastboot boot command, does that overwrite the stock recovery with Clockwork? Or is it just booting into the recovery img without actually flashing it?
I would think this method also gives you a way to back up before unlocking the bootloader.
1) fastboot boot into Clockwork as described here
2) Full nandroid backup from Clockwork
3) Mount "SD" from Clockwork over USB, copy everything to computer (since it wipes everything)
4) Go back and unlock the bootloader as usual, resulting in a full wipe
5) Flash Clockwork Recovery again through whichever method
6) Mount "SD" from Clockwork over USB, copy the backup back to phone
7) Restore nandroid
And now you've unlocked the bootloader without amnesia =)
ravidavi said:
And by the way, my phone and I are both root/ROM cherry. First android phone, first time rooter. Will work up the guts to flash a ROM soon, but of course there's no chance of doing THAT without unlocking the bootloader.
Thanks to all involved in this!
Click to expand...
Click to collapse
Are you sure you need to unlock the bootloader to flash a ROM? Now that you have root, try installing ROM Manager from the Market, and see if it lets you flash custom recovery with bootloader still locked. If so, then yes you can install a ROM!
Also, the fact that you're able to boot into Clockwork using "fastboot boot" - that also means you can install a ROM .zip file right from there.
cmstlist said:
Question: When you do the fastboot boot command, does that overwrite the stock recovery with Clockwork? Or is it just booting into the recovery img without actually flashing it?
Click to expand...
Click to collapse
"fastboot boot" only launches the recovery no unlock needed. "fastboot flash" flash the recovery
cmstlist said:
Are you sure you need to unlock the bootloader to flash a ROM? Now that you have root, try installing ROM Manager from the Market, and see if it lets you flash custom recovery with bootloader still locked. If so, then yes you can install a ROM!.
Click to expand...
Click to collapse
It worked! Here's the process I used, starting from a completely unmodded Nexus S.
1: Use the method detailed here to gain root access without unlocking the bootloader.
2: Using a root-enabled file explorer (I used Super Manager), rename install-recovery.sh (in /etc) to install-recovery.sh.old . You'll need to remount as r/w to do this. NOTE: You don't *have* to do this step, but if you don't, then you can only use clockwork once after which it will be erased on reboot.
3: Using ROM Manager, install Clockwork Recovery.
4: Pleasure yourself, because your bootloader is still locked and nothing was erased.
I have yet to try actually flashing a custom ROM. Does this mean that it can also be done without unlocking bootloader?
Well damn, whaddaya know. I just flashed MoDaCo r10 without unlocking the bootloader, and without losing any personal data on /sdcard.
I figure someone at XDA should like this.
Pretty much followed distortedloop's advice. Starting from a fully stock Nexus S with Android 2.3.2 (GRH78C):
* Root using the method on this thread.
* Rename install-recovery.su to install-recovery-old.su. (in /bin)
* Install Clockwork Recovery from ROM Manager.
* Download whatever ROM you want (compatible with Clockwork), rename to update.zip, and copy to sdcard.
* Reboot into Clockwork.
* Wipe cache, reset to factory (IF REQUIRED BY NEW ROM). This was my first install of MoDaCo, and that requires it. This step does NOT erase your personal files on sdcard, just all android-related files.
* Install update.zip from Clockwork.
* Continue self-pleasuring ... you now have a custom rom without touching your bootloader or wiping your personal sdcard data.
Maybe it's just because I'm a noob here, but it seems to me that this is a BIG deal. All root/ROM installation methods that I've seen so far have required an unlocked bootloader. This seems to be the first time a Nexus S has been unlocked and custom-ROM'd without unlocking the bootloader and wiping the entire /sdcard.
Ravi
Yeah, it's pretty clear that the unlock the bootloader step isn't necessary for most of what we want to do. Just a habit from earlier devices, perhaps?
What's really odd is now we have to wonder what's the purpose of the oem unlock erasing your sdcard? Speculation was that it was a security feature to keep people from accessing your data if they stole your phone; they couldn't flash something on the phone to get access, but clearly they can. Fastboot into a custom recovery and you own the phone.
Perhaps this is a security hole Google will try to fix some day?
At any rate, I wish we'd discovered this sooner, it would have saved several people some grief in having to lose saved games (Angry Birds!) when they finally decided to root.
distortedloop said:
Yeah, it's pretty clear that the unlock the bootloader step isn't necessary for most of what we want to do. Just a habit from earlier devices, perhaps?
...
At any rate, I wish we'd discovered this sooner, it would have saved several people some grief in having to lose saved games (Angry Birds!) when they finally decided to root.
Click to expand...
Click to collapse
You say "for most of what we want to do." Could you think of a case where you would need to unlock it now? It's now shown to be unnecessary for rooting and installing custom recovery/ROM.
Is there any way to get the word out? This thread isn't stickied, and all the stickied threads on rooting & custom ROMs currently assert that you have to unlock the bootloader.
Ravi
ravidavi said:
You say "for most of what we want to do." Could you think of a case where you would need to unlock it now? It's now shown to be unnecessary for rooting and installing custom recovery/ROM.
Click to expand...
Click to collapse
I'm thinking that something like Superboot might need to have the bootloader unlocked, since it replaces the boot image, right? But I'm not sure.
ravidavi said:
Is there any way to get the word out? This thread isn't stickied, and all the stickied threads on rooting & custom ROMs currently assert that you have to unlock the bootloader.
Ravi
Click to expand...
Click to collapse
There's only a page and a half of posts in the development section right now, so it's not likely to disappear any time soon, but you could ask a mod (theimpaler747 is ours) via PM to sticky it. I thought about asking myself, but seemed a bit tacky to ask for my own thread.
Meanwhile, I'd been linking people to various posts I'd made in other threads suggesting this might work, but once inakipaz and shrivelfig confirmed it, I'm just now pointing people here. I just hope people see this before wiping their phones unnecessarily.
Really, the other guides should just be updated to skip the oem unlock step. That's really the only different thing we're doing here.
i'm just waiting for more people "newbies" to confirm this actually works for them, before making it a sticky
In theory if you really really screw up your phone, you might need fastboot flash in order to recover it. But if fastboot also lets you boot into an img recovery... then you still have a recovery route that doesn't require unlocking.
Sent from my Nexus One using XDA App
I know it's a noob question and all since all you're doing is flashing a custom recovery but will you still be able to get OTA updates after doing this as well?
Sent from my Nexus S using XDA App
qreffie said:
I know it's a noob question and all since all you're doing is flashing a custom recovery but will you still be able to get OTA updates after doing this as well?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
yes because you still have the original recovery installed
distortedloop said:
Perhaps this is a security hole Google will try to fix some day?
Click to expand...
Click to collapse
This would be my guess.
But how? Is it possible to plug this with just a software update? Time will show, I guess.
This (security hole) should also make it possible to do perfect out-of-the-box OS backups. And restores. The problem is that nobody's going to do a backup without playing with their shiny new toy first.
shrivelfig said:
This would be my guess.
But how? Is it possible to plug this with just a software update? Time will show, I guess.
This (security hole) should also make it possible to do perfect out-of-the-box OS backups. And restores. The problem is that nobody's going to do a backup without playing with their shiny new toy first.
Click to expand...
Click to collapse
I can confirm that the Nexus One does not allow this "fastboot boot" on a locked bootloader. Maybe this was just an oversight?
It is entirely possible to plug this with a software update: Samsung/Google could issue a signed update that includes a bootloader upgrade. This has been done many times by HTC for example.
I can confirm that this method works, without unlocking the BL or erasing the SD part.
This is pretty cool. I wish I new about this before I unlocked the bootloader days after I received my phone. I too wonder if this was intentional or an oversite. Google did want this phone to be for developers, but like other's said, this is also a bit of a security hole. The wiping of the sd card on unlock would protect the person if the phone was stolen, like if there was confidential corporate stuff on there. Even if you password protect your phone, someone could fastboot clockwork, mount the sd card and retrieve all the information that was on there.
cmstlist said:
It is entirely possible to plug this with a software update: Samsung/Google could issue a signed update that includes a bootloader upgrade. This has been done many times by HTC for example.
Click to expand...
Click to collapse
It's also been done by Samsung with some versions of the Galaxy S line (some of the "leaked" roms, and even one official kies push (IIRC) changed the bootloader, causing people the ability to use 3 button mode for Odin access, and causing others to lose it.
Not applicable
Delete this thread
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Too complicated.
Just:
1. turn on phone by holding volume up + power to go to bootloader
2. fastboot oem unlock (confirm it on the phone)
3. fastboot flash recovery recoveryfilename.img
4. Select recovery on the phone.
5. You're in ClockworkMod. Go flash a new ROM.
Let me answer myself.
I don't think the latest rom 2.3.4 is compatible with the clockwork you supplied. So I have to flash my phone back to GRH78. I downloaded the stock ROM from the internet. and then push all the images file into /sdcard/clockworkmod/backup/2010.xxx.
Next, I restore the image in clockwork menu.
after restore, reboot the phone, now I am back in business.
When the phone is boot, i lost the root again, so i went to modaco.com and get Paul's package. run it, restart, I got the root.
Finally, go to market place and get ROM Manager, install the clockwordmod. and I have a 'proper' phone.
although I don't have the least rom, at least i got a working phone that is rooted.
bante said:
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Click to expand...
Click to collapse
I have the same problem. How did you handle it?
Wow, why risk messing up your phone with flashing a boot.img when you can just rename /etc/install-recovery.sh to something like /etc/install-recovery.bak?
Here's one way to rename (courtesy of Matridom). Another is to use Root Explorer.
Matridom said:
The new update applies the install-recovery.sh script into our phones (not there previously.
Boot into the bootloader
flash CWM
select recovery from the bootloader (DO NOT reboot the phone)
apply the su binary
boot into the OS and test root
make sure busybox is properly installed
run ADB shell
then:
Code:
su
mount -o remount,rw /dev/block/mtdblock3 /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
Boot back into the bootloader and re-flash CWM, should stay permanent now.l had applied the SU binary at the same time as the OTA update, then renamed the installer script and flashed back CWM.
Click to expand...
Click to collapse
andnaz said:
I have the same problem. How did you handle it?
Click to expand...
Click to collapse
same here someone please help ?
This is a totally unorthodox way to make the custom recovery permanent. If your phone is messed up, good luck fixing it.
There is a much easier and safer way like I mentioned.
PS: flashing recovery for 2.3.4 is the exact same as for 2.3.3!
fastboot flash recovery <recovery .img>
Sent from my Nexus S using XDA App
bante said:
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Click to expand...
Click to collapse
Hi Bante, I am sorry for the inconvenience. I have revert back the CWM Recovery to 3.0.2.4. You can download it at the link above, and try it again
I hope that the problem you mention wont persist anymore
zero383 said:
This is a totally unorthodox way to make the custom recovery permanent. If your phone is messed up, good luck fixing it.
There is a much easier and safer way like I mentioned.
PS: flashing recovery for 2.3.4 is the exact same as for 2.3.3!
fastboot flash recovery <recovery .img>
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I am sorry but not all people can successfully use Command Prompt to do so.
I cant use command prompt, as it says "Image cant be loaded".
So I had to use this method.
I search around the forum and seen this as a quite common problem,
so I decided to share it
Hope you understand.
Anyway, thanks for your method too Cheers
andnaz said:
I have the same problem. How did you handle it?
Click to expand...
Click to collapse
The CWM Recovery I supplied is version 3.0.2.5,
which is not compatible.
So I replaced with version 3.0.2.4.
You just download it at the link above and follow all the step again.
You should able to solve this problem
Do notify me if any problem persist
16vMK1 said:
same here someone please help ?
Click to expand...
Click to collapse
The CWM Recovery I supplied is version 3.0.2.5,
which is not compatible.
So I replaced with version 3.0.2.4.
You just download it at the link above and follow all the step again.
You should able to solve this problem
Do notify me if any problem persist
Wow people like to make things complicated. Why install an entire rom to get ride of a script?
if you can flash cwm, you should have some basic understanding of fastboot, adb and the search options in the forums. the answers are all there already.
Sent from my Nexus S
No disrespect, I agree flashing recoverys should only be done after you understand how to use the tools to do it. there is no reason someone who is going to mod systems on their nexus shouldn't be able to use fastboot and adb properly. all the right drivers are in the sdk.
Sent from my Nexus S 4G using Tapatalk
nxt said:
Too complicated.
Just:
1. turn on phone by holding volume up + power to go to bootloader
2. fastboot oem unlock (confirm it on the phone)
3. fastboot flash recovery recoveryfilename.img
4. Select recovery on the phone.
5. You're in ClockworkMod. Go flash a new ROM.
Click to expand...
Click to collapse
This is what I did.
I rooted my NS, which had 2.3.3
Used phone with stock 2.3.3 until I figured out which ROM I want to flash.
Before I flashed any ROM, did a Nandroid Backup through CWM.
Used the ROM for a few days, but when I saw that official update is ready for download for i9020A, did do a restore from the Nandroid backup I created.
Updated from 2.3.3 to 2.3.4, phone works fantastic, video chat also works great.
After update when I tried using any of the apps required SU permission, they didn't work. I tried installing a couple of .apk files, couldn't either install it or after installation it didn't work.
Thought let me try wiping my phone clean and start all over again, may be I will use a custom ROM again, downloaded ROM, went to ROM Manager to reboot into recovery, nothing happens.
Tried booting into Recovery option manually by pressing Volume Up and Power button, nothing happens but the Bot with an Arrow appears on screen.
So, I thought I will follow this procedure to reflash CWM to my phone and get it going. I was able to use the command FastBoot once, and suceeded pushing .img file to my phone but now whenever I try using the commands from my computer, this error message appears : "This application has failed to start becasue AdbWinApi.dll was not found. Re-installing the application may fix this problem."
Why this error message if I have the sdk on my computer already through which I was once able to push .img file without any troubles?
Can anyone tell me what would be a possible solution?
Also, how can I fix this problem and get ClockWorkMod Recovery installed on my NS again?
How can I get stock recovery image on my phone if I want start all over again from scratch?
Thx a million.
Edit ::: I found the answer as to how to how to install CWM again. Thx anyways.
Other question still remains a puzzle... why am I not able to install certain programs or if did manage to install, can't run them?
I ran your method and I think I'm stuck at some step...
My phone now default boots into CWM 3.0.2.4
Recovery boots to a newer recovery I flashed.
How do I get my phone to default boot into the OS again?
Edit: nevermind, just downloaded the full 2.3.4 rom, extracted and flashed the original boot.img.
dreamsforgotten said:
All the right drivers are in the sdk.
Click to expand...
Click to collapse
After installing the sdk and a platform, I have adb, but where is fastboot?
I was getting the same error as "Image cant be loaded". after hours of struggling I found that It's only because I was not in the same directory as the img file. silly eh?
hi,did you repaiar your phone,i have try everything but it just keep going in clockwork mode,if i than pres reboot now in clockworkmode it stays on google padlock
i realy need phone if you can help or someone else,than ....
just tried this method of window7 (thanks for the work) with cwm 3.0.2.4, but got the same result like the others in this thread: cant boot the android 2.3.4, the system is always booting into the cwm, no way out.
I don't think this tool works as it should.
:-(
EDIT:
I didn't realize that window7's tool would install the cwm into the boot-partition instead of the recovery-partition.
To get my boot partition back I downloaded the 2.3.4 firmware image from http://forum.xda-developers.com/showthread.php?t=1056062 and extracted the boot.img from the zip.
with "fastboot flash boot boot.img" I restored my orginal boot partition an can boot into android again.
(fastboot is part of the android sdk)
Didn't see this in General so thought it would be worth adding, especially since there have been many threads lately with new users wanting to root their phone and then getting scared of the guides.
Now there is also the option to go the official way to unlock the bootloader.
http://htcdev.com/bootloader/
noob here with a question... rooting is the same as unlocked bootloader??
coldsun15 said:
noob here with a question... rooting is the same as unlocked bootloader??
Click to expand...
Click to collapse
Not quite. It can probably explained more accurately but the gist of it is this:
An unlocked bootloader is what allows you to flash custom roms to your phone.
Root access simply grants you the rights to mess with your phones rom whichever way you want.
thomas_wlc said:
Not quite. It can probably explained more accurately but the gist of it is this:
An unlocked bootloader is what allows you to flash custom roms to your phone.
Root access simply grants you the rights to mess with your phones rom whichever way you want.
Click to expand...
Click to collapse
so, basically whats this means is, now i dont need to root and s-off and stuff to be able to put CM7 (for example)?
coldsun15 said:
so, basically whats this means is, now i dont need to root and s-off and stuff to be able to put CM7 (for example)?
Click to expand...
Click to collapse
I thinks that's pretty much it, once you have unlocked your bootloader you'll be able to flash any custom rom you like. Though it'll probably a bit tricky on the first go since you don't have a custom recovery yet, so I believe you'd have to flash some pc10img.
Still it's commonly to believed to be the better choice to stick with the more exhausting solutions posted around here, since HTC will register your phone if you use their tool. At least for the time being they claim that by using their way, your warranty will be void.
I've unlocked my desire z through the htcdev.com website.
Bootloader is unlocked, S-on..
But I can't get a rom installed, it gave me an error while trying to update from the recovery mode (apply update zip) using a stock rom with root.
Akward..
So now I've unlocked my bootloader, but still can't change my rom..
Anyone know how to do it after you've unlocked the bootloader?
flash custom recovery first, from there flash the rom
if you're s-on, bootloader is still locked....
artov said:
flash custom recovery first, from there flash the rom
Click to expand...
Click to collapse
I'm working on it
Gaining temp root using this guide worked.
http://forum.xda-developers.com/showthread.php?t=1178912
But when I press start clockwordmod, it says that my phone is not rooted..
While I press "flashcockwork" clockword mod recovery, I get an error.
än error occurred while attempting to run privileged commands!
I'm doing something wrong..
pretty annoying
I get unlock my bootloader today, and YES there is S-ON, but on the top is written in hboot menu big letters UNLOCKED (How you thinks, htcdev joke?).
I've installed clockworkmod using fastboot:
Code:
fastboot flash recovery clockwork_mod_for_vision.img
Then put off battery and turn on phone with volume down + power, I pressed 'recovery' menu option. Clockworkmod runs correctly. Then tried last stable CyanogenMod 7.1.0, flash was done without errors, I wiped out what's need (cache, data). Next I tried run phone, but freezes at splash (green htc letters on white background).
I tried also miui mod, but Ive got only MIUI splash screen nothing else.
Then I restored my htc from backup (done before flashing using clockworkmod) and Im still on the stock htc android 2.3.3.
Regards,
Mariusz
p.s Sorry for my poor english.
how can I install CM7 or other roms after unlocking the bootloader
Hi,
I also unlocked using the official method of unlocking the bootloader. How can I get root and install CM7 now? Even to install clockwordmod its asking me root the phone.
Can someone help me out here?
Thanks...
RSK
rskainth82 said:
Hi,
I also unlocked using the official method of unlocking the bootloader. How can I get root and install CM7 now? Even to install clockwordmod its asking me root the phone.
Can someone help me out here?
Thanks...
RSK
Click to expand...
Click to collapse
1. boot to fastboot mode, flash a custom recovery (recommand ClockWorkMod), power down the phone.
2. put your downloaded update_cm7.xxx.zip into sdcard, boot phone into recovery
3. choose in the recovery, first "wipe data", then "install update from sdcard", choose the zip file you just put in.
4. choose "reboot system"
that's all to go.
pentie said:
1. boot to fastboot mode, flash a custom recovery (recommand ClockWorkMod), power down the phone.
2. put your downloaded update_cm7.xxx.zip into sdcard, boot phone into recovery
3. choose in the recovery, first "wipe data", then "install update from sdcard", choose the zip file you just put in.
4. choose "reboot system"
that's all to go.
Click to expand...
Click to collapse
I did it, but CM7 doesnt boot.
rskainth82 said:
Hi,
I also unlocked using the official method of unlocking the bootloader. How can I get root and install CM7 now? Even to install clockwordmod its asking me root the phone.
Can someone help me out here?
Thanks...
RSK
Click to expand...
Click to collapse
flak999 said:
I did it, but CM7 doesnt boot.
Click to expand...
Click to collapse
Booting problem is mostly kernel related, do you have logcat output? (run "adb logcat" and boot the phone)
I encountered with the situation (w. another phone) that the recovery can't flush the boot partition during the recovery installation, I have to extract the boot.img file from the zip and flash it manually in the fastboot mode (fastboot flash boot boot.img)
EDIT:
That was a EVO3D with UNLOCKED HBOOT, I believe you're having the same situation, try my method or may others make out a better perfect solution ? (not my own phone, I just helped with its owner, no time to dig the details)
pentie said:
I encountered with the situation (w. another phone) that the recovery can't flush the boot partition during the recovery installation, I have to extract the boot.img file from the zip and flash it manually in the fastboot mode (fastboot flash boot boot.img)
EDIT:
That was a EVO3D with UNLOCKED HBOOT, I believe you're having the same situation, try my method or may others make out a better perfect solution ? (not my own phone, I just helped with its owner, no time to dig the details)
Click to expand...
Click to collapse
Thanks men thats worked for me. First flash the boot.img from CM7.0.1 then run recovery and run update_cm7.0.1.zip. After reboot everything run corectly.
Once more thanks!
flak999 said:
Thanks men thats worked for me. First flash the boot.img from CM7.0.1 then run recovery and run update_cm7.0.1.zip. After reboot everything run corectly.
Once more thanks!
Click to expand...
Click to collapse
now I confirmed the UNBLOCKED HBOOT somehow blocks the CWM to flash boot.img
My Phone have a S-OFF HBOOT and i was considering flash it to the UNLOCK the last night, now it seems not worth the try ~
pentie said:
I encountered with the situation (w. another phone) that the recovery can't flush the boot partition during the recovery installation, I have to extract the boot.img file from the zip and flash it manually in the fastboot mode (fastboot flash boot boot.img)
Click to expand...
Click to collapse
My friend has an officially unlocked Desire Z as well and I gave him these instructions to try it out, he has the same boot problem (stuck at splash screen). Maybe this information should either be stickied or added to a faq until there is a real solution to the problem (unlike this workaround), updated cwm or something like that.
Anyway thanks for sharing this information.
HTC bootloader unlock tool is quite restrictive. It still leaves you S-ON, so you won't be able to flash a new hboot or radios.
I recommend avoiding it and using the current well-proven methods from the XDA Wiki.
Sent from my Desire Z running CM7.
Its working now...
Steps I followed:
1. flash recovery using fastboot
2. Do a nandroid backup using recovery
3. flash boot.img using fastboot
4. reboot into recovery
5. wipe data/cache
5. install update for CM7, and gapps
Also make sure before doing any of these steps you have copied CM7 and gapps update onto sdcard.
Thanks everyone for helping out.
I am experimenting with this myself and I don't seem to be having the same issues flashing a boot.img from an update.zip in ClockworkMod recovery with the official HTC unlocked bootloader that others are having. Maybe it is the version of the recovery that is the issue? Which version is everyone trying to use? I am using the 3.xxxx version that is linked from the wiki. I have had other problems with the 5.xxx version and tend to stick with the older version for that reason anyways.
I'm trying to install jelly bean on my kindle fire but using KFU I've only managed firefirefire and clockworkrecovery.
I tried rooting using KFU to root but that doesn't work. Always gets stuck with the twrp.img error saying it's the wrong image (seems to be a common problem)
I've tried getting twrp installed using adb shell but when I get to the command to load the recovery image I get error; couldn't load recovery image. I thought maybe there was a problem so I tried loading the fff bootloader even though I already had it on my kf but it also returned with error: couldn't load image.
Theoretically, if you have clockwork recovery, there is no need for TWRP. But if you must have TWRP instead, use clockwork to flash a rom (and FFF1.4 while you're at it). Boot into the rom and use the Smirkit to install TWRP. It will save you a lot of hassle.
soupmagnet said:
Theoretically, if you have clockwork recovery, there is no need for TWRP. But if you must have TWRP instead, use clockwork to flash a rom (and FFF1.4 while you're at it). Boot into the rom and use the Smirkit to install TWRP. It will save you a lot of hassle.
Click to expand...
Click to collapse
The problem is getting root access. Most of the guides I've tried to follow require twrp installed to get into recovery. Without root I can't flash another rom.
I also already have FFF 1.4.
So I reverted back to stock and went through the manual process again and I was able to get it to work. When I was initially trying to flash twrp with the command line I copied pasted the name of the file without adding the file extension. Fixed that by adding .img and everything went through. Got Jellybean on here now and it's running great.
If you are installing a custom rom (including MoDaCo), there is no need to go through the "rooting" process, hence saving you "a lot of hassle". Recoveries, like CWM and TWRP provide temporary root access.
soupmagnet said:
If you are installing a custom rom (including MoDaCo), there is no need to go through the "rooting" process, hence saving you "a lot of hassle". Recoveries, like CWM and TWRP provide temporary root access.
Click to expand...
Click to collapse
This is odd because I tried installing the JB rom after I got CWM on there. It booted up to a black screen and left it there for 5 minutes and still black screen. I reverted back with the update bin from amazon website after that.
hxu976 said:
This is odd because I tried installing the JB rom after I got CWM on there. It booted up to a black screen and left it there for 5 minutes and still black screen. I reverted back with the update bin from amazon website after that.
Click to expand...
Click to collapse
That has nothing to do with "rooting". Most of the time it's caused by a bad download (always check MD5s) or not "wiping" correctly before installation.
Update 2 after some fiddling I found that after flashing Pico Capps hdxposed is needed to make the play store work on this build http://forum.xda-developers.com/showthread.php?t=2618158
Update 1 New lolipop ota, this appears to be based on lolipop 5.1 and as such requires xposed unofficial by romracer if you want to use xposed Xposed for 5.0 would not flash for me. Same upgrade steps as before just this one instead of the bottom one and change your xposed package
https://mega.nz/#!i5RRCKQZ!NC291mcIo-2yzr23j8Vg_mLZ11ECql4lL_xen6xwXuM
update-kindle-devpreview_ariel-20.5.2.2_user_522041550.bin
siegesoldier said:
this is the developer preview, sorry if the title is a little misleading. Thanks to http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
Use at your own risk.
https://www.dropbox.com/s/38i2lqq5p...review_ariel-20.5.2.0_user_520033250.bin?dl=0
Hopefully someone can figure out how to make this thing boot when flashed from TWRP
Click to expand...
Click to collapse
Important update, the instructions below are not to be followed !!! They are historical ...
Same drill as in here :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
Replace the original META-INF/com/google/android/updater-script with the one from the zip below. Remove "images" directory. This will ensure that your bootloader stays 4.5.3 and unlocked. When TWRP asks to add root, say yes.
If for some reason you lose TWRP (recovery), reflash it from within 5.0. Since you have root, no biggie. I'll play with this a bit too, but later.
I tried yours and tried my attempt. I'm getting a bootloop with both, let me know if you have any luck. TWRP protects itself from getting replaced.
siegesoldier said:
I tried yours and tried my attempt. I'm getting a bootloop with both, let me know if you have any luck. TWRP protects itself from getting replaced.
Click to expand...
Click to collapse
OK. Does it flash successfully? Does it ask to install root? If it does and bootloops, the bootloader probably needs to be updated too. You could try to flash the new bootloader (just grab my uboot_4.5.3.zip, replace both files in /images, and re-zip).
The trick is that you install Lollipop, install root, and install the new bootloader separately. It should boot OK and you should have root in 5, but you'll lose TWRP (it won't be able to boot since the bootloader will probably be signed). To get TWRP back you'll need to downgrade to 4.5.3
bibikalka said:
OK. Does it flash successfully? Does it ask to install root? If it does and bootloops, the bootloader probably needs to be updated too. You could try to flash the new bootloader (just grab my uboot_4.5.3.zip, replace both files in /images, and re-zip
Click to expand...
Click to collapse
Yes it flashes successfully and asks to install root. Looks like I'll be trying that tonight, thanks!
Edit we have a winner.
Flashed lolipop without bootloader
Installed su
Reboot to recovery
Installed superuser flashable zip
Flashed uboot file with lolipop images folder
Fire has booted and is currently doing the very long lolipop upgrading screen
Currently booting to home screen but then back to the fire screen, etc. Probably my fault for not clearing the cache or a factory reset. I'm not at a computer at the moment but any ideas on how to fix this?
siegesoldier said:
Currently booting to home screen but then back to the fire screen, etc. Probably my fault for not clearing the cache or a factory reset. I'm not at a computer at the moment but any ideas on how to fix this?
Click to expand...
Click to collapse
Turn it off with a long press of "power" button. Then press "power" and "vol+" together, this should get you into the Amazon recovery. It should offer you a factory reset option. Your system should be pretty much stock Lollipop, so I don't see why it should be doing what it does ...
Actually, does it now have stock Amazon recovery or TWRP ? My suspicion is that it should have flashed recovery during the first upgrade cycle.
Upon reflection, there is a chance you have a bit of a soft brick. If the factory reset option does not come up, it may end up a little tricky to fix things. I wonder if you'd be able to connect via adb before it reboots.
bibikalka said:
Turn it off with a long press of "power" button. Then press "power" and "vol+" together, this should get you into the Amazon recovery. It should offer you a factory reset option. Your system should be pretty much stock Lollipop, so I don't see why it should be doing what it does ...
Actually, does it now have stock Amazon recovery or TWRP ? My suspicion is that it should have flashed recovery during the first upgrade cycle.
Click to expand...
Click to collapse
it appears to have TWRP but it will not boot to it with holding keys. I can get the device to appear in ADB but I can not authorize it. Appears to not actually be rebooting. just crashing to fire screen for some reason then back to launcher etc. I may be able to try again at home with a usb port that it remembers.
siegesoldier said:
it appears to have TWRP but it will not boot to it with holding keys. I can get the device to appear in ADB but I can not authorize it. Appears to not actually be rebooting. just crashing to fire screen for some reason then back to launcher etc. I may be able to try again at home with a usb port that it remembers.
Click to expand...
Click to collapse
I wonder if Lollipop does not update recovery at all, and just uses the one from 4.5.4 You do have your old settings around, so there is a chance that prior USB authorization will help. It looks like one should have updated to stock recovery while in TWRP as the last step, after updating the bootloader, ir order to be able to do a factory reset in a situation like this.
If it comes to worst, Amazon reps never ask "did you brick the device yourself?". They only ask if you can get to the home screen, and if not, proceed with the replacement
I think TWRP just blocked it from updating. Oh well, if the ports at home don't work, I was eventually going to get it replaced anyway since I had a blue discoloration on my screen. Glad to be of some moderate use to the community instead of a leecher for once. May the next person have some luck!
bibikalka said:
I wonder if Lollipop does not update recovery at all, and just uses the one from 4.5.4 You do have your old settings around, so there is a chance that prior USB authorization will help. It looks like one should have updated to stock recovery while in TWRP as the last step, after updating the bootloader, ir order to be able to do a factory reset in a situation like this.
If it comes to worst, Amazon reps never ask "did you brick the device yourself?". They only ask if you can get to the home screen, and if not, proceed with the replacement
Click to expand...
Click to collapse
ok I was able to get adb on a previously used port. I do not have root though. What are my options? What recovery should I flash? I also have a replacement kindle coming tomorrow so this is mostly for science now. I am also able to get into bootloader.
erased cache via fastboot. stuck on fire instead of boot to homescreen
siegesoldier said:
ok I was able to get adb on a previously used port. I do not have root though. What are my options? What recovery should I flash? I also have a replacement kindle coming tomorrow so this is mostly for science now. I am also able to get into bootloader.
erased cache via fastboot. stuck on fire instead of boot to homescreen
Click to expand...
Click to collapse
So no adb anymore? I am not sure how SuperSu comes in, there gotta be su program somewhere.
Anyway, the great news is that JMZ is going to be back soon. That's going to boost our tinkering capabilities by 300%
siegesoldier said:
Yes it flashes successfully and asks to install root. Looks like I'll be trying that tonight, thanks!
Edit we have a winner.
Flashed lolipop without bootloader
Installed su
Reboot to recovery
Installed superuser flashable zip
Flashed uboot file with lolipop images folder
Fire has booted and is currently doing the very long lolipop upgrading screen
Click to expand...
Click to collapse
And then soft brick ...
So I wonder now if one could do this :
install 5.2.0 via TWRP
install supersu.zip
and here it gets very tricky:
without any reboots, replace TEE1, UBOOT, and recovery to stock versions 5.2.0
The hope is to end up in 5.2.0 with root. If things fail, then booting into 5.2.0 recovery (which must be installed!!!) should give one an option to do 1) factory reset 2) downgrade to stock 4.5.3 as in here : http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
The problem is that I don't see a way to boot into 5.2.0, and then flash GAPPS after (since your TWRP was replaced by stock recovery earlier). So one would have to install GAPPS those via something like Titanium backup if root does work.
Please, if you already had 1 warranty replacement, don't do this. And, if you replace TEE1 and UBOOT (5.2.0) but not recovery, then you won't have any way to recover.
bibikalka said:
And then soft brick ...
So I wonder now if one could do this :
install 5.2.0 via TWRP
install supersu.zip
and here it gets very tricky:
without any reboots, replace TEE1, UBOOT, and recovery to stock versions 5.2.0
The hope is to end up in 5.2.0 with root. If things fail, then booting into 5.2.0 recovery (which must be installed!!!) should give one an option to do 1) factory reset 2) downgrade to stock 4.5.3 as in here : http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
The problem is that I don't see a way to boot into 5.2.0, and then flash GAPPS after (since your TWRP was replaced by stock recovery earlier). So one would have to install GAPPS those via something like Titanium backup if root does work.
Please, if you already had 1 warranty replacement, don't do this. And, if you replace TEE1 and UBOOT (5.2.0) but not recovery, then you won't have any way to recover.
Click to expand...
Click to collapse
Yes I've used my warranty replacement so I'll be waiting until the official release before breaking my kindle again . How do you stop TWRP from preventing the recovery from being flashed? I noticed it gave a message about protecting itself.
siegesoldier said:
Yes I've used my warranty replacement so I'll be waiting until the official release before breaking my kindle again . How do you stop TWRP from preventing the recovery from being flashed? I noticed it gave a message about protecting itself.
Click to expand...
Click to collapse
Interesting, at what stage of the update did this happen? 5.2.0 file system is slightly packaged and is pain in the neck to peak into, but in 4.5.3 the recovery is updated via a pretty specific command install-recovery.sh , and I cannot find any references to this in updater-script. So I wonder at what stage will this be run. Also, there is no direct image for recovery, one has to reconstruct it as the commands below do. A bit messy ...
install-recovery.sh
Code:
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery:5888256:6d9d1bbc4172c107db3228ed8d9f97111219c617; then
log -t recovery "Installing new recovery image"
applypatch -b /system/etc/recovery-resource.dat EMMC:/dev/block/platform/mtk-msdc.0/by-name/boot:5370112:c2c686ada1b194050a3c8f05e2102345df48e9ce EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery 6d9d1bbc4172c107db3228ed8d9f97111219c617 5888256 c2c686ada1b194050a3c8f05e2102345df48e9ce:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Edit: It kind of looks like /system/etc/install-recovery.sh will be run at every boot. So I wonder if TWRP just renames it to something and calls it "protection". I guess one can double check the file system after 5.2.0 update while still in TWRP, and see what happened to recovery files.
Help
If someone can please help me. I downloaded the update to 5.0, unzipped it, replaced the updater script, but when I zip it back and try to flash it says that it failed. Am I doing something wrong.
Also, if someone has the zip file already and wouldn't mind uploading and sharing it, I would appreciate it.
Thanks for all the help.
hawkazn said:
If someone can please help me. I downloaded the update to 5.0, unzipped it, replaced the updater script, but when I zip it back and try to flash it says that it failed. Am I doing something wrong.
Also, if someone has the zip file already and wouldn't mind uploading and sharing it, I would appreciate it.
Thanks for all the help.
Click to expand...
Click to collapse
Last time this procedure ended up with a soft brick. Are you sure you want to pursue this route?
Help
Maybe not, but if someone can help me with something else. The developer preview for the camera is extremely sharp and the 4.5.4 really isn't. Is there a way to make it crystal clear and sharp?
hawkazn said:
Maybe not, but if someone can help me with something else. The developer preview for the camera is extremely sharp and the 4.5.4 really isn't. Is there a way to make it crystal clear and sharp?
Click to expand...
Click to collapse
Meaning exactly what? It'd be possible to replace the camera app, one for another. Do you think some other system stuff is involved such as some sort of settings?
You'll have to find a way to mount the big 5.2.0 system update file as a filesystem, then you could read what's in there, including the camera stuff.
TWRP help
So I downloaded the zip file for 5.0 and it flashed and asked to install super user. I had to download the apk for supersu and then update it.
But the problem is that I lost my twrp. I push the volume + and power and it just reboots. I also lost my play store. Any thoughts how to get twrp back on?