Related
Hello,
I need some help. I decided to try out a mod while at work today. i tried it out and didnt like it too much and try to restore my last back up that i did before the change. the phone cut off then back on and was stuck on the mytouch 4g screen and has been this way for about 3 hours.i took the battery out and i went to the hboot screen and tried a factory reset and then the rom manager opened up (v3.0.0.5). from there i went to reboot now and it goes back to the my touch screen. idk what to do and i need help. im new to the droid and am unfamiliar with the terms. can anyone help PLEASE. if possible to gtalk me at j.d.louisy.
thisisjay said:
Hello,
I need some help. I decided to try out a mod while at work today. i tried it out and didnt like it too much and try to restore my last back up that i did before the change. the phone cut off then back on and was stuck on the mytouch 4g screen and has been this way for about 3 hours.i took the battery out and i went to the hboot screen and tried a factory reset and then the rom manager opened up (v3.0.0.5). from there i went to reboot now and it goes back to the my touch screen. idk what to do and i need help. im new to the droid and am unfamiliar with the terms. can anyone help PLEASE. if possible to gtalk me at j.d.louisy.
Click to expand...
Click to collapse
calm down take a breather us XDA users got your back, OK take out the battery and put it back in then go to the Hboot ( hold power and volume down) then once you get to the Hboot Settings use volume down to get to RECOVERY (i think its the third one) then once you get into Clockwork Recovery scroll down to (Backup and Restore) click then press (Restore) and then choose your Restore file it usually Year-month-day hope i helped you donate pls if i did
BE SURE TO KEEP THE CHARGER IN!!
p.s. if it turns off while its restoring even with the charger in let it boot into recovery mode and let it charge up a bit
incase you still need help gtalk me [email protected]
and p.s. CWM 3.0.0.5 is for gingerbread only
Certain roms require certain versions of clockworkmod. I don't know if this also applies to restoring from backups, though. Which type of rom did you flash?
If he flashed the add on 3.0.0.5 has ext3/ext4 support. Should be able to flash froyo and TB Rome.
Sent from my HTC Glacier using XDA App
3.0.0.6 supports ext3/ex4 3.0.0.5 only does Gingerbread
Edit: I'm being a dumbass yea what he said was right I'm overly tired and I have to explain to her why I was being a dumbass and trying to flash through fastboot but what I don't understand is why its still stuck at the boot screen
thisisjay said:
Hello,
I need some help. I decided to try out a mod while at work today. i tried it out and didnt like it too much and try to restore my last back up that i did before the change. the phone cut off then back on and was stuck on the mytouch 4g screen and has been this way for about 3 hours.i took the battery out and i went to the hboot screen and tried a factory reset and then the rom manager opened up (v3.0.0.5). from there i went to reboot now and it goes back to the my touch screen. idk what to do and i need help. im new to the droid and am unfamiliar with the terms. can anyone help PLEASE. if possible to gtalk me at j.d.louisy.
Click to expand...
Click to collapse
Three options
Option one: (easiest)
Since you flashed 3.0.0.5 you must flash a Gingerbread ROM, (Which you can download from here ). Make sure to flash the G/apps after you flash the ROM.
Option two:
you can flash a 2.x.x.x Recovery image, or flash 3.0.0.6 via script or manually do it via the HBoot.
Option three:
Flash the PD15IMG and start over from ground one.
thank you so much for the advice and help. i could bang my head on the wall for trying to load gorillasens. i shouldve left it alone. once i get home from work i will give it a try again.
thisisjay said:
thank you so much for the advice and help. i could bang my head on the wall for trying to load gorillasens. i shouldve left it alone. once i get home from work i will give it a try again.
Click to expand...
Click to collapse
Ah. i think i see what happened. You rooted your phone. downloaded Clockwork Rom Manager, then flashed a recovery image (which was version 3.x). then tried to flash a 2.2 ROM.
Okay. so what.....
a common mistake but one that can be avoided by doing a little research.
Clockwork's 3.0.0.5 recovery image is only compatible with Gingerbread (2.3) based ROMs.
Clockwork's 2.x recovery image are only compatible with FroYo (2.2) based ROMs.
gorilla is 2.2 So it's not cannot be flashed by the recovery image you are using.
if that is correct then the text in the recovery image should be orange in color. If that is correct.....If i were in your shoes i'd load CM7 w/ the GAPPS > download CWRM from the markert > scroll to the bottom (all clockwork recoveries) and flash the newest 2.x. then boot into recovery / make sure the text is GREEN, not ORANGE, wipe then flash your GorillaSense.
Can you cite a source, because I've also heard people claim that Clockwork 3 is backwards compatible, but there was no evidence either way...?
How would you go about switching from a 2.2 ROM to a 2.3 ROM? Do you have to backup with CWM 2, then install CWM 3 to install the new ROM? Doesn't make a lot of sense to me...?
Sent from my Nexus One using XDA App
danger-rat said:
Can you cite a source, because I've also heard people claim that Clockwork 3 is backwards compatible, but there was no evidence either way...?
How would you go about switching from a 2.2 ROM to a 2.3 ROM? Do you have to backup with CWM 2, then install CWM 3 to install the new ROM? Doesn't make a lot of sense to me...?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
3.0.0.5 is not backwards compatible, which is the official 3.x that you download via the Application. 3.0.0.6 which is "beta" flashed via the HBoot is backwards compatible.
It's seriously jacked if you ask me.
to go from lets say CM6 > CM7 one would do a nandroid backup of CM6, then go to CWRM flash the 3.0.0.5 recovery image > boot into recovery and flash the CM7.
now to get back to a 2.2 ROM you have to scroll to the bottom of CWRM app's and flash a 2.x version of the recovery then do your nandroid restore, flash the 2.2 recovery image.
From what i've heard once 3.0.0.6 is finished you can use that for everything.
What a pain...
I'm real sketchy about the Clockwork 3 recoveries for the Nexus, because they've been screwing up partitions (mine included). Has there been any problems with Clockwork 3 on the Glacier?
Sent from my Nexus One using XDA App
danger-rat said:
What a pain...
I'm real sketchy about the Clockwork 3 recoveries for the Nexus, because they've been screwing up partitions (mine included). Has there been any problems with Clockwork 3 on the Glacier?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I haven't had any problems with mine. The only problem that was noted was the 3.0.0.5 prior to the official release wouldn't do Nandroid Backups directly from the application. Some were reporting it work work from the recovery image, but mine never did.
and i have a feeling the reason it's screwing with Partitions is this (CM7/CW3.x) is a Ext4 set up. And CM6/CW2.x is a Ext3 set up.
but since it went official the only problem i've seen is people flashing the the wrong recovery for the wrong ROM. People are flashing 3.x because 3 is higher than 2 so they think it's an upgrade and have no clue on the who/what/when/wheres and whys of what its for.
The partition thing is different for the Nexus, because they are cross compatible to a certain degree. I rolled back to CWM 2, but I can still flash CM7 no probs...
It's interesting to note the differences between the two platforms though (Nexus vs Glacier).
Sent from my Nexus One using XDA App
danger-rat said:
The partition thing is different for the Nexus, because they are cross compatible to a certain degree. I rolled back to CWM 2, but I can still flash CM7 no probs...
It's interesting to note the differences between the two platforms though (Nexus vs Glacier).
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Yea between Google's way of doing thing and HTC, but i'm sure the chip-set has something to do with that. and with the sexy nexi only having 512Mb of memory the factor of tricking the phone to use the SD card has something to do with it i'm sure.
i have the 3.x recovery and i can flash iceglacier which is a 2.2 rom with out any issues. what i can't do is restore my backup from my other phone onto this replacement i just got. i made the backup with the 3.x recovery but i just keep getting stuck at the mytouch bootup screen... gonna try flashing the 2.x recovery and see if it lets me do the restore.
hey there everyone. just giving an update.......phone is still messed up. we tried putting gingerbread on and no go....tried flashing to PD15IMG and starting over. no go, it kept saying that "main version older <bad>" the phone wont go past the htc screen. im going on day 3 and no phone. *sigh* open for more advice. should i just buy another phone?
OMG OMG OMG i fixed it.......thank you for this post http://forum.xda-developers.com/showthread.php?t=957457 i re downloaded the PD(insert file name) and it worked. i broke down in tears. thank you guys sooooo much.
I used the .zip file to restore my mytouch, but now it wont go into Hboot.
I got the same problem and is fixed thanx to this link
http://forum.xda-developers.com/showthread.php?t=957457
now I have to root the phone again
Thank you
Thank goodness someone had this problem
I just ran into the same issue. whew good thing xda is here!!! Thanks fellas
Hi,
My warranty has just run out on my Nexus One so I've decided to unlock the bootloader.
My Aim is to get from stock non rooted Gingerbread to rooted Gingerbread with busybox, SU, and ultimately being able to boot into ubunto in chroot, I've been reading up on all this for a few days now but just need a small amount of help with Recovery, Gingerbread ROM choice, and the order that thing should be done, by someone who's done this before.
I take it the first thing is to install SDK and get The USB Driver working on PC, its running XP by the way.
Then I unlock the bootloader, !HELP! to do this do I enter hboot or fastboot, before connecting the phone to the PC? I have to copy 3 files somewhere and use ADB and run command for **** OEM unlock, can't remember the exact command, (I've got instructions for this) and then agree to void my warranty etc.
I then find and download the correct custom recovery image and copy this into the tools folder of the SDK. And install (got instructions for this to).
!HELP!
Which custom recovery image should I use? and which Rooted Gingerbread ROM is most popular ?
After installing the custom Recovery can I just flash a custom ROM? I've seen something about SU.zip mentioned, is this necessary?
If I can just flash a custom ROM, I do this by downloading and copying the custom ROM of choice to the root of my SD card. Start phone in recovery mode and install from SD? I then install the google add ons .zip (if required) using the same method.
Sorry for such a long post and so many questions but I can find all the information for what I'd like to achieve but not in one place and nowhere in any chronological order.
Any advice appreciated .
Please read the Wiki, "Root" guides, "Unlock bootloader and install custom ROM" thread. Execute until the point of installing custom ROM.
Look in "Recovery" section for recoveries, install the latest Amon_RA.
Ive Successfully Rooted Gingerbread by following this method http://chensun.net/android-development/root-nexus-one-with-android-2-3-3-gingerbread/8/
GB ROM
Im running CM7RC4 and am happy w/ it
MouseIdt said:
Ive Successfully Rooted Gingerbread by following this method http://chensun.net/android-development/root-nexus-one-with-android-2-3-3-gingerbread/8/
Click to expand...
Click to collapse
Thanks everyone, but this looks like the one for me, going to unlock bootloader now install custom recovery and flash su.zip.
I'll post back with how I went on. Wish me look
A apprehensive newbie ;-)
Flash this as well, otherwise you will lose your custom recovery...
http://db.tt/cp7De8G
Sent from my Nexus One using XDA Premium App
Good show with unlocking the bootloader, it's the best way.
However... looking at your flag, you're in the UK... this means your phone is still in warranty, as we get 24 months.
Nooooo
Rusty! said:
Good show with unlocking the bootloader, it's the best way.
However... looking at your flag, you're in the UK... this means your phone is still in warranty, as we get 24 months.
Click to expand...
Click to collapse
My understanding was 12 months but, your probably right. I've unlocked the bootloader now and fortunately my N1 is in good condition, funtioning correctly ( well at least for now, I'll have to cross that bridge if and when I get to it )
Getting on to custom recovery, I realised something wasn't quite right after my first attempt. I installed custom recovery but without su.zip on my SD card. I managed after rebooting my PC to complete the custom recovery with su.zip on the SD card and was successful in that I've got SU on my N1. However I am quite sure I do need to fix something with the recovery, can someone explain what method or how I do this now. I've unlocked the bootloader, I am rooted with gingerbread but with a dodgy recovery.
Or do I do exactly the same as I did with su.zip and push recovery from ADB and flash from SD card, making sure that fix-recovery.zip is indeed on the SD card.
Hope this makes sence?
Any help appreciated.
After I unlocked my n1 I used rom manager for everything else, first flashing clockwork mod, then selecting a stable cm 7 build and flashing that, since then I've done everything through recovery, flashing custom kernels and nightlie builds, I'm currently using cm7 rc4 highly recommend rover theme too!
Sent from my Nexus One using XDA Premium App
sparkyryan said:
After I unlocked my n1 I used rom manager for everything else, first flashing clockwork mod, then selecting a stable cm 7 build and flashing that, since then I've done everything through recovery, flashing custom kernels and nightlie builds, I'm currently using cm7 rc4 highly recommend rover theme too!
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
I've got ROM Manager installed and if I want to try anything it tells me I have to flash clockwork mod recovery, I was unsure if It was safe to do this after using a completely different recovery image to get where I am now.
Sorry for being such a paranoid newbie, but we all got to start somewhere ;-)
sparkyryan said:
After I unlocked my n1 I used rom manager for everything else, first flashing clockwork mod, then selecting a stable cm 7 build and flashing that, since then I've done everything through recovery, flashing custom kernels and nightlie builds, I'm currently using cm7 rc4 highly recommend rover theme too!
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
I think CM7 rc4 is next, I do want to get Linux up and running though, even if it's in a virtual environment (chroot). and deffinately would like to check some nice themes out, I've not even looked at themes yet, I suppose it's quite easy after unlocking bootloader, installing custom recovery then flashing su.zip though. But still any pointers where to start my quest wouldn't go a miss ;-)
Recovery
its safe to let rom manager flash clockwork,ive done it
I heared about amonRA but it seemed like clockworkmod was more commonly used so I went for that, but yeah it's fine to flash a new recovery, just remember that whilst it's rare things can go wrong, it's YOUR fault not anyone's here regardless of the advice you may get here if your phone gets bricked or screwed up.
That said I'm still new to this but I'm learning as I'm going, just remember to backup your phone using rom manager before doing anything major so that you can always recover your phone/rom.
I started out hacking my nokia 5800 so was keen to have a go with the android platform.
Sent from my Nexus One using XDA Premium App
CM7 stable
Have you upgraded to cm 7 stable? its a definate upgrade
This is my FINAL VERSION of my Idiots Guide for the HP Touchpad. Now that a stable enough version of CM10 is available, I finally created a guide for you.
Here are links to the files you will need:
CM10 03/04/2012 Build
GAPPS 10/11/2012
ACMEInstaller3
Moboot 3.8
Anything else that you might need, you'll find on http://www.reverendkyle.com
Thanks for the video. It came just in time as I just purchased a used TP that had an older version of android ICS already on it and I wanted to upgrade but seeing as how this is the first device I have sort of inherited already rooted, it is hard to just jump in and know everything that I would have learned from the beginning like i did with my previous phones.
Anyways, I did everything you said except I used the newest AOKP rom. But my tp is still booting to the older version of android that I had on it. Any ideas? Feel free to pm me if you prefer that.
aujbman said:
Thanks for the video. It came just in time as I just purchased a used TP that had an older version of android ICS already on it and I wanted to upgrade but seeing as how this is the first device I have sort of inherited already rooted, it is hard to just jump in and know everything that I would have learned from the beginning like i did with my previous phones.
Anyways, I did everything you said except I used the newest AOKP rom. But my tp is still booting to the older version of android that I had on it. Any ideas? Feel free to pm me if you prefer that.
Click to expand...
Click to collapse
If the AOKP ROM is using a unique uImage file, then you may see two different entries on your moboot screen for two different Android builds.
What does your moboot menu have in it?
Maybe your install failed. Try downloading and flashing it again. If you're trying AOKP JB, you should wipe both /data and dalvik cache to avoid a boot loop!
If using AcmeInstaller3 remember to rename the ROM with ”update-” at the beginning so that it looks like update-AOKPJB_UnOfficial.zip
Sent from my SAMSUNG-SGH-T989 using xda premium
-SGA- said:
Maybe your install failed. Try downloading and flashing it again. If you're trying AOKP JB, you should wipe both /data and dalvik cache to avoid a boot loop!
If using AcmeInstaller3 remember to rename the ROM with ”update-” at the beginning so that it looks like update-AOKPJB_UnOfficial.zip
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I believe it was the "update-" thing that was keeping it from updating. I followed another video tutorial which provided files that had the "update" in front of them and it worked.
I haven't tried yet but now that it worked will the regular method of wiping and flashing through recovery work? (Like, if I want to try out different JB Roms) Are there any files that need to be in a particular place for the recovery method to work? I tried that method first and it would never take, would always revert back to the original version. Don't know if, because I just jumped in and haven't been here from the beginning, I am just missing a necessary step that is hardly even talked about anymore.
Love your work Rev! Thank you again for everything that you do!
Update went like clockwork, unfortunately I can't seem to get the camera to work (not a terrible loss, but I was sorta excited to see it actually working with this release).
Jubmasterflex said:
Love your work Rev! Thank you again for everything that you do!
Update went like clockwork, unfortunately I can't seem to get the camera to work (not a terrible loss, but I was sorta excited to see it actually working with this release).
Click to expand...
Click to collapse
I can attest to the improved battery life on this cm10 build. Amazingly, it holds battery life when it's sleeping now.
Thank you so much for taking the time in making the video for us. Your instructions are easy to follow, hard for anyone to mess up.
(The hosting site for the files is not working, not sure if you were aware)
Hi, I have CM9 running on my TP. With the latest release, the camera works great. But before updating it to CM10, I'd like to know about the issues currently in this build.
Thanks.
Where does one go when the goo.im site appears down, to get the needed files? Mirror somewhere?
ljderm said:
Where does one go when the goo.im site appears down, to get the needed files? Mirror somewhere?
Click to expand...
Click to collapse
Don't go for external mirrors unless some recognized developer suggests them. Best will be to wait for goo.im to come up again, being a prime site, it won't be down for long.
The goo servers do appear to go down on occasion. They always come back up a bit later.
Problem with installing GAPPS using ACMEInstaller3
Excellent tutorial for an idiot like me. Thanks for again for the guide! Question:
I followed the instructions step by step and was able to get CM10 installed successfully. However, I wasn't able to get GAPPS installed using this method. From researching I understand sometimes there is a problem installing GAPPS through ACMEInstaller3 and one can simply get GAPPS installed through CWM Recovery. However, I would like to use/have TWRP instead so is there a way to get GAPPS installed properly through ACMEInstaller3 and then I can install TWRP through GooManager?
Alternatively, is there a way to install GAPPS without using CWM Recovery?
Or, I guess I can install CWM Recovery first, then install TWRP Recovery, then remove CWM Recovery while keeping TWRP and not go back to the stock Recovery? I tried to search the forums and wasn't able to find instructions on removing CWM Recovery WHILE still keeping CM10 and not go back to the Stock recovery.
Any help would be much appreciated. Thanks in advance for your help.
@reverendkjr - appreciate your videos. they're awesome. definitely helped me (and several other friends) many times and saved a ton of time. super easy to follow.
Yes you can install TWRP normally, flash gapps in CWM then install goomanager app, open and click the 3 dot menu and install custom recovery script then it will install it
Now using a root file manager go to the directory called boot and delete uimage.cwm.img (this is from memory but still should be correct
Sent from my cm_tenderloin using XDA Premium HD app
waynekirby said:
Yes you can install TWRP normally, flash gapps in CWM then install goomanager app, open and click the 3 dot menu and install custom recovery script then it will install it
Now using a root file manager go to the directory called boot and delete uimage.cwm.img (this is from memory but still should be correct
Sent from my cm_tenderloin using XDA Premium HD app
Click to expand...
Click to collapse
Dumb question. I had dual boot installed with moboot and one day my dumbarse clicked erase SD card.well it did...EVERYTHING accept twrp. I successfully reinstalled webos and installed preware. Its actually pretty cool.its like a fledgling play store for webos. Now....where should i go from here.i no longer think twrp is on it. All i have is webos with preware.sorry if this is newbie
Sent from my Galaxy Nexus using xda premium
Crwolv said:
Dumb question. I had dual boot installed with moboot and one day my dumbarse clicked erase SD card.well it did...EVERYTHING accept twrp. I successfully reinstalled webos and installed preware. Its actually pretty cool.its like a fledgling play store for webos. Now....where should i go from here.i no longer think twrp is on it. All i have is webos with preware.sorry if this is newbie
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
My goodness you have forgotten everything, you will need to install acmeuninstaller 3, moboot, CMW and the rom you want along with the relevant gapps. Sounds complicated this thread will make it easy
http://forum.xda-developers.com/showthread.php?t=2147284 and has all the necessary links. Have fun.
Sent from my Transformer Prime TF201 using Tapatalk 2
Heck ya i did lol. That refreshed my memory instead of a long video. Thank yo very much
Awesome!
Sent from my cm_tenderloin using xda app-developers app
Great vid!! Finally got CM10 on my Touchpad.
so i got my g2 back from lg after getting the screen repaired. and of course they set it back to stock. now i expected this and made a backup of cyanogenmod thinking i could just root put on a recovery and reflash the backup and be done super quick.
well i had a hell of a time getting the recovery on but its on there now running newest philz however after I flashed my backup i got stuck in a boot loop. luckily i also kept a copy of the original download of the rom. i checked the md5 and its good however even after doing a clean wipe and install of the base rom i still get stuck in a boot loop. this has been a huge headache and i have no idea what i did wrong.
omega52390 said:
so i got my g2 back from lg after getting the screen repaired. and of course they set it back to stock. now i expected this and made a backup of cyanogenmod thinking i could just root put on a recovery and reflash the backup and be done super quick.
well i had a hell of a time getting the recovery on but its on there now running newest philz however after I flashed my backup i got stuck in a boot loop. luckily i also kept a copy of the original download of the rom. i checked the md5 and its good however even after doing a clean wipe and install of the base rom i still get stuck in a boot loop. this has been a huge headache and i have no idea what i did wrong.
Click to expand...
Click to collapse
is the one you flashed from here http://download.cyanogenmod.org/?device=ls980 and also did you flash gapps after flashing rom?
XxZombiePikachu said:
is the one you flashed from here http://download.cyanogenmod.org/?device=ls980 and also did you flash gapps after flashing rom?
Click to expand...
Click to collapse
yes it is the 03-08 snapshot... no i did not flash gapps... and i can't get an up-to-date one on there either because i can't figure out how to get the thing to mount to my computer while in recovery
still scratching my head on why i don't have KK gapps though...
edit hang on ive got a 10.2 nightly and jb gapps i might have something here will report shortly... nvm i think... it locks up saying "using legacy property environment for update-binary...please upgrade to latest binary"
omega52390 said:
yes it is the 03-08 snapshot... no i did not flash gapps... and i can't get an up-to-date one on there either because i can't figure out how to get the thing to mount to my computer while in recovery
still scratching my head on why i don't have KK gapps though...
Click to expand...
Click to collapse
well naturally after flashing cm you have to flash a gapps also did you make a nandroid backup
XxZombiePikachu said:
well naturally after flashing cm you have to flash a gapps also did you make a nandroid backup
Click to expand...
Click to collapse
but cm should still at least boot w/o gapps i've done that with this phone before (when i first got it) and of course i didn't do a nandroid because thats the smart thing to do T_T i was running low on space and figured this was going to be so easy but of course murphy's law got the better of me.
omega52390 said:
but cm should still at least boot w/o gapps i've done that with this phone before (when i first got it) and of course i didn't do a nandroid because thats the smart thing to do T_T i was running low on space and figured this was going to be so easy but of course murphy's law got the better of me.
Click to expand...
Click to collapse
well unless you have adb access to push a zip to your device then that means another trip back to stock(I know what it means to be out of space which is why I actually have an otg with pendrives as my backup) and after that you might want to try one of the latest nightly's and if it still bootloops then there just might be something broken in the builds, you would have to get support from someone who uses the same device/cm
XxZombiePikachu said:
well unless you have adb access to push a zip to your device then that means another trip back to stock(I know what it means to be out of space which is why I actually have an otg with pendrives as my backup) and after that you might want to try one of the latest nightly's and if it still bootloops then there just might be something broken in the builds, you would have to get support from someone who uses the same device/cm
Click to expand...
Click to collapse
thats the thing i've only ever had trouble with adb coudl never wrap my head around it let alone get it to work
w00h0000 i figured it out after a bunch of reading and failing i figured out that my problem was the ZVA radio had reasserted itself however the fix others were talking about wasnt' working then i remember i had a stock rom backed up in twrp so i tried sideloading twrp (btw i got adb working XD) and boom still nothing then after a bunch of stressing i tried installing a zv8 radio and boom back into a stock rom and i am now reinstalling cm at least now if it fails I have a fall back XD
omega52390 said:
w00h0000 i figured it out after a bunch of reading and failing i figured out that my problem was the ZVA radio had reasserted itself however the fix others were talking about wasnt' working then i remember i had a stock rom backed up in twrp so i tried sideloading twrp (btw i got adb working XD) and boom still nothing then after a bunch of stressing i tried installing a zv8 radio and boom back into a stock rom and i am now reinstalling cm at least now if it fails I have a fall back XD
Click to expand...
Click to collapse
I completely forgot about the zva radio(I had helped someone in the past with a similar issue) and that's great news you by adb working that will make things easier since it gives you more options to fall back on, awaiting to see if you managed to get cm running
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
XxZombiePikachu said:
I completely forgot about the zva radio(I had helped someone in the past with a similar issue) and that's great news you by adb working that will make things easier since it gives you more options to fall back on, awaiting to see if you managed to get cm running
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
for some reason cm is still failing to load im going to try installing cm then putting on furnace kernel
edit i remember and succeeded in recreating my secret recipe. first i have an old twrp and 10.2 unofficial nightly thats where i am now. next ill put on a new CWM philz and try putting my CM backup on
another update i finally got my cm 11 backup running however it appears there is damage to the install from back when i made the backup do you know of anyway of repairing an install w/o having to do a reset? really the only noticable problem right now is that i can't use any live wallpapers :/
So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.
rmngorelov said:
So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.
Click to expand...
Click to collapse
Restore from nandroid backup. I hope you made one. Try going into recovery do a factory reset and wipe all cache and data and what not and then install a ROM from Odin.
rmngorelov said:
So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.
Click to expand...
Click to collapse
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware): https://mega.co.nz/#F!0JdRkIZR!AqqKdbvba_Hpg5VrCmrbPw
i7vSa7vi7y said:
Restore from nandroid backup. I hope you made one. Try going into recovery do a factory reset and wipe all cache and data and what not and then install a ROM from Odin.
Click to expand...
Click to collapse
I restored to this stock ROM before and everything worked well. Currently I can't boot into recovery, Samsung flashes once and that's it, that's why I'm desperate the only thing I can do is boot in to download mode for odin.
silentdeath631 said:
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware):
Click to expand...
Click to collapse
Does it matter that I can't get into recovery to clear the cache first before trying new roms?
silentdeath631 said:
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware):
Click to expand...
Click to collapse
Maybe I'm doing something foolish but every time I try to download files from the link you gave I get a decryption error so I can't download them zip or original.
rmngorelov said:
I restored to this stock ROM before and everything worked well. Currently I can't boot into recovery, Samsung flashes once and that's it, that's why I'm desperate the only thing I can do is boot in to download mode for odin.
Click to expand...
Click to collapse
Just hold home power and volume up. Right when you see text at the top left let go. You have to have the right timing
i7vSa7vi7y said:
Just hold home power and volume up. Right when you see text at the top left let go. You have to have the right timing
Click to expand...
Click to collapse
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.
rmngorelov said:
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.
Click to expand...
Click to collapse
Depends what recovery you had and what version. I personally like Philz touch recovery but TWRP is good. Now wipe and flash a ROM my friend or restore a backup
rmngorelov said:
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.
Click to expand...
Click to collapse
im having similar issues. which version of TWRP worked for you?
thank you
fearthemarchx said:
im having similar issues. which version of TWRP worked for you?
thank you
Click to expand...
Click to collapse
I recommend flashing the newest one here using odin
http://teamw.in/project/twrp2
Then once you are able to boot into recovery go to wipe and perform both factory reset and format data. Then install whatever rom you like, I used Sprint Galaxy S4 SPH-L720 VPUFNAE (Androdi 4.4.2) found here
http://galaxys4root.com/galaxy-s4-stock-firmware/ (or maybe find a newer stock rom if this one gives you errors)
Just copy the zip file to the phone, boot into twrp, do wipe factory reset again, select install then select the zip in whatever directory and you should be good to go. Make sure you do a back up in twrp once you get the phone to boot so you can always revert to stock.
I hope I was thorough enough that some of the information was useful. Let me know if you need any more help.
only certain recoveries will stick. ive tried the most recent twrp, with no luck. only a few versions of philztouch work.
Sent from my LGL34C using XDA Free mobile app
fearthemarchx said:
only certain recoveries will stick. ive tried the most recent twrp, with no luck. only a few versions of philztouch work.
Sent from my LGL34C using XDA Free mobile app
Click to expand...
Click to collapse
Format with philztouch that works then try flashing a new stock rom with odin. That should bring everything back to stock including the recovery.
ive tried. when i flash rom via odin i only get a blue "recovery booting" at the top of boot screen. even when i only power on, not into recovery. im going to attempt to flash rom provided in previous post via philz.
Sent from my LGL34C using XDA Free mobile app
fearthemarchx said:
ive tried. when i flash rom via odin i only get a blue "recovery booting" at the top of boot screen. even when i only power on, not into recovery. im going to attempt to flash rom provided in previous post via philz.
Sent from my LGL34C using XDA Free mobile app
Click to expand...
Click to collapse
You're in download mode when you flash from odin right? If you your getting an error flashing, try a different stock rom after reformating/resetting to factory (it's crucial to clear the cache before trying a different rom). I had to try a few roms before I found one that worked.