Database Develop

Problem rooting - Failed: Too many links

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.

Trouble flashing any update.zip

I'm sorry if this is posted anywhere, but I spent a couple hours last night and another couple hours today searching here and in Google with no luck.
-Skip me for TL;DR-
I got a G1 when they first came out, and rooted it as soon as I could. I ran JF1.5 then JF1.6 then after a while upgraded to Cyanogen. It was great and my GF still uses it and loves it. I got a Nexus One about a month after they came out and I've been in love. I haven't went to Cyanogen since, only because the stock rom has been great and I haven't needed any extra features yet.
Now that 720p is available along with a few other things I'd like, I want to upgrade finally.
-TL;DR end-
Basically I'm trying to say I'm not an idiot or very new to loading roms and toying with an Android device.
From past experiences I basically know the process of root/recovery/rom etc.
I loaded froyo onto the phone when it was available via the stock recovery console and an update.zip ... no problems.
Yesterday, I unlocked the bootloader.
Installed Modaco's superboot.
And used fastboot to push recovery-RA-nexus-v1.7.0.1-cyan.img
After that I turned the phone on, and logged in to check it out and make sure I had root. Everything was running great (Froyo saves your app installs in the cloud!!!) and I did, in fact, have root. All seemed well.
-The Problem-
Now, I can't load any more update.zip files. Nothing at all. Stock rom, modded rom, rom updates, anything. When I try to install any update.zip I get the following output:
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
At the top of the recovery screen it reads: Android system recovery <3e>
If that makes any difference....
NOTE: I can still use fastboot to push new recovery images, which I've tried.
System information below:
Fastboot/Bootloader Screen:
NEXUSONE PVT SHIP S-ON
HBOOT-0.33.0012
MICROP0b15
TOUCH PANEL-SYNT0103
RADIO-4.06.00.12_7
Dec 17 2009, 13:05:23
ABOUT PHONE
Model number: Nexus One
Android version: 2.2
Baseband version: 32.36.00.28U_4.06.00.12_7
Kernel version: 2.6.32.9-27220-g328f560 [email protected] #1
Build number FRF50
Thanks in advance for any help/info!!

Looks like you still have the stock recovery image... do you have backup & restore options iin recovery mode, if not, you still have the stock recovery, reflash Amon-RAs recovery...

No, I don't have backup or restore in the options, neither in recovery or fastboot.
This doesn't make much sense. Here's what I'm doing. It looks like it should be working fine:
Code:
C:\Users\Chris\Desktop\meh\android-sdk-windows\tools>fastboot devices
HT9CWP806497 fastboot
C:\Users\Chris\Desktop\meh\android-sdk-windows\tools>fastboot.exe flash recovery
recovery-RA-nexus-v1.7.0.1.img
sending 'recovery' (3948 KB)... OKAY [ 0.582s]
writing 'recovery'... OKAY [ 1.439s]
finished. total time: 2.021s
Edit:
I was thinking maybe I need a different radio image, but then I remembered reading that Froyo came with a new radio image (right?). And I couldn't install a new radio image anyway because the update.zip files won't load. I'm pretty stumped here....
Edit again:
The code above was what I just did to flash the new recovery, and I still don't have the options to backup and restore the data.
Another edit!: I also loaded Modaco's superboot again (successfully) and started the process over again with no luck.

You don't have a backup/restore option with AmonRa's 1.7.0? That means you don't actually have the custom recovery. Your fastboot is lying to you.

In the terminal app,type "reboot recovery". What happens?

And,try dropping the ".exe" from fastboot.

what they said. Sounds like you still have the stock recovery image. Try reflashing the recovery again.

I tried both the regular RA recovery and RA Cyanogen recovery using both commands, fastboot and fastboot.exe but I continue to get the same recovery image.
I know there's no way to relock the bootloader, but is there any way to reverse what Modaco's superboot did and try that again?

Go here. Scroll to the bottom of the first post. Looks at the screenshots. Does your recovery look like that?

Nope, it's the stock recovery image with the exclamation point and Andy in the background. 4 options: reply, update.zip, factory reset, and wipe cache

Flawd said:
Nope, it's the stock recovery image with the exclamation point and Andy in the background. 4 options: reply, update.zip, factory reset, and wipe cache
Click to expand...
Click to collapse
Try using amon ra recovery image stock for n1, not the cyanogen version.
This one:
http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-nexus-v1.7.0.1.img
and rename it to recovery.img or something short then try the fastboot flash recovery recovery.img

Flawd said:
Nope, it's the stock recovery image with the exclamation point and Andy in the background. 4 options: reply, update.zip, factory reset, and wipe cache
Click to expand...
Click to collapse
Confirm you have root. Go to the terminal app and type "su". What does it say?

Well root isn't necessary to flash a recovery. He just needs an unlocked bootloader.
Well, OP, you might as well just find a different computer and try it on that.

