[Q] Evo 4g can only flash CM7, nothing else - General Questions and Answers

Ok, so i've exhausted all searches. I always always search first and try every possible solution, after a week, i'm back to square one.
I rooted my htc evo 4g with unrevoked. Ive been flashing and rooting for almost a year now and never enountered a problem like this before
Amon_ra 2.3
S-OFF
Hboot 2.10.0001
the issue is everytime i try to flash a rom other than CM7, i get this error:
assert failed: write_raw_image("/tmp/boot.img","boot") Status 7
I am only trying to flash a sense rom so i can update my prl.
I followed the advice on this page: http://androidforums.com/evo-4g-all...-write_raw_image-tmp-boot-img-boot-error.html
but i still get boot: PU-Fail running the all in one PC36IMG.zip, when that didnt work, i tried the stand alone version
I then tried partitioning my sdcard using this: http://forum.xda-developers.com/showthread.php?t=1158993
and still no luck. Everytime i mess up, i just re-flash CM7 and it works like nothing was wrong. I could live with cm7 forever, i just want to update my prl then go back to cm7.
These are the roms ive tried:
Sprint lovers stand alone| Result: didnt give me error but stayed on white screen for over 1.5 hours.
sprint lovers all in one PC36IMG.zip| Result: boot-PU-Fail, update failed
latest fresh. 4.3.3.| Result: assert failed: write_raw_image("/tmp/boot.img","boot") Status 7
Stock rom deodexed: assert failed: write_raw_image("/tmp/boot.img","boot") Status 7
synergy| result: assert failed: write_raw_image("/tmp/boot.img","boot") Status 7
FYI i do a full wipe of system, dalvich cache, and then flash the virus wipe zip.
I am stuck. I feel like i cant flash any sense rom and i can only flash CM7.
Please help let me know if you need any other info

Have you upgraded your recovery? Back in the day (less than a year ago actually) certain versions of clockwork didn't play nice when switching from AOSP based ROM's back to a sense ROM.

yeah i flashed the latest amon 2.3 recovery just recently. i can try reflashing it.

same problems unfortunately, flashed amon 2.3. then full wipe of system and dalvich. still getting assert failed: write_raw_image("/tmp/boot.img","boot") Status 7 when trying when trying any sense rom.

am i stuck with cm7 forever then?

I think i'll start from fresh again. this will be my steps:
my sd card is already partitioned, and after nandroid i'll do this:
i'll reflash amon ra2.3
1. so in recovery wipe data, dalvik cache, and cache do that 3x.
2. vr superwipe
3. i'll try reflashing the fresh rom, or any/all sense rom
4.cross my fingers *hope*

could it be a kernal problem? i tried flashing the fresh-evo-4.3.3.zip and it went through all 8 steps, but on step 8 it said:
assert failed: write_raw_image ("/tmp/boot.img", "boot") just like before

im going to keep talking to myself because it keeps me sane. i just did another complete full wipe and did the pc36img.zip update for the all in one that was recommended on this page: http://androidforums.com/evo-4g-all...mage-tmp-boot-img-boot-error.html#post3555107
i get boot -fail-pu and partition fail. so weird. i am trying to install the stand alone version now. it seems to 'flash' with no problems, however last time i did so, it stayed on the white screen for a good hour. right now im just waiting on the white screen again. we shall see.
any other suggestions?

In all do respect but what HBoot is that? Mines 6.16.1002 what hardware do you have? That's kinda weird that your having problems flashing other ROMs but CM7..

its hboot 2.10.0001 for the htc evo 4g. its currently doing its whitescreen thing with sprint lovers rom. if i decide to pull battery i can get the specifics on the hardware info. ive been reading this thread: http://forum.xda-developers.com/showthread.php?t=894331&page=13
shouldnt amon 2.3 take care of partition issues?

i think its the 003 hardware since its one of the original evos. im loading a cm7 nandroid and can double check since i dont see the info in the bootloader

Honestly I'm not gonna lie but I read the 1st 50 posts in that link and didn't sh*t make any sense lol
I can't remember what HBoot I had on my 0003 before I broke it so I'm even more confused and don't know how to help you out...

Yeah im back on my cm7 nandroid lol. its basically my go to when everything messes up haha. for some reason cm7 doesnt like to tell hardware info in the settings. unless they put it in a completely diff place. im pretty sure its 0003 though. this $hit is crazy! should i try an older amon recovery?

