I always use philz latest recovery to format and unzip etc. I was going to format sd not sd ext and accidently clicked format/data and / data/media/(sd card) so I thought I'd proceed to just format /sd card as I normally do when cleaning my phone of junk the do a factory reset from the philz menu.
O dear when I did this the phone booted into the normal Samsung logo screen (boot animation) but sound cut short and stopped and stayed on gti9505 screen
I fixed by reflashing firmware i9505xxubmea and re-rooting and reflashing philz. Eventually the phone worked properly but wondered if anyone knew if by formatting the format/data and / data/media/(sd card) I had messed things up or it was just a mystery.
The main issue I had was it wouldn't boot into regular touch wiz it played boot ani and sound only played half of what it shoul
This probably make don sense as I am tired whilst writing this after work and for that I apologise.
Thanks for any answers lol
Related
I wanted to run a custom ROM on my A500 (first attempt at installing custom ROM), but i'm now stuck at the boot animation.
I downgraded my A500 to 3.0.1, rooted, installed clockwork mod, upgraded cwm to 1.5. So far so good.
Then i downloaded thor rom v12, copied it to the external sd card (by putting it on USB thumb drive, transfer to tablet, copy to external SD using file explorer - something tells me I'm going to need to pick up an sd card reader for my computer)
Rebooted into recovery, wiped everything (had nothing of value installed yet), and then chose to install zip file, chose thor_rom_v12.zip on external SD card, it started installing - looked like it succeeded.
Reboot tablet, and i've been staring at the boot animation (electric blue pulsating android with spinning gears on it) for about 45 minutes.
How should I proceed from here? Any idea what I did wrong?
Thanks
Hold the power button down and see if you can force it to shut down. I dont think itll turn off but its worth a try. You could also try the hard reset button (pin hole on the side of the tab) if the reset works than you should be able to boot back into recovery. If not than youll just have to wait till the battery dies.
Once you eventually get it turned off than try booting into recovery and do a full wipe and reflash the rom. I have a feeling the file you downloaded is corrupted though. if this is so than your tab probally wont boot up again.
At this point id redownload the thor or another rom and than try flashing that. You'd have to get an sd reader since you won't be able to transfer the files through your iconia again. If you can manage to get a clean download on your micro sd somehow than i'd skip straight to this step and start redownloading the rom right now.
BTW these are just the things i would try from knowing what I do about android. I haven't had any issues with my tab yet so I havent looked for solutions for this it, but ive dealt with other boot looped and soft bricked devices.
I'm sure if you do a search you'll find something.
I flashed an ICS nightly from over in the development forum and I'm left with a Nook that won't boot. Basically I flashed the nightly, booted ICS and then rebooted as I forgot to flash gapps. Upon rebooting I got the new cyanoboot bootloader however I can not boot into anything. I just get loading... If I try to boot into recovery I get loading recovery... and nothing. I tried flashing recovery onto my SD card and selecting each one of the 3 SD card boot options from the bootloader menu however none of them work. Everything hangs at loading. Any ideas one what my next step should be?
Sigh!!!
eMMC or uSD?
votinh said:
Sigh!!!
eMMC or uSD?
Click to expand...
Click to collapse
Here's the original thread. My best guess is that it's eMMC.
http://forum.xda-developers.com/showthread.php?t=1526115
Obviously the recovery image I tried was flashed to the external SD card.
Got it! Turned out to be a shotty card reader. Swapped it out with another I had lying around and it worked just fine. Thanks anyway!
EDIT: I got recovery working on the external SD card so I tried flashing a stock image. (nookcolor_1_4_1_signed-cwm-OC) I made sure to format everything first. After flashing I held in the power button, removed the sd card, placed it in my reader and formatted it. I reinserted it into the nook and booted. Everything seemed to boot fine until it got to the "nook color by barnes & noble" screen. The gradient bar goes back and forth across the lettering a bit and then I get a flash of a black screen and then back to the lettering. It keeps doing this over and over again like its in a boot loop. Any ideas?
tlenker09 said:
Got it! Turned out to be a shotty card reader. Swapped it out with another I had lying around and it worked just fine. Thanks anyway!
EDIT: I got recovery working on the external SD card so I tried flashing a stock image. (nookcolor_1_4_1_signed-cwm-OC) I made sure to format everything first. After flashing I held in the power button, removed the sd card, placed it in my reader and formatted it. I reinserted it into the nook and booted. Everything seemed to boot fine until it got to the "nook color by barnes & noble" screen. The gradient bar goes back and forth across the lettering a bit and then I get a flash of a black screen and then back to the lettering. It keeps doing this over and over again like its in a boot loop. Any ideas?
Click to expand...
Click to collapse
Since you just flashed the stock firmware with OC and CWM (as alternate) you should also have the ability to boot eMMC Recovery Mode... do that... it will clear data... and restore the data from the original rombackup.zip file... should solve your problem.
DizzyDen said:
Since you just flashed the stock firmware with OC and CWM (as alternate) you should also have the ability to boot eMMC Recovery Mode... do that... it will clear data... and restore the data from the original rombackup.zip file... should solve your problem.
Click to expand...
Click to collapse
I actually did something along these lines last night but since I flashed the stock firmware that was pre-rooted and with CWM... I booted into CWM, wiped everything, mounted usb, copied over the stock pre-rooted zip file, flashed it and then fixed permissions. Everything booted fine.
i have the same problem but im on emmc. im just stuck with loading... any solution for me?
I have an A500 that was originally purchased in Thailand. I contacted Acer Thailand and they provided me a recovery package to install. I put this on a FAT32 formatted Micro SD card and it installs, but when the tablet reboots itself it gets suck on the screen with the silver "android" logo.
I've gone also some of the advice in this thread as well: http://forum.xda-developers.com/showthread.php?t=1874345.
So far I've tried 3/4 recovery zips provided (41-124-01, 41-125-03, 41-203-01) with the same results. Rather than simply trying to load recovery ROMs at random hoping one magically fixes the problem, what I'd like to do what I would like to do is completely erase the flash on the device, and then try reloading the recovery ROM.
Is there a NON-acer recovery tool I can use to blow away everything that is on there now (and presumably, the corrupted bits?)
bassmosphere said:
I have an A500 that was originally purchased in Thailand. I contacted Acer Thailand and they provided me a recovery package to install. I put this on a FAT32 formatted Micro SD card and it installs, but when the tablet reboots itself it gets suck on the screen with the silver "android" logo.
I've gone also some of the advice in this thread as well: http://forum.xda-developers.com/showthread.php?t=1874345.
So far I've tried 3/4 recovery zips provided (41-124-01, 41-125-03, 41-203-01) with the same results. Rather than simply trying to load recovery ROMs at random hoping one magically fixes the problem, what I'd like to do what I would like to do is completely erase the flash on the device, and then try reloading the recovery ROM.
Is there a NON-acer recovery tool I can use to blow away everything that is on there now (and presumably, the corrupted bits?)
Click to expand...
Click to collapse
I ended up getting it booting up into Jellybean. First I tried restoring as mentioned above with the SD card.
This next part, I believe is the key as the device revived after this step. I put it into a bootloader restore mode by powering on with volume down and flicking the screen lock switch once the device vibrated. After this, it continued with the tablet setup mode and booted into Jellybean.
How it started: I use a NC with mirage 7.2 flashed to the emmc in my car. It runs Torque to display engine data, and is switched in and out of sleep with the ignition. Two days ago I started the car and got the low-battery "exclamation point" icon thing, so I figured the charging cable must have come loose*. I took it all out and left it charging overnight, but when I went to boot it in the morning it was stuck in a cyanoboot loop. I couldn't power the device down or enter emmc recovery. When I completely unplug the NC I can't do anything, the screen remains black no matter what I press, except it flashes white every 5 seconds or so. If I manage to plug it on, get to the cyanoboot loading screen and unplug it while holding the power button down at the right time, I can sometimes get it to power off completely.
What I have done so far: Tried various recovery SD methods, none of which worked. Wiped cache/data/system, factory reset, tried loading 7.2 again over the top of whatever is left in there, lol. Basically after it first happened I probably made a big mess of the file system in a desperate attempt for some kind of stability. I tried this recovery SD: http://forum.xda-developers.com/showthread.php?p=25354258#post25354258 ; section A10, and managed to get into CWR. I've never felt such joy in my life.
What finally worked: I repaired the 2nd partition with the help of this thread: http://forum.xda-developers.com/showthread.php?t=1759558 . I did not repair or format any other partitions though. After repairing the partition, I did a factory reset and flashed mirage 7.2 and gapps back onto the emmc. Before I rebooted, I swapped a clean SD in but it still went back into the bootloop..BUT...when I put my recovery SD back in it booted into 7.2! I set everything up and was happy to have it running again. Battery level was at 88%.
What made it stop working: I was testing to make sure the NC would enter sleep mode when disconnected from power, so I unplugged it. Everything went black, no "sleeping" screen, just a hard shut-down. I powered it back on and I'm now back in a cyanomod boot loop.
So...any ideas? If there's a way to completely wipe and reinstall everything I'm OK with that. I've never used ADB before but I'll give it a shot if someone can lead me in the right direction. Thanks in advance.
*I'm using a 2amp USB car charger with a modified data-looped cable for a/c style charging in the car. I know the supplied nook cables are prone to going bad, and this may have happened with the vibration of the car and all. Not sure.
Little update: I can sometimes get into TWRP by selecting the "normal emmc" boot from the cyanoboot screen. I don't understand how that's possible, as I flashed that on my original install of 7.2 months ago. Guess I need to figure out how to completely wipe and re-flash everything.
SPLEclipse said:
Little update: I can sometimes get into TWRP by selecting the "normal emmc" boot from the cyanoboot screen. I don't understand how that's possible, as I flashed that on my original install of 7.2 months ago. Guess I need to figure out how to completely wipe and re-flash everything.
Click to expand...
Click to collapse
To completely wipe and reflash everything, do the other two zips that you said you did not do from my partition repair thread.
Sent from my Nook HD+ running CM10 on Hybrid SD
No luck with that. Here's exactly what I did, so tell me where I might be going wrong:
1) Burned an image of the 6.1.0.2 recovery onto SD, then put the (2) recovery zips and the (1) format zip as well as the mirage 7.2 and gapp zips onto the SD.
2) Booted into cyanoboot, it took a few tries to get out of the loop and into CWM. Note that I can't power on at all unless it's plugged in. As soon as I unplug the NC it turns of except the screen will flash every 5 seconds or so. Once I got into CWM, I installed both partition repair zips, starting with the 1-4-5-6-7-8, followed by the 2. Rebooted. There were no errors at all.
3) Again it took a few tries to get out of the bootloop and into CWM. Installed the format zip and rebooted again.
4) Installed Mirage 7.2 and gapps and restarted, but went straight back into bootloop. I know that the rom requires a clean formated SD card, so before rebooting after I installed the zips I took out the SD card, formatted with SDFormatter and reinserted in into the NC.
I'm beginning to think this is something hardware related. :crying:
Sounds like there might be some bad data in emmc, I had this problem before and fixed it by formatting everything , even emmc and wiping dalvik cache. Then boot off a SD card using the latest cwm.
Sent from my NookColor using xda app-developers app
SPLEclipse said:
No luck with that. Here's exactly what I did, so tell me where I might be going wrong:
1) Burned an image of the 6.1.0.2 recovery onto SD, then put the (2) recovery zips and the (1) format zip as well as the mirage 7.2 and gapp zips onto the SD.
2) Booted into cyanoboot, it took a few tries to get out of the loop and into CWM. Note that I can't power on at all unless it's plugged in. As soon as I unplug the NC it turns of except the screen will flash every 5 seconds or so. Once I got into CWM, I installed both partition repair zips, starting with the 1-4-5-6-7-8, followed by the 2. Rebooted. There were no errors at all.
3) Again it took a few tries to get out of the bootloop and into CWM. Installed the format zip and rebooted again.
4) Installed Mirage 7.2 and gapps and restarted, but went straight back into bootloop. I know that the rom requires a clean formated SD card, so before rebooting after I installed the zips I took out the SD card, formatted with SDFormatter and reinserted in into the NC.
I'm beginning to think this is something hardware related. :crying:
Click to expand...
Click to collapse
It is possible that your partition table is messed up. The only way to find out is to boot to recovery, connect your USB cable to the PC and run ADB. It is also possible to make a CM bootable SD and use terminal emulator to check it out.
Once you get ADB shell or terminal emulator working, type the following command:
fdisk -l /dev/block/mmcblk0
It should say 965 cylinders, 4 heads, 63 sectors.
If it does not, we need to do a manual repair.
You can also abandon emmc and just run off SD.
Sent from my Nook HD+ running CM10 on Hybrid SD
Ok, so my A3000-H (16 gb) has got the boot freeze for some reason after I ran out of battery during playing some game, it never turned on or show the charging battery screen since, I used CWM to flash TWRP (I thought this may work) but all it did that I lost the recovery too, and now choosing the recovery from the fast boot menu only restarts the device.
so all I can access now is the fastboot menu! how can I recover my data on sdcard? i need them badly!
/**************************************************************************/
////// Update: problem fixed!
I used SP flash tool to flash the rom from this post, I made sure to uncheck the last image (the userdata one)
I waited, started the device,
bingo! it passed the lenovo bootlogo I've been prisoned with since 3 weeks ago!
I held out my breath -literally- for data saving part..
it started "upgrading applications" like whats happened when I clean the cache.. it's 190 applications, my number of installed applications not the stock number!
system fully booted...
I fired my ES explorer to check my sdcard...
Voila! I'm saved!
faissl said:
Ok, so my A3000-H (16 gb) has got the boot freeze for some reason after I ran out of battery during playing some game, it never turned on or show the charging battery screen since, I used CWM to flash TWRP (I thought this may work) but all it did that I lost the recovery too, and now choosing the recovery from the fast boot menu only restarts the device.
so all I can access now is the fastboot menu! how can I recover my data on sdcard? i need them badly!
Click to expand...
Click to collapse
You can try flashing CWM again, using flash tool. But I believe you have a big problem there if you want to save your data that is on the internal memory. I had this problem, too. I completely discharged the battery and when I went on to charge it, nothing happened, the screen just stayed black. I could not recover it without completely reinstalling the ROM.
MirXas said:
You can try flashing CWM again, using flash tool. But I believe you have a big problem there if you want to save your data that is on the internal memory. I had this problem, too. I completely discharged the battery and when I went on to charge it, nothing happened, the screen just stayed black. I could not recover it without completely reinstalling the ROM.
Click to expand...
Click to collapse
flashing CWM is no good in my condition, I always recieve a "fastboot partition 'recovery' not support flash)" massage on the device side, and the flash tool says the the partition and recovery are "not the same size" or something similar
will flashing certain img files from the rom (like recovery or boot or something else) can save me? I tried both boot and recovery with no luck..
I just hope the data on the internal storage are not that important.. but unfortunatly it is
..and just today Lenovo mails me about Reachit service!
I can't reach it, Lenovo!
breaking news: I've managed to bring it back online with no data loss!
details in the first post update, if this helped you too click thanks
I have the same problem but don't know what to do
when i open my tab it stops on the splash screen with the Lenovo logo and doesn't complete its booting . I found some solutions that said Hard Reset, but how to get my data before doing this step ??