I just traded up from an iPhone 3G to a Europe model Nexus One and am considering rooting for unrestricted access to the App Market (I am using in China), but I wanted to make sure that I've got all my facts straight about the rooting process. My bootloader is unlocked and I have flashed upgrade packages manually before, but everything else appears to be stock.
So first, root access actually only involves installing the Superboot update over the stock ROM, if there is a superboot for that ROM version, right?
This then lets you install apps that require root access (such as Market Enabler or MarketAccess), so if I just wanted unrestricted market access, then this is all that I would have to do, right?
However, getting root also lets me install a custom recovery, which gives me some nifty functions from the recovery boot, such as backing up my phone (does it do anything else? Why does Amon_RA's recovery have Busybox if it already comes with superboot?). It also allows me to install a custom ROM.
So far so good? Am I missing anything?
Are there any other methods to root? I have heard that you can install the SDK and go through ADB to manually do root, but I have not found any detailed information about this method. I have FRF91 OTA, and since there is no superboot for that yet, could I potentially got the ADB route?
Didn't miss anything.
You can go several ways: since your bootloader is unlocked, to save yourself the pain with ADB loop method, which is completely unneeded, you can just use the regular method, skipping the "unlock bootloader" part, which leaves you with "flash custom recovery" part (totally independent) and then just flash whatever ROM you like, pre-rooted. You don't need to flash a rooting file over your ROM, you just can change your ROM to pre-rooted one.
So you are saying that I can flash a custom recovery, then load a custom rom that is pre-rooted?
How do I flash a custom recovery if I am not rooted? I thought that in order to get the recovery you needed to root via superboot?
And I must have a custom recovery in order to have a pre-rooted rom, otherwise the phone will reject the package, right?
So the only thing that prevents root on the Android is the rom and recovery partition's own integrity check for whatever you are flashing? In other words, people can lose root by flashing a stock rom, and you can get root by flashing a pre-rooted rom. I seem to remember seeing some pre-rooted packages saying that you must have previously had root in order for it to work. Is that not correct, then?
Thanks.
hgcrpd said:
I just traded up from an iPhone 3G to a Europe model Nexus One and am considering rooting for unrestricted access to the App Market (I am using in China), but I wanted to make sure that I've got all my facts straight about the rooting process. My bootloader is unlocked and I have flashed upgrade packages manually before, but everything else appears to be stock.
So first, root access actually only involves installing the Superboot update over the stock ROM, if there is a superboot for that ROM version, right?
Click to expand...
Click to collapse
Not exactly - root access simply indicates having the su and superuser.apk binaries installed, and the suid bit set on su. But you are close enough. If you are running FroYo, Cyanogen and Lox have published flashable rooters.
You will already need a custom recovery to flash either of these - but since your bootloader is unlocked, a custom recovery does not pose any problem - see below...
hgcrpd said:
This then lets you install apps that require root access (such as Market Enabler or MarketAccess), so if I just wanted unrestricted market access, then this is all that I would have to do, right?
Click to expand...
Click to collapse
Yes.
hgcrpd said:
However, getting root also lets me install a custom recovery, which gives me some nifty functions from the recovery boot, such as backing up my phone (does it do anything else? Why does Amon_RA's recovery have Busybox if it already comes with superboot?). It also allows me to install a custom ROM.
Click to expand...
Click to collapse
Couple of points here:
1. No, you don't need root to install a custom recovery - you need an unlocked bootloader. In fact, you have reversed them - you usually need a custom recovery to get root! Since you have that bootloader already unlocked, you can go ahead and install Amon's recovery (or another one) and get what you need to get.
2. Recovery does not use the same shell and variables as /system. Busybox is usually installed in recovery to allow you to run things via ADB or scripts when in recovery mode without manually calling them off of system (something that would be a problem if you were formatting and rewriting system, for example).
hgcrpd said:
Are there any other methods to root? I have heard that you can install the SDK and go through ADB to manually do root, but I have not found any detailed information about this method. I have FRF91 OTA, and since there is no superboot for that yet, could I potentially got the ADB route?
Click to expand...
Click to collapse
You need to have the SDK installed (which includes adb) to unlock the bootloader in any case, right? Or did someone unlock the bootloader for you? In any case, I would just install the SDK - it's free, fast and gives you access to fastboot and adb. You need fastboot to install a custom recovery, and adb is useful for lots of things.
And there are plenty flashable root zips for FRF91. You need to first install a custom recovery!
http://forum.xda-developers.com/showthread.php?t=715799
http://forum.xda-developers.com/showthread.php?t=686627
So, if I were you:
1. Install the Android SDK on your computer to get ADB, fastboot and the necessary drivers.
2. Download and flash a custom recovery using fastboot.
3. Reboot into recovery.
4. Copy Lox or Cyan's rooter to your SD card using adb push.
5. On the phone, in recovery, do a nandroid backup!
6. Flash the zip from step 4.
7. Reboot your phone and confirm that you have root - the easiest way is to start up a terminal session and type "su". The Superuser authorization program should pop up and ask you to approve the application's request for root access. Grant it. If the prompt turns from "$" to "#", you have root.
1. No, you don't need root to install a custom recovery - you need an unlocked bootloader. In fact, you have reversed them - you usually need a custom recovery to get root! Since you have that bootloader already unlocked, you can go ahead and install Amon's recovery (or another one) and get what you need to get.
Click to expand...
Click to collapse
I see. So the post on modaco is not quite correct when it says that root is a pre-req for Amon_RA's recovery. I'm guessing that's only a pre-req if you flash via a terminal session on the phone? (By the way, is there an official terminal app? The only one I could find was Terminal Emulator.)
You need to have the SDK installed (which includes adb) to unlock the bootloader in any case, right? Or did someone unlock the bootloader for you?
Click to expand...
Click to collapse
Bootloader was unlocked when I bought it. The phone is a grey-market item that I purchased here in China, and every grey-market phone that comes in gets modified by the importers in order to add Chinese language support and such. I think that's all they did, since I've been able to do updates and get OTA without a problem.
Thanks! I will give the SDK route a try, if I get time before the superboot for FRF91 comes out.
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
hi there every one i updated my nexus one to 2.3.6 (GRK39F) from stock 2.3.4 (GRJ22) sorry but i did not read the post for to upgrade and keep root before upgrading to 2.3.6 and now i am suffering and thought it is not a good idea to post a question there so posting here
my problem is when i upgraded 2.3.6 i was rooted and had clockworkmod recovery image and i had a backup from rom manager as well but before upgrade i wiped the partition and cache and after upgrade i dont have SUPER USER permission nor the clockworkmod recovery tried to flash su.zip from sd card but no luck please can anyone help me get my root back pleaseeeee i need help ....
You'll have to passimg back to an earlier version of Froyo, root, restore your backup, and then flash the update and su zip...
danger-rat said:
You'll have to passimg back to an earlier version of Froyo, root, restore your backup, and then flash the update and su zip...
Click to expand...
Click to collapse
Thankyou very much danger-rat really appriciate your help but today was a bit lucky day for me
I tried to flash a recovery image through ADB and then it went well and then flashed the su.zip from sdcard that gave me superuser permission again thanks again for your help
@0mpranav
No need to flash the system partition, no need to use ADB, just flash Superboot:
Code:
https://bexton.net/2011/09/24/root-access-for-nexus-one-on-android-2-3-6-grk39f-superboot/
If your bootloader is unlocked all you have to do is reboot into fastboot mode. Flash a custom recovery such as RA or CWM, reboot directly into revovery and flash su.zip or whatever flash zip you used to root your device before. Reboot and you are rooted once again.
The following thread has a step by step how to do it. It's fast and easy.
http://forum.xda-developers.com/showthread.php?t=1019759
jboxer said:
If your bootloader is unlocked all you have to do is reboot into fastboot mode. Flash a custom recovery such as RA or CWM, reboot directly into revovery and flash su.zip or whatever flash zip you used to root your device before. Reboot and you are rooted once again.
The following thread has a step by step how to do it. It's fast and easy.
http://forum.xda-developers.com/showthread.php?t=1019759
Click to expand...
Click to collapse
Yup. This is the way every one should be doing it. It's sort of the whole point of the Nexus One. It has an unlockable bootloader.
GldRush98 said:
Yup. This is the way every one should be doing it. It's sort of the whole point of the Nexus One. It has an unlockable bootloader.
Click to expand...
Click to collapse
I have purchased two second hand Nexus Ones. The first thing I did after receiving them and charging the battery was to reboot into fastboot mode and issue "fastboot oem unlock" command. Since they were purchased second hadn I didn't thing I had a warranty anyway so unlocking the bootloader seemed to be a non brainer.
GldRush98 said:
Yup. This is the way every one should be doing it. It's sort of the whole point of the Nexus One. It has an unlockable bootloader.
Click to expand...
Click to collapse
Will any version of su.zip, and fastbook.zip work? What about recovery-RA-passion-v2.2.1.img? or should we be using a different version?
If we should be using different versions of those, could you link to where we could get them?
I've had my Nexus one half-rooted since 2.3 came out, and I haven't been able to root it back.
why mess with 2.3.6 just use oxygen 2.3.7...
kuljit55 said:
why mess with 2.3.6 just use oxygen 2.3.7...
Click to expand...
Click to collapse
I'm sorry I have no idea what that is. I don't even know if its helpful at all. Again, I don't even have root, or a custom recovery. Presently, I have an unlocked bootloader, ADB on my PC, and a half-rooted nexus one from before 2.3.
I have absolutely no idea how to do anything presently, and when someone tells me that trying to root on 2.3.6 is futile and to just use a custom update, it doesn't make any more sense to me.
Care to elaborate past one line that doesn't help at all? Hell when using shell commands through adb, it keeps on saying "permission denied" any time I type in su.
You have an unlocked bootloader, so flash a custom recovery via fastboot, and use the custom recovery to flash the su zip...
danger-rat said:
You have an unlocked bootloader, so flash a custom recovery via fastboot, and use the custom recovery to flash the su zip...
Click to expand...
Click to collapse
Thanks Danger-rat. Although I know you said nothing different that what was already said in this thread, I figured that since you didn't give me specific info about whether or not there were multiple versions of su.zip or fastboot.zip, I figured I should take that as a "No.", so I went for it. All re-rooted now.
I appreciate the help.
EDIT: So if you are as new to this stuff as I am, anyone else who's reading-
You can DL su.zip from http://www.google.com/url?sa=t&sour...ZxOuf9Kw_URvtvh9Q&sig2=Hj72LDNoiBq2Zoa4QquZWQ
and fastboot.zip from http://www.mediafire.com/?ttdkgamud3j
and amon Ra 2.2.1 from http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-passion-v2.2.1.img
then follow the directions here: http://forum.xda-developers.com/showthread.php?t=1019759
** Note: again, these are for people who have unlocked bootloaders. For that info, you'll have to go elsewhere, but it should be readily available, such as this stuff is. I'm just linking it again because I know how frustrating it can be for people like me who aren't too well versed in rooting/unlocking yet.
Downgrade 2.3.6 to 2.2.2 - Nexus One
Problem:
I would like to downgrade my Nexus One to 2.2.2, because I've had non-stop problems with Gingerbread.
So I've gone through the Bootloader -> Recovery -> apply sdcard:update.zip steps, and it fails. This begs the question, how do I go from 2.3.6 to 2.2.2?
Fix:
Generally, phone manufacturers will not allow you to downgrade for various reasons. The stock recovery does indeed validate the update image, so that it's of a greater (or same) version than the installed system. With the Nexus One being a developer phone, you can unlock the bootloader and replace the recovery image with the one that doesn't perform this check, and will allow installation of any image. The caveat is that unlocking the bootloader voids your warranty with the carrier (and sometimes the manufacturer too,) and wipes all user data off the device.
Unlocking the N1 is dead easy. Just install Android SDK and the USB drivers (located in "google-usb_driver" directory.) Then restart the phone in bootloader mode by shutting it off and powering on while holding down the trackball, hook it up to the computer via USB, and in command prompt issue the following command: C:\<path to Android SDK>\tools\fastboot oem unlock. You will be presented with a confirmation screen with further instructions. Upon successful unlock, you can flash a custom recovery that will allow you to install any custom ROM, including downgrade to 2.2.x stock version of Android OS.
To flash ClockworkMod recovery, download the latest version for Nexus One from here, reboot into bootloader mode (power on while holding the trackball down,) and in command prompt issue command C:\<path to ANdroid SDK>\tools\fastboot flash recovery C:\<path to downloaded img>\recovery-clockwork-3.0.0.5-passion.img
Reboot to bootloader mode again, and then use the Volume keys to highlight the "Recovery" option and press Power button. You are now in ClockworkMod recovery, and can flash any custom ROMs via the "Install zip from sdcard" option.
Here is a "stock" 2.2.2 ROM (with root) off XDA-developers forum.
http://forum.xda-developers.com/showthread.php?t=927935
source:http://android.stackexchange.com/questions/13933/downgrade-2-3-6-to-2-2-2-nexus-one
Try It & Report Back...
I have an htc One running on the Reliance Network. Versions 4.1.2 / 1.29.651.10
It is Bootloader Unlocked with TWRP 2.6.0.1 and root
I have downloaded the mouthful OTA_M7_WL_JB_50_SPCS_Sprint_WWE_1.31.651.2-1.29.651.10_release_326731tcfazf1gnytc7g74.zipOTA_M7_WL_JB_50_SPCS_Sprint_WWE_1.31.651.2
-1.29.651.10_release_326731
When I try to flash it using TWRP it bombs out as there is no MD5 file.
I have two queries:
1. How do I update the TWRP to 2.6.3.0?
2. How do I install the update.
I prefer to use the fastboot method?
I have downloaded the update to my PC since aborting deletes the file. Also, I have the TWRP on my PC.
Please advise and help.
Check PM
sgiitk said:
I have an htc One running on the Reliance Network. Versions 4.1.2 / 1.29.651.10
It is Bootloader Unlocked with TWRP 2.6.0.1 and root
I have downloaded the mouthful OTA_M7_WL_JB_50_SPCS_Sprint_WWE_1.31.651.2-1.29.651.10_release_326731tcfazf1gnytc7g74.zipOTA_M7_WL_JB_50_SPCS_Sprint_WWE_1.31.651.2
-1.29.651.10_release_326731
When I try to flash it using TWRP it bombs out as there is no MD5 file.
I have two queries:
1. How do I update the TWRP to 2.6.3.0?
2. How do I install the update.
I prefer to use the fastboot method?
I have downloaded the update to my PC since aborting deletes the file. Also, I have the TWRP on my PC.
Please advise and help.
Click to expand...
Click to collapse
You cannot upgrade when your phone is rooted(i got to know from hetaldp)
I upgraded to JB 4.3, it awesome. Touch is Excellent. i too use relaince. there are no issues.
BUT remember you cannot root again, as over i am facing problems,,,
check : http://forum.xda-developers.com/showthread.php?t=2494594
So Please kindly wait, till the root for hTC ONE for upgraded JB 4.3 one Comes...
Are you using Sprint or T-Moile or Version HTC ONE?
To get upgrade installed, please un-root, relock, and then you can perform the update...
[email protected] said:
You cannot upgrade when your phone is rooted(i got to know from hetaldp)
I upgraded to JB 4.3, it awesome. Touch is Excellent. i too use relaince. there are no issues.
So Please kindly wait, till the root for hTC ONE for upgraded JB 4.3 one Comes...
Are you using Sprint or T-Moile or Version HTC ONE?
To get upgrade installed, please un-root, relock, and then you can perform the update...
Click to expand...
Click to collapse
It is Sprint, and from Hetal. Unrooting and relocking can be a pain, reloading everything. However, for almost two years I did not do any work on the Android side, so have forgotten everything.
I do not mind a locked phone it I can get to 4.3
Can you please pm me with the unrooting, relocking and the 4.3! Root for 4.3 is inevitable - just a matter of time.
Following the GooManager route I managed to get TWRP 2.6.3.0 installed, except the phone did not reboot. I did check it is 2.6.3.0.
Now the problem of the OTA remains. Maybe I will be forced to follow pm.mohanani's route of relocking. I cannot understand if I relock the bootloader then is not the unrooting automatic!
Also, Mr Mohanani GooManager requires root, so do not bother.
Managed to upgrade to 4.3 using Sprint_HTC_One_m7wls_3_04_651_2_RUU from Android Central as suggested by Hetal. I had to do a <fastbook oem lock> first. No problems except it wiped the data totally. Working fine. I have a few points / questions
1. Booting into Recovery is showing the Red Exclamation in a Triangle. Obviously not working, as in rooted!!
2. The Boot into recovery is showing both [RELOCKED] and S-off.
- Is this the cause?
- As per Hetal S-off means that I can root straight away irrespective of the Relocked status
- I guess OTA to KitKat (when it comes) is also a no go.
- What recovery is suggested TWRP 2.6.3, CWM (version?), or some other. This means that 4.4 will again be a full reload.
- Any fixes?
sgiitk said:
Managed to upgrade to 4.3 using Sprint_HTC_One_m7wls_3_04_651_2_RUU from Android Central as suggested by Hetal. I had to do a <fastbook oem lock> first. No problems except it wiped the data totally. Working fine. I have a few points / questions
1. Booting into Recovery is showing the Red Exclamation in a Triangle. Obviously not working, as in rooted!!
2. The Boot into recovery is showing both [RELOCKED] and S-off.
- Is this the cause?
- As per Hetal S-off means that I can root straight away irrespective of the Relocked status
- I guess OTA to KitKat (when it comes) is also a no go.
- What recovery is suggested TWRP 2.6.3, CWM (version?), or some other. This means that 4.4 will again be a full reload.
- Any fixes?
Click to expand...
Click to collapse
There is no need to accept the OTA if you are s-off
bigdaddy619 said:
There is no need to accept the OTA if you are s-off
Click to expand...
Click to collapse
Thanks. So I will again wait for the 4.4 RUU to be available on XDA or somewhere, and then install and forget OTA.
The point is recovery. I presume with S-off custom recovery must to be installed.
Do I install TWRP which takes care of root or do you suggest some other route, ie, root (how?) > recovery.
sgiitk said:
Thanks. So I will again wait for the 4.4 RUU to be available on XDA or somewhere, and then install and forget OTA.
The point is recovery. I presume with S-off custom recovery must to be installed.
Do I install TWRP which takes care of root or do you suggest some other route, ie, root (how?) > recovery.
Click to expand...
Click to collapse
Install TWRP 2.6.3.0
Option 1 flash SuperSU or another superuser file and run stock rooted
Option 2 flash a custom rom
Still stuck. I downloaded GooManager, and it will go into download > nowstarting and hang forever. I was advised to go the adb fastboot way, i.e.
download latestTWRP image filethen
adb reboot bootloader
then when I get
ui fstboot
fastboot flash recovery <twrp-recovery-name.img>
and its done.
I downloaded the .img file. Put everything into c:\recovery. Moved there under the command prompt. Plugged the phone into the computer, got both the drives (htc sync manager, and HTCONE) . So the connection was kosher.
Then gave adb reboot bootloader
The adb daemon started, but it found no device.
Obviously I being a noob in this game was missing something.
Also, I hear that the ROMs are available which to not reformat the storage. Are these the Deodexed versions or something.
Also, once in ten calls or so the screen goes totally blank at the end and is pain to restart the phone.
Checked up with http://forum.xda-developers.com/showthread.php?t=2497712
Seems that I am S-off but no rooted! Now what??
After a day or so and some cool thought I think I may have the problem identified. It is likely to be the lack of a root. I tried the following and the responses there from:
adb reboot bootloader
rebooted into bootloader Showing relocked and S-off. No fastboot option in the lower menu!
Now:
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
I get
sending recovery <8600kB>...
Okay [ 1.140s]
writing 'recovery'...
FAILED <remote not allowed>
finished. total time 1.170s
Any ideas, and when may I expect root for 4.3. At the moment the phone appears to be working file, but no recovery!! HELP!!
Do I need to unlock again despite S-off. Also, then what is the bitstream I send it from 4.3 - the same as the old one!!
Yes you need to unlock your bootloader again to be able to flash twrp
I did as per the htc route - Do the unlock, reinstalled the OS, download the bitstream, etc, and then the OS reloaded. Still Goomanager could not get TWRP 2.6.3.0 so used the fastboot route and succeeded in downloading it to the phone. Thanks for encouraging me and putting me on the right track.
Now ho to root. Then I may as well get Titanium up!
You can get SuperSU or Superuser from the playstore or install a custom rom.
A very interesting experience. I could not enter bootloader [Down-vol + power was just restarting the phone], even adb devices was drawing a blank. So I decided to do a factory reset from phone. Lo and behold it dropped me into the TWRP screen. I managed to root, restarted to the main Downloaded su checker which completed the root. Confirmed. Then downloaded Titanium with Pro license (I have it) and did a recovery. Also, TWRP Manager (downloaded) is working and I am able to start into bootloader, etc.
When I try and look for upgrades with TWRP installer it says none. I know 2.6.3.0 has been upgraded to 2.6.3.2 Let sleeping dogs lie.
Also, I have not checked with adb devices but I am sure that too will now work.
Thanks, but what is going on. Is it only God and maybe Google know what happened?
Thanks for helping, and keeping me going.
I had more or less decided to revert to 4.1 and do an S-on <fastboot oem writesecureflag 3> and bootloader lock and look for OTA!
Added on 25th November
adb still not recognising the beast. adb devices gets a blank list. Phone is available under Windows so drivers etc are Ok.
A noob question. I saw
Stock Rooted 3.04.651.2 Odex & De-Odexed
Insecure Boot img. init.d support, data/app support
Stock Rooted 3.04.651.2 Odex
Stock Rooted 3.04.651.2 De-Odexed
on the upgrade thread. Now what do the terms Rootedm Odex and De-Odexed mean to the average user. Stock means the basic htc ROM I presume.
Also, rooted means what stages are covered.
afaik to upgrade you lock the bootloader, do the upgrade, and then in normal situations again unlock the bootloader, root and install a custom recovery (TWRP does the rooting - hopefully).
Do these ROMs take care of some or more of these stages?
Having an issue with the unified rooting tool (http://forum.xda-developers.com/nexus-6/orig-development/toolkit-skipsoft-unified-android-t2967053). Paid for the pro version because i enjoy supporting quality work.
Went to do the all-in-one unlock/recovery/root, however it's not rooting for me. The final step of rooting gets stuck in TWRP and nothing happens. The program says 'Recovery mode not detected' and just hangs asking me to try again, ask for help, or abort.
I have ADB and everything on and working as unified can connect to my phone, just can't get root going.
The phone is now unlocked with TWRP, but I can't achieve root. I flashed 5.0.1 via the app. Anyone have any clues?
edit: did it manually (before reading simms22's post). was hoping for lazy-automated as i paid money for the app and all.
If you have twrp installed just flash SuperSU. The newest version of SuperSU (2.37 or something I think) can be flashed like old days.
lol, learn to root a nexus the right way. its easier than using a toolkit..
1. fastboot oem unlock
2. fastboot flash yourself a recovery
3. flash the latest supersu with that new recovery
4. reboot and profit
root
So I followed a guide off of YouTube on how to root this phone. The steps were simply put use fastboot to enable oem unlocking. Use adb to push twrp. Use twrp to flash supersu walla you have rooted stock rom. I attempted this and got stuck after flashing supersu. The rom would not boot. I let it sit for 15 mins. Held the power button let it try again. Again it didn't boot. So I fiddled with it trying to figure out how to get stock rooted and wasnt able to. I could flash a stock image in twrp and it would boot. But as soon as I flashed supersu it would no longer boot. I read somewhere I needed a different supersu so I tried that one. Just asking simply how can I achieve stocked rooted. I also don't understand the encryption thing this phone has. Apparently you have to delete a partition to get rid of it but at boot it will just encrypt again. Any information on that would be greatly appreciated. Sorry for any spelling or grammar mistakes. Writing this out over my lunch break.
jakeneal22 said:
So I followed a guide off of YouTube on how to root this phone. The steps were simply put use fastboot to enable oem unlocking. Use adb to push twrp. Use twrp to flash supersu walla you have rooted stock rom. I attempted this and got stuck after flashing supersu. The rom would not boot. I let it sit for 15 mins. Held the power button let it try again. Again it didn't boot. So I fiddled with it trying to figure out how to get stock rooted and wasnt able to. I could flash a stock image in twrp and it would boot. But as soon as I flashed supersu it would no longer boot. I read somewhere I needed a different supersu so I tried that one. Just asking simply how can I achieve stocked rooted. I also don't understand the encryption thing this phone has. Apparently you have to delete a partition to get rid of it but at boot it will just encrypt again. Any information on that would be greatly appreciated. Sorry for any spelling or grammar mistakes. Writing this out over my lunch break.
Click to expand...
Click to collapse
I always use this toolkit: https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729
So far it worked flawlesly and saved me trouble.
jakeneal22 said:
So I followed a guide off of YouTube on how to root this phone. The steps were simply put use fastboot to enable oem unlocking. Use adb to push twrp. Use twrp to flash supersu walla you have rooted stock rom. I attempted this and got stuck after flashing supersu. The rom would not boot. I let it sit for 15 mins. Held the power button let it try again. Again it didn't boot. So I fiddled with it trying to figure out how to get stock rooted and wasnt able to. I could flash a stock image in twrp and it would boot. But as soon as I flashed supersu it would no longer boot. I read somewhere I needed a different supersu so I tried that one. Just asking simply how can I achieve stocked rooted. I also don't understand the encryption thing this phone has. Apparently you have to delete a partition to get rid of it but at boot it will just encrypt again. Any information on that would be greatly appreciated. Sorry for any spelling or grammar mistakes. Writing this out over my lunch break.
Click to expand...
Click to collapse
What version of supersu you installed, and on what version of system you were ?
I was on the latest official version of both as of yesterday. I will try the toolkit when I get home. With this toolkit are you able to root the new 7.1? I tried that out and liked it when attempting to get back to stock. Ultimately the goal is the newest software one plus has to offer with root, snapchat working, and a custom kernel set for better battery life.
You probably flashed an older version of SuperSU, which will cause endless boot animation. The SuperSU included in the toolkit should be the latest stable version. Alternatively, you could root with Magisk, which I have personally found to be easier to install (not as many branched versions) and use. Magisk is not the same as SuperSU, but they both result in the same outcome - systemless root. It's also easier to hide root from other apps (such as Snapchat) using Magisk through the Magisk Manager app. You can find out more about it here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Toolkit worked perfectly for me. I flashed the latest beta directly from one plus and installed snapchat and logged in. Used the toolkit to root and install franco kernel. Moderator please close this thread.
Are there any issues using adb backup to babkup all apps and restore after unlocking the bootloader? Or is there any better way to backup apps?