memekmek said:
Yeah im back on my cm7 nandroid lol. its basically my go to when everything messes up haha. for some reason cm7 doesnt like to tell hardware info in the settings. unless they put it in a completely diff place. im pretty sure its 0003 though. this $hit is crazy! should i try an older amon recovery?
Click to expand...
Click to collapse
Actually I used the recovery that they're talkin about AmonRa v2.3 on my HW 0003 and NEVER ran into any problems flashin anything and I was flashin EVERYTHING known to flash so that's why I'm trippin out I even used RA-SuperSonic-v3.08.gnm Recovery on my 0003 and it was even better then the Original AmonRa v2.3 maybe try out the recovery I'm using I have the zip if you wanna give it shot bro

yeah let me try that out... i never had any of these issues till now. i was able to flash whatever i wanted till now too. now just cm7 ha.

infamousteeboy said:
Actually I used the recovery that they're talkin about AmonRa v2.3 on my HW 0003 and NEVER ran into any problems flashin anything and I was flashin EVERYTHING known to flash so that's why I'm trippin out I even used RA-SuperSonic-v3.08.gnm Recovery on my 0003 and it was even better then the Original AmonRa v2.3 maybe try out the recovery I'm using I have the zip if you wanna give it shot bro
Click to expand...
Click to collapse
i found the file here i believe: http://forum.xda-developers.com/showthread.php?t=1339654
see i search! thats why my posts are low lol, every other time i wanted to post, i found the answer. i guess i could post more for helping others, which ive been trying to do more recently

memekmek said:
yeah let me try that out... i never had any of these issues till now. i was able to flash whatever i wanted till now too. now just cm7 ha.
Click to expand...
Click to collapse
CLICK HERE
You know what to do right?
-Download
-Place on ROOT OF SD *not in a folder*
-Rename PC36IMG.zip
-Boot to Bootloader
-Follow on screen prompts
-Vol. up to accept update
-Vol. up to confirm
-Reboot
-Boot to Recovery

infamousteeboy said:
CLICK HERE
You know what to do right?
-Download
-Place on ROOT OF SD *not in a folder*
-Rename PC36IMG.zip
-Boot to Bootloader
-Follow on screen prompts
-Vol. up to accept update
-Vol. up to confirm
-Reboot
-Boot to Recovery
Click to expand...
Click to collapse
yep yep, going to try it now

memekmek said:
yep yep, going to try it now
Click to expand...
Click to collapse
For sure and FYI you can use the Haptik Keys with this recovery
Home - Up
Menu - Down
Back - lol
Search - Select

infamousteeboy said:
CLICK HERE
You know what to do right?
-Download
-Place on ROOT OF SD *not in a folder*
-Rename PC36IMG.zip
-Boot to Bootloader
-Follow on screen prompts
-Vol. up to accept update
-Vol. up to confirm
-Reboot
-Boot to Recovery
Click to expand...
Click to collapse
eh same problems, still getting status 7 error. installation aborted.
should i try upgrading to latest hboot?

Related

Cant update ROM. What am I doing wrong

