Related
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
Hello i was making a tutorial and i clicked root in flashtool 2.9.1 and now when i go to terminal emulator and type su i get this
Code:
reloc_library[1314]: 2639 cannot locate '_mktemp'... CANNOT LINK EXECUTABLE 255| [email protected]:/ $ n
so now i want to go back to stock rom and kernel and redo it all but if i go to stock rom and kernel is my bootloader going to lock himself????
Bootloader won't lock after flashing stock ROM via SEUS or other tool
Bootloader will be locked by update again to 2.1 with SEUS or PC Companion.
If you want stock kernel and you're bootloader will stay unlocked, here is it : STOCK kernel
Hi guys, my friend just bricked his LG Optimus black, by trying to reach recovery mode through Rom manager...
When booting, the security error screen flashes and it turns back off.
I've tried to reach recovery/download mode, by trying several button combinations found on the internet, but none of them seems to work, I get the same security error screen (even when the phone is connected to PC).
Can you guys please help, I have zero experience with this phone
Your friend's phone shows security error because he flashed recovery while he was running a v30x stock rom.
With the update to official ICS, the bootloader changed and if you want to keep stock ICS with recovery you need to flash an unlocked bootloader following this guide http://forum.xda-developers.com/showthread.php?t=2160394.
You could also try using SmartFlash Tool to flash this ROM that already includes a recovery, but, if you flash it, you'll have a gingerbread ROM with an old bootloader and a recovery that can be used to flash CyanogenMod based ROMs.
Lorenzoval said:
Your friend's phone shows security error because he flashed recovery while he was running a v30x stock rom.
With the update to official ICS, the bootloader changed and if you want to keep stock ICS with recovery you need to flash an unlocked bootloader following this guide http://forum.xda-developers.com/showthread.php?t=2160394.
You could also try using SmartFlash Tool to flash this ROM that already includes a recovery, but, if you flash it, you'll have a gingerbread ROM with an old bootloader and a recovery that can be used to flash CyanogenMod based ROMs.
Click to expand...
Click to collapse
Thanks, I finally managed to access Download mode and flash stock firmware, and I also flashed the unlocked bootloader, using the exe file...
But I still have a problem...
I still can't access CWM. When pressing the combination in the post you linked, it just shows me a screen, writing recovery mode, and it does nothing.
Didn't the exe file install CWM?
Is it safe to install it with Smart Flash Tool now?
Can you boot to stock ROM? If yes, is his phone rooted?
Lorenzoval said:
Can you boot to stock ROM? If yes, is his phone rooted?
Click to expand...
Click to collapse
I can boot to stock ROM, and yeah I rooted it with Unlock Root after installing the unlocked bootloader.
Download terminal emulator from play store, download recovery.img from here and place it in the root of his sdcard.
Open terminal emulator, type su, press enter, type dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4 and you should have finished! :highfive:
Hi,
I've just done an OTA update to 6.09.401.5
My phone is 801n, S-OFF with locked bl. Hboot is 1.57.
After the OTA I had lost root, so I went on to recovery (stock) to sideload supersu.
Much to my surprise, I can't adb with the stock recovery.
Looking in device manager, it just shows up as mass storage device.
I've added the device ID to the google driver inf:
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0FF9
and forced the driver, which loaded fine. But adb devices still shows nothing.
Same thing when I force ADB Composite Device.
Also tried disabling and enabling USB debugging without any success.
Do you guys have a similar issue? Are your device ids the same as mine in recovery? ADB works?
Nemesis_00 said:
Hi,
I've just done an OTA update to 6.09.401.5
My phone is 801n, S-OFF with locked bl. Hboot is 1.57.
After the OTA I had lost root, so I went on to recovery (stock) to sideload supersu.
Much to my surprise, I can't adb with the stock recovery.
Looking in device manager, it just shows up as mass storage device.
I've added the device ID to the google driver inf:
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0FF9
and forced the driver, which loaded fine. But adb devices still shows nothing.
Same thing when I force ADB Composite Device.
Also tried disabling and enabling USB debugging without any success.
Do you guys have a similar issue? Are your device ids the same as mine in recovery? ADB works?
Click to expand...
Click to collapse
You can not sideload with stock recovery nor use adb commands. flash a custom recovery
alray said:
You can not sideload with stock recovery nor use adb commands. flash a custom recovery
Click to expand...
Click to collapse
That seems strange. It was a while ago, but i did root my 4.4.2 install somehow with the bootloader remaining locked (I didnt erase my phone), and keeping stock recovery. Since the BL is locked I probably didnt flash a custom recovery and then revert to stock.
I was pretty sure I just sideloaded it with stock recovery since my device is SOFF.
Are you certain it can't be done?
It's pretty stupid of me then, as I am not sure how I rooted it before then.
Nemesis_00 said:
That seems strange. It was a while ago, but i did root my 4.4.2 install somehow with the bootloader remaining locked (I didnt erase my phone), and keeping stock recovery. Since the BL is locked I probably didnt flash a custom recovery and then revert to stock.
I was pretty sure I just sideloaded it with stock recovery since my device is SOFF.
Are you certain it can't be done?
It's pretty stupid of me then, as I am not sure how I rooted it before then.
Click to expand...
Click to collapse
you can not use adb sideload with stock recovery.
if you don't want to wipe the phone by unlocking the bootloader using htcdev.com you can:
flash a custom recovery in a masked firmware.zip with the bootloader locked (s-off only)
or
do wait said above and then unlock bootloader from custom recovery using adb shell or guru bootloader reset tool.
alray said:
flash a custom recovery in a masked firmware.zip with the bootloader locked (s-off only)
or
unlock the bootloader with the s-off method and flash a custom recovery.
Click to expand...
Click to collapse
is masking firmware works ?
If this works then no one need htcdev I think it's not possible or can brick
For totally stock locked S On phone I take a same version firmware mix TWRP flashing you don't need htcdev or unlocked ?
How I can unlock with S Off & stock Recovery non root ?
yatindroid said:
is masking firmware works ?
Click to expand...
Click to collapse
with s-off you can flash a custom recovery with a locked bootloader, no risk. just pack the custom recovery image (renamed recovery.img) with an android-info.txt that match your phone info inside a firmware.zip file and flash it in ruu mode.
you can then use the guru bootloader reset tool to unlock your bootloader using the custom recovery or by using an adb shell from custom recovery
If this works then no one need htcdev I think it's not possible or can brick
Click to expand...
Click to collapse
This is not a magical way to unlock, you first need s-off. if the phone is s-on then htcdev is required.
For totally stock locked S On phone I take a same version firmware mix TWRP flashing you don't need htcdev or unlocked ?
Click to expand...
Click to collapse
will only work for s-off, you can not flash a firmware with twrp inside, you can only flash sigend firmware with s-on
How I can unlock with S Off & stock Recovery non root ?
Click to expand...
Click to collapse
you can't, you first need to flash custom recovery using a masked firmware.zip like said above or use htcdev. using the firmware method will not wipe the phone.
alray said:
you can not use adb sideload with stock recovery.
if you don't want to wipe the phone by unlocking the bootloader using htcdev.com you can:
flash a custom recovery in a masked firmware.zip with the bootloader locked (s-off only)
or
do wait said above and then unlock bootloader from custom recovery using adb shell or guru bootloader reset tool.
Click to expand...
Click to collapse
Well, im an idiot. That's probably what I did last time as well.
For some reason I remembered using sideload.
Flashed TWRP, installed SuperSU and back to stock recovery.
Thanks a bunch,
Hello everyone, this guide will be as simple as possible, taking into account that they deal with almost all the same things as to unlock the bootloader
First of all from flashtool flash the stock version number 76 (the one used to unlock the bootloader)
Turn on the device in fastboot mode, and use this command "fastboot flashing lock or fastboot flashing lock_critical" to then proceed to turn off the device
Then from lolinet download the latest stock version for your region and your device version either arm or arm64, once downloaded flash from flashtool, they must do this after blocking the bootloader because the last stock does not allow said unlocking
After doing all this, you should already have the bootloader locked with its latest corresponding stock version, I must remind you that basically the same thing is used as when unlocking the device.