Help me root :) - Nexus One General

What do I do wrong? - using this guide: http://forum.xda-developers.com/showthread.php?t=612858
My bootloader is unlocked.
Settings -> applications -> unknown sources enabled
- recovery-RA-nexus-v1.6.2.img is in my tool folder
- nexus-addon-0.1-signed.zip is on my sdcard
SHIFT + rightclick and open CMD from the tool folder.
Run two commands:
fastboot devices
fastboot flash recovery recovery-RA-nexus-v1.6.2.img
Go into bootloader and choose recovery - and I get a triangle with an android every time.
What do I do wrong?

try this:
1) fastboot boot recovery recovery-RA-nexus-v1.6.2.img, you're trying to force RA to run without actually having it "flashed".
2) once RA is up and running, use RA to flash the root image
3) your phone is now rooted
4) reboot
5) Test to see if it's rooted by downloading the N1 torch or something
6) Once root is confirmed, reboot into fastboot again
7) fastboot flash recovery recovery-RA-nexus-v1.6.2.img
I had the same issue as you. The problem is that the RA recovery doesn't flash because the phone is not rooted. However, you need RA running in order to flash the root image. So here we're going to load RA without having it flashed, then use it to root, then flash RA afterwards.

Related

help with cyanogen Rom upgrade from 5.0.7 to 6.0.0

I have a rooted mytouch original with cyanogen 5.0.7/android 2.1 and want to upgrade to cyanogen 6.0.0/android 2.2.
Can I just install the new rom, or are their prior steps to prepare for this.
Thanks
DAve
Check CM wiki.. all the info is there!
yes, I had already read through the cm wiki before posting. I just read through it a second time, though the specific question that I had asked was not addressed as far as I could tell. Don't want to flash a new rom without first knowing its the right step to take. So if someone doesn't mind answering the question...
Just do a nandroid backup. Then you flash the CM 6 over the old one, do a cache+dalvic wipe and start it up.... It should be ok.
If not, then just revert back with the knowledge that you have to do a complete wipe, meaning that you need to start from scratch.
I now have initiated flashing new rom, starting with backing up data and wiping cash. However, I am now unable to go into recovery mode, whereas the phone is stuck on the logo when attempting to do so. I had installed through rom manager clockworkmod 2.5.0.1, got the message it installed correctly.
Here are the methods I have used to go into recovery:
1. click on "reboot into recovery"
2. backup current rom
3. flash alternative recovery with RA Recovery v.1.7.OH downloaded by rom manager, and use rom manager to restart into recovery mode
4. turn phone off, try to press home and power button together, for the new RA and the new clock work mod programs.
will not go into recovery mode, gets stuck on the boot up logo. Phone otherwise works fine, on the older Cyanogen Rom..., just can't go into recovery mode which I need to do to upgrade.
My original recovery was RAv1.2.0G.img, but this was I assume replaced by the rom manager.
In case this is important, my other software versions I have been using the past year:
Hboot 1.33.2005 (sapp30000), Cpld 10, Radio 2.22.19.261
will not go into recovery mode, gets stuck on the boot up logo. Phone otherwise works fine, on the older Cyanogen Rom...
any suggestions?
You flashed wrong recovery version...
You need RA Recovery v.1.7.OG and not H as stated above.
If all ****s up, then use my guide (check my signature) to flash a custom recovery... just skip the steps about root since you already got that!
Remember, G and NOT H.
lost recovery
mumilover
I do actually have v.1.7.0G installed, not H (my bad).
it just will not go into recovery.
Please let me know where your guide is, but right now I have been unable to communicate with my device through my xp desktop, get the "device not found" error (I assume you are suggesting that). Not sure how this will help though, since I already seem to have the correct recovery image installed.
Any help you can offer would be appreciated.
Dave
mumilover said:
You flashed wrong recovery version...
You need RA Recovery v.1.7.OG and not H as stated above.
If all ****s up, then use my guide (check my signature) to flash a custom recovery... just skip the steps about root since you already got that!
Remember, G and NOT H.
Click to expand...
Click to collapse
Download my fastboot commander (CHECK MY SIGNATURE, magic version).
Restart into fastboot mode.
Download this recovery image:
http://rapidshare.com/files/387932919/recovery-RA-sapphire-v1.7.0G.img
Using the tool and your eng spl, you can just flash the recovery image on the phone.
Just use the first tab -> recovery button -> navigate to the above image -> click "flash recovery". Done.
Restart into recovery by home + power combo.
You could also try this command:
Code:
adb shell reboot recovery
to force it to boot into recovery from the system.
[Problem is fixed. Thanks for your help.
I used my mac bootcamp (could not get sdk to run on my desktop or mac), and could find my device through adb. Then I pushed a separate version of the RA 1.7.0 G (the one the came with rom manager did not work!) to my phone via flash command. Voila, I am now able to go into recovery mode. 6.0 is installed and running.
QUOTE=mumilover;10252460]Download my fastboot commander (CHECK MY SIGNATURE, magic version).
Restart into fastboot mode.
Download this recovery image:
http://rapidshare.com/files/387932919/recovery-RA-sapphire-v1.7.0G.img
Using the tool and your eng spl, you can just flash the recovery image on the phone.
Just use the first tab -> recovery button -> navigate to the above image -> click "flash recovery". Done.
Restart into recovery by home + power combo.
You could also try this command:
Code:
adb shell reboot recovery
to force it to boot into recovery from the system.[/QUOTE]