I have a NS unlocked and rooted. I have ROM Manager, busybox etc. I followed all the instructions but I can't update ROMs or the 2.3.3 update or CM7 nothing. Each time it starts to unpack or whatever it gets about 1/3 the way and aborts. Something about verifying signatures or something.
Very frustrating.
Thanx in advance
I Love The Smell Of Burnt Rubber Anytime
try to download the ROM again
sounds like the zip file is corrupted
What version Clockwork Recovery are you using? Try reverting back to a older version or something.
Verify the ROM's MD5 Hash using HashTab (Google it)
I've tried several times with downloads and now the latest clockwork and the version prior.
Samething always aborts, can't verify signature. Tried manual and through rom manager.
When using rom manager is that suppose to do the whole install? Cuz that only gets me to the little droid and the triangle. I have to get myself into bootloader and continue manually from there.
Thanks
I Love The Smell Of Burnt Rubber Anytime
hllywd said:
I've tried several times with downloads and now the latest clockwork and the version prior.
Samething always aborts, can't verify signature. Tried manual and through rom manager.
When using rom manager is that suppose to do the whole install? Cuz that only gets me to the little droid and the triangle. I have to get myself into bootloader and continue manually from there.
Thanks
I Love The Smell Of Burnt Rubber Anytime
Click to expand...
Click to collapse
what's the latest clockwork recovery? did you try 3.0.0.5?
Ya. The new ver is 3.0.2.4
I Love The Smell Of Burnt Rubber Anytime
hllywd said:
I've tried several times with downloads and now the latest clockwork and the version prior.
Samething always aborts, can't verify signature. Tried manual and through rom manager.
When using rom manager is that suppose to do the whole install? Cuz that only gets me to the little droid and the triangle. I have to get myself into bootloader and continue manually from there.
Thanks
I Love The Smell Of Burnt Rubber Anytime
Click to expand...
Click to collapse
Hmm... It sounds like clockwork isn't properly installed. ROM Manager should take you directly to clockwork recovery without you having to do anything.
the problem you are facing is that you are still on stock rom. so even if you flash clockwork recovery and then reboot to recovery, you'll always end up going to the stock recovery. this is a new feature implemented by google.
what you should do is...
1) go to bootloader
2)flash the clockwork recovery using fastboot
3)DO NOT reboot the phone or quit bootloader. immediately after flashing the rec. using fastboot, just enter recovery (through bootloader)
4)flash you new rom
just for u to have an idea. the recovery should be orange in colour.
option 2.
you also have the option of using a file manager with moun/root functions such as root explorer and rename the recovery script in etc folder but i guess step 1 is much easier for now.
OK I played alot today and this is what happened.
After fixing permissions and flashing the new CWM and wiping data/cache it finally worked. Unfortunately titanium and my backup didnt bring everything over. So I went back and forth between stock and CM7 several times but I just couldnt get all my stuff back in CM7. So I thought Id try the 2.3.3 update but not wiping stuff. That didnt work. Then I tried one more time with CM7 but not wiping. I couldnt get pastthe little CM7 droid on the skateboard. So went back to stock for now. Ill have more time on Sat to give things another try.
At least I can get in it now.
Any ideas/thoughts/
Thanks and sorry for the long post.

NS4G Wont boot need help!

