Develop Bugs

[Q] Everytime I wipe cache or dalvik I can't boot or install roms

Ok, I just finished formatting one of my memory cards and installed a new rom. It booted fine. I went back into recovery to wipe the cache and dalvik and when I go to reboot it stays stuck at the white HTC screen. This has happened with multiple roms. After that I went back into recovery to try to reflash the rom and this is when the errors from last night come back:
Gets all the way to formatting cache, then system, then copying files....
E:Failure at line 6:
Copy_dir Package: data DATA:
Installation aborted.
This is the problem I've been running into before I formatted the card. This is a brand new Evo, with the 2.02 boot, version 4.
If I wipe data
What does this sound like? Something go bad in the rooting process? Maybe something to do with Amon recovery? Maybe try clockwork or what?

I rebooted into recovery and wiped all 3 then went to install the rom on the card and it installed this time. I don't remember my last phone working anything like this at all... not sure what gives.

Jbroad572 said:
Ok, I just finished formatting one of my memory cards and installed a new rom. It booted fine. I went back into recovery to wipe the cache and dalvik and when I go to reboot it stays stuck at the white HTC screen. This has happened with multiple roms. After that I went back into recovery to try to reflash the rom and this is when the errors from last night come back:
Gets all the way to formatting cache, then system, then copying files....
E:Failure at line 6:
Copy_dir Package: data DATA:
Installation aborted.
This is the problem I've been running into before I formatted the card. This is a brand new Evo, with the 2.02 boot, version 4.
If I wipe data
What does this sound like? Something go bad in the rooting process? Maybe something to do with Amon recovery? Maybe try clockwork or what?
Click to expand...
Click to collapse
Ive seen this also with a new phone that has the older hBoot, just without the errors. Couldn't get it to take a custom ROM but you could flash kernels with no problem.
Have you tried running the RUU and then reflashing the recovery?

xHausx said:
Ive seen this also with a new phone that has the older hBoot, just without the errors. Couldn't get it to take a custom ROM but you could flash kernels with no problem.
Have you tried running the RUU and then reflashing the recovery?
Click to expand...
Click to collapse
I think it might be something with the recovery, because I tried to flash Clockwork via rom manager and it said it took, but Amon is still there. I'm going to flash the pc36 ruu that was originally used to see if it has any affect.

Solved.. thanks for the help

I am getting the exact same situtation going on. I hope I didnt break my phone. I really LOVE this damn thing. hahah Please help. What are the steps I need to do to get my phone working again.

[Q] Help.... phone stuck in saying "CyanogenMod 7"...

HI... i updated my phone with cyanogen 7 rc2, but after it booted up it's stuck in the animation that says cyanogen mod 7 , and the blue android sign... in comes than goes, again it comes... about 20 min stuck... what to do???

It sounds like you need to go into recovery mode and delete all your caches. If you are using ClockworkMod recovery do the following (make sure you are backed up first):
Delete all user data and info (under wipe data/ factory reset),
Wipe cache (under wipe cache partition),
Wipe Dalvik Cache (under advanced).
Then once you've done that try installing and running the ROM again.

i done that one time... for info im using AmonRA.. i cleaned all the cache and everything also... and installed again... nothing happens... fortunately i restored my nand backup and booted my phone with the OTA again... waiting for some answer.... do u think that installing stable version can fix this?

Sounds like a bad flash. I had rc2 running for a month or so with no issues. I've had times when the rom just doesn't install properly ans reflashing fixes it.
Download the zip again, if possible check md5 to make sure it's all good, make sure you have the desire/bravo GSM version, clear everything and flash just the rom and nothing else. If it boots, then go back and flash your gapps and whatever else you want.
Sent from my HTC Desire using XDA App

thx for replying.. as i was waiting for your reply, i download the cm 6 that is a stable version and checked, it has the same problem too.. i also downloaded GingerVillain 1.6 and it had the same problem too. do u think the problem might be that my phone is "s-on"? and how should i know if my phone is s-on or s-off... when i was rooting my phone with unrevoked, i checked the option that says disable security, but i'm not sure if it's disabled.... because i can't install un-signed zip packages....
any reply?