[Q] Problems flashing recovery

I've achieved permroot via the tutorial and am using a mac, but so far have not been able to flash a recovery to be able to do ROMs. Whenever I do the fastboot command
./fastboot flash recovery recovery.img
< waiting for device >
I get that, and it does nothing. Any ideas what's going wrong?
Have you set your phone to Fastboot mode? You have to select fastboot from the bootloader, just a guess
Did you place the recovery image in the sdk tools folder?
powered by the tears of a million orphaned alpacas...
Yep it's in the proper folder. Putting the phone in fastboot mode? I haven't heard of that. It is plugged in with USB debug on. I leave it on the main screen.
If you're following bcnice's instructions and you hopefully have the fastboot.exe in a folder you put into your Windows path (AdroidSDK\platform-tools)
You just cd to the directory where the recovery.img is (on the PC) power your phone off, turn on while holding volume down (bootloader) select fastboot (I believe is says something like fastboot-usb when it's ready, then just type in the command:
fastboot flash recovery recovery.img
you will see the transfer happen then you boot into recovery (on the phone) and if you got it right it will now be a black background with green font
go to backup/recovery, select recovery, there's your Nandroid!
I just did this today so I feel your pain but I've already flashed a new ROM and the OC'd kernel so I'm sure you can get the hang of it. Fun fun fun.
Edit: Sorry, didn't see you were using a mac... I have no experience with those. It may be in your best interest to have the recovery.img in the same folder your fastboot.exe is
You know you don't have to fastboot to do recovery..you can just push the files
Sent from my PG06100 using XDA App
Or...
1) Download the recovery you want (either CW 2.5 or CW 3.0).
2) Download Rom Manager from the Market.
3) Flash Clockwork Recovery from the Rom Manager main menu. (Make sure you select HTC EVO CDMA).
4) Open File Explorer, go to ClockworkMod/download/mirror1.kanged.net/recoveries and rename the recovery file to "recovery-clockwork-3.0.0.5-supersonic1.img.
5) Move the recovery file that YOU want into this folder, and rename it to "recovery-clockwork-3.0.0.5-supersonic.img.
6) Open Rom Manager and Flash Alternate Recovery.
7) Flash ClockworkMod Recovery (select HTC EVO CDMA again), and it will flash the correct recovery image compatible w/ our EVO Shift.
This set up works w/ any of our recoveries out now or going forward. Simply rename the file each time. Hopefully ClockworkMod will add our recovery to the base soon and we won't have to go through this step, but for now, this is an alternate way to flash recovery for those of you not wishing to use Fastboot, and want to do things directly from your phone.

[HOW TO] Revert to latest stock ROM (GRI40)

