[Q] TWRP 2.8.7.1 - Cannot see files under /sdcard - Nexus 6 Q&A, Help & Troubleshooting

Hi guys, I've been using TWRP for a long time, but this one is a bit of a head-scratcher for me. I'm running stock Android MMB29S on my N6, unlocked bootloader, and unrooted. I decided to install TWRP 2.8.7.1 and then root it with Beta supersu 2.66. The fastboot flashing of TWRP went fine the first time, and I opted to leave TWRP read-only. But I didn't install supersu right afterwards. Rather, I rebooted into system first, and downloaded supersu. When I attempted to reboot into recovery again to flash supersu, I'm finding out that stock recovery has overwritten TWRP. Ok, no problem, I re-flashed TWRP, but this time I allowed it to modify the system (instead of read-only). Now, I'm unable to see anything under /sdcard or any of the other folders when I go to flash the zip. Under the "Mount" Menu, I see that only "cache" is checked. Didn't want to mess with anything there.
Rebooting into system now gives me the "Your device is corrupted..." spiel, which I'm not concerned about, but I really do need to be able to see files in TWRP. Would re-installing TWRP be an option or even a different version of it?

mount system. if its still empty after that, use twrp to locate the right place in the filesystem. yes, like a file explorer app twrp can act

The solution to my problem was actually as simple as just removing the lockscreen passcode. I was wondering why TWRP was asking for that in the first place. Once I removed the lockscreen PIN and went back into TWRP I was able to see all the files. Happily rooted now. :good:

Related

How to Install 4.2 images, keep root and all data

