No camera on MMB29K? - Nexus 5X Q&A, Help & Troubleshooting

I just flashed the Factory Image MMB29K (flash-all.bat then reinstalled TWRP and SU manually). Now the camera doesn't work (see attachment below). I did check the MD5 and it matched.
Any help is greatly appreciated.

Very odd. If I do not install TWRP (I have tried both 2.8.7.0 and 2.8.7.2) or SU (Beta 2.52) the camera works fine. Or maybe it's the version of the modified boot image (Chainfire's mdb08i) that's not compatible.

Disregard. Found another thread with a discussion of the same issue. The problem is with the old mdb08i boot image.
In case anyone is experiencing the same issue please see this post:

The way I just rooted 2 5x's was, I unlocked the bootloader, flash-all on the MMB29K update, reinstalled TWRP, and then installed Super SU v2.61. You don't have to use a modified boot, that version of Super SU does the modifying for you. Just make sure to read the directions - I got caught in a boot loop trying to install 2.61 over a modified boot (essentially I did the process backwards the first time.) Recovered, and did both phones just fine. Camera works great.

How is that systemless root - any problems so far? I was feeling lazy so stuck with the old fashioned version - haven't had time to read up on the new method.

The only problem I have had so far (and I had the same problem on system root as systemless) is when I boot into TWRP, it brings up the pattern lock. The problem is, sometimes it doesn't recognise my touch on the pattern, so I can't get it to mount the Data partition. When that happens, I either have to flash whatever I was going to flash using USB-OTG (luckily I bought one of these, and got it the same day the phone arrived) or keep re-booting into system, then back into recovery until I get it to work. Might be able to take the pattern off before I go into recovery, but that'd be a pain - and I think I'd have to re-do fingerprints every time, too.

Danariel - thanks for the reply. I think I'll wait until the next go around of updates before trying out the systemless root. Feeling extremely lazy right now.

Related

