Related
I've searched and searched and can't find this topic so here goes...
I have the DE and it is rooted. I'd like to install the OTA as I'm still running stock otherwise. Do I have to unroot to get it to install? For fun I tried loading it with CWM and that just locked it up.
Thoughts or threads I've missed?
im curious too :/ the only way i could update was unrooting and for that the only way i could do so, was restoring a backup from CWM, i couldnt falsha RUU or ZIP :/
would be great if some one help us to find out how to unroot (an easier way) or apply OTA even rooted (guess this is not possible :/)
eltoffer said:
im curious too :/ the only way i could update was unrooting and for that the only way i could do so, was restoring a backup from CWM, i couldnt falsha RUU or ZIP :/
would be great if some one help us to find out how to unroot (an easier way) or apply OTA even rooted (guess this is not possible :/)
Click to expand...
Click to collapse
As far as I know, OTA should work fine if you have ONLY rooted and NOT installed any custom recovery. So I believe restoring stock recovery could make your phone receive the OTA. I could be wrong too.
shahul_555 said:
As far as I know, OTA should work fine if you have ONLY rooted and NOT installed any custom recovery. So I believe restoring stock recovery could make your phone receive the OTA. I could be wrong too.
Click to expand...
Click to collapse
Hmmm then I'm a bit confused, I believe I have stock recovery installed, I haven't done anything other than backup and root. I just tried running the update from the prompt and it sends me to CWM. Maybe I'm misunderstanding what stock recovery is?
thepktrckt said:
Hmmm then I'm a bit confused, I believe I have stock recovery installed, I haven't done anything other than backup and root. I just tried running the update from the prompt and it sends me to CWM. Maybe I'm misunderstanding what stock recovery is?
Click to expand...
Click to collapse
CWM is a custom recovery, hence why it's not working
Sent from my Nexus 4 using xda premium
EddyOS said:
CWM is a custom recovery, hence why it's not working
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
D'oh! My bad.
In attempt to get the stock recovery back I've tried the RUU that should be for the 64GB DE edition but it keeps throwing an error. Is Brightstar US WWE RUU 3.4.10 v4.1 1.29.1540.3 the wrong one?
thepktrckt said:
D'oh! My bad.
In attempt to get the stock recovery back I've tried the RUU that should be for the 64GB DE edition but it keeps throwing an error. Is Brightstar US WWE RUU 3.4.10 v4.1 1.29.1540.3 the wrong one?
Click to expand...
Click to collapse
First things first is your phone the developer edition? Sorry to ask a silly question just want to make sure you are not trying to flash the wrong firmware to your phone.
You can find the stock recovery under the development thread and you can flash this with fastboot flash recovery recovery.img (in fastboot mode of course)
for a DE, you have to lock its bootloader and then using RUU to get it back to stock, or just fastboot flash the stock recoery image to override your custom recovery, both are working to update OTA according to my test.
Sent from my HTC One using xda app-developers app
I posted this in another section a couple days ago on how I did the OTA with my DE.
Now you do have to push a stock recovery to get it working but then after you load the OTA you can go back and push TWRP or CWM. I then reflashed supersu but not sure if I needed to or not.
You don't need to lock the bootloader on the DE edition.
MG
moregadget said:
I posted this in another section a couple days ago on how I did the OTA with my DE.
Now you do have to push a stock recovery to get it working but then after you load the OTA you can go back and push TWRP or CWM. I then reflashed supersu but not sure if I needed to or not.
You don't need to lock the bootloader on the DE edition.
MG
Click to expand...
Click to collapse
relocking bootloader is needed for the RUU way, for reflashing stock recovery way, it is not necessary.
Sent from my HTC One using xda app-developers app
zhangke said:
relocking bootloader is needed for the RUU way, for reflashing stock recovery way, it is not necessary.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I don't understand why you'd have to lock a bootloader for a device that came with it unlocked from the factory? Even the ruu from HTC for the DE requires you to lock the bootloader?
MG
moregadget said:
I don't understand why you'd have to lock a bootloader for a device that came with it unlocked from the factory? Even the ruu from HTC for the DE requires you to lock the bootloader?
MG
Click to expand...
Click to collapse
Actually I don't understand either, but it is true, I failed several times to use RUU gettting back stock before re-locking my DE, I guess HTC developer does not apply any special code for the DE RUU program, you can have a try if you have a chance to do so.
Dang I already relocated and RUU'd it... Oh well next time.
Thanks though!!
Sent from my Nexus 4 using xda app-developers app
Hi, I have an Unlocked 32GB HTC One (BS_US001) and I'm having a hard time trying to find info about stock recoveries.
My phone currently is on stock 4.1.2, bootloader unlocked, S-Off and rooted. I was using the TWRP recovery, used to root my phone. Since the 4.3 update came out, I was searching for the stock recovery to proceed with the update, but too many different files seems to exist. I just want to install the right recovery and apply the 4.3 update, no full ROM flash.
Yesterday I flashed this recovery file (9MB) and got icons similar of those on the right of this image.
Today, I flashed this one (7.9MB) and got something like this, the little android icon.
Later, I've found another one (9.8MB).
Edit: and another one, a few bytes shorter than the third.
But now I'm little afraid of flashing again, just for the sake of it.
So, first of all, which one is the right file for my phone (yet another one)?
Second, I flash recoveries through fastboot command line (fastboot flash recovery recovery.img). Can this method and command brick my phone?
Third, how the stock recovery behaves on your phone? Both times, when I flashed the files and entered in recovery mode, my phone would boot 2 or 3 times straight into recovery mode again, until it boot itself properly, into the system. Also, recovery mode goes from the green to the red icon and awaits until I reboot the phone again.
Thanks in advance.
Final edit: For the sake of others lost in the lack of good info, I'm editing this old post.
I found some crap advices here and there. One of them was the need to relock the bootloader to accept OTAs. It doesn't make any sense, but if you are seeking help, you will take **** as good advice. Don't do it.
Another bad advice was about the stock recovery. Just open the last update you got (Downloads folder on your phone or get the OTA from HTC website) and extract the recovery.img file. Flash it and you have the proper stock recovery for your phone.
All of this is about the stock HTC One - no custom roms, no xposed changes, nothing. The only thing I did prior to this was to flash TWRP and root. That's how I want my phone for now - stock with root.
I kind of went through this today. Ended up just wiping it, running a RUU and reapplying OTAs.
I'll tell you this… after I went through this I attempted to salvage the stock recovery before rerooting etc. I was stuck trying to get fastboot to boot a recovery instead of flash one. I did find an alternate way to harvest the recovery. I got it out of the ota. I'm not done testing it yet, but my phone was still showing tampered. Flashed cwr and called it a day at that point
Sent from my HTC One
Thank you for your answer. I'm trying to avoid the whole RUU thing, but I'll keep it as a last resource, for sure. Also, I'm trying to understand more about this piece of software called recovery.
The one I sent you is pulled directly from stock 1.29.1540.16 for Dev. edition, which comes with an unlocked bootloader as well. Also, it's signed, which will allow it to be flashed whether you're s-on or off. Assuming your MID is PN0712000, with CID BS_US001, this recovery is your stock and will work. Hope it helps.
kibmikey1 said:
The one I sent you is pulled directly from stock 1.29.1540.16 for Dev. edition, which comes with an unlocked bootloader as well. Also, it's signed, which will allow it to be flashed whether you're s-on or off. Assuming your MID is PN0712000, with CID BS_US001, this recovery is your stock and will work. Hope it helps.
Click to expand...
Click to collapse
I've been running into similar issues. For the previous 2 OTA's (1540.3 --> 1540.16 & 1540.16 --> 1540.17), simply reflashed stock recovery, ran the OTA, it updated, then I flashed TWRP again. For the most recent OTA (3.22.1540.1, I think), that seems to not be working, but I can't seem to find the right recovery. I've found 1540.3's recovery, but not 1540.16 (or .17 if there was a new recovery in that OTA). Where did you end up finding it?
Thanks!
bjg222 said:
I've been running into similar issues. For the previous 2 OTA's (1540.3 --> 1540.16 & 1540.16 --> 1540.17), simply reflashed stock recovery, ran the OTA, it updated, then I flashed TWRP again. For the most recent OTA (3.22.1540.1, I think), that seems to not be working, but I can't seem to find the right recovery. I've found 1540.3's recovery, but not 1540.16 (or .17 if there was a new recovery in that OTA). Where did you end up finding it?
Thanks!
Click to expand...
Click to collapse
I pulled it directly from my decrypted RUU zip of 1540.16.
Here, there are some of stock recovery.
Check if there is the right version for you.
You have to check the versionmain on your phone
kibmikey1 said:
I pulled it directly from my decrypted RUU zip of 1540.16.
Click to expand...
Click to collapse
Would you be willing to share it? I haven't found a decrypted version of the 1540.16 RUU since Bugsy's hosting server stopped hosting downloads (The new thread only has 1540.3 last I checked).
Guich said:
Here, there are some of stock recovery.
Check if there is the right version for you.
You have to check the versionmain on your phone
Click to expand...
Click to collapse
Thanks, looks like for the dev edition, those sites only have the new recovery from the Android 4.3 updated (3.22.1540.1), though
bjg222 said:
Thanks, looks like for the dev edition, those sites only have the new recovery from the Android 4.3 updated (3.22.1540.1), though
Click to expand...
Click to collapse
Is the 3.22 in the folder
Guich said:
Is the 3.22 in the folder
Click to expand...
Click to collapse
In the Dev Edition folder, 3.22 is all that's there. Have you had any luck finding the 1.29.1540.16 recovery? That's the one I need.
bjg222 said:
In the Dev Edition folder, 3.22 is all that's there. Have you had any luck finding the 1.29.1540.16 recovery? That's the one I need.
Click to expand...
Click to collapse
1.29.1540.16 Developer Edition signed stock recovery.
Has anyone else flashed stock recovery while on custom ROM? I was pleasantly surprised to discover my SD card was wiped Is this normal, and was there some way I could have figured out this was what was going to happen? I don't really understand what stock recovery does/is for. The only other time I'd flashed stock recovery was after restoring to stock ROM from nandroid.
kibmikey1 said:
1.29.1540.16 Developer Edition signed stock recovery.
Click to expand...
Click to collapse
Awesome, thanks!
bjg222 said:
Awesome, thanks!
Click to expand...
Click to collapse
Have you had any luck with this? I have a DE 64gb and I'm in the same situation you were/are, I'm on stock recovery but I can't accept the OTA unlike the other 4.1.2 ones. Always gets stuck on the red triangle !.
arikah said:
Have you had any luck with this? I have a DE 64gb and I'm in the same situation you were/are, I'm on stock recovery but I can't accept the OTA unlike the other 4.1.2 ones. Always gets stuck on the red triangle !.
Click to expand...
Click to collapse
If you're rooted, unroot through SU, then do a factory reset and try it again.
kibmikey1 said:
If you're rooted, unroot through SU, then do a factory reset and try it again.
Click to expand...
Click to collapse
I haven't been rooted since one of the last 4.1.2 updates, because that's when I went back to stock recovery. I was able to accept those OTA packs, why is this one different? I'm really trying to save factory resets or RUU's for the absolute last ditch effort, in fact I'm more likely to stick with 4.1.2 until I can find a way to do this.
help
I have att htc one dev edition, its in soft brick state and i cny get it to do anything, i have tried running the recovery kit, and that get to the end then error 131...
could somebody please suggest some help for me please, thanks in advance
Hello, I have HTC One Intl (see my signature) on everything stock. Phone is S-off and rooted. Yesterday I had seen 4.3 OTA notification, downloaded it and tried to install, but installation failed in recovery (red triangle with exclamation). I've tried it several times, but no luck - phone reboots to recovery, installation process begins and fails at ~30 per cent.
Help me find out, why it happens (maybe i can find installation log somewhere, but don't know where to search) and how to install this update.
You need:
- Stock Recovery
- Stock rom without root
- Locked/Relocked bootloader
After your phone can install the OTA.
Guich said:
You need:
- Stock Recovery
- Stock rom without root
- Locked/Relocked bootloader
After your phone can install the OTA.
Click to expand...
Click to collapse
Recovery is stock.
Can I use Voodoo OTA Rootkeeper to temporary unroot? At least it gives such possibility, don't know will it work or not.
Is locked/relocked bootloader obligatory? if yes, I will search how to relock it again.
Thanks.
valery.m said:
Hello, I have HTC One Intl (see my signature) on everything stock. Phone is S-off and rooted. Yesterday I had seen 4.3 OTA notification, downloaded it and tried to install, but installation failed in recovery (red triangle with exclamation). I've tried it several times, but no luck - phone reboots to recovery, installation process begins and fails at ~30 per cent.
Help me find out, why it happens (maybe i can find installation log somewhere, but don't know where to search) and how to install this update.
Click to expand...
Click to collapse
Guich said:
You need:
- Stock Recovery
- Stock rom without root
- Locked/Relocked bootloader
After your phone can install the OTA.
Click to expand...
Click to collapse
Dont mean to intrude, but I'm pretty sure he can leave the bootloader unlocked, even root I think
He does need to have stock recovery, stock rom (including the preloaded apps that get deleted when unlocking), I think that's about it.
valery.m said:
Recovery is stock.
Can I use Voodoo OTA Rootkeeper to temporary unroot? At least it gives such possibility, don't know will it work or not.
Is locked/relocked bootloader obligatory? if yes, I will search how to relock it again.
Thanks.
Click to expand...
Click to collapse
I don't know i never used this app.
Yeah, probably bootloader relocked is necessary
nkk71 said:
Dont mean to intrude, but I'm pretty sure he can leave the bootloader unlocked, even root I think
He does need to have stock recovery, stock rom (including the preloaded apps that get deleted when unlocking), I think that's about it.
Click to expand...
Click to collapse
Mate i have a friend that with s-off needed a relocked bootloader for OTA.
I'm not sure.
but i think is better upgrading with a flash or firmware and rom.
Guich said:
I don't know i never used this app.
Yeah, probably bootloader relocked is necessary
Mate i have a friend that with s-off needed a relocked bootloader for OTA.
I'm not sure.
but i think is better upgrading with a flash or firmware and rom.
Click to expand...
Click to collapse
Hey @Guich, I personally havent tried, but did some searching a while back (while helping someone with a similar problem), and I think it did work with unlocked bootloader, I also just found this: http://forum.xda-developers.com/showthread.php?t=2306880
nkk71 said:
Hey @Guich, I personally havent tried, but did some searching a while back (while helping someone with a similar problem), and I think it did work with unlocked bootloader, I also just found this: http://forum.xda-developers.com/showthread.php?t=2306880
Click to expand...
Click to collapse
Will take a look
However, i think is easier update with a firmware flash and flash of rom.
He have the s-off...
Why turn to stock for rooted another time?
Guich said:
Will take a look
However, i think is easier update with a firmware flash and flash of rom.
He have the s-off...
Why turn to stock for rooted another time?
Click to expand...
Click to collapse
You're right :good: With s-off, so no problems locking/unlocking etc
@nkk71 Thanks for thread, I will try to restore that APKs and flash OTA again.
valery.m said:
@nkk71 Thanks for thread, I will try to restore that APKs and flash OTA again.
Click to expand...
Click to collapse
make sure the "preload" apps are for your version, mate!!
If you signature is correct: "ROM: Stock 2.24.401.8 (Android 4.2.2)" Maybe just best to use the Guru Reset ROM.
EDIT: I recommend full backup to PC first though, just in case!!
Guich said:
Will take a look
However, i think is easier update with a firmware flash and flash of rom.
He have the s-off...
Click to expand...
Click to collapse
I want phone to do it itself It can "see" the OTA update - so let it to flash! :laugh:
nkk71 said:
make sure the "preload" apps are for your version, mate!!
If you signature is correct: "ROM: Stock 2.24.401.8 (Android 4.2.2)" Maybe just best to use the Guru Reset ROM.
EDIT: I recommend full backup to PC first though, just in case!!
Click to expand...
Click to collapse
Yes, of course, i will search apps for my ROM version and backup it to PC before doing anything.
Signature is correct, i've taken it from fastboot screen.
valery.m said:
Yes, of course, i will search apps for my ROM version and backup it to PC before doing anything.
Signature is correct, i've taken it from fastboot screen.
Click to expand...
Click to collapse
fastboot screen only shows your firmware, you also need a stock ROM (you can check which version you have in Settings -> About -> etc.)
nkk71 said:
fastboot screen only shows your firmware, you also need a stock ROM (you can check which version you have in Settings -> About -> etc.)
Click to expand...
Click to collapse
Same version there
ROM is stock, it was updated via OTAs from 4.1.2 to 4.2.2. All was fine.
Only my customization is rooting, s-off and unlocking bootloader.
valery.m said:
Same version there
Click to expand...
Click to collapse
then you may just be missing the "preloaded" apps, here's an idea, why not dirty flash (ie no WIPE) the Guru Reset ROM: http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
BTW: the reason I mentioned the backup to PC, is one time I flashed stock recovery (and accessed it), and i was unpleasantly surprised it wiped my internal storage.
nkk71 said:
then you may just be missing the "preloaded" apps, here's an idea, why not dirty flash (ie no WIPE) the Guru Reset ROM: http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
BTW: the reason I mentioned the backup to PC, is one time I flashed stock recovery (and accessed it), and i was unpleasantly surprised it wiped my internal storage.
Click to expand...
Click to collapse
Thanks for the idea, i will try it!
valery.m said:
Thanks for the idea, i will try it!
Click to expand...
Click to collapse
Good luck, and if you do (and wanna help the rest of the community) can you try with both ROOT and unlocked bootloader first, and see if it works.
I know it's a bit of a hassle but at least you would be able to confirm if ROOT or unlocked bootloader are interfering with the update
unlocked bootloader will not interfere with ota,did it myself
sent from my s-off 801n M7_UL
steelmaggot said:
unlocked bootloader will not interfere with ota,did it myself
sent from my s-off 801n M7_UL
Click to expand...
Click to collapse
Can you describe the whole procedure?
Sorry guys, i'm not so patient - so flashed new firmware from OTA's zip archive, flashed TWRP and then flashed ARHD. I'm happy now
Hey, just seen that sense 6 will get pushed out beginning may 12th in canada. My question is that my phone has an unlocked bootloader, is rooted, but not s-off. I havn't installed a new rom. has the same as after i unlocked bootloader. Will I be able to install the update when it is pushed?
Howie3045 said:
Hey, just seen that sense 6 will get pushed out beginning may 12th in canada. My question is that my phone has an unlocked bootloader, is rooted, but not s-off. I havn't installed a new rom. has the same as after i unlocked bootloader. Will I be able to install the update when it is pushed?
Click to expand...
Click to collapse
Until you have the stock recovery ...you can install the update when it is pushed
As you've stated that you phone is rooted then you might've flashed TWRP or CWM to do it so
flash back the stock recovery of your model and you are good to go...
Did you unlock via htcdev ?
Sent from my HTC_PN071 using Tapatalk
I have twrp and did unlocked via HTC dev
Sent from my HTC One using XDA Free mobile app
i have the latest hboot as well. i didnt actually unlock and root until after the last OTA update.
Howie3045 said:
Bell Canada HTC One, want to flash the stock recovery back so that i can get the Sense 6 update. Phone is rooted and unlocked with HTC dev but does not have S-off. been running into issues with hboot 1.56 in that regard and cant get S-off to work. Anyway. From what I gather the OTA update wont work without the stock recovery. How do I know which one to install
Click to expand...
Click to collapse
You need the stock recovery that match your fw version. I.e if you are on 3.23.666.1 then you need the recovery from this version.
Here is a collection of stock recovery. If you can't find yours, you can extract the recovery.img from the previous ota. The recovery packed in the upcoming ota update might also work.
my software number now says 4.19.666.8. im as up to date as i can be through bell so if i flash an old recovery will it cause problems? or will i just get an OTA update to bring it back to the latest version
Howie3045 said:
my software number now says 4.19.666.8. im as up to date as i can be through bell so if i flash an old recovery will it cause problems? or will i just get an OTA update to bring it back to the latest version
Click to expand...
Click to collapse
then flash the 4.19.666.8 stock recovery. an older recovery might work, not for sure. Or the recovery packed in the upcoming ota might also work.
I think I'm a little over my head now. Lol. I think I'm also missing some of the apps that were removed after the HTC dev unlock. Not good.
Sent from my HTC One using XDA Free mobile app
Howie3045 said:
I think I'm a little over my head now. Lol. I think I'm also missing some of the apps that were removed after the HTC dev unlock. Not good.
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
you'll probably have to restore these app if you want to update. The ota updater script md5 check these apps. If they are not on your phone, the ota installation will probably fail because of MD5 mismatch.
See this post from arhd if you want more details
Ota update will not apply until and unless you have pure stock rom.
e.g. If your phone is pure stock you unlock its bootloader it will remove some apps which are installed in preload. Now if you relock the bootloader and flash stock recovery the ota update will not be applied as during flashing ota update check for these apps whether they are installed in preload or not. For ota updates to applied succesfully you need to run RUU of your model then flash ota.
Sent from my HTC One using XDA Premium 4 mobile app
asking me to do the update now. im really not sure what exactly i need to do to get it now
alright ive found a nandroid backup for bell 3.23.666.1 and i also have the recovery to go with it. if i run that nandroid and flash the recovery do ya'll think i can then get the OTA?
alright i tried this any couldnt get it to work. i flashed the recovery then rebooted phone. it asked to do the 4.19.666.8 update then rebooted, went to recovery but it was still TWRP recovery and not stock. so before getting to far involved i reflashed the nandroid i made this morning.
the whole not being able to s-off with hboot 1.56 is a bit of a pain. ive tried rumrunner and firewater with no luck.
so troubleshooting purposes i should add that i dont care about the tampered bar or anything like that. i dont have to send it back i just want the sense 6 ota. l
Howie3045 said:
alright i tried this any couldnt get it to work. i flashed the recovery then rebooted phone. it asked to do the 4.19.666.8 update then rebooted, went to recovery but it was still TWRP recovery and not stock. so before getting to far involved i reflashed the nandroid i made this morning.
the whole not being able to s-off with hboot 1.56 is a bit of a pain. ive tried rumrunner and firewater with no luck.
so troubleshooting purposes i should add that i dont care about the tampered bar or anything like that. i dont have to send it back i just want the sense 6 ota. l
Click to expand...
Click to collapse
I already told you run ruu of your phone. Then you will be able to apply ruu.
Sent from my HTC One using XDA Premium 4 mobile app
Unfortunately a RUU of 4.19.666.8 is hard to come by
Howie3045 said:
Unfortunately a RUU of 4.19.666.8 is hard to come by
Click to expand...
Click to collapse
I haven't seen one yet, the CWR backup was the best I could find.
Maybe someone who has Sense 6 will make and upload a TWRP or CWR backup.
Howie3045 said:
alright i tried this any couldnt get it to work. i flashed the recovery then rebooted phone. it asked to do the 4.19.666.8 update then rebooted, went to recovery but it was still TWRP recovery and not stock
Click to expand...
Click to collapse
Then you didn't flash stock recovery... Either the recovery you flashed was not stock, or you didn't flash it right.
Now that I think about it after the flash it didn't do anything so I had to hold the power for 10 seconds. After that I panicked and just reverted back to my nandroid from that morning.
Sent from my HTC One using XDA Free mobile app
Pretty much what it says in the title. I want to install MaximusHD and try out cm13 but I don't accidentally want to install a ROM that isn't supported. Thanks.
Oh and, I don't have S-OFF, Unlocked Bootloader, TWRP and currently running the Deodexed Tmobile rom from this forum.
TheFatDemon said:
Pretty much what it says in the title. I want to install MaximusHD and try out cm13 but I don't accidentally want to install a ROM that isn't supported. Thanks.
Oh and, I don't have S-OFF, Unlocked Bootloader, TWRP and currently running the Deodexed Tmobile rom from this forum.
Click to expand...
Click to collapse
No, You need to be S-off to flash the MM firmware and also need to super cid.
kc6wke said:
No, You need to be S-off to flash the MM firmware and also need to super cid.
Click to expand...
Click to collapse
What exactly is Super CID? I'm still pretty new to rooting on HTC so I'm not too sure about these kind of things.
TheFatDemon said:
What exactly is Super CID? I'm still pretty new to rooting on HTC so I'm not too sure about these kind of things.
Click to expand...
Click to collapse
Cid is your carrier ID. T-Mobile is T-MOB010
When you super Cid, what it does is change that to all ones (11111111) which allows you to be able to flash other carriers firmware to your device.
Then you can flash other carriers roms.
To flash the latest Maximus, which is Marshmallow, since T-Mobile does not yet have the firmware for it , we need to flash the International firmware for Marshmallow.
Also to flash the International firmware, we need to make sure the MID (model ID) matches your device MID which is in the android-info.txt in the firmware zip. For T-Mobile its 0PJA12000.
Here is a guide that might help.
I suggest you do some research on this before attempting it.
Hope this helps
kc6wke said:
Cid is your carrier ID. T-Mobile is T-MOB010
When you super Cid, what it does is change that to all ones (11111111) which allows you to be able to flash other carriers firmware to your device.
Then you can flash other carriers roms.
To flash the latest Maximus, which is Marshmallow, since T-Mobile does not yet have the firmware for it , we need to flash the International firmware for Marshmallow.
Also to flash the International firmware, we need to make sure the MID (model ID) matches your device MID which is in the android-info.txt in the firmware zip. For T-Mobile its 0PJA12000.
Here is a guide that might help.
I suggest you do some research on this before attempting it.
Hope this helps
Click to expand...
Click to collapse
So do we have to edit the android-info.txt to have modelid: 0PJA12000? or just as long as we have the right CID?
TheFatDemon said:
So do we have to edit the android-info.txt to have modelid: 0PJA12000? or just as long as we have the right CID?
Click to expand...
Click to collapse
Yes, I had to change it for it to flash.
kc6wke said:
No, You need to be S-off to flash the MM firmware and also need to super cid.
Click to expand...
Click to collapse
I'm sort of in the same boat and have been trying to find an answer. I have an unlocked bootloader, but no S-OFF. I would like to try a custom LP rom, would I still be able to install one without changing from the 2.11.531.19 firmware?
shmyset said:
I'm sort of in the same boat and have been trying to find an answer. I have an unlocked bootloader, but no S-OFF. I would like to try a custom LP rom, would I still be able to install one without changing from the 2.11.531.19 firmware?
Click to expand...
Click to collapse
You can definitely install the LP ROMs. I used Candy 5 without any issues.
TheFatDemon said:
You can definitely install the LP ROMs. I used Candy 5 without any issues.
Click to expand...
Click to collapse
Thanks. The other issue I'm having is backing up my stock recovery, I tried the "fastboot boot twrp.img" while in download mode, but my phone just shows that the img downloaded 100%, but it just hangs after that and doesn't actually boot into TWRP. I've tried looking for a stock recovery on XDA for my CID (T-MOB010), but I haven't had any luck.
shmyset said:
Thanks. The other issue I'm having is backing up my stock recovery, I tried the "fastboot boot twrp.img" while in download mode, but my phone just shows that the img downloaded 100%, but it just hangs after that and doesn't actually boot into TWRP. I've tried looking for a stock recovery on XDA for my CID (T-MOB010), but I haven't had any luck.
Click to expand...
Click to collapse
I honestly can't help ya there. I didn't know about doing that before I installed a custom recovery and now I'm just like, eh, oh well.
shmyset said:
Thanks. The other issue I'm having is backing up my stock recovery, I tried the "fastboot boot twrp.img" while in download mode, but my phone just shows that the img downloaded 100%, but it just hangs after that and doesn't actually boot into TWRP. I've tried looking for a stock recovery on XDA for my CID (T-MOB010), but I haven't had any luck.
Click to expand...
Click to collapse
Here is the stock recovery for 2.11.531.19
kc6wke said:
Here is the stock recovery for 2.11.531.19
Click to expand...
Click to collapse
Thank you!
kc6wke said:
Here is the stock recovery for 2.11.531.19
Click to expand...
Click to collapse
Thank you!
kc6wke said:
Here is the stock recovery for 2.11.531.19
Click to expand...
Click to collapse
I flashed this via fastboot, but when I reboot into it I'm seeing the phone graphic graphic a red triangle+exclamation point. I rebooted and tried to update to marshmallow, but it keeps failing with that same graphic after 20%. Any thoughts as to why this may be happening?