Database Develop

[Q] Root Nexus One 2.3.4 (stock)

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

[Q] stock 4.2.2 - how to root ?

Can someone please help with this ?
I'm want to flash the stock recovery in order to receive the 4.2.2 OTA update (currently I have the stock 4.1.2 + root + TWRP + S-OFF)
Can someone guide me please, what stock recovery do I need to flash and where should I grab it from ?
I've found only this link http://forum.xda-developers.com/showthread.php?t=2158763
Not sure if is the right recovery but the download link from there is broken
Any idea if I need to be S-OFF or ON in order to receive the OTA ?

That's old thread. Run either a ruu or Mike's stock. Be sure u have stock recovery as well.
Sent from my HTC One

where can I have the stock recovery ? (I can't find it)

- Ok after a lot of digging around I've found a stockrecovery.img file , so I've flashed that like this: fastboot flash recovery stockrecovery.img
- the spooky part after doing this was that I was unable to enter into recovery anymore , the screen alway remained in Entering Recovery and that was it ... maybe someone explain why ?
- then I've locked the bootloader like this: fastboot oem lock
- then I've installed a RUU for Europe (also found out here after diggin around) which actually downgraded my firmware to an older version
- after downgrade I've received an OTA update to a newer firmware - did that
- then after I've received the 4.2.2 OTA update , finaly
- then I've performed a bootloader unlock
- then I've flashed a TWRP recovery image in order to root the device
Now here comes the issue, after flashing the TWRP recovery image, while entering into the TWRP recovery I'm not able to click on any menu , is like the touch screen does not take any input so I'm unable to install the SU binaries
Has anyone encountered this issue ?
How did you root your stock 4.2.2 device ?

Reflashed the CWM recovery (instead of TWRP) as somebody recommend it and it worked - now I have root, too.

dinoc said:
Reflashed the CWM recovery (instead of TWRP) as somebody recommend it and it worked - now I have root, too.
Click to expand...
Click to collapse
Hi there,
i have the exact same problem, the screen wont register touches. How do i reflash CMW? im a noob

You are going to flash it in the same manner you did with the TWRP.
You put your phone into fastboot then issue a command like :
fastboot flash recovery cwm_image_name
You should search for a cwm recovery image file.
And you need to have the bootloader unlocked

After update to 4.2.2 TWRP wont recocnize touch due to the driver update.
Here is a modified version of TWRP where touch work with 4.2.2 OTA
Download and rename it to howdoyouwant.img then
fastboot flash recovery howdoyouwant.img
fastboot erase cache

[Q] Stuck on boot after KK update

This is for my friend's ATT One. Bone stock, unrooted, S-On, no changes made to the device from the store. He took the OTA for Kit Kat and was running fine, then his phone rebooted on him a couple days later and won't go past the white HTC boot screen.
Two problems: First, I cannot use ADB, as it does not detect his phone. When I plug in his phone, it says drivers failed to install for HTC MTP device. I also have an HTC One, unlocked, S-Off, etc., and when I plug mine in, it's detected and ADB works just fine like always (so it's not that I need to reinstall drivers).
Problem 2: the phone seems to hang trying to do a factory reset from the bootloader menu, or from the stock recovery menu. It will start the reset, reboot to the white HTC screen then hang. I left it for more than an hour twice. Nothing doing.
Is there a way to reflash/restore his phone without wiping his sdcard? He's OK losing the data partition, but wiping sdcard is last resort. Using an RUU .exe will wipe his sdcard, as will unlocking his bootloader to try to install a custom recovery. Just not really sure what tools I have at my disposal with a stock recovery and no adb. Will fastboot flashing a rom.zip extracted from the ATT RUU also wipe his sdcard? Or does that only happen with the RUU .exe? Any ideas appreciated..

