Related
I haven't found any solution with this. About 3 or 4 weeks ago my Evo went crazy so I rebooted and was missing many apps. I did a nand to another sense rom and every time I tried to install an app (either download or from sd card) it would reboot. The odd thing is, it only does it with sense roms. I can use CM 6 or 7 fine and install whatever I want. I was originally one Myn's rls5, I also tried the Fresh roms. I have non clue what's causing this, tried googling and all said clear the market cache or try an older market, which I've done both. Any help would be greatly appreciated.
tricky one. have you tried flashing a stock sense rom, and seeing how things work for you there?
Don't use a backup. Flash a sense ROM and install everything manually.
Sent from my PC36100 using XDA App
shogun26 said:
tricky one. have you tried flashing a stock sense rom, and seeing how things work for you there?
Click to expand...
Click to collapse
I haven't tried a stock rom yet, once I get things back up I'll find one and try it.
gqstatus0685 said:
Don't use a backup. Flash a sense ROM and install everything manually.
Click to expand...
Click to collapse
I can't install anything. period. as soon as I try to install any apk from my sd card or anything from the market that doesn't come installed in the rom, as soon as it "finishes" the installation part it will reboot, but not a full reboot, it will go out to the boot screen (but not all the way to the htc screen).
Since going from AOSP to Sense what was your procedure for flashing? Just want to make sure your starting with a clean slate.
- What steps to you take?
- Full wipe? Data, cache, sd-ext?
- SD format?
The more info you can give the better and maybe we can help you track it down.
Ive done the standard full wipe, data, cache, dalvik. I do that everytime between roms. Not sure what the ext does and in haven't formatted my sd card since then
Sent from my PC36100 using XDA App
Update - I flashed the stock rooted 3.70 and was able to install. This was after formatting my sd card. Then tried to flash Myn's rls5 again and had the same problems as before. Only difference is with the 3.70 I forgot the flash the radios, but still had a fine signal. I flashed the radio updates with Myn's. Any help/advice is greatly appreciated.
At this point all I can think of doing is unrooting your device and getting it completely back to stock, then try re-rooting and make a nandroid of your rooted, stock sense rom.
Maybe you can root through a different methods than what you did originally.
After that, try another sense rom, make sure the md5 checks out too.
Sent from my PC36100 using XDA App
What recovery are you using and what version? I thought there were known issues with ClockWork 3.x.x.x version of recovery not wiping cache correctly? If you are using ClockWork you might want to try switching to Amon_RA 2.2.1. to see what happens. There is also a zip floating around (which I have attached) that can be used to wipe everything, you may want to give that a shot then reinstall the ROM. I have not used this zip, so use it at your own risk as I cannot guarantee the results. I have read about others using this and it working just fine.
I've had this phone for a about a month, and decided to get adventurous - should have left it alone.
I ran unrevoked the day I got the phone and decided to try cyanogem - it didn't work, got stuck on splash screen so I recovered my stock backup. I read in the developers forums about needing flash a new bootloader and use amon-ra instead of clockwork to load cyanogem.... I got the PC36IMG from the forum here
http://forum.xda-developers.com/showthread.php?t=764062&page=2
I've been stuck in boot loop since then.
I have followed all of the suggestions for those stuck in bootloop in the thread, (including both versions of the PC36IMG and no luck...
I went as far as running unrevoked forever again, in the hopes that it would put it back to the way it was before I flashed the file from the post.
I can get into recovery, and the hboot version is 2.02
none of my backups will install ( error 7), and the cyanogem 7 nightly will not load.
I am 350 miles away from home for the next two weeks and can't call home
to recap
1) unrevoked forever - ok
2) tried to flash cyanogem7 - got stuck in bootloop
3) flashed clockwork - ok
4) recovered backup - ok
5) flashed PC36IMG from above thread - stuck in bootloop wont load rom
6) flashed alternative PC36IMG from above thread - stuck in bootloop wont load rom
7) flashed clockwork again - ok
8) tried to restore backup - error 7
9) flashed mtd-eng.zip (from xda) - hboot .76 - hboot version on phone did not change
10) flashed mtd-eng.zip (from xda) - hboot .76.200 - hboot version on phone did not change
11) unrevoked forever - completed but still stuck in bootloop/recovery
10)
7) flashed clockwork again - ok
I really don't know where to go from here, and everything I try from the xda forums doesnt work. Any help with this will be deeply appreciated..
Start fresh ,get calkulins wipe all and then flash it and then flash a rom and start from there
Sent from my PC36100 using XDA App
Thanks
a few more questions...
where do I get caulkins wipe all?
do I need to backup my roms on my computer?
will I loose my 4g keys?
Thank you.
luckyhubby said:
a few more questions...
where do I get caulkins wipe all?
do I need to backup my roms on my computer?
will I loose my 4g keys?
Thank you.
Click to expand...
Click to collapse
http://www.mediafire.com/?ikylelx99c49133 There ya go.
It is always a good idea to backup your rom, and espciallu your wimax. And using the format all won't kill your 4G keys.
wimaxx?
Again noob here... srry...
I assume backing up my roms would just be copying them from the sd card, but the wimax is something I haven't run across yet. How do you back that up?
luckyhubby said:
Again noob here... srry...
I assume backing up my roms would just be copying them from the sd card, but the wimax is something I haven't run across yet. How do you back that up?
Click to expand...
Click to collapse
Well you backup the rom that way, but when someone says "backup your rom" they mean you boot into recovery and select back, and it backups your system image, and you can restore it if something goes wrong.
clockwork recovery- selct backup/restore, select backup, and you're done
amon_ra- select backup/restore, select which items you want
Wimax is the official name for 4G, so if you hear wimax, they mean 4G. Clockwork backs up wimax automatically, and it can be extracted from the zip and copied if on a computer. On amon_ra 2.3 you have to physically select wimax and back it up, otherwise it can be lost.
I think I got it
so ... move calkulins to sd card
install from zip
flash backup
trying now
luckyhubby said:
so ... move calkulins to sd card
install from zip
flash backup
trying now
Click to expand...
Click to collapse
Well I would backup before flash, but you got it there.
Off topic,but teh roxx u still on cm7
Sent from my PC36100 using XDA App
backed up before I started this...
copying contents of sd card just in case...
Thanks... I will let you know in a few minutes how it went
davidc23 said:
Off topic,but teh roxx u still on cm7
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yes, that I am.
luckyhubby said:
copying contents of sd card just in case...
Thanks... I will let you know in a few minutes how it went
Click to expand...
Click to collapse
Format all only touches the system data, like the cache, ect. But its always handy to backup the contents every so often. And sound good, I'll be around.
didn't work
error while flashing boot image
I also tried to install CM7, that didn't go either - status 7
Awkward. let me see if I find it. But you can just click:
format data, wipe cache, and under advanced [if on clockwork] wipe dalvik, and it does the same thing. I've never used the format all zip and been just fine.
I am using clockwork, will try dalvic method
luckyhubby said:
I am using clockwork, will try dalvic method
Click to expand...
Click to collapse
Alright, so wipe data/factory restore, wipe cache, and then under advanced, wipe dalvik cache, and you'll be all set.
I'm sorry, but still sys error while flashing boot image....
I have 3 recoveries saved... will try the other two, as well as CM7
Well apparently it doesn't like the file. What exactly are you trying to do now, flasha new rom?
just get A rom to work..
the phone won't boot, I can only get it into recovery.
I started out trying to get CM7, but now I just want it to work. lol
Well try flashing the latest CM7 nightly. And to use that [CM7] you are on the 3.0+ version of clockwork?
Heres my situation...Im currently running MIUI 1.3.4 ROM. I finally decided to try out another rom so I choose Warm Two Point Two RLS 5. So I downloaded that as well as radio/wimax update zip that was said on thread to flash w/ rom.Heres EXACTLY wat I did: (1st) Did a Nandoid backup (2nd)did a full wipe...data/factory reset...cache...then dalvik (3rd) flashed Warm 2pt2 ROM (4th) in same recovery session wiped cache...then dalvik and flashed radio/wimax update(was told to wait for for radios to flash..would see little green arrow/phone icon which I did (5th) then I rebooted. So my problem is after doing all that it rebooted back to my MIUI rom and NO new rom was installed! Dont get what I did wrong! I hav not had problems flashing different kernels on the MIUI rom but struck out on starting with fresh install to change roms. So can anybody give me advice on this matter?
are you using clockwork? try RA.
Try it again. Or maybe try flashing the radios first, then the rom.
Flash calkulin's format all, then flash the radios, then myn's rom, then reboot. Nothing else, and do it all within one recovery session.
The format all will wipe all the things you did, plus system and one other. It's usually just a good idea to do whenever you switch actual rom's.
Sent from my hand with XDA Premium installed
yes I used unrevoked 3 to root my phone so im runnin clockwork. So if I wanted to change recovery...how wud I go about doin that?
It was said on the install instructions in the thread I got the warm's two point two rom from to flash rom first then radio/wimax update. Does it really matter or will I mess up my phone if I do it the other way?
jro73 said:
yes I used unrevoked 3 to root my phone so im runnin clockwork. So if I wanted to change recovery...how wud I go about doin that?
Click to expand...
Click to collapse
try clockwork again, except in your step (2) when you get to wipe dalvik hit yes, let it load, then hit restore boot at top....let it load, then when it returns to main, hit chose zip and flash...
..or in clockwork scroll down to alternate recovery...hit it should change to RA. MAY need to be the paid version i forget.
you could also do the other suggestions.
Edit...as for the updates it won't matter if the radios and ROM are up to date.
Well thts wat I mean as far as I kno Im not a sense rom if im runnin MIUI which is a AOSP rom. Thats why Im askin if flashing the radio/wimax update before the the Warm's rom wud do anything to my phone? I already hav the Calkulin's format all zip on my sd card so I will try tht but before I do I just need to kno if its ok to flash update before rom.
You are fine to flash the radio/wimax before flashing the rom.
Well I finally got the warms rom to flash. It ended up being a corrupted zip file on my sd card. So I deleted it and downloaded it again on my sd card then flashed...so everything is workin now....YEH!!!! Thanks everyone for the advice...much appreciated!
Glad you got it working...and that's the end of that chapter.
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
Everytime I install a custom rom on rom manager, it has corrupted my phone and each and everytime I'd have to restore it. Is there any way to fix it? I've seen comments on the custom roms and people have commented that it works fine on the DHD.
Hi drkhrsy
Kindly explain further by your meaning of corrupt? This would allow us here to clearly understand the problems you're facing. Thanks.
Well I first installed cyanogenmod 7 and that gave me the boot loop. After restoring the phone I thought I'd try another ROM, so I went to download the TB 7.0.3 ROM and that booted up the phone but I had constant popups on HTC sense force closing and couldn't do anything else so I had to restore the phone again. So yeh, I'm not really sure what I'm doing wrong here.
drkhrsy said:
Well I first installed cyanogenmod 7 and that gave me the boot loop. After restoring the phone I thought I'd try another ROM, so I went to download the TB 7.0.3 ROM and that booted up the phone but I had constant popups on HTC sense force closing and couldn't do anything else so I had to restore the phone again. So yeh, I'm not really sure what I'm doing wrong here.
Click to expand...
Click to collapse
Did you do a full wipe before flashing those roms, multiple fcs normally indicate that you didn't try a full wipe then reflash either of your chosen roms.
Full wipe as in factory settings?
Well I've installed a new RUU after the boot loop problem, isn't that considered as a full wipe? or should I just do a wipe again now?
I had that horrible boot loop aswell after installing Rom.manager but I fixed it with a ruu
Sent from my Desire HD using XDA App
Installing a new RUU does not constitute that you have full wipe any data and cache. As the ROM you tend to flash is, in a small or large extent, relatively different from that of RUU. That why we always advised to do a full wipe whenever we wish to flash ROMs. Else it will cause some issues such as Force Close issues.
You have to boot into recovery and select Wipe Data and Wipe Cache. That you will consider yourself that you have wipe those data and caches. Then now you can flash the desired ROM in your list.
In addition, before flashing is best to do a Nandroid back-up.
Also do check on your recovery version before you flash any ROMs as different ROMs need/may require different version in order to be flashed successfully(i.e. no or minimal issues)
Cheers mate.
aiight sweet, I'll give that a go.
Cheers!
You're most welcome.
drkhrsy said:
aiight sweet, I'll give that a go.
Cheers!
Click to expand...
Click to collapse
Memory serving EVERY ROM says you MUST perform a wipe of data and cache if coming from a different ROM. This is custom ROM 101. Please read instructions thoroughly before doing things like this. The ROM devs don't spend their free time writing instructions just for the hell of it.
Regarding ROM Manager, don't you get asked if you want to wipe data and cache when you flash a new ROM (or is that not an option on the free version)?
Yeh I do get asked for wiping data and cache, I do that and it just seems to still screw up. Also backing up my files through clockwork seems to make my phone get stuck on the HTC boot up screen which requires me to reformat using the RUU file.
I would suggest re-flashing the recovery.img file.
Also, are you using the same cwm-r version to restore as used to create backup? For example, If version 2.x.x.x was used to backup you can't use 3.x.x.x to restore.
Sent using witchcraft via XDA Developers Premium App.
I've just checked my CWM-R version and its recovery version is at 3.0.2.6 hmm now I cant get into the recovery boot screen :S. I'd just most likely restore the phone again and try root the phone again. but thanks anyway
nvm I got in the recovery boot. Yeh the CWM-R are the same version.
drkhrsy said:
nvm I got in the recovery boot. Yeh the CWM-R are the same version.
Click to expand...
Click to collapse
I think you miss understand. I don't mean do they match wherever you look.
Did you make the original backups using version 3.0.0.x or 2.5.x.x?
Sent using witchcraft via XDA Developers Premium App.
drkhrsy said:
I'd just most likely restore the phone again and try root the phone again.
Click to expand...
Click to collapse
You don't need to do that, just redo the recovery.img
Sent using witchcraft via XDA Developers Premium App.