FORUMS
Remove All Ads from XDA
Honor View 10

**UPDATE** Mounting Errors in Custom Recovery

266 posts
Thanks Meter: 115
 
Post Reply Email Thread
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/0B3f...ew?usp=sharing
LTE (DEB) https://drive.google.com/file/d/0B3f...ew?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/show....php?t=2389107

Download your recovery image
  1. Open Wugs Nexus Toolkit
  2. Setup device preference
  3. Go into advance
  4. Click flash recovery
  5. choose recovery image file
  6. 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/show....php?t=2457063


Good Luck and hope everything works out.
The Following 30 Users Say Thank You to masterchiefb117 For This Useful Post: [ View ] Gift masterchiefb117 Ad-Free
 
 
26th March 2015, 04:38 AM |#2  
masterchiefb117's Avatar
OP Senior Member
Flag Los Angeles
Thanks Meter: 115
 
More
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.
The Following User Says Thank You to masterchiefb117 For This Useful Post: [ View ] Gift masterchiefb117 Ad-Free
26th March 2015, 04:59 AM |#3  
masterchiefb117's Avatar
OP Senior Member
Flag Los Angeles
Thanks Meter: 115
 
More
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.,
Attached Thumbnails
Click image for larger version

Name:	IMG_20150325_193524.jpg
Views:	1660
Size:	230.9 KB
ID:	3229545   Click image for larger version

Name:	IMG_20150325_194022.jpg
Views:	3788
Size:	251.3 KB
ID:	3229546   Click image for larger version

Name:	IMG_20150325_194414.jpg
Views:	1994
Size:	250.0 KB
ID:	3229547   Click image for larger version

Name:	IMG_20150325_194109.jpg
Views:	1978
Size:	239.6 KB
ID:	3229548  
The Following 2 Users Say Thank You to masterchiefb117 For This Useful Post: [ View ] Gift masterchiefb117 Ad-Free
26th March 2015, 11:09 AM |#4  
masterchiefb117's Avatar
OP Senior Member
Flag Los Angeles
Thanks Meter: 115
 
More
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.
The Following User Says Thank You to masterchiefb117 For This Useful Post: [ View ] Gift masterchiefb117 Ad-Free
26th March 2015, 12:09 PM |#5  
masterchiefb117's Avatar
OP Senior Member
Flag Los Angeles
Thanks Meter: 115
 
More
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.
The Following User Says Thank You to masterchiefb117 For This Useful Post: [ View ] Gift masterchiefb117 Ad-Free
26th March 2015, 03:31 PM |#6  
masterchiefb117's Avatar
OP Senior Member
Flag Los Angeles
Thanks Meter: 115
 
More
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
The Following User Says Thank You to masterchiefb117 For This Useful Post: [ View ] Gift masterchiefb117 Ad-Free
26th March 2015, 06:58 PM |#7  
masterchiefb117's Avatar
OP Senior Member
Flag Los Angeles
Thanks Meter: 115
 
More
So looks like twrp updated there recovery today gonna see if this fixes anything
The Following User Says Thank You to masterchiefb117 For This Useful Post: [ View ] Gift masterchiefb117 Ad-Free
26th March 2015, 07:32 PM |#8  
masterchiefb117's Avatar
OP Senior Member
Flag Los Angeles
Thanks Meter: 115
 
More
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.
The Following User Says Thank You to masterchiefb117 For This Useful Post: [ View ] Gift masterchiefb117 Ad-Free
26th March 2015, 09:58 PM |#9  
Junior Member
Thanks Meter: 0
 
More
I'm in the same boat, I was surprised to see that the cf autoroot went through without a bitch.
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.
27th March 2015, 02:25 AM |#10  
Senior Member
Thanks Meter: 3
 
More
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...
27th March 2015, 05:19 AM |#11  
masterchiefb117's Avatar
OP Senior Member
Flag Los Angeles
Thanks Meter: 115
 
More
Quote:
Originally Posted by fragon69

I'm in the same boat, I was surprised to see that the cf autoroot went through without a bitch.
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.

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
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes