Related
I'm having a problem rooting my Nexus One (I have also read the newbie FAQ and searched the forum to no avail) - I have followed the instructions listed on the androidandme site.
When I try to unlock using fastboot I get this returned:
C:\....\Desktop\android-sdk-windows\tools>fastboot oem unlock
... INFOErasing userdata...
FAILED (status read failed (Too many links))
When I start the phone in fastboot mode it now says *** UNLOCKED *** at the top of the screen. I then flashed Amon-Ra's recovery image, as below:
C:\....\Desktop\android-sdk-windows\tools>fastboot flash recovery recovery-
RA-nexus-v1.6.2.img
sending 'recovery' (3954 KB)... OKAY
writing 'recovery'... OKAY
I assumed everything was going to be fine despite the issues unlocking. On trying to boot into recovery mode all I get is a screen with an exclamation mark and the android robot.
On turning the phone on as usual it seems that I can not run "Root required" apps such as the N1 torch.
I have tried running the OEM unlock command again but it seems to think that it has worked, as below:
C:\....\Desktop\android-sdk-windows\tools>fastboot oem unlock
... INFODevice was already unlocked!
OKAY
It would seem from the newbie guide that I still need to flash the recovery image but that seems to be going fine. I can't see that I've messed up so far so is there some way to "unroot" my phone or go through the OEM unlock process again?
Thanks.
You already unlock your bootloader, now put your rom of choice in the root of your sdcard, now flash again
AmonRa recovery, but this time don't reboot, after you you flash the recovery, flash the rom, and reboot.Now you should have su permition. Remember to nandroid backup before flashing the rom.
jongie123 said:
You already unlock your bootloader, now put your rom of choice in the root of your sdcard, now flash again
AmonRa recovery, but this time don't reboot, after you you flash the recovery, flash the rom, and reboot.Now you should have su permition. Remember to nandroid backup before flashing the rom.
Click to expand...
Click to collapse
I tried this, but still don't have root permissions - any thoughts?
I have read and searched and read some more and searched some more, and now just need some help...
Thanks in advance.
2 options, either install superboot from the Modaco's site to gain su, or flash Cyanogen's google adon.
jongie123 said:
2 options, either install superboot from the Modaco's site to gain su, or flash Cyanogen's google adon.
Click to expand...
Click to collapse
I suggest One thing. Pay 15.47 american Usd, at Online Kitchen for Modaco, Viola, Your done, always rooted.. Always Su'd up..
The Bootloader is simple on a windows machine, and so is root.. On Modaco's site there is a whole tutorial on this.. Plus search the threads, a whole ish load too..
i"d pay the 15.47.. Just Nike it, Just do it.. It's so much easier.. Just click-click, bake, download, flash, done..
Go..Go..!
jongie123 said:
You already unlock your bootloader, now put your rom of choice in the root of your sdcard, now flash again
AmonRa recovery, but this time don't reboot, after you you flash the recovery, flash the rom, and reboot.Now you should have su permition. Remember to nandroid backup before flashing the rom.
Click to expand...
Click to collapse
Thanks, I managed to flash the custom ROM this way, however I can't boot into recovery mode unless I boot from fastboot. Is this to be expected or should I be able to just turn on the phone, unconnected to the computer, while holding volume-down and boot into recovery mode?
If you just need root, get 'superboot'. It needs to be flashed to the "boot" partition (after unlocking the bootloader).
What it does is copy the root files to the data ROM and sets up permissions the first time the phone is booted (runs some sort of script I guess).
Link to superboot (free), make sure you get the right version:
http://android.modaco.com/content/g...erd79-epe54b-superboot-rooting-the-nexus-one/
look up "get root back".... Try these commands via ADB:
adb remount
adb shell chmod 6755 /system/xbin/su
....This should "fix_permision" and get you root back, IF you ever had it....
papermonk said:
Thanks, I managed to flash the custom ROM this way, however I can't boot into recovery mode unless I boot from fastboot. Is this to be expected or should I be able to just turn on the phone, unconnected to the computer, while holding volume-down and boot into recovery mode?
Click to expand...
Click to collapse
Using adb you can issue "adb reboot recovery" and wind up in recovery mode. You can also hold down the power button and trackball (connected or disconnected from the computer) and enter fastboot. From there, select bootloader and then recovery.
I am trying to unlock g1 but it fails showing "too many links". It does not do anything else.
sadhuKashmir said:
I am trying to unlock g1 but it fails showing "too many links". It does not do anything else.
Click to expand...
Click to collapse
If you are rooting a G1, correct me if I am wrong, but couldn't you just use one of the one click root methods?
I thought all of the patches denying one click root were contained in official FW's of GB and the G1 did not get it.
Anyone know how to root Nexus One 2.3.4? I've done a few search but I can't find a full guide for that.
Thank you. Peace.
Since Gingerbreak doesn't work with 2.3.4(IIRC), what you can do is:
1.
- Downgrade to 2.3.3.
- Use gingerbreak to get root, flash custom recovery.
(If you downgraded to froyo, you can root it with z4root or SuperOneClick)
- Get ChainsDD's Superuser in flash-able .zip file. Copy it to SD card.
- Get 2.3.4 OTA update patch, copy it to SD card. If you don't want to lose custom recovery, open zip file with any archive utility, delete /recovery from zip. It will prevent stock recovery from restoring.
(If you downgraded to froyo and rooted, you need to get all OTA patches for upgrading to 2.3.3 and 2.3.4)
- Boot to recovery, flash (modified) OTA update patch. Don't reboot the device yet.
- Flash Superuser.
If you can use any application that requires root permission, you're done.
2. Unlock bootloader, push custom recovery and Superuser.
3. This requires Android Kitchen.
- Downgrade to 2.3.3 and root, flash custom recovery, same as 1.
- Get 2.3.4 system dump here.
- Use Android Kitchen to make rooted stock 2.3.4 package. When it's done, copy it to SD card.
- Backup all your data before proceed.
- Reboot to recovery, flash the package you made.
- Reboot and check. If nothing's wrong, you will have rooted stock with custom recovery.
Or when you're on 2.3.4, go to fastboot, flash a custom recovery, flash the superuser.zip
illuminarias said:
Or when you're on 2.3.4, go to fastboot, flash a custom recovery, flash the superuser.zip
Click to expand...
Click to collapse
You need to unlock bootloader to do that.
LFact said:
You need to unlock bootloader to do that.
Click to expand...
Click to collapse
unlock bootloader will wipe all data on device.
Hi guys, thank you for the tips.
So the best way is tho unlock the bootloader? I have no issue to do that since my warranty is finished. Doesn't matter whether it wipes out my data. I have few questions:
1. After I unlocked my bootloader, can I update any upcoming firmware OTA in the future? Or I have to flash it via sdcards.
2. I've heard about rebooting will unroot the phone. Is it true?
3. How do I unlock my bootloader?
4. Is changing rom will reset the phone to factory setting? Will my phone get unrooted?
Sorry I'm quite a noob here. Peace! Appreciate any helps.
1. With unlocked bootloader you do what you want.
2. No.
3. Read the wiki or a another guide. Mainly get the needed software onto a computer and run fastboot oem unlock when the phone is in the bootloader.
4. Flashing/updating to any rom that does not have root included you will loose root. With unlocked bootloader that is no issue. Flash custom recovery then flash su = root.
Great! Thanks!! I will search for a guide and unlock my bootloader soon!
I just picked up a nexus one unlocked with 2.3.4 stock. I want to downgrade to 2.2.2 or 2.2.1, root it with super one click, then after I get root go to rom manager and get my recovery and then flash a cyanogenmod rom. Saying all that what is the easiest way to downgrade to 2.2.1 or 2.2.2 ???
Thanks
vinnyjr said:
I just picked up a nexus one unlocked with 2.3.4 stock. I want to downgrade to 2.2.2 or 2.2.1, root it with super one click, then after I get root go to rom manager and get my recovery and then flash a cyanogenmod rom. Saying all that what is the easiest way to downgrade to 2.2.1 or 2.2.2 ???
Thanks
Click to expand...
Click to collapse
Use passimg.zip. However, if it has really unlocked bootloader, all you have to do is use fastboot to flash custom recovery and any custom rom you want without doing so.
I have locked bootloader and have stock 2.3.4 on my nexus one... How to downgrade it to 2.3.3?
william31518 said:
I have locked bootloader and have stock 2.3.4 on my nexus one... How to downgrade it to 2.3.3?
Click to expand...
Click to collapse
Use passimg.zip, though it depends on your main version saved in bootloader. If you can get FRG33 or FRG83 passimg.zip(though I wonder if you can find it...), use that, then (manually) update them until you reach 2.3.3.
Hey peeps I've unlocked my bootloader and rooted it. So far so good. Thanks for all the helps.
cjoshua said:
Hey peeps I've unlocked my bootloader and rooted it. So far so good. Thanks for all the helps.
Click to expand...
Click to collapse
I feel daft; I have unlocked the bootloader but cannot root, how ridiculous is that.. Am on 2.3.4 build GRJ22.
I'm trying to install "Root" (point V) on http://forum.xda-developers.com/showthread.php?t=636795 but cannot enter the recovery, getting "triangled" for ever & ever.
Please help guys..
(P.S. It is 06:30 here and I've just worked the whole night, that doesn't make anything any easier..)
Not sure what the guide says, but:
Download and place this zip on your SD.
http://dl.dropbox.com/u/6408470/su-releases/su-2.3.6.1-ef-signed.zip
When connected in fastboot, type:
fastboot flash recovery name-of-recovery.img
fastboot boot name-of-recovery.img
Then flash the su zip - DONE!
Note:
name-of-recovery.img should be replaced with the actual name of the recovery image you have.
The recovery image needs to be located in the same folder on your PC as fastboot.
If your using mac or linux, fastboot may need to be substituted for fastboot-mac or fastboot-linux, etc.
danger-rat said:
Not sure what the guide says, but:
Download and place this zip on your SD.
http://dl.dropbox.com/u/6408470/su-releases/su-2.3.6.1-ef-signed.zip
When connected in fastboot, type:
fastboot flash recovery name-of-recovery.img
fastboot boot name-of-recovery.img
Then flash the su zip - DONE!
Note:
name-of-recovery.img should be replaced with the actual name of the recovery image you have.
The recovery image needs to be located in the same folder on your PC as fastboot.
If your using mac or linux, fastboot may need to be substituted for fastboot-mac or fastboot-linux, etc.
Click to expand...
Click to collapse
Thanks for the reply!
I think the problem is in that the "recovery-RA-passion-v2.2.1" isn't supporting build GRJ22 yet. Doing the above correctly (I think) but cannot boot into recovery.
You think wrong. Do it EXACTLY as danger said.
albundy2010 said:
You think wrong. Do it EXACTLY as danger said.
Click to expand...
Click to collapse
Woa, easy mate.. Found the problem, I think. There's no SD card in the phone. Would that explain it?
(Need to wait a while now until I can use the girlfriend's..)
SD isn't required to install recovery, but you will need it for the su zip.
What sort of message are you getting when you flash recovery?
danger-rat said:
SD isn't required to install recovery, but you will need it for the su zip.
What sort of message are you getting when you flash recovery?
Click to expand...
Click to collapse
I get OKAY on both "sending" & on "writing" the recovery in fastboot. I just cannot boot into recovery. It gets stuck on the triangle and I have to pull the battery
I am trying to get rid of the CM7.1 on my Incredible S. I have fastboot on my Ubuntu machine and all the android libraries necessary. I tried a lot of commands from fastboot a couple of days ago but nothing happened. Miui got stuck on boot screen, CM7.2 also did the same. I want to wipe my phone. Delete everything. I am sick of the CM7.1 it is old.
My bootloader says this:
***UNLOCKED***
VIVO .. S-ON
HBOOT-2.00.0000
RADIO-3822.10.08.28_M
I want a step by step way to wipe my phone and install the STOCK ROM (but keeping my root), and using Ubuntu. I have been through dozens of tutorials, my phone wont wipe.
OFFICIAL ROMS:
http://www.filefactory.com/f/e45d6fe3dcf51228/
question: which one do I download (which one is the latest) and why do they have 100mb + difference? thanks a lot!
I need your help before I smash the phone on the wall
Since you're s-on still and unlocked, have you flashed the boot.img from the roms are flashed? Its required after a new rom/kernel flash in order to get the rom booting.
Why do I have to flash the boot.img? I download the *.zip file and flash the whole zip file using ROM manager. That should be enough
alrosh7 said:
Why do I have to flash the boot.img? I download the *.zip file and flash the whole zip file using ROM manager. That should be enough
Click to expand...
Click to collapse
With s on you still have to fast boot flash boot.img to get the phone booting
Search how to do it, you probably did it when you flashed CM7
Sent from my Nexus 7
alrosh7 said:
Why do I have to flash the boot.img? I download the *.zip file and flash the whole zip file using ROM manager. That should be enough
Click to expand...
Click to collapse
With the unlocked bootloader, the boot partition only gets mounted as ReadOnly when in Recovery mode, thus when you flash a ROM in recovery mode, the boot.img file does not get written to your phone.
You manually have to flash the boot.img while in FASTBOOT USB mode using the command:
fastboot flash boot [boot.img file]
Also, you stated that you want to install a stock ROM but keep your root. Here are some things to keep in mind:
1. In order to flash an official HTC stock RUU, you must relock your bootloader. If you attempt to flash a RUU on an unlocked bootloader, you will get a 155 error.
2. Depending on which stock RUU you choose to flash, that particular bootloader may or may not be unlockable.
In the Development section there are several IncS stock, rooted ROMs that were built from official RUUs. I would recommend you give those a try. You may also want to look at mike1986's ARHD ROM which is based on the IncS ICS ROM.
hello,
i recently updated to the official ICS for o2x, and now i wanted to flash a custom ROM again.
so i tried with ROM manager to flash CWM, but my device is not listed above in rom manager.
i tried to install manually with nvflash, and this also didnt work, every time i try to flash cwm, it gives me this error:
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 14 NvError 0x120000
command failure: partition download failed
anybody has any idea how to fix this, and flash CWM?
additional info: im on the new ics layout, my bootloader is unlocked, i have root, USB debugging was on, and i have the correct APX drivers.
Use this tool to flash things ... It has correct recoveries included for old and new bootloader .... http://forum.xda-developers.com/showthread.php?t=2020737
owais40 said:
Use this tool to flash things ... It has correct recoveries included for old and new bootloader .... http://forum.xda-developers.com/showthread.php?t=2020737
Click to expand...
Click to collapse
i tried it before, but if i flash it with that AIO toolkit, it gets me in a bootloop
Detox96 said:
i tried it before, but if i flash it with that AIO toolkit, it gets me in a bootloop
Click to expand...
Click to collapse
Then you must be doing something wrong.... May be flashing something meant for old bootloader to the new bootloader ..... Bootloop at what point ??? Are you able to enter recovery ??? AIO Toolkit is a proven solution working for all P990's.... Also, which Custom ROM do you want to flash and for which bootloader, old or new?????
owais40 said:
Then you must be doing something wrong.... May be flashing something meant for old bootloader to the new bootloader ..... Bootloop at what point ??? Are you able to enter recovery ??? AIO Toolkit is a proven solution working for all P990's.... Also, which Custom ROM do you want to flash and for which bootloader, old or new?????
Click to expand...
Click to collapse
it gets me in the bootloop after changing the recovery image, and then booting in the recovery gets me in a bootloop. (bootloop only happens with toolkit) i tried the latest version available, and with nvflash, i tried it with cwm 5.0.2.0. im not flashing a rom cuz i cant flash cwm yet
Detox96 said:
it gets me in the bootloop after changing the recovery image, and then booting in the recovery gets me in a bootloop. (bootloop only happens with toolkit) i tried the latest version available, and with nvflash, i tried it with cwm 5.0.2.0. im not flashing a rom cuz i cant flash cwm yet
Click to expand...
Click to collapse
Then you might be choosing the recovery for old (GB) bootloader ... Since you are on new bootloader, you will have to choose recovery for ICS bootloader... Use recoveries given within the toolkit itself....
Hello,
Tried rooting my phone with no prior experience. Worked, but eventually I got to where the phone wouldn't boot past splash screen (logo came up, then screen went black while backlight is on and didn't respond to stimuli until battery was removed). Possibly resulted from a build.prop file problem. Did get into boot though, so I fixed that problem by installing a cyanogen rom from a zip file using twrp recovery. I didn't want a custom mod though since I'm used to the look and feel of the 4.0.3 ICS I had, and the cyanogen doesn't seem to have google play so I can't even download anything (original purpose of rooting was to get incompatible apps by spoofing via build.prop file). Currently trying to get back to stock. Unfortunately I didn't make a nandroid backup of the system before the problem occurred, hence I have no backup to flash.
What I tried:
1. Use the official HTC 4.0.3 RUU .exe to upload to the phone. Unfortunately HTC Sync doesn't see this phone, even though I have the correct drivers installed.
2. Attempted to use twrp recovery to install the rom.zip extracted from the RUU directly, the same way I successfully installed the cyanogenmod rom. Failed, claiming it's unable to open zip. The .zip file was checked for integrity and returned by an archiver app.
3. Tried to use these commands from the cmd with phone connected to install the .zip from fastboot:
fastboot erase cache
fastboot oem rebootRuu
fastboot flash zip rom.zip (rom.zip being the functional file of the stock rom)
Failed, saying it's not allowed. Tried it with both locked and unlocked bootloader, no difference.
4. Unzipped the file and tried to flash the system.img file directly, but that failed with a "data length is too large" error.
5. My recovery being twrp 2.1.1, tried looking for altenatives. Can't find any links to download the WCX recovery, but I found several for newer twrp versions, including 2.3.1.0 and 2.6.3.0 which I tried downloading flashing. After flashing the phone got stuck at the cyanogenmod loading logo and wouldn't boot further, and the recovery itself didn't work, just showed the HTC splash, turned black, then booted again normally, getting stuck at the cyanogen logo. Same thing for the 2.6.3.0 version, so I reflashed the original 2.1.1, at which point I can get into recovery but the phone is still stuck at the cyanogenmod during normal boot. At this point I installed the original cyanogenmod .zip from recovery and now at least the phone boots up normally. Still need to get stock back somehow.
Out of ideas and exhausted from this. Any help would be appreciated. Perhaps anyone has a working stock 4.0.3 rom for the Vivid, nandroid backup, etc., or any other ideas. Thanks for reading.
Oh crap...
OK... First... Stock rom can be found in development... Most of the roms there are stock... Read the OP... It'll tell you...
Second... You should use TWRP 2.5.3.0 or something like that I forget...
Third... When you tried the ruu... Did you relock your bootloader...
Side note... Could you get your phone to show up with 'fastboot devices'