I am using US tmobile amaze overseas so the only convenient solution for me was to buy an unlock code online. Now it has been unlocked. Ok, I was aware of the OTA upgrade since december time, but everytime I checked for upgrade in About Phone it turned out to say no update for me. And I am also aware the upgrade was planned to stop delivering in mid Jan, so I would have missed it forever.
Now the question: Are unlocked phone not eligible for pushed updates?
I am aware of the stock roms compiled by xboarders especially the deodex 1.43.531.5 version, but it must need custom recovery to install. Any other way for me to install the said version without wipeout?
otivaeey said:
I am using US tmobile amaze overseas so the only convenient solution for me was to buy an unlock code online. Now it has been unlocked. Ok, I was aware of the OTA upgrade since december time, but everytime I checked for upgrade in About Phone it turned out to say no update for me. And I am also aware the upgrade was planned to stop delivering in mid Jan, so I would have missed it forever.
Now the question: Are unlocked phone not eligible for pushed updates?
I am aware of the stock roms compiled by xboarders especially the deodex 1.43.531.5 version, but it must need custom recovery to install. Any other way for me to install the said version without wipeout?
Click to expand...
Click to collapse
Not Development related.
this is a question and not a development for the amaze. please post in correct section next time (General). Being that the phone is unlocked does not matter since you have not modified any system files. You also need to post more information like what carrier and what version are you on and trying to update to?
Binary, Would you please move this where it belongs. Thnx
fcpelayo said:
this is a question and not a development for the amaze. please post in correct section next time (General). Being that the phone is unlocked does not matter since you have not modified any system files. You also need to post more information like what carrier and what version are you on and trying to update to?
Binary, Would you please move this where it belongs. Thnx
Click to expand...
Click to collapse
Right. The phone has not been modified. I have tried the phone on Vodafone and Three UK during the update, but couldn't receive the OTA update, not even via wifi. My version is 1.36.531.5 TMOUS, wanting 1.43.531.5 TMOUS.
Thank you
It will not update because of the custom recovery.
kruschman said:
It will not update because of the custom recovery.
Click to expand...
Click to collapse
OP didn't say he has installed custom recovery so that has nothing to do with it. Sounds like his phone is stock. I'm not sure how OTA updates work when you're on another network other than Tmobile. I know that my Telus phone will never see an OTA update.
otivaeey said:
Right. The phone has not been modified. I have tried the phone on Vodafone and Three UK during the update, but couldn't receive the OTA update, not even via wifi. My version is 1.36.531.5 TMOUS, wanting 1.43.531.5 TMOUS.
Thank you
Click to expand...
Click to collapse
It will not upgrade bc the update is carrier related. According to HTC when I called, but I remember hearing a menu for support in europe. I had called in for something else. Although you can try contacting them. Also if you dont care about your warranty being voided then I suggest you unlock bootloader, root and flash the update manually or flash a custom rom. For non us customers your update should be 1.46 i think.
marleyfan61 said:
OP didn't say he has installed custom recovery so that has nothing to do with it. Sounds like his phone is stock. I'm not sure how OTA updates work when you're on another network other than Tmobile. I know that my Telus phone will never see an OTA update.
Click to expand...
Click to collapse
My bad, I assumed it was rooted also.
otivaeey said:
I am using US tmobile amaze overseas so the only convenient solution for me was to buy an unlock code online. Now it has been unlocked. Ok, I was aware of the OTA upgrade since december time, but everytime I checked for upgrade in About Phone it turned out to say no update for me. And I am also aware the upgrade was planned to stop delivering in mid Jan, so I would have missed it forever.
Now the question: Are unlocked phone not eligible for pushed updates?
I am aware of the stock roms compiled by xboarders especially the deodex 1.43.531.5 version, but it must need custom recovery to install. Any other way for me to install the said version without wipeout?
Click to expand...
Click to collapse
other than flashing a custom rom, only other way i can think of is this, it'll keep your bootloader locked, stock recovery, just like a brand new amaze with the ota update, but it will wipe absolutely everything...
http://forum.xda-developers.com/showthread.php?t=1335703
smatthew45 said:
other than flashing a custom rom, only other way i can think of is this, it'll keep your bootloader locked, stock recovery, just like a brand new amaze with the ota update, but it will wipe absolutely everything...
http://forum.xda-developers.com/showthread.php?t=1335703
Click to expand...
Click to collapse
Exactly.
Just backup your data to your external sdcard, backup your internal sdcard to your computer, download the PH85IMG.zip file for 1.43 rom, relock your bootloader if you haven't done so already (or have done it at all), place the PH85IMG.zip (named as such) onto the root of your external sdcard, boot into bootloader and flash the file.
Afterwards restore your backups.
hmmm makes me wonder now.. what kind of unlocked did the op mean? network unlock to use overseas or bootloader unlocked
fcpelayo said:
hmmm makes me wonder now.. what kind of unlocked did the op mean? network unlock to use overseas or bootloader unlocked
Click to expand...
Click to collapse
He said he he's overseas and bought an unlock coded online. That can only mean network unlock.
Binary100100 said:
Exactly.
Just backup your data to your external sdcard, backup your internal sdcard to your computer, download the PH85IMG.zip file for 1.43 rom, relock your bootloader if you haven't done so already (or have done it at all), place the PH85IMG.zip (named as such) onto the root of your external sdcard, boot into bootloader and flash the file.
Afterwards restore your backups.
Click to expand...
Click to collapse
Thanks so much for the help guys, but I am still stuck in the bootloader part. I have done: place PH85IMG.ZIP (exactly zip, around 400mb) onto the root of my EXTERNAL sdcard.
In the bootloader what I have got was this:
SD checking...
Loading...[PH85DIAG.zip]
No image!
Loading...[PH85DIAG.nbh]
No image or wrong image!
Loading...[PH85IMG.zip]
No image!
Loading...[PH85IMG.nbh]
No image or wrong image!
Loading...[PH85IMG.tar]
No image!
Loading...[PH85IMG.aes]
No image!
My phone is on stock rom, stock bootloader, stock recovery, everything is stock. Perhaps I didn't put it right in the root. Can you guys specify the root location? I mean /what?
otivaeey said:
Thanks so much for the help guys, but I am still stuck in the bootloader part. I have done: place PH85IMG.ZIP (exactly zip, around 400mb) onto the root of my EXTERNAL sdcard.
In the bootloader what I have got was this:
SD checking...
Loading...[PH85DIAG.zip]
No image!
Loading...[PH85DIAG.nbh]
No image or wrong image!
Loading...[PH85IMG.zip]
No image!
Loading...[PH85IMG.nbh]
No image or wrong image!
Loading...[PH85IMG.tar]
No image!
Loading...[PH85IMG.aes]
No image!
My phone is on stock rom, stock bootloader, stock recovery, everything is stock. Perhaps I didn't put it right in the root. Can you guys specify the root location? I mean /what?
Click to expand...
Click to collapse
Did you relock your bootloader?
mine was doing that too for awhile, so what i did was make sure the ONLY thing on my external sdcard was the PH85IMG.zip file, after that the phone recognized it without any problems
Are you sure it's not named as PH85IMG.zip.zip? When you downloaded the file, did you add the .zip extension? If so, remove the 2nd .zip extension, and you should be golden.
fcpelayo said:
It will not upgrade bc the update is carrier related..
Click to expand...
Click to collapse
It's incorrect. I got that update straightway in December - in fact my Amaze is being used overseas and therefore certainly unlocked from T-Mobile..
Related
I've been trying to root my G2 Touch and have used the goldcard method.
I can only find the latest tmobile RUU (2.73) which can't be rooted!
Is there anywhere the stock (1.73) tmobile RUU is?
Regards
Signed update zip is here>> http://www.4shared.com/file/133081624/c5e35fa0/update-hero-t-mobile-1761106-s.html if any good.
Is there a reason for you to use goldcard on your G2? On mine (got at end of last month), it was the original unlocked 1.73 version, and it had an unlocked bootloader, allowing me to use fastboot to boot a custom recovery image (AmonRA) and then do a nandroid backup before flashing an update.zip
Presuming you need to use goldcard, I would have thought that a generic HTC version would have done. So long as it is 1.73, I think it would work fine, since the purpose of the goldcard (IIRC) is to ignore the carrier id and let you install the stock HTC ROM onto the device. From there you could root and flash the recovery partition to allow installation of custom roms.
So in conclusion-
-You might not actually need to use a goldcard, but if you do,
-Give the generic HTC 1.73 ROM a shot
BTW, I haven't personally tried this, so hopefully someone who knows a bit more about this can confirm if this would work, but I reckon it should. If possible, take a nandroid backup first, but this might be a bit difficult if fastboot doesn't work for you.
anon2122 said:
Is there a reason for you to use goldcard on your G2? On mine (got at end of last month), it was the original unlocked 1.73 version, and it had an unlocked bootloader, allowing me to use fastboot to boot a custom recovery image (AmonRA) and then do a nandroid backup before flashing an update.zip
Presuming you need to use goldcard, I would have thought that a generic HTC version would have done. So long as it is 1.73, I think it would work fine, since the purpose of the goldcard (IIRC) is to ignore the carrier id and let you install the stock HTC ROM onto the device. From there you could root and flash the recovery partition to allow installation of custom roms.
Click to expand...
Click to collapse
Yea I needed the goldcard because I did the 2.73 RUU lag update which I didn't know could not be rooted :/
Lord Lucan said:
Signed update zip is here>> http://www.4shared.com/file/133081624/c5e35fa0/update-hero-t-mobile-1761106-s.html if any good.
Click to expand...
Click to collapse
I downloaded the file and it wasn't the RUU file. Thanks for your help though.
use the rooted htc generic 2.73.405.38, that what i used
http://android.modaco.com/content/h...-24-11-hero-roms-radios-in-update-zip-format/
use the rooted htc generic 2.73.405.38, that what i used
http://android.modaco.com/content/h...-24-11-hero-roms-radios-in-update-zip-format/
How do I install it when its not an RUU file?
ohh my mistake, i used the same method as you look on here
http://forum.xda-developers.com/showthread.php?t=573866
20. Use the Official HTC RUU to downgrade to 2.73.405.5 here ftp://xda:[email protected]/Hero...ed_NoDriver.exe
Click to expand...
Click to collapse
worked perfectly for me
You're using a tmobile G2 Touch right? I'm sure I tried this and it brought up the [131] customer ID error lol.. I'll try again though Thanks
yep i am, long story short i had a problem with and i had to apply the official so i could send it back to tmob for repair and once i got it back, i started to follow the video done by lockr and i got the [131] customer ID error when trying to use stock (1.73) ruu, saw the forum post use that ruu worked perfectly
I still got [131] error...
Where did you find the stock (1.73) RUU? The only one I can find is the 2.73, which is my current one.
i didn't use the 1.73 ruu, i used the 2.73 and i used that ruu i'm sorry that i can't help you :-(
Arr okay no worries I'll just wait until the 2.1 rom is released and hope that has some holes in! Thanks for trying
How about one of the first 2 RRUs from this page?
http://forum.xda-developers.com/showthread.php?t=559622
None of the WWE RUU's seem to work... Only the tmobile one :/
Sounds like the goldcard isn't working properly
It is what makes any old RRU work, as it disables the Carried ID check which means only T-Mobile RRUs work for you. Seems strange...
Personally, I'd try making the goldcard again.
Yea I made the Goldcard twice on the same SD, so maybe its the SD card thats the problem... I try using some others I have somewhere
Iirc, the default micro SD card (2gn) that came with the phone works correctly. I've had a think and I reckon the goldcard is definitely the problem, as a working goldcard will accept any try file, such as the one I referenced before.
Give that a shot and if you have trouble, just try other cards until it works, but I reckon the stock card is your best bet for now. The HTC 1.73 rru should work after that.
I never recieved the stock 2gb card as I bought off an eBay seller...
But lucikily I had one lying about and created the goldcard and loaded the WWE RUU sucessfully, Thanks for your advice!
Does unlocking the bootloader cause problems with downloading OTAs? Also, is it possible to pull the update file from someone's phone and update through the recovery? I don't know if this is all the same as it is on the OG Droid.
You'll have to relock in order to get the full update (radios ect.). Which means the re-unlock will factory reset you. But if you want to do it manually here are files and instructions: http://forum.xda-developers.com/showthread.php?t=1467329
I had some troubles with that, but got it to take on the second try. As noted in the first post of that thread, you can also grab the new RUU and it'll take you to factory fresh with the OTA. Make sure you backup though, I know RUU wipes the internal SD and it may wipe external as well.
A2Aegis said:
Does unlocking the bootloader cause problems with downloading OTAs? Also, is it possible to pull the update file from someone's phone and update through the recovery? I don't know if this is all the same as it is on the OG Droid.
Click to expand...
Click to collapse
If you want just the update file you can download it and then grab it before you let it install.
The file is called OTAPkg.zip and should be in /cache/fumo. You can just download it and postpone the install then move it out to somewhere where you can always use it at a later date.
But you have to relock and unlock regardless of which method you use to update.
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.