I can flash clockworks recovery through adb and can get in but I'm getting some errors:
E: Can't find misc
E: failed to find "cache" partition to mount at "/cache"
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
And a bunch few more which seem to repeat
I also tried to run the restore to stock from here but get an error right when I have to click to write the image.
When I just boot all I see is the unlocked lock and google. It used to boot into storage so I can mount it but not anymore. The only thing I have on the SD is the super user app, Netarchy kernel for 4G, CM7 latest stable for NS and thats it.
Need help
I can push something to the phone through the sdk but I don't know how to mount the sd card to do it.
ufff.... nevermind. I tried the factory restore one more time on another machine 32 bit and it works. It's restoring the image again. Will be locked again so I'll have to try again tomorrow. But the steps on rooting the NS4G don't really work well.
There is a bunch of stuff missing. Like the recovery gets overwritten each time. There are some links missing and dead.
Someone should fix that before we brick some phones.
OK, it restored but only gave me the sd card mount thing. I tried going back to fastboot and unlocked was still there. So I flashed recovery again and wanted to see if I can put the stock rom for 4G from here on it.
No go. I get:
assert failed: write_raw_image("/tmp/netharchy.img", "boot")
Installation aborted.
Help
ok, I'm not sure what ROM I have but I unplugged the cable and bam... sign in screen came in so I'm sighing in. Once I can get to the main menu I'll check versions and kernel but it looks like I have root. It's just that recover is not working well. I have 3.0.0.5. should I get a different one?
OK, I restored again because wifi didn't work. I think it was because I was trying to flash after the first restore and it wouldn't take. So now I checked and the lock when I boot showes up as unlocked but none of the root apps work so I don't think I have root. Not sure.
I also have to figure out what's up with that recovery. I know I need to rename the original so it doesn't flash it every time on boot but I think I need a new version. Anyone know which one is the latest and which one works on NS4G?
3005 is the problem. Use 3024. I don't know for sure but are you absolutely sure cm7 is compatible with the ns4g? Isn't a lot of stuff still not working? Isn't 4g still not working? If flashing the wrong rom is what happened here then this problem isn't going away. Many people are doing this and almost bricking their phones. I read one post recently that pointed to a doc that said the gsm and cdma are two separate versions of the same os. I thought I read something that said kernels might be cross compatible but roms aren't yet.
Here are the correct recovery files for the ns4g
I think I remember seeing recovery ***** about cache when I was nandroid for the first time. I think after that I chose factory reset and clear dalvik and some other cache and might have rebooted then came back and flashed cwm again and tried nandroid and it worked that time. This was the very last step for me after I had managed to get the su file to the root of the card, flashed it in cwm, rebooted and changed the filename of the script to check and reinstall stock recovery in system/etc. I forget the name but it was a .sh file. It's name was in the guides somewhere...
I think that's backwards. Roms might be compatible but kernels which these roms come with are not. So I believe that it I just flash netarchys kernel which now supports NS4G all should work ok.
Like I said, I'm back to stock and all looks like exactly like it was before ie. no root but the weird part is that fast boot menu says "unlocked". And I also get the lock which looks unlocked with the google sign during boot.
So how is that possible? Anyone?
When trying any app with root it tels me it has no access or it failed. Ie, su cmd says access denied.
BTW, why you attached two files? What is the difference between the two?
herbthehammer said:
3005 is the problem. Use 3024. I don't know for sure but are you absolutely sure cm7 is compatible with the ns4g? Isn't a lot of stuff still not working? Isn't 4g still not working? If flashing the wrong rom is what happened here then this problem isn't going away. Many people are doing this and almost bricking their phones. I read one post recently that pointed to a doc that said the gsm and cdma are two separate versions of the same os. I thought I read something that said kernels might be cross compatible but roms aren't yet.
Here are the correct recovery files for the ns4g
I think I remember seeing recovery ***** about cache when I was nandroid for the first time. I think after that I chose factory reset and clear dalvik and some other cache and might have rebooted then came back and flashed cwm again and tried nandroid and it worked that time. This was the very last step for me after I had managed to get the su file to the root of the card, flashed it in cwm, rebooted and changed the filename of the script to check and reinstall stock recovery in system/etc. I forget the name but it was a .sh file. It's name was in the guides somewhere...
Click to expand...
Click to collapse
Thanks for your help. I'm rooted and recovery is sticking ok. It was the old recovery. As soon as I flashed it all was good.
One is stock and the other is cwm that works with the ns4g. It wouldn't hurt to have the stock laying around. There might be a time when you need it.
Thanks for the stock recovery.
Sent from my Nexus S 4G using XDA App

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] Please help me! Flashed a nexus s 4g rom onto a nexus s 3g phone