That definitely sounds odd. Its definitely not an issue with S-ON/OFF, nothing you've done here requires S-OFF to work properly.
Lets just make sure you're following all the steps.
In amonra, you've done your nandroid backup, so no need to do it again. There's no point having a non working backup
Go to wipe and wipe data/factory reset
Wipe davlik cache
Wipe sd-ext (shouldn't need to do this one as you don't have apps2sd yet, but better to be safe)
Now you flash your update.zip, then reboot and you should be fine. The only other thing I can perhaps suggest if every rom you flash sticks at boot is to perhaps try clockwork recovery instead of amonra. Apart from that we might have to wait for folks more knowledgeable than myself cause I'm all out of ideas.

thx for reply.... in meanwhile , i s-off ed my phone and it has the same problem too... i have problem with all cm and gingervillain roms.. but i don't have any problem with leedriod... one more question that maybe the problem is that i have android 2.2 installed, but gingervillain and cm use android 2.3 ... this maybe the problem.... and that's why leedroid works right, because it uses android 2.2.... i'm going to check OxyGen roms... i will post the result here...

i also faced same problem CM7 .. i tried CM6 and it went on fine..

heyyy... right after i posted the reply , i went to recovery and wiped anything, then installed gingervillain 1.6, and everything's fine now... it booted up and now im setting it up.... im going to check the cm 7 too.

i tried cm7 rc2 ... and it was fine and now im using it... here's a how to for solving the problem...:
1.S-OFF your device with AlphaRev : http://forum.xda-developers.com/showthread.php?t=805811
2.Install the AlphaRev Recovery(S-OFF Image will do it automatically).
3.Go to recovery and install the rom...
4.Boot up and it should not go to system and it should stay in loop as the problem was..
5.Now you should reboot your device into recovery... there are two ways to do this... either take the battery off and put it on, then boot to bootloader by pressing the volume down and the power key and select recovery , or the second way connect it to your computer and start adb and run this command:
adb reboot recovery
6.In AlphaRev recovery first wipe the cache partition , wipe user data, and factory reset...
7.then install the rom (either cm7 or gingervillain)...
8. boot up , and now you have the system running...
This solved my problem... reply if it didn't yours...

hooo.. it worked for me now. just kept update.zip in a new SD card and not flashed google apps..

im very happy that i solved one's problem.. ... thread marked as solved...
*UPDATE* : now i realized that we can mark it as solved.. !!! hehe.. Admin do it for us...

