Database Info

Flashing new rom

My buddy has the inspire 4g. He bought it rooted by somebody else. I've flashed cynogenmod for him aqnd several updates over the past few months. We are trying to flash new roms and its constantly aborting. Ive rooted my droids and always flash roms and never run into this problem.
He has the newest clockwork mod should we possible get a different recovery?
I don't do anything with flashing a new radio, is that necesary and whats causing the problem?
I am trying to flash core droid or revolution, he wants the best sense rom any suggestions?
I would appreciate any help. If there is no way to fix it I planned to totally reset and unroot and then root it myself and make sure everything is done right, does that sound right?

dieseldank said:
If there is no way to fix it I planned to totally reset and unroot and then root it myself and make sure everything is done right, does that sound right?
Click to expand...
Click to collapse
Though probably not necessary, the peace of mind that comes with knowing what's been done to the phone from the ground up might be worth it.
As for a fix to your current issue, please provide a little more detail as to the error.

It clears the cache and everything like that but it has a line that says installing update then the next line is installation aborted. That happens very quickly when I try to apply the update.zip

dieseldank said:
It clears the cache and everything like that but it has a line that says installing update then the next line is installation aborted. That happens very quickly when I try to apply the update.zip
Click to expand...
Click to collapse
Is this the same SD card for every try? It might be a flakey SD card. Try a different card if you can.

I have several sd cards so will try the one I use. Am going over to help him in a few hours. Anyone have other suggestions? Should I be able to just flash a rom or do I have to flash a new radio also? <Because Ive only done cynogen on his which didnt have a radio.
Thanks again.

