First let me say that I installed CWM once already so I am fairly confident that I understand the basic steps. However, after I had initially installed CWM I tried to install a new ROM, but my tablet just hung on the "Viewsonic Birds" screen for like 45 mins. So, I shut down and booted to CWM but now my tablet is empty. I mean literally empty because I wiped everything in order to install the new ROM and somehow I messed that up big time because even that .zip file is no longer there. After some searching through the forums, I found a stock image of TnT 3588 and got it loaded, but in doing so lost CWM. So, I reinstalled CWM and saw it load (saw the cardboard box etc.), rebooted holding down Vol + key and saw the 'recovery key detected'. Then it goes to a screen with a progress bar and then it just boots normally....
Any help would be appreciated. Thanks!
I'm having the same issue after a nvflash that didn't take. Can't get into recovery.
I've had a few issues with that also. I try the SD card installer, drop it on the card named update.zip, reboot, it looks like it installs, but after rebooting it won't let me boot to CWM. So, I try the internal installer, drop it on the SD card named udpate.zip, it installs, I reboot, and go right into CWM. So either when I connect my tablet it somehow doesn't mount the SD card but mounts one of the internal partitions, or the SD and Internal installers were mixed up...
Related
Long story short I find myself in a boot loop and am a little hesitant to try what I believe to be the 'next step' to recovery in case I am mistaken and totally fubar my new toy. (this is my first android device and I'd prefer not to brick it in the first 24hrs!)
As to how I got myself into this situation here's a play by play.
1) Researched internet for best value tablet with awesome dev community. Found my gtablet and xda! (buy, buy, buy!)
2) I spend the week leading up to taking delivery of my new tablet reading everything I can get my hands on.
3) Unpacked new tablet and played with stock rom briefly before saying farwell.
4) Installed clockworkmod .08 and then TNT Lite 4.4 and everything worked wonderfully
(youtube.com/watch?v=mY_FvJnWNEw&feature=related) used this method
5) when I turned my gtab on for round 2 I find myself in a boot loop, I figured there's an issue with something I changed so since clockwork seems to be working brilliantly and the update.zip file in root is the same I wipe data/factory reset and wipe cache partition and then rerun the update. This still leaves me in a boot loop...
6) In further reading the recommended fix seems to be repartition sdcard and then reinstall rom with clockworkmod off of sdcard2. I put the update.zip file with \Recovery\command (edited to point to sdcard2) onto the microsd popped the micro sd into the tablet and restarted... the tablet did not read the microsd when i started up clockworkmod. And so I am left with questions at this point and a semi-bricked device.
am I correct in trying to repartition the sdcard as my next step?
does the mircosd need to be of a certain format?
have I done something ridiculously obviously wrong??
Thanks in advance for your any help or guidance you can provide...
I'm experiencing the same thing man. However, i have another g-tablet that i haven[t cracked open yet and i'm wondering if i can just partition and copy/paste the folders from the g-tablet that hasn't been opened to get the device back to stock.
Hello!
I have just recently (last night) successfully recovered from your *exact* same problem. Short answer...Yes, Install CWM on your micro card, partition the sd card (2048 and 0). I have my microsd card formatted to FAT32.
Here is my thread:
http://forum.xda-developers.com/showthread.php?t=1028118
I specifically used "butchconner"'s first post although all of the responses were friendly and helpful!
Best of luck!
Pat
Wait a minute everyone!!!! (Talking about gilpin)
He said when he tried to boot the microSD card, he couldn't find it in CWM.
If CWM is up, that's the main thing he needs??!!!
If you can get into CWM, go to the Advanced Menu and run the Partition, Fix Permissions and Wipe Dalvik Cache options. Then go to the Main Menu and run
the Wipe Cache and Wipe/Reset Factory Settings.
Then re-boot and see if your tablet is okay.
If it's not (and CWM is still working), you can put the appropriate ROM update.zip
in /sdcard and then select and load it through CWM.
Hope this helps.
Rev
geedup,
If you are boot looping also, you need to re-partition and the nvflash back to
stock.
The following thread pretty well covers nvflashing:
http://forum.xda-developers.com/showthread.php?t=861950
After you nvflash, check to see if you still are getting boot loops.
If so, you need to load CWM and do the same thing as gilpin. When
you finish the CWM routine either it will be working -- or you can
nvflash again and it should be good to go.
Let me know......
Rev
working again...
Thanks for the fast replies all! I repartitioned my sdcard (2048, 0) reset permissions, cleared data and then rebooted. This seems to have fixed my problem as I booted cleanly and everything is working again!
Okay, this is quite a long story, so I apologise in advance.
I decided to update my Galaxy S2 today to a newer ROM (SuperNexus 2) with the latest version of Android. I was coming from a CM9 build. I went through the usual process of backing up data and performing a full NANDROID backup via CWM Recovery, booted the phone again and transferred the backups to my PC via USB. These files transferred fine.
I then downloaded the zip files for the new ROM and proceeded to copy them to the internal storage of my phone. The copy dialog in Windows said that it was "discovering items" and stayed like this until I turned off USB transfer mode on the phone and removed it (ie. the files failed to copy) This happened a number of times and I didn't get anywhere. I have plenty of space free on the SD card, but just to make sure I started the phone in CWM again and formatted the SD card, and since I was going to do it anyway, the data and cache partitions too. When I booted the phone again, the files still wouldn't copy. I managed to copy a text file to the phone which was about 32kb but anything larger just seemed to fail.
I then went back into CWM and decided to partition the SD card, as I thought that it may have been corrupted somehow and needed to rebuild the filesystem. This however, caused even more problems as trying to format the SD card (In CWM) now just reported "Error, can not mount E:/sdcard".
Feeling fairly frustrated, I decided to download the Stock ICS ROM for the Galaxy S2 and install it via Odin, thinking that the problem was probably with CWM. The install went fine, but upon reboot the phone just stayed on the boot animation, no matter how long I left it. To make sure the install went smoothly I decided to try and reinstall the Stock ROM via Odin again, but now Odin didnt seem to get past the "Initializing.." stage.
So all in all, I now have a phone which wont boot into Android, cant copy anything to internal storage, and Odin wont seem to connect to.
I am convinced this is a software issue and therefore fixable. But maybe the internal storage was not working correctly in the first place. I have installed many ROMs before and never had such issues.
Anyone know anything about this or how I could potentially fix it? Thanks so much in advance!
Benji1992 said:
Okay, this is quite a long story, so I apologise in advance.
I decided to update my Galaxy S2 today to a newer ROM (SuperNexus 2) with the latest version of Android. I was coming from a CM9 build. I went through the usual process of backing up data and performing a full NANDROID backup via CWM Recovery, booted the phone again and transferred the backups to my PC via USB. These files transferred fine.
I then downloaded the zip files for the new ROM and proceeded to copy them to the internal storage of my phone. The copy dialog in Windows said that it was "discovering items" and stayed like this until I turned off USB transfer mode on the phone and removed it (ie. the files failed to copy) This happened a number of times and I didn't get anywhere. I have plenty of space free on the SD card, but just to make sure I started the phone in CWM again and formatted the SD card, and since I was going to do it anyway, the data and cache partitions too. When I booted the phone again, the files still wouldn't copy. I managed to copy a text file to the phone which was about 32kb but anything larger just seemed to fail.
I then went back into CWM and decided to partition the SD card, as I thought that it may have been corrupted somehow and needed to rebuild the filesystem. This however, caused even more problems as trying to format the SD card (In CWM) now just reported "Error, can not mount E:/sdcard".
Feeling fairly frustrated, I decided to download the Stock ICS ROM for the Galaxy S2 and install it via Odin, thinking that the problem was probably with CWM. The install went fine, but upon reboot the phone just stayed on the boot animation, no matter how long I left it. To make sure the install went smoothly I decided to try and reinstall the Stock ROM via Odin again, but now Odin didnt seem to get past the "Initializing.." stage.
So all in all, I now have a phone which wont boot into Android, cant copy anything to internal storage, and Odin wont seem to connect to.
I am convinced this is a software issue and therefore fixable. But maybe the internal storage was not working correctly in the first place. I have installed many ROMs before and never had such issues.
Anyone know anything about this or how I could potentially fix it? Thanks so much in advance!
Click to expand...
Click to collapse
I9100?
Can get to DL mode?
Can get to recovery?
Get an older Odin version and flash siyah just to see if it can be flashed again.
If you can get to recovery, Nuke Script is the way to go.
It sounds to me that maybe your memory is corrupt...
Not just yet, smells like soft brick.
Sent from the little guy
First off, I am no expert so please be gentle! I previously rooted my old Samsung Galaxy S i9000 and installed ICS, which went OK, but the phone became quite slow and unstable. I was advised to install RemICS and downloaded all the zip files from this forum, and put them on the external SD card. I followed the developer's instructions to the letter, as well as reading everything I could find on the subject. The reset and data wiping went fine, but the installation of the ROM didn't. It halted with an error message -`ROM incompatible, trying to use an invalid partition'. I repeat that this is supposed to be the specific ROM for the i9000. The phone now won't boot into recovery. It stops with an orange Android logo and the text `Powered by Mackay Kernel'. It won't boot into download mode either. The Mackay screen stays there however long I leave it. I really need help from the ROM developer but I can't post to that forum. How can I either boot into recovery or into download mode? Is this ROM reliable? What could I have done wrong?
More info:
Presumably everyone is on holiday! But just in case anyone is reading, there is further news. The reason I could not start recovery mode was that the button sequence was different from what I had been told. It now boots reliably into Mackay (which of course is TWRP). I have found that the phone is unable to mount the partitions DATA and SYSTEM - they seem to be corrupted. Hence it has not wiped DATA, although TWRP wrongly reports success. I have tried updating the partitions to ext3 or ext4 but this fails every time. I could format the thing from Windows but that will wipe everything including recovery of course. I need a tool to repair these partitions, but have not found anything so far. This may well have been the reason the phone was getting creaky in the first place.
I have copied a new ROM to the external SD card, using a card reader, and inserted this into the phone. Strangely the TWRP file manager reports that EXTERNAL SD is a sub-folder of SD CARD, and that is empty. The file manager does not show the real external SD card. But the real external SD shows up on the Windows USB connection. What is going on?
When I try to mount the partitions, DATA and SYSTEM can't be checked - the other partitions (Cache, sdcard, and emmc are all checked).
kingGrn Copeland
Well for the benefit of anyone else with the same problem, I have managed to re-flash the ROM back to stock. It just took 3 days of intensive web browsing until I understood how to do it, and found software that worked - a lot of stuff out there has errors.
To summarise, the problem was:
1. Data and System partitions became damaged, so phone became unstable.
2. Attempt to upgrade ROM failed because of damaged partitions.
3. Could not boot phone into recovery or download because button combination was different from what I was told.
The solution was:
4. Boot into download mode using correct button combination.
5. Re-flash back to stock ROM and re-partition using Odin.
Yes, someone did tell me that, and I would have done that straight away if I could have gotten into download mode. We live and learn
The solution was:
4. Boot into download mode using correct button combination.
5. Re-flash back to stock ROM and re-partition using Odin.
Click to expand...
Click to collapse
Thanks this wa useful for me too.
I don't normally do this I just lurk around for my questions but this time I really give up. I have done plenty of work with 16 gb stuff, but never 8 GB nook, trying to install CM 10.2 on a friend's 8GB Tablet, the issue is I cannot seem to find an img for clockworkmod I can just burn to an SD card, lavero.burgos guide requires CWM to already be installed into the internal recovery, but what if I take a clean nook out of the box, are there no CWM images I can burn straight to the SD version 6.x.x and after?
The other method seems to be the one where you create the partitions manually. Which is fine and all, and my device is obviously doing something, but it locks up on the cattonbox and doesn't continue on to CWM. Things I have tried:
1. putting in MLO first after freshly creating 0x0c partition (yes its active) and then the other files for custom SD-recovery
2. replacing the recovery in lavero burgos zip with the cwm_6012.img file, renaming it recovery.img
3. also tried renaming the file instead to boot.img that some guy recommended
4. have tried another sd, rinse, repeat
All the "SD" burnable images are either invalid, or have no partition information. The custom SD method has some sort of issue. I do plug in the cable. The problem isn't getting it to recognize the SD card as a bootable media, the problem is getting to go into CWM, I'm all out of wit, it's been two days man, basically:
HELP?
EDIT: Just tried cwm_6033.img; no dice. These images are supposed to be 8GB Friendly I believe. I don't understand what gives
EDIT 2: Great. I wasted some freaking space on the forum. Sorry guys. Use cwm_6033, rename boot.img, and hold "N" when the trash box comes up. Yay
Hi guys,
I can't work out why but when I go to wipe all settings then install custom rom from zip file in cmw recovery, it completes normally but after the reboot it just stays on the android bot. I went back into recovery and managed the phone through usb to my PC & saw that in the phone storage there was nothing where there is obviously supposed to be boot files. I have installed this custom rom before & it has been no problem. I also have tried a few other roms (all that i've tried before & they all work) and the same thing happens. I have found one rom that worked strangley and when I manged the phone on my PC i saw that it has placed the boot files on the sd card (not the phone storage).
how can i fix this.
i am very new to rooting so please no complicated talk
can someone not help? this is a big issue.
ill try and explain the problem in more detail below...
i have been messing with my phone lately using CMW TOUCH to wipe my data then install rom from zip. everything was going great until now.
i want to install a rom (that i have installed before.so i know its compatible with my phone), i go through tge same procedure of wiping data then installing from zip.all goes the way it should with it telling me its installing from zip, after a while it tells me to reboot the phone. when i do all that happens is it stay on the green android bot for 1 min then reboots. i went into CMW TOUCH to connect phone to pc & found out that it installed nothing, nothing on the phone storage and on the sd card except the custom rom.
i have tried this with few other roms all with the same results.
NOW...
ive managed to find a rom that will install so it is functional all except recently after a reboot it has stopped detecting the sim，weird.
i connected the phone to my pc to find that all boot files are stored on the sd card not phone storage like it used to.
i had an idea that i will try later today and that is to move the custom rom over to the phone storage from the sd card. remove the sd card during install. maybe that will force the install to use the phone storage for the boot files
will let you know the outcome
jamos
i have just tried to install the rom with the sdcard removed from phone & the same thing happened. even though during the installation it tells me that it is formatting system then installing it installs nothing to the phone storage.