Related
Hi everyone!
I recently unlocked my bootloader and rooted my m8.
I tried using firewater to "s-off" my phone and unfortunately, it did not work out. The way I understand it, I cannot install stock ROMs (such as the 5.0.1 GPE) without "s-off." Now, I want to unroot my phone and stick to waiting for the OTAs to roll out instead.
I followed the instructions in the "returning to stock" thread and noticed that I have no version main (see attached image). I looked around the forums and saw that the advice was to flash the latest TWRP version. Since I'm stuck with a phone that I cannot update, I'm trying to be careful now. Can anyone please confirm if flashing the latest TWRP will bring my version main back?
The noob in me also has a few questions/requests as well:
1. Since my phone is rooted, I cannot receive OTA updates and upgrade to lollipop once these updates roll out?
2. Please tell me which files to download to return to stock. Just trying to be really careful this time around.
3. Lastly, is it also true that I can only install custom ROMs once have rooted? As to stock ROMs, I can't install them until I get "s-off"?
Thanks a lot, everyone! Cheers!
panchizzles said:
Hi everyone!
I recently unlocked my bootloader and rooted my m8.
I tried using firewater to "s-off" my phone and unfortunately, it did not work out. The way I understand it, I cannot install stock ROMs (such as the 5.0.1 GPE) without "s-off." Now, I want to unroot my phone and stick to waiting for the OTAs to roll out instead.
I followed the instructions in the "returning to stock" thread and noticed that I have no version main (see attached image). I looked around the forums and saw that the advice was to flash the latest TWRP version. Since I'm stuck with a phone that I cannot update, I'm trying to be careful now. Can anyone please confirm if flashing the latest TWRP will bring my version main back?
The noob in me also has a few questions/requests as well:
1. Since my phone is rooted, I cannot receive OTA updates and upgrade to lollipop once these updates roll out?
2. Please tell me which files to download to return to stock. Just trying to be really careful this time around.
3. Lastly, is it also true that I can only install custom ROMs once have rooted? As to stock ROMs, I can't install them until I get "s-off"?
Thanks a lot, everyone! Cheers!
Click to expand...
Click to collapse
Your firmware version: 3.32.708.4
I got it from your radio (baseband) number.
xunholyx said:
Your firmware version: 3.32.708.4
I got it from your radio (baseband) number.
Click to expand...
Click to collapse
Thanks for the reply!
Do I have to flash the latest TWRP version before proceeding?
Hey guys, I was rooted but on my stock 4.4.2 Sense Rom. I wanted to flash the OTA lollipop update. I had TWRP so i could not update the OTA. So i found a video on youtube that said i had to...
1 - Replace custom recovery with stock recovery
2 - Process OTA Update
3 - Replace stock recovery with custom recovery
I was at step 2 and my htc one m8 is tmobile US and was T-MOB010 so i downloaded "stock+recovery+1.12.531.19+recovery" there was two different ones for me to choose from. There was that one and then "2.22.531.5" however i could not find that DL link. I then flashed the stock recovery thru ADB and rebooted my phone, and it started to update but then i got a red triangle. I saw a comment on the youtube video that said i needed to find the OTA update and transfer to my PC and find the "recovery.img" file and then extract that and flash that to my phone. I looked thru the entire zip file however there is a folder i could not access, the last one named "firmware" I try to extract but i get an error message saying "cannot open, file is invalid" The OTA update i found in my internal storage in download folder and it is named "OTA_M8_UL_L50_SENSE60_MR_TMOUS_4.20.531.4-3.32.531.2_release_420432xio08y7xuups2gkl" that's got to be it because that's the only thing that could be the update any help??
youtube video: https://www.youtube.com/watch?v=PPPT5J8xG6w
Thread i was going off: http://forum.xda-developers.com/show....php?t=2701376
jfreshh330 said:
Hey guys, I was rooted but on my stock 4.4.2 Sense Rom. I wanted to flash the OTA lollipop update. I had TWRP so i could not update the OTA. So i found a video on youtube that said i had to...
1 - Replace custom recovery with stock recovery
2 - Process OTA Update
3 - Replace stock recovery with custom recovery
I was at step 2 and my htc one m8 is tmobile US and was T-MOB010 so i downloaded "stock+recovery+1.12.531.19+recovery" there was two different ones for me to choose from. There was that one and then "2.22.531.5" however i could not find that DL link. I then flashed the stock recovery thru ADB and rebooted my phone, and it started to update but then i got a red triangle. I saw a comment on the youtube video that said i needed to find the OTA update and transfer to my PC and find the "recovery.img" file and then extract that and flash that to my phone. I looked thru the entire zip file however there is a folder i could not access, the last one named "firmware" I try to extract but i get an error message saying "cannot open, file is invalid" The OTA update i found in my internal storage in download folder and it is named "OTA_M8_UL_L50_SENSE60_MR_TMOUS_4.20.531.4-3.32.531.2_release_420432xio08y7xuups2gkl" that's got to be it because that's the only thing that could be the update any help??
youtube video: https://www.youtube.com/watch?v=PPPT5J8xG6w
Thread i was going off: http://forum.xda-developers.com/show....php?t=2701376
Click to expand...
Click to collapse
It sounds like the stock recovery that you loaded wasn't a new enough version. To update to lollipop you need to install a lollipop or a 4.4.X stock recovery. If you install anything that was released prior to that you will get the red triangle deal.
So try and find one thats a little newer. Perhaps see if someone has posted the lollipop one for your carrier. You can use that one. Should be easy to find as it's the latest. Then the OTA should take just fine. Perhaps the other stock one you mentioned would work. You just need to find it. I'm on Rogers in Canada so I'm not too familiar with the T-Mobile files. As mentioned though, just make sure the stock recovery is from Android 4.4.X or 5.X.X and you will be fine.
flexfulton said:
It sounds like the stock recovery that you loaded wasn't a new enough version. To update to lollipop you need to install a lollipop or a 4.4.X stock recovery. If you install anything that was released prior to that you will get the red triange deal.
So try and find one that a little newer. Perhaps see if someone has posted the lollipop one for your carrier. You can use that one. Should be easy to find as it's the latest. Then the OTA should take just fine. Perhaps the other stock one you mentioned would work. You just need to find it. I'm on Rogers in Canada so I'm not too familiar with the AT&T files. As mentioned though, just make sure the stock recovery in from Android 4.4.X or 5.X.X and you will be fine.
Click to expand...
Click to collapse
Thank you for the reply! Is there a chance of bricking by trying to change out the stock recovery? Or would the worst that would happen is I get the red triangle. I mean obviously I'm not going to be flashing stock recoverys from different devices but u know.
jfreshh330 said:
Thank you for the reply! Is there a chance of bricking by trying to change out the stock recovery? Or would the worst that would happen is I get the red triangle. I mean obviously I'm not going to be flashing stock recoverys from different devices but u know.
Click to expand...
Click to collapse
You mentioned stripping out the recovery.img from the OTA update. This shouldn't be a problem. Not sure why it wouldn't let you access it. Perhaps you have a bad download?
Look around XDA a little more. You should be able to find the OTA you are looking for.
As for flashing a wrong branded stock recovery, I don't really want to say cause I'm not sure what would happen. Just to be safe I'd stick to your carrier's files but perhaps someone else can speak on that.
---------- Post added at 08:00 AM ---------- Previous post was at 07:51 AM ----------
http://forum.xda-developers.com/showthread.php?t=2714456
That link will be of great help to you. Has the recovery you require (3.32.531.2 - I just downloaded it myself with no issues) and much discussion on the subject of OTA Lollipop updates etc for T-Mobile.
Let me know if you need anything else. If you still can't get it to work, those would be the guys to consult.
Happy flashing!
flexfulton said:
You mentioned stripping out the recovery.img from the OTA update. This shouldn't be a problem. Not sure why it wouldn't let you access it. Perhaps you have a bad download?
Look around XDA a little more. You should be able to find the OTA you are looking for.
As for flashing a wrong branded stock recovery, I don't really want to say cause I'm not sure what would happen. Just to be safe I'd stick to your carrier's files but perhaps someone else can speak on that.
Click to expand...
Click to collapse
So I was going to try and download the official Rom off the HTC website. I've found the download link for the Rom. 4.16.1540.8 do you really think of I just use the recovery. IMG file it will work?
flexfulton said:
You mentioned stripping out the recovery.img from the OTA update. This shouldn't be a problem. Not sure why it wouldn't let you access it. Perhaps you have a bad download?
Look around XDA a little more. You should be able to find the OTA you are looking for.
As for flashing a wrong branded stock recovery, I don't really want to say cause I'm not sure what would happen. Just to be safe I'd stick to your carrier's files but perhaps someone else can speak on that.
---------- Post added at 08:00 AM ---------- Previous post was at 07:51 AM ----------
http://forum.xda-developers.com/showthread.php?t=2714456
That link will be of great help to you. Has the recovery you require (3.32.531.2 - I just downloaded it myself with no issues) and much discussion on the subject of OTA Lollipop updates etc for T-Mobile.
Let me know if you need anything else. If you still can't get it to work, those would be the guys to consult.
Happy flashing!
Click to expand...
Click to collapse
Awesome thanks so much!
jfreshh330 said:
So I was going to try and download the official Rom off the HTC website. I've found the download link for the Rom. 4.16.1540.8 do you really think of I just use the recovery. IMG file it will work?
Click to expand...
Click to collapse
Sideload the latest recovery as found in the thread I linked to above. Reboot and the OTA should take no problems. It was downloading and everything fine for you before but was unable to flash because of an outdated recovery you installed.
So my recommened method to update OTA, is to follow the first route you were taking but with the newest recovery.img file in place of what you used in step 1.
If you already have the OTA downloaded on your phone, you shouldn't have to download it again either. It should see that it's already downloaded ready to be installed.
---------- Post added at 08:15 AM ---------- Previous post was at 08:13 AM ----------
jfreshh330 said:
Awesome thanks so much!
Click to expand...
Click to collapse
No problem. Let me know how it turns out for you.
If you don't mind wiping your personal data (you can of course back it up first,and restore later by a variety of methods) and setting up the phone again; it would be much easier to just update by RUU. Relocking the bootloader required if s-on.
The method of returning to stock ROM and recovery will work to update OTA. But its just a lot more potential pitfalls, as you have found (finding the right stock recovery, stock ROM, and even then there is no guarantee your data will be retained, although it should).
redpoint73 said:
If you don't mind wiping your personal data (you can of course back it up first,and restore later by a variety of methods) and setting up the phone again; it would be much easier to just update by RUU. Relocking the bootloader required if s-on.
The method of returning to stock ROM and recovery will work to update OTA. But its just a lot more potential pitfalls, as you have found (finding the right stock recovery, stock ROM, and even then there is no guarantee your data will be retained, although it should).
Click to expand...
Click to collapse
If you flash the stock recovery and let the OS do the OTA update there will be no issues. Relocking bootloaders etc sounds like a lot more work to me.
He is already on stock ROM and has the instructions to do the stock recovery OTA update so I think that's the best route. I provided him with the correct recovery so there should be no problems now.
Also I don't see how in any case doing an OTA would cause you to lose your data. People would have a S$%t fit if they lost data on OTA updates.
flexfulton said:
If you flash the stock recovery and let the OS do the OTA update there will be no issues. Relocking bootloaders etc sounds like a lot more work to me.
He is already on stock ROM and has the instructions to do the stock recovery OTA update so I think that's the best route. I provided him with the correct recovery so there should be no problems now.
Click to expand...
Click to collapse
Its a matter of opinion which approach is easier or "best". I just gave it as another option.
Relocking the bootloader is a single fastboot command. Yes, the OP would then need to unlock the bootloader again after the RUU.
On the other hand, the OTA approach requires flashing stock recovery, then installing 3 OTA updates in order to get up to Lollipop (opposed to just a single RUU that would take the OP up to LP).
flexfulton said:
Also I don't see how in any case doing an OTA would cause you to lose your data. People would have a S$%t fit if they lost data on OTA updates.
Click to expand...
Click to collapse
Its not "supposed" to happen. But I have seen it happen to folks, on more than a few occasions. And yes, those folk have a S$%t fit when it happens.
In any case, everyone should backup their data and be prepared to have to restore it (and its all that much easier on a phone that is already rooted). No data is immune from loss, even from day-to-day use, and all the more for a major system change like an OS update.
redpoint73 said:
Its a matter of opinion which approach is easier or "best". I just gave it as another option.
Relocking the bootloader is a single fastboot command. Yes, the OP would then need to unlock the bootloader again after the RUU.
On the other hand, the OTA approach requires flashing stock recovery, then installing 3 OTA updates in order to get up to Lollipop (opposed to just a single RUU that would take the OP up to LP).
Its not "supposed" to happen. But I have seen it happen to folks, on more than a few occasions. And yes, those folk have a S$%t fit when it happens.
In any case, everyone should backup their data and be prepared to have to restore it (and its all that much easier on a phone that is already rooted). No data is immune from loss, even from day-to-day use, and all the more for a major system change like an OS update.
Click to expand...
Click to collapse
Agreed backups are good.
Why 3 OTA updates? Is that a T-Mobile thing? I only had 1 when I made the jump on the Rogers network.
flexfulton said:
That link will be of great help to you. Has the recovery you require (3.32.531.2 - I just downloaded it myself with no issues) and much discussion on the subject of OTA Lollipop updates etc for T-Mobile.
Click to expand...
Click to collapse
The OP is presently on Android 4.4.2, which is software number 1.xx. He will need a recovery corresponding to 1.xx software, as he seems to have already figured out, but its not working.
---------- Post added at 09:53 AM ---------- Previous post was at 09:50 AM ----------
flexfulton said:
Agreed backups are good.
Why 3 OTA updates? Is that a T-Mobile thing? I only had 1 when I made the jump on the Rogers network.
Click to expand...
Click to collapse
Not just a T-Mob thing.
He is on Android 4.4.2 (software 1.x). Unless T-Mob skipped a software version (and I don't think they did) he needs to update in sequence to software 2.x, then 3.x, then finally up to the current 4.x.
OTAs need to be installed in sequence; opposed to RUUs which are complete factory images, so you can skip software numbers.
Not sure about Rogers. But my guess is that you only had to update from 4.4.4 to 5.0; or something to that effect.
redpoint73 said:
The OP is presently on Android 4.4.2, which is software number 1.xx. He will need a recovery corresponding to 1.xx software, as he seems to have already figured out, but its not working.
---------- Post added at 09:53 AM ---------- Previous post was at 09:50 AM ----------
Not just a T-Mob thing.
He is on Android 4.4.2 (software 1.x). Unless T-Mob skipped a software version (and I don't think they did) he needs to update in sequence to software 2.x, then 3.x, then finally up to the current 4.x.
OTAs need to be installed in sequence; opposed to RUUs which are complete factory images, so you can skip software numbers.
Not sure about Rogers. But my guess is that you only had to update from 4.4.4 to 5.0; or something to that effect.
Click to expand...
Click to collapse
Makes sense. I only had to go up one level. I figured that the carriers would package all of the older updates in with new one but apparently I'm wrong. I appologize.
I was trying to help out as I had the same issue when I went to update. I installed a recovery that was too old, determined that I needed to flash a recovery from either 4.4.X or lollipop and my OTA update was fine after that. Point being, I could go ahead and flash a newer recovery to get the OTA to download.
Anyway I applogize if I was in error in my help. No one else was helping and based on my own experiences it sounded like the same issue.
flexfulton said:
Makes sense. I only had to go up one level. I figured that the carriers would package all of the older updates in with new one but apparently I'm wrong. I appologize.
Click to expand...
Click to collapse
OTAs will normally only allow you to install from the immediate previous version (you cannot skip a version). Sometimes they are complete packages; but often they are not. Sometimes the OTA just contains what has been changed; basically a "patch". And for that reason, the updates need to be installed sequentially. In fact, I've seen folks brick due to unwittingly installing partial firmware packages from OTAs (with s-off, which bypasses such safety checks).
flexfulton said:
Anyway I applogize if I was in error in my help.
Click to expand...
Click to collapse
There's no need to apologize. As you are well aware, this is a self-supporting community that flourishes due to the contributions of its members. Your answers may not have been 100% correct. But it was well intended; and you answered to the best of your knowledge. At least you learned something and can pass it along now. I'm just a member who passes along what I've learned here also (don't have any specialized developer knowledge or anything); and I'm certainly not right all the time.
So the recovery 3.32.5312 will not work? And i apologize i am on 4.4.4 not 4.4.2
Hey everyone,
I have searched for quite a while and simply couldn't find a root method for my Canadian G4 running Marshmallow. If there is none, is it possible to downgrade? It doesn't seem to me like there is any root for any model running Marshmallow
Thanks,
Dan
Root is not available for the H812 on Marshmallow. Yes, you can downgrade to Lollipop and install root. However, you would lose all your data if you do this.
Check these posts for steps on flashing Lollipop back on your device:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
sleepy_76 said:
Root is not available for the H812 on Marshmallow. Yes, you can downgrade to Lollipop and install root. However, you would lose all your data if you do this.
Check these posts for steps on flashing Lollipop back on your device:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Click to expand...
Click to collapse
I can't find a link for Bell H812 20E. I don't mind downgrading from MM to LP.
h812 Marshmallow Root
magickarle said:
I can't find a link for Bell H812 20E. I don't mind downgrading from MM to LP.
Click to expand...
Click to collapse
Hi everyone,
I have been searching high and low for a proper method to root this otherwise useless device. Does anyone have a guide that actually works for them to obtain root on Bell LG G4 (h812) on Marshmallow?
I will downgrade if necessary, data loss is not an issue at this point.
I am also wanting to use alternate ROM if any are available for this device.
ON a separate note, is there another model of the LG G4 that is interchangable with the h812 that I can safely use it's ROMs and Root method, or does it HAVE to be specifically for the h812 model?
Thank Kindly!!
905jay said:
Hi everyone,
I have been searching high and low for a proper method to root this otherwise useless device. Does anyone have a guide that actually works for them to obtain root on Bell LG G4 (h812) on Marshmallow?
I will downgrade if necessary, data loss is not an issue at this point.
I am also wanting to use alternate ROM if any are available for this device.
ON a separate note, is there another model of the LG G4 that is interchangable with the h812 that I can safely use it's ROMs and Root method, or does it HAVE to be specifically for the h812 model?
Thank Kindly!!
Click to expand...
Click to collapse
The only way to root LG G4 on MM (for now) is to downgrade it to LP and then copy over a rooted image using DD command.
Thanks. Would you know where I could find a proper guide for bell h812? It's my daily driver ....
frolovvl said:
The only way to root LG G4 on MM (for now) is to downgrade it to LP and then copy over a rooted image using DD command.
Click to expand...
Click to collapse
So once you downgrade to lolipop and root, how can you bring it back to marshmellow?
Check this out and read EVERYTHING carefully ...
905jay said:
Thanks. Would you know where I could find a proper guide for bell h812? It's my daily driver ....
Click to expand...
Click to collapse
Check this out and read EVERYTHING carefully (EVERYTHING you need is there) ... [Canadian Guide] - Complete Source for the LG G4 H812. Linux VM/Root/Tools&Files: https://forum.xda-developers.com/g4/general/canadian-guide-complete-source-lg-g4-t3212449
Once done: then check this out for a custom recovery - [LOCKED][G4][TWRP][UNOFFICIAL] TWRP-in-FIsH for all locked G4 devices:
https://forum.xda-developers.com/g4/development/locked-twrpinfish-locked-g4-devices-t3573048
- use version 3 Beta 4 first, linked in post # 193: for me it has been the most stable:
Enjoy
S.
---------- Post added at 07:33 PM ---------- Previous post was at 07:19 PM ----------
BIG_BADASS said:
So once you downgrade to lolipop and root, how can you bring it back to marshmellow?
Click to expand...
Click to collapse
Use LGUP - NEW (https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803), re-install the stock Lollipop rom (kdz) you used (before flashing the rooted image you used to get root), then ... upgrade again with LGUP - NEW with the appropriate MM kdz (you can check here for that): https://lg-firmwares.com/lg-h812-firmwares/
Suggest you read the Canadian Guide referenced above, thoroughly as well.
S.
PS - Remember the Thanks button.
sdembiske said:
Check this out and read EVERYTHING carefully (EVERYTHING you need is there) ... [Canadian Guide] - Complete Source for the LG G4 H812. Linux VM/Root/Tools&Files: https://forum.xda-developers.com/g4/general/canadian-guide-complete-source-lg-g4-t3212449
Once done: then check this out for a custom recovery - [LOCKED][G4][TWRP][UNOFFICIAL] TWRP-in-FIsH for all locked G4 devices:
https://forum.xda-developers.com/g4/development/locked-twrpinfish-locked-g4-devices-t3573048
- use version 3 Beta 4 first, linked in post # 193: for me it has been the most stable:
Enjoy
S.
---------- Post added at 07:33 PM ---------- Previous post was at 07:19 PM ----------
Use LGUP - NEW (https://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803), re-install the stock Lollipop rom (kdz) you used (before flashing the rooted image you used to get root), then ... upgrade again with LGUP - NEW with the appropriate MM kdz (you can check here for that): https://lg-firmwares.com/lg-h812-firmwares/
Suggest you read the Canadian Guide referenced above, thoroughly as well.
S.
PS - Remember the Thanks button.
Click to expand...
Click to collapse
Thank you, this is just what I have been looking for. But do I need to install a custom recovery tool such as TWRP or CWM before I root it? Because the bootloader on the H812 is locked so who knows what flashing might do.
BIG_BADASS said:
So once you downgrade to lolipop and root, how can you bring it back to marshmellow?
Click to expand...
Click to collapse
There's no way to get it back to MM unless you in-root it and use OTA. Unfortunately on all G4 except European variant bootloader is locked and LG doesn't want to open that for us.
---------- Post added at 05:34 PM ---------- Previous post was at 05:33 PM ----------
BIG_BADASS said:
Thank you, this is just what I have been looking for. But do I need to install a custom recovery tool such as TWRP or CWM before I root it? Because the bootloader on the H812 is locked so who knows what flashing might do.
Click to expand...
Click to collapse
As you noticed, the BL is locked. Without unlocking it you'll not be able to install either custom recovery on H812.
You are WRONG ...
frolovvl said:
There's no way to get it back to MM unless you in-root it and use OTA. Unfortunately on all G4 except European variant bootloader is locked and LG doesn't want to open that for us.
---------- Post added at 05:34 PM ---------- Previous post was at 05:33 PM ----------
As you noticed, the BL is locked. Without unlocking it you'll not be able to install either custom recovery on H812.
Click to expand...
Click to collapse
Read the post regarding TWRP-in-Fish, it allows a custom recovery WITH a locked bootloader and has been tested by me on my H812, ReeS86 (who led the way on the H812) and many others with different models with locked bootloaders - do not proclaim what you do not know. You CAN restore back to MM by re-installing the stock Lollipop KDZ with LGUP - NEW and then, using LGUP - NEW again, upgrade back to MM stock provided you have the right KDZ. You cannot however, install a custom rom, as yet. It is being worked on, however, by steadfasterX, first on unlocked bootloaders, then on locked bootloaders ... with a little luck and a lot of his hard work we will have the ability at that point
Do your homework before making proclamations, please!
S.
---------- Post added at 10:59 PM ---------- Previous post was at 10:41 PM ----------
BIG_BADASS said:
Thank you, this is just what I have been looking for. But do I need to install a custom recovery tool such as TWRP or CWM before I root it? Because the bootloader on the H812 is locked so who knows what flashing might do.
Click to expand...
Click to collapse
No, No ... no - please read the posts in the links thoroughly ... you install TWRP-in-FisH AFTER u have got a rooted system image installed. YOU WILL NOT (repeating ad nauseam) BE ABLE TO INSTALL A CUSTOM ROM (at this point any way, until we have a successful efidroid port to a locked LG G4), as you will still have a locked bootloader. You will simply have a way to get back to where you have gotten to at any point in time and if you suffer a hardware bootloop you will be able to get back to where u were once your phone is repaired. And please note, if and when in TWRP (from the TWRP-in-FisH install), it asks you if u want to install TWRP, do not respond Yes - you will brick as it tries to install to your stock recovery partition which cannot be done with a locked bootloader.
Just read all the posts thoroughly, please.
Good Luck,
S.
Thank you Sir! you're right, you can install a body without a head...
sdembiske said:
Read the post regarding TWRP-in-Fish, it allows a custom recovery WITH a locked bootloader and has been tested by me on my H812, ReeS86 (who led the way on the H812) and many others with different models with locked bootloaders - do not proclaim what you do not know. You CAN restore back to MM by re-installing the stock Lollipop KDZ with LGUP - NEW and then, using LGUP - NEW again, upgrade back to MM stock provided you have the right KDZ. You cannot however, install a custom rom, as yet. It is being worked on, however, by steadfasterX, first on unlocked bootloaders, then on locked bootloaders ... with a little luck and a lot of his hard work we will have the ability at that point
Do your homework before making proclamations, please!
S.
---------- Post added at 10:59 PM ---------- Previous post was at 10:41 PM ----------
No, No ... no - please read the posts in the links thoroughly ... you install TWRP-in-FisH AFTER u have got a rooted system image installed. YOU WILL NOT (repeating ad nauseam) BE ABLE TO INSTALL A CUSTOM ROM (at this point any way, until we have a successful efidroid port to a locked LG G4), as you will still have a locked bootloader. You will simply have a way to get back to where you have gotten to at any point in time and if you suffer a hardware bootloop you will be able to get back to where u were once your phone is repaired. And please note, if and when in TWRP (from the TWRP-in-FisH install), it asks you if u want to install TWRP, do not respond Yes - you will brick as it tries to install to your stock recovery partition which cannot be done with a locked bootloader.
Just read all the posts thoroughly, please.
Good Luck,
S.
Click to expand...
Click to collapse
:crying:
I've been searching high and low for a full nougat firmware package for the RETUS model... and i cant find one. Has anyone else found one?
I know there are OTAs out there, I'm looking for an FXZ that can be used with fastboot.
filefactory, mirrors.lolinet, etc... seem to have most 7.0 firmware packages EXCEPT for RETUS which only have 6.0 packages.
I have not seen a release for RETUS as of yet... did you not make a nandroid of your original stock before you started flashing...?
If not, flash the 6.0 and the updates found here on XDA.
Jimi Mack said:
I have not seen a release for RETUS as of yet... did you not make a nandroid of your original stock before you started flashing...?
If not, flash the 6.0 and the updates found here on XDA.
Click to expand...
Click to collapse
I haven't unlocked or flashed anything yet... I wanted to try and find an up to date firmware package to have on hand before I start flashing anything.
Do you know if there would be an issue with using the latest 7.0 RETAIL firmware package on my RETUS device?
https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/
I'm still trying to wade through all these posts about firmware packages and the lost imei issues.
FanDroid09 said:
I haven't unlocked or flashed anything yet... I wanted to try and find an up to date firmware package to have on hand before I start flashing anything.
Do you know if there would be an issue with using the latest 7.0 RETAIL firmware package on my RETUS device?
https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/
I'm still trying to wade through all these posts about firmware packages and the lost imei issues.
Click to expand...
Click to collapse
Sorry to bump this thread, but I tried to root my 7.0 retus yesterday and it is now bootlooping and not working pretty much at all. I am having the same problem with being unable to find stock 7.0 retus fastboot firmware. Did you ever find a solution? Did you just install the retail version, or did you find a fastboot file?
chris23445 said:
Sorry to bump this thread, but I tried to root my 7.0 retus yesterday and it is now bootlooping and not working pretty much at all. I am having the same problem with being unable to find stock 7.0 retus fastboot firmware. Did you ever find a solution? Did you just install the retail version, or did you find a fastboot file?
Click to expand...
Click to collapse
What did you do to root? Unlock bootloader then what?
chris23445 said:
Sorry to bump this thread, but I tried to root my 7.0 retus yesterday and it is now bootlooping and not working pretty much at all. I am having the same problem with being unable to find stock 7.0 retus fastboot firmware. Did you ever find a solution? Did you just install the retail version, or did you find a fastboot file?
Click to expand...
Click to collapse
Unfortunately I was never able to find a Retus firmware package. However I did flash the Retail firmware package from this thread:
https://forum.xda-developers.com/moto-z-play/how-to/downgrade-7-1-1-soak-test-to-7-0-t3646807
If you follow that guide you should be fine. Worked good for me.
BTW
Nice I See Stars avatar. :good:
Listened to New Demons on repeat when it came out back in the day haha.
EspElement said:
What did you do to root? Unlock bootloader then what?
Click to expand...
Click to collapse
So I am on Retus and upgraded to April patch. Then I unlocked bootloader (successfully), flashed newest TWRP (successfully), flashed the f2fs patch kernel for 7.0 (successfully), then finally Magisk's newest stable (successfully). Phone booted up fine. I went into settings and tried to factory reset, and when the phone rebooted it went to recovery and then now it just doesn't ever boot. It just bootloops. No idea why that is happening.
I found a thread that has steps to downgrade to MM (without flashing bootloader or modem or things that would possibly hard brick) and then after the downgrade I can sideload the Nougat update.
I've seen a lot of people saying if you downgrade after April patch you may hard brick your device, which I am definitely trying to avoid. So if you have any other ideas or if you think what I'm doing is fine, any advice is appreciated!
---------- Post added at 09:14 AM ---------- Previous post was at 09:12 AM ----------
FanDroid09 said:
Unfortunately I was never able to find a Retus firmware package. However I did flash the Retail firmware package from this thread:
https://forum.xda-developers.com/moto-z-play/how-to/downgrade-7-1-1-soak-test-to-7-0-t3646807
If you follow that guide you should be fine. Worked good for me.
BTW
Nice I See Stars avatar. :good:
Listened to New Demons on repeat when it came out back in the day haha.
Click to expand...
Click to collapse
I might try that instead of taking the risk of downgrading. This seems to be much better. Do you know if I would still get OTAs going this route?
Nice!! Never found anyone else on here that likes that music. I've seen them live and met them twice, they are amazing.
Does anyone know where to get the latest either RETAIL or RETUS stock firmware with the May 1st security update? NPN25.137-24.4
chris23445 said:
So I am on Retus and upgraded to April patch. Then I unlocked bootloader (successfully), flashed newest TWRP (successfully), flashed the f2fs patch kernel for 7.0 (successfully), then finally Magisk's newest stable (successfully). Phone booted up fine. I went into settings and tried to factory reset, and when the phone rebooted it went to recovery and then now it just doesn't ever boot. It just bootloops. No idea why that is happening.
I found a thread that has steps to downgrade to MM (without flashing bootloader or modem or things that would possibly hard brick) and then after the downgrade I can sideload the Nougat update.
I've seen a lot of people saying if you downgrade after April patch you may hard brick your device, which I am definitely trying to avoid. So if you have any other ideas or if you think what I'm doing is fine, any advice is appreciated!
---------- Post added at 09:14 AM ---------- Previous post was at 09:12 AM ----------
I might try that instead of taking the risk of downgrading. This seems to be much better. Do you know if I would still get OTAs going this route?
Nice!! Never found anyone else on here that likes that music. I've seen them live and met them twice, they are amazing.
Click to expand...
Click to collapse
Do not side load android N!! You will brick.
Do as the person said here. Flash the N from the forms without .gpt and bootloader
EspElement said:
Do not side load android N!! You will brick.
Do as the person said here. Flash the N from the forms without .gpt and bootloader
Click to expand...
Click to collapse
Yep, I did exactly as that thread said and everything has been working great so far! Thank you both for the help, it is greatly appreciated. I was up until almost 3 AM last night trying to fix it.
chris23445 said:
Yep, I did exactly as that thread said and everything has been working great so far! Thank you both for the help, it is greatly appreciated. I was up until almost 3 AM last night trying to fix it.
Click to expand...
Click to collapse
Is it worth after all?
chris23445 said:
Yep, I did exactly as that thread said and everything has been working great so far! Thank you both for the help, it is greatly appreciated. I was up until almost 3 AM last night trying to fix it.
Click to expand...
Click to collapse
I've been there done that that's for sure. I just bricked one of my Moto Z plays last week doing what you were about to do.
StOP!!!! If you are on Custom firmware above 6, for the love of everything holy and merciful DO NOT downgrade so you can get the OTA. Some of us have and we are waiting for blankflash files that don't even exist yet.
tpx00 said:
StOP!!!! If you are on Custom firmware above 6, for the love of everything holy and merciful DO NOT downgrade so you can get the OTA. Some of us have and we are waiting for blankflash files that don't even exist yet.
Click to expand...
Click to collapse
He stopped and is all good! I am with you. Got a dead Moto Z Play. My new one from eBay is coming today. Sigh
EspElement said:
He stopped and is all good! I am with you. Got a dead Moto Z Play. My new one from eBay is coming today. Sigh
Click to expand...
Click to collapse
Ya I'm about to go pick up a nexus 6 from craigslist until mine comes back from Motorola.
Can Nougat work on AT&T any roms. im getting a phone soon and im hoping i can get other than Marshmallow on my phone. Can someone direct me the steps to do this please?
Any of the ROMs in the "generic/international" M8 development sections will work on the AT&T version. There is no hardware difference between the models. Just stay away from ROMs intended for Sprint and Verizon.
When you receive the phone, you'll want to confirm it's on Marshmallow firmware (and if not, update to MM). Then unlock the bootloader via HTCDev.com, install current TWRP 3.1. Then you can flash any ROM you like (as long as it meets the description already mentioned above).
Looks like you're pretty experienced on these forums (other devices), so may be familiar with some/all of these steps. But if not, or you have any specific questions, let us know and we'll be happy to help further.
redpoint73 said:
Any of the ROMs in the "generic/international" M8 development sections will work on the AT&T version. There is no hardware difference between the models. Just stay away from ROMs intended for Sprint and Verizon.
When you receive the phone, you'll want to confirm it's on Marshmallow firmware (and if not, update to MM). Then unlock the bootloader via HTCDev.com, install current TWRP 3.1. Then you can flash any ROM you like (as long as it meets the description already mentioned above).
Looks like you're pretty experienced on these forums (other devices), so may be familiar with some/all of these steps. But if not, or you have any specific questions, let us know and we'll be happy to help further.
Click to expand...
Click to collapse
Sunshine not required?
cell2011 said:
Sunshine not required?
Click to expand...
Click to collapse
Sunshine not required. S-off is only needed for certain things, like changing the phone's CID/MID, flashing modified hboots, "downgrading" firmware/RUU, SIM unlock.
For most mods, such as root, flashing ROMs (Nougat ROMs included), custom kernels, etc. all you need is an unlocked bootloader and custom recovery TWRP.
redpoint73 said:
Sunshine not required. S-off is only needed for certain things, like changing the phone's CID/MID, flashing modified hboots, "downgrading" firmware/RUU, SIM unlock.
For most mods, such as root, flashing ROMs (Nougat ROMs included), custom kernels, etc. all you need is an unlocked bootloader and custom recovery TWRP.
Click to expand...
Click to collapse
Ok thanks yea thisphone im getting has never been touched meaning rooted or modified probably not even on MM yet. So i should be good to go just update to MM unlock BL and twrp?
My guess is you're buying a carrier unlocked phone? Here is a good thread I started and should answer all your questions.
https://forum.xda-developers.com/htc-one-m8/help/carrier-unlocked-gsm-m8-t3598115
theandies said:
My guess is you're buying a carrier unlocked phone? Here is a good thread I started and should answer all your questions.
https://forum.xda-developers.com/htc-one-m8/help/carrier-unlocked-gsm-m8-t3598115
Click to expand...
Click to collapse
Im sorry i should have been more clearer in my title it will be a US AT&T M8
cell2011 said:
Im sorry i should have been more clearer in my title it will be a US AT&T M8
Click to expand...
Click to collapse
:good: Should still help. When I bought the phone in that thread a few weeks ago on ammmmmmmozon it was advertised as a GSM network phone which AT&T is. I'm on AT&T and it was easy to unlock the bootloader through HTCdev and flash TWRP and custom ROM's and Kernels. As you stated it will probably not be on the latest firmware so you probably have OTA before doing anything. If OTA dosen't work then you'll have to RUU to get on the latest AT&T firmware before unlocking and installing TWRP.
The one think I've had issues with is network speed meaning it indicates HSPA (3G+ speeds) and not 4g or 4g LTE. I've tried all the latest APN's for AT&T's network but still can only get indicated HSPA speeds. This is on an old SIM card and I've not gone to the AT&T store to pick up a new one to see if that is my problem. My SIM is the original one I got when I bought my first M8 shortly after launch in 2014.
I'm currently running LeeDroid (Android 6.0 HTC Sense 7.0) ROM and tomorrow I'm going to try DarkNess reDefined which is Nougut based.
ROM Darkness Redefined
Yes I was told to update to mm and then unlock BL and then twrp and root
theandies said:
As you stated it will probably not be on the latest firmware so you probably have to unlock and RUU upgrade before doing anything
Click to expand...
Click to collapse
This is one wrong advise.
OP just needs to OTA update to the latest. If using RUU to upgrade, need a Locked bootloader for S-On device.
Previous advise by @redpoint73 is correct.
After all the firmware is updated to the latest, then only unlock bootloader then install latest TWRP and OP is ready to install custom ROM including Nougat.
---------- Post added at 05:31 AM ---------- Previous post was at 05:27 AM ----------
cell2011 said:
Yes I was told to update to mm and then unlock BL and then twrp and root
Click to expand...
Click to collapse
This is correct.
Only thing is you don't need to root because custom ROM is pre-rooted.
You root only if you want a rooted stock ROM
ckpv5 said:
This is one wrong advise.
OP just needs to OTA update to the latest. If using RUU to upgrade, need a Locked bootloader for S-On device.
Previous advise by @redpoint73 is correct.
After all the firmware is updated to the latest, then only unlock bootloader then install latest TWRP and OP is ready to install custom ROM including Nougat.
---------- Post added at 05:31 AM ---------- Previous post was at 05:27 AM ----------
This is correct.
Only thing is you don't need to root because custom ROM is pre-rooted.
You root only if you want a rooted stock ROM
Click to expand...
Click to collapse
If it's a true AT&T phone then yes, just OTA first and foremost. If OTA doesn't work then he'll have to go the RUU route. Once the firmware is up to date (either RUU or OTA) with the latest AT&T then unlock bootloader and install TWRP. I've edited my response as to not confuse. My bad, I just re-read my responce and it didn't come out the way I wanted it to. Guess that's why I'm not an English major..........
Yes this will be an At&t phone not just Sim
cell2011 said:
Yes this will be an At&t phone not just Sim
Click to expand...
Click to collapse
Best thing to do, when you get the phone, is do fastboot getvar all, and post the results (delete IMEI and serial number before posting). We can take a look, and remove all doubt about the carrier version, whether the firmware needs to be updated, etc.