Develop Bugs

[Q] Gotta be an easier way

I just managed to nearly brick my buddy's Droid X, and I just wanted to see if there was an easier way to do what I had to go through.
Going from Liberty 2.0 to DarkSlide, did a nandroid backup, wiped data, cache, dalvik, the usual... But, darkslide didn't install right for some reason, and it hung on the bootlogo. After waiting 15 minutes, I finally pulled the battery, expecting Clockwork to come up, and I could restore. Instead, I had the normal recovery, with the four options to wipe data, wipe cache, install update.zip, or reboot.
Now, besides the point that I just had to sieve through several update.zip's, including a bad md5 sum or two, running RSD Lite and loading a stock Rom and re-rooting. This was my first time ever going through all this crazy process... I'm just wondering:
If a ROM goes wrong in installing, is there a way to avoid all the insanity I just went through, or am I running the risk of going through all that every time I flash a new ROM?

Haha same here. I almost bricked my phone but o was able to restore it with the original RUU to downgrade and reset to factory settings. By doing that I just had a spare sd card to format and re-rooted. Once that was done ROM Manager did the rest with restoring my last backed up working ROM on my original sd card.
Its hard to come by one click rooting tools.
Sent from my HTC Inspire 4G
XDA Developers Premium App

homescrub said:
I almost bricked my phone but o was able to restore it with the original RUU to downgrade and reset to factory settings. By doing that I just had a spare sd card to format and re-rooted.
Click to expand...
Click to collapse
How would I go about that?

hmm If you would flash Clockwork into recovery section of you phone and not using Rom Manager to boot into update.zip (ClockWork), you woudln't have such problems
Everytime I do a update and it fails it still boots into the Bootloader and my beloved ClockWork Mod v3 with the ability to flash another CustomRom with works.
Greetins

Man, I'm stuck in a boot loop.

Ok, So I wanted to change my ROM and I thought I did it right, but obviously that was not the case lol.
Pretty much I flashed the clockwork recovery, had it set to wipe the two things you want to wipe and then once it came back I installed zip from sd card, however, when I thought I was done and restarted my phone it just continuously loops back and forth back and forth.
I know there's a way to fix it since I have a micro sd reader, but how? I've got something REAL important to do tomorrow and not having my phone will be a huge mess.

d3athb4dishonor said:
Ok, So I wanted to change my ROM and I thought I did it right, but obviously that was not the case lol.
Pretty much I flashed the clockwork recovery, had it set to wipe the two things you want to wipe and then once it came back I installed zip from sd card, however, when I thought I was done and restarted my phone it just continuously loops back and forth back and forth.
I know there's a way to fix it since I have a micro sd reader, but how? I've got something REAL important to do tomorrow and not having my phone will be a huge mess.
Click to expand...
Click to collapse
What ROM were you on and what ROM are you going to?
What did you wipe?
How did you wipe?
How did you flash?
Sent from my T-Mobile G2 using XDA App

OriginalGabriel said:
What ROM were you on and what ROM are you going to?
What did you wipe?
How did you wipe?
How did you flash?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
I was on the stock rom and I was trying use the update-cm-7.0.3-vision-signed
I used Clockwork Recovery to wipe and it already had two options checked to wipe, Pavlik cache and wipe data or whatever it says... Then I flashed into clockwork recovery and I went to install from ZIP, I went and found the rom file on my sd card and pressed install, it took a few moments and was done. I also added the googlepack using the same method right after. Then when I thought I was finished I rebooted my device and its been stuck in a loop ever since.

