Related
So here's my goal, to leave everything stock, with only root (su installed), so I can install a Verizon locked app, su, and perhaps busybox (I installed Terminal Emulator, but virutally no commands available).
1. Why use the one-click method over the method? As I understand it, the just unlocks the bootloader, so I'd need to install a custom recovery, to be able to flash an unsigned zip (su). I'd like to keep the stock recovery. Perhaps the process is to flash custom recovery, su, then restore stock recovery?
2. After I get root, will future OTA updates work? I'd like to not break that functionality.
3. It would be nice if would also allow you to just get root on your phone without dealing with the bootloader.
I've rooted and flashed my old Cliq, and it's nice having root when I need it. I also wanted to play around with setting the button led backlight levels, which via the command line requires root.
wrong section man
Well, perhaps I mis-understood the sections. Seems any questions having to do with roms/rooting go in this section.
Either way, questions still stands, and it seems your the resident expert for this phone.
Forgot to add, from all the other threads I've read, it seems there is/was some confusion as to whether or not the method would all you to flash a new kernel, not that I currently want to do that.
Edit: Since this is apparently in the wrong section, can one of the mods move it?
Edit 2: Thanks Binary100100 for moving this thread to the correct section.
oryan_dunn said:
Well, perhaps I mis-understood the sections. Seems any questions having to do with roms/rooting go in this section.
Either way, questions still stands, and it seems your the resident expert for this phone.
Forgot to add, from all the other threads I've read, it seems there is/was some confusion as to whether or not the method would all you to flash a new kernel, not that I currently want to do that.
Edit: Since this is apparently in the wrong section, can one of the mods move it?
Click to expand...
Click to collapse
you can flash kernels it is harder what else you need to know
How do I backup the stock recovery?
If I unlock the bootloader, do I need to flash a custom recovery to move forward? Or does unlocking the bootloader allow me to flash unsigned zips?
yes and its hard to backup stock recovery i got a backup all ready
So with an unlocked bootloader, I won't need a custom recovery? Just trying to learn, as it's a bit different than my Cliq.
you do need custom recovery sorry man i cant do much more explaing so busy butother people help you and look around read root threads etc
Well, thanks for the help so far.
If any one else is reading this thread, these are the questions I still have:
1. How do I backup the stock recovery? I know once I load a custom recovery, I will be able to backup the stock ROM.
2. Disregarding any warranty issues, why choose the method or the One-Click method?
3. Once unlocked/rooted, will DRM content still work? Will the Movies section in the Android Market still be available? It's not on my Cliq with CyanogenMod 7.
4. Once unlocked/rooted, will OTA updates apply correctly? Was anyone rooted on 1.36.531.5 and have the 1.36.531.6 update apply correctly?
5. Does the method wipe the device?
Thanks,
Ryan
oryan_dunn said:
Well, thanks for the help so far.
If any one else is reading this thread, these are the questions I still have:
1. How do I backup the stock recovery? I know once I load a custom recovery, I will be able to backup the stock ROM.
2. Disregarding any warranty issues, why choose the method or the One-Click method?
3. Once unlocked/rooted, will DRM content still work? Will the Movies section in the Android Market still be available? It's not on my Cliq with CyanogenMod 7.
4. Once unlocked/rooted, will OTA updates apply correctly? Was anyone rooted on 1.36.531.5 and have the 1.36.531.6 update apply correctly?
5. Does the method wipe the device?
Thanks,
Ryan
Click to expand...
Click to collapse
1. There is no need to backup the stock recovery. Once you flash a custom recovery there will never be a need to go back to stock. If for whatever reason you do want stock then just flash an ruu and you'll go completely back to stock.
2. You MUST use the method to get the unlock_code.bin file to unlock your bootloader before you even attempt to get root access. Once you have your bootloader unlocked you can make changes to the root of your device. With it locked you can only obtain a partial root which will reset itself after a reboot. For example, if you obtain a temporary root and remove a system app (like boatware), or two, or ten (whatever) then reboot they will re-appear. So you MUST have either s-off (not going to happen until an exploit is found and really isn't needed) or an unlocked bootloader. Once you receive the file from HTC then follow the included instructions to unlock your device. NOTE: You will lose all of your data when you unlock your bootloader so back it up first! After your bootloader is unlocked you can obtain root by one of two methods.
a) 1-Click root script.
This simply pushes an app called SuperUser.apk to the /system partition and a su binary file to the /system/bin directory which gives us root. Then download ClorckworkMod app from Market and install the custom recovery. From the app you can select "reboot to recovery" and install your custom roms.
b) Placing a custom recovery in a form of a PH85IMG.zip on the root of your external sdcard and boot into the bootloader. Then update the recovery.
Now with all of that being said I want to make something clear. The unlock method does NOT allow you to use the device for other carriers! You would still require the T-Mobile SIM to use the device.
3. Having root does have some disadvantages. Some roms may effect the ability to watch DRM movies, watch movies from Market, etc. Depends on your rom though. Check with the developer. ALWAYS make a nandroid backup prior to flashing any rom! That way if you don't like what you flashed you can always revert.
4. Okay... well I stand corrected.... this is the ONLY real reason to install the stock recovery. However installing an OTA update will cause you to lose root. Even with a custom recovery and a stock rom... if you receive a notice to install an update it will not work! The best alternative if you really really really want the update and lose all root then flash an RUU, do the update and hope that HTC didn't do anything to prevent you from getting root again. My best advice would be to wait for your favorite developer to update his/her rom with the update that you're trying to flash. That way you won't lose your data (shouldn't anyway) and no real risk of losing root.
With all that being said... I'm moving this to General because it's where all the Q&A's go.
Thanks for all the detailed info. I'd like root (installation of Superuser only) for the stock ROM. I don't plan on installing a custom ROM at this time. If I have an unlocked bootloader, how could HTC block root access? Couldn't I just flash an su zip? Ideally, I'd like to be able to swap recoveries out to apply the OTA updates. I kinda wish they had a code to just give me root access on the stock ROM.
I see the ruu thread, but am concerned about the source of the ROMs. Does HTC ever officially release a complete stock ROM?
Sent from my HTC_Amaze_4G using XDA App
oryan_dunn said:
Thanks for all the detailed info. I'd like root (installation of Superuser only) for the stock ROM. I don't plan on installing a custom ROM at this time. If I have an unlocked bootloader, how could HTC block root access? Couldn't I just flash an su zip? Ideally, I'd like to be able to swap recoveries out to apply the OTA updates. I kinda wish they had a code to just give me root access on the stock ROM.
I see the ruu thread, but am concerned about the source of the ROMs. Does HTC ever officially release a complete stock ROM?
Sent from my HTC_Amaze_4G using XDA App
Click to expand...
Click to collapse
This is all that you really need here.
http://forum.xda-developers.com/showthread.php?t=1324177
If you really want to be able to download and install system updates you will need the stock recovery in step 4.
oryan_dunn said:
Thanks for all the detailed info. I'd like root (installation of Superuser only) for the stock ROM. I don't plan on installing a custom ROM at this time. If I have an unlocked bootloader, how could HTC block root access? Couldn't I just flash an su zip? Ideally, I'd like to be able to swap recoveries out to apply the OTA updates. I kinda wish they had a code to just give me root access on the stock ROM.
I see the ruu thread, but am concerned about the source of the ROMs. Does HTC ever officially release a complete stock ROM?
Sent from my HTC_Amaze_4G using XDA App
Click to expand...
Click to collapse
IDK but I read your questions in a very slow voice like mr. mackey in southpark or something
anyways, why are you so worried about getting OTA updates?
a developer will eventually root and deodex it anyways.
You say you want to keep stock rom, but why don't you try the Custom ROMs which are basically stock ROMs on steroids?
You do realize when you apply an OTA update you lose your root access and there is a possibility that it'll be harder to even have your device rooted in the future.
For example, the mt4g, everybody got happy and updated to the gingerbread OTA, but lost root and nobody found out how to exploit it until about a month later or so.. and that is only by downgrading which is a tedious process that many, who don't know how to use ADB, have troubles with.
I believe the OTA updates comes with new bootloaders and radios, not only the rom, so it will lock your bootloader. (I think) that's what it does to other devices. Who knows if htcdev will work on all bootloaders. just my two cents, if you want full control of your device, unlock bootloader and root it. You can get every OTA update through developers here.
Teo032 said:
IDK but I read your questions in a very slow voice like mr. mackey in southpark or something
Click to expand...
Click to collapse
Man, hopefully I don't sound like that. I really appreciate all the step-by-step guides; but, unlike most people, I want to understand what I'm doing, not just run through the steps.
anyways, why are you so worried about getting OTA updates?
a developer will eventually root and deodex it anyways.
You say you want to keep stock rom, but why don't you try the Custom ROMs which are basically stock ROMs on steroids?
Click to expand...
Click to collapse
Well, I don't really want to wipe my device at this time, so that probably rules out the HTC Dev method and installing a custom ROM. I asked about the source of the ROMs in the RUU thread, but if the stock recovery would flash them, then they'd obviously have been signed by HTC. If software is available via an official source, why would I download it from a forum? If I can get Ubuntu from Canonical, I wouldn't go download the ISO from an unofficial mirror (or if I did, I'd verify with the md5sum keys posted by Canonical).
Since I am really happy with my device as it is, and the ease of updating via OTA, I didn't want to give that up, just for the couple things I want to do with root access.
You do realize when you apply an OTA update you lose your root access and there is a possibility that it'll be harder to even have your device rooted in the future.
For example, the mt4g, everybody got happy and updated to the gingerbread OTA, but lost root and nobody found out how to exploit it until about a month later or so.. and that is only by downgrading which is a tedious process that many, who don't know how to use ADB, have troubles with.
I believe the OTA updates comes with new bootloaders and radios, not only the rom, so it will lock your bootloader. (I think) that's what it does to other devices. Who knows if htcdev will work on all bootloaders. just my two cents, if you want full control of your device, unlock bootloader and root it. You can get every OTA update through developers here.
Click to expand...
Click to collapse
Hmm, unless these devices have backup/secondary bootloaders, I doubt and OTA update would flash a new one, as an error during that flash could brick the device. It would seem odd that HTC would promise to unlock bootloaders, give an OTA update that would not work with their site. I'm not saying that it couldn't happen, just seems unlikely. Was the MT4G unlock done via? If it was an exploit to gain root, then I'd understand why they'd loose root.
oryan_dunn said:
Hmm, unless these devices have backup/secondary bootloaders, I doubt and OTA update would flash a new one, as an error during that flash could brick the device. It would seem odd that HTC would promise to unlock bootloaders, give an OTA update that would not work with their site. I'm not saying that it couldn't happen, just seems unlikely. Was the MT4G unlock done via? If it was an exploit to gain root, then I'd understand why they'd loose root.
Click to expand...
Click to collapse
HTC has updated their bootloaders via OTA on a few occasions. And we know that HTC and T-Mobile (along with other carriers) read these forums as well (shout out to HTC and our wireless carriers) so almost literally the day of an exploit is discovered and if HTC isn't happy with our findings what do you suppose they will do? They will almost always look for the safest way to update the bootloader and keep us from being able to use that exploit. Seeing that we still don't have S-OFF (and may never have it) they are obviously doing all they can to make it more and more difficult. That in itself is proof that they don't want us to have it. So would they push an OTA to keep us locked to S-ON if they can? You better believe it!
I can see them patching a hole that would get you S-OFF, but seems odd that they would take back an unlocked bootloader that they themselves unlocked.
I guess I'm ok with the offical unlock method without S-OFF, if the only things I can't do are flash a new bootloader, radio, or unlock the SIM. Did I miss anything there?
I don't get it, you say you want to use root on the stock roms, and now you're saying why bother downloading a stock ROM that is prerooted when you can download stock ROM that isn't rooted ota? What is the difference? You're going to want to root the ota updates and the developers are already providing it for you. it doesn't matter where you get it, you're gonna use some 3rd party exploit to root the ROM anyways.
You my friend seems to have a indecisive problem. I understand that you want to understand the process, but if you don't want anything to do with 3rd party developing you're in the wrong place. You're making your life very hard.
And i think that's about it about being s-on. It's more of the hardware functionality that is locked.
Think about it as a locked bios kinda... Lol
Sent from my HTC_Amaze_4G using XDA App
Teo032 said:
I don't get it, you say you want to use root on the stock roms, and now you're saying why bother downloading a stock ROM that is prerooted when you can download stock ROM that isn't rooted ota? What is the difference? You're going to want to root the ota updates and the developers are already providing it for you. it doesn't matter where you get it, you're gonna use some 3rd party exploit to root the ROM anyways.
You my friend seems to have a indecisive problem. I understand that you want to understand the process, but if you don't want anything to do with 3rd party developing you're in the wrong place. You're making your life very hard.
Sent from my HTC_Amaze_4G using XDA App
Click to expand...
Click to collapse
I don't need to use an exploit to root the stock rom. I can unlock my bootloader direct from HTC, flash a new recovery, and then flash the superuser program. That was kinda my point in asking in the first place... why use an exploit (one-click), when an official route is available?
oryan_dunn said:
I don't need to use an exploit to root the stock rom. I can unlock my bootloader direct from HTC, flash a new recovery, and then flash the superuser program. That was kinda my point in asking in the first place... why use an exploit (one-click), when an official route is available?
Click to expand...
Click to collapse
That's considered official? It's basically the same thing..
Sent from my HTC_Amaze_4G using XDA App
Teo032 said:
That's considered official? It's basically the same thing..
Sent from my HTC_Amaze_4G using XDA App
Click to expand...
Click to collapse
Well, yeah, you end up at the same place, except instead of using an exploit, I go to HTC to get an unlock code. I'd consider it official since I'd go through HTC to get the ball rolling.
Hey all,
I'm fairly new to unlocking/rooting (I'm from the simple iPhone jailbreak world).
I have my Atrix 4G rooted with no issues and ClockworkMod installed... that was the easy part it seems.
Where I am struggling is to figure out IF I can unlock my Atrix 4G and if it is safe to do.
I am running Android 2.3.6 on the Bell network. I see a bunch on unlocks for bootloader 2.3.4 and am confisued if that bootloader version has any relation to the android version? How can I figure out what bootloader I have? Would it also be 2.3.6?
If it is indeed 2.3.6, is it possible to unlock, I see no specific unlocks for that version.
Thanks,
You cant install a different recovery with out being unlocked. so if you can boot into CWM then your phone is already unlocked.
Where did you get the phone? was it new?
Its possible if its used that it was already unlocked and someone RSD back to stock for sale purpose, if its new and you havent unlocked yet then you dont have CWM installed.
Random Canadian said:
You cant install a different recovery with out being unlocked. so if you can boot into CWM then your phone is already unlocked.
Where did you get the phone? was it new?
Its possible if its used that it was already unlocked and someone RSD back to stock for sale purpose, if its new and you havent unlocked yet then you dont have CWM installed.
Click to expand...
Click to collapse
Sorry should have been a little more clear, I have installed ROM Manager and choose the CWM install, but I cannot boot into it, I get a boot error 2 (I think). Sorry phone is at home now so I can't recall exact error will post later.
I got phone 6 month ago, was used phone. I am fairly certain its not unlocked because I cannot boot with CWM, hence cannot install custom ROM.
Thanks for the reply.
Random Canadian said:
You cant install a different recovery with out being unlocked. so if you can boot into CWM then your phone is already unlocked.
Where did you get the phone? was it new?
Its possible if its used that it was already unlocked and someone RSD back to stock for sale purpose, if its new and you havent unlocked yet then you dont have CWM installed.
Click to expand...
Click to collapse
You don't need to be unlocked to have CWM on your Atrix. I had it on at least 1.83 if not the original stock firmware. I know it was possible with only root on 1.83 because that was what I was running up until a month ago and I had CWM on it with a locked bootloader.
cerps said:
You don't need to be unlocked to have CWM on your Atrix. I had it on at least 1.83 if not the original stock firmware. I know it was possible with only root on 1.83 because that was what I was running up until a month ago and I had CWM on it with a locked bootloader.
Click to expand...
Click to collapse
Right, my phone is rooted so I have CWM, just can't boot it. My understanding is because I need to unlock, but I don't know how to unlock because I don't know how to figure out what bootloader I have.
cerps said:
You don't need to be unlocked to have CWM on your Atrix. I had it on at least 1.83 if not the original stock firmware. I know it was possible with only root on 1.83 because that was what I was running up until a month ago and I had CWM on it with a locked bootloader.
Click to expand...
Click to collapse
Locked or it just didnt say unlocked at the top? two very different things.
avalanche333 said:
Right, my phone is rooted so I have CWM, just can't boot it. My understanding is because I need to unlock, but I don't know how to unlock because I don't know how to figure out what bootloader I have.
Click to expand...
Click to collapse
dur im pretty sure that unlocking the boot loader allows unsigned code to run at boot, I could be wrong but I think you two are out to lunch on installing CWM with just root.
That or you can install it but you cant run it because the boot loader wont allow something with out motorolas signature to execute. making the point of if it is or is not, installed, a moot one. Aside from the fact you no longer have any sort of a functional recovery mode.
There is a LOT of info on how to unlock the bootloader and its not exactly hidden. I dont know if its even still done with RSD but that would be a place to start as that is how I did mine in sept of last year.
Random Canadian said:
Locked or it just didnt say unlocked at the top? two very different things.
dur im pretty sure that unlocking the boot loader allows unsigned code to run at boot, I could be wrong but I think you two are out to lunch on installing CWM with just root.
That or you can install it but you cant run it because the boot loader wont allow something with out motorolas signature to execute. making the point of if it is or is not, installed, a moot one
There is a LOT of info on how to unlock the bootloader and its not exactly hidden. I dont know if its even still done with RSD but that would be a place to start as that is how I did mine in sept of last year.
Click to expand...
Click to collapse
Yes I see what your saying, but I am saying that I cannot run CWM. I can only install onto my SD card. But the boot in recovery does not work (ie it will not run CWM). I'll post the error little later tonight when I try at it again.
I realize there is lots of info on unlocking bootloader and I am not concerned about doing the unlock, once I find a way to verify my bootloader version. Ive seen a few posts warning that bootloader must be v 2.3.4 or you can brick the phone.
So I guess ultimately my question is, how can I figure out my bootloader version? Have not seem this answers after some googling.
http://forum.xda-developers.com/showthread.php?t=1136261
Read that and your version will be in settings and then about phone. although I do believe that 234 and 236 unlock via the same method.
If you are going to install Custom roms CM7/9/10 or a blur based then you dont need to even worry about root. otherwise there are instructions in that thread to root that SBF
Random Canadian said:
Locked or it just didnt say unlocked at the top? two very different things.
dur im pretty sure that unlocking the boot loader allows unsigned code to run at boot, I could be wrong but I think you two are out to lunch on installing CWM with just root.
That or you can install it but you cant run it because the boot loader wont allow something with out motorolas signature to execute. making the point of if it is or is not, installed, a moot one. Aside from the fact you no longer have any sort of a functional recovery mode.
There is a LOT of info on how to unlock the bootloader and its not exactly hidden. I dont know if its even still done with RSD but that would be a place to start as that is how I did mine in sept of last year.
Click to expand...
Click to collapse
I'm positive it was locked, running 1.83, and had CWM on it. I bought the phone at an AT&T store myself. I rooted it and put CWM on it. The early version of CWM for the Atrix only was accessible by turning the phone on while plugged into the wall charger that came with the phone.
I've had a lot of trouble upgrading to KitKat. After attempting to flash different image files for stock recovery/boot/system, I found it impossible to completely unroot the phone using the instructions posted because the phone kept re-rooting itself. Finally, I S-offed, wrote superCID, used the Telus RUU, applied the OTA downloaded to the phone, changed the CID back to GLOBA001 (my carrier is WindMobile). And finally! I know I relocked and unlocked the bootloader somewhere in the process, but I can't quite remember when.
Now, before I even think of re-rooting the phone or installing a custom recovery, I'd like to create a backup of the stock boot, recovery, and system. I tried running
Code:
fastboot boot openrecovery-twrp-2.7.1.1-zaracl.img
using the special KitKat TWRP. There's a message about boot.img being downloaded successfully but the phone reboots to a black screen.
I know that TWRP 2.7.1.0 downloaded from their website worked fine on my phone before I ran the RUU . So I'm not sure that the new TWRP is incompatible with my phone.
If I wanted to use adb instead, I'd need to root the phone before being able to pull the stock recovery, boot, and system images using adb shell. If I have to resort to rooting, is there any way to do so without flashing a custom recovery first? If there is, I might be able to unroot the phone afterward and make it stick. (Delete the supersu apk and su binary, right?)
I remember that the first time my phone attempted to download and apply the OTA automatically, my phone wiped itself. It was a lot of hard work to get it back to a usable state, but it was my own fault for not having a proper backup. I'd like to avoid making that mistake again, and have a stock backup handy on my computer in case there are carrier updates for my phone in the future.
To re-iterate, possible to back up stock everything without root? If not, possible to root without installing custom recovery?
You can no longer boot into a custom recovery, you have to actually flash it.
As far as having the stock recovery and boot, those are actually inside the OTA so you can pull it from there.
Since you'll have the stock recovery already, you can flash TWRP and use that to backup boot and system.
When you need to go stock, just use TWRP to restore your backup and then manually flash the stock recovery.
Since you made the device S-OFF, I recommend that if you need to lock/unlock the bootloader that you use the commands in this thread versus using the htcdev method as that wipes the /data/preload/ folder (as part of its normal /data wipe) which includes a few stock apps.
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
Locking the bootloader won't do anything, it's only unlocking using the htcdev token that causes the data wipe. So if you haven't unlocked using the htcdev method since running the RUU you will still have the 2 - 3 apps.
I don't know if the /data/preload/ folder is a requirement for a successful OTA update or not but I checked inside my OTA zip for my phone and it does include the 3 items stored there for the VM variant.
The unlock was AFTER the RUU. I ran the RUU, then used the OTA to upgrade to KitKat, then unlocked the bootloader again. However, I didn't notice any apps disappearing and the OTA zip for Wind also has a /data/preload folder.
*Shrugs* Seems good enough to me. TWRP, here I come!
needing wind stock stuck with wind awsy amd wont connect
I have an unlocked desire 601 it finds only wind away I'm trying to get a backup of the stock Rom to flash it does anyone k ow if there any around or even a back up I can use to try to get my phone working on wind home
jayjsteez said:
I have an unlocked desire 601 it finds only wind away I'm trying to get a backup of the stock Rom to flash it does anyone k ow if there any around or even a back up I can use to try to get my phone working on wind home
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2804427
needing help for s-off
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
hey i have unlocked desire 601 but only says wind away and wont connect ive knoticed the wind version is the same as the other versions but im wondering do i need the wind rom in order for it to pick up the wind home i cant seem to find anywhere online the wind rom and everytime i try to s-off it saysfailed and ive followed everything is there any insite you could give me to help me with this issue if its fixable again my phone says wind away but wont connect to it and i need to get it working as its my only device and carrier i use thx
---------- Post added at 11:29 PM ---------- Previous post was at 11:16 PM ----------
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
hey i have unlocked desire 601 but only says wind away and wont connect ive knoticed the wind version is the same as the other versions but im wondering do i need the wind rom in order for it to pick up the wind home i cant seem to find anywhere online the wind rom and everytime i try to s-off it saysfailed and ive followed everything is there any insite you could give me to help me with this issue if its fixable again my phone says wind away but wont connect to it and i need to get it working as its my only device and carrier i use thx
-Duir- said:
You can no longer boot into a custom recovery, you have to actually flash it.
As far as having the stock recovery and boot, those are actually inside the OTA so you can pull it from there.
Since you'll have the stock recovery already, you can flash TWRP and use that to backup boot and system.
When you need to go stock, just use TWRP to restore your backup and then manually flash the stock recovery.
Since you made the device S-OFF, I recommend that if you need to lock/unlock the bootloader that you use the commands in this thread versus using the htcdev method as that wipes the /data/preload/ folder (as part of its normal /data wipe) which includes a few stock apps.
Click to expand...
Click to collapse
I don't understand how you can pull the stock recovery from the OTA. I thought OTA's are immediately installed, instead of stored untill you want to install it? So, how do you backup the stock recovery?
It is saved until you want to install. When it go finishes Downloading, just choose install later. And you will be able to copy it into other storage devices and extract files and what not. I'm not sure if it stores in internal or external I'm 80% sure external sd if you have one.
Sent from my HTC0P4E1 using XDA Free mobile app
So I've been unlocking and rooting/flashing phones since the HTC Universal but i'm stumped. I've downloaded the toolkit to unlock my bootloader, downloaded my .bin file and the toolkit says my bootloader is unlocked but the screen on my phone asking me whether i want to unlock it never comes out...any senior members willing to point me in the right direction? I'm using my AT&T M8 on T-mobile and i haven't had a single update since i bought the M8 so i need to update it ASAP.
Update: So I used the sunshine method to try and finally root my phone. Now I'm in the interesting situation where my boot loader is unlocked, it's s-off, yet there is still the stock recovery and not rooted yet. Quite the last 12 hours trying to get root access. I should be able to root it on the PC now that my boot loader is unlocked.
HTCFAN0923 said:
So I've been unlocking and rooting/flashing phones since the HTC Universal but i'm stumped. I've downloaded the toolkit to unlock my bootloader, downloaded my .bin file and the toolkit says my bootloader is unlocked but the screen on my phone asking me whether i want to unlock it never comes out...
Click to expand...
Click to collapse
The Toolkit hasn't been updated in forever, is very obsolete, and will therefore cause more problems than anything.
Toolkit just does functions that are easy to do yourself "manually" anyway. You don't need the toolkit, and you didn't need to s-off to unlock the bootloader (although it can be handy for other things).
HTCFAN0923 said:
I'm using my AT&T M8 on T-mobile and i haven't had a single update since i bought the M8 so i need to update it ASAP.
Click to expand...
Click to collapse
OTA updates for the AT&T version will only be received when connected to AT&T's network (an AT&T specific annoyance). You could have updated to Lollipop using RUU.
---------- Post added at 11:28 AM ---------- Previous post was at 11:26 AM ----------
HTCFAN0923 said:
Update: So I used the sunshine method to try and finally root my phone. Now I'm in the interesting situation where my boot loader is unlocked, it's s-off, yet there is still the stock recovery and not rooted yet. Quite the last 12 hours trying to get root access. I should be able to root it on the PC now that my boot loader is unlocked.
Click to expand...
Click to collapse
Now that the bootloader is unlocked, just flash TWRP via fastboot. Then flash SuperSU 2.46 using TWRP to obtain root.
But your OP says you want to update. Here it says you want to root. Those are 2 very different things, so its not clear what your actual goal is.
redpoint73 said:
The Toolkit hasn't been updated in forever, is very obsolete, and will therefore cause more problems than anything.
Toolkit just does functions that are easy to do yourself "manually" anyway. You don't need the toolkit, and you didn't need to s-off to unlock the bootloader (although it can be handy for other things).
OTA updates for the AT&T version will only be received when connected to AT&T's network (an AT&T specific annoyance). You could have updated to Lollipop using RUU.
---------- Post added at 11:28 AM ---------- Previous post was at 11:26 AM ----------
Now that the bootloader is unlocked, just flash TWRP via fastboot. Then flash SuperSU 2.46 using TWRP to obtain root.
But your OP says you want to update. Here it says you want to root. Those are 2 very different things, so its not clear what your actual goal is.
Click to expand...
Click to collapse
Thanks for the help and sorry for the confusion.
I'm looking to update my phone AND root just because I've always rooted my phones but just now got a replacement for my old laptop that broke down shortly before I got the M8. I figured since I was on T-Mobile my best bet to update it would be to root it and upload a new ROM anyway. Your suggestion is easy enough so I'll be doing that after work.
My last question is this: On the M7, I was able to use an international M7 ROM as everything apart from the radios was the same. Is that the case with the M8 as well? I typically like having Sense ROM's but hate the bloat carriers put on their RUU's....
thanks again!
HTCFAN0923 said:
I'm looking to update my phone AND root just because I've always rooted my phones but just now got a replacement for my old laptop that broke down shortly before I got the M8. I figured since I was on T-Mobile my best bet to update it would be to root it and upload a new ROM anyway. Your suggestion is easy enough so I'll be doing that after work.
Click to expand...
Click to collapse
In that case, I would suggest updating by RUU first, and then root.
Reason I say that, is that RUU would wipe out root anyway, so no point in having to do it twice.
Whether you unlock the bootloader (via HTCDev.com) before or after RUU is somewhat irrelevant. Especially since you have s-off, so its not required to relock the bootloader to RUU (which is required with s-on).
But one other thing to consider. Since you are using the AT&T version on the T-Mobile US network; the ATT version is actually missing support for the AWS band that T-Mob uses in most areas for HSPA (3G). If you are in an area with good LTE coverage (and I'll assume NYC is) you may have not even noticed this. But if you move into an area where T-Mob doesn't have LTE, you might find that you don't have 3G either, and be pushed down to 2G (EDGE) data speed.
One cool thing about the M8, is the band support is actually software based. So one option would be to change your device's carrier ID (CID) and model ID (MID) which are possible with s-off, then flash the T-Mobile firmware or RUU to "convert" the phone to a T-Mob device including the proper T-Mob band support. After that, you can unlock the bootloader, root, flash a custom ROM.
HTCFAN0923 said:
My last question is this: On the M7, I was able to use an international M7 ROM as everything apart from the radios was the same. Is that the case with the M8 as well? I typically like having Sense ROM's but hate the bloat carriers put on their RUU's....
Click to expand...
Click to collapse
Yes, its a similar situation on the M8. All international ROMs should work on the M8. But note that your firmware (hboot, radio, etc.) needs to be the proper version supported by the ROM. So for instance, if you are still on KitKat (sounds like you are) you will want to update firmware first, otherwise if you flash a Lollipop ROM, you will likely suffer major issues such as broken WiFi and extreme long boot times (10+ min).
redpoint73 said:
In that case, I would suggest updating by RUU first, and then root.
Reason I say that, is that RUU would wipe out root anyway, so no point in having to do it twice.
Whether you unlock the bootloader (via HTCDev.com) before or after RUU is somewhat irrelevant. Especially since you have s-off, so its not required to relock the bootloader to RUU (which is required with s-on).
But one other thing to consider. Since you are using the AT&T version on the T-Mobile US network; the ATT version is actually missing support for the AWS band that T-Mob uses in most areas for HSPA (3G). If you are in an area with good LTE coverage (and I'll assume NYC is) you may have not even noticed this. But if you move into an area where T-Mob doesn't have LTE, you might find that you don't have 3G either, and be pushed down to 2G (EDGE) data speed.
One cool thing about the M8, is the band support is actually software based. So one option would be to change your device's carrier ID (CID) and model ID (MID) which are possible with s-off, then flash the T-Mobile firmware or RUU to "convert" the phone to a T-Mob device including the proper T-Mob band support. After that, you can unlock the bootloader, root, flash a custom ROM.
Yes, its a similar situation on the M8. All international ROMs should work on the M8. But note that your firmware (hboot, radio, etc.) needs to be the proper version supported by the ROM. So for instance, if you are still on KitKat (sounds like you are) you will want to update firmware first, otherwise if you flash a Lollipop ROM, you will likely suffer major issues such as broken WiFi and extreme long boot times (10+ min).
Click to expand...
Click to collapse
Crap....went back to the toolkit to flash twrp and root it and lo and behold, my phone is now stuck in the entering recovery screen....How ****ty is that toolkit that it can't do even do a proper recovery flash right...8 years on XDA and I've never had such a headache from rooting/flashing a device....
HTCFAN0923 said:
Crap....went back to the toolkit to flash twrp and root it and lo and behold, my phone is now stuck in the entering recovery screen....How ****ty is that toolkit that it can't do even do a proper recovery flash right...8 years on XDA and I've never had such a headache from rooting/flashing a device....
Click to expand...
Click to collapse
I gave previous advice to stop using the toolkit, so I don't know why you insist on ignoring that advice.
Older versions of TWRP don't work on newer hboots; and the opposite is true where older hboots don't work with newer TWRP builds. This is the most frequent reason for TWRP not working properly.The toolkit worked fine at the time it was updated. But it hasn't been updated in a very long time, and therefore won't work on many M8 versions now. The issue is more your lack of understanding, and lack of following advice given to you.
Flashing TWRP is just a matter of downloading the proper version, and flashing with a single fastboot command (2 commands, if you want to be thorough and wipe cache before flashing TWRP). You don't need a toolkit for that, and again I advise stopping its use altogether.
Its not clear whether you chose to update before TWRP and root (current device status) and once I know the main version (OS number on bootloader screen) and present hboot number I can probably advice what version TWRP you need to flash.
And you're absolutely right about that. It was my fault for not listening. I was being lazy about it honestly.
I did end up using the lollipop pre rooted RUU and that worked after two atttempts. I think the issue was that the toolkit flashed the recovery without root. Add that to the fact that the toolkit caused the SD card issue to pop up made it a nightmare. Thankfully, I was able to fix it and now I'm running the AT&T lollipop ROM rooted.
You truly are the best and I thank you for the advice and help. Let me know your PayPal so I can send you beer money for the trouble.
HTCFAN0923 said:
I think the issue was that the toolkit flashed the recovery without root.
Click to expand...
Click to collapse
I don't follow. Root isn't needed to install custom recovery; nor does flashing custom recovery automatically root the phone (this has to be done as an additional step, usually by flashing SuperSU in TWRP).
I think the main issue was that the toolkit flashed an old TWRP version that was not compatible with the software/firmware that was on your phone.
HTCFAN0923 said:
You truly are the best and I thank you for the advice and help. Let me know your PayPal so I can send you beer money for the trouble.
Click to expand...
Click to collapse
I appreciate the thought; but your thanks is all I expect in return. I've benefited plenty from XDA from folks that don't ask for any monetary compensation; so I just like to give back to the community by helping how I can.
Wanting to root Alcatel Fierce (model #5049z) and trying to discover whether boot loader is "locked". Read all the posts here concerning this phone and still don't know whether it can be rooted (yet). This is a fairly new phone and information for/about it is sparse. Anyone familiar with this phone and can offer up some vital stats/information or where I might obtain the information? This phone has "unlock boot loader" option, but not sure it works? HELP!!!!!! [Android 7.0]
THANX:
Rick
This does have a oem unlock option yet king root or kingo root doesnt work lol anyways I just picked one of these phones up today and looks like I will have to create my own root and hell mise well get a working twrp in order too. Back to the kitchen!
Just check whether bootloader is unlocked using fastboot.
Use rooting tools after unlocking.
Thats the plan, I planned on creating a way to root then once rooted I can make a full dump if all the partitions of the phone with fire flash then off to deodexing and debloating the system and placing SuperSU in the system so no more issues with root
I will like to know the working method as well i have turned on that option to unlock the bootloader but i have failed to google anything that actually works I have tried iroot, rootme, SRSRoot for Android and none of them was able to root the device
Anything yet?
Has anyone going out anything on this phone. Would like to be able to change a few settings on this phone. Thanks.