Confirmed, Problem w/ Older TWRP, Get all the latest Recoveries - RAZR HD General

Update. http://forum.xda-developers.com/showpost.php?p=49949505&postcount=15
http://forum.xda-developers.com/showpost.php?p=49510873&postcount=31
More http://forum.xda-developers.com/showpost.php?p=49576967&postcount=37
Dhackers latest has md5 0908108cc64deaa73345f2136819635a for twrp2.6.3.1-HD.img
http://androidhosting.org/Devs/Dhacker29/msm8960/
Flashable done. I did not notice a distinction made by Dhacker about 925 & 926 but that confirms what thought: the recoveries are the same.
The noemcwipe build is for 16gb phones.
http://forum.xda-developers.com/showpost.php?p=47389748&postcount=53
Related: here are the latest philz cwmr 6045 flashable. Philz does not host a flashable version so there is a 925 & 926 version in attachments, the no assert is just a more reliable flash. http://forum.xda-developers.com/showthread.php?t=2545120
This one is not the latest.
http://forum.xda-developers.com/showthread.php?t=2476238

Just to clarify, I made that build at or near the date that the thread was posted. It was built from the latest TWRP tree at that time (this was before other devs had made a build of it, hencce the unofficial tag). There have been many commits to the project since then and newer builds have been made. For the record, i'm still using the one from my thread and have been flashing CM nightlies with it, but I would probably suggest using a newer one if you were going to be installing one anyway.
EDIT: I have updated the OP in that thread with a warning about the age of the build.

aviwdoowks said:
The HD could be a train with a bad engine too.
http://forum.xda-developers.com/showpost.php?p=49510873&postcount=31
Dhackers latest has md5 0908108cc64deaa73345f2136819635a for twrp2.6.3.1-HD.img
http://androidhosting.org/Devs/Dhacker29/msm8960/
****If any want a flashable I will make one***
Click to expand...
Click to collapse
Yes please.

pistacios said:
Yes please.
Click to expand...
Click to collapse
Done.

Excellent! Thank you

Just flashed dhackers version in the OP. I haven't flashed any ROMS yet, but I feel better knowing which twrp is installed (bought the phone used with unknown twrp installed). Especially after reading about the "read-only' issue .

Boot Failure
I tried to install the file labeled twrp-xt926-noemmcwipe -flashable.zip and now I am getting ...Boot Failure in AP Fastboot.
I still have unlocked bootloader and root. What course of action do I need to take to remedy this problem. I cannot reboot in TWRP like I used to since. Thank You in advance for taking to the time to review and respond to this question.
Respectfully,
Jim92y

jim92y said:
I tried to install the file labeled twrp-xt926-noemmcwipe -flashable.zip and now I am getting ...Boot Failure in AP Fastboot.
I still have unlocked bootloader and root. What course of action do I need to take to remedy this problem. I cannot reboot in TWRP like I used to since. Thank You in advance for taking to the time to review and respond to this question.
Respectfully,
Jim92y
Click to expand...
Click to collapse
I take it you do not have a 16 gb phone. I will rename the attachment to a warning...
If YOU cannot boot. Get fastboot working & fastboot the proper img.
Or rsd lite restore time!
Or use the lattest matts in the dev section. But only to flash recovery.
House of moto in my gen post, if you want to climb that hill.
If you get it to boot use Rom Manager & flash photon Q recovery.
What build of twrp did you flash the noemmc... with?

Everybody needs to update!!
Confirmed.
http://forum.xda-developers.com/showpost.php?p=49949505&postcount=15

Related

New July images posted