[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.

First boot taking forever on ICS BCM ROM

Hi folks,
I flashed the ICS 4.0.4 BCM RC3.2U1 ROM on my phone and I have now been waiting for first boot to complete for well over 90 minutes (animation looping continuously).
I wiped Dalvik-cache, formatted the SD-Ext partition as recommended and then flashed the ROM.
How long is the first boot supposed to take? Should I remove the battery and try flashing again?
HTC Desire
S-OFF
Radio 5.17.05.23
Stock hboot
Clockwordmod Recovery
Thanks.

thegreendroid said:
Hi folks,
I flashed the ICS 4.0.4 BCM RC3.2U1 ROM on my phone and I have now been waiting for first boot to complete for well over 90 minutes (animation looping continuously).
I wiped Dalvik-cache, formatted the SD-Ext partition as recommended and then flashed the ROM.
How long is the first boot supposed to take? Should I remove the battery and try flashing again?
HTC Desire
S-OFF
Radio 5.17.05.23
Stock hboot
Clockwordmod Recovery
Thanks.
Click to expand...
Click to collapse
It says about five mins
just be patient
I froze my self few days ago until I've red it in their thread

thegreendroid said:
animation looping continuously
Click to expand...
Click to collapse
this is known as a bootloop. whenever your phone does this for a long time, don't bother waiting for 90mins, it's not going to go anywhere. pull the battery.
thegreendroid said:
I wiped Dalvik-cache, formatted the SD-Ext partition as recommended and then flashed the ROM.
Click to expand...
Click to collapse
as a bare minimum you need to perform a full wipe before flashing a rom: 'wipe data/factory reset' option within recovery.
i don't think you have done this, therefore you have bits of old and new rom mixing up so it bootloops

eddiehk6 said:
this is known as a bootloop. whenever your phone does this for a long time, don't bother waiting for 90mins, it's not going to go anywhere. pull the battery.
as a bare minimum you need to perform a full wipe before flashing a rom: 'wipe data/factory reset' option within recovery.
i don't think you have done this, therefore you have bits of old and new rom mixing up so it bootloops
Click to expand...
Click to collapse
Aye, correct. Before you flash a new rom format boot, system, data, cache, dalvic and sd-ext (which you need if you want mounts2sd!!)
It also says on the BCM thread that at first it may take a while to boot, and 2nd time it will not boot at all, for which you press volume down, power and trackpad to restart the phone, and it will boot fine.

Thanks for the replies all, as it turns out I hadn't wiped the /data partition prior to installing the ROM.
Although I now have a "insufficient storage space" available issue even though I have enabled m2sd. Is anyone else having the same problem?

here's same as u!
thegreendroid said:
Thanks for the replies all, as it turns out I hadn't wiped the /data partition prior to installing the ROM.
Although I now have a "insufficient storage space" available issue even though I have enabled m2sd. Is anyone else having the same problem?
Click to expand...
Click to collapse
its not comin up..its an ics on htc desire, but its not working, i'd performed a factory full wipe, heading for another full wipe..hope it works,
but a question?! should i update the firmware when im coming from gingerbread rom (stock) to ics?

Hi,
can you load your old working rom ?
which one was it ?

thegreendroid said:
Thanks for the replies all, as it turns out I hadn't wiped the /data partition prior to installing the ROM.
Although I now have a "insufficient storage space" available issue even though I have enabled m2sd. Is anyone else having the same problem?
Click to expand...
Click to collapse
did u change the hboot to alpharevs data ++? The rom needs 180mb on the system partition.

Wiped Internal Storage; now phone reboots on loading ROMs

Hey guys,
So last night I accidentally wiped internal storage in TWRP. I guess that messed up my partitions or something, I don't know. Anyway, I can still access recovery, and I've tried to do a restore (one that I made back when I was on stock 4.4.2 I think) but after that it tries to boot, gets to "Android is upgrading... Optimizing app Y of X." and once that operation completes it shows the lockscreen for about a tenth of a second, and the phone reboots.
I'm stumped. Anyone know what can I do?
Sorry if this has been asked a hundred times. For some reason the search function in the forums isn't working for me. And I've been looking for a solution all morning.
EDIT: FYI when I tried the restore I did only System and Data and not Boot, because I was afraid that'd cause more problems.

Did you try restoring and performing a factory wipe before booting the newly-restored ROM?

It seems that Marshmallow based roms aren't working, but Lollipop ones will boot. Not sure why as I didn't have any problem with the same MM roms in the past.
More info:
MM roms wont flash in TWRP; after the failed attempt, TWRP says system cannot be mounted until I either wipe or install a 12.1 rom.
Tried to install a stock rom (4.4.2) and it failed in TWRP. Just says "Error Flashing"

Are you performing a full wipe (system, Dalvik, cache, data) before installing or restoring a ROM? Is the phone running the latest version of TWRP?

audit13 said:
Are you performing a full wipe (system, Dalvik, cache, data) before installing or restoring a ROM? Is the phone running the latest version of TWRP?
Click to expand...
Click to collapse
Yes to full wipe. TWRP is 2.8.7.0, so yeah I think it's the newest? Not 100% sure.

Wiping internal storage should not affect the partitions. I'm not sure that TWRP even has the ability to change partitions.
Yes, 2.8.7.0 is the latester version of TWRP.
If you are on the nj2 bootloader, try flashing this in TWRP: http://forum.xda-developers.com/galaxy-s3-att/general/rooted-ucufnj1-stock-rom-t2985006

Welp, seems to be all good now. Not sure if I really did anything to fix it or not. I tried to install a stock ROM but it wouldn't boot (stuck on Samsung logo) but after that my CM13 ROM installed properly again. The one CM13 ROM I have still wont install at all - maybe that file became corrupt or something? Not sure if that's even possible.
Either way I'm all fixed up. Thanks for all your help.
Cheers

Glad you got it sorted out. If you do figure out what you did to get it working, post your answer as it may help others that are in a similar situation.