model: Nexus S (I9023)
History: Installed ICS 4 couple of months back.
Wanted to try out cm7. But, saw that there was cm9, so didn't actually pay attention to which rom I was going to flash. Downloaded the rom from the cm official website (cm_crespo4g-ota-eng.burnsra.a18).
After reboot, I am not able to connect to network and in system settings all 4G options are being shown!
Not able to flash any other ROM's too (Tried installing 2.3.4).
Don't have any backup (I thought I may not run into any problem, as I had done it once already)
How can I restore the communication functionality?
you have to flash a radio that is compatible to your phone from here http://forum.xda-developers.com/showthread.php?t=1116884
Update: I just found that before installing ICS, i did make a back up. I tried to restore and I got the following msg:
Checking MD5 sums...
MD5 mismatch!
If there is a way I can restore, from the back up, I would prefer that rather than messing up with anything else. Because now I feel, I should read more first before actually doing something!
u could try this http://forum.xda-developers.com/showthread.php?t=714114
this may help too cwm nandroid backup ics for i9023 http://forum.xda-developers.com/showthread.php?t=1396224 just place in cwm backup folder on your sd card
Here's what I would do if it were me ...
Assuming that you still have recovery, d/l a copy of the proper radio for your device and a solid rom like Peter Alfonso's "Bugless Beast". You will also need the "Wipe All" zip. Place everything on your sdcard, wipe cache and dalvik, then flash the radio. Next, back into recovery, flash "wipe all" zip, and then flash the full rom.
If everything goes ok, allow phone to completely boot, and then back into recovery. Again flash the "wipe all" zip, and then restore the back up you made previously. Good luck.
sean1984 said:
u could try this http://forum.xda-developers.com/showthread.php?t=714114
this may help too cwm nandroid backup ics for i9023 http://forum.xda-developers.com/showthread.php?t=1396224 just place in cwm backup folder on your sd card
Click to expand...
Click to collapse
OK thanks. But just to let you know, I am complete noob here. I was trying to comprehend about the RADIO's that you directed me to and nothing made much sense.
The latest guide you directed me to, clearly says that I need to have ClockWorkMod 5.0.0 or higher (I am running 3.1.0.1 ).
wmdunn said:
Here's what I would do if it were me ...
Assuming that you still have recovery, d/l a copy of the proper radio for your device and a solid rom like Peter Alfonso's "Bugless Beast". You will also need the "Wipe All" zip. Place everything on your sdcard, wipe cache and dalvik, then flash the radio. Next, back into recovery, flash "wipe all" zip, and then flash the full rom.
If everything goes ok, allow phone to completely boot, and then back into recovery. Again flash the "wipe all" zip, and then restore the back up you made previously. Good luck.
Click to expand...
Click to collapse
Thanks. This seems pretty straight forward. I will try this. Just one last doubt: How do I find the right radio for my device?
deepak.s829 said:
Thanks. This seems pretty straight forward. I will try this. Just one last doubt: How do I find the right radio for my device?
Click to expand...
Click to collapse
I'm not sure which one of these is the latest, but any of the ones for your device (I9023?) should work. My guess is that the KF1 should be ok ...
http://forum.xda-developers.com/attachment.php?attachmentid=737283&stc=1&d=1317509083
wmdunn said:
I'm not sure which one of these is the latest, but any of the ones for your device (I9023?) should work. My guess is that the KF1 should be ok ...
http://forum.xda-developers.com/attachment.php?attachmentid=737283&stc=1&d=1317509083
Click to expand...
Click to collapse
I was just learning about the RADIO and all that... And I was in the system settings of my phone. It is showing options like "Sprint system updates" and also some CDMA options....
I am in India and I use airtel GSM connection..
Can anybody tell me what I have done?Can flashing a wrong ROM make such big changes?
deepak.s829 said:
I was just learning about the RADIO and all that... And I was in the system settings of my phone. It is showing options like "Sprint system updates" and also some CDMA options....
I am in India and I use airtel GSM connection..
Can anybody tell me what I have done?Can flashing a wrong ROM make such big changes?
Click to expand...
Click to collapse
The rom you flashed was for Sprint phones, so it's no surprise that those files are present. They will all be replaced when you get everything back on track. Good luck ...
wmdunn said:
I'm not sure which one of these is the latest, but any of the ones for your device (I9023?) should work. My guess is that the KF1 should be ok ...
http://forum.xda-developers.com/attachment.php?attachmentid=737283&stc=1&d=1317509083
Click to expand...
Click to collapse
Device is GT-i9023
deepak.s829 said:
Device is GT-i9023
Click to expand...
Click to collapse
You should be ok with the radio file I linked you to in the earlier post.
I did a clean wipe of everything and also flashed the radio. But, I am unable to flash new ROM. And now the phone doesnt go past the google start up screen logo
Do I have a bricked phone now?
But I am still able to boot into recovery.
deepak.s829 said:
I did a clean wipe of everything and also flashed the radio. But, I am unable to flash new ROM. And now the phone doesnt go past the google start up screen logo
Do I have a bricked phone now?
I still have recovery
Click to expand...
Click to collapse
Turn the phone completely off, then press and hold volume "up" and the power button at the same time. That should get you into recovery. From there flash the "wipe all" zip and then the new rom in the same session. Then let your phone boot normally.
Easy mistake with all the ****ing roms shoved into general lately. You'll get it worked out.
wmdunn said:
Turn the phone completely off, then press and hold volume "up" and the power button at the same time. That should get you into recovery. From there flash the "wipe all" zip and then the new rom in the same session. Then let your phone boot normally.
Click to expand...
Click to collapse
After installing wipe-all, when I try to flash the rom, everytime I get the same, following message:
--Installing /sdcard/pete_crespo_10-23-11.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device")=="crespo" | |
"crespo"
E:ERROR in /sdcard/pete_crespo_10-23-11.zip
(Status 7)
Installation aborted.
I dunno how it happened..
I just flashed ClockWorkMod recovery version 5, and then repeated the same steps>
1. Wipe-all
2.Install bugless beasty ROM.
3.The problem got fixed.
4. ALL communications restored
5. Thank you
Thanks a tonne for your patient replies
I learnt a lot today
So, the problem was with the version of the recovery image i was running?
update your clockworkmod to the latest official one (5.0.2.0) and then try to restore your backup. if that doesnt work, flash the radio for i9023.
did you backup your efs folder?
good luck.
Edit:just saw your reply.
thegtfusion said:
update your clockworkmod to the latest official one (5.0.2.0) and then try to restore your backup. if that doesnt work, flash the radio for i9023.
did you backup your efs folder?
good luck.
Edit:just saw your reply.
Click to expand...
Click to collapse
Now that I could recover my phone, I would like to try another ROM. Before I do that, What all are the necessary things I would have to back up so that, if in case I run into any problem, I can recover everything from back up?
deepak.s829 said:
I dunno how it happened..
I just flashed ClockWorkMod recovery version 5, and then repeated the same steps>
1. Wipe-all
2.Install bugless beasty ROM.
3.The problem got fixed.
4. ALL communications restored
5. Thank you
Thanks a tonne for your patient replies
I learnt a lot today
So, the problem was with the version of the recovery image i was running?
Click to expand...
Click to collapse
Yes ... the last error message you got was due to using an out dated version of the recovery image. You did the right thing by flashing CWM 5. Glad you were able to get back to normal. Take care ...
Bill
---------- Post added at 05:52 PM ---------- Previous post was at 05:49 PM ----------
deepak.s829 said:
Now that I could recover my phone, I would like to try another ROM. Before I do that, What all are the necessary things I would have to back up so that, if in case I run into any problem, I can recover everything from back up?
Click to expand...
Click to collapse
Just do a nand backup of the working rom, and keep the "wipe all" zip and radio zip on your sd card.