Two again - MMB30K & MOB30O. I have no idea what the difference is, but I've used MOB30O successfully.
Link to the Nexus 6 OTA page with instructions for sideloading (no data loss, need to reinstall TWRP & reroot):
https://developers.google.com/android/nexus/ota
For those people who prefer to install separate components:
MMB30K
MOB30O
dahawthorne said:
Two again - MMB30K & MOB30O.
Click to expand...
Click to collapse
Did anyone ever figure out what the difference was? Google did this last time, and the result seemed the same between the two.
I went with MOB30M last time and it worked fine, so I'm going with MOB30O.
@dahawthorne added the links on the first post for you..
Thanks. I should have included the links, but I reckoned that anyone who's interested knows where to find them, and anyone who doesn't know probably shouldn't be tinkering...
But yes, the pointer is appreciated.
Edit: I used the OTA at this link - simpler, and doesn't lose your data:
https://developers.google.com/android/nexus/ota#shamu
Instructions are on the page. A simple sideload, flash recovery, install SuperSU.
Sir , is there any difference between MMB30K and MOB30O versions?
marcus droid said:
Sir , is there any difference between MMB30K and MOB30O versions?
Click to expand...
Click to collapse
we have to wait for the AOSP change logs on that
Encrytable boot/kernel IMGs:
MOB30O:
https://www.androidfilehost.com/?fid=24572369242688110
MMB30K:
https://www.androidfilehost.com/?fid=24572369242688111
What was the difference between the last 2 images? That was released without explanation as well!
I flashed the MOB30O version, anyone having trouble flashing SuperSU like me?
SuperSU flashed alright in TWRP(though the log seems a bit shorter than usual). When I rebooted the system, it says that SuperSU binary is not installed. I've tried to reflash TWRP (since stock recovery takes over) & different versions of SuperSU: 2.74 / 2.76 and can't seem to get root.
Strange. I sideloaded the MOB30O OTA, flashed TWRP (twice - it didn't stick first time) then installed SuperSU 2.76 from TWRP. No problems at all so far.
ayang02 said:
I flashed the MOB30O version, anyone having trouble flashing SuperSU like me?
SuperSU flashed alright in TWRP(though the log seems a bit shorter than usual). When I rebooted the system, it says that SuperSU binary is not installed. I've tried to reflash TWRP (since stock recovery takes over) & different versions of SuperSU: 2.74 / 2.76 and can't seem to get root.
Click to expand...
Click to collapse
I flashed SuperSU 2.76 just fine after flashing the MOB30O image. Also, I've never had stock recovery get replaced on my Nexus 6 ever. That's really strange.
The difference between these two images has been posted many times - not sure why people are confused about it!
MOB is the version you want.
MMB is the version for the Carriers who haven't approved the newer radio in MOB.
MOB also includes some kernel enhancements to increase performance. These changes related to the Kernel "Tick Rate". I think the changes have improved performance a little, but you're not going to think you've purchased a new phone or anything.
Summary:
MOB: Newer kernel with performance improvements, updated Radio image.
MMB: Older kernel sans performance improvements, old radio.
Summary: MOB is the train you want to be on.
ayang02 said:
I flashed the MOB30O version, anyone having trouble flashing SuperSU like me?
SuperSU flashed alright in TWRP(though the log seems a bit shorter than usual). When I rebooted the system, it says that SuperSU binary is not installed. I've tried to reflash TWRP (since stock recovery takes over) & different versions of SuperSU: 2.74 / 2.76 and can't seem to get root.
Click to expand...
Click to collapse
I dl'd the O image, extracted and flashed the system image only through twrp while at work. Rooted using a PC when I got home and I have no issues so fah. I use chainfires method and his method requires running his image with fast boot. Fastboot boot cf... What ever you have the file named. It'll do it's thing on the phone then reboot 1-3x before it boots up fully. This root it rebooted once. On previous updates, up to 3 times before it finally finished.
Why are people insisting on flashing the "old" modular way (extracting components for individual flashing) when Google have provided a total no-data-loss OTA? 15 minutes, risk-free. Why choose the difficult way when there's a seamless simple upgrade? Incomprehensible.
dahawthorne said:
Why are people insisting on flashing the "old" modular way (extracting components for individual flashing) when Google have provided a total no-data-loss OTA? 15 minutes, risk-free. Why choose the difficult way when there's a seamless simple upgrade? Incomprehensible.
Click to expand...
Click to collapse
For me it's because I've lost my data a couple of times in the past doing an OTA update. I guess old habits die hard and I like the control I have flashing each image file manually. At least that way I can be reasonably sure that my data isn't messed with by not flashing the userdata image, plus, I can skip flashing recovery so I don't have to reinstall that. It only took me 9 minutes to complete the process tonight, including re-rooting, doing it the "old" way.
dahawthorne said:
Why are people insisting on flashing the "old" modular way (extracting components for individual flashing) when Google have provided a total no-data-loss OTA? 15 minutes, risk-free. Why choose the difficult way when there's a seamless simple upgrade? Incomprehensible.
Click to expand...
Click to collapse
Two very simple reasons. 1) if you are rooted. 2) if you are unencrypted.
FWIW: it takes about 60 seconds to extract the images from the .zip file. And about 3 minutes to flash the boot and system image files in fastboot.
before i download the entire package can anyone tell me if there is a new modem in july update?
H4X0R46 said:
I flashed SuperSU 2.76 just fine after flashing the MOB30O image. Also, I've never had stock recovery get replaced on my Nexus 6 ever. That's really strange.
Click to expand...
Click to collapse
Then that means you were able to get root successfully. My TWRP recovery got overwritten because I didn't get root. Anyways, I am gonna try flashing stuff from scratch in a few days. I've also never had issues flashing monthly updates and SuperSU until now.
Sent from my Nexus 6 using XDA Free mobile app
adm1jtg said:
before i download the entire package can anyone tell me if there is a new modem in july update?
Click to expand...
Click to collapse
There is no new modem, nor bootloader. Just security updates to boot and system images.