Shott3r said:
This is for my friend's ATT One. Bone stock, unrooted, S-On, no changes made to the device from the store. He took the OTA for Kit Kat and was running fine, then his phone rebooted on him a couple days later and won't go past the white HTC boot screen.
Click to expand...
Click to collapse
Did you tried wiping /cache?
Shott3r said:
Two problems: First, I cannot use ADB, as it does not detect his phone.
Click to expand...
Click to collapse
ADB can only be used when phone is booted+usb debug on or via custom recovery
Shott3r said:
He's OK losing the data partition
Click to expand...
Click to collapse
I hope so, factory reset is a /data wipe... probably already wiped from your first attempt to factory reset
Shott3r said:
but wiping sdcard is last resort. Using an RUU .exe will wipe his sdcard
Click to expand...
Click to collapse
And the available ruu.exe for at&t is a downgrade in version so it will require s-off.
Shott3r said:
Will fastboot flashing a rom.zip extracted from the ATT RUU also wipe his sdcard? Or does that only happen with the RUU .exe? Any ideas appreciated..
Click to expand...
Click to collapse
you can't flash a rom directly from fastboot. You can flash a rom via a custom recovery or flash a ruu.zip from RUUmode (fastboot oem rebootRUU).
Unfortunately I think there is no way to save /sdcard. You will need to unlock bootloader to flash a custom recovery.
easy way:
flash twrp custom recovery
flash guru reset rom for your version
or
flash twrp custom recovery
flash and use arhd rom
or the long way:
flash twrp
flash arhd
s-off
flash ruu.zip

alray said:
Did you tried wiping /cache?
...
you can't flash a rom directly from fastboot. You can flash a rom via a custom recovery or flash a ruu.zip from RUUmode (fastboot oem rebootRUU).
Unfortunately I think there is no way to save /sdcard. You will need to unlock bootloader to flash a custom recovery.
...
Click to expand...
Click to collapse
I did erase cache first thing. Regarding flashing the ruu.zip from RUUmode, my question is whether flashing the ruu.zip will erase the sdcard? Also does it even matter, since he has KK firmware, and is S-On? Will the ruu.zip from Jellybean 4.3 even flash on his (current) KK firmware?
Any ideas on why the factory reset would hang? Cuz that's best case scenario is to simply factory reset, but it seems not to work presently.

Shott3r said:
I did erase cache first thing. Regarding flashing the ruu.zip from RUUmode, my question is whether flashing the ruu.zip will erase the sdcard? Also does it even matter, since he has KK firmware, and is S-On? Will the ruu.zip from Jellybean 4.3 even flash on his (current) KK firmware?
Any ideas on why the factory reset would hang? Cuz that's best case scenario is to simply factory reset, but it seems not to work presently.
Click to expand...
Click to collapse
ruu will wipe everything.
and no you can't use ruu with s-on because its a downgrade in version.

Is there any way that you know of to get access to the sdcard in the circumstance I've described to try to rescue some files before I set about with the rescue? Doubt it, but just asking.

Shott3r said:
Is there any way that you know of to get access to the sdcard in the circumstance I've described to try to rescue some files before I set about with the rescue? Doubt it, but just asking.
Click to expand...
Click to collapse
maybe you could use remote recovery booting (booting a custom recovery without installing it). Not sure if it still can be done (think it was disabled in 4.2.2)
fastboot boot name_of_recovery.img
then use adb from recovery to copy sdcard content to your computer
adb pull /sdcard C:\somefolder
If you can't boot from a remote recovery, then I think you can say goodbye to those files in your /sdcard

[q] [help] cannot flash

Hello to everyone, yesterday i tried to unlock bootloader, root m7 and flash a custom rom...everything seems to go well, except that i get a bootloop after installing the rom.
I tried to reflash the rom but still get bootloop, then for my mistake i erase all the file (and the rom too) inside my phone, so i only can flash rom with adb.
I can acces to recovery, but if i try to mount usb otg i can't copy there any rom .zip.
I'm trying with the ruu, but windows after the double click doesn't open anything.
If i try to flash something with fastboot i get this error( see attachment).
Now i'm asking you how can i resolve this?? Am i missing something??
Ask me if you nedd to know more details.

