**UPDATE** Mounting Errors in Custom Recovery - Nexus 7 (2013) Q&A

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.

Related

No camera on MMB29K?

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.

Boot loop and factory image restore

Hi,
I'm writing here as a last hope, after I've tried every possible solution I could find online. Any help here will be very much appreciated.
Couple of days ago I received my fresh Nexus 5X, that I plan to use with Project Fi.
After unlocking the bootloader (with Google Support blessing!) and installing TWRP+SuperSU, I ran into problems, big problems.
Following the Android wizard setup, I connected to the wifi and the phone started downloading an update of ~79Mb.
When rebooted, though, it started TWRP, and it didn't go ahead.
To play safe, I decided to do a factory reset, using the official ROM from Google, replacing also TWRP with the original recovery (I basically did every step in the "flash-all.sh" script).
That didn't work either, and the phone now gets stuck at the boot animation.
I've tried also wiping partitions using both fastboot ("fastboot -w...") and TWRP, but nothing worked.
Another diagnostic symptom.
I've noticed that the recovery (TWRP for sure, the stock one not so much sure) had problems finding the sdcard partition ("unknown volume for path couldn't mount sdcard installation aborted").
Could that be a source of issues?
I thought that it would be possible to do a factory reset, but I'm probably missing something.
At this point, I'm completely lost and I don't know what to do.
Thanks in advance.
Try the flash all script again with latest firmware and let it boot up completely. It will take a while, once booted, flash TWRP and root if you want.
ntropia said:
Hi,
I'm writing here as a last hope, after I've tried every possible solution I could find online. Any help here will be very much appreciated.
Couple of days ago I received my fresh Nexus 5X, that I plan to use with Project Fi.
After unlocking the bootloader (with Google Support blessing!) and installing TWRP+SuperSU, I ran into problems, big problems.
Following the Android wizard setup, I connected to the wifi and the phone started downloading an update of ~79Mb.
When rebooted, though, it started TWRP, and it didn't go ahead.
To play safe, I decided to do a factory reset, using the official ROM from Google, replacing also TWRP with the original recovery (I basically did every step in the "flash-all.sh" script).
That didn't work either, and the phone now gets stuck at the boot animation.
I've tried also wiping partitions using both fastboot ("fastboot -w...") and TWRP, but nothing worked.
Another diagnostic symptom.
I've noticed that the recovery (TWRP for sure, the stock one not so much sure) had problems finding the sdcard partition ("unknown volume for path couldn't mount sdcard installation aborted").
Could that be a source of issues?
I thought that it would be possible to do a factory reset, but I'm probably missing something.
At this point, I'm completely lost and I don't know what to do.
Thanks in advance.
Click to expand...
Click to collapse
I wonder if you need a modified boot.img or kernel since you are rooted .In my experience since Android 5.1.1 you need a custom kernel for root and sometimes a modified boot.img after flashing twrp
Sent from my Nexus 5X using XDA Free mobile app
androidddaaron said:
I wonder if you need a modified boot.img or kernel since you are rooted .In my experience since Android 5.1.1 you need a custom kernel for root and sometimes a modified boot.img after flashing twrp
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
That's an interesting perspective, actually.
I didn't know that you needed a special image for rooted devices.
Although, I would imagine that's always possible to 'un-root' it, and honestly I was hoping that 'fastboot flash -w...' would have removed any trace of the root.
Is that the case?
Either way, where could I find these modified images?
Thanks a bunch!
Solved
I found the solution which, as it happens when nothing seems to be wrong, was fairly trivial.
Basically, the scripts provided with the stock ROM from Google has problems, and this last command fails:
Code:
fastboot update image-bullhead-mmb29p.zip
saying that system.img is missing.
To fix that, you have to manually extract the content of the files and proceed to flash manually userdata, system, etc...
The problem is that if you don't flash also vendor.img, you're in trouble, and the device will not boot.
Some of the guides that I've found were suggesting that you need to do it for the Nexus 9, and I didn't notice when other guides were mentioning it.
Once you flash the vendor.img, the boot loop is gone.
I'll put it here, I hope it can be helpful to somebody.
Thanks to androidddaaron and k.s.deviate for the support!
(I've thanked also used the thank button near the posts, but if there's more to do, let me know)
Now, back to mess up the Project Fi SIM...