[Guide][How to]Update Bootloader/Firmware to OOS3/H2OS2 w/o installing OOS/H2OS

Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ones who are on stock recovery and just want to update their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
I created this thread to help the CM13(Official or Sultan's)//any custom rom using new BL,users who want to update their BL without flashing the OOS through the tedious way just to update BL and users who are stuck on bootlogo due to old BL with roms using new BL.
Here I will guide you through the required steps to update our bootloader "In easiest and fastest way without wiping and restoring anything".
So what are we waiting for ,lets start .
Prerequisites
you will need two files for this process,nothing else.
1 . First one is BLUpdater zip --->Here.
2. Second is TWRP compiled from latest sources use either This or the one from Here<--use v41 or use Sultan's from Here OR if you are Martin's fan like me and want to use his MutiRom TWRP goHere.
PS:I am assuming you have Unlocked Bootloader and have either
official/blu_spark/sultan's/ Multirom TWRP installed,in a working condition on OOS2.x BL(if not what are you doing here).
Note: make sure oem unlocking is checked in developer options in your current rom,else updating the BL may cause it to get locked ,and you will have to unlock it again and flash the recovery manually through fastboot itself.
Now the steps
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
NOTE:If you chose to use Sultan's recovery.zip then just flash it normally.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Now voila you should have updated your firmware/BL.Congrats.
You can now install any rom that supports the new BL.Older roms won't boot on the new MM BL.So check the rom thread before installing the rom and later on quacking here about your device being stuck at bootlogo.
Notes
i)Neither I nor XDA will be responsible if your OPX bricks or explodes or ditches you and flies to space.
ii)We are not touching system partition so last installed ROM will be intact.
iii)This guide will leave you into bootable rom only if you have a rom installed that works on latest firmware.
iv)This can also be used to restore all your OPX partitions back to OOS3.x partition state,if you messed any.
v)In case you are using latest nightly (cm13) and face bootloop - go Here
psst:If you are not diggin the new BL,and wanna downgrade again ,back to old BL,check this post.
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
matwaking said:
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ons who are on stock recovery and just want to their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
So I created this thread just to shorten the process provided by Joshwin.I also created this thread to help the official CM13 users who have problem with latest nightlies due to new bootloader or are stuck in bootlogo.
...
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
Click to expand...
Click to collapse
Booomshkalaka!!!
Great guide, can't test (already have new bootloader and too lazy to switch back but look very good.
Thx to all
Kurt
Kurt Krummbein said:
Booomshkalaka!!!
Click to expand...
Click to collapse
Lol .
Thanks mate.
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
jonrodz said:
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
Click to expand...
Click to collapse
Will work with any twrp,no requirement of official one.
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
jonrodz said:
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
Click to expand...
Click to collapse
No it wont,right now almost all the custom roms need to update to support new firmware.Only latest cm13 nightlies are booting now,also aosp compiled by olddroid for new BL(shh its only for testers right now)
also maybe the MIUI8 port ,just posted in the forums.
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
jerikooo said:
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
Click to expand...
Click to collapse
no update the BL using the steps above ,then flash the latest nightly.That way it would be good.
Or you can flash nightly first then update BL.Choice is yours.I recommend updating the BL first.
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Duplicate post.Deleted
ccaappton said:
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Click to expand...
Click to collapse
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
matwaking said:
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
Click to expand...
Click to collapse
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
ccaappton said:
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
Click to expand...
Click to collapse
Well no fix without any problems hehehe,.Haapy 4 u.
Click that button if you think my posts are useful
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Manelit said:
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Click to expand...
Click to collapse
taking you wanna flash ashwins cm14 right. You just wanna follow the instructions in first post and then flash the cm14.No need to install the whole Oos zip.
This way you should have updated BL and working cm14.
Just flash the cm14 after booting into new TWRP
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
slaav said:
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
Click to expand...
Click to collapse
Press that sweet sweet button mate
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Click to expand...
Click to collapse
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
walsash said:
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
Click to expand...
Click to collapse
u can flash bluespark twrp via fasboot
Sent from my ONE E1003 using XDA-Developers mobile app

BEST Rooting and twrp flashing without pc for m9 **TESTED ON ANDROID 7.0**

