Related
Hello XDAs
I'm middle of the way on rooting my phone (Nexus One, Android 2.3.4) & flashing a custom rom (cm7 passion-V106)
I follow the tutorial at below & i've done most of the steps
http://wiki.cyanogenmod.com/wiki/Nexus_One:_Full_Update_Guide
Here is what i've done,
-Unlocking the Bootloader
-Installing a Custom Recovery Image both Amon_Ra's Recovery & ClockworkMod Recovery but Amon_Ra is not working.... i unable to boot into Amon_Ra...
-Flashing Radio 5.08.00.04 but i receive a error message that the version is not supported
- Flashing CyanogenMod via ClockworkMod Recovery but i didn't receive install sucessfull message, it only return me back to ClockworkMod Recovery menu.
- Flashing Google Addon Apps via ClockworkMod Recovery - the only flashing that i receive install complete message
After i've done the process above and its come out that i have stuck on the CM7 Loading screen (Blue boot animation screen)
There is a few thing i've noticed which might be the problem...
1:The S_Lock is till On when i boot into Bootloader mode
2: My phone is still unrooted and i unable to use the ROM Manager from Apps Market.
3: sometimes i will not able to access ClockworkMod, it only shows me the " ! " Sign with an Android logo next to it.
Can someone help me with this... i'm stuck now and unable to turn on my phone...
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One
Sent from my Nexus One using XDA App
Unlocking the bootloader doesn't give you s-off or root. You would need a rooted rom to run root apps/superuser.
You need to wipe everything and flash the rom again in recovery (you can't have both recoveries installed at once btw). Your hboot may need updating.
Flash the radio via fastboot so you don't brick your phone. Download it again in case your version is corrupt. You might wanna flash the recovery again.
Might be easier to go back to your nandroid backup (that you must have made, right?) and have a working phone for a while until you read around the subject.
*edit* or just read the wiki lol
hi there every one i updated my nexus one to 2.3.6 (GRK39F) from stock 2.3.4 (GRJ22) sorry but i did not read the post for to upgrade and keep root before upgrading to 2.3.6 and now i am suffering and thought it is not a good idea to post a question there so posting here
my problem is when i upgraded 2.3.6 i was rooted and had clockworkmod recovery image and i had a backup from rom manager as well but before upgrade i wiped the partition and cache and after upgrade i dont have SUPER USER permission nor the clockworkmod recovery tried to flash su.zip from sd card but no luck please can anyone help me get my root back pleaseeeee i need help ....
You'll have to passimg back to an earlier version of Froyo, root, restore your backup, and then flash the update and su zip...
danger-rat said:
You'll have to passimg back to an earlier version of Froyo, root, restore your backup, and then flash the update and su zip...
Click to expand...
Click to collapse
Thankyou very much danger-rat really appriciate your help but today was a bit lucky day for me
I tried to flash a recovery image through ADB and then it went well and then flashed the su.zip from sdcard that gave me superuser permission again thanks again for your help
@0mpranav
No need to flash the system partition, no need to use ADB, just flash Superboot:
Code:
https://bexton.net/2011/09/24/root-access-for-nexus-one-on-android-2-3-6-grk39f-superboot/
If your bootloader is unlocked all you have to do is reboot into fastboot mode. Flash a custom recovery such as RA or CWM, reboot directly into revovery and flash su.zip or whatever flash zip you used to root your device before. Reboot and you are rooted once again.
The following thread has a step by step how to do it. It's fast and easy.
http://forum.xda-developers.com/showthread.php?t=1019759
jboxer said:
If your bootloader is unlocked all you have to do is reboot into fastboot mode. Flash a custom recovery such as RA or CWM, reboot directly into revovery and flash su.zip or whatever flash zip you used to root your device before. Reboot and you are rooted once again.
The following thread has a step by step how to do it. It's fast and easy.
http://forum.xda-developers.com/showthread.php?t=1019759
Click to expand...
Click to collapse
Yup. This is the way every one should be doing it. It's sort of the whole point of the Nexus One. It has an unlockable bootloader.
GldRush98 said:
Yup. This is the way every one should be doing it. It's sort of the whole point of the Nexus One. It has an unlockable bootloader.
Click to expand...
Click to collapse
I have purchased two second hand Nexus Ones. The first thing I did after receiving them and charging the battery was to reboot into fastboot mode and issue "fastboot oem unlock" command. Since they were purchased second hadn I didn't thing I had a warranty anyway so unlocking the bootloader seemed to be a non brainer.
GldRush98 said:
Yup. This is the way every one should be doing it. It's sort of the whole point of the Nexus One. It has an unlockable bootloader.
Click to expand...
Click to collapse
Will any version of su.zip, and fastbook.zip work? What about recovery-RA-passion-v2.2.1.img? or should we be using a different version?
If we should be using different versions of those, could you link to where we could get them?
I've had my Nexus one half-rooted since 2.3 came out, and I haven't been able to root it back.
why mess with 2.3.6 just use oxygen 2.3.7...
kuljit55 said:
why mess with 2.3.6 just use oxygen 2.3.7...
Click to expand...
Click to collapse
I'm sorry I have no idea what that is. I don't even know if its helpful at all. Again, I don't even have root, or a custom recovery. Presently, I have an unlocked bootloader, ADB on my PC, and a half-rooted nexus one from before 2.3.
I have absolutely no idea how to do anything presently, and when someone tells me that trying to root on 2.3.6 is futile and to just use a custom update, it doesn't make any more sense to me.
Care to elaborate past one line that doesn't help at all? Hell when using shell commands through adb, it keeps on saying "permission denied" any time I type in su.
You have an unlocked bootloader, so flash a custom recovery via fastboot, and use the custom recovery to flash the su zip...
danger-rat said:
You have an unlocked bootloader, so flash a custom recovery via fastboot, and use the custom recovery to flash the su zip...
Click to expand...
Click to collapse
Thanks Danger-rat. Although I know you said nothing different that what was already said in this thread, I figured that since you didn't give me specific info about whether or not there were multiple versions of su.zip or fastboot.zip, I figured I should take that as a "No.", so I went for it. All re-rooted now.
I appreciate the help.
EDIT: So if you are as new to this stuff as I am, anyone else who's reading-
You can DL su.zip from http://www.google.com/url?sa=t&sour...ZxOuf9Kw_URvtvh9Q&sig2=Hj72LDNoiBq2Zoa4QquZWQ
and fastboot.zip from http://www.mediafire.com/?ttdkgamud3j
and amon Ra 2.2.1 from http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-passion-v2.2.1.img
then follow the directions here: http://forum.xda-developers.com/showthread.php?t=1019759
** Note: again, these are for people who have unlocked bootloaders. For that info, you'll have to go elsewhere, but it should be readily available, such as this stuff is. I'm just linking it again because I know how frustrating it can be for people like me who aren't too well versed in rooting/unlocking yet.
Downgrade 2.3.6 to 2.2.2 - Nexus One
Problem:
I would like to downgrade my Nexus One to 2.2.2, because I've had non-stop problems with Gingerbread.
So I've gone through the Bootloader -> Recovery -> apply sdcard:update.zip steps, and it fails. This begs the question, how do I go from 2.3.6 to 2.2.2?
Fix:
Generally, phone manufacturers will not allow you to downgrade for various reasons. The stock recovery does indeed validate the update image, so that it's of a greater (or same) version than the installed system. With the Nexus One being a developer phone, you can unlock the bootloader and replace the recovery image with the one that doesn't perform this check, and will allow installation of any image. The caveat is that unlocking the bootloader voids your warranty with the carrier (and sometimes the manufacturer too,) and wipes all user data off the device.
Unlocking the N1 is dead easy. Just install Android SDK and the USB drivers (located in "google-usb_driver" directory.) Then restart the phone in bootloader mode by shutting it off and powering on while holding down the trackball, hook it up to the computer via USB, and in command prompt issue the following command: C:\<path to Android SDK>\tools\fastboot oem unlock. You will be presented with a confirmation screen with further instructions. Upon successful unlock, you can flash a custom recovery that will allow you to install any custom ROM, including downgrade to 2.2.x stock version of Android OS.
To flash ClockworkMod recovery, download the latest version for Nexus One from here, reboot into bootloader mode (power on while holding the trackball down,) and in command prompt issue command C:\<path to ANdroid SDK>\tools\fastboot flash recovery C:\<path to downloaded img>\recovery-clockwork-3.0.0.5-passion.img
Reboot to bootloader mode again, and then use the Volume keys to highlight the "Recovery" option and press Power button. You are now in ClockworkMod recovery, and can flash any custom ROMs via the "Install zip from sdcard" option.
Here is a "stock" 2.2.2 ROM (with root) off XDA-developers forum.
http://forum.xda-developers.com/showthread.php?t=927935
source:http://android.stackexchange.com/questions/13933/downgrade-2-3-6-to-2-2-2-nexus-one
Try It & Report Back...
I had a mostly-stock Nexus 7 running 4.1.1 - unlocked, rooted, TWRP installed, but no major /system changes. When the update came in, I figured "what the heck, I'll just see if it applies - worst case I lose root and my recovery console, but it's a nexus, it's easy to get those back". I applied the update, and it worked! It applied and rebooted, worked fine - but it did lose root and recovery as I expected.
So I tried to get recovery back. It won't come back. Here are the ways I tried:
Hold down VolUp+VolDown+Power to get to fastboot mode. Ran
Code:
fastboot boot recovery.img
(using a number of different copies of both clockwork and TWRP recovery). Each time, the screen went black, google logo came up, but then it booted to AndroidOS
Tried to do
Code:
fastboot flash recovery recovery.img
The flash seemed to look like it did fine, but when I selected "Boot Recovery", it didn't. It booted Android OS
I can get into STOCK recovery using the normal method of selecting it from the menu just fine.
Stock recovery doesn't have ADB running. Fastboot mode doesn't have adb running. Fastboot doesn't have any command for rebooting into recovery apart from the method I mentioned (fastboot boot recovery.img). Booting into AndroidOS reflashes the recovery console with the stock console (I tried to race it running adb reboot recovery, but lost).
I tore my hair out for hours. Nothing I tried would let me boot into a custom recovery. I eventually backed everything up as best as I could using adb (Since luckily Android OS still worked), and reflashed to stock everything. PROBLEM IS STILL HERE! Then I decide to revert the bootloader from 3.41 to 3.34. SUCCESS. 3.34 booted to recovery without any problems at all.
Any idea what the heck is going on here? Anybody else seen this? All the threads I've seen with people having problems booting into recovery end with somebody suggesting "Just get app xyz that will reboot into recovery" - but that is NOT an option if A). you cannot get it to boot or B). you are not rooted/are running stock, because you can't be in AndroidOS and still have the custom recovery flashed UNTIL you are able to get into recovery to actually fix it.
Here's a video of me trying to flash recovery, since nobody will believe me that it doesn't work. Turn off the audio, the bell noise is obnoxious, sorry.
http://www.youtube.com/watch?v=zhHWiu7pO34
I brought up the same concerns when I did a manual flash to 4.1.2 and went through a mess eventually reverting to 4.1.1, using OTA rootkeeper than updating again because on bootloader 3.41 *NO* custom recoveries successfully boot.
how do you flash the old bootloader? if you don't mind me asking.
I have been on boot loader 3.41 for a few days and no issues with twrp. I have flashed a few things since and all is good? Sorry not sure why its not working for some.
ls3c6 said:
I brought up the same concerns when I did a manual flash to 4.1.2 and went through a mess eventually reverting to 4.1.1, using OTA rootkeeper than updating again because on bootloader 3.41 *NO* custom recoveries successfully boot.
Click to expand...
Click to collapse
Huh? I have 3.41 and can go from bootloader to recovery with no problems. Even got a video of it if you don't believe me
Sent from my Galaxy Nexus
You are not alone in this issue, me too, and others more, http://forum.xda-developers.com/showthread.php?t=1932063
I update to 4.1.2 using CWM, didn't lose root. Then changed back to TWRP 2.2.2.0 with bootloader 3.41, now I just updated to TWRP 2.2.3. Everything went smooth even though I'm android noobie.
anotherxyz said:
how do you flash the old bootloader? if you don't mind me asking.
Click to expand...
Click to collapse
Code:
fastboot flash bootloader bootloader-3.34-grouper.img
(or whatever the actual filename is). Then you do:
Code:
fastboot reboot-bootloader
You should at that point see the correct version listed in fastboot
masully84 said:
Huh? I have 3.41 and can go from bootloader to recovery with no problems. Even got a video of it if you don't believe me
Click to expand...
Click to collapse
I think the issue comes from going back to stock recovery without a rooted AndroidOS. Either one by itself seems to be fine. If you still have the CWR or TWRP recovery already flashed, 3.41 can boot to that. If you have root in AndroidOS, you can always re-flash recovery from ROM Manager or something, and that will work fine. And you can boot to recovery from Android OS (so long as you have root).
If you have stock recovery and no root, your only option is fastboot. And that fastboot flash and boot commands do not work. They look like they work - but they don't. So if you already HAVE a custom recovery, it probably won't even break it.
If you really want to do a proper test / prove this, go back to stock recovery with 3.41. Turn the tablet off completely. Boot up holding the three buttons and go into recovery to see that it can go into the stock recovery console. Then reboot with the three buttons again (don't boot AndroidOS), and run the fastboot boot command to run a custom recovery. If that works, I'll eat my hat.
(well, really all that means is that the problem isn't occurring on all systems. Doesn't mean it's not happening to me and many others)
The problem might not be that 3.41 can't boot to recovery -it might just be that 3.41 can't FLASH or BOOT a recovery console through fastboot. Many people will never notice that because:
A). They already have a recovery console flashed, so it still works
B). They flash their recovery from ROM Manager, GooManager, or whatever
If you lose root, you no longer have B as an option. If you also lose your recovery console, you can't get root access back without fastboot, so you have to use fastboot.
Se7enLC said:
Code:
I think the issue comes from going back to stock recovery without a rooted AndroidOS. Either one by itself seems to be fine. If you still have the CWR or TWRP recovery already flashed, 3.41 can boot to that. If you have root in AndroidOS, you can always re-flash recovery from ROM Manager or something, and that will work fine. And you can boot to recovery from Android OS (so long as you have root)[...]
[/QUOTE]
Not sure you've got it right. At least on my N7. My first try was flashing the update.zip in another thread without updating my ROM at all. Running Paranoid Android (2.1799 then) and TWRP. Not sure when in the mix I updated TWRP though.
Thought it might have been a problem with the update.zip, so downloaded the full update.zip from google and tried installing bootloader*.img from that via fastboot.
No change. Reverted to 3.34 without any playing around with deleting files and all is good.
Click to expand...
Click to collapse
Se7enLC said:
I had a mostly-stock Nexus 7 running 4.1.1 - unlocked, rooted, TWRP installed, but no major /system changes. When the update came in, I figured "what the heck, I'll just see if it applies - worst case I lose root and my recovery console, but it's a nexus, it's easy to get those back". I applied the update, and it worked! It applied and rebooted, worked fine - but it did lose root and recovery as I expected.
So I tried to get recovery back. It won't come back. Here are the ways I tried:
Hold down VolUp+VolDown+Power to get to fastboot mode. Ran
Code:
fastboot boot recovery.img
(using a number of different copies of both clockwork and TWRP recovery). Each time, the screen went black, google logo came up, but then it booted to AndroidOS
Tried to do
Code:
fastboot flash recovery recovery.img
The flash seemed to look like it did fine, but when I selected "Boot Recovery", it didn't. It booted Android OS
I can get into STOCK recovery using the normal method of selecting it from the menu just fine.
Stock recovery doesn't have ADB running. Fastboot mode doesn't have adb running. Fastboot doesn't have any command for rebooting into recovery apart from the method I mentioned (fastboot boot recovery.img). Booting into AndroidOS reflashes the recovery console with the stock console (I tried to race it running adb reboot recovery, but lost).
I tore my hair out for hours. Nothing I tried would let me boot into a custom recovery. I eventually backed everything up as best as I could using adb (Since luckily Android OS still worked), and reflashed to stock everything. PROBLEM IS STILL HERE! Then I decide to revert the bootloader from 3.41 to 3.34. SUCCESS. 3.34 booted to recovery without any problems at all.
Any idea what the heck is going on here? Anybody else seen this? All the threads I've seen with people having problems booting into recovery end with somebody suggesting "Just get app xyz that will reboot into recovery" - but that is NOT an option if A). you cannot get it to boot or B). you are not rooted/are running stock, because you can't be in AndroidOS and still have the custom recovery flashed UNTIL you are able to get into recovery to actually fix it.
Here's a video of me trying to flash recovery, since nobody will believe me that it doesn't work. Turn off the audio, the bell noise is obnoxious, sorry.
http://www.youtube.com/watch?v=zhHWiu7pO34
Click to expand...
Click to collapse
Found the solution to the the issue (sorta), I too went through all this trouble as you did in your OP.
I did not have to do anything other then straight up flash this version "recovery-clockwork-touch-6.0.1.5.b8147-grouper.img" via fastboot and bam! recovery works. Link - http://forum.xda-developers.com/showpost.php?p=32810167&postcount=228
Problem is with previous versions of 6.0.1.0 (Official) and TWRP 2.3.1
I still prefer TWRP, but hey This is better then the alternative (No recovery at all)
Now we need to figure out what changed between CWM 6.0.1.0 and 6.0.1.5 and get the other guys (TWRP) to fix their **** for us poor saps that seem to be a minority in the Nexus 7 world having this issue.
I would love to know what actually the fix is and why only some have these issues with older versions of CWM and TWRP.
I installed CWM recovery successfully, my phone's bootloader is also unlocked, but now my cwm is gone, i cannot boot into recovery mode! Any suggestions? do i need to install CWM again? will the root disappear if i do so?
Did you change your kernel?
If you reinstall cwm your root shouldn´t be gone (idk how you installed your recovery, so can´t say for shure ^^), but even if it does, it´s about 5 minuits to re-root your device via recovery
I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks
jdpeck said:
I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks
Click to expand...
Click to collapse
Never trust a recovery installed by a tool kit. Grab the recovery img from the site and flash it manually.
all i have now is stock recovery. whats the best way to manually install twrp
go into fastboot and flash it. you have to be in your bootloader to flash via fastboot. you put the file in the same window as your fastboot program, then type.. fastboot flash recovery recoveryname.img, and that will flash twrp. if you type fastboot boot recovery recoveryname.img then itll only boot into recovery one time, thats what your toolkit did.
Wugfresh Toolkit works great for me and I used it for 6.0.1
Make sure you flash permrecovery file provided by the toolkit, it prompts this during the steps.
If the copies of factory img or recovery provided by the toolkit are not working one easy way is download your own, the toolkit allows you to use your own files and not the one it obtains.
jdpeck said:
I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks
Click to expand...
Click to collapse
Don't use toolkits. I recommend yoiu follow @simms22's solution.
Sent from my Nexus 6 running cyosp using Tapatalk
when you have root, you can always use an app, like flashify, to flash twrp recovery. but you need to have root first.
arcane spade said:
Wugfresh Toolkit works great for me and I used it for 6.0.1
Make sure you flash permrecovery file provided by the toolkit, it prompts this during the steps.
If the copies of factory img or recovery provided by the toolkit are not working one easy way is download your own, the toolkit allows you to use your own files and not the one it obtains.
Click to expand...
Click to collapse
I have tried with and without perm recovery checked, I had the newest twrp img file so I choose other and selected it, I even used the option for one time recovery boot with twrp and then flashed twrp within it like I was updating twrp and still nothing. I am going to try fast boot itself without the tool kit.
Is there any other part of the stock factory image that would update the recovery? I didn't install it coming from lp but it still went back to stock instead of staying on twrp
jdpeck said:
I have tried with and without perm recovery checked, I had the newest twrp img file so I choose other and selected it, I even used the option for one time recovery boot with twrp and then flashed twrp within it like I was updating twrp and still nothing. I am going to try fast boot itself without the tool kit.
Is there any other part of the stock factory image that would update the recovery? I didn't install it coming from lp but it still went back to stock instead of staying on twrp
Click to expand...
Click to collapse
no. but when you flash the full factory image, stock recovery will replace twrp. if you just want to update, flashing the system.umg and boot.img will work, and youll keep twrp.
This is why we don't use toolkits.
Boot to bootloader mode
Code:
fastboot flash recovery <recovery filename>
Where <recovery filename> is the path and filename of the twrp image you downloaded
After flashing use the arrow keys to boot into your newly installed recovery
Take a backup of your phone
Use recovery to boot android
Reboot to recovery with custom power menu options, or by opening a console on your phone and typing in reboot recovery
Post here to tell me that I am right, and thank me.
If you don't reboot to recovery from the bootloader, it will likely be restored back to the OEM recovery.
scryan said:
This is why we don't use toolkits.
Boot to bootloader mode
Code:
fastboot flash recovery <recovery filename>
Where <recovery filename> is the path and filename of the twrp image you downloaded
After flashing use the arrow keys to boot into your newly installed recovery
Take a backup of your phone
Use recovery to boot android
Reboot to recovery with custom power menu options, or by opening a console on your phone and typing in reboot recovery
Post here to tell me that I am right, and thank me.
If you don't reboot to recovery from the bootloader, it will likely be restored back to the OEM recovery.
Click to expand...
Click to collapse
well, thats how you should flash recovery. but its not the reason that we dont use toolkits. we dont use toolkits for several reasons.. 1. they mess up 2. doing it properly is just as fast if not faster 3. newbs think that toolkits are made for them to use. well, they are wrong. toolkits teach you absolutely nothing, which is the worst for beginners.
simms22 said:
no. but when you flash the full factory image, stock recovery will replace twrp. if you just want to update, flashing the system.umg and boot.img will work, and youll keep twrp.
Click to expand...
Click to collapse
thats why after going to lp and getting twrp working I flashed system, boot, and newest radio independently and skipped over recovery but for some reason it reverted back.
just using fastboot by itself worked great thanks for the help
jdpeck said:
thats why after going to lp and getting twrp working I flashed system, boot, and newest radio independently and skipped over recovery but for some reason it reverted back.
just using fastboot by itself worked great thanks for the help
Click to expand...
Click to collapse
if you skipped the recovery.img, your recovery should have stayed.. oh, never mind, i just remembered a file that you need to remove after the first boot, or itll install the stock recovery after the first reboot. its called recovery-from-boot.bak. if you remove that on first boot, youll be fine