Related
EDIT: I believe I have figured out a part of the problem or all of it, but need some help. In twrp, my good gnex doesn't say "E: unable to mount '/efs' (tw_mount)" while my other phone does multiple times when flashing things. I am having some trouble finding out what this means, but hoping someone can help me figure out what it means and why it is happening so I can solve the problem.
Okay, so I recently got a verizon galaxy nexus, after having had a htc g1, samsung intercept, droid 2 global, htc thunderbolt, and samsung stratosphere. I am not new to rooting and romming and such and have never had any major issues with such things. However the galaxy nexus I got has been giving me a very hard time. I have tried restoring to stock, reunlocking, rooting, and such, and then trying to install roms with twrp and/or cwm recovery. neither one seems to work right on this phone. I tried codename android 3.3.0, bamfed paradigm 2.2, and some other roms. They all get stuck at the boot animation and just stay there, even waiting 5-10 mins does nothing.
The strange thing is that I ordered a 2nd galaxy nexus and so now I have 2, and the 2nd one I just got, and tried to install codename android and it went flawlessly. I unlocked the bootloader, rooted, flashed twrp, backed up, cleared the phone out, and then flashed the JB bootloader, imyoseon's lean kernel, codename android, and cna's gapps package. Doing them all at once, then wiped cache & dalvik after and rebooted. All went perfectly.
Did the same on the first gnex, and it is still on the boot animation. It seems to refuse to boot. I just don't get it. This phone has rejected every rom I give it except for cm9 rc2 and the version of aokp that it originally came with. I literally followed the exact same steps as the other gnex, and not seeing the same results. I don't see how it is possible for a phone to reject random roms like this since it does work in general.
The only difference between the two phones is that one is hardware version 9 and the other is version 10. That and the problem one was running cm9 and had the jb bootloader on it prior to my reflashing the jb bootloader and then the same kernel, rom, and gapps. I would not expect the bootloader to be able to affect anything though, and they had the same one flashed, and system and everything else got wiped, so I don't think being on a custom rom should be affecting this either.
So does anyone have any ideas?
I am having the exact same problem as you are with hardware version 9. I believe it has something to do with the efs partition as well.
ben7337 said:
EDIT: I believe I have figured out a part of the problem or all of it, but need some help. In twrp, my good gnex doesn't say "E: unable to mount '/efs' (tw_mount)" while my other phone does multiple times when flashing things. I am having some trouble finding out what this means, but hoping someone can help me figure out what it means and why it is happening so I can solve the problem.
Okay, so I recently got a verizon galaxy nexus, after having had a htc g1, samsung intercept, droid 2 global, htc thunderbolt, and samsung stratosphere. I am not new to rooting and romming and such and have never had any major issues with such things. However the galaxy nexus I got has been giving me a very hard time. I have tried restoring to stock, reunlocking, rooting, and such, and then trying to install roms with twrp and/or cwm recovery. neither one seems to work right on this phone. I tried codename android 3.3.0, bamfed paradigm 2.2, and some other roms. They all get stuck at the boot animation and just stay there, even waiting 5-10 mins does nothing.
The strange thing is that I ordered a 2nd galaxy nexus and so now I have 2, and the 2nd one I just got, and tried to install codename android and it went flawlessly. I unlocked the bootloader, rooted, flashed twrp, backed up, cleared the phone out, and then flashed the JB bootloader, imyoseon's lean kernel, codename android, and cna's gapps package. Doing them all at once, then wiped cache & dalvik after and rebooted. All went perfectly.
Did the same on the first gnex, and it is still on the boot animation. It seems to refuse to boot. I just don't get it. This phone has rejected every rom I give it except for cm9 rc2 and the version of aokp that it originally came with. I literally followed the exact same steps as the other gnex, and not seeing the same results. I don't see how it is possible for a phone to reject random roms like this since it does work in general.
The only difference between the two phones is that one is hardware version 9 and the other is version 10. That and the problem one was running cm9 and had the jb bootloader on it prior to my reflashing the jb bootloader and then the same kernel, rom, and gapps. I would not expect the bootloader to be able to affect anything though, and they had the same one flashed, and system and everything else got wiped, so I don't think being on a custom rom should be affecting this either.
So does anyone have any ideas?
Click to expand...
Click to collapse
Have you tried flashing stock JB to the hw version 9 one? Handy guide here: http://forum.xda-developers.com/showthread.php?t=1626895
ben7337 said:
EDIT: I believe I have figured out a part of the problem or all of it, but need some help. In twrp, my good gnex doesn't say "E: unable to mount '/efs' (tw_mount)" while my other phone does multiple times when flashing things. I am having some trouble finding out what this means, but hoping someone can help me figure out what it means and why it is happening so I can solve the problem.
Okay, so I recently got a verizon galaxy nexus, after having had a htc g1, samsung intercept, droid 2 global, htc thunderbolt, and samsung stratosphere. I am not new to rooting and romming and such and have never had any major issues with such things. However the galaxy nexus I got has been giving me a very hard time. I have tried restoring to stock, reunlocking, rooting, and such, and then trying to install roms with twrp and/or cwm recovery. neither one seems to work right on this phone. I tried codename android 3.3.0, bamfed paradigm 2.2, and some other roms. They all get stuck at the boot animation and just stay there, even waiting 5-10 mins does nothing.
The strange thing is that I ordered a 2nd galaxy nexus and so now I have 2, and the 2nd one I just got, and tried to install codename android and it went flawlessly. I unlocked the bootloader, rooted, flashed twrp, backed up, cleared the phone out, and then flashed the JB bootloader, imyoseon's lean kernel, codename android, and cna's gapps package. Doing them all at once, then wiped cache & dalvik after and rebooted. All went perfectly.
Did the same on the first gnex, and it is still on the boot animation. It seems to refuse to boot. I just don't get it. This phone has rejected every rom I give it except for cm9 rc2 and the version of aokp that it originally came with. I literally followed the exact same steps as the other gnex, and not seeing the same results. I don't see how it is possible for a phone to reject random roms like this since it does work in general.
The only difference between the two phones is that one is hardware version 9 and the other is version 10. That and the problem one was running cm9 and had the jb bootloader on it prior to my reflashing the jb bootloader and then the same kernel, rom, and gapps. I would not expect the bootloader to be able to affect anything though, and they had the same one flashed, and system and everything else got wiped, so I don't think being on a custom rom should be affecting this either.
So does anyone have any ideas?
Click to expand...
Click to collapse
Looks like you created swap and other strange partitions with a recovery, so "sdcard" hyerarchy got corrupted
try to lock and unlock device
in your adb folder type those commands
fastboot oem lock
then
fastboot oem unlock
My wife and I have the same phone, Verizon GNex. However, our phones are completely different! I'm currently on AOKP build 4. She was on Build AOKP ICS 40. I attempted to flash build 4 and gapps after a full wipe, etc, but I never could get it to flash properly. The first time I flashed it, it allowed to try to sign her into her account. She had google 2 step on and I wasn't able to get her loaded. The second phone on file for 2 step was her own, so when the text came I couldn't get to it (for whatever reason the soft keys were missing and I couldn't get out once I was stuck in the 2 step process.) I then pulled the battery to reboot. It was stuck in a boot loop that I couldn't get out. When I tried to flash back to the backup file from build 40 it was missing, as was all the other backup files. I didn't have a copy to flash to and the rom was stuck in boot loop. I couldn't use fastboot because it was saying "fastboot read error 2147483647" I decided to odin 4.02 stock software. It worked great to get me out of the loop and get the phone up and going again. Since that point I updated the stock software, rerooted ,and reinstalled CWR. However, no matter how I try to flash any build of AOKP now it fails. I even pulled the files from my phone that I had flashed just days before and put them on my wife's phone. Nope. Didn't work. I tried TWRP and I couldn't get it to work either. What other options should I take to get the rom on my wife's phone. She's about to kill me already for "messing" it up.
Redownload the ROM, make sure she doesn't have toroplus and you're trying to flash a toro ROM or something like that, make sure if she has a toro GalNex she also has a toro recovery, try flashing the latest 4.1.1 radios....
Toro is Verizon GalNex, toroplus is Sprint.
Sent from my Galaxy Nexus using xda app-developers app
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I tried something different. One phone good. One phone JACKED!
I tried a clean download via a wired connection. Same result, FAIL! Instead I used the odin files I found to flash the toro (VZW). After which I rerooted the device and downloaded CM10 nightly and flashed without ANY problems.
My phone (AOKP toro JB build 4) ran completely out of battery charge that it powered off. The ironic thing is, after charging completely in the off state I started it back up...(same) BOOT LOOP! I've searched a little bit on the forums, but I can't seem to find the exact way to undo this. This is the same boot loop I had with my wife's phone. I tried to flash my most recent JB 4 backup and it gets an error after the system restore and just before the data restore. I tried all the other backups of many different builds with CWM and had the same result. I tried flashing the AOKP JB 4 but it just ends up in the boot loop again.
I can't push any new files to it for whatever reason so I can't try to flash the radios or bootloader. Honestly, I can't even read the internal memory where everything is stored. I think it's because the debuging mode isn't turned on since I tried to reflash a new build and restore my backup. " I love AOKP, but I'm going to hold off until a new milestone build comes out. At this point I just want the pictures/videos from my phone. I have a backup on my computer saved, but none of the pictures/videos are saved.
:crying:
-Chlorine
jimmyco2008 said:
Redownload the ROM, make sure she doesn't have toroplus and you're trying to flash a toro ROM or something like that, make sure if she has a toro GalNex she also has a toro recovery, try flashing the latest 4.1.1 radios....
Toro is Verizon GalNex, toroplus is Sprint.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Chlorine tablet said:
I tried a clean download via a wired connection. Same result, FAIL! Instead I used the odin files I found to flash the toro (VZW). After which I rerooted the device and downloaded CM10 nightly and flashed without ANY problems.
My phone (AOKP toro JB build 4) ran completely out of battery charge that it powered off. The ironic thing is, after charging completely in the off state I started it back up...(same) BOOT LOOP! I've searched a little bit on the forums, but I can't seem to find the exact way to undo this. This is the same boot loop I had with my wife's phone. I tried to flash my most recent JB 4 backup and it gets an error after the system restore and just before the data restore. I tried all the other backups of many different builds with CWM and had the same result. I tried flashing the AOKP JB 4 but it just ends up in the boot loop again.
I can't push any new files to it for whatever reason so I can't try to flash the radios or bootloader. Honestly, I can't even read the internal memory where everything is stored. I think it's because the debuging mode isn't turned on since I tried to reflash a new build and restore my backup. " I love AOKP, but I'm going to hold off until a new milestone build comes out. At this point I just want the pictures/videos from my phone. I have a backup on my computer saved, but none of the pictures/videos are saved.
:crying:
-Chlorine
Click to expand...
Click to collapse
Code:
fastboot boot cwm_or_twrp.img
when in recovery:
Code:
adb pull /sdcard/
note: if no folder is really pulled, change /sdcard/ to /data/media
Some tips for the two step verification that I have found out. Although it says not to use a Google voice account it is by far the Best method for dong two step. For me I always have some other device logged into Google Voice and I use that device to get the text. The other thing I do is forward texts with that string to my gmail account so I get it as an email. I figure if someone has my device and is trying to log in then they can't see my Google voice or emails
I will try this in the morning. I just drove the family 12 hours back from our Disney vacation. Ah, my own bed to sleep in.
-Chlorine
bk201doesntexist said:
Code:
fastboot boot cwm_or_twrp.img
when in recovery:
Code:
adb pull /sdcard/
note: if no folder is really pulled, change /sdcard/ to /data/media
Click to expand...
Click to collapse
While waiting for things to settle down this morning I thought I would try one last thing to get the phone back to working. Within CWM I choose to use fix permissions. After a few minutes it finished and returned to CWM menus as normal. I rebooted the phone and it's working. I'll need to copy the files from it before progressing forward. Once I do this I will try rebooting and see what it does. Take in mind I tried flashing, recovering, etc before I even thought of the fix permissions. It stopped me in my tracks with the errors. Once I reboot I will post my results. I just hope I didn't leave my cable in Florida.
:victory:
-Chlorine
Just bought a new cable and I'm starting a full backup now. I'll reboot and see if the phone loops again or not in an hour or so. Details to come.
Reboot. No boot loop.
I've spent about 3 days and worked closely with a few knowledgeable people outside of this forum. I'm desperate and a bit terrified to start this topic. I've read too many to know how frustrating it to answer the same questions over and over again.
In short:
a.) Was running CM9, flashed using CWM. (Did not have issues and have flashed in the past with other roms successfully)
b.) Went to flash another ROM (can't remember which one) and did not back up (big mistake, troll away)
c.) Cannot get phone to start, can flash roms all day long and only get to their boot/splash screens. It will sit there until my battery dies
d.) I've tried Galaxy Nexus Toolkit and Wugs
e.) I've installed TWRP and formatted drive
f.) I've read and followed 3 full days of different forums and still can't figure this out. I've tried so many things it would take forever to type.
I'm severely desperate.
Will someone help me start from scratch and walk me through a surefire process. At this point, I'm lost. Nothing seems to work.
Apologies in advance and I am willing to accept the bad vibe. I'm lost.
Phone is a Verizon Galaxy Nexus
Did you try fully wiping, formatting /system, flashing a ROM and wiping cache after that? Or flashing another kernel?
Wow finally something
Wow! I finally got something to load. I'm on 4.0.2. I need to get back to jelly bean.
Wow, I'm stuck in nearly the same rut as you are in right now.
Experienced flasher here too - I was using the Xylon v18 until now, and Paranoid Android 2.99 before this. Yesterday night my phone rebooted after some weird Contacts application opening issue. And kept rebooting. One backup restore said there was an I/O error in /data/data/com.android.contacts or something. The backup never booted.
I have TWRP 2.4.0.0.
I tried new ROMs, different ROM backups, a few kernels, formatting /data including internal memory, tried Adb sideloading (said Read Only file system), finally installed Xylon v18 through Usb-otg, but it refused to go beyond Google logo. Restored a backup through OTG, and the same continues.
Could someone tell me what could be going on here?
I swear I was about to put in a post similar to the OP.
Thanks for the headsup just_some_dude, I'll go try an ICS rom now.
---------- Post added at 01:59 PM ---------- Previous post was at 01:23 PM ----------
Edit1 : So it looks like my phone wanted to remind me what it feels like to actually jump with joy!
Installed the deodexed version of stock rom, and after a failed first boot, "Android is upgrading".
Edit2: Scratch that, couldn't get through phone setup. Changed to CWM 6.0.2.3. Flashed radio and RIL, PA2.99 again, and for now it seems to be working.
desktopfusion said:
Wow, I'm stuck in nearly the same rut as you are in right now.
Thanks for the headsup just_some_dude, I'll go try an ICS rom now.
---------- Post added at 01:59 PM ---------- Previous post was at 01:23 PM ----------
Click to expand...
Click to collapse
I was able to IMM76K, but phone wants to push newer version. I can't upgrade newer version without it getting stuck on that splash screen for the rom. I'm putting IMM76K back on.
So, weird. So much of this is not making sense to me.
Rebooting continuing for me despite different kernel and cache/dalvik wipes.
I'm sorry, absolutely not trying to hijack this thread. Only writing symptoms incase anyone notices something they have gone through too.
Baah, this is going to properly spoil my weekend.
Why not try to go back to stock by flashing the stock images first? At least you'd know if the phone works...
Thank you for the input.
I did, but in the zip, deodexed form. For me, all things are now pointing to Wifi causing the reboots, even when the Stock 4.2.1 was used I couldn't go past phone setup.
On PA2.99, after switching wifi off as soon as it booted, the phone is now stable for 10 minutes for the first time in 8 hours of trial-and-error.
Shouldn't XXLH1 flashing have fixed such things?
FIXED! It was a corrupted /data partition, which showed the /data/media or /sdcard was already 11 gb full after a full wipe with TWRP.
A /data and /data/media format with CWM did the trick!
desktopfusion said:
Thank you for the input.
I did, but in the zip, deodexed form. For me, all things are now pointing to Wifi causing the reboots, even when the Stock 4.2.1 was used I couldn't go past phone setup.
On PA2.99, after switching wifi off as soon as it booted, the phone is now stable for 10 minutes for the first time in 8 hours of trial-and-error.
Shouldn't XXLH1 flashing have fixed such things?
Click to expand...
Click to collapse
For reference, that's not going back to stock. Back to stock means flashing the Google factory image, which would have also formatted your data partition, so do that in future
EddyOS said:
For reference, that's not going back to stock. Back to stock means flashing the Google factory image, which would have also formatted your data partition, so do that in future
Click to expand...
Click to collapse
Ah, I did not know flashing the image wiped data partition as well, thanks!
I stopped looking for the image when I couldn't find JOP40G on the site. Classic case of beggars trying to be choosers. :cyclops:
I just tried to flash mmuzzy and gapps using wugs and am sitting at the Jelly Bean 'X' splash screen. I set it up so wugs would wipe data cache and Dalvik. Don't know what it is, but I cannot get Jelly Bean on this phone.
Tried flashing the Stock factory image? Not through recovery, but through fastboot. That is what I did ultimately.
Actually, my problem was deeper. My /userdata partition had some errors. On going through some posts here on /data partition corruption issues, these links helped me a lot, and made the phone ultimately much smoother than it ever was!
Definitely try the e2fsck command through adb shell while in recovery with /data partition unmounted. Try this before you flash a stock ROM image.
Here you go. I think these should help you too:
1. http://forum.xda-developers.com/showthread.php?t=1541379&page=4
2. http://forum.xda-developers.com/showthread.php?t=2025675
3. http://linux.101hacks.com/unix/e2fsck/ - e2fsck command options if you need help.
If adb asks you to 'check forced' because it finds problems, just use
Code:
adb shell "e2fsck -f /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata"
I'm guessing it was all a result of months of flashing huge amount of ROMs. :angel:
So my phone is stuck in bootloop. and I cant get my phone to boot correctly.
To start, I was running 4.2.2 AOKP for about half a year and it started to not work as well. Force closing alot, freezing etc. So I decided it was time to update. While I was running AOKP, I experienced bootloop almost every time I turned off my phone. This became regular, but by pulling the battery and trying again (sometimes I had to do with a few times) it always got working again.
I went and found the new 4.3 Carbon ROM and decided that looked cool and would be a nice upgrade. So I downloaded it and the new 4.3 gapps. Put them on an external sd card, and put it into my phone. I then booted into CWM and did a factory reset. Then I went and installed the Carbon from the external sd, installed gapps, and rebooted immediately. I was then, and still am, stuck in a bootloop.
I can restart my phone go back into clockwork.
But I cant get the phone, despite all my efforts, to boot correctly. I have tried to wipe caches, wipe dalvik, format system. All of it. yet I cannot boot correctly.
I really need a working phone. Any help would be really great.
Thanks all
Also, I am using TWRP 2.6.3 to do the flash of the Carbon after it failed the first time
Moheemo said:
Also, I am using TWRP 2.6.3 to do the flash of the Carbon after it failed the first time
Click to expand...
Click to collapse
2.6.3.0 seems to be giving many people issues. You need to install 2.6.1.0.
And is your radio up to date? Only 2 work...the new T-Mobile and Telus radios.
After those 2 things are taken care of, you should be fine. Tho lots of things can cause boot loops, and there's many.. many posts about it. If my suggestions don't help.....Search and read up. Try some various fixes.
Maybe try a different rom too.
Sent from my cellular telephone
---------- Post added at 03:09 PM ---------- Previous post was at 03:06 PM ----------
Hope you did a nandroid backup in recovery? Restore it if so. If not, you may need to start from scratch and Odin flash stock rom, flash recovery and root again.
Sent from my cellular telephone
Moheemo said:
So my phone is stuck in bootloop. and I cant get my phone to boot correctly.
To start, I was running 4.2.2 AOKP for about half a year and it started to not work as well. Force closing alot, freezing etc. So I decided it was time to update. While I was running AOKP, I experienced bootloop almost every time I turned off my phone. This became regular, but by pulling the battery and trying again (sometimes I had to do with a few times) it always got working again.
I went and found the new 4.3 Carbon ROM and decided that looked cool and would be a nice upgrade. So I downloaded it and the new 4.3 gapps. Put them on an external sd card, and put it into my phone. I then booted into CWM and did a factory reset. Then I went and installed the Carbon from the external sd, installed gapps, and rebooted immediately. I was then, and still am, stuck in a bootloop.
I can restart my phone go back into clockwork.
But I cant get the phone, despite all my efforts, to boot correctly. I have tried to wipe caches, wipe dalvik, format system. All of it. yet I cannot boot correctly.
I really need a working phone. Any help would be really great.
Thanks all
Click to expand...
Click to collapse
flash stock rom zip via odin then you should be good to root and try to flash another custom rom again:good:
All I want..... Is an S3 with AICP on Sprint's network.
Two weeks ago I bought an S3 for $50, started playing with it, easily flashed AICP and TWRP 2.8.7.0 Recovery. Everything was awesome, until Sprint couldn't activate it. I flashed back to stock through Odin, Sprint still couldn't activate it (problems with programming). There was no Sprint boot screen, so assuming that was the main problem I found "SPH-L710_ND8_Full Restore_UNROOTED.exe" that restored the Sprint boot logo and viola! I had Sprint 4GLTE and talk and text.......... But now, this little devil S3 won't flash Roms that are 5.0 or newer. I have tried AICP, PAC-ROM, Vanir, Exodus.... all just boot to the boot logo and stay there, but when i try Gummy 4.4.4 it boots and works fine.
I always wipe cache, dalvik, & use correct gapps. Using TWRP 2.8.7.0 and have tried two other recoveries with same result. Tried flashing L710VPUDNJ2_L710SPRDNJ2_L710VPUDNJ2_HOME.tar.md5 through Odin and then reflashing recovery and retrying ROM, same result.
Right now its working fine with gummy 4.4.4 but I want 5.1-6.0 because that's the only way I will feel ok about having an S3 I'm sure I'm forgetting some details as this has been a two week off and on thing trying to get this phone to work, so if I am please forgive me and have pity (I'm using a blackberry Q10)
Why will lollipop roms not boot?!?!?!
Please..... help me obi wan kenobi...... you're my only hope
Papa Z said:
All I want..... Is an S3 with AICP on Sprint's network.
Two weeks ago I bought an S3 for $50, started playing with it, easily flashed AICP and TWRP 2.8.7.0 Recovery. Everything was awesome, until Sprint couldn't activate it. I flashed back to stock through Odin, Sprint still couldn't activate it (problems with programming). There was no Sprint boot screen, so assuming that was the main problem I found "SPH-L710_ND8_Full Restore_UNROOTED.exe" that restored the Sprint boot logo and viola! I had Sprint 4GLTE and talk and text.......... But now, this little devil S3 won't flash Roms that are 5.0 or newer. I have tried AICP, PAC-ROM, Vanir, Exodus.... all just boot to the boot logo and stay there, but when i try Gummy 4.4.4 it boots and works fine.
I always wipe cache, dalvik, & use correct gapps. Using TWRP 2.8.7.0 and have tried two other recoveries with same result. Tried flashing L710VPUDNJ2_L710SPRDNJ2_L710VPUDNJ2_HOME.tar.md5 through Odin and then reflashing recovery and retrying ROM, same result.
Right now its working fine with gummy 4.4.4 but I want 5.1-6.0 because that's the only way I will feel ok about having an S3 I'm sure I'm forgetting some details as this has been a two week off and on thing trying to get this phone to work, so if I am please forgive me and have pity (I'm using a blackberry Q10)
Why will lollipop roms not boot?!?!?!
Please..... help me obi wan kenobi...... you're my only hope
Click to expand...
Click to collapse
If you the original Sprint S3 and not the new Sprint Triband S3 then you should not have any problem at all! How long are you waiting on it to boot? I had the new Triband model and I had and I thought the lollipop roms wouldn't boot either but I had to give it 5-10mins sometimes on the 1st boot!
RootSuperSU said:
If you the original Sprint S3 and not the new Sprint Triband S3 then you should not have any problem at all! How long are you waiting on it to boot? I had the new Triband model and I had and I thought the lollipop roms wouldn't boot either but I had to give it 5-10mins sometimes on the 1st boot!
Click to expand...
Click to collapse
I have let it sit overnight a few times now.... just to make sure. With the Gumy 4.4.4 Rom it only took about 2 minutes which I was shocked by.
I feel like I have literally tried everything.
Papa Z said:
I have let it sit overnight a few times now.... just to make sure. With the Gumy 4.4.4 Rom it only took about 2 minutes which I was shocked by.
I feel like I have literally tried everything.
Click to expand...
Click to collapse
Yea Kitkat roms don't take very long on 1st boot anymore. But as for lollipop what all roms have you tried flashing?
There's only 2 reasons I can think of that they might not be working. 1st is your model SPH-710T or SPH-710 and 2nd are trying to flash a custom kernel with it?
Another thing I feel like is worth mentioning.... When I first flashed the AICP Rom I played with it for a few days so i had all my stuff installed. Realized I had to flash to stock to activate on Sprint so i made a Nandroid backup of my AICP 5.1 setup. When i restore this backup it boot loops as well.
Tried restoring everything except data, wiped dalvik and cache, all using the same twrp recovery. So strange...
RootSuperSU said:
Yea Kitkat roms don't take very long on 1st boot anymore. But as for lollipop what all roms have you tried flashing?
There's only 2 reasons I can think of that they might not be working. 1st is your model SPH-710T or SPH-710 and 2nd are trying to flash a custom kernel with it?
Click to expand...
Click to collapse
I have tried AICP, PAC-ROM, Vanir, Exodus.... all just boot to the boot logo and stay there. Mine is the SPH-L710 not the triband 710T. The Roms I tried to install, as far as I know, come with the kernel in the ROM zip. I have tried AICP and the pac-rom with just the rom zip and gapps, as well as with a few custom kernels just to see if it would change anything.
Ah another thing, may be unrelated because I only get this when flashing AICP and Pac, it says "unmount of /system failed; no such volume" and then flashes boot img and seems to be successful.
When I flashed exodus and Vanir it does not say this, and all seems to go perfect..... buuuuuut still boot loops/gets stuck at boot animation
Even tried flashing rom and gapps via adb sideload
I have a bad esn l710 in really poor condition. Just flashed the same recovery, same AICP rom, same gapps, all from the same SD card, and this one is working fine. Boots up in just a few minutes.
So i have to be missing something or something is wrong with the one I can actually activate.
EDIT: So "unmount of /system failed; no such volume" error doesn't matter, same thing happened on the bad ESN device that booted up fine.
Update (if anyone cares lol): I flashed both devices completely to stock with the "SPH-L710_ND8_Full Restore_UNROOTED.exe" and then did the exact same thing to both devices, twrp>aicp rom>gapps>dalvik>boot, the bad ESN crap device boots AICP fine, the good condition good ESN one boot loops forever.
I am at a loss here, both devices are exactly the same SPH-L710, flashed to stock completely, but the one with a good ESN that would actually work will not boot lollipop roms. I disassembled both devices to look for hardware differences of any kind, they're identical (with no signs of damage). The only difference is the bad esn one is a slightly deeper shade of blue. I'm pulling my hair out.
I even tried using the force, but my midichlorian levels have never been that good.
Who knows man
I've seen this only a couple times. One guy had luck. When it was stuck, he just kept randomly hitting the power button and eventually long pressed until it was about to reboot (screen freezes for a second) and when it shut off, held home and volume up so it booted recovery when it came on. Then just rebooted system, and this time it booted. Also, sometimes when going back and forth between KitKat and lollipop, you need to wipe internal storage. Make sure you have the latest twrp too (2.8.7.0).
Just shots in the dark, but you never know.
I saw one member who was never able to boot lollipop roms, you would be the second. So its pretty rare.
Well you now know 3 people that cant flash lollipop roms on an l710 NON tri-band.... Ive tried all of them including a couple of Vanir 6.0 roms and the ONLY one i could get to take was a BeanStalk 5.01 rom and a Candykat only after flashing its KitKat predecessor... All KitKat roms work just fine.. Curious,, as I also used the same odin non- rooted rom to get back to stock and after that had trouble flashing lollipop roms period.. Maybe something with the symlinks in that un-rooted rom??? I'm at a loss myself...
madbat99 said:
I've seen this only a couple times. One guy had luck. When it was stuck, he just kept randomly hitting the power button and eventually long pressed until it was about to reboot (screen freezes for a second) and when it shut off, held home and volume up so it booted recovery when it came on. Then just rebooted system, and this time it booted. Also, sometimes when going back and forth between KitKat and lollipop, you need to wipe internal storage. Make sure you have the latest twrp too (2.8.7.0).
Just shots in the dark, but you never know.
I saw one member who was never able to boot lollipop roms, you would be the second. So its pretty rare.
Click to expand...
Click to collapse
As the only possible solution I have not tried, I will attempt to randomly press/long press the home button as it boots and then boot recovery..... lol
What's even weirder is it worked fine with AICP lollipop just about a month ago, before i had done anything to it. but I repeated all the things i did to it on another s3 and that one still worked fine with lollipop roms.
nexusdread13 said:
Well you now know 3 people that cant flash lollipop roms on an l710 NON tri-band.... Ive tried all of them including a couple of Vanir 6.0 roms and the ONLY one i could get to take was a BeanStalk 5.01 rom and a Candykat only after flashing its KitKat predecessor... All KitKat roms work just fine.. Curious,, as I also used the same odin non- rooted rom to get back to stock and after that had trouble flashing lollipop roms period.. Maybe something with the symlinks in that un-rooted rom??? I'm at a loss myself...
Click to expand...
Click to collapse
I used that same unroooted Odin rom on a bad esn s3 and it works fine with lollipop roms. So strange
Edit: no idea what symlinks are
I have similar probl.
After 4 months with CM12.1 I'm flashing NJ2 and upd. to OH1.
After THAT - I cant to flash anything ROM lollipop and higher.
I dont know, what is it.
I was waiting for 4 hours, 8 hours, 12 hours, a day!
I dont know, I dislike TW roms, help anyone!
CyanogenMod 13.0 D2SPR
...I dunno, wanna start from scratch?
http://forum.xda-developers.com/galaxy-s3-sprint/development/rom-d2spr-cyanogenmod-13-0-t3248561
- Use the Sprint-made TWRP .img in the OP with Flashify (from the Play Store)
- Flash a CM 13, add GApps (from OpenGApps), and a recent SuperSU.
I'm a bit of a half-no0b, so I may be talking out me pants.
Bonne chance!
DavidovDI said:
I have similar probl.
After 4 months with CM12.1 I'm flashing NJ2 and upd. to OH1.
After THAT - I cant to flash anything ROM lollipop and higher.
I dont know, what is it.
I was waiting for 4 hours, 8 hours, 12 hours, a day!
I dont know, I dislike TW roms, help anyone!
Click to expand...
Click to collapse
I'm glad I'm not the only one. Someone has to know how to fix this.... somewhere.
Papa Z said:
I'm glad I'm not the only one. Someone has to know how to fix this.... somewhere.
Click to expand...
Click to collapse
Yep!:crying::crying::crying:
I had the same problem. Try this. It worked for me today.
I have a d2spr (originally from sprint). It is now activated with boost. L710VPUDOH1 bootloader and baseband. CF-Auto-Root-d2spr-d2spr-sphl710.tar.md5 flashed with odin for root. twrp-2.8.7.0-d2spr.img.tar.md5 flashed with odin as recovery. I backed up Apn's with "APN Backup & Restore" app. I wiped system, cache, dalvik, data. Flashed cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2spr.zip... . Flashed pa_gapps-modular-full-5.1-20150315-signed.zip. I Wiped Dalvik. The device booted smoothly within approximately 7 minutes. I had full function as far as I could tell. Everything worked well. Ran this setup for about a month. I decided to restore a stock w/root backup made with twrp2870. Bootlooped until I learned to wipe internal sd when going back to 4.4.2. I wiped the internal sd and successfully booted stock w/root backup. When I tried to go back to cm 12.1 backup, I ran into the same problem... boot loop for hours. Multiple times. Backups and different nightly zips. I found and flashed every custom recovery I could find for this device to try to make it work. Eventually... while I had twrp-2.8.7.2-d2spr.img as my recovery (not sure if it makes a difference or not). I found this...
(apparently the link is not allowed due to my lack of posts with this forum)
im pasting from another page at this point...
Ha! Got it! Visited the #cyanogenmod channel on freenode irc and there were some VERY helpful people there. So I've got a few instructions.
Flash the latest TWRP recovery via ODIN. (2.8.7.0-d2spr at the time of writing).
Flash your CM 12 zip file
On your PC (with adb installed) run the command "adb shell dd if=/dev/block/platform/msm_sdcc.1/by-name/persist of=/sdcard/persist.img"
Then run "adb pull /sdcard/persist.img" (This will give you a backup of the persist partition in case anything goes wrong)
Run the command "mke2fs -t ext4 /dev/block/platform/msm_sdcc.1/by-name/persist"
Run the command "adb reboot"
If it boots into OS, great! Reboot into recovery and install the lastest gapps package.
I did it from adb in a Cygwin64 Terminal. The device booted my cm12.1 backup the first time I tried. I think it would work just as well with adb from a windows command prompt. I only found this on another page. Credit goes to someone from "#cyanogenmod channel on freenode irc". Hope it is as much help to all of you as it was to me.
HouseHG said:
I have a d2spr (originally from sprint). It is now activated with boost. L710VPUDOH1 bootloader and baseband. CF-Auto-Root-d2spr-d2spr-sphl710.tar.md5 flashed with odin for root. twrp-2.8.7.0-d2spr.img.tar.md5 flashed with odin as recovery. I backed up Apn's with "APN Backup & Restore" app. I wiped system, cache, dalvik, data. Flashed cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2spr.zip... . Flashed pa_gapps-modular-full-5.1-20150315-signed.zip. I Wiped Dalvik. The device booted smoothly within approximately 7 minutes. I had full function as far as I could tell. Everything worked well. Ran this setup for about a month. I decided to restore a stock w/root backup made with twrp2870. Bootlooped until I learned to wipe internal sd when going back to 4.4.2. I wiped the internal sd and successfully booted stock w/root backup. When I tried to go back to cm 12.1 backup, I ran into the same problem... boot loop for hours. Multiple times. Backups and different nightly zips. I found and flashed every custom recovery I could find for this device to try to make it work. Eventually... while I had twrp-2.8.7.2-d2spr.img as my recovery (not sure if it makes a difference or not). I found this...
(apparently the link is not allowed due to my lack of posts with this forum)
im pasting from another page at this point...
Ha! Got it! Visited the #cyanogenmod channel on freenode irc and there were some VERY helpful people there. So I've got a few instructions.
Flash the latest TWRP recovery via ODIN. (2.8.7.0-d2spr at the time of writing).
Flash your CM 12 zip file
On your PC (with adb installed) run the command "adb shell dd if=/dev/block/platform/msm_sdcc.1/by-name/persist of=/sdcard/persist.img"
Then run "adb pull /sdcard/persist.img" (This will give you a backup of the persist partition in case anything goes wrong)
Run the command "mke2fs -t ext4 /dev/block/platform/msm_sdcc.1/by-name/persist"
Run the command "adb reboot"
If it boots into OS, great! Reboot into recovery and install the lastest gapps package.
I did it from adb in a Cygwin64 Terminal. The device booted my cm12.1 backup the first time I tried. I think it would work just as well with adb from a windows command prompt. I only found this on another page. Credit goes to someone from "#cyanogenmod channel on freenode irc". Hope it is as much help to all of you as it was to me.
Click to expand...
Click to collapse
I flashed mine back to stock and sold it.... got a good deal on an S5 and flashed MOAR to it.
I found this thread a while back and attempted to do what it says to do, but I couldn't get it to work for me. What exactly does running those commands do that suddenly makes it work?
I think it either reformats or converts the persist partition to ext4. I'm not 100% sure yet bc I haven't had time to look into it.
Sent from my SPH-L710 using Tapatalk