mildly freaking out here, need advice.
D800 - AT&T
CWM 6.0.4.4
Hellfire ROM
phone has been acting up recently when bluetooth is connected. it's not totally locked up, just extremely super slow to the point that it appears locked up and if i can't wait for it, i just reboot (hold down power button until restart)
This happened just a little while ago. When it came back up, I opened terminal and input
Code:
su reboot recovery
When in CWM, I went to "wipe cache partition"
I let it sit on that for over 5 minutes, and the animation was frozen, so I hard rebooted again.
When the OS came back up, ES File explorer reported "unable to find /sdcard"
yikes.
I rebooted into recovery again and went to "format /data and /data/media (/sdcard)"
I let it sit on that screen for over five minutes and no progress.
Hard reboot again, reboot to CWM, choose "factory reset"
this took about ten minutes, and said "complete"
I rebooted and it sat on boot animation logo for over ten minutes.
reboot into recovery again, still no /sdcard found.
at this point, i'm guessing the data on the sdcard is totally lost, but i just want the OS to load.
What's the best way to get all the partitions back to normal, including /sdcard ?
I understand this will be wiping the phone.
adb, flash new image or what?
Related
So... I have the MT4G, and for some reason continuously stuck on boot loop("MY" loading screen after rebooting).
Here's what I've done.
-VISIONary rooting.
-Downloaded Terminal Emulator on my phone.
-Downloaded ROM manager on my phone.
-Downloaded CM7 nightlies(7.0.0), and GAPPS 2.3 onto my computer.
-Extracted files.
-Plugged my phone in, opened the "Local Disk", opened my phone files and dropped them in there.
-Unplugged my phone, typed "su," and all that good stuff into T.E.
-Opened Recovery mode, and wiped all files.
-Installed CM7.
It SAYS installation complete, but when I reboot my phone, it doesn't get past the "MY" loading screen. This should only take about 5 minutes, as I've read. Boot loop. How do I get past this?
---- Or does anybody know a different method I could use for CM7? I have Windows XP, if that makes a difference.
Also- What's the best/strongest battery for the MT4G? I'm on my phone ALL day, VERY heavy use. Mine doesn't last more than 4 hours.
Boot into recovery by completely turning the phone off. hold power and volume down it. from manu select recovery and boot the phone into recovery. press wipe factory reset and wipe cache. than select install zip from sd card. navigate with your trackpad your your sd card where the CM.zip is located and install it. make sure you are rooted. after installation u should be all good your phone should boot up.
I will try to give a decent amount of detail.
My G-tablet apparently ran out of battery, without me knowing. I tried to boot it up and it booted mostly in to android (enough for me to see battery at 0%) and then died.
I let it charge but next time I booted, though android loaded, none of my apps worked. I was also unable to boot in to recovery by holding the volume down button. As a last desperate attempt I went to Privacy - Wipe Data, which prompted the device to shut down.
When it started back up, I receive the message "Booting recovery kernel image", note WITHOUT holding the button (and without the recovery button held text).
From recovery I do a wipe of data partition and try to boot again. Same message, straight to recovery.
I say ok, I will flash the ROM again (vegantab), so I flash the ROM and reboot. Boot straight to recovery again.
One last try, I go to restore and try to restore a image from a few months ago. Restores successfully BUT, straight to recovery again.
No matter how I try to reboot, on the screen with the birds I get "booting recovery kernel image". It's like it isn't even TRYING to boot off the boot partition, and instead decides to load the recovery kernel no matter what I do.
So basically, I am now stuck in recovery and no amount of flashing / formatting can convince the thing to attempt a normal boot. Ideas?
edit: Fed up and in frustration I decided to format all partitions from recovery, including system and boot. After formatting the boot partition I now get the "Magic Value Mismatch" error message. Googling for solutions has returned around 95 different guides to fixing a gtablet, all with various completely different directions and outdated dead links to files. So if anyone has links to a MODERN guide to recovering through nvflash with files that actually exist, let me know.
Hey go to the gtablet for dummies website and download the nvflash 1.2 branch with clockworkmod. You do know how to nvflash right? Just press down your gtablet power button with volume - at the same time. That will put your gtablet in nvflash mode that is a black screen.
The nvflash you downloaded will have a folder with several files, if you are a windows user just put your tablet in nvflash mode and then Run the batch file located in the nvflash folder. Then wait for the process to finish and if the gtab doesnt reboots after everything is finished just reboot it by yourself
Remember you have to install windows drivers if your gtab is not being recognized.
Sent from my MB865 using xda app-developers app
Hi! I had Android 3.1 on my TF101 and it was already rooted, I updated CWM to 6.0 and in recovery I can't mount storage, and I can't do anything...when trying to reboot it stucks at the boot logo (I think i formatted, wiped system but not sure). And when I trying to do a Factory reset, it freezes at: Formatting /data... So? Can somebody help me please? Oh, and when I trying to reboot with power, and volume down, it says something like this: Press Vol Up to enter recovery in 5 secs. If I dont press it, it brings me to a menu, like this: Press vol up to execute, ot vol down to skip wipe. I've tried both options but I think it freezes...or I didn't wait as much as it needs (10 mins about)??
Mazseex said:
Hi! I had Android 3.1 on my TF101 and it was already rooted, I updated CWM to 6.0 and in recovery I can't mount storage, and I can't do anything...when trying to reboot it stucks at the boot logo (I think i formatted, wiped system but not sure). And when I trying to do a Factory reset, it freezes at: Formatting /data... So? Can somebody help me please? Oh, and when I trying to reboot with power, and volume down, it says something like this: Press Vol Up to enter recovery in 5 secs. If I dont press it, it brings me to a menu, like this: Press vol up to execute, ot vol down to skip wipe. I've tried both options but I think it freezes...or I didn't wait as much as it needs (10 mins about)??
Click to expand...
Click to collapse
Hiya have you tried this yet?
http://forum.xda-developers.com/showthread.php?t=1688012
this should get you back to a fresh start but whay where you trying to do?
I'm guessing you used ROM Manager to install CWM.
Use EasyFlasher as noted by all43 to install a working recovery - I highly recommend TWRP. Then put your ROM on a microSD formatted for FAT32z
Boot to recovery (VOL DOWN and POWER for 12-15 sec, then tap VOL UP to enter RCK)
Then wipe cache, Davlik, format system and factory reset.
Install ROM and if applicable GAPPS and Kernel.
Reboot
Profit
Thanks, Easy Flasher solved my problem
Hi there, having just the old casual phone crisis. I was running cyanogenmod 12.1 for awhile and decided to finally upgrade to a nougat 7.1 build.
I tried using this one https://forum.xda-developers.com/google-nexus-5/development/rom-dark-rom-t3492150 using adb sideload as I had tried a earlier one and the gapps messed up so I wasn't able to put twrp back on the phone. The rom said it had installed successfully but I wasn't able to sideload gapps, I kept getting an error status 255. I went ahead and just tried to load the rom without gapps and see if I could install it slowly through APKs. I managed to get past the initial android load and the services started up, and it got in an endless crash loop because the phone service wouldn't start. So I went to try and flash another rom and was going to delete the cache. When I went to delete the cache the phone hung for about an hour so I tried to just reset it into recovery mode again.
Now when I hold the power button and volume down key to into fastboot mode I can. I have access to the initial screen with the four options, but when I try to start recovery mode or start the phone my screen goes black, and it'll flash the dead android symbol with the error saying unable to mount cache, it only flashes it for like half a second then goes black and repeats every 10-15 seconds.
I tried holding power down, doing volume up, and letting go to do a hard factory reset but it does nothing. I also can't seem to access the adb sideloading anymore, I'm very scared that it's hard bricked, is there anything I can do at all to fix this.
Flash a new version of the recovery via fastboot. Then do a full wipe. After that install the ROM only! Reboot recovery (not system but recovery) then reflash the ROM (no wipe) and add everything else. Hope this helps you out.
The phone may not boot the ROM without wiping data if installing a 7.1 ROM over a 5.1.1 ROM.
I was doing some testing of installing and backing up various roms using TWRP. After I'd finished all my tests I got ready to return to OOS.
For whatever reason, I now find myself with the phone showing the OOS boot animation sequence but never completing the boot process.
The phone is unresponsive to the power button (even holding it down for more than one hour) - I can't turn the phone off or reboot into some other mode . It does not connect to the PC at all, even in EDL mode with the vol up+vol dn buttons pressed.
So I'm hoping that it will eventually shut down when the battery runs out and then I may be able to boot up into bootloader or recovery again.
In the mean time, does anybody have any suggestions for getting the phone out of its endless rebooting state?
Well, all is now OK. I let the phone run until the battery was drained.
Then I plugged the battery in and rebooted to bootloader, wiped /data using fastboot -w.
At that point I could have used any number of ways to get my phone back, but I chose to do it as follows:
Next I booted into TWRP, took a backup of EFS to find out where it was expecting to find backups, which was /data/media//TWRP/BACKUPS/<serial.id> and then I pushed a system backup (boot, dtbo, and super) there, restored it and rebooted the system.
Once the system had rebooted (and /data is now properly formatted), I returned to TWRP, pushed my other files and backups, restored my data backup and rebooted back to my working system.