Aroma semi-bricked my phone?!

I saw that the new CleanROM was using the Aroma installer for both versions of the ROM, so I figured I'd give it a shot. I don't have any experience with Aroma, but it all seemed to be working at first. However, I guess the file may have been corrupt because it just stuck at "Installing ROM" and never finished.. I hit the next button and it said it was finished even though I never got a status update. Stuck at HTC load screen, and will NOT boot into recovery even from the bootloader.
Since I can still load the bootloader, but not recovery, I still have some hope, right?
All I should have to do is run the AT&T RUU, right?
Halp!
infamousjax said:
I saw that the new CleanROM was using the Aroma installer for both versions of the ROM, so I figured I'd give it a shot. I don't have any experience with Aroma, but it all seemed to be working at first. However, I guess the file may have been corrupt because it just stuck at "Installing ROM" and never finished.. I hit the next button and it said it was finished even though I never got a status update. Stuck at HTC load screen, and will NOT boot into recovery even from the bootloader.
Since I can still load the bootloader, but not recovery, I still have some hope, right?
All I should have to do is run the AT&T RUU, right?
Halp!
Click to expand...
Click to collapse
Relock then try the RUU
http://forum.xda-developers.com/showthread.php?t=1761429
Sent from my HTC One X
Or push twrp recovery and flash again.
Thanks for the responses -- was able to boot into recovery (CWM)... Not sure why it wouldn't work before.
Now it says it cannot mount the sdcard...
doesn't sound good.
Waiting on RUU to finish downloading, then I'll relock and try that.
infamousjax said:
Thanks for the responses -- was able to boot into recovery (CWM)... Not sure why it wouldn't work before.
Now it says it cannot mount the sdcard...
doesn't sound good.
Waiting on RUU to finish downloading, then I'll relock and try that.
Click to expand...
Click to collapse
You should not use cwm, use twrp, CleanROMs op stated that, try pushing twrp, and flashing before you ruu, it causes issues that hasn't been fixes yet.
Sent from my HTC One X
Can't use clock work. Use team win.
If everybody is saying use TWRP and the person is still using CWM; one has to wonder how intelligent that person is.
mankind 0 monkey 1
infamousjax said:
Now it says it cannot mount the sdcard...
Click to expand...
Click to collapse
This is a known issue with CWM, mount SD simply does not work. Use TWRP like everyone is saying.
Did you try wiping anything in Aroma? Because that is a known issue as well (results in soft bricks). Only wipe in recovery, and use Aroma only for picking the various ROM options (not for wiping anything).
Got it working -- used fastboot to flash TWRP and formatted SD card and now everything is lovely.
I've been flashing CleanROM since the beginning before there was TWRP and never bothered to switch recoveries. I guess I should have read the notes more closely.. oh well, no harm done
thanks for the replies and help

Categories

Resources