How Do I Flash Factory Image?

It's been some time since I've done this so I'm hoping someone can point me in the right direction. I've had my Pixel 2 XL for like a month now...but since day one I've gotten occasional force closes of various apps. Well next week I'm going with a new carrier (Koodo here in Canada) and I thought it would be a great time to flash a factory image to make sure everything is correct. Also when does Google release monthly updates? Is it the first week of April, maybe I'll just wait and flash that factory image when it comes out. Thanks for the help.
acheney1990 said:
It's been some time since I've done this so I'm hoping someone can point me in the right direction. I've had my Pixel 2 XL for like a month now...but since day one I've gotten occasional force closes of various apps. Well next week I'm going with a new carrier (Koodo here in Canada) and I thought it would be a great time to flash a factory image to make sure everything is correct. Also when does Google release monthly updates? Is it the first week of April, maybe I'll just wait and flash that factory image when it comes out. Thanks for the help.
Click to expand...
Click to collapse
If your wanting to flash a factory image, you'll need a few things first.
I would highly recommend that you look over the linked thread carefully. It has many links and tips to help you on your way :good:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
acheney1990 said:
It's been some time since I've done this so I'm hoping someone can point me in the right direction. I've had my Pixel 2 XL for like a month now...but since day one I've gotten occasional force closes of various apps. Well next week I'm going with a new carrier (Koodo here in Canada) and I thought it would be a great time to flash a factory image to make sure everything is correct. Also when does Google release monthly updates? Is it the first week of April, maybe I'll just wait and flash that factory image when it comes out. Thanks for the help.
Click to expand...
Click to collapse
https://developers.google.com/android/images
Make sure you have the latest adb and fastboot. Get them from Google...
Go get the latest image and Unzip it. Do not Unzip the folder inside. Move everything you just unzipped into the folder with adb and fastboot.
Now, if you've unlocked and unlocked critical, great. If you haven't unlocked critical, you'll have to. The system image won't install if the bootloader is out of date. Sadly, this will wipe your data.
If both are already unlocked, then open the flash-all file with a text editor and remove the,"-w" and the space preceding, then save the file. Removing the -w will keep your data. Run the flash-all.bat file and in about 10 minutes everything will be flashed.
back to stock
how to back on stock ....i sell the phone and want all stock...no root no boot loader unlocked ...what is the fastest way pls
lomski said:
how to back on stock ....i sell the phone and want all stock...no root no boot loader unlocked ...what is the fastest way pls
Click to expand...
Click to collapse
First thing!! Forget fast!! You need to fastboot flash a full factory image with the -w still in the script. Maybe even do it twice. Then go in and do a factory reset from the OS for good measure. Once that is done and you know it reboots you can go through the locking command. I would NOT toggle the OEM switch in dev though.
Sent from my Pixel 2 XL using XDA Labs
So this has been a a very frustrating experiance but I think I've got everything working again. I don't know how many times I've flashed different factory images and then tried to install TWRP and then install a new custom rom. So I want to explain all of the steps I took (if I remember them all).
0. I couldn't boot into my system but had TWRP installed. At this point I should have tried to get all my data from the sd card via "adb pull /sdcard" .
1. I didn't find any option to fix my system. So I followed this guide to install a factory image (link).
3. I skipped through all of the setup processes and gave my phone wifi. Then I went into the system and did a factory reset.
4. After skipping thourgh the setup again I enabled adb and bootet into the bootloader "adb reboot bootlader"
5. From the bootloader I booted into TWRP by "fastboot boot twrp-3.3.0.0-taimen.img. In the recovery I set the display time out to 300s because for some reason once the phone timed out I could get into twrp any more and the screen stayed black.
6. I transferred the twrp installer and my rom by " adb push TWRP_installer.zip /sdcard/Download" and " adb push ROM.zip /sdcard/Download"
7. I first added the TWRP installer to the flash queue and then I added the rom and then falshed them both. This allowed me to install the rom.
8. For some reason TWRP was not installed. So repeat step 5 and only flash the TWRP_installter.zip
Problems I had:
- In twrp I often got errors that said unable to mount system or vendor. I decided to ignore the error but this thread might help
- Installing TWRP while the stock rom is installed led to the problem that touch didn't work in TWRP
- Entering a pin for the stock rom and then installing TWRP led to TWRP asking for a pin to decrypt my data. Apparently this is not the case if you use a stock image which is older
After flashing stock ROM ota and twrp installer zip the only way to get TWRP to respond to touch is if you disable screen lock and connect to your PC before booting TWRP.
I've found the most reliable way to flash factory images is do it manually with fastboot, latest platform tools installed and a Linux OS like Ubuntu or pop os.
But first do some research and get comfortable with fastboot commands. And dear god don't relock your bootloader unless you're ?% sure it's totally stock.
@schpongo,
Also, a good point to keep when flashing via TWRP is to flash/install ONE AT A TIME. As per the great @Az Biker, you should even reboot to the bootloader after each subsequent flash/install. So, in your case, it seems that you might/should be rebooting to the bootloader three times; one for TWRP installation, one for flashing the custom ROM, and one more for any other subsequent installation (i.e. custom kernel or custom font)...
Also, as it's been said before, but stock kernel doesn't play nice with touch commands on TWRP, and (usually) the only way around it is to reboot into bootloader using the adb command -- as opposed to holding the volume-down button or from an app.
I know you figured this all out already, but it might bear repeating just in case you didn't know and/or to help any other users here...

