Related
I Think i have bricked my nexus s ......it wont startup and goes to do first setup but force closes....i can access recovery but when i flash a rom it aborts ....only just bought it
U can odin it back to stock. Check out the android dev forums
Sent from my Nexus S using XDA App
afishpie said:
U can odin it back to stock. Check out the android dev forums
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Please can you elaborate...or point me in right direction......recovery is now only accessible by flashing it first....phone just wont do anything
download a 2.3.3 nandroid backup and restore to it using clockwork recovery
ignore odin.
http://forum.xda-developers.com/showthread.php?t=884093
update to 2.3.3 using http://android.clients.google.com/p...2cf141e6a.signed-soju-ota-102588.f182cf14.zip
or just download CM7 and flash that along with gapps (wipe dalvik/cache/factory)
and your phone is not bricked. the definition of a bricked phone is a phone who cannot access recovery/fastboot/etc.. can access absolutely nothing
Well, he does say that his attempts to flash a rom always abort...
OP, we need more details.
Are you using Clockwork Recovery? Which version? Try an older/newer version...
What ROM are you trying to flash? Have you tried others?
What happens when you try a normal boot? You say you get as far as the first setup screen?
Have you tried a Factory Reset of the phone from within recovery (stock or clockwork)?
distortedloop said:
Well, he does say that his attempts to flash a rom always abort...
OP, we need more details.
Are you using Clockwork Recovery? Which version? Try an older/newer version...
What ROM are you trying to flash? Have you tried others?
What happens when you try a normal boot? You say you get as far as the first setup screen?
Have you tried a Factory Reset of the phone from within recovery (stock or clockwork)?
Click to expand...
Click to collapse
Many thanks to both of you.....for your help .....so much appreciated......i have got past first setup screen after applying a nandroid backup......it finally worked after 5 times trying....but i have stock android recovery but rom manager on phone .....how can i get clockwork mod back as everytime i flash it.....i get to use it for that one instance ans then it returns to stock android recovery
I think it might be okay now ....after titanium said busybox was installed....i dont think it was done correectly.....after downloading busy box from market....recovery seems to be sticking rather then reverting back to android. Just to check....is there anything i should do to check all is well on my phone and also while flashing i think i changed build number from IR to GH (what are the implications of this move? many thanks...phew
EDIT- NO recovery still wont stay....any ideas?
menov321 said:
I think it might be okay now ....after titanium said busybox was installed....i dont think it was done correectly.....after downloading busy box from market....recovery seems to be sticking rather then reverting back to android. Just to check....is there anything i should do to check all is well on my phone and also while flashing i think i changed build number from IR to GH (what are the implications of this move? many thanks...phew
EDIT- NO recovery still wont stay....any ideas?
Click to expand...
Click to collapse
That's normal. See below:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
sano614 said:
That's normal. See below:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
Click to expand...
Click to collapse
Thankyou SOOO MUCH.....you put my mind at rest......can you maybe help me with one other thing.....WHEN I MESSED UP EARLIER i flashed a different rom build.....does this have any negative affect on the phone....my stock rom was a IR something but i flashed a GR or GH something....
menov321 said:
Thankyou SOOO MUCH.....you put my mind at rest......can you maybe help me with one other thing.....WHEN I MESSED UP EARLIER i flashed a different rom build.....does this have any negative affect on the phone....my stock rom was a IR something but i flashed a GR or GH something....
Click to expand...
Click to collapse
No it doesn't. You're fine. The latest is android 2.3.3 with GRI40.
Sent from my Nexus S using Tapatalk
First, let me get the formalities out of the way... long time lurker, first time poster. I hope you guys can help me out!
My GS4 semi-bricked while trying to restore my phone from LiquidSmooth ROM . My phone had no MAC address nor IP address after I flashed to LiquidSmooth, so I figured I needed to restore files I may have accidentally deleted.. The phone became stuck on the splash screen so I tried pulling the battery, going into recovery, and clearing cache/dalvik. No luck.
So then I tried to restore using a backup that I had made before flashing, but then it got stuck on the AT&T screen. Tried to clear cache/dalvik, but it didn't work. I thought maybe the back up didn't work because I was flashed into a different ROM, so I downloaded this stock rom by scrosier, and tried again... but to no avail.
Now I want to try flashing the phone back to stock, but I have a early 2008 MacBook running 10.7.5 (Lion). Odin is windows only, and Heimdall doesn't work on my version of OS X (keeps crashing the moment I open it). I thought maybe updating my MacBook to Mountain Lion (10.8) might work, but Mountain Lion is not supported on my Macbook, thus cannot update OS X... and I don't have access to a PC at this moment either.
Is my only option to go out and buy windows and install on bootcamp? Does anyone know if I could flash my phone back to stock using the computer I have now?
Sorry if my post didn't make any sense. I'm in a hurry and I want to fix my phone already! Thanks in advance
EDIT:
I have TWRP 2.5.0.3 on my phone
sebbo1 said:
First, let me get the formalities out of the way... long time lurker, first time poster. I hope you guys can help me out!
My GS4 semi-bricked while trying to restore my phone from LiquidSmooth ROM . My phone had no MAC address nor IP address after I flashed to LiquidSmooth, so I figured I needed to restore files I may have accidentally deleted.. The phone became stuck on the splash screen so I tried pulling the battery, going into recovery, and clearing cache/dalvik. No luck.
So then I tried to restore using a backup that I had made before flashing, but then it got stuck on the AT&T screen. Tried to clear cache/dalvik, but it didn't work. I thought maybe the back up didn't work because I was flashed into a different ROM, so I downloaded this stock rom by scrosier, and tried again... but to no avail.
Now I want to try flashing the phone back to stock, but I have a early 2008 MacBook running 10.7.5 (Lion). Odin is windows only, and Heimdall doesn't work on my version of OS X (keeps crashing the moment I open it). I thought maybe updating my MacBook to Mountain Lion (10.8) might work, but Mountain Lion is not supported on my Macbook, thus cannot update OS X... and I don't have access to a PC at this moment either.
Is my only option to go out and buy windows and install on bootcamp? Does anyone know if I could flash my phone back to stock using the computer I have now?
Sorry if my post didn't make any sense. I'm in a hurry and I want to fix my phone already! Thanks in advance
Click to expand...
Click to collapse
If you are able to access recovery then do this:
Put Liquid Smooth and its gapps on the external card using a card reader
Go into recovery, factory reset, wipe both caches, format /system, flash the rom and gapps, reboot
Colonel Sanders said:
If you are able to access recovery then do this:
Put Liquid Smooth and its gapps on the external card using a card reader
Go into recovery, factory reset, wipe both caches, format /system, flash the rom and gapps, reboot
Click to expand...
Click to collapse
I actually tried to reflash Liquid Smooth and wiped cache / factory reset, but once it reboots, a screen pops up that says "Android is updating" and updates 120 files. However, when it finishes, it gives me an error along the lines of "Unfortunately... something something," and instantly reboots. Then it hangs on the Liquid Smooth splash screen. Couldn't get a good look at what the message said because it happens so quickly.
sebbo1 said:
I actually tried to reflash Liquid Smooth and wiped cache / factory reset, but once it reboots, a screen pops up that says "Android is updating" and updates 120 files. However, when it finishes, it gives me an error along the lines of "Unfortunately... something something," and instantly reboots. Then it hangs on the Liquid Smooth splash screen. Couldn't get a good look at what the message said because it happens so quickly.
Click to expand...
Click to collapse
Then I suggest you flash a different ROM. Try out Slim. Liquid Smooth is just a Slim ripoff.
Put Slim and the Addons on the SD, and flash it like you would when changing ROMs. A clean wipe.
Colonel Sanders said:
Then I suggest you flash a different ROM. Try out Slim. Liquid Smooth is just a Slim ripoff.
Put Slim and the Addons on the SD, and flash it like you would when changing ROMs. A clean wipe.
Click to expand...
Click to collapse
I'll give that a shot. Do you recommend the new 4.3 Google Edition Slim Rom?
sebbo1 said:
I'll give that a shot. Do you recommend the new 4.3 Google Edition Slim Rom?
Click to expand...
Click to collapse
That's not Slim, he just put Slim because it's slimmed down. I haven't personally tried it. I'm a tester for SlimRoms, so thats all I ever run. Test builds. It does look nice though, but it won't have near the customization of Slim.
Colonel Sanders said:
That's not Slim, he just put Slim because it's slimmed down. I haven't personally tried it. I'm a tester for SlimRoms, so thats all I ever run. Test builds. It does look nice though, but it won't have near the customization of Slim.
Click to expand...
Click to collapse
Are you talking about slimroms.net? If you are, which addons do I download?
EDIT: nevermind. I downloaded the AIO (all in one)
sebbo1 said:
Are you talking about slimroms.net? If you are, which addons do I download?
Click to expand...
Click to collapse
Yes, slimroms.net
It just depends on whether or not you want all of the Google apps typically in a regular gapps pkg, or a stripped down version. I use the AIO_Addons, or you could get the Aroma, so you can pick and choose. The Slim_gapps is a stripped down version.
Colonel Sanders said:
Yes, slimroms.net
It just depends on whether or not you want all of the Google apps typically in a regular gapps pkg, or a stripped down version. I use the AIO_Addons, or you could get the Aroma, so you can pick and choose. The Slim_gapps is a stripped down version.
Click to expand...
Click to collapse
One last question before I flash the rom. Is it loki'd? I don't see the answer on the website
sebbo1 said:
One last question before I flash the rom. Is it loki'd? I don't see the answer on the website
Click to expand...
Click to collapse
Last time I flashed a weekly, it wasn't loki'd, but that was a while back. I'm running test builds from black_jck, and build my own sometimes. I mentioned it to him that the weekly wasn't loki'd but that was a while back, so I can't speak for them now. The official builds are. If you're going to flash the weekly, flash loki_doki just to be safe.
Colonel Sanders said:
Last time I flashed a weekly, it wasn't loki'd, but that was a while back. I'm running test builds from black_jck, and build my own sometimes. I mentioned it to him that the weekly wasn't loki'd but that was a while back, so I can't speak for them now. The official builds are. If you're going to flash the weekly, flash loki_doki just to be safe.
Click to expand...
Click to collapse
Alright, so I flashed Slim and the AIO_addons, and rebooted the phone.
Once it was rebooting, the screen i mentioned earlier popped up, that said "Android is updating" and went through 109 files. When it was done, an error popped up quickly, saying that "Unfortunately..." and I couldn't read the rest before the phone rebooted. I let the screen hang for about 10 minutes, pulled the battery, cleared cache and dalvik, and rebooted again. No luck.
I think my best option now would be to return to stock, but I can't using my macbook. So my original question still stands.. How can I return to stock without using Odin and Heimdall?
sebbo1 said:
Alright, so I flashed Slim and the AIO_addons, and rebooted the phone.
Once it was rebooting, the screen i mentioned earlier popped up, that said "Android is updating" and went through 109 files. When it was done, an error popped up quickly, saying that "Unfortunately..." and I couldn't read the rest before the phone rebooted. I let the screen hang for about 10 minutes, pulled the battery, cleared cache and dalvik, and rebooted again. No luck.
I think my best option now would be to return to stock, but I can't using my macbook. So my original question still stands.. How can I return to stock without using Odin and Heimdall?
Click to expand...
Click to collapse
I would say so myself, Odin back to stock, but since you have a mac and I'm not sure if Heimdall support the S4 try this:
Factory Reset
Wipe Cache
Wipe Dalvik
Format /system
Format /data
Format /internal (If CWM-based recovery)
Flash ROM, addons, reboot
sebbo1 said:
Alright, so I flashed Slim and the AIO_addons, and rebooted the phone.
Once it was rebooting, the screen i mentioned earlier popped up, that said "Android is updating" and went through 109 files. When it was done, an error popped up quickly, saying that "Unfortunately..." and I couldn't read the rest before the phone rebooted. I let the screen hang for about 10 minutes, pulled the battery, cleared cache and dalvik, and rebooted again. No luck.
I think my best option now would be to return to stock, but I can't using my macbook. So my original question still stands.. How can I return to stock without using Odin and Heimdall?
Click to expand...
Click to collapse
I forgot to mention, the red LED light flashes every once in a while while on the Slim screen
sebbo1 said:
I forgot to mention, the red LED light flashes every once in a while while on the Slim screen
Click to expand...
Click to collapse
That means the battery is low... Charge it up some... Check your PM for my gmail if you need some help, posting back and forth can take a while.
Well thanks for all your help! Happy that my phone is working again without having to flash to stock.
Phone booted normally once I switched to SlimBean. Much snappier and responsive than LiquidSmooth. Fixed the problems I was having with WiFi also.
Still haven't figured out a way to flash to stock using OS X Lion since Heimdall doesn't work and Odin is Windows only... Mods please lock or close thread because I don't need help anymore
sebbo1 said:
Well thanks for all your help! Happy that my phone is working again without having to flash to stock.
Phone booted normally once I switched to SlimBean. Much snappier and responsive than LiquidSmooth. Fixed the problems I was having with WiFi also.
Still haven't figured out a way to flash to stock using OS X Lion since Heimdall doesn't work and Odin is Windows only... Mods please lock or close thread because I don't need help anymore
Click to expand...
Click to collapse
Glad you got it going man, and enjoy Slim, it's hands down the best ROM there is if you prefer minimal with tons of customization options.
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.
I am not new to ROMs and flashing etc., but I am completely stumped on this one. I have looked everywhere I know to look (supposedly) but if you find some easily locatable solution that I have missed, please feel free to call me mean names and share the solution with me. Otherwise, this is what I have tried so far (I will start from the beginning):
First, the 4.3 OTA update bricked my phone. I hadn't rooted my N4 yet because it was an updrage from D1 (yes, big jump). I decided to root the phone and install a custom ROM. Can't be too hard right? Its a Nexus for crying out loud. WRONG. Well I rooted pretty easily, and installed my first custom ROM for N4. To install this ROM, I had to erase boot.img, system.img, and userdata.img and then flash each individually from the ROM zip file I downloaded. This worked! I was winging it and it worked out. However, from then on, EVERY ROM I tried to install ended up in a bootloop. I have wiped cache/data, dalvik cache, and even my own (c)ache before flashing new ROM. They all end in bootloop (never ending).
I am able to revert to stock 4.2 easily every time. However, any attempt at installing a custom ROM from there is void. Today I downloaded 4.4.2.tgz from google and ran flash-all.bat. Everything works great! Until I try to boot up; bootloop. I fastboot format this and fastboot erase that, then fastboot flash each .img individually. I fastboot flash new radio, new kernel, etc. etc. but still bootloop.
I really am clueless as to what I am doing wrong or how I screwed myself somewhere along the way, but I am humbly coming before my superiors and asking for help. Please offer me the simplest solution and call me dumb for not seeing it, I will hold you in my heart 4eva
CausableMidget said:
I am not new to ROMs and flashing etc., but I am completely stumped on this one. I have looked everywhere I know to look (supposedly) but if you find some easily locatable solution that I have missed, please feel free to call me mean names and share the solution with me. Otherwise, this is what I have tried so far (I will start from the beginning):
First, the 4.3 OTA update bricked my phone. I hadn't rooted my N4 yet because it was an updrage from D1 (yes, big jump). I decided to root the phone and install a custom ROM. Can't be too hard right? Its a Nexus for crying out loud. WRONG. Well I rooted pretty easily, and installed my first custom ROM for N4. To install this ROM, I had to erase boot.img, system.img, and userdata.img and then flash each individually from the ROM zip file I downloaded. This worked! I was winging it and it worked out. However, from then on, EVERY ROM I tried to install ended up in a bootloop. I have wiped cache/data, dalvik cache, and even my own (c)ache before flashing new ROM. They all end in bootloop (never ending).
I am able to revert to stock 4.2 easily every time. However, any attempt at installing a custom ROM from there is void. Today I downloaded 4.4.2.tgz from google and ran flash-all.bat. Everything works great! Until I try to boot up; bootloop. I fastboot format this and fastboot erase that, then fastboot flash each .img individually. I fastboot flash new radio, new kernel, etc. etc. but still bootloop.
I really am clueless as to what I am doing wrong or how I screwed myself somewhere along the way, but I am humbly coming before my superiors and asking for help. Please offer me the simplest solution and call me dumb for not seeing it, I will hold you in my heart 4eva
Click to expand...
Click to collapse
This is why once I have my phone rooted, there's no turning back to stock.
Are you sure that you wiped system, along with everything else between adventures? (factory reset via recovery)
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
This is why once I have my phone rooted, there's no turning back to stock.
Are you sure that you wiped system, along with everything else between adventures? (factory reset via recovery)
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Yes. I even just did it again to make sure, but I am still watching the beautifully colored circles fold in on themselves.
CausableMidget said:
Yes. I even just did it again to make sure, but I am still watching the beautifully colored circles fold in on themselves.
Click to expand...
Click to collapse
Ok, gonna make a suggestion, and it's totally on you if you want to take it, and of course I won't be held responsible. I have had a bootloop or two on my G2 (the original), I would get impatient and pull the battery. (wish the Nexus 4 had a removable battery) Without fail, that cured the bootloop. Just remember, that was a G2, not a Nexus 4.
Don't ask me why it worked because I have no clue.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
Ok, gonna make a suggestion, and it's totally on you if you want to take it, and of course I won't be held responsible. I have had a bootloop or two on my G2 (the original), I would get impatient and pull the battery. (wish the Nexus 4 had a removable battery) Without fail, that cured the bootloop. Just remember, that was a G2, not a Nexus 4.
Don't ask me why it worked because I have no clue.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
I have cycled power a few times during the boot to no avail. I also just reverted back to stock 4.2 and then installed OTA 4.3 update hoping outcome would be different (definition of insanity according to Vaas). I don't know what to do. It's just not in me to run 4.2 forever
CausableMidget said:
I have cycled power a few times during the boot to no avail. I also just reverted back to stock 4.2 and then installed OTA 4.3 update hoping outcome would be different (definition of insanity according to Vaas). I don't know what to do. It's just not in me to run 4.2 forever
Click to expand...
Click to collapse
Have you tried calling an Exorcist?
I've run out of ideas!
Sent from my Nexus 7 (2013)
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.