Appreciate you trying to help, I guess I figured it out with a good ole fashioned guess hahaa.
I went and wiped my phone and data to factory, wiped the Pavlic (which I think I'm saying wrong lol) and then I installed the ROM again and it worked this time.

d3athb4dishonor said:
I was on the stock rom and I was trying use the update-cm-7.0.3-vision-signed
I used Clockwork Recovery to wipe and it already had two options checked to wipe, Pavlik cache and wipe data or whatever it says... Then I flashed into clockwork recovery and I went to install from ZIP, I went and found the rom file on my sd card and pressed install, it took a few moments and was done. I also added the googlepack using the same method right after. Then when I thought I was finished I rebooted my device and its been stuck in a loop ever since.
Click to expand...
Click to collapse
I would recommend flashing the superwipe from this thread. there are 3 downloads, Try the standard superwipe first. and use superwipe+ if you have GPS problems.
Super wipe automaticly wipes system, data and cache partitions. Flash the ZIP in recovery as you would flash a ROM.
And it is recommended not to use ROM manager for flashing and to always to it manually in CWM.
So download superwipe, flash superwipe, flash ROM, flash GAPPS and reboot.

I would also recommend flashing cm 7.1 because its an outrageously HUGE upgrade over the one you just flashed.
Sent from my HTC Vision using XDA Premium App

[Q] WTF is up with my phone???

Hey everyone,
Ok, here's the deal. I flash new ROM's by CM or Amon and I get the message saying SD card unmounted. Go to settings to mount it, it shows as no SD card installed. Reboot into recovery, SD available. I've read clearing cache and davlik a few times usually clears up any initial load problems for new ROM's. Nope, doesn't help. Reboot shows no SD installed
Back into Recovery.
Mount SD card?
Tried it. Still unmounts on boot.
BUT...
Not on ALL ROM's.
I'm running Myn's Warm 2.2 fine (well, some laggyness)
I'm running 1975jamie's King Cocoa II True Blue just fine
I ran Cyogen fine (just don't like AOSP ROM's)
MIUI ran great.
I'm dying to keep the new line of Sense 3 ROM's.
They all install, load, and boot just fine.
I get to the initial "new user" setup stages and they all connect and sync just fine, then POOF! I get the little SD card symbol in the upper left hand corner saying SD card unmounted...
I ignore that to check out the ROM's and they scroll just fine, everything opens and closes fine.
Any ideas?
Jack

Are you flashing in recovery or with ROM Manager?

Last flashed ROM was Warm 2.2
Used ROM Manager to D/L ROM, add on's, and flash them.
All boxes checked prior to flashing (Backup, Cache, Cache/Davlik)
Previously was running Warm 2.2 (prior to King Cocoa II), but flashed through CM.
Both flashing methods yielded no problems.
Flashed MIUI in Recovery AND ROM Manager to test.
Both yielded no problems.
Every other ROM, but the 4 I listed in my OP, shows no SD card.
So basically, list of WORKING Rom's installed and run, in order, were:
Warm 2.2 then
New install of King Cocoa II then
New install of Cyogen then
New install of Warm 2.2 (deleted backup for fresh start) then
New install of MIUI then
Backup of Warm 2.2
Only backups I still have are KC 2, Warm, and MIUI.
In between some of those I tried flashing other ROMS, but all croaked with no SD message...
Jack

I don't recommend using Rom manager for flashing roms. Rom manager and clockwork mod tend to not wipe cleanly. You should gave better luck using only amon ra. Wipe everything 3 times(except sd) before flashing. If you still have issues, try formating your sd card on your computer.
Sent from my PC36100 using XDA App

That's all well and good, but doesn't explain why only 4 ROM's flash "right" on my phone regardless of what method I use, lol

Gotta tell ya though, as much as I've liked this Evo...
The Samsung Galaxy S II is looking better and better every day.

I can't promise, but I can assure that you'll have better results using Amon Ra and flashing in recovery.
The best method is do a nandroid of you current working ROM. Backup everything but cache (arguable), then go to wipe and wipe every setting there is once, except the SD card itself, and the battery stats, if you're not fully charged.
Then wipe Dalvik cache and cache 2 times.
Then flash your ROM.
If you REALLY wanna do it up right, before you flash the new ROM, back up your SD Card to your computer, format it in Windows with a card reader, then put it back in the phone, go to partition, in Recovery.
Partition using 64mb for swap (arguable.. some people put 0) and 1024 for EXT partition.
When it's done, convert to EXT3.
Then copy all your stuff back to your SD Card.
Flash your ROM and then flash DT APS2SD before you reboot. I know a lot of ROMS have it baked in, but I still flash it manually.
Once your ROM boots (if it does) let the phone just sit til the screen shuts off, then reboot to Recovery and do another Nandroid, so you have a backup of a stock/working version of your ROM. Flash a custom kernel if you want to (wipe cache and Dalvik Cache first), then reboot. Let your phone settle again (til the screen turns off) then start setting things up, Google acct., apps, etc.
If you use Titanium backup to restore your apps, ONLY RESTORE apps/Data that you put on your phone. No Google apps, no System apps, No HTC apps.
Then reboot again, when you're done.
Yes, it will take some time to do all this.
Yes, you will have very little chance of problems like force closes, reboots, etc.
Now if you REALLY REALLY want to do it right, do a nandroid of your current setup, and then flash a stock/Sense ROM in recovery and Nandroid that so you have a stock setup for flashing GPS fixes, updating your profile, etc.
(BTW, having a stock setup means you can probably just flash that and not unroot if you have to take your phone in at all)

Is your card partitioned if so did you partition it after you backed up warm 2.2 .
You may need to fix sdext in recovery or run a fix using your computer I had something like that happen and I fixed it by mounting to my PC in recovery then started to copy some files then just stopped it in the middle of coping and when I plunged it back in my PC recognized there was a problem and ran a fix for it .
I know that sounds kind of geto.
Sent from my PC36100 using XDA App

Just thought I put in my 2 cents. I Used to use Rom Manager to download roms but I experienced a lot of force closes. Now, I always flash thru recovery. I Factory wipe 3 times, I also use calkulin's format 3 times, clear cache 3 times and clear delvick cache 3 times... then flash. Also, read thru the forums on the roms you are using this maybe a problem with that rom. I personally have not the issue you have.

Help with Rebooting wiping storage

Hello everyone,
I would post this in the development thread but I can't since I am a ne user. Anyway..
I am currently on InFamous switching between the 2.4 TW version and the Google Edition v2.0.
My problem is every time I reboot my phone, it gets stuck on the Samsung Galaxy S4 boot image. Then when I go to recovery the Internal storage shows 0 MB available, and I can't fix permissions or wipe anything without having to format data first. The only way to boot my phone again, is to format data, wipe everything, and reinstall the ROM which is very annoying and time consuming.
PLEASE HELP!!
Thanks in advance
-Jesse

re: rebooting into Google Edition Rom
razorj7 said:
Hello everyone,
I would post this in the development thread but I can't since I am a ne user. Anyway..
I am currently on InFamous switching between the 2.4 TW version and the Google Edition v2.0.
My problem is every time I reboot my phone, it gets stuck on the Samsung Galaxy S4 boot image. Then when I go to recovery the Internal storage shows 0 MB available, and I can't fix permissions or wipe anything without having to format data first. The only way to boot my phone again, is to format data, wipe everything, and reinstall the ROM which is very annoying and time consuming.
PLEASE HELP!!
Thanks in advance
-Jesse
Click to expand...
Click to collapse
Have you tried this:
Before doing anything, be sure to back up the internal sdcard to a folder on your computer if you have anything you
want to save on the internal sdcard. Also be sure that the Google Edition zip file rom is on your "external" sdcard.
When the phone is flashed and ready to use go into settings>accounts tab>backup and reset>"Factory data reset".
Click on the factory data reset.
After doing that reboot into cwm or twrp which ever you are using and do a full wipe as you usually do but don't
forget to include "Factory reset".
Then flash the Google Edition rom as you normally have done and it should fix the problem you are having hopefully.
Good luck!

Misterjunky said:
Have you tried this:
Before doing anything, be sure to back up the internal sdcard to a folder on your computer if you have anything you
want to save on the internal sdcard. Also be sure that the Google Edition zip file rom is on your "external" sdcard.
When the phone is flashed and ready to use go into settings>accounts tab>backup and reset>"Factory data reset".
Click on the factory data reset.
After doing that reboot into cwm or twrp which ever you are using and do a full wipe as you usually do but don't
forget to include "Factory reset".
Then flash the Google Edition rom as you normally have done and it should fix the problem you are having hopefully.
Good luck!
Click to expand...
Click to collapse
Unfortunately, this did not work =(. Again, as soon s I reboot, I get stuck on the Samsung screen and have to pull out the battery. Then, in recovery my Internal storage has 0 MB aeven though the folders are empty.

razorj7 said:
Unfortunately, this did not work =(. Again, as soon s I reboot, I get stuck on the Samsung screen and have to pull out the battery. Then, in recovery my Internal storage has 0 MB aeven though the folders are empty.
Click to expand...
Click to collapse
Have you tried holding the power button, home key and the volume up key all at the same time to boot in recovery? If not do a battery pull and do it when turning the phone back on
Sent from my SGH-M919 using xda premium

razorj7 said:
Unfortunately, this did not work =(. Again, as soon s I reboot, I get stuck on the Samsung screen and have to pull out the battery. Then, in recovery my Internal storage has 0 MB aeven though the folders are empty.
Click to expand...
Click to collapse
If you already tried to Odin flash the STOCK rom and formatted your internal sdcard and you still find "0 MB"
in your internal storage then it must be a hardware issue and if I were you I would return/exchange the phone.
Good luck!

It's not a hardware issue. It's a bug in twrp. Whenever you do "format data" it corrupts the data partition. Use PhilZ Touch recovery. His recovery includes the fix. Try it.

teshxx said:
It's not a hardware issue. It's a bug in twrp. Whenever you do "format data" it corrupts the data partition. Use PhilZ Touch recovery. His recovery includes the fix. Try it.
Click to expand...
Click to collapse
Thanks, I'll try that. How do I get rid of the bug after writing the new recovery? Format data?
Thanks!

Hello, any progress please? I have exactly the same issue.

I found here http://forum.xda-developers.com/showthread.php?t=2265588&page=23 this solution:
I wanted to clean my internal SD card before flashing Omega ROM, so I used Format Data option from Wipe section in TWRP.
After that I lost almost two days trying to fix my phone. Flashed stock ROM, TWRP and Omega ROM endless times without success after that.
My phone became randomly unbootable on reboot or power on! It was stuck on i9505 logo that is shown before boot animation forever. It was same for both stock and Omega ROM, with or without external micro SD.
After endless tries, I figured out that my phone works fine if I do factory reset and wipe from original recovery. Worked fine before and after flashing TWRP.
I tired to Format Data from TWRP again and my phone again was stuck on boot.
So I did everything once more. Flashed stock, did factory reset and wipe from original recovery and then installed TWRP and in the end I flashed Omega without wiping anything.
Everything works just fine now and I will not try to use Format data option from TWRP on this device in near time! Please fix this.
First I used TWRP 2.5.0.1 and then 2.5.0.2, but it is same in both of them.
Click to expand...
Click to collapse
Now I'm downloading stock rom so I'll try it in next 2 hours.

bet you guys previously flashed a aosp rom, I could be wrong, but it sounds as if you did.

TheAxman said:
bet you guys previously flashed a aosp rom, I could be wrong, but it sounds as if you did.
Click to expand...
Click to collapse
It says so in the OP... going between TW and Google Edition 2.0.. Out of curiosity though, what difference would that make? I have flashed and have backups of two versions of TW and quite a few AOSP variants... I can move between them seamlessly and haven't encountered any such problems as the OP. I use TWRP as well.

It was TWRP problem. I have flashed the stock ROM with stock recovery. I have done full wipe and my phone works well again. This is bug in TWRP. Don't push "format data" button!

[Resolved!] Update to 4.3+ ROM freezes on boot

I am on Liquid Smooth 2.9 (4.2.2) and using TWRP 2.6.3.0 phone is an i747m 32GB model. I tried upgrading to LS2.10 which is 4.3. Installed ROM OK but after first reboot phone froze on the Samsung logo. It wouldn't even get the the boot animation. I tried several methods of flashing as requested but to no avail. Today I tried the latest nightly of Carbon ROM which is 4.3.1 and encountered the same issue. I tried rebooting after flashing GAPPS and it just froze at the Samsung logo without going to boot animation. I did flash the latest bootloader in between while trying to diagnose as well.
Does anyone have any suggestions or similar situations? I would really like to upgrade to a 4.3 ROM but seem to have hit a hurdle...
Thanks in advance.

So I've had a little time to try some other things. I've verified the MD5sum of all files trying to flash. All are good. I've tried installing the latest nightly of Carbon ROM after doing a full wipe of all internal. I haven't formatted my external yet. Flashed ROM and phone boots fine. I've tried flashing GAPPS both during initial flash, after initial flash and not at all. In every case the phone boots fine after the initial flash and functions perfectly. It will not boot a second time at all. In all cases so far on reboot it just stays on the Samsung logo screen and I've left it for about a half hour just to make sure it isn't that I'm not waiting long enough. I hold the power button for 8 seconds and then boot into recovery. I've tried doing a factory reset and rebooting. No go. I've tried refreshing the ROM and it still won't boot after. I haven't taken a logcat yet as I just haven't had time but I'm really confused why multiple ROM's. I've currently restored back to 4.2.2 liquidsmooth 2.9.
I'm really hoping someone has a suggestion or that they've come across this before.

Galloway said:
So I've had a little time to try some other things. I've verified the MD5sum of all files trying to flash. All are good. I've tried installing the latest nightly of Carbon ROM after doing a full wipe of all internal. I haven't formatted my external yet. Flashed ROM and phone boots fine. I've tried flashing GAPPS both during initial flash, after initial flash and not at all. In every case the phone boots fine after the initial flash and functions perfectly. It will not boot a second time at all. In all cases so far on reboot it just stays on the Samsung logo screen and I've left it for about a half hour just to make sure it isn't that I'm not waiting long enough. I hold the power button for 8 seconds and then boot into recovery. I've tried doing a factory reset and rebooting. No go. I've tried refreshing the ROM and it still won't boot after. I haven't taken a logcat yet as I just haven't had time but I'm really confused why multiple ROM's. I've currently restored back to 4.2.2 liquidsmooth 2.9.
I'm really hoping someone has a suggestion or that they've come across this before.
Click to expand...
Click to collapse
When you flash the ROM, are you wiping dalvik cache as well as wiping all data/ factory reset and cache?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I have the same, CM10.2, Quantum. First boot is ok. but after reboot phone freeze on samsung logo and recovery TWRP 2.6.3.0 needs password. I cant make any wipes, cant restore backup - needs password. Update last bootloader, before flashing made wipe /system /data /cache /dalvik, after - wipe /cache /dalvik /data againe - nothing, second boot only logo,
Could some one tell me, what I do wrong?

gluk1470 said:
I have the same, CM10.2, Quantum. First boot is ok. but after reboot phone freeze on samsung logo and recovery TWRP 2.6.3.0 needs password. I cant make any wipes, cant restore backup - needs password. Update last bootloader, before flashing made wipe /system /data /cache /dalvik, after - wipe /cache /dalvik /data againe - nothing, second boot only logo,
Could some one tell me, what I do wrong?
Click to expand...
Click to collapse
At least it's not just me....unfortunately I don't have much time lately so I haven't been able to try experimenting. I noticed you are using TWRP as well....I may try flashing CWM if I get a sec and see if the results are the same. Also if the same happens and I have enough time I'll try and grab a logcat. If I don't have time it's called wipe and restore from a backup.
And yes Dalvik + cache are always wiped anytime I flash anything as a minimum. With this issue I have been doing an entire internal format. I have tried just wiping cache and Dalvik when it occurs as well as fixing permissions but still doesn't boot. Wish I had more time latrely to narrow it down.

Yes, its work. I flashed stock ROM 4.1.2, then root device, flash CWM 6.0.2.3 (no touch) and flash Quantum 2.20. But I think, problem not in recovery or device. Problem in Titanium Backup, I used it to restore some system apps and accounts, now I restored only call log and SMS.

I have now tried flashing with TWRP and pulling SD card before initial boot to eliminate an SD card issue. I've set to not install backups from Google as precaution. Still the same result of frozen at Samsung logo.
I've then flashed the newest CWM non-touch and wiped all with flash. The result was even worse. This time it wouldn't even boot the first time for initial setup it just hangs at the Samsung logo.
This is starting to get frustrating just due to the fact of me not having a huge amount of time to dedicate to isolating the issue. I need to get a logcat but I am not usually near a computer to ADB to it when it is not booting. If I have time this weekend I'll try and get a logcat to post up.

CWM broke it real good! LOL! Anyways I couldn't even get my backups to restore. I tried taking a logcat while it was frozen but was not able to get an ADB connection in order to even get a logcat. I managed to push a fresh copy of Liquidsmooth 2.9 to the SD card and install it. Then flashed TWRP back. Then restored my back up. What a tedious task to still be scratching my head as to why multiple 4.3 ROM's won't boot on the second boot after flashing...

It's been resolved! As per an awesome person on Carbon's G+ thread don't flash the ROM from external SD .Only flash it from internal storage!