I personally have tried lots of ROM's but all I really want is the stock ROM with the option to root if I want. After lots of research, I couldn't find a comprehensive tutorial on how to do this. There is of course the GRI40 image available in update.zip format for custom recoveries which is helpful for most. However, if your a bit anal like me, and want the official update directly from Google servers, follow this guide. This might also be helpful for people who can't get into the custom recovery any more.
NOTE: I will not provide help for anybody. This guide assumes you have the Android SDK in order to use adb. There may be other ways of doing this, I am not an experienced programmer, this works for me, it will work for you.
[GUIDE]
Download the following files:
Stock Froyo Image (Contains stock recovery image)
Stock GRI40 Image
Instructions
You first have to revert to stock Froyo image to get the stock recovery back. This is needed to install the GRI40 update ZIP
1. Disable backup my settings under privacy settings.
2. Unzip the original Froyo shipping ROM and put it somewhere you can find
3. Plug in Nexus One with USB to computer (enable USB Debugging)
4. Open command prompt, navigate to SDK folder which contains adb. Type
Code:
adb reboot bootloader
(which will boot into the bootloader)
5. Confirm fastboot connection with
Code:
fastboot devices
6. Type
Code:
fastboot erase userdata
7. Type
Code:
fastboot erase cache
*If step 6 and 7 does not work, and if you have a custom recovery installed, you can do a factory data wipe from there. Also perform a dalvik-cache wipe.
Alternately, you can also do a factory data wipe within Android. Settings => Privacy Settings => Factory Data Reset.
8. Go to the directory that you stored your unzipped files from the official Froyo ROM, for ease of use, copy these into the directory containing adb.exe
9. Type
Code:
fastboot flash userdata userdata.img
10. Type
Code:
fastboot flash boot boot.img
11. Type
Code:
fastboot flash system system.img
12. Type
Code:
fastboot flash recovery recovery.img
13. Type
Code:
fastboot reboot
14. Once phone has started, skip all account setup. Copy the new GRI40 .zip from Google servers to the root of your SD card. Ensure it has been renamed to update.zip if necessary.
15. Reboot into bootloader mode (hold trackball when switching on), select recovery, you will see an exclamation mark with a little green Android.
16. Hold power button and press Vol. Up to see recovery menu. Select 'Apply: Update.zip'
17. After the system boots up and while setting up skip setting up with the google account and you can setup accounts later. This will prevent the phone from pulling down the previous settings (downloaded apps, wallpaper etc) from google.
18. You are done. Enjoy.
If you want to root:
Download the following:
Latest Clockworkmod Recovery
su.zip
Instructions
How to root the stock ROM
1. Download su.zip and copy to root of your SD card
2. Download a recovery image file and for ease of use, copy into same directory containing fastboot on your PC
3. Turn on USB debugging and connect phone to PC
4. Open command prompt, navigate to SDK folder which contains adb. Type
Code:
adb reboot bootloader
(which will boot into the bootloader)
5. Type
Code:
fastboot flash recovery recovery.img
where 'recovery.img' is the name of your recovery image file (easy thing to do is rename the file to 'recovery.img'!)
6. It will upload, once complete, disconnect you phone from computer
7. On your phone, select Bootloader, then Recovery to boot into your new recovery
8. Now select ‘Apply Update.zip’ and find the su.zip file (Turn off signature verification if using Amon RA)
Note:Custom recovery will be overwritten with the stock recovery on reboot but root privelages will still be in place.
No need to do that. Flash the stock rom. Done.
Sent from my Nexus One using XDA App
albundy2010 said:
No need to do that. Flash the stock rom. Done.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
You mean you can flash the official GRI40 zip from Google server with a custom recovery?
Iggy82 said:
You mean you can flash the official GRI40 zip from Google server with a custom recovery?
Click to expand...
Click to collapse
Yes!
Make sure it's the full image (80+meg), and not just the update (40+ meg). Recovery should restore to stock after a reboot...
Sent from my Nexus One using XDA Premium App
Well that serves me right for assuming Google would not allow an official update zip to install from a custom recovery!
Did the official update ZIP from Google come out after dsixda made his own update zip then?
The link above is for the full update zip from Google (80MB or so)
Sent from my Nexus One using Tapatalk
usually the official updates come out and people edit them to allow root, busybox, etc.
or just a stock rom that won't over write your custom recovery, etc.
Thanks for this. I have been looking for a stock image all morning!

OEM Unlock works,unfortunately we do not have a REC

