Related
I'll give my question first, then the history. I tried to search the EVO 4G subforums and couldn't seem to find it. If there's a post on this please kindly point me in the right direction.
Regardless of which ROM I install on my EVO except for what I understand is the engineering ROM or possibly the stock ROM, I go into a boot loop.
History:
- Did not install any updates or use unrevoked after receiving my EVO
- Did the root method known as "part 1" before NAND unlocking was available, never did any system updates. It seemed I had root because I was able to use the sudo "allow" or "deny" and use Wifi Tether in AP mode successfully (the open source APK)
- Was having some random reboot issues so I decided I needed to finally get an updated, custom ROM on my phone
- Yesterday spent many hours trying to get SimpleRoot to root my phone. However, ROM Manager keeps complaining it can't do privileged commands
- I was able to get Clockwork Recovery onto my phone finally using Unrevoked 3 just to get it on there (with what I know as the engineering ROM)
- Used clockwork to try and install Fresh 1.0.1, DamageControl v3.1.2 or seemingly anything other than that same engineering ROM (that has the HTC logo and sound) puts it into a boot loop. Also Clockwork (the APK) complains it still can't run privileged commands on that ROM from SimpleRoot.
I've been flashing a Kaiser/Tilt since forever but still pretty newb on Android but trying to learn fast. Love my EVO!
If there is any more information I can provide to help someone help me please let me know and hopefully this can help others not go astray as I have...
EDIT: Oh, yes and I read some of the troubleshooting information for different ROMs and one said to reformat sd-ext but my SD card is just formatted how it comes from the factory. I would really like to keep it that way unless it is a must for installing custom ROMs on the EVO. Clockwork did not seem to be able to do the partitioning for me.
EDIT: Now resolved after following thoroughly the directions listed here:
http://forum.xda-developers.com/showthread.php?t=721055
Thanks for helping me out!
aikeru said:
I'll give my question first, then the history. I tried to search the EVO 4G subforums and couldn't seem to find it. If there's a post on this please kindly point me in the right direction.
Regardless of which ROM I install on my EVO except for what I understand is the engineering ROM or possibly the stock ROM, I go into a boot loop.
History:
- Did not install any updates or use unrevoked after receiving my EVO
- Did the root method known as "part 1" before NAND unlocking was available, never did any system updates. It seemed I had root because I was able to use the sudo "allow" or "deny" and use Wifi Tether in AP mode successfully (the open source APK)
- Was having some random reboot issues so I decided I needed to finally get an updated, custom ROM on my phone
- Yesterday spent many hours trying to get SimpleRoot to root my phone. However, ROM Manager keeps complaining it can't do privileged commands
- I was able to get Clockwork Recovery onto my phone finally using Unrevoked 3 just to get it on there (with what I know as the engineering ROM)
- Used clockwork to try and install Fresh 1.0.1, DamageControl v3.1.2 or seemingly anything other than that same engineering ROM (that has the HTC logo and sound) puts it into a boot loop. Also Clockwork (the APK) complains it still can't run privileged commands on that ROM from SimpleRoot.
I've been flashing a Kaiser/Tilt since forever but still pretty newb on Android but trying to learn fast. Love my EVO!
If there is any more information I can provide to help someone help me please let me know and hopefully this can help others not go astray as I have...
EDIT: Oh, yes and I read some of the troubleshooting information for different ROMs and one said to reformat sd-ext but my SD card is just formatted how it comes from the factory. I would really like to keep it that way unless it is a must for installing custom ROMs on the EVO. Clockwork did not seem to be able to do the partitioning for me.
Click to expand...
Click to collapse
i had a similar issue, and so did a few people. i wrote out a post some time ago, i don't know if you read it...
http://forum.xda-developers.com/showpost.php?p=7204861&postcount=4
try that out. let me know how it goes.
EDIT: it also sounds like you don't have nand unlocked.
Thank you for your quick reply! I will try it and report back what I did, what works/didn't.
As a side note...
Since I have Clockwork on the recovery (I can boot to recovery all day long just using volume up and clockwork is there) doesn't that mean NAND is unlocked? Anyway, thank you again.
aikeru said:
Thank you for your quick reply! I will try it and report back what I did, what works/didn't.
As a side note...
Since I have Clockwork on the recovery (I can boot to recovery all day long just using volume up and clockwork is there) doesn't that mean NAND is unlocked? Anyway, thank you again.
Click to expand...
Click to collapse
having a boot recovery program doesn't necessarily mean you have nand unlocked. the ability to flash custom roms does though. good luck! i know it's frustrating, but keep at it.
silly question but are you wiping correctly ?
I had to ask...
elegantai said:
silly question but are you wiping correctly ?
I had to ask...
Click to expand...
Click to collapse
i almost spilled my drink LOL
elegantai said:
silly question but are you wiping correctly ?
I had to ask...
Click to expand...
Click to collapse
lol XD nice ... any comeback I can think of just goes way too far
Well, I've downloaded the files so sometime this evening/tonight I should have results. That post links to what appears to be a very, very thorough set of instructions
http://forum.xda-developers.com/showthread.php?t=721055
So I'll go through the whole thing there and of course report back
aikeru said:
lol XD nice ... any comeback I can think of just goes way too far
Well, I've downloaded the files so sometime this evening/tonight I should have results. That post links to what appears to be a very, very thorough set of instructions
http://forum.xda-developers.com/showthread.php?t=721055
So I'll go through the whole thing there and of course report back
Click to expand...
Click to collapse
lol good luck buddy. it's a relatively easy walkthrough if you follow it closely. post up any questions you have.
when i try to restore my nandroid it says error flashing boot image please help
That happened to me once. I think the actual file was corrupt because I was able to restore from a different nandroid. Do you have any others saved that you can try?
I don't remember that exact error message (I actually think it might have been different), but a very similar (or identical) error can occur of on backup/restore you have a low battery, low disk space or have renamed the directories.
What recovery are you using?
Do you have other backupsyou can try?
Are you trying to restore a clockwork backup with ra, or an ra backup with clockwork?
Sent from my blah blah blah blah
Once you get through this (best option, use one of the other Nandroid backups if you have them), download and install Titanium Backup, I trust it more than Nandroid's backup. Heck use both before you install ROMS and make any major changes. Just a thought...
rcbarr said:
Once you get through this (best option, use one of the other Nandroid backups if you have them), download and install Titanium Backup, I trust it more than Nandroid's backup. Heck use both before you install ROMS and make any major changes. Just a thought...
Click to expand...
Click to collapse
Wait, what?
It's not like you have a choice to do one or the other, nand and titanium do totally different things. You should always do a nand backup before flashing anything, regardless if you use tb...unless I misunderstood what you're saying...
Sent from my blah blah blah blah
I am having this same problem. i switched from the regular sense rom to CM 6 rs2. i can load cm6 backups all day long but my sense rom gives me an error when i try to load it saying "clockwork mod error while flashing boot image!". Both nandroid backups were made with clockworkmod. I had to downgrade my version of hboot to install cm6. I am wondering if i need to upgrade it again to load my original sense rom or am i wrong in thinking this?
DaKlown said:
I am having this same problem. i switched from the regular sense rom to CM 6 rs2. i can load cm6 backups all day long but my sense rom gives me an error when i try to load it saying "clockwork mod error while flashing boot image!". Both nandroid backups were made with clockworkmod. I had to downgrade my version of hboot to install cm6. I am wondering if i need to upgrade it again to load my original sense rom or am i wrong in thinking this?
Click to expand...
Click to collapse
OP didn't give as much detail as you - good example of how details help.
You can only restore backups you made with the same version of hrboot. You can't restore a .79 backup while running .76 (which I'm pretty sure is what you downgraded to in order to load cm6).
Now I need to find flashable zips of both hboots so I can switch between cm6 and sense. I so miss my 4g lol. Thanks for your help!
I upgraded hboot to .79 and still got the same error. Funny thing is that my cm6 loaded fine and my hboot is still reading .79 anyone have any clue as to why sense wont load and why cm6 loaded on a different hboot?
did you ever get this figured out? i am in the exact same boat.
i rooted with unrevoked 3.21, this went well
i backed up oem sense in recovery via nandroid, this worked, i wiped and restored from this backup just to test, again the restore worked just fine.
later i tried to flash cm6 but all arrows pointing towards not having the right hboot. i dont remmeber what i had but i needed to got to eng boot .76.2000, which i finaly got figured out and was able to flash to cm6.
at this point cm6 loads and runs juts fine, i decided to boot to recovery and do a backup via nandroid, infact i did two of these back ups. i wiped my phone and did a restore just to test these back ups.
heres my problem: just for the fun of it i thought i would try to use the first nadroid back up to restore (that had stock sense installed at the time) and it wont flash. it says something about:
"Checking MD5 sums…
Erasing boot before restore…
Restoring boot image…
Error while flashing boot image!"
i thought i found a fix: i need to "Switch .76 with .79", this still did not allow me to restore from my oem sense backup, i get the exact same error.
i found another potential fix pertaining to going back to .93.
i feel like i dont know enough about what i am doing and im abit scared to try this as i dont see much info on this method.
basicaly i'd lile to be able to go back and forth between stock and custom for a while and also i'd like to be able to use nandroid backups to quickly do this.
am i approaching my problem correctly pertaining to the hboot thing? and can i just drop the .76,.79, 93. images in and out of the pc36image.zip file that i will place on root on my sd card with out anything else in this zip and expect it to just work?
i was able to achieve my objective and then some. now i can restore to a cm6 or a oem rom in a matter of maybe 5 or ten minutes.
maybe it wasn't directly the way i wanted to do it but i think it was similar enough that it worked without me understanding what i was doing therefore keeping me out of the mix which is why it probably worked.
what ui did was i found a ruu.exe for 3.29, i downloaded it and ran it
once it was done i ran unrevoked to get root again and the boot loader installed, i think the .97 boot loader was key here, but i dont know.
then i booted to recovery and did a nandbackup
then i did a nand recovery to my older backups of cm6-success
then i did a nand recovery of a older oem 3.29 sense rom- success
im sure that i rambled on here and i never really knew what i was doing but i was able to do what i set out to do and then some. if only we could dual boot roms.....
potna said:
i was able to achieve my objective and then some. now i can restore to a cm6 or a oem rom in a matter of maybe 5 or ten minutes.
maybe it wasn't directly the way i wanted to do it but i think it was similar enough that it worked without me understanding what i was doing therefore keeping me out of the mix which is why it probably worked.
what ui did was i found a ruu.exe for 3.29, i downloaded it and ran it
once it was done i ran unrevoked to get root again and the boot loader installed, i think the .97 boot loader was key here, but i dont know.
then i booted to recovery and did a nandbackup
then i did a nand recovery to my older backups of cm6-success
then i did a nand recovery of a older oem 3.29 sense rom- success
im sure that i rambled on here and i never really knew what i was doing but i was able to do what i set out to do and then some. if only we could dual boot roms.....
Click to expand...
Click to collapse
You are doing exactly what I am trying to do, and ran into the same trouble.
Seems like having to run unrevoked again is unnecessary. There must be a way to switch the boot loader without it ? Did you ever find a quicker way?
I feel pretty comfortable messing with this stuff, even though I am new to the EVO. That said, I really do not want to brick it doing something stupid. Messing with these boot loaders does scare me a bit.
potna said:
did you ever get this figured out? i am in the exact same boat.
i rooted with unrevoked 3.21, this went well
i backed up oem sense in recovery via nandroid, this worked, i wiped and restored from this backup just to test, again the restore worked just fine.
later i tried to flash cm6 but all arrows pointing towards not having the right hboot. i dont remmeber what i had but i needed to got to eng boot .76.2000, which i finaly got figured out and was able to flash to cm6.
at this point cm6 loads and runs juts fine, i decided to boot to recovery and do a backup via nandroid, infact i did two of these back ups. i wiped my phone and did a restore just to test these back ups.
heres my problem: just for the fun of it i thought i would try to use the first nadroid back up to restore (that had stock sense installed at the time) and it wont flash. it says something about:
"Checking MD5 sums…
Erasing boot before restore…
Restoring boot image…
Error while flashing boot image!"
i thought i found a fix: i need to "Switch .76 with .79", this still did not allow me to restore from my oem sense backup, i get the exact same error.
i found another potential fix pertaining to going back to .93.
i feel like i dont know enough about what i am doing and im abit scared to try this as i dont see much info on this method.
basicaly i'd lile to be able to go back and forth between stock and custom for a while and also i'd like to be able to use nandroid backups to quickly do this.
am i approaching my problem correctly pertaining to the hboot thing? and can i just drop the .76,.79, 93. images in and out of the pc36image.zip file that i will place on root on my sd card with out anything else in this zip and expect it to just work?
Click to expand...
Click to collapse
I'm having the same problem, but I don't have the luxury of either Sense or Cyanogen working--I'm just permanently stuck inside the ClockworkMod Recovery and can't get back to a nandroid restore point I've verified in the past as working.
Is there something I can do to remove the pc36img.zip file? How?!
I have amon_ra and I ran into this issue a while back too. You most likely got this error due to your battery level being too low. Turn your phone off, charge the battery for a while and try again.
http://forum.xda-developers.com/showthread.php?t=705026&highlight=%5Brecovery%5D
Near the top of his post it states your battery must be atleast 30%, in red text.
Sent from my HTC Evo 4g
I have been rooted for a while now and had bakedsnack 1.4 installed for about 2 months now. Everything was stable until a few days ago when it started rebooting randomly then much more often so I decided it was to time to update...went for Ava v9. After reseting factory defaults, wiping cache, wiping dalvik, I installed the rom. Immediate infinite loop reboot, tried this rom 2 more times then the newest baked snack then the plain rooted stock. All are infinite reboot loops...I have wiped numerous times now and can't seem to find a problem, I have updated my radios and everything trying to fix this to no avail. I could really use some help...here is a catlog of my bootup and 2 of the infinite reboots after a clean install.
pastebin.com/jBub3Upf
Also using amon-ra recovery and my root is full nand unlock.
same thing is happening to me. plz help. ava v9 running both stock kernel and kings 10 cfs. plz help. plz. i have the exact same problem. plz. i am bagging you. plz.
plz.
dk
Have you guys tried running a stock PC36IMG? That is the first thing I would try if I was in your shoes.
link to file: http://forum.xda-developers.com/showthread.php?t=791019
_MetalHead_ said:
Have you guys tried running a stock PC36IMG? That is the first thing I would try if I was in your shoes.
link to file: http://forum.xda-developers.com/showthread.php?t=791019
Click to expand...
Click to collapse
i have tried unrooting and rerooting, but not flashing a stock pc36img.zip. thanks for the link. megafileupload is wired do you mind sending me a mirror? i will post results. if that doesnt work, i am unrooting nd trying again. if that still doesnt work, i am bricked
dkdude36 said:
i have tried unrooting and rerooting, but not flashing a stock pc36img.zip. thanks for the link. megafileupload is wired do you mind sending me a mirror? i will post results. if that doesnt work, i am unrooting nd trying again. if that still doesnt work, i am bricked
Click to expand...
Click to collapse
devs, i'm not sure you get how serious this problem is, and how badly it needs fixing. i reboot any time i open a network connection. for example, when i boot up, even before htc sense loads, i reboot. i cannot stay up for more than 15 seconds. i have forcefully deleted all apps that even remotely might require data, and still somehow, i sync to my voicemail. boot up, pull down lock, reboot, stuck. plz help me i want to be able to use my phone.
dkdude36 said:
i have tried unrooting and rerooting, but not flashing a stock pc36img.zip. thanks for the link. megafileupload is wired do you mind sending me a mirror? i will post results. if that doesnt work, i am unrooting nd trying again. if that still doesnt work, i am bricked
Click to expand...
Click to collapse
Have you been able to get it downloaded? I just tried to dl it from megaupload again and it worked no prob.
Downloading it now, will try it out. Thanks!
download went fine. about to push and flash. wish me luck... i just want my evo back waaaaa
flashed it. first try, boot failed because of a pu fail. stuck in bootloader. tried agian, and worked fine. my phone is rebooting as we speak. lets see if it worked...
and the big question: should i stick with ava v9 or what other rom should i try? i have never tried fresh, and cyanogen is too unstable for me. i have pretty much only tried ava, omj, and cm. plz recommend the must tries etc. i'm not asking you to choose for me, just tell me what to try.
dk
SHOOT IT STILL WONT WORK! i booted just fine, and was able to set up just the google account. the second i hit finish for the google account only and it tried to sync contacts, reboot. please help me knowledgable people!
EDIT: once i rebooted, i dragged down unlock screen and BAM! reboot... sad me i just want my evo back
dkdude36 said:
flashed it. first try, boot failed because of a pu fail. stuck in bootloader. tried agian, and worked fine. my phone is rebooting as we speak. lets see if it worked...
and the big question: should i stick with ava v9 or what other rom should i try? i have never tried fresh, and cyanogen is too unstable for me. i have pretty much only tried ava, omj, and cm. plz recommend the must tries etc. i'm not asking you to choose for me, just tell me what to try.
dk
Click to expand...
Click to collapse
I had the EXACT same problem as you. Was the PU fail next to the boot line during the update? If so, then I think you've got bad blocks in your boot partition and I hate to say it but you might not be able to flash any custom kernels anymore. Once I finally got mine booted, the only kernel that worked was a stock one. I was able to flash Fresh, but HAD to keep the kernel stock. I ended up calling Asurion and filed a claim. Got my new evo today and am having no issues.
SHOOT IT STILL WONT WORK! i booted just fine, and was able to set up just the google account. the second i hit finish for the google account only and it tried to sync contacts, reboot. please help me knowledgable people!
EDIT: once i rebooted, i dragged down unlock screen and BAM! reboot... sad me i just want my evo back
Click to expand...
Click to collapse
That sucks man. Do what I did, file an insurance claim and get a new phone. They ship it out next day.
same problem I'm having:
http://forum.xda-developers.com/showthread.php?t=808280
ok i think i finally have it. but now, what rom to use? please tell me. i might be going with the cm nightlies. but plz give your opinion. thanks for the stock pc...zip. tweetqit, thanks for letting me overrun your thread..ha
TO GET IT TO WORK, ONCE YOU ARE STUCK IN BOOTLOADER, JUST RE-UPDATE AND THE BAD BLOCKS WILL GO AWAY. OR AT LEAST THAT WORKED FOR ME.
Yup, failed for me the first time but worked the second. My phone was never the same after I went through that ordeal. No custom kernels worked, terribly sluggish performance, constant reboots. That's why I said f*ck it and had Asurion send me a new one.
dkdude36 said:
ok i think i finally have it. but now, what rom to use? please tell me. i might be going with the cm nightlies. but plz give your opinion. thanks for the stock pc...zip. tweetqit, thanks for letting me overrun your thread..ha
TO GET IT TO WORK, ONCE YOU ARE STUCK IN BOOTLOADER, JUST RE-UPDATE AND THE BAD BLOCKS WILL GO AWAY. OR AT LEAST THAT WORKED FOR ME.
Click to expand...
Click to collapse
what'd you do? what exactly did it fix? everything?
On first try, boot: fail-PU. I guess this is a common problem? pretty lame. Will post after I try again.
Ok so now that, that failed..how do I try it again? when I reboot into recovery it just checks the PC36IMG.ZIP and dumps me back to the bootloader without asking me to install it...
I've done what I think dkdude36 did [install PC36IMG] and did get PU fail, and now i'm stuck in HBOOT/BOOTLOADER as expected. Now I only have the few options in bootloader and don't know what to do. I've rebooted and gotten the bootloops then wen't back into bootloader and it loads PC36IMG but it doesn't give me the option to update again. Am I supposed to do something in order for it to give me that option again? If so, what? As of now, I'm stuck and am bricked (hopefully not permanently).
Tweeqit2 said:
Ok so now that, that failed..how do I try it again? when I reboot into recovery it just checks the PC36IMG.ZIP and dumps me back to the bootloader without asking me to install it...
Click to expand...
Click to collapse
what if we run:
fastboot erase boot
fastboot erase recovery
what will happen? will it prompt me to update with PC36IMG.zip as it did the first time?
Ok, so here is what I have done: I have already rooted my phone, etc, and have flashed some different roms on my phone, and have not had any problems until now. I recently tried the miui rom, but didn't like it.I just flashed the newest miui rom, and it was acting really weird, so I decided to go back to the virtuous rom which I had used before. For whatever reason, I am getting this error: E: can't mount /dev/block/mmcblk0p1 (file exists), and the installation aborts. I did the wipe data deal, and I also tried to reinstall the miui rom. It says that installs fine, but it won't get past the htc incredible screen. Any suggestions? Also, I didn't want to try this and mess things up further, but can I restore a backup I had done when I had the virtuous rom installed, or do I have to have the rom already working properly? Kind of a noob question, I know.
calamari85 said:
Ok, so here is what I have done: I have already rooted my phone, etc, and have flashed some different roms on my phone, and have not had any problems until now. I recently tried the miui rom, but didn't like it.I just flashed the newest miui rom, and it was acting really weird, so I decided to go back to the virtuous rom which I had used before. For whatever reason, I am getting this error: E: can't mount /dev/block/mmcblk0p1 (file exists), and the installation aborts. I did the wipe data deal, and I also tried to reinstall the miui rom. It says that installs fine, but it won't get past the htc incredible screen. Any suggestions?
Click to expand...
Click to collapse
Hmmm... Do you have any Nandroids from earlier roms? That'd be the easiest route.
If not, since you can't even get to a homescreen, you might try an RUU reset, but let's hope it won't come to that for now.
I get that too, but only when going into the menu for Dalvik Cache wiping, and it never actually gets in my way, it just pops up and then I can keep going on about my business.
1. yes you can restore the backup whether a rom is currently working or not
2. post questions in the correct forum
If you can't get a nandroid backup to work, you may have to RUU back to stock.
Here's the older one that will still let you use unrevoked after. Just rename this PB31IMG.zip, load up H-boot, follow the prompts, and be patient. Then run unrevoked when it finishes and install rom manager to restore your backup. If the backup still won't work, try a fresh install of virtuous.
Sorry
g00s3y said:
1. yes you can restore the backup whether a rom is currently working or not
2. post questions in the correct forum
Click to expand...
Click to collapse
My apologies, where should I have posted? And can I move the thread so it is in the correct place?
calamari85 said:
My apologies, where should I have posted? And can I move the thread so it is in the correct place?
Click to expand...
Click to collapse
Probably in the Q & A General Forum, but don't worry about it this time, just as long as it doesn't end up being a frequent thing.
But I don't know about being able to move the thread, I think that's a Moderator power.
Regarding your issue though, either use the RUU link posted above, or try Nandroid-ing back.
No go
I tried restoring a backup, and got cannot mount /data, along with the previous error... It changed my boot animation, but has not restored my phone. should I do this RUU back to stock? Sorry for not being very good at this, and I definitely appreciate the help.
calamari85 said:
I tried restoring a backup, and got cannot mount /data, along with the previous error... It changed my boot animation, but has not restored my phone. should I do this RUU back to stock? Sorry for not being very good at this, and I definitely appreciate the help.
Click to expand...
Click to collapse
It's cool.
Yes, you'll need it on the root of your SD-card (not in any folders), run it through hboot, and then you'll have to re-run the unrEVOked tool from your PC. I would also suggest running the S-Off tool afterwards, just to be safe. That has saved me once before.
Make sure you have at least 50% battery before you do the hboot flash. VERY IMPORTANT. If your phone dies or loses power while updating the radio files from the RUU, your phone is as good as bricked.
If you get stuck with the unrEVOked tool at waiting for root for more than fifteen minutes, post back here again and we'll continue from there.
EDIT: Actually, run the unrEVOked Forever S-Off tool through CWM recovery before doing this, as a pure precautionary measure.
I'm an idiot apparently
Well, I am really sorry guys, I won't ask any more questions on here. Apparently I am super stupid. I figured it out, I left out some info because it didn't even register as relevant, but it was the key apparently. So I just go a new sd card, and I formated it on my computer, and just dropped the zip files on there, and was trying to flash like that, and apparently the phone didn't like the new sd card, or it needed info off the old one, because once I put it back in and tried flashing from it, it works fine now. Sorry for bothering everyone, I am going to go sit in the corner in shame now.
calamari85 said:
Well, I am really sorry guys, I won't ask any more questions on here. Apparently I am super stupid. I figured it out, I left out some info because it didn't even register as relevant, but it was the key apparently. So I just go a new sd card, and I formated it on my computer, and just dropped the zip files on there, and was trying to flash like that, and apparently the phone didn't like the new sd card, or it needed info off the old one, because once I put it back in and tried flashing from it, it works fine now. Sorry for bothering everyone, I am going to go sit in the corner in shame now.
Click to expand...
Click to collapse
Hahaha! No worries, we all have our moments!
Glad you figured it out. Be sure to make a backup of your current rom on your new SD card right away haha.
Hey all,
I'm trying to install either CM10 or the Lifeless ROM (links here and here: http://forum.xda-developers.com/showthread.php?t=2189788 and http://forum.xda-developers.com/showthread.php?t=2083320). I had tried CM10 in the past but it didn't work that well. Thought I'd give it a second go, and, failing that, I'd try out this "lifeless". Sounded like a cool idea.
Background: phone was already rooted, and as I mentioned, i did actually get this CM10 rom to load sucessfully in the past, though I wasn't fully satisfied with the results. i figured this time I'd give it more time to sort out any issues I found. Failing that, I was going to go with the Lifeless ROM (which, I have decided I'm going to do over an unoffical CM10, I love that installer, if I can ever get it to work!). Anyway, here's what happened: I formatted Cache, Data, Davlik, and System just to be safe (same as I did last time). I tried flashing the CM10 ROM along with GApps. I got a hang on boot... just a black screen after the LG screen disappeared (yes, i forgot to do the TeenyBin flashes at the end... more on that later). So, I took this as a sign to try Lifeless, and I installed it successfully. Still a hang on boot... just the LG screen, and I let it go for a good half hour or more. Decided to do a restore of my backup (always do backups!), and... same thing. Even with the stock backup it would hang on boot.
So, I did some digging and I remembered about the TeenyBins! So I flashed the original one, just as I had last time I got CM10 to work. No dice, and even worse, TWRP was changed somehow (I am not sure if it changed versions, or what, but the menus were different), and now for some reason it couldn't even see my backup, even though the file browser in TWRP shows it clearly in the TWRP folder. So, I tried to install CM10, and flashed every one of the three TeenyBins offered on that page. The first one, of course, did nothing. The second, gave me a Google logo instead of LG, and I can actually see the choices on the bootloader screen now (I assume becuase it's based on the Nexus?), but again, nothing. The third (ZVBin) gave me a stuck LG logo for 5 minutes, then a few screen flashes and a kernel panic! Now I'm utterly confused.
EDIT: After the kernel panic, I restarted into recovery, and after the ZVBin flash, i have TWRP 2.4.4.0. It now sees my backup! I'm attempting to run the backup to see if I can at least get my phone back! If this doesn't work, I'll re-flash the Original TeenyBin... and then go from there. I thought about flashing the modems as the link from the CM10 page says, but before I get into changing even MORE, I'll defer to a professional's suggestions, haha.
I've exhausted just about every single option I can think of, I hope someone out there can help me! I would love to just get my phone to boot in some way so I can flash my backup file right back on. Any ideas on what might be causing this?
Thanks!
Sucess! Kinda. With the ZVBin, I was able to restore my phone, and get it to boot. And for some reason, the restore took my /sdcard folder and moved it into sdcard/sdcard0... don't know what that's about.
Any suggestions on what might have happened, and why Lifeless didn't want to work? Does it have soemthing to do with the TeenyBins I had to flash to make CM10 work? What do the TeenyBins replace? Sounds like the boot partition. Is there a way to get a plain one, with just TWRP 2.5 and the LS970 stuff it needs?
Ok, last post for the night, I think... tried to install Lifeless again, and it just fails, right off the bat. it says "Error flashing zip" with no explanation.
VDub2625 said:
Ok, last post for the night, I think... tried to install Lifeless again, and it just fails, right off the bat. it says "Error flashing zip" with no explanation.
Click to expand...
Click to collapse
If it reads error or fail something in that nature it still flashes fine for lifeless ROM, he posted something bout on the first page so go ahead and enjoy
RubbleTea said:
If it reads error or fail something in that nature it still flashes fine for lifeless ROM, he posted something bout on the first page so go ahead and enjoy
Click to expand...
Click to collapse
No, it didn't even get to the flash stage, just when I swipe to flash, it instantly failed.
But, i got it working! Not sure why or how, but I re-downloaded the Lifeless ROM and it worked with a fresh file. The file I had on there originally worked at first, but something must have happened to make it not work afterwards.
However, I do still have the Google boot-up screen and the Bootloader screen shows me menu choices, unlike every other Optimus G. I'm also still on TWRP 2.4.4.0. I hope it's not a problem. And maybe my expirences could help enlighten others,or maybe someone can help explain why exactly I went down this road, haha. I'd love to understand how the bootloader works on this particular phone, because it seems different from my old HTC.
Sorry to seem a little skittish with this post... but I was figuring it out as I was going along, and understood about half of it, haha. Just typing it out I think helped me to figure out what I was doing.
VDub2625 said:
Ok, last post for the night, I think... tried to install Lifeless again, and it just fails, right off the bat. it says "Error flashing zip" with no explanation.
Click to expand...
Click to collapse
I just quoted you here cause your last entry was long anyways here's a flash able twrp 2.5,http://androidforums.com/boost-mobi...ry-twrp-2-5-touch-recovery-cwm-flashable.html just flash in your recovery!
VDub2625 said:
No, it didn't even get to the flash stage, just when I swipe to flash, it instantly failed.
But, i got it working! Not sure why or how, but I re-downloaded the Lifeless ROM and it worked with a fresh file. The file I had on there originally worked at first, but something must have happened to make it not work afterwards.
However, I do still have the Google boot-up screen and the Bootloader screen shows me menu choices, unlike every other Optimus G. I'm also still on TWRP 2.4.4.0. I hope it's not a problem. And maybe my expirences could help enlighten others,or maybe someone can help explain why exactly I went down this road, haha. I'd love to understand how the bootloader works on this particular phone, because it seems different from my old HTC.
Sorry to seem a little skittish with this post... but I was figuring it out as I was going along, and understood about half of it, haha. Just typing it out I think helped me to figure out what I was doing.
Click to expand...
Click to collapse
Well now I know I need to try that second teenybin... I miss having that Google bootloader screen and the menu options I wonder if that is the only way to get it?
Sent from my Lifeless Optimus G