A13 - Android won't mount data - Android Q&A, Help & Troubleshooting

Background on what I did, in case it's relevant:
I had rooted my A13. Installed BusyBox. Then was trying to figure out how to flash CWM by first trying to figure out how to get into the stock recovery. Holding down power+volup and power+voldown didn't do anything. I think I had the USB and power both plugged in at the same time. Next thing I know, the tablet rebooted and appeared to have factory reset. But now every time it is turned off and turned back on it goes back to factory default.
Real problem:
Turns out the OS is not mounting data which is why it appears like its factory reset.
What I have done:
Installed CWM. The only way I can get to CWM is to choose factory reset from the OS and when it reboots, it goes into CWM. There's no other way for me to get into recovery, so at this point, I am hesitant to try and flash random ROMs. From CWM I can mount data and see that it should go to /dev/block/nande. With the OS booted back up, I can manually mount data and see all the files in ADB shell, But it doesn't affect the OS since it has already booted up. And if I reboot, it won't be mounted again.
So how do I make Android mount data on bootup? Or what to check to see why its not mounting data anymore? vold.fstab appears to only list SDCARD mounts.

Bump!
Sent from my Nexus 4 using Tapatalk 2

Related

[Fixed] Long post, short question on CWM/TWRP

I'll put the question first for those not wanting to read the details.
I cannot get into CWM (internal) on my 16GB nook tablet. I can boot to CWM (external), but nothing works. When I try to activate ANY menu option, it takes me to a blank screen with the CWM hat logo in the background. Pressing power returns me to the main menu. Not even "reboot device" works. Can someone help? (I want to do a backup before i flash a JB Rom (internal), and to flash a JB Rom)
Now the long part:
I purchased and rooted my NT in December 2011 (about the 21st) using the snowball root (incase you are not familiar, as I don't see any post about it now, it was a modified zerg root borrowed from Albert's root method that with one menu option allowed rooting, recovery, and removal of certain nook apps and the addition of your choice of three launchers). I used it successfully on three nooks within a month or so, but this is the only one I did the complete nook removal option to.
Root works fine, but debug does not. When I run the NT hidden settings app to turn on debug mode, the developer options are listed twice (one compete set followed by another), this did not happen until after rooting, before they were only listed once. The bottom set was correctly checked to allow debug mode, and its how I rooted; however titanium backup says debug is not enabled every time I load it. (No complaints from RTB Pro) So I go into the developer settings and found two sets, the top one not checked... When I check it I get the pop-up warning, if I uncheck the bottom one, then debug does not work, if I check the bottom one I don't get the pop-up warning. With both checked, adb works, otherwise it does not. It had been this was since December 2011, and has not really prevented me from doing anything, although as the pop-up warns somethings may not work (converting apps to/from system, merging system app updates, restoring system app backups) and cause titanium to hang, but after a manual force close of titanium, most of the time the change was successfully completed.
Now, moving on one day I was being up my phone and thought "I can't remember the last time I did a nandroid of my nook" so I used RTB to reboot into recovery, the nook booted right back up into android, no errors, no different screen than a normal boot (with the nook --> hack logo, which incidentally takes about 12 minutes to boot every time, not sure if that is normal). So I tried an adb reboot recovery, but adb said no devices were attached. I went back into NT hidden settings and due enough debug was unchecked on the top, but still checked on the bottom (I've learned it lose it every reboot), do I rechecked it, got the pop-up, and went on my way. Adb reboot recovery also restarted my nook back into the OS, not into CWM.
I started to think that I may never have installed CWM, so I checked the root package I downloaded and viewed the script, first thing it does its copy the recovery image to the device, even before rooting, then installs it right after rebooting, post root hack. I thought maybe the posh was bad flash, so I searched XDA, downloaded a newer CWM, and manually adb pushed it to the phone and dd it per the instructions in the XDA thread. Reboot recovery, still nothing.
Please note I CAN get the factory reset screen to show up, but really don't want to try it without a backup, as I've been using my nook like this for 12 months and only have a titanium backup of the apps.
So I made a CWM SD from the NT thread here on XDA and booted to it :-/ intending on flashing 6.0.12 CWM to the internal emmc, the recovery on the SD was 5 something and none of the menu options worked, as mentioned above pressing power while any are selected gives a new screen with the background image, but no options. Pressing power again takes me to the main screen (same thing when selecting reboot device).
So I found a newer CWM SD package on XDA and swapped them out, this time a newer version 5.5.x, no change in how it works, so downloaded 6.0.12 and renamed the recovery image file and booted the SD. Small change this time (beyond the new version number and the option to power off, which also does nothing), when pressing the power button to select a menu option, the screen refreshes, but continues to display the same menu choices for all options in the menu.
I have also tried pushing each of these recovery images to the device and using adb to dd them to the recovery partition. Three nook will only boot the SD clockwork image.
Yes I made sure to select internal images for dd to the nook and external images for the SD.
So last night I installed nook tab recovery flasher, it said it successfully installed, before I clicked yes to allow it root access... the pressed the reboot recovery button, no good. So I downloaded and installed goo manager from the market and had it flash TWRP, same thing, reboot recovery ignores it.
Now to repeat my question, anyone have any clue how I can get recovery working spp I can make a nandroid and flash a JB Rom? (I know I can make a backup using adb, and Iam pulling one now, but I am wanting a recovery (that works) on my nook.)
Also, I am willing to try an adb push install of the Rom, I think I can make it work (although Ihave never tried it, on any device, I might be able to do it without further help), but I do not see how a new Rom will make any difference on my recovery situation and if I screw up, it would be comforting to know I had a working recovery at least.
Sent from my VS920 4G using Tapatalk 2
For selecting an option in recovery is N button not power one
Sent from my Xperia S using my fingers to swype.
Your question belongs in Q&A with all other questions and not in development. Only work being shared belongs there.
Thanks
AvRS
Caught that, and was able to flash CWM 6.1.15 (emmc) from the SD; but still cannot get to it.
Power+ nook= regular boot
Power+ vol up+N= regular boot
Power+ vol up= regular boot
Power+ vol down+N= regular boot
Rom toolbox pro reboot recovery = regular boot
Adb reboot recovery= regular boot
However, using goo manager to reboot recovery works, sort of...
I get the cyanoboot screen, hold N, use the menu to get to emmc internal recovery and I get CWM.
Now the problem starts about 3-7 minutes later (have not tried timing it, but it seems to be the exact same length of time each time), the nook reboots, don't matter what I am doing, using it, creating a nandroid, adb push or adb pull out apparently flashing cm10...
I decided to try a flash of cm 10 from a 11-28 build with multi touch firmware for 10 points. All was good, but I had to step away for about 2 minutes... I sneaked a peek and all was well, then when I got back my nook was on the "read forever" logo and has now been that way for 20 minutes. I checked the updater script in the Rom and it does NOT have a reboot command at the end.
I'll give it another 20 before ring to get back to CWM with out goo manager...
Sent from my VS920 4G using Tapatalk 2
Update
So, no change. Hiding the power button shut it off, I also tried plugging the usb cable in to activate boot, this causes a regular boot, which at this tinge never gets to "nook" but stays on "n" "read forever" which makes me laugh as it is currently the only thing I will "read forever" until I fix it.
Next up is to try to flash from an SD.
Update to my update
Booted from the SD, wiped everything three times, flashed the Rom, rebooted and ended up with TWRP, multi-touch and JB. Reinstalling apps through the market now, hoping previous issues are gone.

[Q] Phone won't boot. Mount SD?

Edit: Fixed the problem. Used OTG cable and flash drive to move the recovery.
Phone was working fine, but suddenly after a reboot it goes past the HTC logo, then remains black. I have a backup on my computer, but can't go into recovery and restore because I get an error when I try to mount. Factory reset doesn't work.

Nook won't boot up

The story began when I decided to install CM10 on my nook tablet using old recovery that goes for CM7 and eventually broke my partition table and lost my ID(./adb devices shows 0000000000000000). Since my nook refused to boot futher than CWM loading screen (box) i decided to recreate my partitions through ADB using this method and then reflash nook with AdamOutler's Ubuntu recovery (he provided his own mmcblk0p5).
So, I succesfully recreate partition table (everything was in order, I checked a few times) and reflash it with Ubuntu recovery. Interesting part starts here. Now i get "bla-bla-bla please restart your device" and picture with exclamation mark. A couple of reboots gave nothing and brought me to the same screen. Reflash with BN factory recovery as well as factory reset did not work. At that point I decided to inspect partitions again. Everything was ok, formating, size, etc. But my ID still was 0000000000000000. This brought me to the conclusion that something is wrong with mmcblk0p5 and i need to flash partitions with dd again using this files (method). So, all went well without errors, at the end i killed adb server, dismount SD and pressed "reboot device" in CWM menu. And... From that time my nook is completely dead.
It didn't respond to any key. I charge it all night. I tried to hold home+power simultaneously. No response. Connecting to a computer or power outlet is also nothing.
Be kind, I'd like to hear your advice. Sorry for my runglish.
WidePants said:
The story began when I decided to install CM10 on my nook tablet using old recovery that goes for CM7 and eventually broke my partition table and lost my ID(./adb devices shows 0000000000000000). Since my nook refused to boot futher than CWM loading screen (box) i decided to recreate my partitions through ADB using this method and then reflash nook with AdamOutler's Ubuntu recovery (he provided his own mmcblk0p5).
So, I succesfully recreate partition table (everything was in order, I checked a few times) and reflash it with Ubuntu recovery. Interesting part starts here. Now i get "bla-bla-bla please restart your device" and picture with exclamation mark. A couple of reboots gave nothing and brought me to the same screen. Reflash with BN factory recovery as well as factory reset did not work. At that point I decided to inspect partitions again. Everything was ok, formating, size, etc. But my ID still was 0000000000000000. This brought me to the conclusion that something is wrong with mmcblk0p5 and i need to flash partitions with dd again using this files (method). So, all went well without errors, at the end i killed adb server, dismount SD and pressed "reboot device" in CWM menu. And... From that time my nook is completely dead.
It didn't respond to any key. I charge it all night. I tried to hold home+power simultaneously. No response. Connecting to a computer or power outlet is also nothing.
Be kind, I'd like to hear your advice. Sorry for my runglish.
Click to expand...
Click to collapse
I'm having the same problem. I downgraded from 1.4.3 to 1.4.0. I was able to boot it once and then shut it back down so I could root it. Now it won't start up at all and I have tried everything that I can find to boot it to no avail.
The NT can sometimes get stuck in limbo while booting up, especially with SD-based boot. To get out of it, hold down the power button for 20-30 sec to turn it off then power it on again. Also remove any "bootable" SD card from the card slot; if it boots then the card was not bootable and its non-bootability was the problem.
It's also possible that the NT battery is completely drained (battery readings on some CM builds can be quite off, sometimes as much as 20 points) in which case you'd need to use the BN wall-charger and charge it for 8-12 hours.

[Q] CWM recovery boot loop

I attempted to root a denver tac-70061 tablet in order to be able to switch the mounting of the internal and the external sdcards. I have only rooted once before; a denver tac-70031 tablet which was extremely easy to root by simply installing and running the superuser app. Unfortunately, it seemed that it was not as simple on the 70061.
As I am a novice, I followed the instructions blindly and read them through a number of times before attempting.
I followed a set of instructions which described downloading a zip file which contained adb for windows and some img and zip files to transfer to the sdcard.
I am using ubuntu, so I assumed that the adb which was installed along with android sdk would suffice.
I copied the required files to the root of the tablet's internal sd card and installed recovery via adb.
I unplugged the tablet and rebooted in recovery holding down volume-up while powering on.
When in recovery, the instructions told me to install superuser 3.1.3.zip from the sdcard but this file was not present.
When selecting 'reboot', the tablet kept rebooting to recovery and now seems to be stuck in a loop.
I hope that someone can help.
Factory Default reset?
How do you even get into the recovery menu. W/o I try, I get to the screen with the stupid robot laying down, and a ! inside a triangle showing. What buttons do you press to open recovery menu? On that page, no lists of stuff appear, and I want to reset the android tablet I used, also a TAC-70061, b/c it just keeps loading on the 3rd boot screen, and never gets passed it. Lame Denver product is not worth 2 cents. Apart from how annoyed I am, can you explain to me how to get into the factory reset and reset it/fix it?

tablet Multilaser M9 Quad Core ML02, stuck in recovery mode

here's the story
so wanted to boot this considerably old tablet because nostalgia
then i saw myself on the recovery screen, can't move the highlight with volume buttons, and got a bunch of mount errors on /data and /cache
tried reflashing stock rom, nope, same mount errors.
the only way i found to control the recovery is via a keyboard on an usb otg. a wipe data and wipe cache resolves the mount issues.
also, allwinner chipset. yeah.
the rom is a stock from china (exdroid4.4.2_r2-a33-v2.0)
root attempts were done on the device, which consequently factory resets whenever i shut it down. i don't know how that works.
here's what works:
adb sideload (with integrity checks)
download mode
access to internal storage is denied
yes i'm brazillian, stop asking

Categories

Resources