FaJu said:
Well root isn't necessary to flash a recovery. He just needs an unlocked bootloader.
Well, OP, you might as well just find a different computer and try it on that.
Click to expand...
Click to collapse
OP said he unlocked the bootloader.... so OP verify that when you TURN ON your Nexus One, the logo with the X there is a PADLOCK on the bottom of the screen. If it does, then your bootloader is unlocked and you need to install amon ra recovery.
If no padlock, you're not unlocked.

OP make life easy. Go to Market. Install ROM manager. Either install clockwork recovery, or scroll down. Select the option to flash another recovery. Flash. Done

Unlocked but unrooted nexus one in peril

Alright, I give up.
I've wasted one full day and all I do is keep going in circles. I have an unlocked bootloader but I am not able to flash custom recovery to it. When I do:
fastboot flash recovery recovery-RA-passion-v2.2.1.img
it is successful but am having the problem mentioned here:
"Make sure that init.rc isn't calling any install-recovery.sh script, otherwise you'll boot back to stock recovery (exclamation mark with a little Android)."
http://forum.xda-developers.com/showpost.php?p=10467058&postcount=1638
So, no custom rom because I cant turn off verification in order to flash custom rom zip file. Now the problem is that I can't even fix this problem because I don't have root so I can't delete the following files:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
When I try adb shell it keeps saying "permission denied"
It gets better - I've managed to mess things up royally even further. I tried flashing FRG83 system image using "flashboot update update.zip". It was successful but now my phone is going in boot loop!!
Can someone please help me before I lose hope in humanity?

Recovery is only restored when you boot into system, so the idea is that you flash recovery, and go straight into it via the on phone menu, and then install what you need to...
You can either flash a pre-rooted GB, flash the su.zip and then you'll have su access to delete the files when in system or adb, or flash this zip which will remove the two files...
http://db.tt/cp7De8G
Sent from my Nexus One using XDA App

danger-rat said:
Recovery is only restored when you boot into system, so the idea is that you flash recovery, and go straight into it via the on phone menu, and then install what you need to...
Click to expand...
Click to collapse
I totally did not know this. Thanks a lot buddy

RUU for 1.31?

I want to return to stock Ive messed a few things up. Is there a RUU for 1.31?

?
Yeah, I second that request...

Reading through the forums, there isn't one released yet.

tbrad413 said:
I want to return to stock Ive messed a few things up. Is there a RUU for 1.31?
Click to expand...
Click to collapse
I realize this post is hard to follow and all over the place, but I'm tired.
Without a RUU:
Have ADB drivers ready to go if you don't already.
First be sure the bootloader is unlocked via HTCDev.
Next, get a copy of both TWRP and CWM recoveries, you can read why both at the end of the post.
Download the stock rom/stock rooted rom from the thread in development.
Plug the phone into USB and copy the rom onto the phone. Will most likely need to be in a folder called "0" in the root folder.
Open a shell and navigate to your copies of fastboot and adb from the HTCDev unlock.
"adb reboot-bootloader" "fastboot flash recovery TWRP.img"
This will flash TWRP, make sure that you change TWRP.img to the actual file name.
If TWRP doesn't work (like mine didn't), no big deal. Issue the following commands:
"adb reboot-bootloader" "fastboot flash recovery CWM.img"
This will flash clockwork mod recovery, which worked better for me than TWRP.
After you figure out which recovery you want, wipe data/factory reset.
Navigate to 0 and select the stock rom that you downloaded.
One of the recoveries will only see the "0" folder, it's a bug. I believe if you're on TWRP, you can only access 0 which is why you need to put the rom there. Clockworkmod should be able to see anything, but if I remember correctly immediately reboots with the latest firmware.
Flash the room and reboot.
That's how you can go back to stock without a RUU. All of this is from memory but it's accurate. The other option would be to S-OFF via revone and downgrade afterwards. You CAN use revone on the newest firmware - I did it earlier.
Good luck and all that jazz.
Why both recoveries:
TWRP ****ed up really hard on 1.29.x for me and failed to flash or see any files. CWM worked for me on 1.29.x but instantly reboots on 1.31.x. TWRP works for me on 1.31.x but can only see within /sdcard/0/, meaning nothing outside that 0 folder is flashable.
Other notes:
There's also some **** about USB-OTG but I didn't mess around with that. I've been working with multiple Ones over the passed few days and the steps above worked for me. I realize this post is hard to follow and all over the place, but this is all I've been doing this past week and I've got a lot of info on it.
Another note:
If you don't have a working install on the phone to boot into, you can do what I did and boot into the bootloader and use
adb push file.zip /sdcard/0/
Then boot into the recovery and it should be installable.

Fastboot Boot Recovery.IMG not Working after Update

