[Q] Hboot version Gingerbread Bootlooping - EVO 4G Q&A, Help & Troubleshooting

I want to try RC1 of CyanogenMod. However, every time I have tried a GB ROM I get a bootloop (well actually just the tap here to begin android guy that I can't get past) after flashing gapps. I feel like a nub but is there any correlation between my Hboot (.93) and this not working? I have never upgraded my radio (2.15.00.07.28), Hboot, Recovery (clockworkmod 2.6.0.1) or anything else. I do a full data wipe, Dalvik wipe, and cache wipe after doing a nandroid but the same thing happens with every GB ROM. Is there anything that I need to do differently, or upgrade? Also, where can I find the correct gapps for CM7 RC1?

bump. This is probably a stupid question. Could someone take the time to correct or explain this to me?

Related

Flashing a Sense ROM after flashing CM6.1.1

I'm really enjoying CM6.1.1, however I'd like to update my PRL and the only way to do that is to NANDroid backup CM and flash a Sense based ROM.
I did the backup, downloaded Fresh ROM, did a full wipe and even did a separate Cache wipe and then Dalvik Cache wipe. Then I flashed Fresh. The installation goes fine and I reboot.
I hit the white HTC Evo 4g splash and that's it... it just hangs for more than 5 minutes I've waited. I did a battery pull and booted again and it would just hang. Then I did a full wipe, cache wipe and dalvik wipe and rebooted, still just hanging.
I thought I might have gotten a bad download so I tried MYNs warm 2.2 just in case and the same deal.
Is there something that's done to the phone after CM6.1.1 is installed that prevents a Sense ROM from booting up?
thanks for any help!
danootz said:
I'm really enjoying CM6.1.1, however I'd like to update my PRL and the only way to do that is to NANDroid backup CM and flash a Sense based ROM.
I did the backup, downloaded Fresh ROM, did a full wipe and even did a separate Cache wipe and then Dalvik Cache wipe. Then I flashed Fresh. The installation goes fine and I reboot.
I hit the white HTC Evo 4g splash and that's it... it just hangs for more than 5 minutes I've waited. I did a battery pull and booted again and it would just hang. Then I did a full wipe, cache wipe and dalvik wipe and rebooted, still just hanging.
I thought I might have gotten a bad download so I tried MYNs warm 2.2 just in case and the same deal.
Is there something that's done to the phone after CM6.1.1 is installed that prevents a Sense ROM from booting up?
thanks for any help!
Click to expand...
Click to collapse
No sometimes recovery doesn't wipe everything correctly... downlload caulks format all and then flash sense rom. Should fix your problem!!
Sent from my PC36100 using XDA App
!!
I think i figured out what the problem is.
I flashed the latest radios, that is, i flashed the leaked ones (ending in .19 i think)
So I don't any of the roms i was trying to flash were compatible with the new radio.
At least that's what I read in some forum.
After nandroid backing and restoring and wiping things multiple times, i'm too lazy to try flashing an older radio so i might just wait till a new ROM based on 3.70 comes out.
danootz said:
!!
I think i figured out what the problem is.
I flashed the latest radios, that is, i flashed the leaked ones (ending in .19 i think)
So I don't any of the roms i was trying to flash were compatible with the new radio.
At least that's what I read in some forum.
After nandroid backing and restoring and wiping things multiple times, i'm too lazy to try flashing an older radio so i might just wait till a new ROM based on 3.70 comes out.
Click to expand...
Click to collapse
radios have nothing to do with it. they base roms off new ota so that you can get the benefits of the changes not the radios. You can flash the original radio that came with the evo and it would not affect the rom. The radio controls your signal strength and wimax strength. which is why there is a thread with all the different radios because each phone reacts different to each radio.....

[Q] Cyanogen Wiping Incorrectly

I don't know whats going on with my slide. Whenever i do a wipe in recovery and install a cyanogen mod. It will still have the gapps installed even though i know it shouldn't since i have to flash them separately. Not sure why it doesnt seem to be wiping the phone correctly...any ideas?
yajinni said:
I don't know whats going on with my slide. Whenever i do a wipe in recovery and install a cyanogen mod. It will still have the gapps installed even though i know it shouldn't since i have to flash them separately. Not sure why it doesnt seem to be wiping the phone correctly...any ideas?
Click to expand...
Click to collapse
Why are you trying to wipe gapps?
Gapps are in /system/app. When you wipe, you're wiping /data and /cache. Therefore, even though you flashed them separately, they are still there.
Thank you for that bit of info. I want to wipe everything as much as possible because i am having trouble getting a theme to work. when i apply it it just causes my phone to loop. When i would reflash 6.1.1 on my phone i assumed it would remove the gapps. When i would reflash cyanogen on my G1 it would do that making me have to reflash gapps, so i assumed my slide would do the same...
This was the theme i was trying to give a try:
http://forum.xda-developers.com/showthread.php?t=865638
VatExpresso
Also just to double check. Because we dont have S-Off we cant use metamorph?
yajinni said:
Thank you for that bit of info. I want to wipe everything as much as possible because i am having trouble getting a theme to work. when i apply it it just causes my phone to loop. When i would reflash 6.1.1 on my phone i assumed it would remove the gapps. When i would reflash cyanogen on my G1 it would do that making me have to reflash gapps, so i assumed my slide would do the same...
This was the theme i was trying to give a try:
http://forum.xda-developers.com/showthread.php?t=865638
VatExpresso
Also just to double check. Because we dont have S-Off we cant use metamorph?
Click to expand...
Click to collapse
You cant use MM b/c of no S-OFF and you can use the wipe option in clockwork by going to partitions...From there you can wipe /system and other parts.
Also, you can't just use themes for other devices, because the framework-res.apk is device specific, which is why you're having issues.
All you have to do is reflash CM, and then Gapps, and you'll be fine. You don't even have to wipe.
Sent from my T-Mobile myTouch 3G Slide using XDA App

ClockworkMod 3.0.0.5 not fully wiping?

I upgraded to the latest clockworkmod 3.0.0.5 and when I switch ROMs, I notice some of my item's are still "cached". For example, I was using Evervolv and then did a wipe of data, cache, and davlik, and flashed the RC1 for CM7. GApps are not packaged with either of these ROMs but when I booted up CM7 for the first time after flashing, GApps are installed, without me doing so. Is there an issue with the latest version of deleting cache or am I not doing enough wiping?
I am running into exactly the same problem. Works fine for flash over but the minute you choose wipe in ROM Manager of do a data wipe in recovery it does not make any difference. Not sure it is clearing anything in cache or data or at least consistently.
None of the other ROM devs have posted this so I am not sure what is going on
I am still messing with it
EDIT: You may want to post this in the ROM thread also so the devs are aware
i had the same problem.. From what i have been ready downgrade to cwm 2.5.1.2 and it should help..it did for me. the new cwm isnt running as good with some of the roms out there.

MIUI - stuck on bootloader

so im trying to get MIUI on my evo, but when i flash it it sticks at the sprint bootloader. i got the rom from MIUI. anyone help?
Did you wipe everything before flashing? Have you tried other kernels?
i have wiped data and cache. and im sorry but im new at this, what is a kernel
first of all, try also wiping data ( i kno its hard, just back up with titanium backup), system, boot, and battery stats. that should boot right up.
Did you wipe dalvik? You need to wipe data/cache/dalvik when switching ROMs.
If you don't know what a kernel is then I HIGHLY suggest you spend a little time reading up on all this because that is Android 101. You should have known what a kernel is before attempting to flash anything. A kernel is basically the interface between the software and hardware of your phone. It has all the drivers and instructions that tell your hardware what to do. They are flashed the same way ROMs are flashed and can affect performance dramatically. Different kernels perform differently on different EVOs so you need to find one that works well for your device. Sometimes the kernels that come packaged with ROMs don't work well on some EVOs and can cause booting and performance problems.
Mas wipey before flashy! Wipe all data, save for sd card, twice before flashing this rom. The savaged kernel that comes with the rom is just fine. Also, I would avoid titanium backup like the plague, especially if you are going to use MIUI.
Swyped from my CM7 EvO

[Q] Boot Fail after Custom ROM

I have a Samsung Galaxy Nexus GSM and have been trying to install the Paranoid Android flavor custom ROM, I had 2.22 installed not long ago but managed to screw it up when I updated it without clearing my security settings (I had a 4x4 pattern swipe which I couldn't enter with the update which restored it to 3x3 pattern) so I wiped and restored to stock 4.2. I'm now trying to re-install with any custom ROM but it's not working.
Whenever I install a ROM it seems to install ok but when I get to the boot screen it just hangs on the nexus/PA logo.
I've tried with:
Goo Manager
TWRP 2.2
TWRP 2.3
CWM 6.0.1.5
and with
PA 2.22
PA 2.99.1
PA 2.99.5
PA 2.99.6
PA 2.99.7
and I always get the same error, I've tried wiping all options within TWRP and CWM and going from there but that doesn't seem to work, the strange thing for me though is that if I re-install a stock Google ROM it works perfectly fine.
I'm fairly new so please be gentle.
flash the latest twrp and move the rom and gapps to your sdcard then follow this..
1. factory reset
2. wipe system
3. wipe cache
4. wipe dalvik
5. flash rom
6. flash gapps
7. reboot
if it still freezes at boot animation pull battery reboot to recovery wipe cache/dalvik and reboot
Thanks for the suggestion but that didn't work.
Any other suggestions?
When you say TWRP 2.3 do you mean 2.3.2.1? http://teamw.in/project/twrp2/90
Clockwork 6.0.1.5 is also outdated, newest is 6.0.1.9.
You need to update your recoveries for Android 4.2.X which is what PA 2.99 is based off of.
zephiK said:
When you say TWRP 2.3 do you mean 2.3.2.1?
Clockwork 6.0.1.5 is also outdated, newest is 6.0.1.9.
You need to update your recoveries for Android 4.2.X which is what PA 2.99 is based off of.
Click to expand...
Click to collapse
Yes I did mean 2.3.2.1, I wasn't sure what the whole version number was at the time and I was halfway through resetting up stock on my phone at the time so I didn't bother to check exactly. sorry about that.
Is there a way to completely wipe everything on the phone so that it is bare stock? I was just wondering if I would be able to start from a clean phone if it would make any difference. I'm aware of cache/delvik cache/internal storage/(i think it's called "system partition" or something like that).
Using TWRP, wiping cache, dalvik, and system should wipe everything except the sdcard contents. So doing these wipes should make your phone "bare stock" again as you described
Why don't you try downloading another custom ROM or download the same ROM again because maybe it is corrupted or something
osiris231 said:
Yes I did mean 2.3.2.1, I wasn't sure what the whole version number was at the time and I was halfway through resetting up stock on my phone at the time so I didn't bother to check exactly. sorry about that.
Is there a way to completely wipe everything on the phone so that it is bare stock? I was just wondering if I would be able to start from a clean phone if it would make any difference. I'm aware of cache/delvik cache/internal storage/(i think it's called "system partition" or something like that).
Click to expand...
Click to collapse
RANT: huh..... seriously? you couldn't have browsed around, searching for this COMMON issue (which usually comes down to user "error"), read the STICKIES, before posting?
first, internal storage = /data/media aka /storage/sdcard0/ aka /sdcard/
Please read all of this
http://forum.xda-developers.com/showthread.php?t=1626895

Categories

Resources