Related
So I installed several versions of Jelly Bean. I tried TeamBAMF Leaked ROM, Jelly Belly Leaked, and Vicious Toro (Source). All of them soft brick my phone after a day or two. It will just boot loop constantly. New ROM and Wipe make no difference. A Restore doesnt work because it gives an error when restoring Data. Always happens after a reboot or powering on the device. For me to fix this, I must use ADB to push the stock google image to the phone. This is tiring as it happened 3 times. I love JB and the features but I can't deal with this soft brick. Anyone else having an issue? I tried turning off SetCPU as well and using the Kernels that come with the ROMs. I would really like to install JB. I am and have been using AOKP M5 with absolutely no issues.
I am ready to get a new phone through Asurion. This is a launch Verizon Nexus.
EDIT: Missed the fact that this is a Verizon Nexus so removing this comment.
asawoszc said:
Have you tried a stock version of Jelly Bean from the files on XDA? Sorry but it just sounds like you've tried custom ROM's. My other suggestion would be to put on 4.0.4 takju from Google's site and see if you get the Jelly Bean OTA update and if it resolves the issues in the short term. If it does then it must be the process you're going thru to put on the ROM's..... might be missing something simple like Dalvik cache wipe, etc. Just speaking in very general terms.
Click to expand...
Click to collapse
no, he shouldnt do any of what you said. he is on a VERIZON nexus. not a GSM. if he flashed takju there could be serious problems.
Apologies... I missed the last line. Will edit out my comment.
lacesout said:
So I installed several versions of Jelly Bean. I tried TeamBAMF Leaked ROM, Jelly Belly Leaked, and Vicious Toro (Source). All of them soft brick my phone after a day or two. It will just boot loop constantly. New ROM and Wipe make no difference. A Restore doesnt work because it gives an error when restoring Data. Always happens after a reboot or powering on the device. For me to fix this, I must use ADB to push the stock google image to the phone. This is tiring as it happened 3 times. I love JB and the features but I can't deal with this soft brick. Anyone else having an issue? I tried turning off SetCPU as well and using the Kernels that come with the ROMs. I would really like to install JB. I am and have been using AOKP M5 with absolutely no issues.
I am ready to get a new phone through Asurion. This is a launch Verizon Nexus.
Click to expand...
Click to collapse
try do and this if you are comfortable doing it.. note you will lose all data including in your /sdcard/
fastboot erase system
fastboot erase userdata
fastboot erase cache
flash the factory mysid images, then install CWM (not the touch one) or TWRP and flash this rom: http://forum.xda-developers.com/showthread.php?t=1744389
Zepius said:
try do and this if you are comfortable doing it.. note you will lose all data including in your /sdcard/
fastboot erase system
fastboot erase userdata
fastboot erase cache
flash the factory mysid images, then install CWM (not the touch one) or TWRP and flash this rom: http://forum.xda-developers.com/showthread.php?t=1744389
Click to expand...
Click to collapse
Thanks Zepius but I already did this. It's the only way for me to recover. My phone is fine now on AOKP M5 but I want to use Jelly Bean. Is there any reason JB would cause boot loops after 24 hours? It's just a pain in the ass because I can't simply recover through CWM. I need a PC. The first time this happened I had to back up my SDCARD from ADB. This took forever!!
BTW, I know how to Root, ROM, etc. I always do everything twice. Wipe Data/Dalvik/Cache and install the ROM twice.
just curious... which version of CWM are you using?
Oh man I have the same issue I just get stuck at the Google screen or the jb splash screen on my cdma nexus I tried everything and wiped every last thing on my phone I just gave up and said ile wait for the official update I guess. Anyway I hope this thread shed some light on the situation we having
Sent from my Galaxy Nexus using xda app-developers app
Use the superwipe from the android HD thread, flash the rom, everytime it boots let it sit at the google logo IT IS NOT FROZEN. It just takes a while sometimes.
What are you doing that's causing a soft-brick after 24 hours? I mean, the phone is just sitting on a table and BOOM - it freezes and it's soft-bricked?? Maybe give us the scenario that happens when it's soft-bricked. We need more concrete details. It could be something you're doing wrong.
Zepius said:
just curious... which version of CWM are you using?
Click to expand...
Click to collapse
I was using the latest (forgot which version) and I also tried CWM touch between the first two bricks. Same issue.
XfrostX said:
Use the superwipe from the android HD thread, flash the rom, everytime it boots let it sit at the google logo IT IS NOT FROZEN. It just takes a while sometimes.
Click to expand...
Click to collapse
Nope, it keeps boot looping. I had it sitting for over 30 min. It starts with Google then JB splash. Then boot loops and continues. Even when I wipe and install AOKP it still boot loops. I need to use Fastboot to wipe and flash stock image.
akira02rex said:
What are you doing that's causing a soft-brick after 24 hours? I mean, the phone is just sitting on a table and BOOM - it freezes and it's soft-bricked?? Maybe give us the scenario that happens when it's soft-bricked. We need more concrete details. It could be something you're doing wrong.
Click to expand...
Click to collapse
It happens as soon as I reboot or power off the phone. For instance, Saturday I went shark fishing so I powered down the phone to save battery. Power it up several hours later and it boot looped for 20 min.
I am using a AOKP restore I recovered through ADB. Once I flashed stock image, rooted, installed CWM, the restore worked perfectly.
lacesout said:
I was using the latest (forgot which version) and I also tried CWM touch between the first two bricks. Same issue.
Nope, it keeps boot looping. I had it sitting for over 30 min. It starts with Google then JB splash. Then boot loops and continues. Even when I wipe and install AOKP it still boot loops. I need to use Fastboot to wipe and flash stock image.
It happens as soon as I reboot or power off the phone. For instance, Saturday I went shark fishing so I powered down the phone to save battery. Power it up several hours later and it boot looped for 20 min.
I am using a AOKP restore I recovered through ADB. Once I flashed stock image, rooted, installed CWM, the restore worked perfectly.
Click to expand...
Click to collapse
Is it getting wet??
akira02rex said:
Is it getting wet??
Click to expand...
Click to collapse
Lol nope. The shark fishing trip was the third boot loop for me.
Same boat here... I can flash any ics and restore any backup... but some how every time I flash jb rom it just stay in nexus logo or in any kernel logo.. the first time the vicious jb rom out I manage to flash and boot well ..then after a few days tried different jb rom then boom! Infinite boot loop.. then since then I can't flash jb rom. Tried all kind of kernel and rom combo and also used all kinds of cwm..
Sent from my Galaxy Nexus using XDA Premium App
landrian18 said:
Same boat here... I can flash any ics and restore any backup... but some how every time I flash jb rom it just stay in nexus logo or in any kernel logo.. the first time the vicious jb rom out I manage to flash and boot well ..then after a few days tried different jb rom then boom! Infinite boot loop.. then since then I can't flash jb rom. Tried all kind of kernel and rom combo and also used all kinds of cwm..
Sent from my Galaxy Nexus using XDA Premium App
Click to expand...
Click to collapse
Interesting that you got it to work once, because I have the same issue you do but have never gotten it to boot past the Google animation. Wonder if there was a Rom that we flashed that caused the issue to begin with. I have tried so many JB roms now that I don't know which one I started with, but I think it was Vicous JB since that was the first one I saw released at the time. Just wish someone out there that has had our symptoms and finally got past them could tell us what they did.
Well at least I'm not the only having this issue. Hopefully someone can shed some light.
@nothingshocking
Its the [email protected]_jelly jb rom that I flash when this things all starts.. the vicious rom works for me since v1 to v3.. I'm trying other rom because of grs issue in vicious at that time. I'm not afraid to flash or be in softbrick because I know I can always use my backup and restore or there's toolkit just in case ,but this thing I'm really puzzled this is so weird.. I can flash any ics rom but not the jb rom.. someone suggest me to use jb bootloader and I did and same results.. I'm really hoping that someone of our bright dev can look in to this and help us..
Sent from my Galaxy Nexus using XDA Premium App
Same exact problem here. I would boot loop anytime I rebooted or powered down my phone. Today, I flashed the new clockwork recovery (v.6.0.0.?). So of course I rebooted my phone to see what it looked like. Well it looked cool but when I went to reboot my phone it was just stuck on the google screen. Wouldn't boot at all. Tried wiping data/cache/dalvik cache/format system/format cache/fix permission. Got desperate cuz nothing worked. Backups wouldn't restore. Got "installation aborted error". Finally did like the op and flashed stock image. Works fine now. Just seems like my phone doesn't like the JB at all. Has done this on every JB I flashed.
Sent from my Galaxy Nexus using xda premium
had this happen on my cdma toroplus any ics rom will install and work fine but no jelly bean rom will boot past the bootanimation
Maybe it has to do with hardware version? For those of you with problems like me, are you on a launch Nexus? That is what I have.
My SKU is SCHI515MSV
I am not sure if they redesigned the hardware at some time.
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Did you wipe data and cache when you flashed the new rom?
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
cobraboy85 said:
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
Click to expand...
Click to collapse
thanks for the info, will try this all out soon. I've been flashing roms for years now and have never run into anything like this, and as previously stated, this didn't occur solely with your rom which has me thinking something has happened to the phone itself. will get back to you soon and once again thank you
chucktdriscoll said:
Did you wipe data and cache when you flashed the new rom?
Click to expand...
Click to collapse
of course, wiped data, cache, & delvik
nyyankees1237 said:
of course, wiped data, cache, & delvik
Click to expand...
Click to collapse
my point is...
coming from a cm based ROM, or aokp, whatever you said... you would want to format system as well.
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
I was having some of the same issues. I downloaded XquiziT's Superwipe and ran it by installing from external sd card. I ran it three times to clear everything out, then I wiped data, cache and the rest three times.
No probs for me after that.
Will definitely give that a try as well! Thank you! Will post my results when the holiday is over.
Happy thanksgiving
Sent from my SGH-T999 using xda app-developers app
Hi i've come here many times before for any hiccups that came up for me with my phone but this time I believe I need help. I'll start it off with me earlier this week I was running CyanogenMod 10.1 and felt like I wanted to change it up leading me to isntall synergy onto my S3 (completed two nights ago). Today I decided it just wasnt doing it for me. Picked a new ROM ( Paranoid ).
This is where the problem comes in, I started the usual to flash a new ROM, put it into recovery and then started the factory/data reset. it froze waited half an hour for it to complete but it did'nt. Rebooted it into recovery as now I cant boot back into the software anyways. tried the same thing but wiped the cache and dalvik cache first. same thing happened froze on the factory reset. At this time I decided to reset it completley and get rid of the root, flashing the stock firmware. Odin also froze everytime, I cant even reinstall the stock firmware after failing everytime around the Nand area. I found this thread (http://forum.xda-developers.com/showthread.php?t=1840030) with I think a similar problem im really not sure as I cant do anything but the thing is, is that its for Verizon Galaxy S3 ( im on Rogers Canada). I'm sure I can fix this somehow as I can put it into download mode still but any help from the community would be greatly appreciated.
How far does Odin get during the stock ROM flash, before it freezes up on you?
I would try to Odin a stock recovery. Not the ROM & everything, just the recovery. Then go into the stock recovery and wipe everything.
Then Odin the stock ROM. Maybe try an ICS one if you were failing on the JB one.
CZ Eddie said:
How far does Odin get during the stock ROM flash, before it freezes up on you?
I would try to Odin a stock recovery. Not the ROM & everything, just the recovery. Then go into the stock recovery and wipe everything.
Then Odin the stock ROM. Maybe try an ICS one if you were failing on the JB one.
Click to expand...
Click to collapse
It says Nand write start, and then complete (write) operation failed. On the phone in download mode it says Secure check Fail : aboot . CMW works for me still ? is that what you mean ? if so the data/factory reset freezes. I do have a RecoveryGalaxyS3USCanada.tar file in my Root folder, if I should flash that.... but its been so long I forget what its for. Thank you for the feedback ive been searching all day and wasnt able to find anything useful so far. Right now im downloading older stock firmwares to attempt to flash them, hopefully they pan out.
The utility in this thread offers an option to flash the stock recovery. I'd try it out and see what happens!
http://forum.xda-developers.com/showthread.php?t=1746665
Flash stock recovery and then boot to the stock recovery and restore to defaults. Then flash a stock ROM.
Stock recovery = Samsung recovery, not TWRP or Clockwork.
I had 2 soft bricks with cm this week. Had to Odin back to rooted stock for one. The other back to rooted stock and had to factory reset with Samsun 3e recovery before the phone would boot.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Okay i've installed everything (drivers, toolkit, deleted Kies) and now when im going in to flash the stock recovery it says its waiting for USB debugging, which I can't re-anable since im stuck in a boot loop. Am I screwed here ?
French1747 said:
Okay i've installed everything (drivers, toolkit, deleted Kies) and now when im going in to flash the stock recovery it says its waiting for USB debugging, which I can't re-anable since im stuck in a boot loop. Am I screwed here ?
Click to expand...
Click to collapse
can you still access recovery? i'm assuming it's twrp or cwm
if so, here's cwm flashable stock firmware from upndwn4par. flash it, boot in, turn on debugging.
http://d-h.st/8OQ
xBeerdroiDx said:
can you still access recovery? i'm assuming it's twrp or cwm
if so, here's cwm flashable stock firmware from upndwn4par. flash it, boot in, turn on debugging.
]
Click to expand...
Click to collapse
Thank you so much! I doubted it at first just because of the other roms and stock ones also never worked but this one has it up and running smoothy. I want to play it safe just so I dont screw up again so I'm gonna ask you guys one more thing.. Would it be safe to try and flash the Paranoid ROM now? ( I dont believe it was the problem earlier since I never actually got to installing it). The problem was something around the lines of not being able to write things onto the device. ex Data/Factory reset freezing everytime on CMW, while Odin also failed everytime it made to the step of flashing/writing in the stock ROM.
Thanks everyone, your're all very helpful !
If it were me, I'd Odin a stock/rooted JellyBean ROM first. Just to get to get all the correct files & structure on there. THEN I would flash whatever you want.
First, sorrt to speak french, but thatnll be more easy for me to tell it.
A partir du moment ou tu peux passer en mode download, tout va bien ^_^
Il m'est deja arrive sur mon teos de corrompre ma partition systeme et de repartir comme si de rien n'etait avec un flash.
Reflashe avec odin et reessaie
Sent with my AiKi and optimus rom
CZ Eddie said:
If it were me, I'd Odin a stock/rooted JellyBean ROM first. Just to get to get all the correct files & structure on there. THEN I would flash whatever you want.
Click to expand...
Click to collapse
French1747 said:
Thank you so much! I doubted it at first just because of the other roms and stock ones also never worked but this one has it up and running smoothy. I want to play it safe just so I dont screw up again so I'm gonna ask you guys one more thing.. Would it be safe to try and flash the Paranoid ROM now? ( I dont believe it was the problem earlier since I never actually got to installing it). The problem was something around the lines of not being able to write things onto the device. ex Data/Factory reset freezing everytime on CMW, while Odin also failed everytime it made to the step of flashing/writing in the stock ROM.
Thanks everyone, your're all very helpful !
Click to expand...
Click to collapse
i agree with coming from stock firmware when flashing. i would also make sure my cwm was up-to-date while i was at it. i would also boot into recovery and make a nandroid now so you'll have one. with that being said, here ya go:
http://forum.xda-developers.com/showthread.php?t=2179330
in the above link:
step 1: take the time to backup your imei if you havent already
step 2: this is stock with root already injected
step 3: if you dont have rom manager, download it and update your recovery if you're not running 6.0.2.3 or higher
step 4 & 5 are self explanatory
cheers
xBeerdroiDx said:
i agree with coming from stock firmware when flashing. i would also make sure my cwm was up-to-date while i was at it. i would also boot into recovery and make a nandroid now so you'll have one. with that being said, here ya go:
http://forum.xda-developers.com/showthread.php?t=2179330
in the above link:
step 1: take the time to backup your imei if you havent already
step 2: this is stock with root already injected
step 3: if you dont have rom manager, download it and update your recovery if you're not running 6.0.2.3 or higher
step 4 & 5 are self explanatory
cheers
Click to expand...
Click to collapse
The only thing so far (that I have noticed) is that the data/factory reset still does not work, I'm going to continue like you said earlier and flash stock recovery and my own stock firmware for Rogers now that I have turned debugging mode on. my cmw currently is 6.+ and my previous Nandroid backups would also get stuck when I tried to restore to them, I'm assuming that since I still can't factory reset that I wont be able to restore back to them but I will see. Should I make another nandroid even when its still in a semi-messed up state ?
Right now I seriously just want to get rid of the stupid data reset problem.
French1747 said:
The only thing so far (that I have noticed) is that the data/factory reset still does not work, I'm going to continue like you said earlier and flash stock recovery and my own stock firmware for Rogers now that I have turned debugging mode on. my cmw currently is 6.+ and my previous Nandroid backups would also get stuck when I tried to restore to them, I'm assuming that since I still can't factory reset that I wont be able to restore back to them but I will see. Should I make another nandroid even when its still in a semi-messed up state ?
Right now I seriously just want to go back to step one of everything, unrooted stock fimrware with access to Gapps and continue from there. Most of all get rid of the stupid data reset problem.
Click to expand...
Click to collapse
where are you saying the data/factory reset isnt working? cwm or in android settings?
i would download rom manager and update cwm to latest (6.0.3.0), boot into cwm recovery and try making a nandroid.
and i dont think you're as messed up as you think you are right now. you're rooted, with stock firmware and a custom recovery.
when i was ready, i would update recovery, in recovery make a backup, (still in recovery) wipe data/factory reset, wipe cache/dalvik, flash rom
xBeerdroiDx said:
where are you saying the data/factory reset isnt working? cwm or in android settings?
i would download rom manager and update cwm to latest (6.0.3.0), boot into cwm recovery and try making a nandroid.
and i dont think you're as messed up as you think you are right now. you're rooted, with stock firmware and a custom recovery.
when i was ready, i would update recovery, in recovery make a backup, (still in recovery) wipe data/factory reset, wipe cache/dalvik, flash rom
Click to expand...
Click to collapse
Google apps arent showing up for me either, Tried installing them and they did succesfully but i still dont see them. anyways I'm on a slightly lower version of cmw then 6.0.3.0 , can I flash the new version over the current one im on, since I cant install through the play store ?
French1747 said:
Google apps arent showing up for me either, Tried installing them and they did succesfully but i still dont see them. anyways I'm on a slightly lower version of cmw then 6.0.3.0 , can I flash the new version over the current one im on, since I cant install through the play store ?
Click to expand...
Click to collapse
boot into cwm and flash gapps again. flash twice to be sure. reboot. lemme know
I believe everything is working perfectly now, installed Rom manager from the web and updated cmw. Once more tried to data wipe from cmw and it froze again this time crashing by itself, I then went back into it went and formatted my data and then tried the wipe data, this time it worked for me and I proceeded to wipe the cach and dalvik, installed paranoid and everthing is working fine, ill post an update if i notice anything else happens but so far it looks perfect. Thank you so aton, I appreciate it guys especially you "Beer". Now I can relax on my birthday and stop tinkering around on my phone haha.
( Not sure why Gapps wer'nt working earlie,r but i'm done )
Same problem here
The same thing happened to me while trying to Odin to ATT stock rom. Flash stopped half way and Odin showed failed. Tried to reboot into download mode to repeat procedure and would not go into download mode. Phone will reboot but into android recovery mode. When I try to run an update from sd card I get a "file verification error" and the process aborts. I'm going to try this process to see if I have any better results.
So I have a ~week old Tab which I havn't used, I played around with it last night and flashed CWM using Odin and that worked fine. I went and flashed the rooted stock firmware, and it seemed to have flashed fine, except now the tablet is in a reboot loop, it restarts about 3 times and then automatically boots into recovery. I've flashed all the ROMs I can find for the 10.1" and it happens with all of them, last resort is flashing stock recovery then taking it back to the place I bought it from and to play dumb, but I'd rather not. Anyone got any suggestions?
TL;DR Tablet stuck in reboot loop, won't boot ROM, recovery & download mode work fine.
You might have done it, but have you tried flashing back the stock firmware ?
try it and post back please
Agree, I had the same issues with a few of the custom roms. I went back to stock rom and have had no issues. My issue was flashing from a SD card. For some reason it would not work. I put the rom on the device in the download folder and flashed from there. Most roms did flash correctly but I found them to be of little use. Did you by chance do a backup before you started playing around with other roms? Hope so. Then at least you can recover back to factory condition.
Nitro_123 said:
You might have done it, but have you tried flashing back the stock firmware ?
try it and post back please
Click to expand...
Click to collapse
I have, I tried reinstalling my backup, as well as both of the stock roms here, although both times I didn't have a microsd card available, so I sideloaded both of the ROMs (which apparently worked fine, verified etc). I've just gone and bought one, so when I get home tonight I'm going to have another play around and see if I can get something working.
Brian D said:
Agree, I had the same issues with a few of the custom roms. I went back to stock rom and have had no issues. My issue was flashing from a SD card. For some reason it would not work. I put the rom on the device in the download folder and flashed from there. Most roms did flash correctly but I found them to be of little use. Did you by chance do a backup before you started playing around with other roms? Hope so. Then at least you can recover back to factory condition.
Click to expand...
Click to collapse
Interesting, I haven't tried that, I shall, thanks
I might also try flashing the ROM through Odin instead of a recovery.
I do believe that stock roms MUST be uploaded via ODIN. They cannot reside on the device. The stock rom is around 1.9gb (XAR-P5210UEUAMK1). So you will use that file (or whatever stock rom you wish to use). If you are loading one of the other roms developed here then you can put it on the device and load from there (via the recovery app CWM or TWRP)
Brian D said:
I do believe that stock roms MUST be uploaded via ODIN. They cannot reside on the device. The stock rom is around 1.9gb (XAR-P5210UEUAMK1). So you will use that file (or whatever stock rom you wish to use). If you are loading one of the other roms developed here then you can put it on the device and load from there (via the recovery app CWM or TWRP)
Click to expand...
Click to collapse
Oh, damn, really? That would explain quite a lot then, thanks, hopefully I'll be home in a couple hours and can report back
My bad I didn't make myself clear. Yes I meant flashing back a stock ROM via ODIN as that is the best way to restore it to stock. Thanks to @Brian D for pointing that out
Nitro_123 said:
My bad I didn't make myself clear. Yes I meant flashing back a stock ROM via ODIN as that is the best way to restore it to stock. Thanks to @Brian D for pointing that out
Click to expand...
Click to collapse
Haha thanks, I'm downloading a stock rom now, hopefully I'll be able to report back in about 30
Holy ****, thanks guys! Managed to get the stock ROM flashed with Odin, silly me for the not realising. Anyone know what would have caused the boot loop? I really don't want to run the stock rom with all the samsung crap (I guess I can root and remove everything)
I think what you did was called a dirty flash. You had bits and pieces of the original rom on the device when you tried to load another rom. The two mixed like vinegar and oil. You have to wipe your system clean before you can load a new flash. Before proceeding please do a backup of what you have right now. Load either CWM or TWRP and do the backup. My preference is TWRP. I like the look and feel of how it works.
I found the best instruction set to be http://forum.xda-developers.com/showpost.php?p=49715684&postcount=172. I had the same boot loop as you but when I followed these instructions I finally loaded the rom. But like I said, to me I gained nothing by using it. But this is me. After much reading I found that if I just delete bloatware then I should be ok. I used an app called bloatfree from the play store. Worked just great but one has to be careful about what one removes. That is why I always backup before doing anything. I must have had 20 backup files at one time. LOL
Good luck!
I have a SPH-L710 with a stock ROM and CWM root, I just tried to flash a boot animation and am now stuck in a boot loop. I did not make a backup before I tried this. I have wiped cache,div and did fact reset and can not get out of boot loop...................PLEASE HELP
Runing KK 4.4.2 on VIRGIN MOBILE/SPRINT NETWORK
aanddink said:
I have a SPH-L710 with a stock ROM and CWM root, I just tried to flash a boot animation and am now stuck in a boot loop. I did not make a backup before I tried this. I have wiped cache,div and did fact reset and can not get out of boot loop...................PLEASE HELP
Runing KK 4.4.2 on VIRGIN MOBILE/SPRINT NETWORK
Click to expand...
Click to collapse
You most likely will have to flash a stock rom using Odin on the computer.
The only problem with that is if you had to get your phone flashed to Virgin Mobile like I did with PagePlus, it may or may not erase those critical settings. I could never get a clear answer on that, but it is best to play it safe and assume it will. However, your phone should be functioning once again.You will however have to re-root the phone, and might as well install TWRP. All of this can be done through Odin.
Alternatively, if you have a custom recovery installed and a rom or two on your sdcard, you could try to flash the rom instead of going all the way back to stock. That would help ensure your carrier settings arent wiped related to Virgin, as it could if you were to flash back to stock.
Then for the love of god, devil, or whoever you believe in... make a backup once you are fixed and back up and running!! They are perfect and extremely helpful for situations like this.
Rawb0Ss said:
You most likely will have to flash a stock rom using Odin on the computer.
The only problem with that is if you had to get your phone flashed to Virgin Mobile like I did with PagePlus, it may or may not erase those critical settings. I could never get a clear answer on that, but it is best to play it safe and assume it will. However, your phone should be functioning once
again.You will however have to re-root the phone, and might as well install TWRP. All of this can be done through Odin.
Alternatively, if you have a custom recovery installed and a rom or two on your sdcard, you could try to flash the rom instead of going all the way back to stock. That would help ensure your carrier settings arent wiped related to Virgin, as it could if you were to flash back to stock.
Then for the love of god, devil, or whoever you believe in... make a backup once you are fixed and back up and running!! They are perfect and extremely helpful for situations like this.
Click to expand...
Click to collapse
Thank you for the reply and thank you for the help. i did get it to un-bootloop, i unfortunately did not have a rom backup, now i have a full backup zip using CMW on my sd card which i hope would fix this in the future. nothin worked until i found a good boot animation, i should have look for more firat but.once i re-flashed the 3rd one it booted.
aanddink said:
Thank you for the reply and thank you for the help. i did get it to un-bootloop, i unfortunately did not have a rom backup, now i have a full backup zip using CMW on my sd card which i hope would fix this in the future. nothin worked until i found a good boot animation, i should have look for more firat but.once i re-flashed the 3rd one it booted.
Click to expand...
Click to collapse
You have to have the proper boot animation binaries before you go flashing boot animation. Those zips are for flashing in custom roms that already have the proper binaries.