celoni said:
Hello to everyone, yesterday i tried to unlock bootloader, root m7 and flash a custom rom...everything seems to go well, except that i get a bootloop after installing the rom.
I tried to reflash the rom but still get bootloop, then for my mistake i erase all the file (and the rom too) inside my phone, so i only can flash rom with adb.
I can acces to recovery, but if i try to mount usb otg i can't copy there any rom .zip.
I'm trying with the ruu, but windows after the double click doesn't open anything.
If i try to flash something with fastboot i get this error( see attachment).
Now i'm asking you how can i resolve this?? Am i missing something??
Ask me if you nedd to know more details.
Click to expand...
Click to collapse
you can't flash a rom with fastboot / you flash roms with custom recovery
is your bootloader unlocked ? did you install TWRP / CWM custom recovery ?
did you erase cache and reboot the phone after installing the custom recovery ? what device do you have ? post the results from fastboot getvar all minus you serial no and IMEI

clsA said:
you can't flash a rom with fastboot / you flash roms with custom recovery
is your bootloader unlocked ? did you install TWRP / CWM custom recovery ?
did you erase cache and reboot the phone after installing the custom recovery ? what device do you have ? post the results from fastboot getvar all minus you serial no and IMEI
Click to expand...
Click to collapse
Thanks for your fast answer and help...i managed to install the CM11 using the usb-otg with twrp...problem solved

celoni said:
Thanks for your fast answer and help...i managed to install the CM11 using the usb-otg with twrp...problem solved
Click to expand...
Click to collapse
Excellent !!

[ROOT WITH Magisk/TWRP] A70 ANDROID 9/10 ON ANY VERSION

Hi I bring you how to root and install twrp on A70 any version ,I think its work on all new samsung device:good:
note :
1-first unlock your bootloader https://forum.xda-developers.com/galaxy-a70/development/recovery-twrp-galaxy-a70-t3955984
2-in all step Remove auto reboot in odin
requirement files :
PeaZip
https://www.peazip.org/download-installer-p-windows.html
TWRP recovery.img mack it tar with PeaZip
https://github.com/Grarak/android_device_samsung_a70q-twrp/releases
vbmeta.tar Vbmeta.img- https://www.androidfilehost.com/?fid...26312261811717
Stock recovery.img from your stock rom [ you can download your device rom and extract stock recovery ] and mack it tar with PeaZip
Magisk 20.1- https://www.androidfilehost.com/?fid...26312261797449
Odin3- https://www.androidfilehost.com/?fid...26312261811763
Samfirm- https://www.androidfilehost.com/?fid...26312261811762
Lets start
1- in stock roms maybe work on custom roms
2-boot in to download mode and flash vbmeta.tar via odin in ap
3-after that reboot to recovery by pressing vol+ and power and clear data and cache in stock recovery
4- reboot again in to download mod and now flash twrp via odin in ap
5-reboot to twrp recovery by pressing vol+ and power and slide right to modify. Click wipe, click format data, type yes after that go back and reboot to recovery. slide right to modify, click mount, if mount system partition read-only is checked, back out and reboot back to recovery and check mount again, it should now be unchecked. . Now click Vendor so its checked and system should be unchecked, back out.
6- Copy Magisk 20.1 to the External sd card. In TWRP click install, select storage and choose micro sd card, click on magisk and slide right to confirm. (you must have vendor checked in mount or it wont flash properly). when done, click all way back click reboot to download.
7- now flash stcok recovery tar file via odin and reboot your device to system
8-after your device start run Magisk and update it by install options
well done you have twrp and rooted device :fingers-crossed::good::fingers-crossed:
i think this method work on all new samsung device and just you have own your device file like
twrp /stock recovery /vbmeta
note : if your twrp Stuck on twrp logo you have to install stock recovery and repeat from step 2
tested device A705FN:fingers-crossed:
thanks to :good:
MarvinMod
Grarak
and other to help me in this method