Oldtimer turned NUBE question

Hey everyone,
I have been rooted for a LONG time, but have been gone for a year or 2. I have the OnePlus 3 that IS rooted with:
Experience OS R11.0 with
Kernel 3.18.31-perf+
[email protected] #1
7.1.1
OP3_o2_open_18
This one has served me well, but may be a bit obsolete.
What rom and kernel can I use now from 7.1.1 What must I do? I see 8.0 and such, and a host of others. Will I lose everything if I upgrade to a new version? I always do a nandroid, and I have Titanium Backup, which I THINK keeps apps, etc...
I remember having trouble installing Roms way back when. Not sure if it was a TWRP issue, as I also had Philz at one point. ( I Have TWRP now, but not sure which version) I had to use what i have (Which IS a GREAT ROM) because I was afraid to brick my phone, because I had so much trouble getting a rom to load. I constantly remember the little android falling over saying "Leave me the **** alone. If I boot to recovery, I just get the TWRP screen 3.1.0.0 that never opens. It just stays on that page and never opens, so I have to turn off the phone to reboot to turn on
I sincerely apologize for not remembering or keeping up.
Have a great day
wascapsfan said:
Hey everyone,
I have been rooted for a LONG time, but have been gone for a year or 2. I have the OnePlus 3 that IS rooted with:
Experience OS R11.0 with
Kernel 3.18.31-perf+
[email protected] #1
7.1.1
OP3_o2_open_18
This one has served me well, but may be a bit obsolete.
What rom and kernel can I use now from 7.1.1 What must I do? I see 8.0 and such, and a host of others. Will I lose everything if I upgrade to a new version? I always do a nandroid, and I have Titanium Backup, which I THINK keeps apps, etc...
I remember having trouble installing Roms way back when. Not sure if it was a TWRP issue, as I also had Philz at one point. ( I Have TWRP now, but not sure which version) I had to use what i have (Which IS a GREAT ROM) because I was afraid to brick my phone, because I had so much trouble getting a rom to load. I constantly remember the little android falling over saying "Leave me the **** alone. If I boot to recovery, I just get the TWRP screen 3.1.0.0 that never opens. It just stays on that page and never opens, so I have to turn off the phone to reboot to turn on
I sincerely apologize for not remembering or keeping up.
Have a great day
Click to expand...
Click to collapse
Wow.. Not one answer. What happened to the days where you ask a question, you get ridiculed, then many come out of the woodwork to get you on track...
Oh well........
wascapsfan said:
Hey everyone,
I have been rooted for a LONG time, but have been gone for a year or 2. I have the OnePlus 3 that IS rooted with:
Experience OS R11.0 with
Kernel 3.18.31-perf+
[email protected] #1
7.1.1
OP3_o2_open_18
This one has served me well, but may be a bit obsolete.
What rom and kernel can I use now from 7.1.1 What must I do? I see 8.0 and such, and a host of others. Will I lose everything if I upgrade to a new version? I always do a nandroid, and I have Titanium Backup, which I THINK keeps apps, etc...
I remember having trouble installing Roms way back when. Not sure if it was a TWRP issue, as I also had Philz at one point. ( I Have TWRP now, but not sure which version) I had to use what i have (Which IS a GREAT ROM) because I was afraid to brick my phone, because I had so much trouble getting a rom to load. I constantly remember the little android falling over saying "Leave me the **** alone. If I boot to recovery, I just get the TWRP screen 3.1.0.0 that never opens. It just stays on that page and never opens, so I have to turn off the phone to reboot to turn on
I sincerely apologize for not remembering or keeping up.
Have a great day
Click to expand...
Click to collapse
Make sure you have the latest TWRP by Bluspark, it just works flawless for me and alot of other people.
Take a full backup. Wipe system and both cache partitions. Then flash the latest Experience ROM. For the open beta releases I should stick with stock kernel. Otherwise Franco and Flash kernel would be interesting. For root I should go with Magisk. Everyone uses it nowadays and the modules are super handy.
Twrp issues
I have rooted the One Plus 3. I loaded TWRP about a year and a half ago. Now when I try to go into recovery, TWRP comes up, but never opens. I tried removing it, but it wont remove, and I try to reinstall it using several methods including apps, but to no avail. The bootloader is unlocked and the debugging is on. Any suggestions. I can't do a backup or anything.
Thanks
Dave
wascapsfan said:
I have rooted the One Plus 3. I loaded TWRP about a year and a half ago. Now when I try to go into recovery, TWRP comes up, but never opens. I tried removing it, but it wont remove, and I try to reinstall it using several methods including apps, but to no avail. The bootloader is unlocked and the debugging is on. Any suggestions. I can't do a backup or anything.
Thanks
Dave
Click to expand...
Click to collapse
Boot into fastboot, then connect it to your pc and use fastboot flash recovery. Get the latest TWRP.
I tried that, but it won't take. If I had a tar file, I could try it with Odin, but no matter what I do, when I go into bootloader, it says I'm unlocked, then I try to go into recovery, and TWRP shows up, but typically you get the different choices like backup, install, etc... I stay stuck on the TWRP page, that does not do anything, nor does it give me any choices. I have to shut the phone down each time just to get it back to working mode. I tried the adb method using the cmd prompt, and everything works up to trying to actually flashing TWRP...
wascapsfan said:
I tried that, but it won't take. If I had a tar file, I could try it with Odin, but no matter what I do, when I go into bootloader, it says I'm unlocked, then I try to go into recovery, and TWRP shows up, but typically you get the different choices like backup, install, etc... I stay stuck on the TWRP page, that does not do anything, nor does it give me any choices. I have to shut the phone down each time just to get it back to working mode. I tried the adb method using the cmd prompt, and everything works up to trying to actually flashing TWRP...
Click to expand...
Click to collapse
You may have to flash the original recovery by oneplus , you can find it on one plus downloads in google , make sure before you do anything that you backup anything important like photos , videos to a computer , then download the ROM of choice along with the correct gapps for that ROM and the correct firmware ( most ROMs will include the recommended firmware in their post ) , also download the latest twrp recovery from twrp.me and magisk ( if not included in the ROM ) then its just a matter of wiping system , data , cache and dalvick whilst in twrp , install the ROM with the gapps let the ROM boot and setup a few of your settings then go back into twrp and flash magisk manager and you should be good to go , good luck and make sure you fully read the instructions on the ROM page that you want ...

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