**Disclaimer** If you don't understand what follows, don't attempt this. I'm not responsible for you softbricking your device,
This is a quick guide for how to install the new android without losing anything. You'll need fastboot for this. Also, before doing this, be sure to download the supersu cwm update zip, and have it on your sdcard. Make sure you also already have a custom recovery installed (I did twrp, but i'm sure cwm will work just as well). I would also suggest having a backup done, through titanium backup and through recovery, just incase.
First, download the factory images for the n7 from google's website. Decompress them (if you're in windows, you'll need winrar or something similar.) After you decompress the archive, there'll be another one inside (image-nakasi-jop40c.zip), decompress this one as well. Under here, you'll see the .img files for all the partitions. For now, go up one directory. You'll also see here bootloader-grouper-4.13.img. Once you have all this, reboot into the bootloader.
Once you're in the bootloader, you can update the bootloader to the new version (this step isn't needed, but I did it anyways). Plug into your pc, and type fastboot devices. Make sure it's not blank. If it is, you have to update drivers. If you can see the device, open up a command prompt, and cd to the directory that has the bootloader-grouper file. Type the following:
fastboot flash bootloader-grouper-4.13.img
then, after it's done, type:
fastboot reboot-bootloader
Now, you'll be booted back into the bootloader, it'll say 4.13. On to the rom.
cd into the folder image-nakasi-jop40c (make sure you see the files system.img and boot.img before you continue. If you don't see them, the next steps will do nothing but erase your kernel and system parition.)
now, you see the image files. Type the following (still in the bootloader)
fastboot erase system
fastboot flash system system.img
wait until it completes, then type:
fastboot erase boot
fastboot flash boot boot.img
Once this is done, hit the volume up on the device until it shows recovery mode on the top. When it does, push the power key and you'll boot into your recovery (shouldn't be touched.) Inside here, flash the supersu cwm zip file, which'll flash the superuser binary, and supersu. Once this is done, do a factory reset (removing your data and cache.) Boot into the rom.
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
My first boot got stuck for some reason. if it happens to you, just hold the power button and hard reboot. (I did this on 2 devices, it only happened to one of them, so I figured I'd give you all warning.)
Links:
SuperSu binary: https://docs.google.com/open?id=0B7a8xHNJlpgTR0ZkR1pWZWR2VzA
Google Factory Images: https://developers.google.com/android/nexus/images
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Thanks for this.. Apparently you found out too a clean 4.2 isn't rootable via typical methods.
That SuperSU package did the trick. I have to remember to keep a SuperSU binary on hand for these kinds of situations that SuperUser fails..
jefferson9 said:
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Click to expand...
Click to collapse
Yes. If you do it though cwm, you're not using any exploits, you're just inserting the superuser binary and supersu.apk into the proper places on the rom. On any nexus device, any rom, this will root it.
mstrk242 said:
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place.
Click to expand...
Click to collapse
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
tehSmoogs said:
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
Click to expand...
Click to collapse
Exactly.
If everything goes right we should have an AOSP prerooted build in about *looks at watch* 20 minutes.... Unless there is a compile error or SU error. *laff*
Back to watching the scrolling terminal window
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
kwhee07 said:
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
Click to expand...
Click to collapse
I did this all on linux, just kind of adapted the guide for windows. I figured all the linux users would understand how to do it on their own. Glad to know it's the same for mac as well.
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
rootbrain said:
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
Click to expand...
Click to collapse
Settings - about tablet - build number
push it a few times and it will enable dev options
You have .bat file in the package.
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...gned-nakasi-JOP40C-from-JZO54K.094f6629.zipia
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Here is my method:
1. Download official 4.1.2 from http://forum.xda-developers.com/showthread.php?t=1929270 and 4.2 OTA image from http://forum.xda-developers.com/showthread.php?t=1989188
2. Boot into CWM (i have CWM touch installed)
3. Clear data and install 4.1.2, don't forget to turn on root in the installer
4. reboot check that root is fully working
5. reboot into recovery install 4.2
6. before reboot CWM will ask to disable recovery flash and protect root. Ansver yes to both questions
I'm confused, it says if you are already on a custom rom, just flash as usual.
What makes this different?
I was on stock ROM rooted with some system modifications, and this wwadd the only way I could get the update working...
Sent from my Nexus 7 using xda app-developers app
mstrk242 said:
For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
Click to expand...
Click to collapse
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Ill have to wait until a rooted rom is created, I have no comp.
Sent from my Nexus 7 using XDA Premium HD app
can I install image-nakasi-jop40c.zip directly without upgrading bootloader?
Zuk. said:
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Click to expand...
Click to collapse
Not advisable to move this folder - if it got moved to a new location by the o/s then there's probably a good reason why - maybe like 4.2 introducing multiple users
Each user appears to get their own "home" directory created in /mnt/shell/emulated/
Default user dir is "0"
Second user dir is "10"
Each contain the standard dir's from 4.1 and earlier.
Travelawyer said:
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Click to expand...
Click to collapse
You had two extra characters at the end of your link, but I fixed it above and it's good to go for others in the future. Just flashed it in TWRP, it didn't ask if I wanted to maintain root, hit reboot when it was complete and lost root, so it doesn't work for everyone - good news is that all my data remained intact without having to resort to advanced restoring my data from a backup....
When I tried the SuperSU binary root flash trick, I finally got root back. But don't think it's as easy to get to recovery! I had to obtain the TWRP Recovery one more time since it wiped it and put in place a recovery that did absolutely nothing but reboot the device after a few minutes, so you'll have to
Code:
fastboot flash recovery openrecovery-twrp-2.3.1.1-grouper.img
to get TWRP back.... Hope that helped everyone!

[Q] Cannot root my One

I have unlocked my bootloader via htcdev.
I have flashed CWM, CWMT and TWRP. I could never get TWRP to boot, but I can get CWM and CWMT to boot.
Once in recovery, I go to choose zip to install and I can only browse a few locations such as /0, /audio /Android /video. There are maybe like 6 folders in total. I cannot browse to sdcard or mount sdcard. How can I get my SuperSU zip into one of these folders?
Or....why is it only mounting /system?
I even tried fastboot flash boot recovery.img (DON'T TRY THIS AT HOME FOLKS) so I would boot st8 into recovery and it still mounts the same folders.
msimindlessmsi2 said:
I have unlocked my bootloader via htcdev.
I have flashed CWM, CWMT and TWRP. I could never get TWRP to boot, but I can get CWM and CWMT to boot.
Once in recovery, I go to choose zip to install and I can only browse a few locations such as /0, /audio /Android /video. There are maybe like 6 folders in total. I cannot browse to sdcard or mount sdcard. How can I get my SuperSU zip into one of these folders?
Or....why is it only mounting /system?
I even tried fastboot flash boot recovery.img (DON'T TRY THIS AT HOME FOLKS) so I would boot st8 into recovery and it still mounts the same folders.
Click to expand...
Click to collapse
I had to flash TWRP twice before it took. Don't know why. I also had some issues with rooting so I let TWRP do it for. Figured since they released their new version first for the ONE it should work and it did. All you have to do is go to reset once you get into TWRP and it will ask if you want to root. Pretty nifty if you ask me
LOL guess what I just realized?! I have the Sprint version, which has a different TWRP version and forum LOLZ!

[Q] HTC One - Stuck and need help please.

Hi,
My new HTC One's vibrate isn't very strong, so the vendor is sending me a new one. I'm rooted though, so thought I'd better start looking at ways to "undo" the root. When looking at options on the HTC One Toolkit, I "somehow" did something to my phone. All I "Thought" I was doing was getting the version information off it, so I could find the correct RUU, but when trying to reboot after that, it just kept going back to the bootloader with some error like "re-locked" and "security warning".
After extensive searches, I learnt I could flash the unlock.bin file again to unlock it. Done...but then it just sat at the "Slim" logo [ROM I was running]. I could still boot into Recovery (CWM) and tried clearing cache and dalvik - but still sat at the "Slim" logo. So I started digging in. I tried to mount the SDcard in CWM, but wouldn't mount. So flashed TWRP, but same thing there. When I try to mount anything, the only folder it will let me select is "System" - nothing else mounts and my "Storage" reads "0 bytes".
So I thought maybe I'd lost root, everything was Read Only and that's why I couldn't write to anything. So using the HTC One toolkit, flashed SuperSu. Still same thing.
I did manage to adb the slim ROM and the gapps to /sdcard, but when I tried to install, nothing would "mount" in order to install it...so all I got was errors saying install failed, and a bunch of directories that couldn't be "mounted". In summary I've done the following with Fastboot:
Flashed Unlock file
Flashed boot.img (from Slim Rom)
flashed Recovery (CWM first, but now TWRP)
Fastboot Clear cache
But after all that, when I boot into Recovery, nothing mounts and I can't get past this. Any help you could provide would be MOST welcome!
Thanks in advance.
-- Edit --
Disregard - got it finally. Using TWRP, I formatted the data directory, and it was writeable again. Not sure if it helped, but I then resubmitted everything I did in the list above, booted to Recovery, and was then able to adb the ROM and Gapps over and it installed fine. Phew.... Still need to figure out how to get it all back to stock though. That's my next task.

[Q] Brick Help vs980 LG G2

Currently irate because I already typed all this then hit enter to be told I can only register once from this ip.
Any way...
Rooted vs98027a Android 4.4.2 via Stump Root
Used AutoRec which installed TWRP 2.7.00
Backed up Stock Rom
Mount button is missing
Rebooted into Stock to transfer backup to PC and place "cm-12-20150603-NIGHTLY-vs980.zip" as well as Lp gapps.
Rebooted back into TWRP
Wiped, then Installed the CM Nightly, wiped cache and rebooted.
Stuck in LG Boot loop.
Use buttons to boot back into TWRP, open Restore and It's just a blank navigation window.
TWRP just became ****ing worthless
Tried to wipe and possibly install same CM again. Still boot looping.
Tried getting to download mode, but it reboots before installing driver.
I have not a clue as to what to do next.
I can't get it to mount.
ADB Sideload Fails.
Terminal Command lets me select a blank navigation window.
And my original file structure is in like sdcard/0/0/0/0/0/0/0/0/ etc.
Please help, or at least redeem CM and TWRP's value somehow, because this is bs.
I sort of fixed it.
Restore showed up blank, because within the many /0/0/0/0/0/0/0/0 a new TWRP folder would be made or course containing nothing.
I also learned the adb is this magnificent goddess that can do things even when your phone can't.
Throughout further reading I glimpsed upon something about "loki" files that aren't compatible with specific versions of twrp or something. So If you've also been through this and still feel brave enough to flash a custom, then make sure you get the newest version of twrp...
As for the Restore issue, assuming you have a backup saved on pc, wipe everything then adb push the whole file (TWRP/BACKUPS/BLAHBLAH/BLAUGHESDIHF) to /sdcard/.... then it should show up in restore, if it doesn't then use file manager to place it in the right TWRP directory... You can also use the file manager to move the restore folder to the "correct" twrp folder if you don't have it backed up.

Tmobile update is live!

Hit that software update.
Wow thanks for the late news
my phone is upgrading now
Don't know if anybody else had trouble connecting their m9 with their Roku 3 before the update but the miracast feature now works with my Roku 3
Anyone have any suggestions on how to force the update? Still have not gotten the notification to download the update and I get the standard "There are no updates available for your phone" message when I got into settings and check for the update manually.
nickmgray said:
Anyone have any suggestions on how to force the update? Still have not gotten the notification to download the update and I get the standard "There are no updates available for your phone" message when I got into settings and check for the update manually.
Click to expand...
Click to collapse
If you are 100% stock update using the ota from stock recovery.
Download and read here
So I ran into a small issue. I was rooted with TWRP, and i re-flashed the system image that i created when I first installed TWRP. This took, as I was prompted to reinstall SuperSu. I did not reinstall, then flashed the stock recovery back to the phone.
All good so far.
Then I went to install the OTA, and received the error message
E:unknown command [set_err_msg]
/dev/block/bootdevice/by-name/system has been remounted R/W
reflash device to reenable OTA updates
Did my reinstall of the system image not take? As far as i could tell, everything worked properly until installing the OTA.
Thanks in advance for any help.
AaronM7 said:
So I ran into a small issue. I was rooted with TWRP, and i re-flashed the system image that i created when I first installed TWRP. This took, as I was prompted to reinstall SuperSu. I did not reinstall, then flashed the stock recovery back to the phone.
All good so far.
Then I went to install the OTA, and received the error message
E:unknown command [set_err_msg]
/dev/block/bootdevice/by-name/system has been remounted R/W
reflash device to reenable OTA updates
Did my reinstall of the system image not take? As far as i could tell, everything worked properly until installing the OTA.
Thanks in advance for any help.
Click to expand...
Click to collapse
I had this same issue and finally figured it out yesterday. The reason is because in older versions of twrp, the minute the recovery is booted it mounts system as read/write. So any backup done after that was potentially flawed.
First you need to download a system and boot image from http://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022. Note that the backup was created with a beta version of twrp so you have to modify the name of system file from system.emmc.win to system_image.emmc.win. Once this is done put it in your twrp folder.
The way i rectified the issue was to first flash the latest twrp recovery v2.8.7.0. The developer added a mount system as read only option in the mount section of twrp. Once you click on the checkbox. Go to restore the system backup, This time it will show up as a system image backup. Once restored, flash stock recovery and boot into os download the system update and it should go through without any hiccups.
Let me know if you have any questions
darll said:
I had this same issue and finally figured it out yesterday. The reason is because in older versions of twrp, the minute the recovery is booted it mounts system as read/write. So any backup done after that was potentially flawed.
First you need to download a system and boot image from http://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022. Note that the backup was created with a beta version of twrp so you have to modify the name of system file from system.emmc.win to system_image.emmc.win. Once this is done put it in your twrp folder.
The way i rectified the issue was to first flash the latest twrp recovery v2.8.7.0. The developer added a mount system as read only option in the mount section of twrp. Once you click on the checkbox. Go to restore the system backup, This time it will show up as a system image backup. Once restored, flash stock recovery and boot into os download the system update and it should go through without any hiccups.
Let me know if you have any questions
Click to expand...
Click to collapse
Thanks. I kind of figured it out by following the thread about how to take the phone back to stock for OTAs, and used fastboot to flash the system.emmc.win file (wihtout modifying it.) After that, the phone wouldn't boot properly (probably because I didn't edit the filename,) so I flashed my system backup file. That made it so I could boot. I then flashed the stock recovery and it installed just fine.
Only really outlining what I did in case anyone else has the same issues- they can do what I did to get it up and running again.
kc6wke said:
If you are 100% stock update using the ota from stock recovery.
Download and read here
Click to expand...
Click to collapse
Thanks for sharing. I've tried this method on two different stock T-Mobile M9 phones, but both return an "E: Failed to map file" error message when selecting apply from phone storage.
Any suggestions?
nickmgray said:
Thanks for sharing. I've tried this method on two different stock T-Mobile M9 phones, but both return an "E: Failed to map file" error message when selecting apply from phone storage.
Any suggestions?
Click to expand...
Click to collapse
Are you placing the ota zip on internal or external sd?
It needs to be on the internal.
kc6wke said:
Are you placing the ota zip on internal or external sd?
It needs to be on the internal.
Click to expand...
Click to collapse
It's loaded to internal storage.

Categories

Resources