I have been using "fastboot boot recovery.img" to load into TWRP after OTA updates to load SuperSU as I am only rooted using the stock ROM. However, after this recent update (2.16.651.4) that includes the WiFi Calling and Android 4.4.3, when I run the command it just causes the phone to reboot. It does not reboot into TWRP, which is my recovery.img file.
I found a Nexus thread talking about having to add a kernel command line for the Nexus after a certain version of hboot, so I am not sure if it is related.
Does anyone know how to fastboot boot now with the latest update? I would like to avoid replacing my stock recovery with TWRP and just continue to boot into it. Alternatively, is there any other way to install supersu?
Thank you,
Ben

ReproOne said:
I have been using "fastboot boot recovery.img" to load into TWRP after OTA updates to load SuperSU as I am only rooted using the stock ROM. However, after this recent update (2.16.651.4) that includes the WiFi Calling and Android 4.4.3, when I run the command it just causes the phone to reboot. It does not reboot into TWRP, which is my recovery.img file.
I found a Nexus thread talking about having to add a kernel command line for the Nexus after a certain version of hboot, so I am not sure if it is related.
Does anyone know how to fastboot boot now with the latest update? I would like to avoid replacing my stock recovery with TWRP and just continue to boot into it. Alternatively, is there any other way to install supersu?
Thank you,
Ben
Click to expand...
Click to collapse
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.

nfinitefx45 said:
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.
Click to expand...
Click to collapse
Thank you for the reply. I thought about taking that approach, but I was really hoping someone would have an answer on why the procedure wasn't working now. My bootloader is still unlocked.
I found this as an approach someone did on the Nexus 4 for a similar issue:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Thoughts?

nfinitefx45:
I did just now flash TWRP into recovery, loaded SuperSU, and then flashed your recovery.img back to the phone. So thank you very much for the recovery.img.
I'd still like to know if fastboot boot can still work, and also if there is a way in the future I can get my own recovery.img (possibly back it up before taking an OTA)?

ReproOne said:
nfinitefx45:
I did just now flash TWRP into recovery, loaded SuperSU, and then flashed your recovery.img back to the phone. So thank you very much for the recovery.img.
I'd still like to know if fastboot boot can still work, and also if there is a way in the future I can get my own recovery.img (possibly back it up before taking an OTA)?
Click to expand...
Click to collapse
not sure about the fastboot issue, but to backup your recovery any time just go to adb and type the following
adb shell
su
dd if=/dev/block/mmcblk0p43 of=/sdcard2/recovery.img
this will copy your recovery to the external sdcard

Thank you for those steps. I do not have an external SD card installed, so I modified it to store the recovery.img on sdcard instead.
Now I can always fastboot flash twrp and then back to stock recovery.
Thank you again!

nfinitefx45 said:
not sure about the fastboot issue, but to backup your recovery any time just go to adb and type the following
adb shell
su
dd if=/dev/block/mmcblk0p43 of=/sdcard2/recovery.img
this will copy your recovery to the external sdcard
Click to expand...
Click to collapse
You would need root to do this. Not being able to use "fastboot boot" you would just be backing up the flashed recovery. Possibly towel root temp root, but I would assume it has been patched in newest update.

So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?

neudof said:
So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?
Click to expand...
Click to collapse
That's the stock recovery. Did you ever flash a custom recovery back on after the OTA?

xPhantom said:
That's the stock recovery. Did you ever flash a custom recovery back on after the OTA?
Click to expand...
Click to collapse
I am s-on & unlocked but i was able to flash the stock recovery from sd card to take the ota.
Is it possible to flash twrp back in the same way?

neudof said:
I am s-on & unlocked but i was able to flash the stock recovery from sd card to take the ota.
Is it possible to flash twrp back in the same way?
Click to expand...
Click to collapse
Yes, after the OTA, just flash TWRP back through fastboot and then re-flash SuperSU to get root back.

nfinitefx45 said:
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.
Click to expand...
Click to collapse
I just applied the update released today, and I tried to save the recovery.img file before flashing TWRP. However, it kept giving me permission denied. Do you have the recovery.img file from the update released today so I can use it for the next update?

fastboot not working
please any help on how to access fastboot on HTC one m8.
its showing black screen n fastboot mode...
wot can I do 2 annul d problem

rooting problem
hey i am using htc one m8, i unlocked the bootloader and the device reads as
device status modified
*unlocked*
s-on
after this i flashed twrp and cwm a couple of times but its not loading on the device but shows success in the command window, however after clicking on recovery the custom recovery does not show up, and it reboots back into the fastboot mode.
please help me
thank you

jinal shah said:
hey i am using htc one m8, i unlocked the bootloader and the device reads as
device status modified
*unlocked*
s-on
after this i flashed twrp and cwm a couple of times but its not loading on the device but shows success in the command window, however after clicking on recovery the custom recovery does not show up, and it reboots back into the fastboot mode.
please help me
thank you
Click to expand...
Click to collapse
What's the output in the terminal when you fastboot flash recovery?

rooting problem
It doesn't show any error as such.
In the command window it shows successful.
But when I click on recovery it reboots back to fast boot.
Like for a second it shows the screen which reads 'this build is only for developers'
But then instead of opening Twrp it reboots back to fast boot.