HTC One (M9) ReadMe Thread
Q4: Which versions of TWRP and SuperSU are the recommended ones?
A: The answer depends on your current firmware version. If you're using firmware 4.x then you'll find your answer here in the FAQ of the TWRP thread. (Click here, if you can't find SuperSU 2.79 SR3.) For firmware 1.x and 2.x the recommended versions are Captain_Throwback's Beta 1 of TWRP 2.8.7.1 and SuperSU 2.49. For firmware 3.x the recommended versions are TWRP 3.1.1-0 (official) and SuperSU 2.65. Using different versions than the recommended ones will probably lead to a bootloop. The M9 isn't compatible with the ramdisk changes that get executed by many flashable system-less SuperSU versions. However, updating the SuperSU app and its binaries via the Play Store after flashing one of the older versions is safe.
Q5: Are there alternative methods for gaining root?
A: Yes, you can use Magisk if you're using firmware 4.x. (Maybe a user with a lower firmware version can test whether Magisk is usable on firmware 1.x to 3.x, as well?)
Click to expand...
Click to collapse
Requirement
1. S-OFF AND UNLOCKED BOOTLOADER OF HTC ONE M9 (FILE PROVIDED IS FOR INTERNATIONAL VERSION. IF YOU WANT CREATE YOUR CARRIER PHONE COMMENT BELOW )
Method
STRAIGHT TO THE POINT just download the 2 zips provided below and place it in external sd card of phone and reboot to download mode
It will ask to flash press the vol up button and after flash you will have twrp flashed (i had included latest twrp recovery in the zip file but you can place in zip the recovery of your choice but you have to rename it to recovery.img)
NOTE DONT RENAME THE ZIP OR ELSE IT WILL NOT FLASH AND SECONDLY DONT CHANGE THE TXT FILE IN THE ZIP
after flash go to recovery and flash supersu zip
Downloads
Mod Removed
Help Section
Comment or pm me if you are facing any problem and want to get help
If you liked my work hit the appreciation button and if you want to grow my projects donate me as i dont have enough resources
Don't spam. Your previous thread exactly like this has been closed. Can't you take the message from that?
http://forum.xda-developers.com/showthread.php?t=3530127
Hope a mod sees this soon.
Sent from my HTC One M9 using Tapatalk
shaqman89 said:
Don't spam. Your previous thread exactly like this has been closed. Can't you take the message from that?
http://forum.xda-developers.com/showthread.php?t=3530127
Hope a mod sees this soon.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
First of all i am sorry for the previous post.
In my previous post, it was my 1st time i posted anything.I dont know the rules. But now i had got all the rules etc. In previous post i also used some useless terms such as "custom recovery" but in this post everything is ok.
Previous post was closed by moder because i used adf for some earning
But in this the downloads are on direct androidfilehost.com
You can match the md5 in the twrp zip of recovery.img with the md5 of of twrp 3.0.2 at thier website for verification
And try before saying anything
If it will be spam than report about my post
ahmad.abbas54 said:
First of all i am sorry for the previous post.
In my previous post, it was my 1st time i posted anything.I dont know the rules. But now i had got all the rules etc. In previous post i also used some useless terms such as "custom recovery" but in this post everything is ok.
Previous post was closed by moder because i used adf for some earning
But in this the downloads are on direct androidfilehost.com
You can match the md5 in the twrp zip of recovery.img with the md5 of of twrp 3.0.2 at thier website for verification
And try before saying anything
If it will be spam than report about my post
Click to expand...
Click to collapse
You're posting links to outdated versions of both TWRP and SuperSU. The latest versions and guides on how to install them already exist in their official threads.
If you want to be a help, try your hand at questions people are actually asking instead. XDA can always use another helpful expert.
computerslayer said:
You're posting links to outdated versions of both TWRP and SuperSU. The latest versions and guides on how to install them already exist in their official threads.
If you want to be a help, try your hand at questions people are actually asking instead. XDA can always use another helpful expert.
Click to expand...
Click to collapse
Really!! All those methods require a pc. My method is without pc
And Dont miss guide or lie and for your information both twrp and supersu is updated one
Talk before speak
Proofs are attached
ahmad.abbas54 said:
Really!! All those methods require a pc. My method is without pc
And Dont miss guide or lie and for your information both twrp and supersu is updated one
Talk before speak
Proofs are attached
Click to expand...
Click to collapse
I'm sorry if I've offended you - that wasn't my intention. However, you are mistaken about me lying or misguiding others.
Go check out the official TWRP thread. The latest version is posted there - it's version 3.0.3-0.
Check out the official SuperSU thread. The latest version is posted there - it's version 2.79 SR1 (2016-12-22).
Both of these versions, by the way, are important because they address issues that are unique to the M9. Previous versions of TWRP couldn't decrypt HTC's stock encryption. Recent versions of SuperSU couldn't be flashed directly. I'm sure there are other general fixes included as well.
You've got a neat idea, and I commend you for it. But if you're not working with the latest software - and passing it off as the latest - you're adding to people's confusion rather than helping them.
computerslayer said:
I'm sorry if I've offended you - that wasn't my intention. However, you are mistaken about me lying or misguiding others.
Go check out the official TWRP thread. The latest version is posted there - it's version 3.0.3-0.
Check out the official SuperSU thread. The latest version is posted there - it's version 2.79 SR1 (2016-12-22).
Both of these versions, by the way, are important because they address issues that are unique to the M9. Previous versions of TWRP couldn't decrypt HTC's stock encryption. Recent versions of SuperSU couldn't be flashed directly. I'm sure there are other general fixes included as well.
You've got a neat idea, and I commend you for it. But if you're not working with the latest software - and passing it off as the latest - you're adding to people's confusion rather than helping them.
Click to expand...
Click to collapse
I am also sorry if i used some rude words
Still i had checked recently on twrp.me and there's only 3.0.2 for m9 and i am using it right now with supersu 2.79
I am not facing any problem at all in all matters and it is also much stable
You can still update according to your need as you can open up my provided zip and add recovery.img of your choice and also you can flash supersu of your choice
@ahmad.abbas54: What @computerslayer said is correct. There are numerous reports of users facing a bootloop after flashing any other SuperSU version than 2.64 (stable), 2.65 (stable) or the latest beta 2.79 SR1 (link to its thread) on their stock rom. However, flashing one of these three and updating SuperSU via the play store doesn't cause any problems. Therefore I'd ask you for not linking the stable version 2.79.
In regard to TWRP: 3.0.2-0 is working fine. However, it's not the recommended version since 3.0.3-0 (unofficial) is capable of installing HTC's official OTAs.
Flippy498 said:
@ahmad.abbas54: What @computerslayer said is correct. There are numerous reports of users facing a bootloop after flashing any other SuperSU version than 2.64 (stable), 2.65 (stable) or the latest beta 2.79 SR1 (link to its thread) on their stock rom. However, flashing one of these three and updating SuperSU via the play store doesn't cause any problems. Therefore I'd ask you for not linking the stable version 2.79.
In regard to TWRP: 3.0.2-0 is working fine. However, it's not the recommended version since 3.0.3-0 is capable of installing HTC's official OTAs.
Click to expand...
Click to collapse
Kindly elaborate me further about the super su zip which is stable in 2.64 2.79 ??
Btw I had given download link of version supersu 2.79 in my post
ahmad.abbas54 said:
Kindly elaborate me further about the super su zip which is stable in 2.64 2.79 ??
Btw I had given download link of version supersu 2.79 in my post
Click to expand...
Click to collapse
SuperSU changes parts of the ramdisk since the introduction of system-less root. However, the changes that get initiated by any other than the three versions I mentioned above are not compatible with the M9 and cause a bootloop. Updating via the play store only updates the app and its binaries but not the ramdisk changes. This way you could update to a newer version of supersu (before 2.79 sr1 got released) without facing a bootloop.
There are stable and beta releases of SuperSU. Both are different stages of a "software release cycle". (The " " mark the keyword you need to google for further information. At the moment I don't have the time for writing a more detailed post. Sorry.)
You linked the stable version of 2.79. The beta which is safe to use got released a week later than the version in your post and it contains "sr1" in its naming.
Edit: Oh and please don't re-upload files to your afh account that you don't own (e.g. SuperSU) unless you got the permission of the dedicated owner/dev. Your 0PJAIMG.zip should be fine as long as you mention TWRP's devs in the credits of your OP.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
SuperSU changes parts of the ramdisk since the introduction of system-less root. However, the changes that get initiated by any other than the three versions I mentioned above are not compatible with the M9 and cause a bootloop. Updating via the play store only updates the app and its binaries but not the ramdisk changes. This way you could update to a newer version of supersu (before 2.79 sr1 got released) without facing a bootloop.
There are stable and beta releases of SuperSU. Both are different stages of a "software release cycle". (The " " mark the keyword you need to google for further information. At the moment I don't have the time for writing a more detailed post. Sorry.)
You linked the stable version of 2.79. The beta which is safe to use got released a week later than the version in your post and it contains "sr1" in its naming.
Edit: Oh and please don't re-upload files to your afh account that you don't own (e.g. SuperSU) unless you got the permission of the dedicated owner/dev. Your 0PJAIMG.zip should be fine as long as you mention TWRP's devs in the credits of your OP.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Ok i will be carefull next time
Had anyone achieved root with my method before??
I mean without pc
ahmad.abbas54 said:
Ok i will be carefull next time
Had anyone achieved root with my method before??
I mean without pc
Click to expand...
Click to collapse
Well, no one ever posted explicit instructions but it should be known to be possible from Sneakyghost's firmware thread. His firmware packs can get flashed via the SD card method, as well, and your archive is somehow similar to his no wipe packs. The difference is that your archive only contains TWRP whereas his packs contain almost the full stock firmware and TWRP instead of the stock recovery.
Nevertheless, step by step instructions like to ones in this thread are always nice to have.
(Although strictly speaking a PC is needed for your method, too, since you can't achieve S-OFF via Sunshine* without root on the M9 and for rooting the M9 the first time you need to unlock the bootloader which requires a PC. However, don't mind my nitpicking. )
* I have not much knowledge about how to use java cards for the same purpose but I think you need a PC for them, as well.
Flippy498 said:
Well, no one ever posted explicit instructions but it should be known to be possible from Sneakyghost's firmware thread. His firmware packs can get flashed via the SD card method, as well, and your archive is somehow similar to his no wipe packs. The difference is that your archive only contains TWRP whereas his packs contain almost the full stock firmware and TWRP instead of the stock recovery.
Nevertheless, step by step instructions like to ones in this thread are always nice to have.
(Although strictly speaking a PC is needed for your method, too, since you can't achieve S-OFF via Sunshine* without root on the M9 and for rooting the M9 the first time you need to unlock the bootloader which requires a PC. However, don't mind my nitpicking. )
* I have not much knowledge about how to use java cards for the same purpose but I think you need a PC for them, as well.
Click to expand...
Click to collapse
Well thats for obvious that we need pc for atleast bootloader unlock
I'm trying this method to flash TWRP on my unlocked, S-Off m9. (Unlocked with SunShine, my Mac with new USB-C port doesn't see device over ADB) I've unzipped your TWRP package, replaced the old TWRP with the latest--renamed "recovery.img"--and re-zipped it. When I boot phone into Download mode, the script recognizes the zip package, and "start ui-update" appears at the top of the screen. Nothing else happens, and if I eventually force power off, the stock Recovery is still installed. Suggestions?
Do S-OFF AND UNLOCKED BOOTLOADER not need a computer ؟؟؟؟؟؟
!!!!!!!!!!!!!!
Please close this trivial matter

Out of my depth with MultiROM/TWRP problem; could use some guidance

Hi, All . . .
I believe it would be appropriate to label me as an intermediate-to-advanced newbie. That is, I'm not clueless, but there are lots of blind spots in my knowledge.
I just bought a 6P and while I've been waiting for my SIM card to arrive, I've gone ahead and rooted, installed TWRP 3.0.3-0, and made a few customizations here and there. One thing I don't understand is the significance of the vendor image now. I'm coming from a 6 where that wasn't an issue. Also, in the rooting instructions it indicates that one should "find the correct vendor image," without really indicating how one can go about learning which one is "right." In the end, I took the latest one I could find, because my phone did an OTA update and I simply reasoned that I should match latest with latest.
In any case, I want to install MultiROM and I keep running into this problem:
The MultiROM version of TWRP doesn't load. It hangs on the splash screen. The version it uses is 3.0.2-0, so I suspected it was an issue with that. I flashed the TWRP-only recovery version 3.0.2-0 after having no luck, and it wouldn't load beyond the splash screen, either. Finally, I re-flashed the stock system recovery and tried flashing both the 3.0.2-0 TWRP-only recovery and the MultiROM-integrated version, both without success.
Is there something about the move from 3.0.2-0 to 3.0.3-0 that makes a rollback impossible. Is it even necessary?
Re-flashing 3.0.3-0 solved the problem of basic functionality. TWRP comes right up after I do that. But I can't get the MultiROM recovery or the 3.0.2-0 TWRP recovery to work no matter what I try.
My phone says that the vendor version is N4F26J and my "build number" is N6F26Q, and I'm running PureNexus 7.1.1. Those two numbers appear like a mismatch to me, but everything I could find indicated that the vendor version I have, being the latest, is the right one.
What am I missing? Can someone with more experience solve this puzzle, or at least lead me in a direction where I know which questions to ask on my own and can get things to start making sense again?
I appreciate your help! Thanks!
KilgoreTrout71 said:
Hi, All . . .
I believe it would be appropriate to label me as an intermediate-to-advanced newbie. That is, I'm not clueless, but there are lots of blind spots in my knowledge.
I just bought a 6P and while I've been waiting for my SIM card to arrive, I've gone ahead and rooted, installed TWRP 3.0.3-0, and made a few customizations here and there. One thing I don't understand is the significance of the vendor image now. I'm coming from a 6 where that wasn't an issue. Also, in the rooting instructions it indicates that one should "find the correct vendor image," without really indicating how one can go about learning which one is "right." In the end, I took the latest one I could find, because my phone did an OTA update and I simply reasoned that I should match latest with latest.
In any case, I want to install MultiROM and I keep running into this problem:
The MultiROM version of TWRP doesn't load. It hangs on the splash screen. The version it uses is 3.0.2-0, so I suspected it was an issue with that. I flashed the TWRP-only recovery version 3.0.2-0 after having no luck, and it wouldn't load beyond the splash screen, either. Finally, I re-flashed the stock system recovery and tried flashing both the 3.0.2-0 TWRP-only recovery and the MultiROM-integrated version, both without success.
Is there something about the move from 3.0.2-0 to 3.0.3-0 that makes a rollback impossible. Is it even necessary?
Re-flashing 3.0.3-0 solved the problem of basic functionality. TWRP comes right up after I do that. But I can't get the MultiROM recovery or the 3.0.2-0 TWRP recovery to work no matter what I try.
My phone says that the vendor version is N4F26J and my "build number" is N6F26Q, and I'm running PureNexus 7.1.1. Those two numbers appear like a mismatch to me, but everything I could find indicated that the vendor version I have, being the latest, is the right one.
What am I missing? Can someone with more experience solve this puzzle, or at least lead me in a direction where I know which questions to ask on my own and can get things to start making sense again?
I appreciate your help! Thanks!
Click to expand...
Click to collapse
Hey there,
Regarding your TWRP 3.0.2-0/MultiRom 3.0.2-0 and TWRP 3.0.3 issues, check out post #1152 in the official TWRP 6P thread. If there is an update to MR to support Nougat encryption, you'll just have to follow the MR thread or Github for updates.
Here's a brief explainer from my guide in the Nexus 5X forums about Vendor.img:
9. After updating my ROM, I get this message on every boot: "There's an internal problem with your device. Contact your manufacturer."
This warning signifies a mismatched vendor and system partition. The vendor partition was integrated in the system partition for previous Nexus devices but is now a separate partition that must be flashed for each Google security update. Download a factory image and update your vendor partition using fastboot so that it matches your rom's OS base. If you have a file explorer installed on your phone, you can determine which vendor.img is installed by navigating to /vendor/build.prop and clicking on the build.prop. The specific vendor installed will be a combination of six numbers and letters listed in all capitals (example: NMF26F) in the ro.vendor.build.fingerprint line.
Vendor.img is specific to each OTA and contains proprietary binaries for the phone. The phone will fail to boot if you mismatch the vendor.img with a different OS base. For instance, a 6.0 Marshmallow vendor.img will not allow your phone to boot on 7.0 Nougat.
Click to expand...
Click to collapse
Hope this clears things up for you!
Edit: Also, certain rom teams keep an up to date listing of vendor.img available on their websites. Usually this is detailed in the rom thread OP. Find a reliable thread and bookmark their vendor.img downloads, if not download the factory image each month and extract the img.
SlimSnoopOS said:
Hey there,
Regarding your TWRP 3.0.2-0/MultiRom 3.0.2-0 and TWRP 3.0.3 issues, check out post #1152 in the official TWRP 6P thread. If there is an update to MR to support Nougat encryption, you'll just have to follow the MR thread or Github for updates.
Here's a brief explainer from my guide in the Nexus 5X forums about Vendor.img:
Hope this clears things up for you!
Edit: Also, certain rom teams keep an up to date listing of vendor.img available on their websites. Usually this is detailed in the rom thread OP. Find a reliable thread and bookmark their vendor.img downloads, if not download the factory image each month and extract the img.
Click to expand...
Click to collapse
Thanks so much for the swift reply! I'll check these links out right away. I'm sure they will fill in the gaps for me.
Best,
KT
KilgoreTrout71 said:
Hi, All . . .
I believe it would be appropriate to label me as an intermediate-to-advanced newbie. That is, I'm not clueless, but there are lots of blind spots in my knowledge.
I just bought a 6P and while I've been waiting for my SIM card to arrive, I've gone ahead and rooted, installed TWRP 3.0.3-0, and made a few customizations here and there. One thing I don't understand is the significance of the vendor image now. I'm coming from a 6 where that wasn't an issue. Also, in the rooting instructions it indicates that one should "find the correct vendor image," without really indicating how one can go about learning which one is "right." In the end, I took the latest one I could find, because my phone did an OTA update and I simply reasoned that I should match latest with latest.
In any case, I want to install MultiROM and I keep running into this problem:
The MultiROM version of TWRP doesn't load. It hangs on the splash screen. The version it uses is 3.0.2-0, so I suspected it was an issue with that. I flashed the TWRP-only recovery version 3.0.2-0 after having no luck, and it wouldn't load beyond the splash screen, either. Finally, I re-flashed the stock system recovery and tried flashing both the 3.0.2-0 TWRP-only recovery and the MultiROM-integrated version, both without success.
Is there something about the move from 3.0.2-0 to 3.0.3-0 that makes a rollback impossible. Is it even necessary?
Re-flashing 3.0.3-0 solved the problem of basic functionality. TWRP comes right up after I do that. But I can't get the MultiROM recovery or the 3.0.2-0 TWRP recovery to work no matter what I try.
My phone says that the vendor version is N4F26J and my "build number" is N6F26Q, and I'm running PureNexus 7.1.1. Those two numbers appear like a mismatch to me, but everything I could find indicated that the vendor version I have, being the latest, is the right one.
What am I missing? Can someone with more experience solve this puzzle, or at least lead me in a direction where I know which questions to ask on my own and can get things to start making sense again?
I appreciate your help! Thanks!
Click to expand...
Click to collapse
Your vendor image and build number do sound like they are mismatched. If you can't find the vendor image you need on XDA you can find the matching build on the Google site, download the whole factory image and unzip it and get the vendor image that way.
I believe TWRP 3.0.2-0 was buggy. I'm not familiar with Multi rom and I don't know why they would use that build. You should be using 3.0.2-3 or 3.0.3-0.
I personally wouldn't install a custom ROM before activating the phone. I know a couple people have reported in the past that they were unable to activate their phone on a custom ROM. Hopefully you won't have that issue.
jhs39 said:
I believe TWRP 3.0.2-0 was buggy. I'm not familiar with Multi rom and I don't know why they would use that build. You should be using 3.0.2-3 or 3.0.3-0..
Click to expand...
Click to collapse
MultiRom support for this device was released when Marshmallow was out. So MR33 is based on the Marshmallow branch and ships with 3.0.2. The developer just isn't ready to release support for Nougat 7.0 and couple that with the issues of TWRP 3.0.2-x. He's actively pushing commits to support Nougat.
Sent from my Nexus 5X using Tapatalk
jhs39 said:
Your vendor image and build number do sound like they are mismatched. If you can't find the vendor image you need on XDA you can find the matching build on the Google site, download the whole factory image and unzip it and get the vendor image that way.
I believe TWRP 3.0.2-0 was buggy. I'm not familiar with Multi rom and I don't know why they would use that build. You should be using 3.0.2-3 or 3.0.3-0.
I personally wouldn't install a custom ROM before activating the phone. I know a couple people have reported in the past that they were unable to activate their phone on a custom ROM. Hopefully you won't have that issue.
Click to expand...
Click to collapse
Thanks for the input! I actually just got my card and some of the activation seems complete. (I got my voice mails and so on, but no data connection yet.) I didn't have a problem with the Nexus 6 on PureNexus, but we'll have to see how this one plays out. I'm not able to call over WiFi yet.
KilgoreTrout71 said:
Thanks for the input! I actually just got my card and some of the activation seems complete. (I got my voice mails and so on, but no data connection yet.) I didn't have a problem with the Nexus 6 on PureNexus, but we'll have to see how this one plays out. I'm not able to call over WiFi yet.
Click to expand...
Click to collapse
It might just take a while for the service to go through. Good luck.

Having problem rooting my Axon 7 A2017U

Hey guys, first of all sorry about my english, im french.
So my problem is: I tried rooting my Axon 7 A2017U many times, with different guides. I always end up with a softbricked phone, having to restore to stock using MiFlash.
My bootloader is unlocked, i have stock recovery and stock rom for now.
Whenever i flash TWRP, either the signed one (from @tenfar) or unsigned (and up to date) ones, i can't go past the menu saying something like "your phone cant be checked for corruption, please lock your phone [...]" it just freeze. i did read somewhere that i should flash chainfire's root or a special .zip that, i guess, disabled some check that could prevent booting a phone with unsigned stuff/edited system (after flashing TWRP, so it could boot) that didn't work out. i think i found that information in some LineageOS thread here on XDA.
My ultimate goal would be to get a rooted stock nougat 7.1.1, up to date TWRP recovery and to be able to switch to LineageOS to try it out soon.
For what it is worth, i rooted many phones over the years, so while i'm no expert, i should be able to follow most of the steps you give me.
Thanks alot!
What version of TWRP did you flash first?
I have the same root problem i can not install in twrp install in twrp ok but su application displays no root cause i have latest twrp
KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one
KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one
Okay. Download and flash this one alone via fastboot and see what happens. This is one the I personally use. It is required for any of the newer versions to work properly.
twrp-3.0.2-2-a2017u.img
You can choose to rename it to just recovery.img, then:
1. fastboot flash recovery recovery.img
or
2.
if you choose to work with the same filename:
fastboot flash recovery twrp-3.0.2-2-a2017u.img
Select reboot to recovery from the bootloader menu now and try again.
Either way, should work fine. I know you mentioned you knew the basics, but just want to be sure.
Also forgot to mention. If TWRP works but you still can't get your phone to boot, you need to follow this guide here
You can start from the part that says:
-----------------------------------------------------
UPDATING FROM B20_Boot / B20 / B27 / B29 / B15(N)
-----------------------------------------------------
Again, that's the ROM I personally use if I want to go back to stock, not the one from the ZTE site.
Gonna try it and give feedback. thanks for taking time to help!
edit: im downloading the rom from the link you shared.
like you said, i can get TWRP to boot but not the phone.
So if i use full stock from ZTE, it can't boot with modified recovery?
edit 2: i don't know what worked, i think it might be the bootstack. or the rom by DrakenFX. now i can boot to the rom with a TWRP recovery installed. It worked, but i soft bricked again trying to flash SuperSU. So now i'm retrying with an updated TWRP.
I haven't tried that yet, but I really suspect that's the reason you're having problems. I rarely use pure stock ROMs. Like you, I'm not an expert in Android Development so I can't tell you why. Just been a flashaholic for years so made a few observations.
Which supersu are you installing? If you're swiping to the right in twrp, you need to install the dm-verity zip or supersu 2.79. There's some issues with newer builds.
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.
lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable
Click to expand...
Click to collapse
Glad you're up and running root. :good:
lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.
Click to expand...
Click to collapse
Yeah, like I mentioned before that was the base TWRP you needed to flash first, before any of the newer ones. You weren't intended to use it indefinitely.
There's a lot of Dev love for our device now and support is growing ... exciting new ROMs cropping up. Don't hesitate to try them out.

Categories

Resources