thanks a lot. i will test it today and check back here tomorrow
edit: i cant flash twrp via odin. download mode says "only official released binaries are allowed"
bootloader unlocked
oem unlock grayed
vmeta flashed
wipe data cache
but cant flash twrp. tried to download latest version but still no joy
i have 705FN with A705FNXXU5BTC2 rom installed

thewalekk said:
thanks a lot. i will test it today and check back here tomorrow
edit: i cant flash twrp via odin. download mode says "only official released binaries are allowed"
bootloader unlocked
oem unlock grayed
vmeta flashed
wipe data cache
but cant flash twrp. tried to download latest version but still no joy
i have 705FN with A705FNXXU5BTC2 rom installed
Click to expand...
Click to collapse
Hi i think you have to first flash 4file rom on your device
Plez check this maybe help you
https://forum.xda-developers.com/sa...torial-root-november-security-update-t3715661
Your bootloader must be updated

seli1987 said:
Hi i think you have to first flash 4file rom on your device
Plez check this maybe help you
https://forum.xda-developers.com/sa...torial-root-november-security-update-t3715661
Your bootloader must be updated
Click to expand...
Click to collapse
Hi thanks for the reply. But the day before i read this post, i flashed the latest firmware from sammobile which is the rom i told in the post (BTC2). Doesnt latest firmware include latest BL? Where can i find the current version of my BL in my phone?

thewalekk said:
Hi thanks for the reply. But the day before i read this post, i flashed the latest firmware from sammobile which is the rom i told in the post (BTC2). Doesnt latest firmware include latest BL? Where can i find the current version of my BL in my phone?
Click to expand...
Click to collapse
Try again flash 4 file frimware and let device start to system after that reboot to download mod and flash vbmeta.tar and let your device start to system
After that reboot to stock recovery and wipdata and cach and reboot to download mod and now flash twrp
The wrong is with your bootloader if you cant fix it try to search your problem in google
You are not only one have this problem

I did every thing from scratch. Even lock and unlock the bootloader.
I am tring to make sence. Vbmeta is "verified boot". So the idea is trick the phone with our own bootloader so that we can flash twrp.
Since i cant flash twrp, vbmeta should be updated.
Am i right?

thewalekk said:
I did every thing from scratch. Even lock and unlock the bootloader.
I am tring to make sence. Vbmeta is "verified boot". So the idea is trick the phone with our own bootloader so that we can flash twrp.
Since i cant flash twrp, vbmeta should be updated.
Am i right?
Click to expand...
Click to collapse
Unlock bootloader, factory reset, unsure oem is unlocked and grayed out in settings >developer options.
Then flash vbmeta, manual reboot to download mode, flash twrp, boot to twrp, factory reset in twrp , flash magisk zip then factory reset again, now boot system.
The vbmeta you flash is empty and allows flashing third party zips.

Hiii, i did almost everthing, but when i boot in recovery and go to mount, system partition read-only is checked. already tried 4 for times reboot to recovery but still checked.
Yes, i slide right to allow to modify. Any suggestion ?

BubSystemS said:
Hiii, i did almost everthing, but when i boot in recovery and go to mount, system partition read-only is checked. already tried 4 for times reboot to recovery but still checked.
Yes, i slide right to allow to modify. Any suggestion ?
Click to expand...
Click to collapse
Go ahead with the steps. Ignore mount system.
Let's see what happens
Worst scenario, you soft brick the phone or bootloop which can be fixed by flashing stock rom again.
Make sure you have stock rom and you backup your data

Any way to pass SatefyNet?

Instal this path in Magisk:
https://github.com/kdrag0n/safetynet-fix/releases/download/v1.1.0/safetynet-fix-v1.1.0.zip