[Q] Quick question about stock recovery

Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
ericksonline said:
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
Click to expand...
Click to collapse
Yes you can go to software number to get the info you need. To do an OTA you need a stock sense ROM (NO CHANGES TO ANY SYSTEM APPS) you then need to flash the correct recovery for your software number and [IMPORTANT] relock the bootloader. You then can reboot into your system and take the OTA while still being able to unlock the bootloader and flash a custom recovery afterwards.
No need to relock the bootloader for an ota. People should stop spreading that info
Thanks for the replies!
Just to check my understanding, since I simply unlocked the bootloader, used the TWRP recovery, added SuperSU, installed then uninstalled Xposed framework, that means that I should still be on a stock sense ROM (with no changes to any system apps), right?
There is a lot to learn with all of this when you are first starting out. I'm reading a lot, but sometimes you do find conflicting information. I'd rather be a little cautious than do something stupid!
Thanks again!
ericksonline said:
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
Click to expand...
Click to collapse
ericksonline said:
Thanks for the replies!
Just to check my understanding, since I simply unlocked the bootloader, used the TWRP recovery, added SuperSU, installed then uninstalled Xposed framework, that means that I should still be on a stock sense ROM (with no changes to any system apps), right?
There is a lot to learn with all of this when you are first starting out. I'm reading a lot, but sometimes you do find conflicting information. I'd rather be a little cautious than do something stupid!
Thanks again!
Click to expand...
Click to collapse
Yup you're good ROM wise. Just flash the stock recovery and you should be good to go.
You can be unlock and have OTA.
You just need a stock recovery.
HTC ONE M8 fails to load up after failed software update
Hello guys, this is my first post. I really need your help as I'm at risk of loosing all my phone data. My phone internal memory had been exhausted and I bought an external SD card. I am unable to transfer data to the external SD card. I was doing a software update on my phone that failed to install, there was a warning sign on the phone screen for a few minutes then it try to power on but has failed, as it's seem to stuck on the screen that display htc powered by android. I tried the recovery holding down the power button and the column up button, the phone power off and back on but is still stuck on this screen (htc powered by android). I tried connecting the phone to my laptop to try and recover my data, but it's not mounting to the laptop. Please can someone help me. Thanks in advance.
Similar to the post above ie rooted and kept on stock. Also loaded a few Xposed modules but when I connected to my wifi I had over 30 updates so loaded all of them and once loaded the old bootloop started. I restored my nandroid backup from TWRP (this is an essential backup) and I was back in action. Phew!!!! I no longer had Xposed. So I did the updates again and the same thing happened. I am now updating one at a time which is painful when you've got so many. I also tried wiping the caches but that didn't work.
I noticed there were a lot of HTC apps eg HTC sense input, service pack, blinkfeed etc. I also notice a super SU update. ericksonlines post above said he had a problem with superSU. What kind of problem? What does he mean by reapplying? Flashing from TWRP?
So the big question. Which app(s) update did the damage???
Any apps I shouldn't update eg HTCs?
Has this happened to anyone else? What did you then do? Is the new updated superSU the problem
Apologies for cross posting on an Australian site but I'm a bit frazzled with all of this.
jbarr3 said:
Similar to the post above ie rooted and kept on stock. Also loaded a few Xposed modules but when I connected to my wifi I had over 30 updates so loaded all of them and once loaded the old bootloop started. I restored my nandroid backup from TWRP (this is an essential backup) and I was back in action. Phew!!!! I no longer had Xposed. So I did the updates again and the same thing happened. I am now updating one at a time which is painful when you've got so many. I also tried wiping the caches but that didn't work.
I noticed there were a lot of HTC apps eg HTC sense input, service pack, blinkfeed etc. I also notice a super SU update. ericksonlines post above said he had a problem with superSU. What kind of problem? What does he mean by reapplying? Flashing from TWRP?
So the big question. Which app(s) update did the damage???
Any apps I shouldn't update eg HTCs?
Has this happened to anyone else? What did you then do? Is the new updated superSU the problem
Apologies for cross posting on an Australian site but I'm a bit frazzled with all of this.
Click to expand...
Click to collapse
Hello! It is possible that an update came through that caused my phone to start into the boot loop. I'm not sure because it worked fine for a few hours before the problem started happening all of the sudden. My guess is that something updated that broke SuperSU. As soon as something would try to use SuperSU (or maybe the rights granted by SuperSU), the phone would crash and reboot. To fix the problem, I rebooted into the bootloader (TWRP) and re-installed SuperSU from there. After I re-installed, everything began working nicely again. I have not had a problem since and the problem occurred a few months ago now. I have also recently updated to the new version of SuperSU with no problems at all.
I hope this helps!
Ron
ericksonline said:
Hello! It is possible that an update came through that caused my phone to start into the boot loop. I'm not sure because it worked fine for a few hours before the problem started happening all of the sudden. My guess is that something updated that broke SuperSU. As soon as something would try to use SuperSU (or maybe the rights granted by SuperSU), the phone would crash and reboot. To fix the problem, I rebooted into the bootloader (TWRP) and re-installed SuperSU from there. After I re-installed, everything began working nicely again. I have not had a problem since and the problem occurred a few months ago now. I have also recently updated to the new version of SuperSU with no problems at all.
I hope this helps!
Ron
Click to expand...
Click to collapse
You're dead right Ron. Supersu was the culprit. Just simply updating from the playstore caused this. I restored an android backup which got me back. I went into the old SuperSu (V1.94) and clicked "clean up when updating from google play" or similar, did the update again (v 2.04 from google) and while this didn't cause rebooting, I couldn't install the binary. I chose "normal" (maybe I should have chosen TWRP) and it didn't work. So I flashed my old v1.94 from TWRP and that got me back. So some questions on updating SuperSu.
1. Is flashing the zip file through TWRP the best way to install a new version?
2. Should I delete or uninstall the old version or will flashing do that for me? Did you simply flash over the top of the other one?
3. Should I stick with 1.94, which works, or should I update to a new and improved version?
4. I think 2.16 is the latest. What version are you running, is it stable and do you recommend it ?
5. I assume I get the zip file from chainfire. They are way ahead of the google playstore for updates
jbarr3 said:
You're dead right Ron. Supersu was the culprit. Just simply updating from the playstore caused this. I restored an android backup which got me back. I went into the old SuperSu (V1.94) and clicked "clean up when updating from google play" or similar, did the update again (v 2.04 from google) and while this didn't cause rebooting, I couldn't install the binary. I chose "normal" (maybe I should have chosen TWRP) and it didn't work. So I flashed my old v1.94 from TWRP and that got me back. So some questions on updating SuperSu.
1. Is flashing the zip file through TWRP the best way to install a new version?
2. Should I delete or uninstall the old version or will flashing do that for me? Did you simply flash over the top of the other one?
3. Should I stick with 1.94, which works, or should I update to a new and improved version?
4. I think 2.16 is the latest. What version are you running, is it stable and do you recommend it ?
5. I assume I get the zip file from chainfire. They are way ahead of the google playstore for updates
Click to expand...
Click to collapse
I'm no expert, but I'm happy to share my experience. I do believe that flashing from TWRP is the best way to install. That is what I did to fix my reboot problems. I don't recall uninstalling the previous version in any way. I think the old file was still on there. I browsed to it in TWRP and installed it. I'm not sure what version I was on when I did this. Recently, a new update (2.16) was available that downloaded through the Play Store. When I went to update, it recommended that I use TWRP to install. I didn't go this route because I had already switched back to the default bootloader and didn't want to reinstall TWRP if I didn't have to. So, I just used the "normal" method. It updated successfully and I've had no problems. I am now running 2.16.
ericksonline said:
I'm no expert, but I'm happy to share my experience. I do believe that flashing from TWRP is the best way to install. That is what I did to fix my reboot problems. I don't recall uninstalling the previous version in any way. I think the old file was still on there. I browsed to it in TWRP and installed it. I'm not sure what version I was on when I did this. Recently, a new update (2.16) was available that downloaded through the Play Store. When I went to update, it recommended that I use TWRP to install. I didn't go this route because I had already switched back to the default bootloader and didn't want to reinstall TWRP if I didn't have to. So, I just used the "normal" method. It updated successfully and I've had no problems. I am now running 2.16.
Click to expand...
Click to collapse
Thanks erick but given what's happened I don't think I'll ever update from the playstore again. I'll load 2.16 using TWRP and report back. I can't stress enough how important it is to have a nandroid backup. I reckon its the best reason to load a custom recovery. Its got me out of trouble twice now and gives me piece of mind. I've actually gone overboard on this and I have two backups on my phone which I have copied to my PC..
vm54 said:
You can be unlock and have OTA.
You just need a stock recovery.
Click to expand...
Click to collapse
And stock ROM.
Updated to v 2.16. Piece of cake!!!
Loaded through TWRP, rebooted and that was it. It didn't even ask about installing the binary. Same binary I guess.
It worried me, however, when I saw over 700 pages on this version xda. Most with problems.
jbarr3 said:
Updated to v 2.16. Piece of cake!!!
Loaded through TWRP, rebooted and that was it. It didn't even ask about installing the binary. Same binary I guess.
It worried me, however, when I saw over 700 pages on this version xda. Most with problems.
Click to expand...
Click to collapse
Awesome! I'm glad to hear that it worked!

**UPDATE** Mounting Errors in Custom Recovery