dieseldank said:
I have several sd cards so will try the one I use. Am going over to help him in a few hours. Anyone have other suggestions? Should I be able to just flash a rom or do I have to flash a new radio also? <Because Ive only done cynogen on his which didnt have a radio.
Thanks again.
Click to expand...
Click to collapse
Radio is not usually flashed as part of the ROM. As long as you have a valid radio, it should work. If you somehow managed to get an invalid radio flashed, then you've have bigger problems that you indicate (i.e. hard bricked).
The fact that you can boot into recovery indicates that all it well with the device from that perspective. That leaves only the ROM zip to be flashed which is why I suggested trying a different SD card (since you tried several, it's not likely that you always got a bad download).
If it still messes up with a new SD card, try complete wipe, then format system from nandroid before running the update.zip. System partition doesn't get formatted during a complete wipe, but most ROMs should format it as a matter of course before installing. It's unlikely, but it could be a corrupt system partition which should clean up with a format.

dieseldank said:
I have several sd cards so will try the one I use. Am going over to help him in a few hours. Anyone have other suggestions? Should I be able to just flash a rom or do I have to flash a new radio also? <Because Ive only done cynogen on his which didnt have a radio.
Thanks again.
Click to expand...
Click to collapse
Wanna Save yourself some time and maybe some future headaches? Like posted above It helps when you know what has been done. I would start from the ground up. Get back to a stock base and go from there, this way you are not trying to track down something you may not have done but was done before he got it.
As for your issue, If a radio is recommended then it will/should state so in the thread.

I have threads on how to root his inspire but can anyone forward a link of how to completely unroot and reset. When i reset in recovery it still keeps cynogenmod on.

dieseldank said:
I have threads on how to root his inspire but can anyone forward a link of how to completely unroot and reset. When i reset in recovery it still keeps cynogenmod on.
Click to expand...
Click to collapse
There's no good reason to go through all that trouble. If you have S-OFF, then you're good to go as far as being rooted is concerned. Since you appear to have recovery too, then you're 95% rooted no matter what the current ROM is doing.
If you have S-OFF already, then going back to stock and rerooting is just going to waste time.

dieseldank said:
It clears the cache and everything like that but it has a line that says installing update then the next line is installation aborted. That happens very quickly when I try to apply the update.zip
Click to expand...
Click to collapse
In cwm are you trying to "apply update from sdcard" or "install zip from sdcard"
install zip is what you want.... then choose the ROM. IF you're applying update.... it's gonna abort.
You could also try reflashing recovery in Rom Manager or flashing an older version of recovery.
Sent from my time waster.

Gene Poole said:
There's no good reason to go through all that trouble. If you have S-OFF, then you're good to go as far as being rooted is concerned. Since you appear to have recovery too, then you're 95% rooted no matter what the current ROM is doing.
If you have S-OFF already, then going back to stock and rerooting is just going to waste time.
Click to expand...
Click to collapse
Since it has s-off and is rooted correctly what do you advise I do to fix my abort problem? Didn't see an answer in there, thanks.
Nickovtyme said:
In cwm are you trying to "apply update from sdcard" or "install zip from sdcard"
install zip is what you want.... then choose the ROM. IF you're applying update.... it's gonna abort.
You could also try reflashing recovery in Rom Manager or flashing an older version of recovery.
Sent from my time waster.
Click to expand...
Click to collapse
I tried both ways and its aborts both ways. And Ive reflashed recovery in rom manager, should I maybe try a different recovery?

Since you are already rooted and having trouble flashing thru rom manager, why not try flashing to stock rooted thru bootloader? It's my understanding that attn1's Ace_Cingular_US rom will automatically do a full wipe and take you to the latest stock rom and radio. If that works, then you can install the latest rom manager and flash a custom rom. It's worth a shot.
Sent from my Desire HD using Tapatalk

dieseldank said:
Since it has s-off and is rooted correctly what do you advise I do to fix my abort problem? Didn't see an answer in there, thanks.
I tried both ways and its aborts both ways. And Ive reflashed recovery in rom manager, should I maybe try a different recovery?
Click to expand...
Click to collapse
It's not gonna hurt. it sounds like the recovery is having issues with the script so it's aborting... an older recovery may resolve that issue.
But that's a good idea also... flash the lastest stock rooted ROM thru hboot. Then reflash recovery. see If that don't solve it
Sent from my time waster.

[Q] Flashed CM recovery with S-ON - hanging splash at boot

ok, this is my first post, and yes, i have googled for a day and a half and havent found anything similar, although it might be my wording. here it goes.....
i bought a MyTouch 4g Slide on craigslist and it was working. i started the rooting process using the revolutionary method. i discovered i couldnt get perm boot because of my hboot version 1.45.0013.
i moved on to try and root an alternate way, but wasnt sure how to proceed after getting temproot.
in the process i managed to flash the kernel (worst idea ever) in fastboot, which broke the boot process, it would power on, splash, then a black screen.
i then used the all in one tool by hasoon2000 v2.0 to flash the CM recovery, i could get to the recovery but nothing would happen when i selected any of the options (i think we all know why)
i searched and found stock recovery, kernel and system images and tried to flash them but no dice.
when booting it hangs at the splash screen, when i go into hboot and go to recovery, it reboots and then goes to recovery, but i see the download screen briefly then goes to a red triangle with an exclamation point over a phone.
the problem is, at least i think, is that i cant format \data and \system to flash the stock images i have.
any ideas?

rflores3686 said:
ok, this is my first post, and yes, i have googled for a day and a half and havent found anything similar, although it might be my wording. here it goes.....
i bought a MyTouch 4g Slide on craigslist and it was working. i started the rooting process using the revolutionary method. i discovered i couldnt get perm boot because of my hboot version 1.45.0013.
i moved on to try and root an alternate way, but wasnt sure how to proceed after getting temproot.
in the process i managed to flash the kernel (worst idea ever) in fastboot, which broke the boot process, it would power on, splash, then a black screen.
i then used the all in one tool by hasoon2000 v2.0 to flash the CM recovery, i could get to the recovery but nothing would happen when i selected any of the options (i think we all know why)
i searched and found stock recovery, kernel and system images and tried to flash them but no dice.
when booting it hangs at the splash screen, when i go into hboot and go to recovery, it reboots and then goes to recovery, but i see the download screen briefly then goes to a red triangle with an exclamation point over a phone.
the problem is, at least i think, is that i cant format \data and \system to flash the stock images i have.
any ideas?
Click to expand...
Click to collapse
If you get recovery back on there. Trackpad is what selects options in recovery. Then you can wipe and flash whatever you want. Stop using power
And if your not rooted yet or whatever because the post is worded funny, you might want to follow on through with rooting so you can do a manual format of everything
Sent from my myTouch_4G_Slide using Tapatalk 2

strapped365 said:
If you get recovery back on there. Trackpad is what selects options in recovery. Then you can wipe and flash whatever you want. Stop using power
And if your not rooted yet or whatever because the post is worded funny, you might want to follow on through with rooting so you can do a manual format of everything
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
you are a genius. i was able to get recoveyr back on there and wiped. trying to load the PG59img.zip now, well see how that goes.

rflores3686 said:
you are a genius. i was able to get recoveyr back on there and wiped. trying to load the PG59img.zip now, well see how that goes.
Click to expand...
Click to collapse
no dice. still hanging at the boot screen.
im using PG59IMG_Doubleshot_TMOUS_1.63.531.2_Radio_11.59.3504.00_11.16.3504.20_2_release_245247_signed.zip changed the file name to PG59IMG.ZIP, HBoot picks it up and loads. when you reboot, the t-mobile mytouch 4g slide screen hangs.
any other ideas?
update:
tried to flash from recovery. at first zip file would abort installation. this time i used update-cm-9.0.0-alpha4-doubleshot-signed.zip, renamed to update.zip. ran update install from recovery. it completed, upon restart, hangs at the same screen.
update2:
holy crap i got it!
i had to manually flash the kernel from the zip using fastboot.

rflores3686 said:
no dice. still hanging at the boot screen.
im using PG59IMG_Doubleshot_TMOUS_1.63.531.2_Radio_11.59.3504.00_11.16.3504.20_2_release_245247_signed.zip changed the file name to PG59IMG.ZIP, HBoot picks it up and loads. when you reboot, the t-mobile mytouch 4g slide screen hangs.
any other ideas?
update:
tried to flash from recovery. at first zip file would abort installation. this time i used update-cm-9.0.0-alpha4-doubleshot-signed.zip, renamed to update.zip. ran update install from recovery. it completed, upon restart, hangs at the same screen.
update2:
holy crap i got it!
i had to manually flash the kernel from the zip using fastboot.
Click to expand...
Click to collapse
Yeah s-on users have to fastboot flash the kernel somehow. I've never had to do it and never read up on it but I should have told you since I was aware. My bad but glad your running now
Sent from my myTouch_4G_Slide using Tapatalk 2

Just use juopunutbear and gain s-off.

blackknightavalon said:
Just use juopunutbear and gain s-off.
Click to expand...
Click to collapse
thanks for the suggestion. ill give it a shot
edit: i notice the thread is for the sensation, is there any difference in the process for the MyTouch 4g Slide?

rflores3686 said:
thanks for the suggestion. ill give it a shot
edit: i notice the thread is for the sensation, is there any difference in the process for the MyTouch 4g Slide?
Click to expand...
Click to collapse
You mean the thread that's in the MT4GS Development section? I don't know for certain if it works. I haven't bothered to unroot, gain an unlocked bootloader via HTCdev, reroot, then using juopunutbear. My unlocked-via-Revolutionary bootloader works just fine.

[Q] Problems with MD5 file trying to flash CD10 rom

I have an ATT HTC One X 2.20 Hboot 1.14 using twrp 2.4.1 and have been trying to install roms but continue to have an issue with the MD5 file. I have followed the instructions about flashing the boot.img of CM10 but it seems no matter what I do, it can't find the MD5 and says it is skipping MD5. I know just enough not to get out of a bootloop but I am quite new to this. The one odd thing I see is when I go to mount my phone in order to copy the CM10 zip file into the phone, the options I get are different than others I see online: Mount System (unchecked), Mount Data,(unchecked), Unmount Cache (checked), Unmount SD Card (checked). Any help would be awesome.

quick update; same problem
SWell, going through some of other posts and videos, I tried using goo manager to download the CM 10 zip file. But Im still stuck on boot loop. And it still says that the MD5 file was not found. I used the onexroot.com tutorial to root my phone and have superuser and twrp. Not sure what else to try. Ideas on other stable JB roms I could try? Thanks again.

In TWRP, when you install the ROM, do you have the option checked to force MD5 checked?

force check
redpoint73 said:
In TWRP, when you install the ROM, do you have the option checked to force MD5 checked?
Click to expand...
Click to collapse
I'm pretty sure I do. I have always left it unchecked. Should I check it and try again?

I've always left it unchecked (no MD5 check). If its a bad download, all that will happen is the phone will get stuck on boot, anyway.
I'd go into TWRP, and see if its checked or not. And if so, uncheck and try to flash again.

Update: No Luck
I just tried wiping system, factory reset, and cache, flashing the cm10 boot.img and then installing the CM10 zip file and checking the force MD5 and then the entire process and unchecking the force MD5 and with both attempts I get right back to the same issue. All I can say is that I'm so thankful that I created a backup in twrp. I've restored my phone at least 20 times today, haha. Learning is definitely a process. Ill take any more ideas.

Download the ROM again, may just be a bad download.

Will try
I will try to download the rom again from the CM website. If I were to try another rom (viper xl), the process should be the same correct? Thanks for the help.

alemcc said:
If I were to try another rom (viper xl), the process should be the same correct?
Click to expand...
Click to collapse
Put the ROM on your SD.
Boot into hboot, go into TWRP
In TWRP, factory reset, wipe cache, wipe Dalvik
Install ROM
Reboot
ViperXL should flash boot.img in AROMA, although its not foolproof. If the phone doesn't boot (may take about 5 min first time), then flash boot.img using fastboot.
For most ROMs, you will need to flash boot.img manually. ViperXL is one of the few exceptions (also CleanROM 5.1, I think).

Still no luck
I just tried aokp JB 4.1 with no luck. I do everything I've been told or that I have read on these forums (copy zip to SD, flash boot image, install rom...) but i continue to get the same problem: MD5 not found, skipping MD5 and so on. If anyone has any ideas I'll be happy to give any other info needed. At this point I have a rooted phone but cannot install roms. Argh!

He's not the only one. I'm on viper 3.2.3 but when trying to flash any Rom based off of AOSP or anything similar I bootloop. Yes I flash the boot.img then the Rom to no avail . I started a thread in this department called weird problem if the OP would like to take a look there.
Sent from my HTC One X using xda app-developers app

I'm new to all this, but I don't understand why certain people have this issue but most don't. Aren't all att one x phones pretty much the same?

Same thing i'm wondering
Sent from my HTC One X using xda app-developers app

you dont check any md5 checking for custom roms in twrp
you only rom i know of that you will have a md5 without anything selected is evervolv 4.2 i found a fix where you copy the CERT.SF from evervolv 4.1 to evervolv 4.2 and it will install and boot.
also always remember to "fastboot flash boot boot.img" if you are on hboot 1.14 or newer. if you going changing from sense to aosp always do full wipes no matter what. never factory reset in bootloader.

Yes I've done this countless times as I was on jellybam before going to jokers sense 4+ Rom then viper . I know the processes but something is wrong.
Sent from my HTC One X using xda app-developers app

alemcc said:
I used the onexroot.com tutorial to root my phone and have superuser and twrp.
Click to expand...
Click to collapse
I hate websites like that one. They just ripoff content from XDA, repackage it, and give little or no credit to the actual developer or XDA.
Stupid question, your bootloader is unlocked, right? In bootloader, it says UNLOCKED?
It must, for you to have TWRP. But it doesn't hurt to cover all the possibilities.

[Q] upgarde snaufu...

was running viperXL 3.2.5 and wiped and went to cm10.1 now i used goo manager to download xhata (sorry i butchered it) now i can only boot into spash screen and bootloader. i used fastboot to reflash twrp and still only boots to the custom spash... hboot 1.09 s-off..... im kinda lost here. should have syuck with viper, why screw with perfection.

What is xhata? Is it a rom?
I'm not sure we can install roms with Goo Manager on this phone.
If you installed a rom for the quad-core Tegra One X, your phone will not boot and you're lucky you didn't get a brick. You need to do a full wipe and reflash.

first off not a noob. it was the evita rom. i still have bootloader access and can get half way into recovery( spash screen then twrp spash...) then reboot into custom splash. it was the rom... http://forum.xda-developers.com/showthread.php?t=2075783 so if anyone has any ideas please help, just dont start with the usual u screwed up flashing roms i know better. and the odd part is after reflashing the recovery via fastboot i get Twrp spash before going back to the phone main splash and boot looping.... and yes im s-off

No need to be so defensive. If we don't know exactly what you flashed, all we can do is ask. Its not meant as an insult. But its always better to ask the seemingly "obvious" questions first, get them out of the way.
If there is a "usual thing" that gets mentioned, its because the mistake of flashing ROMs for the ENDEAVORU in fact happens so often. Downloading from GooManager is not a great idea either, and often a red flag that someone installed a ROM for the wrong version of the phone.
Did the phone operate properly when you were on CM10.1?
What version of TWRP, and what fastboot command did you use to flash it?

I asked the "usual" questions because:
-You have less than 100 posts. That's often a sign of someone who is new to this.
-You used a rom name I've never heard of, and suggested you weren't sure of the name yourself. That's usually a big red flag for someone who flashed some random rom they found via Google.
-You mentioned using Goo Manager. That's a non-standard method for this phone, and an awful lot of people have bricked their phones trying to flash roms through apps that aren't well-supported. CWM Touch was notorious for this when the One X first came out.
If you don't want people to assume things, you need to state them up front.
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.

iElvis said:
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
Click to expand...
Click to collapse
Yeah, I saw that too, and why I asked the OP what version of TWRP.

i had problems with that rom on version 4.0.1 and 4.1.0 had alot of errors and trouble. i haven't tried 4.2.0 though, i have been having better luck with rom after clearing out recovery cache running "fastboot erase cache" and running only twrp 2.3.3.1.

i flashed the second to last release of twrp (latest gave mount issues), viper was running great, cm 10.1 avatar was running fine just didnt like how plain it was so i used goo manager to download hatkaXL and when the download finished i picked select and flash.. then the usual warning about flashing and it rebooted, hit spash screen where it still is hours later. i then tried manually boot into recovery, it hit the bootloader i selected recovery and it seemed to try and load. next step was back to fast boot and to reflash twrp (fastboot flash recovery recovery.img ) flashed 100% success and still wont boot into recovery just the bootloader, and i wasnt trying to get all defensive, i sent first post using the wifes phone and posted quick, had a guy hooking up my satellite at same time as phone crashed. has anyone tried the new version of cwm for the evita? maybe flashing that may get me back, i have roms and backups on the pc that i can seem to side load but never boot as well.

well after repeated flashing of recovery and (fastboot erase cache) it finally booted to recovery, now to see if my backup will load.

[Q] Can't Get Rom to Boot

I was able to get my wife's phone unlocked over the weekend. I threw twrp 2.5.0.0 on there and tried to flash cleanrom. The phone was on the newest bootloader, so I tried flashing the boot.img in fastboot. It just stays on the boot screen forever. I found that there may be issues with newer twrp versions so I tried installing 3 different older version of twrp and all were unresponsive to touch. I could press power once and the twrp lock screen would come up, but that was it. I put 2.5.0.0 back on and it became usable again. Unfortunately I'm not S-Off yet because it says you have to be rooted and my plan was to put CleanRom on and then S-Off. I've verified the MD5 of the ROM zip on the phone. When I am going through the rom install though, and I go through all the options and it starts to install, it literally takes a tenth of a second and says successful. Then when I go to reboot to bootloader, it asks me if i'm sure since i don't have an OS installed. I figured that's just because I haven't flashed the boot img yet, but I am used to rom installs taking a couple seconds on my One XL. I've tried installing the boot.img with Hasoon's all-in-one and it says successful. I've tried installing the bulletproof kernel both via zip format and the boot img and still nothing boots up. What else can I try guys? The wife goes out of town tomorrow morning and needs a working phone. Thanks for your help.
edit: i found the log of the cleanrom install which appears to show the install failing.

utdps said:
I was able to get my wife's phone unlocked over the weekend. I threw twrp 2.5.0.0 on there and tried to flash cleanrom. The phone was on the newest bootloader, so I tried flashing the boot.img in fastboot. It just stays on the boot screen forever. I found that there may be issues with newer twrp versions so I tried installing 3 different older version of twrp and all were unresponsive to touch. I could press power once and the twrp lock screen would come up, but that was it. I put 2.5.0.0 back on and it became usable again. Unfortunately I'm not S-Off yet because it says you have to be rooted and my plan was to put CleanRom on and then S-Off. I've verified the MD5 of the ROM zip on the phone. When I am going through the rom install though, and I go through all the options and it starts to install, it literally takes a tenth of a second and says successful. Then when I go to reboot to bootloader, it asks me if i'm sure since i don't have an OS installed. I figured that's just because I haven't flashed the boot img yet, but I am used to rom installs taking a couple seconds on my One XL. I've tried installing the boot.img with Hasoon's all-in-one and it says successful. I've tried installing the bulletproof kernel both via zip format and the boot img and still nothing boots up. What else can I try guys? The wife goes out of town tomorrow morning and needs a working phone. Thanks for your help.
edit: i found the log of the cleanrom install which appears to show the install failing.
Click to expand...
Click to collapse
Did you flash boot boot.img?

Crypto66 said:
Did you flash boot boot.img?
Click to expand...
Click to collapse
I've narrowed down the issue to the install of CleanROM failing. This may be to twrp 2.5.0.0 but as I've said, earlier versions such as 2.3.3.0 aren't responding to touch for some reason. I don't think 2.5.0.0 is my problem though. I can see it if it didn't wipe properly, but the install is failing due to I/O errors.
But yes, I have tried flashing boot.img. twrp tells me I don't have an os when I try to reboot though, so that's the issue.

Try going to the advanced tab and fix permissions.
Sorry for slow responses, I've got to wait 5 minutes in between posts.

Crypto66 said:
Try going to the advanced tab and fix permissions.
Sorry for slow responses, I've got to wait 5 minutes in between posts.
Click to expand...
Click to collapse
Fix permissions won't work without a rom installed. It fails. And from what I understand anyways, fixing permissions is mostly for apps anyways.

Problem solved. Everyone make sure to use TWRP 2.3.3.1 and only that exact version. Older has touchscreen problems and newer has install issues. Man, this stuff can be frustrating at times.

That's not exactly true. Older versions work just fine, I'm using version 2.2 and it has never failed me.
Older versions aren't working for you because you have a newer touchscreen firmware, you would need to downgrade your touchscreen firmware in order to have touch response. For the same reason, you would not be able to run aosp roms until downgrading. Just thought I'd clear that up.
Sent from my One XL using XDA Premium