I just successfully rooted my device w/Odin, then decided I wanted to start fresh. I used CWR to wipe my partitions, including the System partition. I take it that was incredibly stupid? I guess I'm so used to having a full .zip ROM package to flash with my old phones that I didn't stop to think about what I was doing.
Now I'm permanently stuck at the T-Mobile splashscreen. The progress bar fills, but the phone boots no further. Is there any existing way to restore the system partition to stock? I still have access to CWR and can still flash with Odin. I do see that there are .img dumps of the system partition; can I do anything with these? Thank you!
Have u tried to Odin back to stock?
Sent from my SGH-T989 using xda premium
Do you mean by flashing the ~10MB SGH-T989-Stock-UVKID tar file? If so, yes. The file successfully flashes in Odin, but it the phone still doesn't boot.
Is it at all possible that I need to reflash the system partition? I've downloaded a couple >300MB images of System, either as .img or .zip files. Can I do anything with these?
Then I have no idea sorry
Sent from my SGH-T989 using xda premium
sb61g2 said:
I just successfully rooted my device w/Odin, then decided I wanted to start fresh. I used CWR to wipe my partitions, including the System partition. I take it that was incredibly stupid? I guess I'm so used to having a full .zip ROM package to flash with my old phones that I didn't stop to think about what I was doing.
Now I'm permanently stuck at the T-Mobile splashscreen. The progress bar fills, but the phone boots no further. Is there any existing way to restore the system partition to stock? I still have access to CWR and can still flash with Odin. I do see that there are .img dumps of the system partition; can I do anything with these? Thank you!
Click to expand...
Click to collapse
Did you happen to make a NANDROID BACKUP prior to your formatting frenzy?
ALWAYS, ALWAYS, ALWAYS...you get the point yet? If someone else hasn't uploaded one, I'll post one when I get home in about 4 hours...
Well, thank you for trying. To reiterate my problem:
I have ClockworkMod Recovery installed and working. While in it I did the following, thinking this would cause the phone to reboot in a "factory fresh", but rooted state:
-wipe data/factory reset
-format /system
-format /emmc
-format /sdcard
-Wipe Dalvik Cache
I then rebooted, and thus cannot boot the phone. The progress bar fills on the Samsung/T-Mobile splashscreen and then just hangs. Could someone confirm for me that I caused this by formatting /system? If so, is there any way to copy the OS back over to the system partition?
Shamwow, that would be amazing. I did a Nandroid backup, then proceeded to format the microsd card on which it was stored. Chalk it up to pure, unadulterated stupidity.
Anyone willing and able to post their Nandroid backup?
Related
My phone is just rebooting to the Fresh boot animation over and over again. Here is what I've done.
I did a full wipe (3 times), cleared storage in recovery, wiped dalvik cache, pulled the battery, fastboot, wipe cache partition, wipe data/factory reset in recovery and nothing works. I'm using Clockwork Recovery v2.5.0.1 and I rooted via this method for mac:
http://forum.androidcentral.com/htc-evo-4g-roms-hacks/17766-how-full-root-evo-4g-mac.html
I'm pretty sure half the **** I did was not necessary but I had to try something. Any ideas on what to do next?
Usually clearing cache/dalvik works... And you've wiped everything else... Have you checked the MD5 of your ZIP that you're flashing from? Or tried a different ROM?
Furthermore, have you just let the phone sit for a bit? The first boot after wiping cache can take quite a while.
EDIT: Also, did you do NAND unlock/eng hboot when you rooted?
I never did a nand backup. What would happen if I nand backup while having these problems? How do I check MD5?
I'm a bit confused at what you're trying to do here...but maybe this will help.
Factory reset/data wipe does not wipe your /system/ which is where most/all of the core files are stored for any ROM.
You could trying doing a logcat from adb to maybe get a better idea on what is causing the bootloop.
Or a broader approach would be to just flash Fresh again and it will overwrite anything in /system/ and whatever files, or lack thereof, that are causing the bootloop issue will be added/overwritten.
Well doing a Nandroid backup of a broken ROM won't do you any good.
As for MD5, you should be able to open adb shell, then use the "md5sum" command to get the MD5 of the file. For example:
Code:
adb shell
md5sum /sdcard/some_rom.zip
You can then compare the MD5 it outputs with the MD5 posted by the ROM maker. If they haven't posted an MD5, you might want to re-think about using that ROM, and the competence of its creator. For example, CM6 Nightly has the MD5 posted in a text file in the same directory as all the ROM zip files for flashing. Amon RA Recovery has the MD5 posted in the OP of the thread, etc.
Philosuffer said:
I'm a bit confused at what you're trying to do here...but maybe this will help.
Factory reset/data wipe does not wipe your /system/ which is where most/all of the core files are stored for any ROM.
You could trying doing a logcat from adb to maybe get a better idea on what is causing the bootloop.
Or a broader approach would be to just flash Fresh again and it will overwrite anything in /system/ and whatever files, or lack thereof, that are causing the bootloop issue will be added/overwritten.
Click to expand...
Click to collapse
What I'm trying to do is get my phone to work again. Here's what happened:
I downloaded this Rosie Clear Taskbar zip file that I found in the Themes section and flashed it. It looked horrible and was showing distorted so I figured I'll just reset my whole phone and get rid of it. Well it didn't work and it put me in a boot loop. I have no idea how to do a logcat and I'm pretty much new at this unless you post instructions I can adb with my mac. I need my phone today because it's my daughters birthday and people are going to be calling me left and right for details on the party. My phone just keeps rebooting at the Fresh boot. I can enter recovery just fine:
Is there a command I can do in adb while in recovery to make it ''safe boot''? How do I flash Fresh again?
Is re-flashing the ROM as easy as me taking the downloaded Fresh Rom.zip, placing it on my SD and flashing from recovery? I don't want to experiment and possibly mess everything up. Thanks.
It's that easy
gqstatus0685 said:
...
Is re-flashing the ROM as easy as me taking the downloaded Fresh Rom.zip, placing it on my SD and flashing from recovery? I don't want to experiment and possibly mess everything up. Thanks.
Click to expand...
Click to collapse
Yes, it's that easy.
I'm not a big fan of how Clockwork wipes, I prefer Amon_RA, where you know you are wiping dalvik cache. Still if you are reinstalling Fresh 3.1.0.2 do a complete wipe.
Once you have your phone operating, immedaitley make a nand back up, or in Clockwork a nandriod. You can then always have a working base to go back to if something isn't playing nice.
Jim M said:
Yes, it's that easy.
I'm not a big fan of how Clockwork wipes, I prefer Amon_RA, where you know you are wiping dalvik cache. Still if you are reinstalling Fresh 3.1.0.2 do a complete wipe.
Once you have your phone operating, immedaitley make a nand back up, or in Clockwork a nandriod. You can then always have a working base to go back to if something isn't playing nice.
Click to expand...
Click to collapse
When Clockwork wipes data it deletes the entire folder, which happens to contain the cache and dalvik folders. There's absolutely nothing wrong with that.
And OP, you might want to wait for Fresh 3.2. Just came out for donators today. I'm using it right now.
Apparently in my case it isn't as easy as flashing from the zip. I downloaded the ROM from geekme and put it on my SD card. Flashed it and even though it was successful I still get boot loop. Could it be because I accidentally did a nand backup of the problem?
What else could I do. I'm using Clockwork but is there a way to flash the other recovery through ADB even though my phone won't boot.
I can't take this to Sprint as it's rooted and showing the Fresh boot screen.
I had the same problem. Turns out I had the wrong kernel flashed from a previous rom. I had constant reboots, couldnt access my sd card, and the usb quit working. I had to ship it back to Asurion. Just got my new one back.
Bottom line:
MAKE SURE YOU HAVE THE RIGHT KERNEL BEFORE YOU FLASH A NEW ROM!!
SD Card
Do you have another memory card that you could use? Try putting a copy of a rooted stock ROM on it and try to install that.
http://forum.xda-developers.com/showthread.php?t=743352
As others have mentioned clockwork does not always work well with Fresh, try Amon RA's recovery
TheBiles said:
When Clockwork wipes data it deletes the entire folder, which happens to contain the cache and dalvik folders. There's absolutely nothing wrong with that.
And OP, you might want to wait for Fresh 3.2. Just came out for donators today. I'm using it right now.
Click to expand...
Click to collapse
The dalvik cache is under /data but the android cache has it's own partition.
Here's the deal. I got a new 16GB sd card, copied everything over (including hidden files) and it worked fine for about two hours. Then the screen went black but the LED and soft buttons stayed lit. I did a Clockwork recovery (with a version that I've used successfully before) but it couldn't find SD-EXT so it would boot up to the red Droid "eye" thing (right before loading the homescreen) and then just keep showing that animation.
So I put the old card back in, tried again, and it still couldn't find the SD-EXT file so I've got a phone now which is stuck at this animation.
My question is, can I just boot into Clockwork and install Cyanogen (because I couldn't find a DINC custom recovery file anywhere) from a zip on the SD and have everything start working again? Don't want to mess it up more than it already is.
Unless you have made an SD-EXT partition, it will give that "error" in recovery. Its not actually messing anything up. I'm not sure why its bootlooping but you can try wiping data and cache then reboot or you can download a zip from www.dougpiston.com to take your phone back to stock.
Sent from my ADR6300 using XDA App
I actually discovered that in further research after I posted.
Clearing the cache was a no-go so of DP's site should I go with PB31IMG or with one of his recovery images? I'm think of going with the one with CWM 2.5 on it.
I would try either doing a complete wipe and reflash of whatever rom you choose or you can use the PB31IMG.zip to get back to stock and flash a rom from there. Make sure you're doing a complete wipe as well (wipe data/factory reset, cache, dalvik cache) and do it manually in recovery, not with rom manager.
Sent from my ADR6300 using XDA App
Hi there, thanks a lot for paying attention to this thread
I have just recently pushed in a partition table 'Bravo CM7 r2' using fastboot and adb.
What i have done so far:
I wiped the cache and wiped data/factory reset after the partition table was done. Then i restored the backup i did before i updated the partition tables.
However, after booting up normally with no problems, the second i unlocked my device, things started to force close (keyboard, android.process and other things)
Desperate, i went back to recovery and i reflashed my ROM (cm7.1), then i wiped the cache and wiped data/factory reset and the same thing happened, i unlocked my device and everything just starts to force close again (refer to previous paragraph for force closed items)
I have no idea how to get this working, it appears it is not as easy as the tutorial says.
I need your assistance, thanks a lot guys!
What exactly did you do when you "unlocked your device"?
Sent from dGB using Transparent XDA App
Hi MatDrOiD, thanks for the prompt reply.
What do you mean by "What exactly did you do when you "unlocked your device"?
Btw, i forgotten to include some information about the device im using. Sorry about that.
Phone Model: HTC Desire (GSM)
ROM: CM7.1
S-OFF
Hi, can't anyone help a noob out?
Can't no one help me? Or am i required to start a new thread?
As far as I can tell, you're doing it wrong. Wipes are to be done before, not after the flash.
fastboot flash hboot cm7r2.img
fastboot reboot-bootloader
fastboot erase cache
Boot to recovery now.
mounts&storage
format system, data, sd-ext and cache (optional as you already wiped it but do so for the piece mind) and do so manually! Not just full wipe.
Now flash your new rom. In case you flashed something else, only one thing is supposed to be flashed per session unless said otherwise in the installation instructions!
If crashes continue, download the rom again.
Sent from my HTC Desire using Tapatalk
Hi, thanks for the reply! Am i supposed to restore my backup after im done flashing my ROM?
UPDATE: I did a restore and the situation looks a lot brighter, less force crashes. The only thing that FCs now is thememanager. Is there anything else i can do? Or should i raise a white flag and restart from scratch?
Why would you flash a new ROM if you can restore your nandroid backup of the previous rom?
But make sure your the /system-partition of the ROM you backed up is smaller than the one of your new hboot.
Hi, let me get a clearer picture of what im supposed to do
1) Push in the img for the partition using fastboot
2) Wipe system, cache, data, sd-ext
3) Restore backup (no need to flash new ROM here?)
In case this helps, i flashed ceberus and gapps for my backup. Would that affect the system partition?
First step: Make nandroid backup!!!
No, there isn't any need to flash rom.
Yes, it will effect it.
Haha! Nandroid Backup has already been made. But it is useless now because i flashed in ceberus isn't it? So the only thing i can do now is to make a backup of all my apps through Titanium backup and start anew?
Also, if i wanted ceberus to be inside, i would have to make a custom partition right?
Excuse me, but what is ceberus??
kassarin said:
I have just recently pushed in a partition table 'Bravo CM7 r2' using fastboot and adb. [...] Then i restored the backup i did before i updated the partition tables.
Click to expand...
Click to collapse
As MatDrOiD said earlier, make sure the ROM you're restoring is made for the CM7R2 partition table. The stock partition table has a 250 MB /system partition while CM7R2 has an 145 MB one. If you're trying to fit your 250 MB /system ROM into an 145 MB /system... there's your problem. So, what ROM were you using before flashing CM7R2?
I have a rooted HTC Evo 4G. It is rooted with revolutionary and the s-off. I didn't root my device. I was playing with trying to install busybox from the busy box installer. It failed. But now that I have rebooted the phone(swapped a new battery on). It is stuck on the HTC EVO 4G white screen. I can get to the hboot screen and can get into recovery for Revolutionary CWM v4.0.1.4. I have tried some stuff. I'm here so it's safe to assume nothing worked. I have wiped the cache partition, I have tried the Fix Permissions option, Wiped Dalvik cache, wipe data/factory reset. I am knowledgeable with computers. Just not sure about this issue or which direct to go.
What can I do to get the phone back operational? Is there an image i can put on the sdcard and flash this thing with? I think I can manage that.
I'm so late in the rooting game here, there is so much information, not sure what I'm looking at. So I thought I would just go ahead and ask the questions. Maybe I won't get beat up too much and get pointed in the right direction.
I'm sure someone here can help you. A detail that you may have left out in your explanation is: what ROM you expect the phone to boot into.
Sounds like you just need to re-flash a ROM while you are in recovery.
Plenty of ROMs around here to choose from. I might recommend a very simple "stock" ROM for starters.
Later on, consider using a different recovery going forward. Evos historically have had issues with CWM. Try Amon Ra or SmelkusMOD...
Sent from my PC36100 using xda app-developers app
Yup, I would recommend Smelkus after you fix this
Go into recovery and make a full backup first (this way you can advance restore data later)
Then, as suggested above, grab a stock rom and flash it through recovery (making sure to wipe EVERYTHING)
Last, try to boot up your phone. It should work
Once it does, restore any data if you need to...if not, flash SmelkusMod recovery and then flash your rom of choice
Sent from my PG06100
I have the revolutionary recovery. Do I need to replace that with the smelkus mod?
a94cobra said:
I have the revolutionary recovery. Do I need to replace that with the smelkus mod?
Click to expand...
Click to collapse
You have the revolutionary BOOTLOADER. There is no "revolutionary recovery"
Sent from my PG06100
If you've wiped cache, dalvik cache, and factory reset your phone then you have no ROM to boot into. Flash a rom and you'll be good to go
kendallc123 said:
If you've wiped cache, dalvik cache, and factory reset your phone then you have no ROM to boot into. Flash a rom and you'll be good to go
Click to expand...
Click to collapse
Thats incorrect....the rom isn't stored on the data partition, which is what a factory reset wipes
ROMs are loaded from the /system partiton
Sent from my PG06100
CNexus said:
Thats incorrect....the rom isn't stored on the data partition, which is what a factory reset wipes
ROMs are loaded from the /system partiton
Sent from my PG06100
Click to expand...
Click to collapse
I was assuming he had formatted everything, including the system. If you didn't, my bad. Sorry
I think I got myself a Maguro Galaxy Nexus (on ATOM ROM, Android 4.2.2) with a corrupted /data partition.
(Not 100% sure though, so if you think I'm wrong, please tell me)
I can't wipe the /data partition in CWM, nor perform a partial restore for data from nandroid backup. When I try that, CMW crashes and my phone reboots.
I can however still boot the phone normally. Everything else works, just can't do a factory reset in CWM, which I want to do to flash a new ROM.
Any ideas how I can solve this? I'm alright if I loose my data, I got backup. Would like to avoid erasing the virtual sdcard though (takes ages to copy).
Djalaal said:
I think I got myself a Maguro Galaxy Nexus (on ATOM ROM, Android 4.2.2) with a corrupted /data partition.
(Not 100% sure though, so if you think I'm wrong, please tell me)
I can't wipe the /data partition in CWM, nor perform a partial restore for data.
I can however still boot the phone normally. Everything else works, just can't do a factory reset in CWM, which I want to flash a new ROM.
Any ideas how I can solve this?
Click to expand...
Click to collapse
Try via fastboot
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Try via fastboot
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Try using what command? I can flash roms n gapps no problem, but I can't do factory reset. Is there a command for factory reset in fastboot?
P.S. We are almost neighbours, Schiedamer hier.
*EDIT*
Lol, feel a bit stupid now. I didn't know there was the fastboot command "erase". I erase userdata using fastboot, however, now I got a whole new problem... It got rid of the whole folder, not just the contents. Now there is no data folder. And I forgot that the virtual sdcard is also inside the data folder... Now I got no data at all, nothing to flash...
I'll try to find out what to do, but if anyone reads this soon, perhaps you can help me.
*EDIT2*
Alright, I tried something I've wanted to try a long time now - I connected my USB memory stick (OTG mode) while in CWM. It worked wonders. I have all my zip files (ROM,Gapps,Kernels) on it, so I flashed from there.
EVERYTHING WORKS NOW.
Though my sdcard data is gone, but luckily I backed it up this morning.
P.S. For those of you who don't know, I found out you can restore nandroid from, and backup to the USB memory. I think I won't even put my nandroid and zip files on my phone anymore. I'll keep it on my usb memory.