Hey there.
My Droid Eris was rooted about a month ago with the Universal Root Method for the 1.49 bootloader. I am unable to flash certain ROMs on my phone such as Kaos Froyo and Plain Jane. I get a "Verification Failed, Installation Aborted" error every single time I try it. I have tried flashing the ROMs using both Clockwork and Armon RA. Clockwork just returns to the main menu, and Armon gives the verification error. I tried searching the forum and found very little people with the problem. In case it matters, I also tried formatting my memory card, wiping Dalvik and memory, and un-rooting my Eris by loading a PB00IMG.zip onto it.
Could anyone help me out here, as I am fairly new to this?
Thank you guys.
jonathan.moran said:
Hey there.
My Droid Eris was rooted about a month ago with the Universal Root Method for the 1.49 bootloader. I am unable to flash certain ROMs on my phone such as Kaos Froyo and Plain Jane. I get a "Verification Failed, Installation Aborted" error every single time I try it. I have tried flashing the ROMs using both Clockwork and Armon RA. Clockwork just returns to the main menu, and Armon gives the verification error. I tried searching the forum and found very little people with the problem. In case it matters, I also tried formatting my memory card, wiping Dalvik and memory, and un-rooting my Eris by loading a PB1000.img onto it.
Could anyone help me out here, as I am fairly new to this?
Thank you guys.
Click to expand...
Click to collapse
Did you format your sd card to fat32 no partitions?
Yes, I formatted it with the recovery.
jonathan.moran said:
Yes, I formatted it with the recovery.
Click to expand...
Click to collapse
So you set both sides to zero right?
Busphan said:
So you set both sides to zero right?
Click to expand...
Click to collapse
Yeah.
But just my luck, it doesn't help anything.
jonathan.moran said:
Yeah.
But just my luck, it doesn't help anything.
Click to expand...
Click to collapse
Ok, have you loaded the engineering bootloader (s-off)?
Busphan said:
Ok, have you loaded the engineering bootloader (s-off)?
Click to expand...
Click to collapse
Uhm, no.
I am rooted with the S-ON 1.49.0000 bootloader. It also says (PB0010000) next to the bootloader number.
jonathan.moran said:
Uhm, no.
I am rooted with the S-ON 1.49.0000 bootloader. It also says (PB0010000) next to the bootloader number.
Click to expand...
Click to collapse
Jcase has a thread on how to change to the s-off bootloader. I think that might be part of the problem. I'm pretty sure I saw someone having similar troubles until he changed his bootloader. I would try that. Just read the thread thoroughly to ensure that you don't brick it. This bootloader is safer when rooted so it is best to run the s-off one.
Busphan said:
Jcase has a thread on how to change to the s-off bootloader. I think that might be part of the problem. I'm pretty sure I saw someone having similar troubles until he changed his bootloader. I would try that. Just read the thread thoroughly to ensure that you don't brick it. This bootloader is safer when rooted so it is best to run the s-off one.
Click to expand...
Click to collapse
Alright.
Thank you for the help!
I hadn't even considered the bootloader.
I will try Jcase's thread when I return home, I have to do a few errands.
Thank you again!
jonathan.moran said:
Alright.
Thank you for the help!
I hadn't even considered the bootloader.
I will try Jcase's thread when I return home, I have to do a few errands.
Thank you again!
Click to expand...
Click to collapse
Anytime
10 chara
I have the same issue. I am rooted and have boot loader s-off engineering boot loader.
What happens Isherwood rom will flash but won't make it past thru boot up. Freezes or boot loops. Only certain roms seem to ever make it to the final stages.
Had a lot of issues with nonsensical v4.6. Been round and round the barn on this one.
Jp50 said:
I have the same issue. I am rooted and have boot loader s-off engineering boot loader.
What happens Isherwood rom will flash but won't make it past thru boot up. Freezes or boot loops. Only certain roms seem to ever make it to the final stages.
Had a lot of issues with nonsensical v4.6. Been round and round the barn on this one.
Click to expand...
Click to collapse
So you haven't found a fix yet?
Hopefully changing his bootloader will work. If not at least he will be on a safer bootloader.
Busphan said:
So you haven't found a fix yet?
Click to expand...
Click to collapse
Not yet. Although I was able to flash Tazz froyo. 2.0 over 1.0 last night with no isssues. That rom has been good to me.
Sent from my Tazz Froyo 2.0 using Tapatalk
Jp50 said:
Not yet. Although I was able to flash Tazz froyo. 2.0 over 1.0 last night with no isssues. That rom has been good to me.
Sent from my Tazz Froyo 2.0 using Tapatalk
Click to expand...
Click to collapse
Yeah, Tazz's rom is my fav.
Jp50 said:
I have the same issue. I am rooted and have boot loader s-off engineering boot loader.
What happens Isherwood rom will flash but won't make it past thru boot up. Freezes or boot loops. Only certain roms seem to ever make it to the final stages.
Had a lot of issues with nonsensical v4.6. Been round and round the barn on this one.
Click to expand...
Click to collapse
My phone won't even get that far into the flashing process.
It just stops the whole thing before it even starts.
But I'm back home now, hopefully when I change my bootloader that it will help.
jonathan.moran said:
My phone won't even get that far into the flashing process.
It just stops the whole thing before it even starts.
But I'm back home now, hopefully when I change my bootloader that it will help.
Click to expand...
Click to collapse
Just let us know, if it doesn't we will go from there.
jonathan.moran said:
My phone won't even get that far into the flashing process.
It just stops the whole thing before it even starts.
But I'm back home now, hopefully when I change my bootloader that it will help.
Click to expand...
Click to collapse
that sounds like a corrupted download. Which browser are you using? Chrome has been known to corrupt downloads.
The other thing to try is, back up all the contents of your sd card. Reformat the card in the phone, boot into amons ra and select partition. set all the values to zero, this will create a FAT32. copy back just the stuff you need back to the sd card, reload the rom to the sd card.
do both wipes, flash and try again.
If its not getting past the installation/flashing stage that has to be an issue with the file itself.
I never solved my issues and resolved that I can only work with certain roms. Tazz's is a great rom and I love it. well, not love but really enjoy it.
which roms are you successful in loading? There may be a connection to the type of riom and what it was based off of. i.e. sprint hero based, or cyanogen or froyo based etc.
Have you tried xtrrom or xtr sense? those loaded with no issues for me.
Aloysius V11 and V12 are both good for me
Roms that don't work for me:
Kaos Froyo (tried so many times, really want to try this one)
any CELB based roms
Nonsensikal v 4.4 and above (3.4 worked great for some reason, just any updates afterwards didn't work.
Jp50 said:
which roms are you successful in loading? There may be a connection to the type of riom and what it was based off of. i.e. sprint hero based, or cyanogen or froyo based etc.
Have you tried xtrrom or xtr sense? those loaded with no issues for me.
Aloysius V11 and V12 are both good for me
Roms that don't work for me:
Kaos Froyo (tried so many times, really want to try this one)
any CELB based roms
Nonsensikal v 4.4 and above (3.4 worked great for some reason, just any updates afterwards didn't work.
Click to expand...
Click to collapse
It really just varies for me.
I can successfully load Evil Eris 4.0 after trying for hours at a time, but if I try to re-flash it again, I get the error.
I can't flash the Froyo ROMs that I have tried either.
The only one that I had absolutely no problem flashing was Evil Eris 3.0
And that's it.
It's quite strange..
Related
Hey all.
I've been trying to flash ShadowROM onto my eris (got the eris dl off their site), but everytime I try to flash it on it gives me "E:missing file: recovery/recovery-from-boot.p" and "E:Verification failed" and then aborts the installation.
So I then tried re-downloading the rom, but the same thing happened again.
Any ideas on what might be going on? I did all my wipes and everything so I'm not really sure what could be going on. Also I have been using Evil Eris for a while, if that makes any difference.
Thanks in advance for any advice.
EDIT: Also I'm currently on 2.1 so I'm not sure if theres anything I need to do to be able to put a 2.2 rom on my eris.
greekstallion said:
Hey all.
I've been trying to flash ShadowROM onto my eris (got the eris dl off their site), but everytime I try to flash it on it gives me "E:missing file: recovery/recovery-from-boot.p" and "E:Verification failed" and then aborts the installation.
So I then tried re-downloading the rom, but the same thing happened again.
Any ideas on what might be going on? I did all my wipes and everything so I'm not really sure what could be going on. Also I have been using Evil Eris for a while, if that makes any difference.
Thanks in advance for any advice.
Click to expand...
Click to collapse
At this time it doesn't work with Amon's recovery. It only will work if you use clockwork, which isn't recommended. I got it to work but I use a rom kitchen and replaced the boot-img.
Busphan said:
At this time it doesn't work with Amon's recovery. It only will work if you use clockwork, which isn't recommended. I got it to work but I use a rom kitchen and replaced the boot-img.
Click to expand...
Click to collapse
Ah I see, hrm I really wanted to give it a try too.
Out of curiosity, why isn't clockwork recommended?
greekstallion said:
Ah I see, hrm I really wanted to give it a try too.
Out of curiosity, why isn't clockwork recommended?
Click to expand...
Click to collapse
There have been a few reports of bricks from just flashing roms.
Busphan said:
At this time it doesn't work with Amon's recovery. It only will work if you use clockwork, which isn't recommended. I got it to work but I use a rom kitchen and replaced the boot-img.
Click to expand...
Click to collapse
You don't need to replace the boot.img....the rom just needs to be signed and it will flash fine amon's. Clockwork can load an unsigned rom but amons can't....
Conap said:
You don't need to replace the boot.img....the rom just needs to be signed and it will flash fine amon's. Clockwork can load an unsigned rom but amons can't....
Click to expand...
Click to collapse
Thanks for the info that would have been easier. I just replace it because of the error message.
**please ignore, sorry!**
Clockwork wont hurt your phone. Also when you go into to clockwork and flash clockwork recovery it will only temp use clockwork as a recovery just to install the rom. After that it will boot into amon.
"Clockwork won't hurt your phone" Boyyyyyyyyy I bet a lot of people with broken eris's would be glad to hear that!
Hungry Man said:
"Clockwork won't hurt your phone" Boyyyyyyyyy I bet a lot of people with broken eris's would be glad to hear that!
Click to expand...
Click to collapse
You running clockwork Hungry Man? I wasn't ever trying to stop anyone, I just wanted them to look into it themselves.
Conap said:
You don't need to replace the boot.img....the rom just needs to be signed and it will flash fine amon's. Clockwork can load an unsigned rom but amons can't....
Click to expand...
Click to collapse
Im not knew to the rooting and flashing thing when it comes to my eris, but i do have to ask for my knowledge: what do you mean by the rom needs to be signed?? thanks!!
duccicucci said:
Im not knew to the rooting and flashing thing when it comes to my eris, but i do have to ask for my knowledge: what do you mean by the rom needs to be signed?? thanks!!
Click to expand...
Click to collapse
He means that this rom will not work with amons recovery because it isn't signed. You can create a zip that isn't sign, meaning you never used a program that signs zips, but you can't flash a zip in amons unless it is signed. So if you just create a zip it probably won't work, but if you use an autosigner then you will be in buisness. I hope this helps, probably not because I have been drinking.
Just so there's full information in case someone finds this thread in the future.
There was a bug with using Clockwork Mod Recovery with the Eris. They squashed it, at least 2-3 months ago.
Besides, you don't have to get rid of amon in order to use clockwork. Just download ROM Manager from the Market and it will make it so that you can load clockwork from amon. Then you get all the advantages of ROM Manager and clockwork without any hassles.
Sent from my xtrSENSE Eris using XDA App
I'm having issues loading the rom, it keeps staying on the 3 skateboarding droids then it reboots back to the skateboarding droids whats going on?
johnny quest said:
I'm having issues loading the rom, it keeps staying on the 3 skateboarding droids then it reboots back to the skateboarding droids whats going on?
Click to expand...
Click to collapse
This seems to be a hit or miss build for the Eris. About 50% (guestimated) of Eris users are unable to boot with v0.2.x and there is no known reason why, even after viewing logcats.
I have dropped the entire desirec device configuration (a mix of kaos & conap) and have forked over a pure conap device config for v0.3.x to attempt to fix this issue. We won't know for sure until v0.3.0 finally releases to the masses. All my testers (even myself) are able to run v0.2.x just fine.
There is no ETA for v0.3.0 at this time.
I'm sorry if this is off topic but I need to ask. Were can you get themes for ShadowRom? Do you just use anything that is for cynogen? Is it best to use metamorph or and update.zip?
I flashed shadowrom using clockmod just fine.
Sent from Eris with Froyo
xtreme3737 said:
I'm sorry if this is off topic but I need to ask. Were can you get themes for ShadowRom? Do you just use anything that is for cynogen? Is it best to use metamorph or and update.zip?
Click to expand...
Click to collapse
We currently have zero themes for the eris. We rely on themers to provide ports, which none have done yet.
Guess I'm one of the lucky ones
billygalbreath said:
This seems to be a hit or miss build for the Eris. About 50% (guestimated) of Eris users are unable to boot with v0.2.x and there is no known reason why, even after viewing logcats.
I have dropped the entire desirec device configuration (a mix of kaos & conap) and have forked over a pure conap device config for v0.3.x to attempt to fix this issue. We won't know for sure until v0.3.0 finally releases to the masses. All my testers (even myself) are able to run v0.2.x just fine.
There is no ETA for v0.3.0 at this time.
Click to expand...
Click to collapse
I flashed this rom and it was slow and jittery and all around not good.
Sent from my ERIS using XDA App
Alright i need help badly. I consider myself an advanced noob in installing roms and kernals on a phone. I have the rezound. I unlocked it about a week about and went through the step by step instructions. I installed ziggys kernal. I was getting some bootloops but not to many until this morning. My phone kept bootlooping. I would take the battery out and put it back and it would do it again. I tried wiping the date cache and dalvik. Nothing. I then formatted all to ext3. After i did that it said i need to install a rom. I try to restart my phone and it just stays on the HTC screen. I tried to do the factory restore. Nothing. I have to put my sd card in after i get into recovery because when i go to the bootloader screen the HBOOT does something and then asks me if i want to do an update. I tried and hit yes and it did it then reboots but nothing. When i hit no it just wants me to reboot my phone, which does nothing for me. As it is right now my phone wont load. it just stays on the HTC screen. HELP please
http://forum.xda-developers.com/showthread.php?t=1394659
Try this, but you should really search first.
I would try that but my phone will not boot. it will not go past the HTC start up screen
Evo4gLI said:
http://forum.xda-developers.com/showthread.php?t=1394659
Try this, but you should really search first.
Click to expand...
Click to collapse
The other half of the problem is that it sounds like he formatted ext3 and wiped his ROM. So, he'd have to reboot back into recovery and restore a backup or drop a new ROM on the phone via USB.
Grab the RUU and start all fresh again.
MrSmith317 said:
The other half of the problem is that it sounds like he formatted ext3 and wiped his ROM. So, he'd have to reboot back into recovery and restore a backup or drop a new ROM on the phone via USB.
Grab the RUU and start all fresh again.
Click to expand...
Click to collapse
Good point. I'm in class, so I just read it quickly. RUU sounds like the way to go.....start with a clean slate.
how do i get to the RUU
See "shipped Rom collection" sticky in dev section
Sent from my ADR6425LVW using XDA App
Good Luck
This is one of the reasons I have not tried to hack this device. Although I may unlock/root my Rezound I'm not in a hurry to. It's really a great device. Just too expensive for me to maybe mess up. Especially since its our own fault if we do. Can't blame the carrier/manufacturer for not paying to fix/replace either. Hopefully you get it fixed soon. I know I wouldn't want to have to go through all that either.
i just installed the CleanRom. Ill let you know if this works
installed cleanrom but now my wifi says error and wont connect
Abead84 said:
installed cleanrom but now my wifi says error and wont connect
Click to expand...
Click to collapse
You need to reflash the kernel in order to get wifi to work.
Abead84 said:
installed cleanrom but now my wifi says error and wont connect
Click to expand...
Click to collapse
The answer should be in the CleanRom thread but as far as I know if you flashed Ziggy's Kernel, you should reflash it and that should solve the problem.
Oops, just noticed this was already answered.
i flashed a kernel and its all good now
Abead84 said:
i flashed a kernel and its all good now
Click to expand...
Click to collapse
Glad you got it all back. That would scare the sh*t out of me
WasabiWa83 said:
Glad you got it all back. That would scare the sh*t out of me
Click to expand...
Click to collapse
It shouldn't. You can't brick with unlock S-On. If you can get to HBOOT, you are fine. And there is no way to overwrite HBOOT yet.
con247 said:
It shouldn't. You can't brick with unlock S-On. If you can get to HBOOT, you are fine. And there is no way to overwrite HBOOT yet.
Click to expand...
Click to collapse
And does it need to be said that this phone has been out for less than a month? Maybe we should give the devs a chance to work out the kinks before we start flashing.
I *really* miss WiFi tethering that I used to do with my DInc, but I am not about to root in the first two weeks of ownership before I see good, dependable feedback from the community.
I love this phone too much.
Sent from my ADR6425LVW using Tapatalk
con247 said:
It shouldn't. You can't brick with unlock S-On. If you can get to HBOOT, you are fine. And there is no way to overwrite HBOOT yet.
Click to expand...
Click to collapse
That's damn good to know
WasabiWa83 said:
That's damn good to know
Click to expand...
Click to collapse
Actually you might be able to mess up the partitions or something, but HTC limits our ability to **** up the phone pretty well
WookieFan said:
And does it need to be said that this phone has been out for less than a month? Maybe we should give the devs a chance to work out the kinks before we start flashing.
I *really* miss WiFi tethering that I used to do with my DInc, but I am not about to root in the first two weeks of ownership before I see good, dependable feedback from the community.
I love this phone too much.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Not trying to knock you but I don't see the point in waiting. Flashing a rom is fairly straightforward and even flashing kernels is for the most part. I had an Incredible prior to this and I am absolutely in love with my phone...that's why I read how to do things properly and learn from others mistakes.
Take the plunge! It's great on the otherside
WookieFan said:
I *really* miss WiFi tethering that I used to do with my DInc
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
There is a wifi tether app that doesn't require root. Koush is the dev. I tried it and it worked. That was the only thing I would have needed root for also. You should be able to find it if you search for it. If not, I'll find the link.
Edit: I found the link
https://plus.google.com/u/0/103583939320326217147/posts/1Yy1jb9z4TA
Sent from my ADR6425LVW using Tapatalk
Ok, I looked around and cannot find an answer that works for me for this issue. I am wondering if it has to do with my phone having S-Off? I am most likely wrong, but i have to know whats going on. No matter what I try, I cannot get My Rezound to go from GB to ICS, ANY ICS BASED ROM for that matter. I checked MD5, Tried with battery door both removed and attached, with or without the SIM card inserted into the phone. The phone boots up almost 100%. I get a message saying "Updating Android" and it says its updating or doing something to 160 apps, the system then reboots, when it gets past the 4G screen again, It says that the boot was completed, I have no signal, i checked on the service type and its correct, tried a factory reset, and still nothing, the system just continues to boot loop over and over again, and when it boots up i cannot get past the Activation screen where it says that the phone is trying to contact Verizon to Auto Activate. I can go back to GB easily, and that works %100. Any and all information would be useful, Only reason why i think this might have to do with S-Off is because my first Rezound was S-On and worked just fine going to ICS, while this new one has S-Off and is just not cutting it.
If you have s-off the rom image could contain a radio update. That could be getting you...also data is off by default in some ICS ROMs.
Sent from my ADR6425LVW using Tapatalk
Sent from my ADR6425LVW using Tapatalk
MrSmith317 said:
If you have s-off the rom image could contain a radio update. That could be getting you...also data is off by default in some ICS ROMs.
Sent from my ADR6425LVW using Tapatalk
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
so what would be recommended in this type of situation? I know its not the data being off thats causing the issue, because when i boot up i dont have a signal at all, and the lock screen instead of showing VZW banner it says No Signal. Would the Radio being an issue also cause boot loop issues?
Did you put the battery cover on the phone ?
Edit saw that u did sorry ...
Sent from my Dinc... I mean Rezound
Only thing i can think of is that the ICS rom you flashed has data off automatically, and requires you to keep pressing the home button until it passes the activation screen.
Also make sure your battery cover is on like yojoe600 said, your antenna is connected to the cover and without it you will have no signal.
who_mike_d said:
Only thing i can think of is that the ICS rom you flashed has data off automatically, and requires you to keep pressing the home button until it passes the activation screen.
Also make sure your battery cover is on like yojoe600 said, your antenna is connected to the cover and without it you will have no signal.
Click to expand...
Click to collapse
this is just sooooooooo irritating. all that i have tried, this is kinda depressing. One interesting thing that i did come across though. When i flashed the BAMF GB, and tried to go from rom to rom to rom, i didnt get any MainVer error.... Dont know if thats just because S-Off allows you to go from one to another freely, or if its just not taking these updates.....
S-off has no mainvar issues. Try putting the gb radio into a PB zip or whatever the resound uses and flash that and boot to see of you get data then
Sent from my ADR6425LVW using XDA App
hey guys, its not just data, the phone is bootlooping on him.
I know several people have s-off devices. You might try looking over on rootzwiki as well. Maybe a dev with s-off can help.
I am one of those people with an s-off and I have had no issues with it but I also updated to the ICS radio AMD have no issues so I'm not totally sure what not working with yours
Sent from my ADR6425LVW using XDA App
werdna87 said:
I am one of those people with an s-off and I have had no issues with it but I also updated to the ICS radio AMD have no issues so I'm not totally sure what not working with yours
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Not sure what is going on with mine that is making it so different. This is just frustrating, last thing that im going to try is going to be flashing th kernel through adb, know that whould not matter too much, but i'll give it a shot, not like it would hurt at all.
dalvear88 said:
Not sure what is going on with mine that is making it so different. This is just frustrating, last thing that im going to try is going to be flashing th kernel through adb, know that whould not matter too much, but i'll give it a shot, not like it would hurt at all.
Click to expand...
Click to collapse
Ok , so i tried this, and as i thought not much happened, more of the same. No real help at Rootz either sadly. I need to find me an S-Off Dev.... lol
On a side note, how would one go about flashing a different recovery.img on an S-Off device, do i have to adb it, or can i do it on the fly? If so, how?
Last thought...did you try the bootloop fix? ##whatever after booting without the battery covery etc...?? There' s a full thread on it.
MrSmith317 said:
Last thought...did you try the bootloop fix? ##whatever after booting without the battery covery etc...?? There' s a full thread on it.
Click to expand...
Click to collapse
yeah was about to give that a go, but the system seems to shut down before i get to the phone portion. I'm having to use the Emergency Call option to get to the dialer since the phone sits on the Self Activation Page.
Before anyone can help you fully and properly, more information needed!
What ROM are you trying to install?
angryPirate12 said:
Before anyone can help you fully and properly, more information needed!
What ROM are you trying to install?
Click to expand...
Click to collapse
what you mean more info, my original post was pretty clear, dont mean to be snappy or anything, i could try to give more info maybe. I've tried all the "fixes" and so far nothing works. ALL AND ANY ICS BASED ROMS are not staying stable on my phone. They get stuck in what i think is the data bootloop, but i cannot access the dial pad other than through the Emergency dial pad, i input the *#*#4636#*#* and nothing comes up, i try without the battery cover, and without the SIM card as well (Also have tried Various combinations of SIM and Battery Cover removals and inclusions). The device has S-Off, and is Unlocked with DevUnlock, and has Perm Root.
Like I stated in my initial post, the leak may contain a radio update that your phone(and the network) isn't ready for. We wouldn't get that update because our radios are locked and only a signed update from HTC would install it. I'd say back down to GB and wait it out...or post in the thread of the ROM maker and ask them about the radio.
dalvear88 said:
what you mean more info, my original post was pretty clear, dont mean to be snappy or anything, i could try to give more info maybe. I've tried all the "fixes" and so far nothing works. ALL AND ANY ICS BASED ROMS are not staying stable on my phone. They get stuck in what i think is the data bootloop, but i cannot access the dial pad other than through the Emergency dial pad, i input the *#*#4636#*#* and nothing comes up, i try without the battery cover, and without the SIM card as well (Also have tried Various combinations of SIM and Battery Cover removals and inclusions). The device has S-Off, and is Unlocked with DevUnlock, and has Perm Root.
Click to expand...
Click to collapse
When I say more info, I mean don't describe every symptom... tell us specifically what you did. Every ICS ROM is unique, like for example I last installed newtoroot's Senseless 4.0.3 ROM. In order to use it, I had to flash a ICS Kernel, I used the fastboot method. Then I could flash the ROM using AmonRa Recovery, and it would boot and operate effectively.
That's the kind of specifics we need, so we can follow your steps and identify possible error points, if any.
angryPirate12 said:
When I say more info, I mean don't describe every symptom... tell us specifically what you did. Every ICS ROM is unique, like for example I last installed newtoroot's Senseless 4.0.3 ROM. In order to use it, I had to flash a ICS Kernel, I used the fastboot method. Then I could flash the ROM using AmonRa Recovery, and it would boot and operate effectively.
That's the kind of specifics we need, so we can follow your steps and identify possible error points, if any.
Click to expand...
Click to collapse
Definetly more descriptive lol thank you for the breakdown infact. In that case, last one i tried what the ICS Sense Redefined, and I tried to use the fastboot method for the Included Kernel as well, but that didnt work at all, what ICS Kernel did you flash to get it to work? a Pre-Packaged one? When installing, I did a full wipe (Both the Amon Ra Factory Reset option and the SuperWipe that is in the Dev Forum) installed the Rom, went into the Bootloader and did ADB CMD of fastboot flash boot boot.img and thats about it.
dalvear88 said:
Definetly more descriptive lol thank you for the breakdown infact. In that case, last one i tried what the ICS Sense Redefined, and I tried to use the fastboot method for the Included Kernel as well, but that didnt work at all, what ICS Kernel did you flash to get it to work? a Pre-Packaged one? When installing, I did a full wipe (Both the Amon Ra Factory Reset option and the SuperWipe that is in the Dev Forum) installed the Rom, went into the Bootloader and did ADB CMD of fastboot flash boot boot.img and thats about it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=22203549&postcount=40
That is the one I used. If you're having issues with fastboot flashing the kernel, you may want to throw the PH98IMG.zip onto your external sd-card and boot into HBOOT then hit vol up to install it that way
angryPirate12 said:
http://forum.xda-developers.com/showpost.php?p=22203549&postcount=40
That is the one I used. If you're having issues with fastboot flashing the kernel, you may want to throw the PH98IMG.zip onto your external sd-card and boot into HBOOT then hit vol up to install it that way
Click to expand...
Click to collapse
ok, i'll give this a shot really quick and do through ext. sd. thanks for the link btw, you've been extremely helpful. let ya know how this goes for me.
Okay I have been trying to get a CM9 rom to boot on my Atrix for about a week now. I am coming from Nottachtrix 1.3.1 on radio 37p with faux GB24 kernel. My bootloader is unlocked and I perform all necessary wipes before install. The furthest I have gotten any of the CM9 roms to boot is the screen that states Android Apps(or something) updateing. It then states starting system and boots back to the booting logo. I have tried fastboot -w. Formating data, cache, system, osh, pre install in mounts storage menu, and clearing both caches before and after install and I get the same results. This only happens with CM9 roms. I cannot get the CNA, Jokers, Turls, or Atrix tablet past the screen stated. I have tried with the latest rom racer from http://forum.xda-developers.com/showthread.php?t=1204500 and both recovery and touch recovery from rom manager and I get the same results. I have posted my issue in the dev section, but decided this was better as I did not want to clutter up the dev forum with my problems. Could it just be my Atrix or would the 37p radio have something to do with the bootlooping issue. Any help would be very much appreciated.
For some odd reason I decided to pull my external SD card before boot, and freaking BOOM BANG POW NO BOOTLOOP!
htcslic said:
Okay I have been trying to get a CM9 rom to boot on my Atrix for about a week now. I am coming from Nottachtrix 1.3.1 on radio 37p with faux GB24 kernel. My bootloader is unlocked and I perform all necessary wipes before install. The furthest I have gotten any of the CM9 roms to boot is the screen that states Android Apps(or something) updateing. It then states starting system and boots back to the booting logo. I have tried fastboot -w. Formating data, cache, system, osh, pre install in mounts storage menu, and clearing both caches before and after install and I get the same results. This only happens with CM9 roms. I cannot get the CNA, Jokers, Turls, or Atrix tablet past the screen stated. I have tried with the latest rom racer from http://forum.xda-developers.com/showthread.php?t=1204500 and both recovery and touch recovery from rom manager and I get the same results. I have posted my issue in the dev section, but decided this was better as I did not want to clutter up the dev forum with my problems. Could it just be my Atrix or would the 37p radio have something to do with the bootlooping issue. Any help would be very much appreciated.
Click to expand...
Click to collapse
Did you flash twice ?
Sent from my MB860 using XDA
I believe the problem is with the radio, I had this issue (on stock radio), then I upgraded to the newest CM9 Kang (0.4.4) and it went away. I then flashed the 37p radio in an attempt to fix a problem I've been having with my WiFi and bluetooth (they both don't work and cause reboots, I assume now it's a hardware problem) and the boot loop came back. I'm gonna try flashing some other radios to see if that works.
Yes flashed twice to no avail. Gonna try the 36p radio and stock to see if that fixes my issue.
Sent from my Wettest Dream Atrix!
giqbal said:
Did you flash twice ?
Sent from my MB860 using XDA
Click to expand...
Click to collapse
No need to flash any ROM twice. Not going to discuss other than to say its not require
OP......Not your phone or radio. There is something you are doing incorrectly. Quite possibly wipe procedure. If I remember when I am at my PC in the morning I will PM you exact instructions, start to finish, for flashing one of the CM9 builds.
Sent from my MB860 using xda premium
CaelanT said:
No need to flash any ROM twice. Not going to discuss other than to say its not require
OP......Not your phone or radio. There is something you are doing incorrectly. Quite possibly wipe procedure. If I remember when I am at my PC in the morning I will PM you exact instructions, start to finish, for flashing one of the CM9 builds.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Trust me, the CM9 kang (not turl's version, haven't tried that) didn't work unless you flashed it twice up to version 0.4.2 (I skipped 0.4.3 and installed 0.4.4 straight without wiping and only flashed once and it worked, so it's possible they fixed the bug). I don't think anyone knows why, but it's been confirmed many times.
CaelanT said:
No need to flash any ROM twice. Not going to discuss other than to say its not require
OP......Not your phone or radio. There is something you are doing incorrectly. Quite possibly wipe procedure. If I remember when I am at my PC in the morning I will PM you exact instructions, start to finish, for flashing one of the CM9 builds.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
That is what I am hoping, but I have tried every procedure I could find within the forums. Your start to finish is gonna be my last hope.
So I followed the same steps I use for other roms and managed to get this one working http://forum.xda-developers.com/showthread.php?t=1580449
Hey CaelanT any luck on getting me a step by step.
hitmannumber47 said:
Trust me, the CM9 kang (not turl's version, haven't tried that) didn't work unless you flashed it twice up to version 0.4.2 (I skipped 0.4.3 and installed 0.4.4 straight without wiping and only flashed once and it worked, so it's possible they fixed the bug). I don't think anyone knows why, but it's been confirmed many times.
Click to expand...
Click to collapse
Haven't had to do that with jokersax, turl, or CNA versions.
---------- Post added at 12:24 PM ---------- Previous post was at 12:24 PM ----------
htcslic said:
Hey CaelanT any luck on getting me a step by step.
Click to expand...
Click to collapse
Thanks for reminding me. Will get something to you here in a few!
<edit> Check your messages!
Gonna give it a shot soon as I get off work.
EDIT:
Unfortunately that was a no go as well. Followed everything to a tee and tried different kernels. I can only get the AOKP rom to boot, but its is currently without USB storage. Does anyone know a difference in the roms that would cause my Atrix to boot on one and not the other. I can also manage to get the MIUI to boot.
htcslic said:
Gonna give it a shot soon as I get off work.
EDIT:
Unfortunately that was a no go as well. Followed everything to a tee and tried different kernels. I can only get the AOKP rom to boot, but its is currently without USB storage. Does anyone know a difference in the roms that would cause my Atrix to boot on one and not the other. I can also manage to get the MIUI to boot.
Click to expand...
Click to collapse
I think something is going on with the kernel. You may have a bad processor. That's where my train of thought is right now. Sorry I couldn't get you up and running!
CaelanT said:
I think something is going on with the kernel. You may have a bad processor. That's where my train of thought is right now. Sorry I couldn't get you up and running!
Click to expand...
Click to collapse
Thanks for all you help. Finally got it to boot by removing external sd card.
[EDIT] Not sure but I believe the problem I had with m external sd is I still had an ext4 primary partition on it from when I was using Webtop2SD. Copying everything over to pc now and reformating external to see if my assumption is correct.
Looks like the ext4 partition on as was the culprit.
Sent from my Flipping ArtixTab!
I used to be able to flash and boot any cm10 rom just fine but just recently, I haven't been able to for some reason. After flashing and trying to boot up, it'll show the boot animation for a split second before rebooting. I've tried everything, formatting sd card, flashing different radios and hboots, different recoveries, and nothing works. I'm currently using the latest firmware, baseband, and 1.04 eng hboot s off. Does anybody know what's wrong?
mathlete777 said:
I used to be able to flash and boot any cm10 rom just fine but just recently, I haven't been able to for some reason. After flashing and trying to boot up, it'll show the boot animation for a split second before rebooting. I've tried everything, formatting sd card, flashing different radios and hboots, different recoveries, and nothing works. I'm currently using the latest firmware, baseband, and 1.04 eng hboot s off. Does anybody know what's wrong?
Click to expand...
Click to collapse
I wish I did. I've had the exact same issues. Above and beyond what you've already done, I've also sifted through many recovery logs and last_kmsg and fastboot flashed the boot.img
hockeyfamily737 said:
I wish I did. I've had the exact same issues. Above and beyond what you've already done, I've also sifted through many recovery logs and last_kmsg and fastboot flashed the boot.img
Click to expand...
Click to collapse
Ah at least I'm not the only one. Hopefully someone knows the problem.
My phone had the same issue where most roms wouldn't flash properly. What worked for me: run the ruu.exe. You'll still be s-off, but everything else will be back to stock. Flash a custom hboot and recovery and then flash a ROM.
I've tried that too and it also didn't work unfortunately.
mathlete777 said:
I've tried that too and it also didn't work unfortunately.
Click to expand...
Click to collapse
Can you boot Sense ROM's OK. Were you able to boot the stock ROM after flashing the RUU?
ramjet73
ramjet73 said:
Can you boot Sense ROM's OK. Were you able to boot the stock ROM after flashing the RUU?
ramjet73
Click to expand...
Click to collapse
I can't speak for mathlette777, but I've had no problems booting any Sense roms, on default, Mac, or Buttered Toast kernels. CM10 / AOSP roms booted fine until about 3 weeks ago (maybe a month), then suddenly without cause or warning they just refused to make it more then a fraction of a second into the boot animation if they got there at all. After looking at my recovery logs, last_kmsg, and last_dmsg and seeing no one else with the same problem I chalked it up to a hardware issue.
hockeyfamily737 said:
I can't speak for mathlette777, but I've had no problems booting any Sense roms, on default, Mac, or Buttered Toast kernels. CM10 / AOSP roms booted fine until about 3 weeks ago (maybe a month), then suddenly without cause or warning they just refused to make it more then a fraction of a second into the boot animation if they got there at all. After looking at my recovery logs, last_kmsg, and last_dmsg and seeing no one else with the same problem I chalked it up to a hardware issue.
Click to expand...
Click to collapse
That's the exact problem I had hockey (could only boot sense 3.6 roms here, not even sense 3 or 4 let alone aosp, etc). Running the ruu fixed it for me.
hockeyfamily737 said:
I can't speak for mathlette777, but I've had no problems booting any Sense roms, on default, Mac, or Buttered Toast kernels. CM10 / AOSP roms booted fine until about 3 weeks ago (maybe a month), then suddenly without cause or warning they just refused to make it more then a fraction of a second into the boot animation if they got there at all. After looking at my recovery logs, last_kmsg, and last_dmsg and seeing no one else with the same problem I chalked it up to a hardware issue.
Click to expand...
Click to collapse
I just wanted to make sure that he flashed the RUU successfully. He said he had no recovery but that shouldn't be if the RUU was successful and he should be able to boot into the stock recovery even though you can't do much with it. Also, if he can't boot the Sprint stock ICS ROM after flashing the RUU then he has something else wrong.
Have you tried flashing the RUU yet?
ramjet73
ramjet73 said:
Have you tried flashing the RUU yet?
ramjet73
Click to expand...
Click to collapse
Nah.... To much hassle to set up a Windows machine just to run an RUU on a phone that runs everything else OK.
Sent from my PG86100 using Tapatalk 2
hockeyfamily737 said:
Nah.... To much hassle to set up a Windows machine just to run an RUU on a phone that runs everything else OK.
Click to expand...
Click to collapse
Well, you could flash the zip version from this post from the bootloader instead.
ramjet73
I'll try flashing the ruu again and see if it works. I can currently boot any sense rom even the 4+ ones fine. Anything based off cm10 doesn't work though.
update: so I've flashed the RUUs from the bootloader and got that working then flashed all my old stuff back and I still can't boot cm10 roms. Just shows the boot screen for a split second then reboots.
mathlete777 said:
update: so I've flashed the RUUs from the bootloader and got that working then flashed all my old stuff back and I still can't boot cm10 roms. Just shows the boot screen for a split second then reboots.
Click to expand...
Click to collapse
Just saw this update. Same results here. We're cursed to stay on Sense for as long as we have these phones lol.
Sent from my PG86100 using Tapatalk 2