having problems flashing a lollipop ROM. Ive never had any problems like these in the past, all other upgrades have gone smoothly
I am running into two problems. Either I will get stuck staring at a boot animation which never goes away, or I actually get through and all Google services go crazy and force close, with the google first time setup repeatedly trying to start and force closing itself so it is impossible to do anything on the phone.
The best I have done so far is flash a ROM without Gapps, but then for some reason I was not able to download any apks so there was no way to get the Play store on the phone.
If anyone could help me I'd appreciate it
brettzz said:
having problems flashing a lollipop ROM. Ive never had any problems like these in the past, all other upgrades have gone smoothly
I am running into two problems. Either I will get stuck staring at a boot animation which never goes away, or I actually get through and all Google services go crazy and force close, with the google first time setup repeatedly trying to start and force closing itself so it is impossible to do anything on the phone.
The best I have done so far is flash a ROM without Gapps, but then for some reason I was not able to download any apks so there was no way to get the Play store on the phone.
If anyone could help me I'd appreciate it
Click to expand...
Click to collapse
I was under exact same position. downloaded 2-3 lollipop rom, different size of gapps from diff sites same place.
solution is to flash factory image and everything works. now I am waiting for 5.1 OTA update and later try again few roms.
So best flash factory image as of now.
just as an update I tried a different kitkat rom and it went smoothly
not sure why lollipop is not working, one difference is when I reboot from recovery after flashing lollipop it tells me root may have been lost, and I get an option for 'yes, fix root' and it reboots.. when flashing kitkat didnt see that message it just rebooted
brettzz said:
just as an update I tried a different kitkat rom and it went smoothly
not sure why lollipop is not working, one difference is when I reboot from recovery after flashing lollipop it tells me root may have been lost, and I get an option for 'yes, fix root' and it reboots.. when flashing kitkat didnt see that message it just rebooted
Click to expand...
Click to collapse
What recovery and version are you using. You may have to update your recovery.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
What recovery and version are you using. You may have to update your recovery.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
hm looks like I was on a slightly outdated one I have updated and will see if this works now
brettzz said:
hm looks like I was on a slightly outdated one I have updated and will see if this works now
Click to expand...
Click to collapse
aha that did it
thank you very much!
Related
i have a nexus thats completely stock( out of the box) worked fine for about a month, let the tablet die and has been unplugged for about a week. got it charged up and and would not turn on. using the nexus root toolkit i was able to get to turn on. unlocked the device( unlock logo below google icon on startup) was unable to get past that point. now finally i can get past the nexus boot logo but it gets stuck on aindroid is upgrading " optimizing app 1 of 11" i cant root using the root tool kit bc when i unlocked device it got rid of developer options ( by what the msg said before i unlocked). im simply trying to get my device to turn back on. i dont plan to root or install a rom, im fine with the stock rom. i just want to damn device to turn back on. when i was able to power on the device when i first got it i did upgrade to the newest jelly bean rom. any one can help me on this issue ??
thanks
Boot into temporary custom recovery using Nexus root toolkit(Advance menu). Now wipe cash and devlock than try rebooting into system. If it doesn't work you can try factory reset. Last but not the least will be Flash Stock + Unroot(Soft brick/boot loop).
ok i wiped cache and devlock was able to to pass the nexus logo into what looks like another android is upgrading screen it got up to 14 of 20 and froze. between my 1st post and yours i was able to get android to fully run. did all the 1st time setup but after about a couple screen taps the device kept freezing and coming up with crash reports. there were a few times that the stock launcher even forced close. after a couple of restarts it finally quit again and would not even pass the nexus logo. ill try to do the other options that u stated in your post. any other thoughts ?
dac2009 said:
ok i wiped cache and devlock was able to to pass the nexus logo into what looks like another android is upgrading screen it got up to 14 of 20 and froze. between my 1st post and yours i was able to get android to fully run. did all the 1st time setup but after about a couple screen taps the device kept freezing and coming up with crash reports. there were a few times that the stock launcher even forced close. after a couple of restarts it finally quit again and would not even pass the nexus logo. ill try to do the other options that u stated in your post. any other thoughts ?
Click to expand...
Click to collapse
If the factory reset doesn't work just go for the Flash. I don't think you are much worried about the data so it's not a big deal for you. and I'm quit sure this is gonna work. Best of luck.
ok did that. went smooth but then once again it just gets stuck at the nexus logo. waited for over 10 mins like the notes say after re flashing and nothing. so i did a restart this time it passed the nexus logo, went to android is upgrading optimizing app and gets stuck at 4 of 11. being that this is pure android are there custom roms out there that i could try to flash via odin. ive rooted and installed roms before on my other android devices no problem but they were never pure google. am i missing something here. also what would cause a brand new nexus 7 just to go "ape ****" on its self.
dac2009 said:
ok did that. went smooth but then once again it just gets stuck at the nexus logo. waited for over 10 mins like the notes say after re flashing and nothing. so i did a restart this time it passed the nexus logo, went to android is upgrading optimizing app and gets stuck at 4 of 11. being that this is pure android are there custom roms out there that i could try to flash via odin. ive rooted and installed roms before on my other android devices no problem but they were never pure google. am i missing something here. also what would cause a brand new nexus 7 just to go "ape ****" on its self.
Click to expand...
Click to collapse
Okay, that's weird!!!
Are you using Nexus Root Toolkit?? If yes are you using pre-downloaded android??
Try Automatically download + Extract.....
Last of all I'm really confused how there could be a problem when you got a fresh OS and Stock.
I agree with the messing thing that you told... Try checking and double checking everything... Check if you have selected the correct device or not.
And do a full wipe(including system) using TWRP before flashing again.
Edit: Make sure you are using the latest toolkit. You can get it from the link bellow.
http://forum.xda-developers.com/showthread.php?t=1766475
Try flash stock image throught toolkit.
i have the most current root toolkit. i installed the rom that was available to download via the app which was android 4.2.2 jdq39
dac2009 said:
i have the most current root toolkit. i installed the rom that was available to download via the app which was android 4.2.2 jdq39
Click to expand...
Click to collapse
I don't see a way how the problem still exists... :S
Whatever the problem is it's seems to be with android OS. But how it exists in completely new android. Sorry can't find a reason behind the problem. You can still try flashing any older android (like 4.1.2).
ok i got a zip of stock 4.1.2 and using the root tool kit i can install a zip via the twrp but it wont let me bc it says adb device not found and that developer options need to be turned on. im un able to turn it on bc i cant even get into the rom on the device.
thanks
ok i got it working. i was able to flash the older rom to my device and its working so far. no force closes yet.
thanks for everyone's help
ok im about to throw this tablet out the window. was messing around with the tablet and it auto installed ( well at least tried to) the 4.2 update. it downloaded the update went to install and now im stuck at this screen(check pic) and cant even get it into recovery mode. im at the point now to cut my loss and say the hell with it. anyone else have any ideas on whats my next step. the thing that wireds me out is of the roms ive been able to use it all works great for only about 5 mins. it seems like the more i touch the screen to do anything it will freeze on me(it will do it after 5 mins or so after a restart). https://www.dropbox.com/s/arnauysa4oglp5b/2013-05-21%2018.37.24.jpg
dac2009 said:
ok im about to throw this tablet out the window. was messing around with the tablet and it auto installed ( well at least tried to) the 4.2 update. it downloaded the update went to install and now im stuck at this screen(check pic) and cant even get it into recovery mode. im at the point now to cut my loss and say the hell with it. anyone else have any ideas on whats my next step. the thing that wireds me out is of the roms ive been able to use it all works great for only about 5 mins. it seems like the more i touch the screen to do anything it will freeze on me(it will do it after 5 mins or so after a restart). https://www.dropbox.com/s/arnauysa4oglp5b/2013-05-21 18.37.24.jpg
Click to expand...
Click to collapse
I can't just think of anything else. Just telling you the things that I'd have done if I were you.
* reinstall boot
* change kernel
* turn off the auto update of android.
* try some costume room.
Don't throw it out the window you call always donate it to me if you really wanna throw it or make a drop test video...
Last of all just don't lose hope keep trying. you'll find out something surely and share it with us.
Sent from my Nexus 7 using XDA Premium HD app
Daft question, but the few times you managed to get it running, was your Wifi on?
Sent from my GT-I9300 using xda app-developers app
yes my wifi was on and was able to stream . spotify among other things
Not the exact same situation, but I found certain Wifi router's would trip my nexus into reboots until I rooted
Sent from my GT-I9300 using xda app-developers app
Phone is stuck in "Android is upgrading. Optimizing application 1 of 1" HELP!!!!!!!!!
hey guys, my phone is stuck in "Android is upgrading. Optimizing application 1 of 1"
and all I can do is
1. apply sdcard/update.zip
2. reboot system now ( does NOT work coz it brings me back to optimizing apps )
3. apply update from external storage
4. wipe data / factory reset
5. wipe cache partition
6. apply update from cache
is there a way i can backup first all my files before factory resetting my phone (if thats the only option i have)????
help me please
Help me XDA, you're my only hope...
First, background: I bought my Nexus 4 over the internet, because it was never officially released in Belgium. I had to have the screen replaced, and let a 3rth party do it. Glass damage isn't covered by the warranty and it would mean sending my phone by international mail if i used the official warranty people. They told me that the also had to replace the proximity sensor.
My phone worked perfectly afterwards. Until I tried to install the automatic upgrade to 4.3.
First it stopped at the X-logo screen and became very hot. I contacted play support and did all the things they advised (including a factory reset, rebooting in safe mode), none of it works. I found someone with the same problem who managed to get past the X-screen by flashing back the 4.2.2 radio version. And that worked: the phone booted and the update started.
However, since that moment I got a lot of problems:
- random shutdowns
- random locking of the SIM card
- phone not starting unless plugged in charger.
Worst of all, reflashing stock images for 4.2 and 4.2.2 or AOKP does nothing to solve these problems. I also tried a new SIM card, and still nothing.
I'm at my wit's end now. Could there be a driver issue? Any other things I can try?
TIA
Possibly a driver issue and also reflashing does not help meaning that you need to flash an other kernel.
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Possibly a driver issue and also reflashing does not help meaning that you need to flash an other kernel.
Click to expand...
Click to collapse
any suggestions for a good kernel that can run stock android?
If your goal was to upgrade to stock 4.3, you can follow efrant's guide to flash the factory image at at http://forum.xda-developers.com/showthread.php?t=2010312&highlight=efrant. Just be sure to download the JWR66V image and use the updated file names when you flash since the file names in this guide are for the Android 4.2 image.
BobWalker said:
If your goal was to upgrade to stock 4.3, you can follow efrant's guide to flash the factory image at at http://forum.xda-developers.com/showthread.php?t=2010312&highlight=efrant. Just be sure to download the JWR66V image and use the updated file names when you flash since the file names in this guide are for the Android 4.2 image.
Click to expand...
Click to collapse
Well, I tried again. (For the 6th time this month) No different as before: it's been stuck on the X screen for 20 minutes now and getting warmer.
EDIT: I finally managed to get into the recovery menu. No idea why it wouldn't let me use volume up + power...
As suggested in the guide I deleted cache and a factory wipe.
My phone is still stuck at the X screen...
any other suggestions, anyone?
Joenr76 said:
As suggested in the guide I deleted cache and a factory wipe.
My phone is still stuck at the X screen...
any other suggestions, anyone?
Click to expand...
Click to collapse
Try installing PA 3.97 with this kernel: http://goo.im/devs/paranoidandroid/roms/mako/pa_mako-Kernel-4.3_JWR66V_HALFBREED.zip
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Try installing PA 3.97 with this kernel: http://goo.im/devs/paranoidandroid/roms/mako/pa_mako-Kernel-4.3_JWR66V_HALFBREED.zip
Click to expand...
Click to collapse
I never did that before: do I flash the kernel first or the Rom first? Are there any guides?
EDIT: I just read that Paranoid Android comes with the halfbreed kernel included. Is that the one you linked too?
Before jumping into the kernel thing (also because i wanted to be able to work with a device that can actually boot), I reinstalled the 4.2.2 factory image. It took about 5 minutes for the first shutdown to happen. *sigh*
And without plugging it in, it goes into a boot loop (going to x screen for a while, then restarting.) When I plug it in, it starts immediately, but shows the battery as empty. It was 63% when it shut itself down.
It's a clean install, I just don't understand...
Okay so, I'm assuming you have a custom recovery like TWRP. Open it and flash the newest boot loader and radio. Then flash Paranoid Android and GApps. Then try flashing Faux kernel and clearing cache/dalvik. If you still have problems, then I have no idea
Sent from my Nexus 4 using xda premium
Open up your phone to see the battery is securely checked and to see if all the components are okay. Then look do a full wipe of cache,dalvik,system,data,and sd (internal storage). Then use wugs toolkit to a upgrade on a clean flash. Double check to make sure you wipe everything!
Sent from my Nexus 4 using Tapatalk 4
TheNerd:] said:
Open up your phone to see the battery is securely checked and to see if all the components are okay.
Click to expand...
Click to collapse
Apparently, my battery had expanded so much that it was pushing at everything in the phone. I ordered a new one and put it in. In 4.2.2 I have no problems anymore with random shut-downs.
However, when I run the OTA upgrade, the phone stays on the X-logo screen. Just like last time. I expect that was why the battery got blown: the first time I ran the OTA, I did it at night and only checked the phone in the morning.
I fixed my N4 by reflashing an older radio (48, IIRC). I have no idea why the newest radio won't work...
Joenr76 said:
Apparently, my battery had expanded so much that it was pushing at everything in the phone. I ordered a new one and put it in. In 4.2.2 I have no problems anymore with random shut-downs.
However, when I run the OTA upgrade, the phone stays on the X-logo screen. Just like last time. I expect that was why the battery got blown: the first time I ran the OTA, I did it at night and only checked the phone in the morning.
I fixed my N4 by reflashing an older radio (48, IIRC). I have no idea why the newest radio won't work...
Click to expand...
Click to collapse
Try flashing 4.3 via the factory image. Then use this guide to flash the factory image to the phone.
tykate said:
Try flashing 4.3 via the factory image. Then use this guide to flash the factory image to the phone.
Click to expand...
Click to collapse
Tried that before. I did some research and I guess this is relevant: http://www.androidpolice.com/2013/0...rops-on-some-nexus-4-handsets-fixes-in-sight/ Especially since I ordered my Nexus from the Netherlands.
I'll have to wait until that bug gets fixed until I can upgrade my radio.
So i just installed the freegs4 rom and i have done everything according to the forums including reverting my twrp installer and it installs and works just fine until i have to restart the device. As soon as the device is restarted it freezes at the samsung splash screen and i have to wipe the rom again and reinstall. Ii can use it until i have to reboot then it same thing all over again
bigdaddybx2 said:
So i just installed the freegs4 rom and i have done everything according to the forums including reverting my twrp installer and it installs and works just fine until i have to restart the device. As soon as the device is restarted it freezes at the samsung splash screen and i have to wipe the rom again and reinstall. Ii can use it until i have to reboot then it same thing all over again
Click to expand...
Click to collapse
Make sure you dont have a bad download. Also try flashing a different kernel. Btw this goes in the question section
ROMANTiC KiD said:
Make sure you dont have a bad download. Also try flashing a different kernel. Btw this goes in the question section
Click to expand...
Click to collapse
I have tried different downloads and when i use a different kernel the wifi will not turn on, i have also done the md5 validation on the rom and its fine. sorry about posting in the wrong area im new to this.
Sounds like your phone might be in factory mode.. Did you wipe EFS in recovery?
Sent from my SPH-L720 using Tapatalk 4
bigdaddybx2 said:
So i just installed the freegs4 rom and i have done everything according to the forums including reverting my twrp installer and it installs and works just fine until i have to restart the device. As soon as the device is restarted it freezes at the samsung splash screen and i have to wipe the rom again and reinstall. Ii can use it until i have to reboot then it same thing all over again
Click to expand...
Click to collapse
When it freezes on that first reboot, try a battery pull and see if it will boot. If it doesn't, try another battery pull.
Mine actually did that a few times too (freeze on the SAMSUNG screen after first reboot).
freegs4
i have a question i had 2.0 working great.
i have tryed to update to 3.0 multible times.
i went from stock md5 right to 3.0 and have issues with the phone rebooting it works ok but once restarted it will not start back up. i also cant get wifi to work.
i have even downgraded to twrp 5.0.2.
i have flashed my phone back to stock md5, than root than wipe everthing than 3.0 and same issues.
i flashed back to stock md5, than root than stock md9 than wipe than 3.0 still issues
i flashed to rooted and odexed md9 wipe than 3.0 still issues.
i have download both direct and torrent and still stumped why the phone freezes after it reboots and no wifi at all after installation.
anyone have any clues?
tabodt said:
i have a question i had 2.0 working great.
i have tryed to update to 3.0 multible times.
i went from stock md5 right to 3.0 and have issues with the phone rebooting it works ok but once restarted it will not start back up. i also cant get wifi to work.
i have even downgraded to twrp 5.0.2.
i have flashed my phone back to stock md5, than root than wipe everthing than 3.0 and same issues.
i flashed back to stock md5, than root than stock md9 than wipe than 3.0 still issues
i flashed to rooted and odexed md9 wipe than 3.0 still issues.
i have download both direct and torrent and still stumped why the phone freezes after it reboots and no wifi at all after installation.
anyone have any clues?
Click to expand...
Click to collapse
Try a different kernel
Sent from my SPH-L720 using xda app-developers app
So i got my phone replaced and installed the software on it and im no longer having the issue i stated above but i do have a new issue with the call recording. I installed it through the aroma installer and then used update me to install it manually like i was reading in the thread. Everytime I try to make a call (with out even pressing the record button) the screen goes black and there is some call recording icon in the left hand side of the status bar. soon after this i get an error that says com.android.phone has stopped. I have tried to reinstall stock with out call recording but it keeps doing it as if the call recording is there. Am i forced to reset and reinstall the rom?
You might want to give Highway55's MF9 ROM a shot. It has the wifi hot spot mod *and* the status bar toggle already built in. I wrote lengthy post on 9/26 detailing my experience with Highway55 along with the simple steps I took to implement the additional mods that I wanted (including call recording).
ROMANTiC KiD said:
Try a different kernel
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
ROMANTiC KiD said:
Make sure you dont have a bad download. Also try flashing a different kernel. Btw this goes in the question section
Click to expand...
Click to collapse
I think the FreeGS4 ROM has its own AGAT custom kernel. So I don't think you want to do that...
And I've had a few issues with V3.0.0 myself. I just downgraded back to V2.0.0
Salil999 said:
I think the FreeGS4 ROM has its own AGAT custom kernel. So I don't think you want to do that...
And I've had a few issues with V3.0.0 myself. I just downgraded back to V2.0.0
Click to expand...
Click to collapse
Ive had everything running good with chronic kernel and also tested with the kernel it comes with. No problems really.
Sent from my SPH-L720 using xda app-developers app
I loved the built in ad-blocker, but noticed it interfered with hulu plus, watch ESPN, and sometimes xfinity player. I've since removed the ad blocker, but was wondering if there was a work around so that I could keep the ad blocker, but have it not block ads for these apps? Or is there a way to get these apps to work with the ad-blocker in place?
I just got the OTA update to Android 4.4, and being eager to get it installed, hit the install button right away. I told a few people I was going to be a few minutes while installing the update... and tapped the button.
That was three hours ago, roughly.
I'm on a rooted nexus 4 with CWM Touch edition installed as a recovery. I don't know exactly what version right now but it was the latest when I installed it a few months ago.
The install launched CWM, and I waited as the loading bar filled. Right at the end it gave an error message - in a panic I didn't take note of what it was, hit the onscreen buttons and went through a window telling me I might have lost SU permissions - which I told it to fix. The startup animation (with four dots, the new 4.4 animation I guess?) started... and continued for more than five minutes.
I was still panicking and instantly launched back into CWM, downloaded a (I think correct, checked it multiple times, as on does...) update zip from the web, and flashed it via adb sideload. This gave me an "Error 7" and a failed install. I tried again, same result. Then gave up and hit the restart button in the hope that one of the attempts had indeed worked...
I now have a Nexus 4 sitting on my desk playing a nice dotty animation, and it's been doing that for fifteen minutes as of now. I'm intending to leave it as such hoping that it will actually turn on and it's just having a very long boot.
So, the question. Anyone have any ideas how to save my Nexus?
I'd rather like to end up with the data on the device intact (stupidly did not back up before installing and can't get any files off it until an install works) and possibly with Android KitKat running on it, as was the original aim of tonight, but if neither are possible, I'd at least like to end up with a functioning phone... just with any stock rom.
Thanks in advance.
P.S. I'm not new to flashing ROMs manually - my last phone was a ZTE Blade which never ran any ROM well, so I must have flashed on that phone at least ten times, including via ADB.
Ignore the above - I fixed the problem by using fast boot to flash the stock rom from developers.google.com/android/nexus/images ....
I feel really stupid now. But it worked perfectly. All I did was open the flash-all.sh and copy the commands out line by line, but removing the -w from the final command to dodge wiping the device. Anyone confident in Terminal or similar should be fine
Sorry for the thread being created but I really thought I couldn't fix this xD
totally-not-me said:
Ignore the above - I fixed the problem by using fast boot to flash the stock rom from developers.google.com/android/nexus/images ....
I feel really stupid now. But it worked perfectly. All I did was open the flash-all.sh and copy the commands out line by line, but removing the -w from the final command to dodge wiping the device. Anyone confident in Terminal or similar should be fine
Sorry for the thread being created but I really thought I couldn't fix this xD
Click to expand...
Click to collapse
Your post saved me from a complete wipe and reinstall, so thank you for sharing your fix. I had a very similar issue but my Status 7 appeared to be because of my previous root and the new install not being able change the permissions on some /system files.
Now I just need to re-enable root via the NRT.
at least you've learnt something. Ota updates will always fail if you have any cwm recovery installed. Not like it hasn't been discussed before. Guess you won't be making that mistake again.
Can't say anything makes be panic not like nexus devices are hard to recover ☺
Sent from my Nexus 4 using Tapatalk
dethrat said:
at least you've learnt something. Ota updates will always fail if you have any cwm recovery installed. Not like it hasn't been discussed before. Guess you won't be making that mistake again.
Can't say anything makes be panic not like nexus devices are hard to recover ☺
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
To be fair, there are several posts around where people have simply updated their version of CWM and then reported the 4.4 upgrade has worked. I think I must have used the OTA Rootkeeper before as I don't recall these issues (other than losing root) during the 4.3 upgrades.
I'm in a similar boat.
My wife accepted the OTA update with TWRP installed and ended up in a boot loop. We didn't care about the data on the device, so thinking I could start from scratch, I did an Advanced Wipe of everything in TWRP. Now the phone has no OS on it.
I tried doing an adb sideload KitKatNexus4.tgz, but it gives me an error of a corrupted .zip every time.
I'm stumped.
thankyousam said:
To be fair, there are several posts around where people have simply updated their version of CWM and then reported the 4.4 upgrade has worked. I think I must have used the OTA Rootkeeper before as I don't recall these issues (other than losing root) during the 4.3 upgrades.
Click to expand...
Click to collapse
Not blaming you xda has almost become useless in terms of finding real info in the past week. Bombardment of repeated posts about 4.4
Sent from my Nexus 4 using Tapatalk
Lokitez said:
I'm in a similar boat.
My wife accepted the OTA update with TWRP installed and ended up in a boot loop. We didn't care about the data on the device, so thinking I could start from scratch, I did an Advanced Wipe of everything in TWRP. Now the phone has no OS on it.
I tried doing an adb sideload KitKatNexus4.tgz, but it gives me an error of a corrupted .zip every time.
I'm stumped.
Click to expand...
Click to collapse
Sideloading is only for flashable zip packages, not official factory images that required using fastboot. Use the guide links in my signature for instruction to flash factory image.
Or you can use sideload to flash flashable stock roms: http://forum.xda-developers.com/showthread.php?t=2527806
Unless your wife is really into flashing, I suggest just leaving it everything stock.
thankyousam said:
To be fair, there are several posts around where people have simply updated their version of CWM and then reported the 4.4 upgrade has worked. I think I must have used the OTA Rootkeeper before as I don't recall these issues (other than losing root) during the 4.3 upgrades.
Click to expand...
Click to collapse
where did you find these posts? the only thing that I'm reading is people constantly saying "CWM will break OTA" or "you can't flash OTA with custom recovery" (this is clearly wrong)
I have the latest CWM recovery (6.0.4.3) and I don't want to lose it or flash stock recovery and CWM back. with 4.3 I remember that everything went good and I didn't have a lot of problems, the only thing I had to do was to unroot before flashing the OTA from CWM... but this time I'm reading a lot of conflicting posts so I'm a bit worried to try this by myself without some sort of feedback from any other user
RickyBO89 said:
where did you find these posts? the only thing that I'm reading is people constantly saying "CWM will break OTA" or "you can't flash OTA with custom recovery" (this is clearly wrong)
I have the latest CWM recovery (6.0.4.3) and I don't want to lose it or flash stock recovery and CWM back. with 4.3 I remember that everything went good and I didn't have a lot of problems, the only thing I had to do was to unroot before flashing the OTA from CWM... but this time I'm reading a lot of conflicting posts so I'm a bit worried to try this by myself without some sort of feedback from any other user
Click to expand...
Click to collapse
It will softbrick the device, or atleast fail. I don't even have to try CWM, but with TWRP, if I make any changes to the /system partition it failed. I suggest you just flash a stock 4.4 rom: http://forum.xda-developers.com/showthread.php?t=2010887
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.