Related
First off, thanks for all the help so far, this site is the best!
I just rooted my Evo using the unrevoked3. Had a little bit of trouble, nothing major, and overall it was a success. I also installed ROM Manager and Titanium Backup, based on suggestions found here.
The problem is, I'm not quite getting how to flash the roms... I downloaded one through ROM manager, and it seemed to work, but I didn't notice a single thing different. I tried to install CyanogenMod, and it downloaded, but it would always fail during the install.
I tried downloading on my computer, then moving the .zip file to my sdcard. Then I select "install rom from sdcard" and everything seems to go ok, I end up having to go into recovery and "rollback" my phone to the stock rom, because twice now I've almost bricked my phone.
Really, what I'm wanting is a setup like that "Kuma Style" one (without the animal), and a different bootscreen. I have spent a lot of time searching around, and it seems simple enough, I just seem to be missing some integral part of the proccess.....
Any help is appreciated!
Mark_Hardware said:
First off, thanks for all the help so far, this site is the best!
I just rooted my Evo using the unrevoked3. Had a little bit of trouble, nothing major, and overall it was a success. I also installed ROM Manager and Titanium Backup, based on suggestions found here.
The problem is, I'm not quite getting how to flash the roms... I downloaded one through ROM manager, and it seemed to work, but I didn't notice a single thing different. I tried to install CyanogenMod, and it downloaded, but it would always fail during the install.
I tried downloading on my computer, then moving the .zip file to my sdcard. Then I select "install rom from sdcard" and everything seems to go ok, I end up having to go into recovery and "rollback" my phone to the stock rom, because twice now I've almost bricked my phone.
Really, what I'm wanting is a setup like that "Kuma Style" one (without the animal), and a different bootscreen. I have spent a lot of time searching around, and it seems simple enough, I just seem to be missing some integral part of the proccess.....
Any help is appreciated!
Click to expand...
Click to collapse
I am not familiar with Unrevoked, but just running unrevoked doesn't completely root your phone. You need to do the second parts of rooting which unlocks nand.
Ah, so there is more to do. Maybe that's the problem then.... *off in search of how to unlock nand
Mark_Hardware said:
Ah, so there is more to do. Maybe that's the problem then.... *off in search of how to unlock nand
Click to expand...
Click to collapse
Unlocking nand just unlocks something so that you can save full image backups. That wouldn't lead to your phone not installing a ROM right, it's just something you'll want just in case things go wrong. So still finish the root and get nand. But that's not what you're missing here.
Possible error: Did you wipe settings &factory reset and wipe cache in ClockworkMod before flashing the ROM? I think that could lead to some problems.
Try flashing the alternative Amon Ra recovery through rom manager (will state that rom manager won't be fully functional unless clockworkmod is installed) and loading the roms onto the sd card then reboot into recovery. Amon Ra seems to work better imo than clockworkmod. When you're talking about something like "kuma style," those are themes that are usually flashable in recovery also. The boot animation could alse be flashable in recovery but if not, there are instructions on how to adb push custom ones onto your phone.
rugedraw said:
I am not familiar with Unrevoked, but just running unrevoked doesn't completely root your phone. You need to do the second parts of rooting which unlocks nand.
Click to expand...
Click to collapse
just fyi, the latest unrevoked (3.21) unlocks nand so u dont need to do it.
"unrevoked3 will permanently unlock NAND write protection by default on the following phones:
*
Sprint EVO 4G"
i'd link the wiki but i cant cuz i'm a new user lol
Gah! So I downloaded the enamored theme, moved it to the sd card, then went to ROM Manager and selected "Reboot into Recovery"and selected the enamored.zip. It said the install was a success, but when I rebooted, the phone stuck on the bootanimation. I tried restarting a couple times, but it always gets stuck in the same place.
I booted into recovery (if thats waht you call the hold the volume button down while pushing the power button trick), and selected recover, then nandroid, then a time under yesterdays date. Phone recovered fine.
WtH am I doing wrong? I realize I am way out of my league, but I'm not completely retarded. Again, GAH!
Are u wiping data and cache when flashing a ROM? I have been stuck at the CM6 boot animation when coming from a different Rom and not wiping.
Sent from my PC36100 using XDA App
Mark_Hardware said:
Gah! So I downloaded the enamored theme, moved it to the sd card, then went to ROM Manager and selected "Reboot into Recovery"and selected the enamored.zip. It said the install was a success, but when I rebooted, the phone stuck on the bootanimation. I tried restarting a couple times, but it always gets stuck in the same place.
I booted into recovery (if thats waht you call the hold the volume button down while pushing the power button trick), and selected recover, then nandroid, then a time under yesterdays date. Phone recovered fine.
WtH am I doing wrong? I realize I am way out of my league, but I'm not completely retarded. Again, GAH!
Click to expand...
Click to collapse
When you flash a theme, it could take up to 2-5 minutes to finish. This occurs during the boot animation. I flash themes all the time and I notice it's usually around 2-3 minutes wait. Maybe faster for others but that's just been my experience. If it's over 5 minutes than there's probably something wrong with your zip file or maybe clockworkmod recovery doesn't flash it properly. Also, it could be an issue with the kernel you're using...I noticed on kingklick cfs #10, I was stuck on boot animation for about 7 minutes and so I reverted back to the stock kernel and the theme was applied within 3 minutes.
ok, apparently I've been missing that step...
where do I do that again?
mizzos4 said:
When you flash a theme, it could take up to 2-5 minutes to finish. This occurs during the boot animation. I flash themes all the time and I notice it's usually around 2-3 minutes wait. Maybe faster for others but that's just been my experience. If it's over 5 minutes than there's probably something wrong with your zip file or maybe clockworkmod recovery doesn't flash it properly.
Click to expand...
Click to collapse
I waited a good long time. Am I at least headed in the right direction? Sorry to sound whiny, it's just that there's a few little things I want to do, and I'm intimidated as hell by actually doing any command line, so I'm hoping to avoid that- aka riding someone else's coattails
First, which rom are you using and is it stock or custom kernel? Are you using clockworkmod recovery? Try flashing the alternative amon ra recovery in rom manager then boot into recovery and apply your selected theme.
if you are using a stock rom it must say stock 2.2 deodexed
if it is not a deodexed rom.. of any kind.. then themes will say they flashed but they will either brick your phone or not work at all.
and stop using clockwork.... just use amon ra
Sent from my PC36100 using XDA App
I could be way off here, but I've seen some people who rooted using unrevoked, and run into trouble flashing things (or maybe I'm thinking of trouble with terminal commands) and it turned out they couldn't find flash_image anywhere in there SD card, Which should be installed (someone please correct me if I'm wrong).
I saw a lot of reports of this in chainsDDs superuser thread, if I remember correctly. They had to install flash_image.img (which is a file available on toasts part 2 root tutorial)
I obviously could be wrong about this, I've never used unrevoked, I rooted via toast, and his method included everything.
@ V_lestat
Thanks for the heads up about themes having the ability to brick your phone if not deodexed, I never knew that. I flash roms and kernels a lotbut never messed with themes much.
At OP, have a look at virus Rom thread. It's a great ROM, and he has built some different themes to go with it. Beautiful stuff, great ROM, great thread.
Good luck
Sent from my PC36100 using XDA App
See, some people say use clockwork, some people say Amon.
I looked around a lot beforehand, and people kept saying to use unrevoked, so I did. Now people say I should have used Toast?
Thanks for everybodies help so far, I am reading everything and taking it all in.
I Don't Mean to add any Confusion to your situation. I am new to this also.. I went with unrevoked also and when I booted into recovery with clockwork mod. I did a nand back up first to make sure if anything went wrong I could just boot back into recovery and load my backup. Then I wiped my Data & Davlick Cache all of the caches. Then I installed my Rom and it worked like a charm. I will add it did take about 5 to 7 mins to boot only on the first time though. I hope that helps some as to the process and what to do first don't give up XDA rocks with the smartest mind on the planet.
Mark_Hardware said:
ok, apparently I've been missing that step...
where do I do that again?
Click to expand...
Click to collapse
If you are using ROM Manager to "install zip from card" it presents you with a dialog with two unchecked check boxes. One of them is "wipe data + cache". make sure you check it before hitting ok on that dialog.
If you are manually booting into recovery then in the recovery choices you will see one that says wipe data and one thats says wipe davlik cache. first do a nandroid back up then wipe those data and davlik then install the rom. By the way are you just installing a theme or a full rom that might be the issue i am just wondering maybe a senior member can help on wether you can install a theme over a rooted stock theme or not?
Success!
I went into ROM Manager, backed up current ROM, went into recovery manually, wiped the cache, then installed from zip, and it worked! I tried a cool theme I found, and I like it, but it seemed old. I just installed fresh, and the enamored theme, and all is working great!
A couple more questions,
1) how do I get my contacts back?
2) How do I get my apps back onto my phone? I have them backed up on appbrain, but I haven't been able to find how to get them back to the phone.
So far, I've tried a couple of ROM's (and/or themes) and I've ended up flashing back to my own "safe" one, until I figure these two things out.
A tremendous thanks to everyones help! I seriously couldn't have done it without you guys
Edit; Oh yeah, one other thing. How do I delete the other nand backups? There's like 5, and I need to free up some memory. I tried going in and selecting one to see if it gave me the option to delete, but I didn't see anywhere that it did.... Got it. Search feature to the rescue
Hello XDA-Forum
As of today this is my first day and post here.
As a noob ( I watched the video on reg, i found it funny yet noobfriendly D: ) i would like to ask some questions that the all-mighty search button could not find me, or atleast i could not find
I whacked my head all day searching for a way to root my HTC Wildfire S a520e running on 2.3.3 stock marvel s-off phone
and after by mistake factory reseting it, twice....
I finally managed to root it with OneClickRoot or something.
Then i tried to to what i originaly wanted to root for, Overclock.
But after downloading the rom i got from a youtube video, it f**ked me up good.
Now my phone is overclocked, but is slower. and the menu's are all glitchy and white and wrong.
I would like to ask how to return to the stock rom of 2.3.3 that i so much desire.
Meanwhile while i await your answears of joy, i am downloading Cyanogen 7.2 Rom that i found on the interwebs and should so-fit my tiddy little wildfire s.
Toodles.
I installed Cyanogen... and .... well i don't like it (Q_Q)!
i want my old 2.3.3 back (cry)
It feels slower, i don't like the UI
EDIT:
Now that i look at it again.. it's not that bad qq
but where's the android market/google play ?
You need to flash Google apps package from clockwork mod recovery:http://cmw.22aaf3.com/gapps/gapps-gb-20110828-signed.zip for market to work.
If you want to go back to stock, download a ruu installer for your region eg euro, Asia etc from here:http://forum.xda-developers.com/showthread.php?t=1074445
Install from a windows pc
As un-adaptable to new stuff i am and as much i hate change.
I find this cyano-genic blue colour to be semi attractive.
and i decided i'll keep it.
I read that cyanogen has built in overclocking.
Where can i see the hardware? i try'd in about settings but it doesn't say there.
For overclocking go:
Settings
Cyanogenmod
Performance
Cpu
I find this slightly more complicated than the normal android sense, but herpyderpderp atleast i'll be the only one in my class with a custom rom 8D
All the others are iOS/IceCreamSandwich richbishes D:
Is there something Cyanogen can't do that the original android stock can do?
intel007 said:
You need to flash Google apps package from clockwork mod recovery:http://cmw.22aaf3.com/gapps/gapps-gb-20110828-signed.zip for market to work.
If you want to go back to stock, download a ruu installer for your region eg euro, Asia etc from here:http://forum.xda-developers.com/showthread.php?t=1074445
Install from a windows pc
Click to expand...
Click to collapse
Nevermind, worked D: I'm a potato.
I know i ask a lot of questions but i'm stuck at "Touch the android" after i flashed this thing
i touch the android and nothing happens... this happens on boot
I find myself in a position where i cannot procceed, this "touch the android" is stopping me ._.
hawp...
You might need to reflash.
Clear your data and dalvik in cwm
Flash cm7 latest nightly
Flash gapps
On first start take your time DONT press the android right away.
Give all background apps and SD time to load, maybe 30-60 seconds then press it and continue setup.
I have had that issue in the past.
Hope it helps you.
CM7 is a great rom, so customisable enjoy and make it your own.
intel007 said:
You might need to reflash.
Clear your data and dalvik in cwm
Flash cm7 latest nightly
Flash gapps
On first start take your time DONT press the android right away.
Give all background apps and SD time to load, maybe 30-60 seconds then press it and continue setup.
I have had that issue in the past.
Hope it helps you.
CM7 is a great rom, so customisable enjoy and make it your own.
Click to expand...
Click to collapse
I factory reseted.. i hate having to do that.....
it got stuck at cyanogen 7 loading boot, will this happen again if i use the thing you gave me for android?
damN! factory reset didn't fix it, how do i reflash when i deleted the file from the SDCard? now i can't put it back on the SDcard
EDIT: I got the file on again, but this software is way too fragile...
http://pockethacks.com/htc-wildfire-s-custom-rom-android-2-3-3-gingerbread/
Is that older or new'r ?
And can i get THAT interface on my now installed rom?
EDIT:
Stuck at HTC, still wown't load after re-flash
Did you wipe data and dalvik?
Its important you do!
Use this cm7, latest nightly build http://cm7-wildfire-s.googlecode.com/files/update-cm-7.2.0-RC1-marvel-03_29_2012.zip
I'm thinking of getting this http://code.google.com/p/cm9-wildfi...rc0-unofficial_rom-alpha0-signed.zip&can=2&q=
So far so good, it has minor problems i don't like
but what can i do -sigh-
there's an option called "Data Enable"
Does that take like money or anything?
also how can i use Voice Speech in this rom?
i wanna be able to talk on skype and it turns out as text
just as a question, could there be a problem during the installation, becouse the clock on the start seems to not be visible, it said some kind of error and i removed it from the screen. also it has 90mb free now
feels like first time i installed it it had like 110
THe clock on the lockscreen? You probably changed a setting. Or a clock widget? You probably deleted it. Just hold on the home screen and re add it form there.
bingzz said:
THe clock on the lockscreen? You probably changed a setting. Or a clock widget? You probably deleted it. Just hold on the home screen and re add it form there.
Click to expand...
Click to collapse
Yes that worked, it wasn't deleted i guess.
I pretty much set up my phone overnight. (now my body hurts from exhausture)
I'm still haveing problems setting things up like voice to text on skype and other stuff.
Overclocking crashes my phone a lot. I know that happens but it happens like every 20 mins or something.
Also can i UPDATE from 7 to 9 without having to start over.
just update?
UPDATE: Also, i loose some files from sdcard (games installed) when it crashes when overclocked sometimes.
What the... i restarted my phone and all the stuff on SDCard is deinstalled, gone D:
EDIT: It came back after 5 mins
EEK!
I was putting some stuff on my SDCard when suddenly i open proccess list and on SC card it says No applications, 1.4 used, 431free but nothing QQ Hawp
all my icons are now with the android pic on them D: helppp
I'm starting to hate this already D:
Also my google play went back to market
If you want to downgrade to 2.3.3, check this tutorial
http://forum.xda-developers.com/showthread.php?t=1540952
Hey there everyone,
I am honestly at a bit of a loss.
I have an AT&T GS3, and I noticed that all the bloatware was SERIOUSLY draining the battery and hogging up RAM, so I thought it would be a great idea to get a custom rom to enhance my phone.
I used the GS3 Toolkit to flash TWRP recovery. - All went well
I read up on some different Roms, and i chose to install http://forum.xda-developers.com/showthread.php?t=2089821
I installed RLS16
I followed the instructions,
Wipe data/factory reset
Wipe dalvik cache
Wipe /system
I went through the Aroma installer and chose to install the Developer's Pick.
This includes a bunch of little addons like 4.2 camera, gallery, keyboard, etc.
but it also installs lean kernel.
The install went fine, nothing said it failed
but once i was in the rom. Things got terrible.
My phone randomly crashed and shut off, like within minutes each time, camera would crash the phone, causing it to shut off, etc.
So i went through the GS3 toolkit, downloaded and reflashed the stock Rom and recovery.
Once it booted, I keep getting "Unfortunately Messaging has Stopped" and I cannot receive or send text messages, even through other texting programs like Handcent SMS.
No matter what, it keeps crashing (the messaging, not the rom). I factory reset, wiped, everything. Nothing will fix it.
I thought that maybe the stock rom doesnt include stock kernel? So i went online, downloaded the stock kernel, flashed, reflashed stock rom, and STILL the same thing. Messaging has stopped working.
Also as a side note, when i tried to do a google voice search. I get a page saying Sorry and that my computer or phone might be sending network requests or something along those lines.
I cannot think of anything else I can do....
If anyone has any idea, please let me know...
Thanks!
eternalcold said:
Hey there everyone,
I am honestly at a bit of a loss.
I have an AT&T GS3, and I noticed that all the bloatware was SERIOUSLY draining the battery and hogging up RAM, so I thought it would be a great idea to get a custom rom to enhance my phone.
I used the GS3 Toolkit to flash TWRP recovery. - All went well
I read up on some different Roms, and i chose to install http://forum.xda-developers.com/showthread.php?t=2089821
I installed RLS16
I followed the instructions,
Wipe data/factory reset
Wipe dalvik cache
Wipe /system
I went through the Aroma installer and chose to install the Developer's Pick.
This includes a bunch of little addons like 4.2 camera, gallery, keyboard, etc.
but it also installs lean kernel.
The install went fine, nothing said it failed
but once i was in the rom. Things got terrible.
My phone randomly crashed and shut off, like within minutes each time, camera would crash the phone, causing it to shut off, etc.
So i went through the GS3 toolkit, downloaded and reflashed the stock Rom and recovery.
Once it booted, I keep getting "Unfortunately Messaging has Stopped" and I cannot receive or send text messages, even through other texting programs like Handcent SMS.
No matter what, it keeps crashing (the messaging, not the rom). I factory reset, wiped, everything. Nothing will fix it.
I thought that maybe the stock rom doesnt include stock kernel? So i went online, downloaded the stock kernel, flashed, reflashed stock rom, and STILL the same thing. Messaging has stopped working.
Also as a side note, when i tried to do a google voice search. I get a page saying Sorry and that my computer or phone might be sending network requests or something along those lines.
I cannot think of anything else I can do....
If anyone has any idea, please let me know...
Thanks!
Click to expand...
Click to collapse
When you flashed stock, did you flash the one for your carrier? (It should flash the kernel at the same time)
Did you try clearing the messaging app's data/cache?
Did you try flashing another custom ROM to see if you still get the errors? If not, could give 4.2.1 a shot.
BWolf56 said:
When you flashed stock, did you flash the one for your carrier? (It should flash the kernel at the same time)
Did you try clearing the messaging app's data/cache?
Did you try flashing another custom ROM to see if you still get the errors? If not, could give 4.2.1 a shot.
Click to expand...
Click to collapse
Yeah i flashed the one for my carrier. And i figured it would do the kernel, but just in case i tried flashing it separately....
and yeah i did try wiping the data/cache, but i will try it again.
and I could always try flashing another custom rom. Do you have any suggestions? i just want one that works quickly, is stable, and has messaging lol
eternalcold said:
Yeah i flashed the one for my carrier. And i figured it would do the kernel, but just in case i tried flashing it separately....
and yeah i did try wiping the data/cache, but i will try it again.
and I could always try flashing another custom rom. Do you have any suggestions? i just want one that works quickly, is stable, and has messaging lol
Click to expand...
Click to collapse
Look in my sig I don't give suggestion per say cause it's up to the user's preference but I'll always be running something that works.
BWolf56 said:
Look in my sig I don't give suggestion per say cause it's up to the user's preference but I'll always be running something that works.
Click to expand...
Click to collapse
I might try that one out. I was looking at some reviews, someone said there may be Bluetooth issues. I just bought the Moga, and i need BT to work perfecty...
Any input on that?
eternalcold said:
I might try that one out. I was looking at some reviews, someone said there may be Bluetooth issues. I just bought the Moga, and i need BT to work perfecty...
Any input on that?
Click to expand...
Click to collapse
Best thing to do is to read changelogs but for now I'll give you the answer, it has been fixed a few releases ago in Task650's AOKP.
BWolf56 said:
Best thing to do is to read changelogs but for now I'll give you the answer, it has been fixed a few releases ago in Task650's AOKP.
Click to expand...
Click to collapse
Alright, i'll flash that one, i'll post to here when it's finished. Thanks!
Did you check your IMEI?
xBeerdroiDx said:
Did you check your IMEI?
Click to expand...
Click to collapse
Just checked, my IMEI is there.
Also, i found this thread
http://forum.xda-developers.com/showthread.php?t=1804782
but their images wont show. Any idea what route they are taking to solve this??
eternalcold said:
Just checked, my IMEI is there.
Also, i found this thread
http://forum.xda-developers.com/showthread.php?t=1804782
but their images wont show. Any idea what route they are taking to solve this??
Click to expand...
Click to collapse
That guy flashed the bootloaders. I'm not sure what the pictures are supposed to be but they don't seem to lead to anything.
My take on it: Don't play with bootloaders, it's the only way to really brick your phone (if something goes wrong that is).
BWolf56 said:
That guy flashed the bootloaders. I'm not sure what the pictures are supposed to be but they don't seem to lead to anything.
My take on it: Don't play with bootloaders, it's the only way to really brick your phone (if something goes wrong that is).
Click to expand...
Click to collapse
Understood, I wont mess with them.
I really just want to understand a couple things.
1. Why did the ROM I installed before work for everyone else except me? and i followed the instructions.
and 2. after flashing to stock, how am I unable to fix this?
mainly to just learn what went wrong.
Sometimes the reason just...you had a bad flash or something broke down in there. I did the CF easy root method and flashed TWRP in goo manager and then started flashing. I've never tried the toolkit but like anything many times it just depends on the download you got or a bad flash. We've all had several...just hate when it involves rooting or using ODIN.
hednik said:
Sometimes the reason just...you had a bad flash or something broke down in there. I did the CF easy root method and flashed TWRP in goo manager and then started flashing. I've never tried the toolkit but like anything many times it just depends on the download you got or a bad flash. We've all had several...just hate when it involves rooting or using ODIN.
Click to expand...
Click to collapse
Thanks,
Is there any way to repair it?
Alright, so....
I think i have figured out what the issue was. Or by random chance got it fixed.
I was going to try to install the Synergy Rom. And while going through the custom setup, i noticed "Install AOSP Messaging" and "Install TW Messaging"
I chose the TW messaging, and went through the rest of the installer.
For some reason i kept hanging at the "Samsung Galaxy S3" logo, and it would not boot.
(Honestly, i've used custom roms since the HTC Touch Pro 2, and i've NEVER had such issues. And i personally think the TP2 was way more difficult lol)
So I ONCE AGAIN flashed to stock. and randomly the messaging works!
I only can guess that even when flashing the stock rom, it doesnt change something regarding the messaging app. I'm not sure. All i know is that i'm on stock again and everything is working. I highly doubt i'm going to try another custom rom for a while until i have a full understanding of what happened.
But in case anyone else was having this problem, i hope this helped.
The first thing I flashed was Viper. I loved it at first, then I froze Rosie to speed things up. I started having battery drain, so I started looking for other roms to try, but I did enjoy this one!
Now I am having charging issues - I've spent hours reading posts about this, can't even get the Anker external charger to work, but that's another story. It might be the port, but even with a battery at 100% it will just dive, for no reason or use. Usually with the wall charger, it just drains the battery, without use.
I've tried flashing Incredibly Paranoid Final, CM7 Nightly, CM10. I've followed the steps to the letter, wiping, wiping, wiping, doing the anti-viper super wipe .. Every time I end up stuck with the boot screen that never actually progresses onward.
I know there has to be an answer somewhere. The battery got down to 18% so I decided to post this in frustration. It's at 31 now, so at least it's charging this time, if I'm careful not to move it.
I just want to flash a different rom!
Can anyone see something that I could be doing wrong?
Thanks
Yay, I figured it out! Even after all of my searching to no avail!
I do NOT have S-off, and I didn't realize that. Once I did, I knew I had to do that one last step after flashing!! The bootimg step!
I'm really excited, I managed to find my way through! :laugh:
Install Evervolv or PAC final
Use the superduperwipe its stickied
So that it won't freeze at boot
Remember to install the correct gapps for PAC is the 20121110 and for evervolv its anything after that but becareful
Sent from my HTC Droid Incredible 2 using xda app-developers app
I actually DID install PAC Final Lovin' it so far, too!
I used the SDWipe, it's in that thread too.
I do need to update gapps though, I used the 07262012 one. I'll do that now. I knew that anything after October something was going to be a later version of jb than it should be.
OK, rock and roll! I love this
Thanks!
Yeah if ur not s-off ull have to manually flash the kernel each time via fastboot. But if u use chilly's anti viper zip in the misc section of the incrediblychilly forum itll do better on u when u flash roms keeps from boot looping. Im s-off and when i used the viper rom after i wanted to go back to aosp it kept boot looping. I used the anti viper zip even if i go from one aosp rom to another. It wipes deep leaving no trail unlike doing a regular wipe in recovery. Give it a try and click thanks if this was helpful.
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