Develop Bugs

Root + Flash Recovery was successful, but can't flash any roms?

Some background:
-This is my 4th Evo. Previous 3 were all rooted.
-Rec'd the new Evo last Thursday, rooted it immediately using the Auto Root method.
-Everything was successful, and Sprint Lover's ROM was automatically flashed on my phone, until I tried flashing a new rom.
Roms I tried flashing:
-MIUI
-BOS "Royal Liquid"
What happens:
-With MIUI, it flashes, restarts and then boots up all the way and then freezes after 20 secs and restarts, EVERY TIME.
-With BOS, stuck in bootloop. Keeps restarting at the white "htc EVO 4g" screen.
Tried both recoveries, Amon_RA AND Clockword Mod(CWM).
Yes, wiped every time. Even d/led "Calkulin's Format ALL" and flashed it (in Amon RA, it wouldn't let me in CWM.)
Please help, and ask me any questions you may need. I'll do my best to provide every answer.

I'm dealing with the same issues except i was trying to flash to Koni Elite 3

I'm can't even do a restore,cuz i get a recovery error.

Update i can do a recovery to an old backup

androidrookie84 said:
Update i can do a recovery to an old backup
Click to expand...
Click to collapse
Next time just update your same post or make a thread of your own. No sense of posting your problems in someone's else's problems thread. But I'm glad it's working for you now.
[Update]
Just d/led and flashed CM7 using ClockwordMod. Everything seems to be working fine.
I don't know what's going on anymore.
I am going to try to flash BOS Royal Liquid again and see what happens.

Make sure your device still displays "S-OFF" in the bootloader screen. Reflash amon RA or flash amon RA v2.3 and then go to the wipe menu and wipe EVERYTHING in it except the SD card itself. Now flash the rom you want to flash.
posting & replying via the XDA Premium app.

Yes Sir!
arozer said:
Next time just update your same post or make a thread of your own. No sense of posting your problems in someone's else's problems thread. But I'm glad it's working for you now.
[Update]
Just d/led and flashed CM7 using ClockwordMod. Everything seems to be working fine.
I don't know what's going on anymore.
I am going to try to flash BOS Royal Liquid again and see what happens.
Click to expand...
Click to collapse
Sent from my PC36100 using Tapatalk

dougjamal said:
Make sure your device still displays "S-OFF" in the bootloader screen. Reflash amon RA or flash amon RA v2.3 and then go to the wipe menu and wipe EVERYTHING in it except the SD card itself. Now flash the rom you want to flash.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
In the bootloader, my info reads:
SUPERSONIC EVT3 SHIP S-OFF
HBOOT-2.10.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.11.19
Oct 15 2010, 12:07:00
Not sure if any of that means anything.
Also, I tried that, and nothing! =[
-D/led Amon_RA v2.3 from his post. Flashed it using Terminal Emulator.
-Flashed Calkulin's Format ALL
-Wiped everything but "SDCARD" and "SDCard:.android_secure"
-Flashed ROM BOS.. and same thing; bootloop...
One thing I noticed is that when I try to Wipe Dalvik Cache in Amon-RA, it says:
"Formatting DATA: dalvik-cache...
Formatting CACHE: calvik-cache...
Skipping format SDEXT:dalvik-cache...
DALVIK-CACHE: wipe complete!"
That 3rd line kinda has me worried.. I don't think I ever seen that before.
And when I try to Wipe Dalvik-Cache in CWM, it gives me:
"E: unknown volume for path [/sd-ext]"
even BEFORE I select "yes" from the menu.
Once I select "yes".. IMMEDIATELY it says "Dalvik Cache wiped."
I don't remember that either from my previous phones.
ALSO TRIED..
I just Flashed an older version of CWM(v2.5.0.7) that allows to flash Amend zips.
-Then tried wiping, and when I tried wiping "Dalvik-cache" this is what I got:
"E: Can't mount /dev/block/mmcblk0p2
(File exists)"
Could that be the problem?

[Another update..]
When I try to flash the Royal Liquid ROMS in CWM, it gives me an error saying something like:
"Cannot install because of Android 1.5 or something.
It was necessary to something something Android 3.0 Gingerbread" or something like that.
Does this mean I can only flash Gingerbread ROMS.. which is CM7 is the only one that works?

The error when trying to flash the BOS rom is because of how it is packed. A lot of people still like to packages their ROMs using an older way that I guess google and Kush are wanting to phase out. It should flash ok with clockwork 2.5 or Amon RA's.
With the reboot issue it sounds like something may have gotten corrupted on your phone. If you still have the autoroot folder on your computer try making a backup on just your Data and .android partitions, and then run the FlashZip script that comes with autoroot and use it to flash the PC36IMG_SprintLovers...zip. That one should give you a clean flash that you can work from. It may be a good idea to mount your sd card as a disk drive and scan it for errors too, a corrupt sd card can do all sorts of weird stuff.

xHausx said:
The error when trying to flash the BOS rom is because of how it is packed. A lot of people still like to packages their ROMs using an older way that I guess google and Kush are wanting to phase out. It should flash ok with clockwork 2.5 or Amon RA's.
With the reboot issue it sounds like something may have gotten corrupted on your phone. If you still have the autoroot folder on your computer try making a backup on just your Data and .android partitions, and then run the FlashZip script that comes with autoroot and use it to flash the PC36IMG_SprintLovers...zip. That one should give you a clean flash that you can work from. It may be a good idea to mount your sd card as a disk drive and scan it for errors too, a corrupt sd card can do all sorts of weird stuff.
Click to expand...
Click to collapse
Just tried it. Same thing bro.
What I did:
-Backed up CM7 in CWM.
-Flashed Amon_RA v2.3 via Terminal Emulator
-Backed up data and .android partitions in recovery
-Restarted phone and ran "FlashZip", chose Option 1 "SPrintLover....zip"
-Flashed it successfully.
-Restarted phone to make sure it works. Went back into recovery and wiped everthing (factory reset, cache, dalvik cache and data), also flashed "Format All"
-Tried flashing BOS and bootloop again.

arozer said:
Just tried it. Same thing bro.
What I did:
-Backed up CM7 in CWM.
-Flashed Amon_RA v2.3 via Terminal Emulator
-Backed up data and .android partitions in recovery
-Restarted phone and ran "FlashZip", chose Option 1 "SPrintLover....zip"
-Flashed it successfully.
-Restarted phone to make sure it works. Went back into recovery and wiped everthing (factory reset, cache, dalvik cache and data), also flashed "Format All"
-Tried flashing BOS and bootloop again.
Click to expand...
Click to collapse
Have you tried pulling your sd card to see if that could be doing it?
Sent from my PC36100 using XDA Premium App

xHausx said:
Have you tried pulling your sd card to see if that could be doing it?
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
I'm sorry, I don't know what you mean by "pulling the sd card". Care to elaborate?
Also an update:
While trying to get BOS to work, I was stuck in bootloop.
So I reflashed it again without wiping anything.
It bootlooped 4 times and then PHONE TURNED ON!! Using BOS rom.
However, same as MIUI, about 10 secs into it, the phone freezes and restarts.
What do you think it could be?
MIUI does the same thing, except the whole bootloop trial.

arozer said:
I'm sorry, I don't know what you mean by "pulling the sd card". Care to elaborate?
Click to expand...
Click to collapse
Try pulling the sd card out of the phone to see if anything changes. You can find it under the battery.
Sent from my PC36100 using XDA Premium App

xHausx said:
Try pulling the sd card out of the phone to see if anything changes. You can find it under the battery.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Lol. Wow bro, way to put it like that and make me feel silly.
I thought maybe "pulling the battery" has a different means in terms of rooting.
And yes, I re-flashed BOS and powered the phone off,
-removed SD card
-Restarted and again, stuck in bootloop.
Btw, did you see my update in my previous post?
Also, I thank you VERY much for taking your time to try and help me.
Seems like only Gingerbread based roms (like CM7) are working. I haven't tried any other ones, other than Sprint Lovers and CM7, but they seem to work perfectly fine without ANY problems.

Have you tried:
Pulling the battery, going back to recovery and wiping dalvik and cache again then rebooting (sorry if I missed you doing this)
or
Re-downloading the BOS ROM, could be a bad download, esp if downloaded from your phone
or
Flashing a completely different ROM like Unleashed, Myn, EViO or MikFroyo?

Sorry, didn't mean for it to come across like that. It's possible there is just something about that ron that doesn't want to work with your phone.
If you want to send me the logcat I can take a look at it for ya.
Sent from my PC36100 using XDA Premium App

jstalford said:
Have you tried:
Pulling the battery, going back to recovery and wiping dalvik and cache again then rebooting (sorry if I missed you doing this)
or
Re-downloading the BOS ROM, could be a bad download, esp if downloaded from your phone
or
Flashing a completely different ROM like Unleashed, Myn, EViO or MikFroyo?
Click to expand...
Click to collapse
Yes. Just tried that brother and doesn't work. (referring to 1&2)
I will try downloading another rom now.
Hopefully BOS and MIUI are just having their own problems, as CM7 works just fine.
xHausx said:
Sorry, didn't mean for it to come across like that. It's possible there is just something about that ron that doesn't want to work with your phone.
If you want to send me the logcat I can take a look at it for ya.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Where do I find the logcat? Sorry.. just don't to send you the wrong one.

Spiicytuna said:
Option #1
1. Download aLogcat from the market
2. Launch the aLogcat
3. Go launch the program thats crashing, allow it to crash
4. Go back to aLogcat
5. Menu -> Send
6. Email it to yourself, then post it on here for shinzul/toast + thread
Option #2
1. Hook your phone to your computer with the usb cable
2. With your fav CLI type: "adb shell logcat > crashlog.txt" (w/o the " ")
3. On the EVO launch the program that's causing problems, allow it to crash
4. In the CLI hit "crtl+c" (to stop the logging process)
5. In the same folder as adb will be a text file called "crashlog.txt"
6. Post it on here so that shinzul/toast + thread can take a look at it
Option #3
1. open terminal on your phone
2. if the character showing is a '$' type "su"
3. type "locat > /sdcard/logcat.txt"
4. post the logcat.txt file on your SD card on here so that shinzul/toast + thread can take a look at it
Click to expand...
Click to collapse
Instructions on how get a logcat

Issues with flashinf roms

I'm having issues with flashing roms, in clockworkmod after i clear davilk cache/cache/data i go to install roms skyraider 4.0 and incubus stock 2.0 sense and OptimizedZ by newtoroot i keep getting "Installation aborted bad" whats causing this to happen i'm running warmZ twopointtwo and i can re install that one along with the nighlies could it be that i'm running WarmZ twopointtwo also i'm running clockworkmod 2.5.1.2 the error is
" E:cant open/sdcard/ROM i'm trying to install.zip
(bad)
Instalation Aborted
I got it fixed i just went out and bought a new sd card.

Do you have enough free space on your SD card?

Yes I do i hope i do anyways i have 25.00gigs

Do you do factory data reset/clear cache/ clear dalvik? Are you using cwm 2.###? Do you wipe first with cwm3 then cwm? You really shouldnt have this much problems , you may want to go back to complete stock. Are you downloading roms to pc then transfering? Maybe files are corrupted. Thats about all i can tjink of. I dl roms directly from phone, then reboot to recovery to install. Never use rom manager.
Sent from my Incredible using XDA App

donnyp1 said:
Do you do factory data reset/clear cache/ clear dalvik? Are you using cwm 2.###? Do you wipe first with cwm3 then cwm? You really shouldnt have this much problems , you may want to go back to complete stock. Are you downloading roms to pc then transfering? Maybe files are corrupted. Thats about all i can tjink of. I dl roms directly from phone, then reboot to recovery to install. Never use rom manager.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
I clear dvlik cache/cache/data and i'm using clockworkmod version 2.5.x.x i will not use 3.0 and im downloading roms to pc and then flashing and i wont touch rom manager and when i download from the phone i keep getting no enough freespace i think its trying to save it to the phone or something and not the sd card.

It would help if you would create full sentences with proper grammar and spelling... It only adds to the confusion to what your problem actually is. Try re-downloading the ROM. If it doesn't work again, try upgrading CWM, you can always downgrade it later if you need/want to. As donny said, the file may have been corrupted, I had this happen to me the very first time I tried flashing a custom ROM. I re-downloaded it, and re-copied it onto my phone and that seemed to work for me.

[Q] RandomRom Hawk 2.3.4 flashing questions

I have been trying for the past 3 hours to flash this ROM correctly. I've tried odining the eg22 deodexed modem, converting to ext4, enabling journaling, flashing the eg22plus kernal, odining the eg22 modem, wiping 3x data,cache, and dalvik cache in all sorts of combinations. I just get the Samsung logo with vibrations after flashing the rom. Does any one have any ideas of what's causing this? Also, after restoring a backup of RandomRom Osprey, I'm receiving Google Framework errors nonstop. I am not new to flashing, but stumped on this one. I'd be grateful for any ideas. Thank you.

When you say "I've tried odining the eg22 deodexed modem, converting to ext4..." did you mean to say modem or rom?
If you're starting off by odining stock eg22 rom then everything sounds right. If not, that should be your first step.
Maybe skip journaling and do it later? Or do the modem before anything else.

xhitman88x said:
I have been trying for the past 3 hours to flash this ROM correctly. I've tried odining the eg22 deodexed modem, converting to ext4, enabling journaling, flashing the eg22plus kernal, odining the eg22 modem, wiping 3x data,cache, and dalvik cache in all sorts of combinations. I just get the Samsung logo with vibrations after flashing the rom. Does any one have any ideas of what's causing this? Also, after restoring a backup of RandomRom Osprey, I'm receiving Google Framework errors nonstop. I am not new to flashing, but stumped on this one. I'd be grateful for any ideas. Thank you.
Click to expand...
Click to collapse
Have you partitioned your sd card yet? When I flashed this rom on my phone, I already have a partitioned sd card and everything went great. When I flashed it on my wifes phone, she did not have a partitioned sd card, and I had the same problem you described above. You have to partition the sd card because you need a separate partition for rfs and for ext4. All I did was partition the sd card and everything worked great. Let me know if that works for you.

update
Thanks for replies. Yes, I meant to say I flashed the eg22 rom, but it was the deodexed version. Should I have done stock? Also, my sd card is partitioned already. I appreciate the responses again.

xhitman88x said:
Thanks for replies. Yes, I meant to say I flashed the eg22 rom, but it was the deodexed version. Should I have done stock? Also, my sd card is partitioned already. I appreciate the responses again.
Click to expand...
Click to collapse
I've modified/updated the install instructions. Try this with Option A:
How Do I Use This ROM?​
How To Install RandomROM:
Pre-Steps:
Option A: Odin the .tar for EC05 deodexed EXT4.
Option B: Use one-click to root nearly any current setup with EXT4.
Option C: Already on an EXT4 setup? You're good to go, proceed.
Steps:
A clean install is recommended (Wipe 3X).
Ensure that your phone is on CWM 3.1.0.1 (Purple).
Odin a Gingerbread modem such as EE03, EF02, or EG22.
Flash RandomROM Alpha "Hawk".
Enjoy

resolved
wow i got a response from the king himself haha..will test it after work today and post a reply..thanks for taking your time out to help me with this..i like this rom and it's worth the trouble
i put the title as resolved because i have a feeling this will work lol

no-go
still a no-go =(
i followed the instructions to the t ..not sure why hawk won't flash
well, im on osprey at the moment and i'm happy with it..

xhitman88x said:
still a no-go =(
i followed the instructions to the t ..not sure why hawk won't flash
well, im on osprey at the moment and i'm happy with it..
Click to expand...
Click to collapse
I flashed Hawk directly over Osprey, just wiped partition cache and dalvik then flashed the rom zip.
Been running awesome.

Failed to move application. Not enough memory
I'm currently running the RandomRom Hawk 2.3.4 but four of my apps won't move to the sd card. It keeps saying failed to move application, not enough memory and it clearly shows that I have enough memory. Have anybody ran into this problem?

[Q] help with flashing Blazer 4.0

Hey all. today I decided to try the blazer 4.0 rom. Im currently on Senzation 2.3 . I followed the instructions completely but the phone got stuck on the galaxy logo screen after rebooting. It would not boot into recovery either. I had to go into download mode and use odin to get it working again. can someone please help me out? would it be an issue with the kernel? Im attaching a screen shot so hopefully it would help. Any kind of help, suggestions, flaming or trolling is much appreciated!!!

Make sure you follow the install instructions in Blazer's OP. My experience with fresh Blazer installs:
-Nandroid
-Wipe /system, /data, /cache
-Install Blazer ROM
-Reboot and let phone site for 10 minutes
-Reboot recovery and install kernel of choice (if different from packaged Blazer kernel)
-Reboot
Good luck. Feel free to poll the large user community for help in the Blazer ROM thread in the Dev section

Make sure you are NOT flashing with the hitman touch recovery that has given allot of people problems including myself.

rbtrucking said:
Make sure you are NOT flashing with the hitman touch recovery that has given allot of people problems including myself.
Click to expand...
Click to collapse
Hi. No Im not running Hitman. I followed his post exactly. I guess i will try it again today after work. I will let you know how it went.

nibrwr said:
Make sure you follow the install instructions in Blazer's OP. My experience with fresh Blazer installs:
-Nandroid
-Wipe /system, /data, /cache
-Install Blazer ROM
-Reboot and let phone site for 10 minutes
-Reboot recovery and install kernel of choice (if different from packaged Blazer kernel)
-Reboot
Good luck. Feel free to poll the large user community for help in the Blazer ROM thread in the Dev section
Click to expand...
Click to collapse
Hi. Your procedures are just like what i did but no dice for me. will trying doing it again today. Thank you for your help.

If you have not flashed EL29 modem, do so... Then follow steps. After Manuel wipe, I would flash format all zip too. Btw, first boot could take up to 5mins...

I have the same problem when I went from blazer 3.8 to blazer 4.0. It just won't boot pass the galaxy logo. I have since flash a couple if different recoveries (cwm,rogue,etc). I was finally able to make it work blazer 4.0 with I've of them recoveries (but I forgot which one). Only problem now is that it won't work with the blazer 3.8 ROM.
I like the Blazer roms but they are very tricky/troublesome to flash. I don't have a problem with any of the recoveries with the other roms.

Blazer rom install
I've been using Rogue Recovery 1.1.2 (CWM v5.o.2.7) flash blazer roms 3.7. to 4.0 with out a problem also Caulkins roms might try that if your on a different version.

If you get stuck on SGS2 screen after flashing the new ROM, reboot to recovery (volume up + power). Flash the ROM again without wiping anything, then reboot.

shahin26 said:
Hey all. today I decided to try the blazer 4.0 rom. Im currently on Senzation 2.3 . I followed the instructions completely but the phone got stuck on the galaxy logo screen after rebooting. It would not boot into recovery either. I had to go into download mode and use odin to get it working again. can someone please help me out? would it be an issue with the kernel? Im attaching a screen shot so hopefully it would help. Any kind of help, suggestions, flaming or trolling is much appreciated!!!
Click to expand...
Click to collapse
You're flashing calkulins format all zip, after wipe, and before flashing the rom....right?

1brainsurgeon said:
You're flashing calkulins format all zip, after wipe, and before flashing the rom....right?
Click to expand...
Click to collapse
I didn't flash calkulins format all zip at first, just did nano, wipe and flash and I was running into the same issue. I finally did a complete format, then flashed calkulins format, then flashed Blazer..worked perfect.

I can Only go into download mode after flashing blazer. it will not let boot into recovery at all.

shahin26 said:
I can Only go into download mode after flashing blazer. it will not let boot into recovery at all.
Click to expand...
Click to collapse
Yeah that happens to me too. You have to use odin to flash a recovery tar file to the phone. I use the cwm 5.0 tar file.

Hi guys, I have one question. When flashing the rom, should I select wipe data/factory reset option before flash calkulins format all zip or just flashing calkulins format all zip is going to be enough? Also, should I select wipe cache partition option too? I am on stock and this is gonna be my first rom.

Unable to flash ICS..please tell me its not just me

Damn I was hungry for some ICS! lol
I just download the new CM9 and put it on my internal sd card. Okay, used chris's stock el26 kernel(flashed zip in cwm then rebooted recovery) but when I go to flash the CM9 zip in cwm, I get a bunch of nonsense.
"getprop("ro.product.device") == "GT-I9100T" || this is repeated over and over, then it says error in [folder where i put the ROM zip]
I have flashed ICS before, in fact i have flashed Blend ICS and Calk ICS just to test this issue with no problems right now. I also tried AOKP and it also failed
I'm out of ideas here. Please help.

Have you used caulks format all before flashing tocm9

igerald904 said:
Have you used caulks format all before flashing tocm9
Click to expand...
Click to collapse
Yes, I have. It has worked before so that's why it seems strange.
If all else fails, I guess I will just have to go with a completely stock wipe(sfhub) then

I think that would be the best suggestion actuall, let me know if that works maybe i might try it I'm running fc24 and was thinking about doing cm9 by installing el26 tar then running that

It could've been a bad download; use an md5 checker.
What I do is use sfhub's el29 one click package, then use his autoroot package to flash el26 cwm. Set up GPS test and get a lock, then reboot into recovery, follow the directions, and I flash the rom twice.
By using sfhub's solutions, you avoid getting the yellow triangle and adding to the download count.

Sound like a plan

thegoodrat said:
Damn I was hungry for some ICS! lol
I just download the new CM9 and put it on my internal sd card. Okay, used chris's stock el26 kernel(flashed zip in cwm then rebooted recovery) but when I go to flash the CM9 zip in cwm, I get a bunch of nonsense.
"getprop("ro.product.device") == "GT-I9100T" || this is repeated over and over, then it says error in [folder where i put the ROM zip]
I have flashed ICS before, in fact i have flashed Blend ICS and Calk ICS just to test this issue with no problems right now. I also tried AOKP and it also failed
I'm out of ideas here. Please help.
Click to expand...
Click to collapse
do a double flash. sometimes the first flash doesn't go thru.

Install guide says to wipe data/ cache then flash cm9 from el26. I would redownload and md5 check also. Might try coming from cm7 or miui also as there recovery works for cm9
Sent from my Epic zipper

darkfire2024 said:
It could've been a bad download; use an md5 checker.
What I do is use sfhub's el29 one click package, then use his autoroot package to flash el26 cwm. Set up GPS test and get a lock, then reboot into recovery, follow the directions, and I flash the rom twice.
By using sfhub's solutions, you avoid getting the yellow triangle and adding to the download count.
Click to expand...
Click to collapse
Why does everything say to use the el26 cwm? Is there something wrong with the el29 cwm or am I missing something?
Sent from my SPH-D710 using Tapatalk

You must flash from EL26, locate StockCWM-EL26.tar and odin that. Then reboot to recovery. Flash update*.zip and gapps*.zip after wiping cache and data.
---------- Post added at 07:55 AM ---------- Previous post was at 07:49 AM ----------
Sn1per 117 said:
Why does everything say to use the el26 cwm?
Click to expand...
Click to collapse
I keep a copy of LoSTkernel on my sd for the recovery, it's EL29 and I just tried this with that and got the same results. Came, read, and came to the conclusion EL26 is the most stable for flashing ICS.

thatdudepoops said:
Might try coming from cm7 or miui also as there recovery works for cm9
Sent from my Epic zipper
Click to expand...
Click to collapse
This is what I ended up doing next right after I posted this thread lol
Flashed MIUI 2.3
Rebooted Recovery
Flashed CM9
Success!
I kept flashing cm9 and wiping everything but it never did work, strange.

Yea you have to be on a gingerbread based ROM like cm7 then install el26 and flash cm9
Epic touch phone of xXHELLBoy91Xx

thegoodrat said:
This is what I ended up doing next right after I posted this thread lol
Flashed MIUI 2.3
Rebooted Recovery
Flashed CM9
Success!
I kept flashing cm9 and wiping everything but it never did work, strange.
Click to expand...
Click to collapse
Glad you got it working, also after you flash your last step should of been to wipe data/factory reset. This will ensure a clean start and possible removal of all potential bugs...