Couple of new tabs were recently released into the wild with some "revisions". Those who went thru Groupon, Frys, and Best Buy received tabs with 5.0.1 pre installed out of box.. Because of this you couldn't go back to any 4.x.x builds as the bootloader wouldn't allow it. After posting this and finding out about this issue some XDA members were able to find a fix and confirmed that this solution is a working solution.
TL;DR
Any Custom Recovery had problems mounting SD/Partitions making flashing roms, zips, ect a problem.
**WARNING**
I AM NOT RESPONSIBLE FOR ANY MISFORTUNE YOU RECEIVE BY APPLYING ANY INFO PAST THIS POINT. YOU TAKE SOLE RESPONSIBILITY FOR YOUR ACTION AND NO ONE HERE BUT YOURSELF IS ACCOUNTABLE.
I have included both LTE (DEB) and WIFI(FLO) setups that are currently working and are confirmed working by XDA members here. Apply based on your device. This works for both 5.0.1 and 5.0.2. ADB or Wugs program is sufficient enough to complete this task.
WIFI (FLO) https://drive.google.com/file/d/0B3fHxCdm5V_Mc2szNnFzT1I0eVk/view?usp=sharing
LTE (DEB) https://drive.google.com/file/d/0B3fHxCdm5V_MU1hfXzV6dFlEZ2c/view?usp=sharing
**NOTE**
The only way so far to root tab is to use cf-auto root. Google it and follow directions.
ADB setup:
Download recovery img and place into location where you ADB resides (or leave in download folder and open CMD in downloads for global ADB users)
make sure ADB is working and confirm that you Nexus is recognized
Code:
Code: adb devices
After confirmation get tab into bootloader mode
Code:
adb reboot bootloader
Flash recovery image (Depending on tab version)
FLO:
Code:
fastboot flash recovery TWRP_multirom_flo_20150328.img
DEB:
Code:
fastboot flash recovery TWRP_multirom_deb_20150328.img
Once flash is complete confirm by booting into recovery and check to see if SD/Partitions mounted. Click the small square in the bottom and see if everything mounted correctly. if you see any red status stating mount error in (system, userdata, system -w, cache, ect something went wrong repeat process)
From this point your are good to go. Be advised flashing roms has a very particular setup that needs to be followed, reported by several members. I will show below
Wugs Nexus Toolkit
http://forum.xda-developers.com/showthread.php?t=2389107
Download your recovery image
Open Wugs Nexus Toolkit
Setup device preference
Go into advance
Click flash recovery
choose recovery image file
Let toolkit do its thing and when complete click boot recovery to confirm everything went ok
On device
Use cf-auto root to root your tab. Google it as it not hard to find. Once you confirmed root you can then download your image file on device and use flashify, TRWP Manager, (anything you can flash recovery on device)
Example:
Once root is confirmed use Flashify to select recovery image to flash. Once flash is complete boot into recovery by any means. confirm no error are present.
**FLASHING ROMS**
When installing any ROM disable "inject multirom after installation" & after installation just hit reboot system (don't hit "MultiROM: Inject curr. Boot sector) once you hit reboot you should be fine!
Direct link to files and some info for recovery
http://forum.xda-developers.com/showthread.php?t=2457063
Good Luck and hope everything works out.
Ok so here goes my issue. I just got my Nexus 7 2013 in the mail yesterday. I bought it specially to install in my Mitsubishi Lancer. Well going thru the motion that nay flasher would go thru I got machine environment setup (drivers, adb/fastboot, wugs program).
I unlocked thru Wugs OEM unlock procedure then followed with root + custom recovery
Thats where my problems start. Root was not sticking correctly/at all. I got all kinds if error thru TRWP about it unable to mount emmc, boot, userdata, system,....
I have restored thru Wugs program several timers now. I have full access to the tab as far as ADB and Fastboot. I have tried
Phliz Rcovery
CWM
TRWP
In All recoverys I get errors that I cannot mount any partitions and reads 0MB available. I have found cf-auto root to root my Nexus 7 so at least theres that but Im trying to flash either Timurs Kernel or Elemental but cant due to recovery cannot mount anything.
What I have done so far...
OEM Unlock -Pass
Wugs root + custom recovery - failed due to mounting issues
cf-auto root - Pass
Fastboot Erase: System -w, system, userdata, boot, recovery, cache - Pass
Fasboot format: System -w, system, userdata, boot, recovery, cache - Pass
stock recovery factory reset/cache wipe - Pass
At this point am i just SOL and just return my tab ( got it thru Groupon for $149.99 brand new) or is there hope and maybe im just not getting it right which i doubt as I did the same for my Nexus 6 and unlocked/rooted.
--------------
I dont know if this will help but my Tab came in out of box 5.0.1. When booted up an update for 5.0.2 was available so I took it.
here are some screenshots to help better explain. These are off TWRP and CWM. Also got a pic of my computer telling me that im on a wrong system setup even though I havent changed anything.,
So I went ahead and did flashed stock recovery. I am able to wipe cache and factory reset. Im still wondering if it just any custom recovery Im flashing that is preventing any kind of mounting.
Starting to see a trend now. Anyone who somehow if you got your tab with 5.0.1 out of the box and either updated to 5.0.2 you may run into issues with custom recovery not being able to mount partitions and what not.
Posting as much info as I can to see if anyone can help me as well as the thread either above me or below with trwp issues. So i tried loading up CM Installer as usually thats my sure fire way to install a custom rom should something be wrong on my end. CM Installer went thru the motion of getting everything setup and right after is indicates to plug in device for prepping and flashing a service warning comes up saying that
"Firmware unsupported for your device at this time"
Then big blue button to close application. So Im not sure what do at at this time as I am currently exhausting all my resources and Google maybe be getting tired of all my Nexus 7 search request.
Also update on what other "procedures" that I attempted
Download terminal from Play store. Tried setting sd as full mount - FAILED
^^ this actually made my tab go full retard as boot up and then kept booting into recovery(TWRP) and if I tired to reboot system or shutdown it would just boot back into TWRP. I had to use WUGS to full flash stock.
Same when trying chmod commands to force mount or force -rw
Booted into recovery and attempted to "ADB Shell" in recovery. Commands were recognized but denied due to mounting issues.
As much abuse I send to it I can still recover from it. I am kinda concerned that if I abuse it to much I may break it. Heres a weird thing
I tried cf-autoroot and watched the commands go thru and saw that cf-auto root can mount /system and /data and declare full mount and root device. After that you see that it puts files in their respected places
So looks like twrp updated there recovery today gonna see if this fixes anything
Well the the TWRP 2.8.6.0 didn't work either. I'm not sure what to do at this point as I've tried as many things as I can google and can't figure it out. I'm afraid that if try to claim replacement by group on I may get another tab that is similar to this which means I may have problems progressing forward with my goals.
I'm in the same boat, I was surprised to see that the cf autoroot went through without a *****.
I also tried to flash a 4.4.4 image and it wouldn't boot up or go past the google logo.
If anyone has any insight to this,it would be greatly appreciated.
I'm going to try flashing from otg when my cable comes in. I'll report back after.
Having the same issue too. Unboxed mine today, and went to look how to root, I can unlock it fine but whenever I go in recovery I can't do anything. Android still boots fine...
fragon69 said:
I'm in the same boat, I was surprised to see that the cf autoroot went through without a *****.
I also tried to flash a 4.4.4 image and it wouldn't boot up or go past the google logo.
If anyone has any insight to this,it would be greatly appreciated.
I'm going to try flashing from otg when my cable comes in. I'll report back after.
Click to expand...
Click to collapse
Did your tab out the box come 5.0 or higher. Seems like anyone who got there tab recently had 5.0 or later factory installed. Also with bootloaders you cannot go back when you pass a certain update in this case you if you ever hit 5.0.1 or higher then you cannot go back to anything 4.x.x. Also depends on what your tab shipped with
TrentB said:
Having the same issue too. Unboxed mine today, and went to look how to root, I can unlock it fine but whenever I go in recovery I can't do anything. Android still boots fine...
Click to expand...
Click to collapse
Yeah same here. I wanna get a video of me trying to complete everything. I mentioned this earlier but I am thinking thinking that any tab recently received and has 5.x.x out of box may have a problem. I'm trying to get devs to look I to this but all I'm getting is just get another tab or buy a used one. It doesn't solve the fact that you can still pick up a new one in stores and the ones coning out now are on 5.x.x I'm not trying to buy a second tab from Craigslist when I have a brand new first owner tab in front of me. **sigh first world problems.
TrentB said:
Having the same issue too. Unboxed mine today, and went to look how to root, I can unlock it fine but whenever I go in recovery I can't do anything. Android still boots fine...
Click to expand...
Click to collapse
When you setup your nexus did were you on 5.0.1 and asking for update when you were done with setup
Yeah, I got mine from Groupon too. 5.0.1 out of the box. Running it now on 5.0.2 stock and it is OK so I may put off rooting for a while until it gets settled.
DEVICE build DATE2014.12 later
android.googlesource.com/kernel/msm.git/+/fa842060088619d2de9986c5c5d588d0f40534e3%5E%21/
.......TWRP2.8.6 no FIX X(
masterchiefb117 said:
Ok so here goes my issue. I just got my Nexus 7 2013 in the mail yesterday. I bought it specially to install in my Mitsubishi Lancer. Well going thru the motion that nay flasher would go thru I got machine environment setup (drivers, adb/fastboot, wugs program).
I unlocked thru Wugs OEM unlock procedure then followed with root + custom recovery
Thats where my problems start. Root was not sticking correctly/at all. I got all kinds if error thru TRWP about it unable to mount emmc, boot, userdata, system,....
I have restored thru Wugs program several timers now. I have full access to the tab as far as ADB and Fastboot. I have tried
Phliz Rcovery
CWM
TRWP
In All recoverys I get errors that I cannot mount any partitions and reads 0MB available. I have found cf-auto root to root my Nexus 7 so at least theres that but Im trying to flash either Timurs Kernel or Elemental but cant due to recovery cannot mount anything.
What I have done so far...
OEM Unlock -Pass
Wugs root + custom recovery - failed due to mounting issues
cf-auto root - Pass
Fastboot Erase: System -w, system, userdata, boot, recovery, cache - Pass
Fasboot format: System -w, system, userdata, boot, recovery, cache - Pass
stock recovery factory reset/cache wipe - Pass
At this point am i just SOL and just return my tab ( got it thru Groupon for $149.99 brand new) or is there hope and maybe im just not getting it right which i doubt as I did the same for my Nexus 6 and unlocked/rooted.
Click to expand...
Click to collapse
rsusami said:
DEVICE build DATE2014.12 later
android.googlesource.com/kernel/msm.git/+/fa842060088619d2de9986c5c5d588d0f40534e3%5E%21/
.......TWRP2.8.6 no FIX X(
View attachment 3231340
Click to expand...
Click to collapse
Hmmmm I just checked mine and its 2015/02. I got another yesterday and that one is 2015.01. FML looks like new Nexus 7 coming out made a revision.
Yea mine was from 2014.12, from groupon too
fragon69 said:
Yea mine was from 2014.12, from groupon too
Click to expand...
Click to collapse
TrentB said:
Yeah, I got mine from Groupon too. 5.0.1 out of the box. Running it now on 5.0.2 stock and it is OK so I may put off rooting for a while until it gets settled.
Click to expand...
Click to collapse
Kinda weird that Groupon selling nexus on deals a d they for some reason no work right. Lol
One more with same issue
Bought from Groupon as will, came with 5.0.1. Haven't updated to 5.0.2 yet.
Unlocked bootloader and installed TWRP. It cannot mount anything (tried 2.8.6.0, 2.8.2.2, 2.8.1.0).
I hope this is a fixable issue. Would hate to return the tablet.
texag said:
Bought from Groupon as will, came with 5.0.1. Haven't updated to 5.0.2 yet.
Unlocked bootloader and installed TWRP. It cannot mount anything (tried 2.8.6.0, 2.8.2.2, 2.8.1.0).
I hope this is a fixable issue. Would hate to return the tablet.
Click to expand...
Click to collapse
Looking at other forums reporting that all Nexus 7 bought from Groupon having the same problems. I bought 2 more, 1 from Frys and another from Best Buy. They are also having issues. Something that they are shipping with them that is making it a problem.

[root] [ZS570KL] Asus Zenfone 3 Deluxe fast rooting method. Despite TWRP

Not tested on nougat.
I use adb and fastboot , twrp, supersu.
Files We need:
TWRP: It's bogus, in my phone the screen flips upsidedown: Connect a mouse thru female usb or try to figure out how to tap in a rotated screen with a non rotated touch panel.
TWRP Download -> https://drive.google.com/file/d/0B0XMYw0cbs_cdm5FZW1DQXl4MFU/view
SuperSU file - > https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip?retrieve_file=1
For ADB access thru MAC:
1.- First of all we have to get open USB debug mode to get adb acces to the phone by going to Settings -> About -> Software Information -> Tap 7 times over Build number.
2.- After we get Developer options available we have to put the phone on usb debugging by goig to "Settings-> Developer Options" Activate USB Debugging.
3.- Install android platform-tools on your PC/Linux/MAC , in my case had work on MAC and no devices acces thru ADB on PC :silly: .
platform-tools -> http://www.androidpolice.com/2017/0...ble-without-full-sdk-android-studio-download/
Here you have the 3 options to download ADB and FASTBOOT
4.- Connect your phone to the PC (USB) and copy SuperSu to the root of your phone, a place that its easy too acces, cause TWRP, for the moment flips the screen.
5.- Copy TWRP3.0.XXX.zip to the folder where you have platform-tools installed.
6.- Reboot your phone to bootloader and in Linux could work too:
./adb reboot bootloader [./ is placed cause I don't put platform-tools on the my PATH]
After the boot, then we have to boot on TWRP
./fastboot boot twrp-3.0xxxx.zip (you don't flash anything) If you want to flash TWRP, at your awn risk, ./fastboot flash recovery twrp-3.0xxxx.zip".
Well, now you have to see TRWP on your phone screen.
My recomendation is to play a little bit with the flipped screen if you don't have a female USB to plug a mouse.
7.- Trying to make a complete backup of the phone could be a good practice to move on TWRP with the flipped screen . Tap backup option and make a Backup. Always recomended!
8.- After Backup, you can go to INSTALL SuperSU.zip file. "Install -> look for your SuperSU.zip file "
9.- Go to Playstore and install supersu app.
Now you can test your root, after reboot for example tryin to install some APP that requires root. Fast move:
./adb shell
su root
It has to appear a screen to grant root access to the phone.
10. Done!
Well I think thats my second post at all, hope can help someone to root the phone.
I placed In Questions and Answers cause XDA says want to protect us from SPAM.
Feel free to correct me anything.
Kronen_75
Your links do not work.
jnmacd said:
Your links do not work.
Click to expand...
Click to collapse
Links are corrected. Thanks!
You can also substitute Magisk instead of Supersu if you need to use any of the pay apps or have root sensitive apps...
Without the right Twrp, many benefits to rooting are missing such as removing stock rom applications. Seems without being able to boot to a recovery, even Titanium cannot remove apps because it needs to clean the dalvic.. Can't do it without a recovery
Sent from my ASUS_Z016D using XDA-Developers Legacy app
Download the right twrp here: https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA
You should change your title !!
Tested on nougat.
The variant ZS550KL can be rooted with same method on latest firmware with nougat
Very nice guide, Thank you. Could you please provide updated links to both TWRP and SuperSU. I am currently using TWRP 3.1.1-0 and it functions properly after hanging for approximately 45 seconds on boot. This may be due to the fact my phone is encrypted. I initially rooted without installing TWRP (fastboot boot twrp.img) but have since flashed it. Both ways work well. The posted version of SuperSU did result in root but caused me to lose cell service! The phone could "see" the sim card but not use it. Updating to SuperSU 2.82 solved that issue. This was all done on my finally rooted ZenFone 3 Deluxe Special Edition (Z016D)!!!
I unfortunately figured something out the other day. Using TWRP 3.1.1-0 I am able to install zip files, complete wipes, make & restore backups. The issues only arise after you restore your nandroid image. Everything works except for two things.
1. The ability to hear audio during phone calls. The phone is actually able to place calls but you are unable to hear or record any phone audio. Oddly enough I was able to play music and use voice dictation. It was only in-call audio that seemed to be affected.
2. If you have a pin set when you create your nandroid image your pin will no longer work once restored. You will be locked out of your own phone!!
Fortunately both are fairly easily resolved and keep TWRP relatively useful, although a bit bothersome!
To resolve the pin issue it is necessary to use the TWRP file manager or ADB to delete 5 files (listed below) and regain entrance to your phone. Once deleted simply reboot the phone and reset your pin. If you remove your pin before creating a backup this issue is averted completely.
/data/system/gatekeeper.pattern.key
/data/system/gatekeeper.password.key
/data/system/locksettings.db
/data/system/locksettings.db-wal
/data/system/locksettings.db-shm
To re-enable call audio use TWRP (install zip) to reflash the same version firmware from the Asus website over your current install without wiping. This will restore any system apps you may have removed but you should still have root and can easily remove them again. There will be two errors when performing the flash, which is why I believe root is retained but the system image will be reflashed. Reboot and enjoy
I sincerely hope I have not caused anyone any issues! Or that someone else finds this information useful. I have tested everything in this post at least three times. All testing was done on the most recent Android 7 firmware on my ZenFone 3 Deluxe Special Edition (SnapDragon 821/6/256).
Sandman45654 said:
I unfortunately figured something out the other day. Using TWRP 3.1.1-0 I am able to install zip files, complete wipes, make & restore backups. The issues only arise after you restore your nandroid image. Everything works except for two things.
1. The ability to hear audio during phone calls. The phone is actually able to place calls but you are unable to hear or record any phone audio. Oddly enough I was able to play music and use voice dictation. It was only in-call audio that seemed to be affected.
2. If you have a pin set when you create your nandroid image your pin will no longer work once restored. You will be locked out of your own phone!!
Fortunately both are fairly easily resolved and keep TWRP relatively useful, although a bit bothersome!
To resolve the pin issue it is necessary to use the TWRP file manager or ADB to delete 5 files (listed below) and regain entrance to your phone. Once deleted simply reboot the phone and reset your pin. If you remove your pin before creating a backup this issue is averted completely.
/data/system/gatekeeper.pattern.key
/data/system/gatekeeper.password.key
/data/system/locksettings.db
/data/system/locksettings.db-wal
/data/system/locksettings.db-shm
To re-enable call audio use TWRP (install zip) to reflash the same version firmware from the Asus website over your current install without wiping. This will restore any system apps you may have removed but you should still have root and can easily remove them again. There will be two errors when performing the flash, which is why I believe root is retained but the system image will be reflashed. Reboot and enjoy
I sincerely hope I have not caused anyone any issues! Or that someone else finds this information useful. I have tested everything in this post at least three times. All testing was done on the most recent Android 7 firmware on my ZenFone 3 Deluxe Special Edition (SnapDragon 821/6/256).
Click to expand...
Click to collapse
The second issue happens in all the phones/twrp.
It's possible to install the firmware from asus website with twrp?? To update i flash the stock recovery, install the firmware, then reflash twrp and supersu. Didn't know that! It updates successfully with twrp??
Thank you Ryder for confirming my suspicion that the pin issue may have been a more common one with TWRP. This is the first phone I actually cared enough about to use a pin. I was thrown for a loop when I first booted my fresh nandroid restore and the pin I know I've been using was incorrect!
As for installing firmware, with the two errors that occurred during I don't know that you would be able to do full scale upgrade to a higher version. To reinstall the system partition however it does seem to work quite well. I tested this part four times. To do so download the correct device/version firmware to the phones storage, click install, and select that file. After it completes I like to wipe both the cache and the dalvik cache before restarting the phone. The audio issue was unfortunately easily reproduced on my phone, but thankfully equally easy to resolve. This worked for me each time without fail.
Sandman45654 said:
Thank you Ryder for confirming my suspicion that the pin issue may have been a more common one with TWRP. This is the first phone I actually cared enough about to use a pin. I was thrown for a loop when I first booted my fresh nandroid restore and the pin I know I've been using was incorrect!
As for installing firmware, with the two errors that occurred during I don't know that you would be able to do full scale upgrade to a higher version. To reinstall the system partition however it does seem to work quite well. I tested this part four times. To do so download the correct device/version firmware to the phones storage, click install, and select that file. After it completes I like to wipe both the cache and the dalvik cache before restarting the phone. The audio issue was unfortunately easily reproduced on my phone, but thankfully equally easy to resolve. This worked for me each time without fail.
Click to expand...
Click to collapse
You said that the two issues occurred when you restored the nandroid backup and to fix one of them by installing the zip firmware from asus website with twrp... I don't understand. I can install zip firmware with twrp or i have to flash the stock recovery and install with it? Errors may occur using the twrp? Sorry
Everything done in my post so far has been in TWRP. Honestly I didn't even back up the recovery image. TWRP seemed to work flawlessly so I bit bullet and flashed it.
On a sidenote I am currently testing the usability of FlahFire on this device. It appears to create a very nice fastboot installable recovery image! I have yet to restore the image however. I will post my findings here once I have thoroughly tested it.
Sandman45654 said:
Everything done in my post so far has been in TWRP. Honestly I didn't even back up the recovery image. TWRP seemed to work flawlessly so I bit bullet and flashed it.
On a sidenote I am currently testing the usability of FlahFire on this device. It appears to create a very nice fastboot installable recovery image! I have yet to restore the image however. I will post my findings here once I have thoroughly tested it.
Click to expand...
Click to collapse
Ok. I'm interested in flashing zip firmware to update. Never tried that. I thought that firmware can be installed only with stock recovery. The stock recovery can be downloaded in an asus forum website
This is the first time I have flashed anything in almost a year. I got to thinking and this is the most success I have had was flashing a stock image with TWRP! I doubt it will perform a full flash. I believe the errors are most likely for the boot and recovery partitions. As a save my butt reflash the system partition it does work. It sounds like it's time to find some TWRP changelogs!
Sandman45654 said:
This is the first time I have flashed anything in almost a year. I got to thinking and this is the most success I have had was flashing a stock image with TWRP! I doubt it will perform a full flash. I believe the errors are most likely for the boot and recovery partitions. As a save my butt reflash the system partition it does work. It sounds like it's time to find some TWRP changelogs!
Click to expand...
Click to collapse
I don't care about stock images... If i can't flash the zip with twrp to update successfully then i reflash the stock recovery and after the update root again with twrp and supersu. By the way, the zip firmare contains factory images? I thought it contains different kind of files
Ryder. said:
By the way, the zip firmare contains factory images? I thought it contains different kind of files
Click to expand...
Click to collapse
I lack the knowledge to answer that with enough certainty to even call it an answer! This is my foray into the insides of this phone and I don't want to start posting my hunches.
What I do know is you can flash the system partition using TWRP. I have done it several times. Asus's zips run as a script based zip install. You are offered no options during install. When the script runs you will see two errors quickly scroll past.
Ryder. said:
Download the right twrp here: https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA
Click to expand...
Click to collapse
Are you creating these TWRP builds? If so thank you very much! TWRP-3.1.1-0-Z016-20170826 seems to work flawlessly! No lag on boot and no known issues after restoring a backup unlike before.
I wanted to post my finding about FlashFire by Chainfire. I have had great success with the fastboot backup! It is the only option I have tested extensively however. I have been running the same fastboot restored phone since soon after my last post on this topic with no issues discovered.
Sandman45654 said:
Are you creating these TWRP builds? If so thank you very much! TWRP-3.1.1-0-Z016-20170826 seems to work flawlessly! No lag on boot and no known issues after restoring a backup unlike before.
I wanted to post my finding about FlashFire by Chainfire. I have had great success with the fastboot backup! It is the only option I have tested extensively however. I have been running the same fastboot restored phone since soon after my last post on this topic with no issues discovered.
Click to expand...
Click to collapse
No. It's not me. It's another user which i don't remember the nickname
Ryder. said:
No. It's not me. It's another user which i don't remember the nickname
Click to expand...
Click to collapse
Okay thank you. If you happen to find out/remember please let me know. I would like to give credit with my project and thank them for their hard work.

How long after flashing superSU zip does first boot take?

First time messing with this phone
followed the instructions for unlocking bootloader, installing TWRP, and rooting here: https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592
Successfully unlocked bootloader, flashed TWRP, but now hung up on SuperSU.
Flashed SuperSU VV2.82 zip from http://www.supersu.com/download in TWRP
Wiped dalvik and cache
reboot
Now it's been about 10 minutes. Blank screen and blue LED.
Hold power until it reboots again, Android sometimes has issues with new boot.imgs at first
l3ones said:
Hold power until it reboots again, Android sometimes has issues with new boot.imgs at first
Click to expand...
Click to collapse
I did, three times.
I ended up flashing the latest complete OTA to get it back to being able to boot.
Are you on Oreo? I don't know if SuperSU is compatible with it. I switched to Magisk a few weeks ago.
Macusercom said:
Are you on Oreo? I don't know if SuperSU is compatible with it. I switched to Magisk a few weeks ago.
Click to expand...
Click to collapse
was on the latest stock OTA, which was 8.0.0
Flashed Mgisk after flashing the latest OTA, and everything is working swimmingly
Exact Same thing happened to me last night.
And I lost my internal sdcard.
Eventually flashed stock recovery didn't do anything different so flash twrp again and got sdcard back.
It was a strange one.
Now I'm waiting for an update or the right file for root.
Maybe this has something to do with Keymaster?
So, I've been trying to get my OP5t working for a solid six hours straight, and I'm just about to loose my mind.
I'm sorry if this isn't the right place to post this. I've always just sorta lurked about in here.
Here's the deal for my OP5t.
Now I'm stuck in a situation where I can get my phone to boot on all of the OOS versions I've mentioned, but always without root. And If I do manage to get it booting, I end up loosing TWRP and having to reflash it through fastboot.
Since I've always just relied on Titanium backup (yes I know, how silly) I've never had any trouble restoring my backups, but since I've now lost root and being unable to obtain it again, I'm locked out of all my sweet app data. It's all a bit messy now, and I think I'm begging to repeat previous steps and combinations, but here's a list of what I've tried. I really hope some white knight comes to the rescue.
It all happened when I tried doing a clean flash wiping caches, data and system of OOS 5.0.3 (coming from the latest official OOS Nougat build). It all started when I tried to flash the magisk 15.3 after this boot, which resulted in ERROR 1.
- I've tried installing both the old version the previous nougat build and the two most recent stable oreo ones. Wiping thoroughly inbetween even, since at this point I have nothing left to loose.
- Whenever I try to flash magisk 15,1 /3 or 4 I get error 1. Whenever I try to flash supersu (s.82 included the modded SR5 version) I Just don't get root or end up in an endless +1 screen (before the spinner) for 12+ minutes.
- I've tried flashing the stock boot.img
- I've tried all of the above in combination with bluspark recovery 8.61 and 69 + the r100 kernel
- I've tried using codeworks cheesburger and dumpling recoveries
What am I missing here? I assume my phone is encrypted since it asks for a code to open TWRP.
I've never had any issues so grave that I couldn't just search my way through it, but this time I'm at my wits end, and just about ready to settle(tm) for no root.
I've never tried exporting a log, but I sense that I do that from TWRP and then grab it via a file manager from some folder?
Use codeworkx dumpling TWRP, dirty flash your ROM, boot it once, then reboot to recovery and flash Magisk 15.3. Should be all you need.
For Nougat, I think it's better to flash Magisk 14, on some ROMs.
New apps
Great information provided by many users. I have just joined this group and read many experts advice. Thanks
Latest SuperSU (beta 2.85 i believe) don't work on OP5T Oreo update (stable or Open Beta). Don't know why, but I had to use Magisk. ANd I must say, I'm pretty happy with it, too!
Elfomze said:
So, I've been trying to get my OP5t working for a solid six hours straight, and I'm just about to loose my mind.
I'm sorry if this isn't the right place to post this. I've always just sorta lurked about in here.
Here's the deal for my OP5t.
Now I'm stuck in a situation where I can get my phone to boot on all of the OOS versions I've mentioned, but always without root. And If I do manage to get it booting, I end up loosing TWRP and having to reflash it through fastboot.
Since I've always just relied on Titanium backup (yes I know, how silly) I've never had any trouble restoring my backups, but since I've now lost root and being unable to obtain it again, I'm locked out of all my sweet app data. It's all a bit messy now, and I think I'm begging to repeat previous steps and combinations, but here's a list of what I've tried. I really hope some white knight comes to the rescue.
It all happened when I tried doing a clean flash wiping caches, data and system of OOS 5.0.3 (coming from the latest official OOS Nougat build). It all started when I tried to flash the magisk 15.3 after this boot, which resulted in ERROR 1.
- I've tried installing both the old version the previous nougat build and the two most recent stable oreo ones. Wiping thoroughly inbetween even, since at this point I have nothing left to loose.
- Whenever I try to flash magisk 15,1 /3 or 4 I get error 1. Whenever I try to flash supersu (s.82 included the modded SR5 version) I Just don't get root or end up in an endless +1 screen (before the spinner) for 12+ minutes.
- I've tried flashing the stock boot.img
- I've tried all of the above in combination with bluspark recovery 8.61 and 69 + the r100 kernel
- I've tried using codeworks cheesburger and dumpling recoveries
What am I missing here? I assume my phone is encrypted since it asks for a code to open TWRP.
I've never had any issues so grave that I couldn't just search my way through it, but this time I'm at my wits end, and just about ready to settle(tm) for no root.
I've never tried exporting a log, but I sense that I do that from TWRP and then grab it via a file manager from some folder?
Click to expand...
Click to collapse
Same kind of problem here. After clean flashing Oreo can't root anymore. Flashing Magisk ends up in Bootloop. Tried various combinations of TWRPs and Magisk versions, no use. :/
Kunjuuuz said:
Same kind of problem here. After clean flashing Oreo can't root anymore. Flashing Magisk ends up in Bootloop. Tried various combinations of TWRPs and Magisk versions, no use. :/
Click to expand...
Click to collapse
Okay so I managed to figure it out. The problem seemed to be that where one TWRP version could flash magisk, another wouldn't be able to decrypt the phone properly, which I think is what caused the bootloops/non sticky root for me (though I'm by no means sure of this).
I managed to get it worked out by fiddling around a bit more with the different versions and using the a Remix ROM to remove the pin (which I probably should've done initially). I also noticed that I didn't originally pay attention to the fact that codeworks' (non universal) recoveries are aimed at 8.0 and 8.1 respectively, which might have complicated things a bit more for me.
Sorry for spamming up the thread. I hope you figure things out though
The latest SuperSu does not work with 8.1 for us and some other (or all other) 8.1 phones.
And... SuperSu is no longer in development.
Rumor has it a slightly older SuperSu version works in 8.1 but I never got around to trying it and forget the version # now.
And Lineage has not released a SuperSu/superuser for 8.1 yet.
It bums me out because I want that Magisk alternative.
Not a fan of Magisk yet.
Elfomze said:
Okay so I managed to figure it out. The problem seemed to be that where one TWRP version could flash magisk, another wouldn't be able to decrypt the phone properly, which I think is what caused the bootloops/non sticky root for me (though I'm by no means sure of this).
I managed to get it worked out by fiddling around a bit more with the different versions and using the a Remix ROM to remove the pin (which I probably should've done initially). I also noticed that I didn't originally pay attention to the fact that codeworks' (non universal) recoveries are aimed at 8.0 and 8.1 respectively, which might have complicated things a bit more for me.
Sorry for spamming up the thread. I hope you figure things out though
Click to expand...
Click to collapse
Locking the bootloader, wiping, and unlocking the bootloader again fixed the issue for me.

Nexus 5x major rooting issues, help!

****** Would really appreciate some help here...
I've tried to install quick reboot (zips), magik, (zips) and busybox, on 3.4 0-0 twrp, and it won't work to boot to system, still says on this version it cannot mount the system. I don't have the perma-recovery file as I cannot find it online, and nexus root toolkit doesn't download it in the dispensaries, latest version.
Hope I haven't knacked it, i also have some screenshots but it doesn't matter as I cannot access the system itself, unless i am missing something it should just boot back to system, I don't understand what I am doing wrong, or have done wrong. Got the img and everything with it.
That said, the mount storage issue is the only thing red, or wrong in the flash, everything else worked apparently, said it installed without a hitch. Which was different that with the standard NRT downloaded twrp, with supersu, as that didn't work.
It just goes back to twrp constantly, can't boot. Help. Really wish I just waited for a response here first. Also I don't believe this is a bootloop, as it just goes back to twrp not bootloader or anything else, probably wrong.
I have been using this vid from the start: realizing that wasn't doing it, magik and a new bionic busybox zip eventually did the trick on 3.4 0-0 twrp, but it sitll won't boot to system. It is probably something obvious, I have been on this for hours today and yesterday, no luck.
only thing i can think of is something to do with: fastboot flash recovery twrp-3.2.1-0-fbe-4core-bullhead.img
basically i flashed the latest version, i dunno if it's supported by nexus 5x.
thanks. uh just please say it ain't bricked.
Anyone?!
edit:
hi all, after immense pain, stress and struggle to get the thing to mount, and trying everything suggested online, it eventually just like "soft-bricked" or whatever, like it was just perma-stuck on the google screen and wouldn't boot to system. i am guessing it's because after a mistake it wiped the system.
i have managed to flash it back to stock, everything is there, and/or redownloading. no way am i gonna bother again, like if it ain't broke don't fix it at this point that would be foolish thought it was perma broke. i'm gonna get a profressional to do it or something, or to give me one to one support to try it again. in the meantime i am going to learn more about rooting and the NRT and all the fundamentals of that.
if anyone here has advice about this still, or articles where I can read about it online, where to learn etc. I'd appreciate that as well, thanks.
Cam3333 said:
****** Would really appreciate some help here...
I've tried to install quick reboot (zips), magik, (zips) and busybox, on 3.4 0-0 twrp, and it won't work to boot to system, still says on this version it cannot mount the system. I don't have the perma-recovery file as I cannot find it online, and nexus root toolkit doesn't download it in the dispensaries, latest version.
Hope I haven't knacked it, i also have some screenshots but it doesn't matter as I cannot access the system itself, unless i am missing something it should just boot back to system, I don't understand what I am doing wrong, or have done wrong. Got the img and everything with it.
That said, the mount storage issue is the only thing red, or wrong in the flash, everything else worked apparently, said it installed without a hitch. Which was different that with the standard NRT downloaded twrp, with supersu, as that didn't work.
It just goes back to twrp constantly, can't boot. Help. Really wish I just waited for a response here first. Also I don't believe this is a bootloop, as it just goes back to twrp not bootloader or anything else, probably wrong.
I have been using this vid from the start: realizing that wasn't doing it, magik and a new bionic busybox zip eventually did the trick on 3.4 0-0 twrp, but it sitll won't boot to system. It is probably something obvious, I have been on this for hours today and yesterday, no luck.
only thing i can think of is something to do with: fastboot flash recovery twrp-3.2.1-0-fbe-4core-bullhead.img
basically i flashed the latest version, i dunno if it's supported by nexus 5x.
thanks. uh just please say it ain't bricked.
Click to expand...
Click to collapse
issues such as what youve experienced are usually caused by version mismatches. I dont have this device and am unfamiliar with the root process for it, but it shouldnt be too different from any other phone. what is the baseband version of your actual phone?
look at this specific reply in this thread
GUIDE - Fix bootloop with locked bootloader via ADB/Fastboot (Android M, N, O)
Hi, Here is fix for those, who have problem with bootloop on 5X with locked bootloader and OEM unlock disabled. This tutorial works for Beta Android O bootloop too. You will need: ADB + drivers installed...
forum.xda-developers.com

Categories

Resources