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.
Hi,
I know this has been requested before for a bunch of other devices and in other forums, but the request was never answered, mainly because other devices had other holes to plug...
basically, my request is to mod the clockwork recovery image in order to protect it with a password. Why, you ask? Simple. The Nexus S has a good protected bootloader (when "oem locked" -- which you can lock while mantaining a custom recovery and/or rooted ROM). When someone steals my rooted phone, the only way to break in is:
- Use the phone normally - PATCHED - I use a pattern lock code;
- Use ADB on the phone via USB access the phone - PATCHED - I disabled usb debugging on the system image;
- Use the bootloader to reflash a new system/recovery image - PATCHED - I "oem locked" the phone so the phone does not accept unsigned images, and also a "fastboot oem unlock" wipes the phone, protecting my private data;
- Boot into recovery - NOT PATCHED - There is no way to password protect a recovery image, as of now.
So, can anyone please attempt this? I'm thinking of trying it myself, but I have very little experience developing for android, and I don't know the source code.
My suggestion is to create a customizable password (maybe a simple 4 to 6 digit PIN code input via the volume keys) on first boot of the recovery image. Then, in subsequent boots, ask for the code before turning on ADB and before giving access to the other recovery options.
If you forget the code, well... you still can reflash a new recovery via the system image. Also you can still fully wipe the phone, so you'll never brick it or anything.
What you guys think? I personally am very sad with this situation. When you root you basically lose all physical security with regards to the data on your phone, I think we can do better.
Sounds like a good idea.
lgrangeia said:
Hi,
"oem locked" -- which you can lock while mantaining a custom recovery and/or rooted ROM
Click to expand...
Click to collapse
How do you do this?
EDIT: This is how ... http://forum.xda-developers.com/showthread.php?t=931865&highlight=oem+lock
I'll second this request. It will save me the pain of doing the following:
To secure my phone between "maintenance" events, I flash back the stock recovery image while I'm not actively performing "maintenance". Do this via adb while the phone is booted with:
flash_image recovery /sdcard/recovery.img
You'll obviously need to put a copy of the stock recovery on your sdcard, along with a copy of clockwork for when you need to do some "maintenance". Note that the flash_image binary isn't present in all ROMs. I know CM7 has it, and in the early days I copied one over from my old Nexus One ROM.
Then turn off USB debugging, OEM lock and password protect your phone.
bubbahump said:
I'll second this request. It will save me the pain of doing the following:
To secure my phone between "maintenance" events, I flash back the stock recovery image while I'm not actively performing "maintenance". Do this via adb while the phone is booted with:
flash_image recovery /sdcard/recovery.img
You'll obviously need to put a copy of the stock recovery on your sdcard, along with a copy of clockwork for when you need to do some "maintenance". Note that the flash_image binary isn't present in all ROMs. I know CM7 has it, and in the early days I copied one over from my old Nexus One ROM.
Then turn off USB debugging, OEM lock and password protect your phone.
Click to expand...
Click to collapse
And you also need one more thing: To be running a rooted ROM. I might want to be running a totally stock rom and use a custom recovery, in order to take advantage of nandroid backup/restore.
If you are running a stock system rom, you cannot reflash recovery from system.
Does anyone know where's the best place to reach the main dev of clockwork mod? is it koush? I might try to tweet him directly to this thread.
I've been thinking about the security of these phones lately as well and it seems there's a lot of holes that a tech-savvy thief could utilize on Android phones... especially one that has custom ROMs.
This suggestion sounds pretty good, but I might be a bit confused. Do you use a terminal emulator on the phone to type in that command to flash between clockwork and stock recovery? Also, if you do a fastboot oem lock when you have a custom ROM, do you have to wipe the whole phone again when you want to fastboot oem unlock to put on another ROM?
bubbahump said:
I'll second this request. It will save me the pain of doing the following:
To secure my phone between "maintenance" events, I flash back the stock recovery image while I'm not actively performing "maintenance". Do this via adb while the phone is booted with:
flash_image recovery /sdcard/recovery.img
You'll obviously need to put a copy of the stock recovery on your sdcard, along with a copy of clockwork for when you need to do some "maintenance". Note that the flash_image binary isn't present in all ROMs. I know CM7 has it, and in the early days I copied one over from my old Nexus One ROM.
Then turn off USB debugging, OEM lock and password protect your phone.
Click to expand...
Click to collapse
dinan said:
This suggestion sounds pretty good, but I might be a bit confused. Do you use a terminal emulator on the phone to type in that command to flash between clockwork and stock recovery? Also, if you do a fastboot oem lock when you have a custom ROM, do you have to wipe the whole phone again when you want to fastboot oem unlock to put on another ROM?
Click to expand...
Click to collapse
Dinan, I'm not 100% sure, but I think the bootloader lock/unlock only prevents you from flashing from the bootloader stage. So you can reflash a custom recovery from the system rom while "oem locked", but you cannot do that from the bootloader.
I thought a bit about this, and pluging this hole in the recovery will make the Nexus S very well protected against physical security attacks (especially since it doesn't even have a SD card slot).
So if I had flashed CM7, then reflashed the stock bootloader and did fastboot oem lock, in order to nandroid or flash a new ROM I would have to first flash clockwork recovery back? If that's the case, would I have to flash it through the terminal from the device or can it be done through adb (or ROM manager)?
lgrangeia said:
Dinan, I'm not 100% sure, but I think the bootloader lock/unlock only prevents you from flashing from the bootloader stage. So you can reflash a custom recovery from the system rom while "oem locked", but you cannot do that from the bootloader.
I thought a bit about this, and pluging this hole in the recovery will make the Nexus S very well protected against physical security attacks (especially since it doesn't even have a SD card slot).
Click to expand...
Click to collapse
dinan said:
So if I had flashed CM7, then reflashed the stock bootloader and did fastboot oem lock, in order to nandroid or flash a new ROM I would have to first flash clockwork recovery back? If that's the case, would I have to flash it through the terminal from the device or can it be done through adb (or ROM manager)?
Click to expand...
Click to collapse
CM7 does not flash your bootloader. Maybe you meant recovery?
you can have an "oem locked" handset and still flash your recovery (or your system) image via both recovery or system, if you have any of those customized/rooted.
What "oem lock" means is that you cannot flash directly from the bootloader (fastboot flash), thats all.
PS: I really have no idea why this was moved to the general forum... this is a development request thread.
In short, what we need is a password protected bootloader which will require password for booting into fastboot or download mode or recovery.
Use Cerberus. Track, remote wipe, take photo, etc. It is embedded into /system and can't be removed with wipe data factory reset. Its all the security you need.
Sent from my Nexus S 4G using xda premium
lgrangeia said:
Hi,
I know this has been requested before for a bunch of other devices and in other forums, but the request was never answered, mainly because other devices had other holes to plug...
basically, my request is to mod the clockwork recovery image in order to protect it with a password. Why, you ask? Simple. The Nexus S has a good protected bootloader (when "oem locked" -- which you can lock while mantaining a custom recovery and/or rooted ROM). When someone steals my rooted phone, the only way to break in is:
- Use the phone normally - PATCHED - I use a pattern lock code;
- Use ADB on the phone via USB access the phone - PATCHED - I disabled usb debugging on the system image;
- Use the bootloader to reflash a new system/recovery image - PATCHED - I "oem locked" the phone so the phone does not accept unsigned images, and also a "fastboot oem unlock" wipes the phone, protecting my private data;
- Boot into recovery - NOT PATCHED - There is no way to password protect a recovery image, as of now.
So, can anyone please attempt this? I'm thinking of trying it myself, but I have very little experience developing for android, and I don't know the source code.
My suggestion is to create a customizable password (maybe a simple 4 to 6 digit PIN code input via the volume keys) on first boot of the recovery image. Then, in subsequent boots, ask for the code before turning on ADB and before giving access to the other recovery options.
If you forget the code, well... you still can reflash a new recovery via the system image. Also you can still fully wipe the phone, so you'll never brick it or anything.
What you guys think? I personally am very sad with this situation. When you root you basically lose all physical security with regards to the data on your phone, I think we can do better.
Click to expand...
Click to collapse
Here's a simple workaround for you, althought less convenient. Once you've made a nandroid backup, move it off your phone. Archive the image with a password and file name encryption on a computer. Extract the image from the archive when you want to restore it, then copy the extracted image to the phone to perform restore.
bubbahump said:
I'll second this request. It will save me the pain of doing the following:
To secure my phone between "maintenance" events, I flash back the stock recovery image while I'm not actively performing "maintenance". Do this via adb while the phone is booted with:
flash_image recovery /sdcard/recovery.img
You'll obviously need to put a copy of the stock recovery on your sdcard, along with a copy of clockwork for when you need to do some "maintenance". Note that the flash_image binary isn't present in all ROMs. I know CM7 has it, and in the early days I copied one over from my old Nexus One ROM.
Then turn off USB debugging, OEM lock and password protect your phone.
Click to expand...
Click to collapse
You can extract flash_image from the ROM Manager app. Unzip the apk file and you'll find it in there. Any rooted ROM can then have this file moved into /system/bin for example.
Rem3Dy said:
Use Cerberus. Track, remote wipe, take photo, etc. It is embedded into /system and can't be removed with wipe data factory reset. Its all the security you need.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
The OP is talking about the security issue, not about the data surviving oem unlock. At the moment, anyone who gets the phone can go into CWM, mount the internal storage, get the image off the phone and extract data from it. The OP is concerned about this security hole.
Rem3Dy said:
Use Cerberus. Track, remote wipe, take photo, etc. It is embedded into /system and can't be removed with wipe data factory reset. Its all the security you need.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Nice. It turns out from little research that both Cerberus and "Theft Aware" have /system support. Call it "root" support if you will.
Now, Theft Aware is far more advanced in this regard in that it also hides the app as a system app with a custom name that you choose. Note that it requires some complexity if you want to uninstall (delete some files manually and stuff).
Theft Aware is also more polished and it seems more effort has been put into the 2.0 version.
Cerberus is more simpler and it feels I can trust them.
mightyiam said:
Nice. It turns out from little research that both Cerberus and "Theft Aware" have /system support. Call it "root" support if you will.
Now, Theft Aware is far more advanced in this regard in that it also hides the app as a system app with a custom name that you choose. Note that it requires some complexity if you want to uninstall (delete some files manually and stuff).
Theft Aware is also more polished and it seems more effort has been put into the 2.0 version.
Cerberus is more simpler and it feels I can trust them.
Click to expand...
Click to collapse
So theft aware is a flashable zip that you flash from recovery?
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
So theft aware is a flashable zip that you flash from recovery?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
It has a "setup app" which you install which in turn installs the actual app. If you have writable /system it can install the app there or if you have ram FS then it can install using what you said.
Sent from my Nexus One using XDA App
(OK, the board ate my first post; maybe this one will do better...)
I am trying to root my Nexus 4 in order to install Titanium Backup. (I have some user data to transfer over from my old Samsung Vibrant before I retire it.) I'm using the Nexus Toolkit for Linux, here:
http://forum.xda-developers.com/showthread.php?t=1999065
The first two steps work fine. I can unlock the bootloader and install clockwork mod. When I try to actually root the device and install su, though, I run into a problem. Specifically, going into recovery mode (either automatic through the toolkit or manually myself) I get the Andy the Android "error" icon (Android flat on his back, chest open, with a red warning triangle over it). That remains until I reboot the device.
Any suggestions? I'm not an experienced rooter (Ti Backup is the ony reason I'm even bothering), so keep it basic please.
Crell42 said:
(OK, the board ate my first post; maybe this one will do better...)
I am trying to root my Nexus 4 in order to install Titanium Backup. (I have some user data to transfer over from my old Samsung Vibrant before I retire it.) I'm using the Nexus Toolkit for Linux, here:
http://forum.xda-developers.com/showthread.php?t=1999065
The first two steps work fine. I can unlock the bootloader and install clockwork mod. When I try to actually root the device and install su, though, I run into a problem. Specifically, going into recovery mode (either automatic through the toolkit or manually myself) I get the Andy the Android "error" icon (Android flat on his back, chest open, with a red warning triangle over it). That remains until I reboot the device.
Any suggestions? I'm not an experienced rooter (Ti Backup is the ony reason I'm even bothering), so keep it basic please.
Click to expand...
Click to collapse
It sounds like you're losing recovery. Do you restart your device after you flash CWM?
Try flashing CWM manually through fastboot, don't restart the device (will overwrite custom recovery) and just go directly into recovery then flash SU.
Alternatively, make sure you're using the right version of CWM and/or double check that the writing process for CWM is going to completion. I don't know if you can disable the stock recovery overwrite without first having root, but you can also look into that
hoponpop said:
It sounds like you're losing recovery. Do you restart your device after you flash CWM?
Try flashing CWM manually through fastboot, don't restart the device (will overwrite custom recovery) and just go directly into recovery then flash SU.
Alternatively, make sure you're using the right version of CWM and/or double check that the writing process for CWM is going to completion. I don't know if you can disable the stock recovery overwrite without first having root, but you can also look into that
Click to expand...
Click to collapse
I'm using whatever version is included in the Universal Tooklkit download. It has two versions included, Standard and Touch. I've tried both, same effect.
Any pointers on "manual" installation of CWM? (As I said, rooting newbie.)
Hi,
Last night i was playing with my N4 (with some root applications) and an app asked for a reboot. I just pressed yes so that the phone will reboot (I have done this earlier without any issues). Suddenly the device doesn't boot up. My N4 is stuck at a black screen. While trying to boot up, the Google logo appears and then a black screen. It doesn't advance to the 'X' logo. I'm running on stock, rooted phone (used N4 toolkit by Wugfresh to root).
I'm able to boot into recovery although. I tried all the possible means, wiped cache, dalvik cache, did a factory reset, backed up the system and tried to restore the same. Nothing happened.
Then i tried the "Back to Stock" option in the N4 toolkit and chose the option "Soft-brick/Bootloop" to recover my N4. These are what happened:
Downloaded the 4.2.2 image from Google servers and tried to flash in the device with prior instruction from the toolkit. Everything went fine until the flashing process. In the last step the CMD window opens up saying it is unrooting and flashing stock and immediately it'll bring up a complete message saying the flashing is complete and to wait until the device boots up. But nothing happens again.
I tried the automatic flashing and on the downloading window it saying download failed and hash checks failed meaning its not downloading.
I searched all the possible threads in a day to find a similar problem but in vain. I'm not a noob but i'm too lazy . But i would do anything to bring my N4 back to life. Anyone please show me a direction.
In short:
Status: Soft-Bricked (guess so), black screen after Google logo
Version: Stock 4.2.2 (rooted+busybox+supersu+twrp)
Able to boot to recovering: Yes, bootable to recovery and bootloader.
Tried Nexus toolkit recovery: Yes but in vain.
Gave up: No and never, I'm searching and searching for answers and I'm worried if I'll end up in a hard brick. :crying:
Guys, please help.
Thank You!
Aghil
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
ameinild said:
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
Click to expand...
Click to collapse
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
aghilvr said:
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Click to expand...
Click to collapse
No, my suggestion would require that the ROM is still on the phone, so you should restore your ROM prior to my suggestion. And I'm by no means an expert (therefore the disclaimer), but I *think* that since it's a bootup problem, it could be solved by flashing a new boot.img (which is essentially flashing a new kernel to the system).
But yeah, let's see if others think this might help, haven't researched it, is at work right now. Just throwing in a suggestion, that's all...
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
I *think* (again, I'm totally not sure about this, as I haven't tried it) that you can sideload a ROM via zip file from recovery, but since I haven't tried it I'm not sure - can anybody confirm???
EDIT: Chromium's suggestion is better, by pushing the ROM.zip to the device and flashing from recovery (check md5 first, just in case).
aghilvr said:
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
Yes there is. Your nexus is not bricked and this is why you shouldnt use toolkits to do things. This is honestly an extremely easy and simple fix. Use adb to push a rom onto the n4.
Code:
adb push \path\to\rom.zip /sdcard
Boot into recovery, do a full wipe, and flash the rom.
You said you downloaded the Google images.
Just boot your phone into the bootloader and run the flashall.bat that is in the Google image folder.
Note this will probably fully wipe you're phone in the process
Sent from my Nexus 4 using xda app-developers app
try this it may help u this toolkit is damn easy to use :
http://forum.xda-developers.com/showthread.php?t=1995688
Okay, thanks guys. I'm on it. Will let you know when I'm done.
That same thing happened to me once. I had to extract the google file and look for the 4 img files(bootloader, system, userdata, recovery) and flash them with toolkit manually and it fixed it, but it erased everything on my sd
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
aghilvr said:
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
Click to expand...
Click to collapse
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
chromium96 said:
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
Click to expand...
Click to collapse
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
aghilvr said:
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
chromium96 said:
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
Click to expand...
Click to collapse
Oh that's why it didn't work all the time
Thanks chromium :fingers-crossed:
Hey thanks guys, my device is back to normal. Chromium a special thanks for you for helping me out. See you guys with my next problem/queris!
I tried to root my Nexus 6P and now I'm stuck. It won't finish booting. I followed instructions found on the web. I unlocked bootloader with no problem. I copied the latest SuperSU file to the phone. I installed TWRP recovery. However, I could not find the SuperSU file when using TWRP. Nevertheless, when I went to exit, TWRP asked if I wanted to instal SuperSU. I recall reading somewhere that it will install the wrong version of SuperSU (not the one for 6.0.1). Somehow I must have hit the wrong selection because it installed it anyway. Now I have an infinite loop.
I have tried to factory reset with TWRP. That fails. I downloaded the 6.0.1 images files from Google. I tried to run flash-all.bat, but that doesn't work. I have pushed images and ZIPs to the /sdcard/ folder with ADB. ADB recognizes the device, but fastboot does not (when connected to my laptop) (which is why flash-all doesn't work). I have tried to install the images/zips with TWRP. However, I always get "failed" messages. I get messages that partitions won't load.
Stupidly, I do not have a nandroid backup (yes, I know, a dumb move).
Any suggestions on what to try next? I'm at my wit's end with this. I've searched the web all morning and found all kinds of helpful info, but I can't find anything to get me past this point. I am perfectly willing to wipe it all out and start over again if I could just force it to do that. I just bought it so I suppose I could return it (I think there's a 30-day return policy), but Google might not like it if it comes back in this state, I suppose. I had an AT&T Galaxy Note 5 for half a day but found out, after the fact, that I can't root it.
Thanks for any help or suggestions.
Why did you follow instructions found on "Web" when u have the beautiful guide by our @Heisenberg? Read this thread. Instead of running flash - all. Bat file, follow the instructions in this guide. http://forum.xda-developers.com/showthread.php?t=3206928
jaidev.s said:
Why did you follow instructions found on "Web" when u have the beautiful guide by our @Heisenberg? Read this thread. Instead of running flash - all. Bat file, follow the instructions in this guide. http://forum.xda-developers.com/showthread.php?t=3206928
Click to expand...
Click to collapse
I saw that post. I wish I had followed it. However, the instructions are very similar to what I tried, although not exact. Where I went wrong is letting TWRP install SuperSU for me. I didn't mean to but when I touched the phone it installed it (of course, I hit something, but I don't know what). Fastboot does not recognize the phone in recovery. I can follow Heisenberg's instructions to get back to stock IF fastboot would recognize the phone. ADB recognizes the phone. Would it be possible to use ADB Sideload instead? How can I force fastboot to recognize the phone? If I could do that, I would be able to flash images back to the phone. Thanks!
U should try fastboot in bootloader / download mode instead of recovery mode..
OK, two comments: Duh (as I slap my head) and Bless You! That worked. I'm back to stock. At least the phone works now. I'll try again to root following Heinsenberg's instructions! Thanks. Where do I sent the beer money?
jaidev.s said:
U should try fastboot in bootloader / download mode instead of recovery mode..
Click to expand...
Click to collapse
Well, I'm back to a stock phone, anyway. Flashing SuperSU per Heinsenberg's instructions did not give me root. Oh well. I'll keep trying. It did install and it did reboot just fine. However, root checker says I have no root and Titanium Backup won't run, either. Thanks.