Hello. I'm having an issue with TWRP , the first time I flashed it , it worked perfectly , but this morning I decided to go back to stock and make it like out of the box , because my old rom was messed up.
So I successfully flashed the factory image , I set everything up , I decided to flash TWRP again , everything went well , after that I booted into TWRP and it asked me for a password , I didn't set any password , so I ask myself "WHAT THE F***". Then I decided to retry flashing the factory image , then flashing TWRP , and the same thing happened. I did this circle 10 times , I'm running out of ideas... I just need TWRP to flash SuperSu to install my Pentest tool for work... I can't do anything without them , I'm going to get killed tomorrow If I can't get this done ... ^^ Thank for your help.
Best Regards,
Rozalina
TWRP currently isn't working with MHC19J. Use MMB29V for now if you need TWRP. I'm here looking to see if anyone has found a workaround/fix
Is this on the latest version of the stock ROM (March Update)? If so, they released 2 versions. The MHC19J and MMB29V. The problem is between TWRP and the Nexus 5X's encryption. If that is the case, reflash with the MMB29V version of the March Update. That fixed this problem for me. If you don't have the March Update version of the stock ROM, then you can also try default_password as the password and see if TWRP will then work for you.
Good luck.
The other way to get around the issue if you want to stay on the newest update (MHC19J) is to use an OTG cable to flash SU. I did this just now, and it works. Another suggestion that I saw is to mount cache, since it's not encrypted and flash SU from there, but I did not try that since an OTG cable is easier. This will allow you to be on the newest update until TWRP is fixed to work again.
bg1906 said:
Is this on the latest version of the stock ROM (March Update)? If so, they released 2 versions. The MHC19J and MMB29V. The problem is between TWRP and the Nexus 5X's encryption. If that is the case, reflash with the MMB29V version of the March Update. That fixed this problem for me. If you don't have the March Update version of the stock ROM, then you can also try default_password as the password and see if TWRP will then work for you.
Good luck.
Click to expand...
Click to collapse
havens1515 said:
TWRP currently isn't working with MHC19J. Use MMB29V for now if you need TWRP. I'm here looking to see if anyone has found a workaround/fix
Click to expand...
Click to collapse
That explains everything then! I think I'm going to downgrade! I thought about downgrading but I was so desperate I didn't want to mess everything up again.
Thank you so much!
Rozalina340 said:
That explains everything then! I think I'm going to downgrade! I thought about downgrading but I was so desperate I didn't want to mess everything up again.
Thank you so much!
Click to expand...
Click to collapse
Not sure if its a downgrade because they released both versions. I just think Google needs to be explicit in what is released and what the differences actually are. I anticipate TWRP will have a fix soon for the problem between it and MHC19J.
---------- Post added at 12:10 PM ---------- Previous post was at 12:08 PM ----------
pkadavid said:
The other way to get around the issue if you want to stay on the newest update (MHC19J) is to use an OTG cable to flash SU. I did this just now, and it works. Another suggestion that I saw is to mount cache, since it's not encrypted and flash SU from there, but I did not try that since an OTG cable is easier. This will allow you to be on the newest update until TWRP is fixed to work again.
Click to expand...
Click to collapse
The flashing isn't the problem, it's getting into TWRP all together. Seems the problem stemmed from those of us who purchased the phone at launch and those that purchased after January 2016. If you had no problems getting into TWRP with MHC19J, then you probably got your phone after January 2016. I got mine at launch and MHC19J and TWRP would not play nicely for me so I had to install the MMB29V version of the March Update.
I didn't take any risks , I downgraded to MMB29Q and it works like a charm! I will stay on MMB29Q until TWRP fixes the issue with MHC19J.
New version of TWRP is available which is compatible with MHC19J:
https://plus.google.com/u/0/+JoshuaLynch50036/posts/ZcNqBDvNmo7
havens1515 said:
New version of TWRP is available which is compatible with MHC19J:
https://plus.google.com/u/0/+JoshuaLynch50036/posts/ZcNqBDvNmo7
Click to expand...
Click to collapse
Thanks and YES it does work. I was able to install MHC19J and Root SuperSU 2.68 with TWRP
With the Test1-Version of TWRP works fine for me with MHC19J.:good:
Thanks.
https://dl.twrp.me/bullhead/twrp-3.0.0-1-bullhead.img.html
havens1515 said:
New version of TWRP is available which is compatible with MHC19J:
https://plus.google.com/u/0/+JoshuaLynch50036/posts/ZcNqBDvNmo7
Click to expand...
Click to collapse
Installed today , works perfectly. Thank you!
Sent from my Nexus 5X using Tapatalk
Related
I got my htc one back in January and immediately rooted it with s-off and installed twrp, since then I have been using this rom and it has worked just fine. But recently I got quite sick of sense and when I tried in stall this rom the phone would not work, I tried cm11 after but it would not flash at all giving me an error every time. I read that I need to update my firmware but Im not really sure what that means, or how to tell what firmware I am on(I thought firmware was the same thing as a rom?)
sorry if this is a stupid question, Im not really that good with technology :L
thewaffleninja said:
I got my htc one back in January and immediately rooted it with s-off and installed twrp, since then I have been using this rom and it has worked just fine. But recently I got quite sick of sense and when I tried in stall this rom the phone would not work, I tried cm11 after but it would not flash at all giving me an error every time. I read that I need to update my firmware but Im not really sure what that means, or how to tell what firmware I am on(I thought firmware was the same thing as a rom?)
sorry if this is a stupid question, Im not really that good with technology :L
Click to expand...
Click to collapse
There were some recent changes to CM11 that require a new recovery. Have you tried the latest version of TWRP?
Where you using the CM11 nightlies or M releases?
durgis said:
There were some recent changes to CM11 that require a new recovery. Have you tried the latest version of TWRP?
Where you using the CM11 nightlies or M releases?
Click to expand...
Click to collapse
I used the most recent nightly at the time, this was on Wednesday. Im on twrp 2.6.3.3, could you or someone link me how to update twrp? goomanager does not work for some reason and those are the only tutorials i can find.
thewaffleninja said:
I used the most recent nightly at the time, this was on Wednesday. Im on twrp 2.6.3.3, could you or someone link me how to update twrp? goomanager does not work for some reason and those are the only tutorials i can find.
Click to expand...
Click to collapse
Looks like you're a few versions behind, the latest version (2.7.0.8), and fastboot installation instructions are available at the link below.
http://forum.xda-developers.com/showthread.php?t=2416431
durgis said:
Looks like you're a few versions behind, the latest version (2.7.0.8), and fastboot installation instructions are available at the link below.
http://forum.xda-developers.com/showthread.php?t=2416431
Click to expand...
Click to collapse
thank you
durgis said:
Looks like you're a few versions behind, the latest version (2.7.0.8), and fastboot installation instructions are available at the link below.
http://forum.xda-developers.com/showthread.php?t=2416431
Click to expand...
Click to collapse
I just updated and it still didn't work :C
thewaffleninja said:
I just updated and it still didn't work :C
Click to expand...
Click to collapse
Where there any errors while installing the rom in TWRP? You might try one of the CyanogenMod snapshots instead of a nightly, they're a bit more stable and well tested. Also, make sure that you backup and wipe when switching between different roms.
http://download.cyanogenmod.com/?device=m7vzw&type=snapshot
So I've stayed at 2.19.40.20 because I wanted to wait to see if a better way to unlock the bootloader would be found, but I've given up and unlocked my bootloader (the unoffical way).
I want to get up to speed and update to the latest OTA.
Can I just flash the latest one or do I need to download every one til the newest update and sideload them individually?
If I have to do each one can I just load them one after the other, or do I need to reboot the phone and let it fully load to the OS for every update?
I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.
So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
DiGecko said:
I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.
Click to expand...
Click to collapse
Azdinflash said:
So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
Click to expand...
Click to collapse
Yes that should do it.
I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
The_wolf88 said:
Yes that should do it.
Click to expand...
Click to collapse
Azdinflash said:
I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
Click to expand...
Click to collapse
You need to unroot and make sure you are sideloading the whole 1.1 gig one.
DiGecko said:
You need to unroot and make sure you are sideloading the whole 1.1 gig one.
Click to expand...
Click to collapse
Does unrooting include removing Xposed?
Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.
Wait, if I flash the 1.1 gig stock ROM, do I lose everything in the internal memory?
DiGecko said:
Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.
Click to expand...
Click to collapse
I did a little digging, and it seems that the bootloop was fixed a few days ago:
http://forum.xda-developers.com/zenfone2/general/guide-to-install-xposed-installer-t3116476/page26
J M L said:
There's a new Xposed out, v78, which claims to fix a bootloop on 5.0 roms due to a security fix. I haven't tried it yet because I'm running a backup. Here is the thread and changelog.
We want the sdk21-x86 version.
Installed with no problem in TWRP with the flash able zip. Took a few minutes to boot, but seems to be working.
Click to expand...
Click to collapse
Good to know. No, you would not loose anything, at least I did not. Everything migrated over without any issues.
So I've gotten through sideloading the current version with no hiccups. Booted into system fine, it's the right version in the About section, and my internal memory came through intact.
I've flashed TWRP, and booted into it to install SuperSU when I got this message: "TWRP may have detected an unmodified system partition"
It explains that I can keep it as read only and make it easier to take official updates, but then TWRP will not be able to stop the stock ROM from replacing it and will not offer to root my device.
Should I keep it "Read Only" or should I allow the modification?
Recently I got a nexus 7 2013 5.1.1 LMY48I which I tried to root with NRT. Long story short like many other people I cant get TWRP to mount the files it needs(I get to the automated step that is suppose to open TWRP and install some files from a ZIP archive and it hangs up). First off I have a USB OTG cable coming within a couple days. I have looked for the past couple hours for a solution and keep coming up empty. Basically I have two questions, 1. what files do I need to have transferred so that I can get my Root permissions installed properly and 2. should I wait for the USB OTG calbe or should I try to use abs push
I'm in the same boat, really would like to get this thing rooted. I have been all over the WugFresh Forum, as well as Android Central and this one too of course. I have not found an answer to this problem yet. If I come across one I will post here, please do the same.
Dude. this is infuriating. Apparently the alst batch that was made, they changed the mmc chip. These all went out on Groupon and stuff on sale.
https://www.reddit.com/r/AndroidQue...e_to_mount_partitions_after_flashing_twrp_on/
The only recovery that I got to work was the TWRP for Multirom because they actually addressed the issue. The bug has been brought up on the TWRP flo github they just have yet to fix it.
This is infuriating
gorilla p said:
Dude. this is infuriating. Apparently the alst batch that was made, they changed the mmc chip. These all went out on Groupon and stuff on sale.
The only recovery that I got to work was the TWRP for Multirom because they actually addressed the issue. The bug has been brought up on the TWRP flo github they just have yet to fix it.
This is infuriating
Click to expand...
Click to collapse
So what version of Android are you running now. I am on 6.0.1 and want to root it. Did you apply this to to Lollipop or Marshmallow? Thanks for the info.
UPDATE: This worked for me I am now on MM 6.0.1 and rooted. Thank you for the find.
Yea we already have a thread for this..
http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562
sgtfoo said:
Yea we already have a thread for this..
http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562
Click to expand...
Click to collapse
Thank you I was able to downgrade and root my device using that method. Now I just need to figure out how to flash to purenexus or just upgrade my device to 6.+ and root it.
AngryPotato said:
Thank you I was able to downgrade and root my device using that method. Now I just need to figure out how to flash to purenexus or just upgrade my device to 6.+ and root it.
Click to expand...
Click to collapse
You can root 6.0.1 using the beta SU from Chainfire. I am running the new one from Groupon using the multirom TWRP and I flashed SU 2.65 and it worked perfectly.
diggitydogg said:
You can root 6.0.1 using the beta SU from Chainfire. I am running the new one from Groupon using the multirom TWRP and I flashed SU 2.65 and it worked perfectly.
Click to expand...
Click to collapse
so update to 6.0.1 stock then root or flash a rooted rom?
AngryPotato said:
so update to 6.0.1 stock then root or flash a rooted rom?
Click to expand...
Click to collapse
I did a clean flash of stock 6.0.1. Then flashed the multirom version of TWRP since I have one of the newer chipsets of the Nexus 7. Then I flashed the beta SU. All was good. The issue I am having now is that I can't get the restore from within TWRP to work. I backup fine, but when I restore it gets partway through the system part and then just says Failed. Not really sure what the deal is there. I am guessing it has to do with this multirom version of TWRP, but I'm not really sure...
Hey - followed this guide (https://matthewtraughber.github.io/pixel_manual-update_guide/) to update my rooted XL to NMF26O, lost root along the process. Flashing the SR5 supersu.zip didn't give me any errors in TWRP, but supersu isn't installed on boot. If I go into the Play Store and install it manually, I get an error about the SU binary not being installed. Any suggestions?
cantsingh said:
Hey - followed this guide (https://matthewtraughber.github.io/pixel_manual-update_guide/) to update my rooted XL to NMF26O, lost root along the process. Flashing the SR5 supersu.zip didn't give me any errors in TWRP, but supersu isn't installed on boot. If I go into the Play Store and install it manually, I get an error about the SU binary not being installed. Any suggestions?
Click to expand...
Click to collapse
That update permanently block root for your device
cwalker0906 said:
That update permanently block root for your device
Click to expand...
Click to collapse
Even if I have an unlocked bootloader already?
cantsingh said:
Even if I have an unlocked bootloader already?
Click to expand...
Click to collapse
No I'm messing with you, many people have had this problem. Easy fix, read last few pages of root thread
cwalker0906 said:
No I'm messing with you, many people have had this problem. Easy fix, read last few pages of root thread
Click to expand...
Click to collapse
Lol you terrified me. What's the fix? I'm looking for the root thread right now..
cantsingh said:
Lol you terrified me. What's the fix? I'm looking for the root thread right now..
Click to expand...
Click to collapse
Fastboot boot twrp alpha 2, flash the su zip, and reboot
cwalker0906 said:
Fastboot boot twrp alpha 2, flash the su zip, and reboot
Click to expand...
Click to collapse
Got it. Thanks, buddy. I'll post back here to confirm.
Confirmed. If you lost root when updating to NMF26O (or after installing TWRP RC1), then hot-boot TWRP Alpha 2 (fastboot boot twrp-alpha-2.img), flash supersu and reboot. Thanks!
confirmed - worked for me!
cantsingh said:
Got it. Thanks, buddy. I'll post back here to confirm.
Click to expand...
Click to collapse
Confirmed, this saved my life
I had a Pixel XL that had 7.1 on it and rooted it successfully. Not sure when but my phone got updated to 7.1.1 I was careful not to take the update, maybe I inadvertently clicked it (I don't think so) but I think it got forced on me. So I ended up with 7.1.1. Tried using my hotspot which worked before and it didn't. Fortunately my device boot loader was still unlocked, but previous root technique using twrp-3.0.2-0-RC1-fastboot-marlin.img didn't work (seems like it does but after reboot, no joy). Figured if I flashed stock 7.1 image that would do the trick - no joy.
Found this post
Followed suggestion above and used twrp-3.0.2-0-alpha2-fastboot-marlin.img and used same SR5-SuperSU-v2.78 - reboot worked great. FYI, I downloaded the stock 7.1.1 (marlin-nof26v-factory-1dce14a1.zip) and rooting works with that.
Note: turn off "Automatic System Updates" (obviously that was probably the originally culprit) under developer options.
miker2069 said:
Confirmed, this saved my life
I had a Pixel XL that had 7.1 on it and rooted it successfully. Not sure when but my phone got updated to 7.1.1 I was careful not to take the update, maybe I inadvertently clicked it (I don't think so) but I think it got forced on me. So I ended up with 7.1.1. Tried using my hotspot which worked before and it didn't. Fortunately my device boot loader was still unlocked, but previous root technique using twrp-3.0.2-0-RC1-fastboot-marlin.img didn't work (seems like it does but after reboot, no joy). Figured if I flashed stock 7.1 image that would do the trick - no joy.
Found this post
Followed suggestion above and used twrp-3.0.2-0-alpha2-fastboot-marlin.img and used same SR5-SuperSU-v2.78 - reboot worked great. FYI, I downloaded the stock 7.1.1 (marlin-nof26v-factory-1dce14a1.zip) and rooting works with that.
Note: turn off "Automatic System Updates" (obviously that was probably the originally culprit) under developer options.
Click to expand...
Click to collapse
You fastboot twrp rc1 but then flash the twrp rc1 zip and then it should be fine and then flash SuperSU 2.79 sr3.
Hi there, im on custom rom (RR). My question is how can i update my phone via OTA, after that i will gonna root it again.? Just want to update my phone to latest security patch and after updating i will root it again. Can anyone help me? And sorry for noobish query. Thanks for help
Kap_Tutan said:
Hi there, im on custom rom (RR). My question is how can i update my phone via OTA, after that i will gonna root it again.? Just want to update my phone to latest security patch and after updating i will root it again. Can anyone help me? And sorry for noobish query. Thanks for help
Click to expand...
Click to collapse
You will have to reinstall to complete Stock (see link below). You can not OTA from a customer rom.
https://mirrors.lolinet.com/firmware/moto/addison/official/RETEU/
Jimi Mack said:
You will have to reinstall to complete Stock (see link below). You can not OTA from a customer rom.
https://mirrors.lolinet.com/firmware/moto/addison/official/RETEU/
Click to expand...
Click to collapse
If you already did update to Nougat via OTA, flashing that Marshmallow stock image can/will brick your device.
There is a generic RETAIL Nougat Stock image for the April Security Updates flying around somewhere. But generally you should install the stock version you originally had on your device, and then update from there.
BtbN said:
If you already did update to Nougat via OTA, flashing that Marshmallow stock image can/will brick your device.
There is a generic RETAIL Nougat Stock image for the April Security Updates flying around somewhere. But generally you should install the stock version you originally had on your device, and then update from there.
Click to expand...
Click to collapse
I downloaded the nougat april security patch of RETAIL. What do you mean by this "But generally you should install the stock version you originally had on your device, and then update from there"!
And is the retail april is working with my reteu dual sim? Do i still able to receive ota uodate when i flash the april patch?
Kap_Tutan said:
I downloaded the nougat april security patch of RETAIL. What do you mean by this "But generally you should install the stock version you originally had on your device, and then update from there"!
And is the retail april is working with my reteu dual sim? Do i still able to receive ota uodate when i flash the april patch?
Click to expand...
Click to collapse
I have no idea in what channel a phone will end up with the generic RETAIL images. I just did a dump of every single partition on my phone before I installed custom stuff, so I can always get back to how it was originally, and OTA from there.
BtbN said:
If you already did update to Nougat via OTA, flashing that Marshmallow stock image can/will brick your device.
There is a generic RETAIL Nougat Stock image for the April Security Updates flying around somewhere. But generally you should install the stock version you originally had on your device, and then update from there.
Click to expand...
Click to collapse
Below is a link on how to properly downgrade and then be able to take OTA.
---------- Post added at 07:22 AM ---------- Previous post was at 06:54 AM ----------
[/COLOR]
Kap_Tutan said:
Hi there, im on custom rom (RR). My question is how can i update my phone via OTA, after that i will gonna root it again.? Just want to update my phone to latest security patch and after updating i will root it again. Can anyone help me? And sorry for noobish query. Thanks for help
Click to expand...
Click to collapse
Below is a link on how to properly downgrade and then be able to take OTA.
I can not say it enough... I really wish people would first learn how to correct their phones before they make the changes.
It really is simple, would you learn how to properly parachute before or after you jump from the plane?
https://forum.xda-developers.com/mot...grade-t3558118
Below is a link on how to properly downgrade and then be able to take OTA.
I can not say it enough... I really wish people would first learn how to correct their phones before they make the changes.
It really is simple, would you learn how to properly parachute before or after you jump from the plane?
https://forum.xda-developers.com/mot...grade-t3558118[/QUOTE]
Actually this is my first non-samsung phone. That's why totally noob in recovering my phone and revert back to stock. Please sorry for such a noob
Kap_Tutan said:
Below is a link on how to properly downgrade and then be able to take OTA.
I can not say it enough... I really wish people would first learn how to correct their phones before they make the changes.
It really is simple, would you learn how to properly parachute before or after you jump from the plane?
https://forum.xda-developers.com/mot...grade-t3558118
Click to expand...
Click to collapse
Actually this is my first non-samsung phone. That's why totally noob in recovering my phone and revert back to stock. Please sorry for such a noob[/QUOTE]
No problem... any time you change a phone I always suggest to really look at the Guides and Discussion section and get to know the phone well before jumping in and hacking it.. Plus Moto did not make this one as simple to flash and recover as some of their others.
Good Luck.
Jimi Mack said:
Below is a link on how to properly downgrade and then be able to take OTA.
---------- Post added at 07:22 AM ---------- Previous post was at 06:54 AM ----------
[/COLOR]
Below is a link on how to properly downgrade and then be able to take OTA.
I can not say it enough... I really wish people would first learn how to correct their phones before they make the changes.
It really is simple, would you learn how to properly parachute before or after you jump from the plane?
https://forum.xda-developers.com/mot...grade-t3558118
Click to expand...
Click to collapse
FYI link is broken.
ViperX85 said:
FYI link is broken.
Click to expand...
Click to collapse
Sorry, try this one...
https://forum.xda-developers.com/moto-z-play/how-to/autoscript-install-firmware-downgrade-t3558118
Jimi Mack said:
You will have to reinstall to complete Stock (see link below). You can not OTA from a customer rom.
https://mirrors.lolinet.com/firmware/moto/addison/official/RETEU/
Click to expand...
Click to collapse
Is this image signed?
Srandista said:
Is this image signed?
Click to expand...
Click to collapse
As far as I Moto has not released any signed firmware for the Addison.
Just flash this with RSD lite and you`ll have 7.1.1 with aug patch )
St.Noigel said:
Just flash this with RSD lite and you`ll have 7.1.1 with aug patch )
Click to expand...
Click to collapse
Flashing that on my reteu device resulted in a bootloop with the phone playing the "Hello Moto" sound over and over again.
I could flash LineageOS over it and it worked fine, but it did not give me a working stock OS.
BtbN said:
Flashing that on my reteu device resulted in a bootloop with the phone playing the "Hello Moto" sound over and over again.
I could flash LineageOS over it and it worked fine, but it did not give me a working stock OS.
Click to expand...
Click to collapse
You can try to do next:
1. Wipe everything (incl internal storage with TWRP)
2. Format (not wipe) data with TWRP
3. Go to fastboot and flash stock ROM with RSD lite
P.S. If you still have bootloop - just flash TWRP and SuperSU with it. But if you`ll do everything, what i wrote - You`ll have fully worked device.
Good luck )
St.Noigel said:
You can try to do next:
1. Wipe everything (incl internal storage with TWRP)
2. Format (not wipe) data with TWRP
3. Go to fastboot and flash stock ROM with RSD lite
P.S. If you still have bootloop - just flash TWRP and SuperSU with it. But if you`ll do everything, what i wrote - You`ll have fully worked device.
Good luck )
Click to expand...
Click to collapse
Step 3 is what I did originally, including erasing userdata. With that exact stock ROM.
I only wanted to update the bootloader and radio firmware, so I don't overly care it does not boot by itself, as I'm using LaOS.
Just as a note for anyone trying to use that image.