I am using LG X-Cam K580DS( Dual SIM )
'abd reboot bootloader' works, the phone did boot into fastboot
'fastboot oem unlock' works, you'll wipe your phone by doing so
unfortunately we do not have any Recovery like CWM or TWRP, so I have no way to flash a superSU, anyone have any idea?
Yes ...
use any guide or tool for porting recoveries ..first download .kdz & extract stock recovery ..use tool to port a twrp for your device ..
Put latest magisk zip on SD card
On device
/settings/about
-enable developer options by clicking on build number
-enable adb
-uncheck verify apps by USB
-allow unknown sources
-authorize PC connection
then using adb
adb reboot bootloader
PUT PORTED RECOVERY INTO FASTBOOT/ADB FOLDER
fastboot boot recovery (name of recovery).IMG
I use :
fastboot boot recovery recovery.img
*if & when recovery boots
-swipe to allow changes
- REBOOT SYSTEM
*IGNORE CORRUPTED DEVICE MESSAGE
-boot recovery again using fastboot
-swipe to allow changes
-in fastboot flash latest magisk .zip
-reboot system & and you will have "systemless" root without custom recovery
*Hints ..look for device with similar specs and see if the recovery will boot so port won't be necessary
*DO NOT FLASH RECOVERY IMG BECAUSE LITTLE KERNEL WILL PREVENT DEVICE FROM BOOTING
*DO NOT USE SUPERSU SYSYEM DEVICE WON'T
BOOT
*COPY .ZIP TO DECOMPRESS FILE SYSYEM IF YOU WANT TO SUPERSU SYSTEMLESS OR WON'T BOOT
*CHECK OUT lg k8 thread by Gottlaz for tips on twrp porting & experience....
Good luck bro

Need help fixing my bricked phone

Hey Guys,
I have a redmi 3s prime and i tried to install lineage os on it, during the process i accidentaly flashed twrp over both the recovery and the boot. Now i cannot get into the recovery (and fastboot) unless i flash it over boot before rebooting my phone. After that i AM able to flash an new rom but it seems to always have wifi issues.
atm i am trying to flash the xiaomi developers global rom to see if it makes any difference. My main goal is to flash TWRP and a curstom rom (linage or resurrectionremix).
Can anyone help me?
Thanks alot!
Update #1
The flashing of the global developer rom worked and the wifi seems to work aswell, i will try to boot into fastboot and recovery.
Update #2
Its seems i am able to boot into fastboot and recovery again
Update #3
Following a tutorial for flashing TWRP and a custom rom but cant se2 anyone help me here?:
Code:
>>> Check then next step to root :
- launch minimal adb tool (previously installed)
- type : adb devices (to list phone connected) it will appear "unauthorized"
- on the phone : accept the computer
- re type : adb devices
it has changed in "authorized"
- type : adb reboot bootloader
it will go in fastboot mode (the same that power + vol down)
- type : fastboot devices
your phone will appear as in adb mode (unless the bad signed driver is choosen in win10 ; i won't repeat it again)
- type (optional) : fastboot oem device-info (to verify if bootloader is locked or unlocked)
now, we go to root
- type : fastboot boot twrp.img (if it is your renamed twrp copied in the minimal adb folder)
link for TWRP guide at the end if needed
!!! it will boot temporary in this recovery but it will keep your original recovery !!!
> allow to modify system (don't keep the "read only" if you want to root or flash recovery later)
go to settings to set date, hours, language, set custom options...
My optional advices :
- save your EFS & persist partitions or all whole partitions (except cache) to make a backup
- export this backup in computer or SD card in case of future problem
(EFS, persist are usefull to save and restore your IMEI in particular)
- you can flash directly TWRP with fastboot command : fastboot flash recovery twrp.img
>>> Root :
Now flash DM-verity patch, then superSU.zip to root and accept to wipe dalvik/cache after, finally reboot !
Device is rooted ! and you have kept the original recovery.
the reboot is quite long like rom update (because of cache rebuild)
sometimes, parts of theme are lost after rooting : just restore your theme
some devices don't need DM-verity patch as explained upper
superSU app shows "systemless root" from android 6+, it is normal, read below
>>> Change the Recovery by TWRP (optional) :
Now you are rooted, you have 2 methods :
- Install one TWRP app with googleplay and flash recovery through app on rooted device.
New official app in development (flash/backup .img & .tar)
- OR reboot in fastboot mode (with TWRP app method or power+vol- method or adb reboot recovery method)
in fastboot mode, and type commands :
fastboot devices
fastboot flash recovery twrp.img
(be sure your twrp.img is unlocked and correctly copied/renamed in minimal adb folder)
Now, long press power to turn OFF phone
power + vol+ (release power at vibration) to enter in TWRP or by TWRP app or Updater app or under Windows with minimal adb reboot recovery command
Note for devices with DM-verity : flashing TWRP needs to have patched system with DM-verity patch before because you will modify system most of time - generally, you don't need to patch again because you have ever done it in previous steps - in case of bootloop : go to fastboot mode, boot in TWRP with command and patch it.
Chainfire has recently modified superSU for android 6+ devices with DM-verity to install root without modify the system : it's called "systemless root". When you flash superSU.zip, it detects automatically android version, cleans old files and installs with appropriate method. Maybe no need to patch boot in this case with DM patch.

Categories

Resources