I rooted and ran a couple diff custom ROMs: cm10.1.3 and infamous alpha, both with oc kernels (never set mhz past 2051). Began getting random reboots, alot while running the Alpha ROM, and a couple while running cm10.1.3 which I thought was weird because its a RC. should be stable, right? Anyway, got tired of RRs, so I decided to unroot and got stock, till I had some free time.to tinker with it. Well guess what, getting RRs EVEN IN UNROOTED STOCK. Any ideas?
I'm not exactly sure what steps you have taken to get back to Stock, where you're still having random reboots, but I'll let you know what I've done in the past to get to Stock which resolved the issues:
- Factory reset device from device. Save and/or move your Internal files/data prior as you'll be wiping Internal. I'd remove my extSdCard prior to Factory reset and after moving files to it.
- ODIN Samsung Stock Firmware
http://samsung-updates.com/details/9595/Galaxy_S_4_T-Mobile/SGH-M919/TMB/M919UVUAMDL.html
- After the device boots, you'll probably get stuck on the Samsung splash boot screen. After a few minutes - -
- pull the battery, replace the battery but Don't power the device on
- Place device in Stock Recovery mode by pressing Power and Vol up buttons at the same time.
Release the buttons when you see the blue letters appear in the upper left hand corner of the screen.
- Scroll to Factory reset using the volume buttons.
(During the above process, you'll see the Android on its side with a Red X on him/her.)
- press the power button to lock in Factory reset
Let the Recovery scroll through its script
(during this process the Android will come to life )
- After the script is completed which takes less than a minute or so, scroll to reboot and select it with the power button.
- the device will now boot.
Important: while the device is booting, the screen will stay on the T-Mobilessplash screen for what will seem forever. Don't panic. The screen will show T-Mobile across the screen for about 15 or so minutes. Could be a little more or a little less. The device will then continue and complete the booting cycle.
Some notes:
1) during the above process, I have removed my extSdCard card as I didn't want tottake a chanceiit would be wiped. ODIN doesn't wipe extSdCard card but I don'tbneed it during theiprocess so I remove it in case Murphy decides to pay a visit.
2) during ROM flashes, I've experienced almost every issue youccan imagine. This occurred while using TWRP 2.5.0.2, but only when flashing ROMs with Aroma. For months prior, I had zero issues.
The problems I was experiencing were:
Random reboots, splash screen freezes, bootloops, installation of choices in Aroma which only partially installed, issues which didn't seem to havesan answer, and when you found the solution, that solution wouldn't work when the issue appeared again.
- constantly ODINing back to stock
- sometimes in Recovery, I couldn't get past the TWRP lockscreen, and only wiping Internal SD resolved the issue so I could do a Factory reset. I was doing this so often, that I left all files on my extSdCard so Iewouldn't lose my data when I had to wipe internal. It was faster this way as I didn't have to keep moving stuff back & forth.
After endless hours of troubleshooting and aggravation, I changed Recoveries.
I installed Philz Touch Recovery, and I have had Zero issues since installing it about 3 or so weeks ago, which have included multiple ROM flashes with Aroma.
I didn't want to switch Recoveries as I was very used to TWRP, but I just couldn't deal with the new found issues I was having so I made the switch and haven't looked back. Some people don't have issues with TWRP, but I wasn't one of them
Hopefully you can relate to some of my experiences which I have written above, which may help you to resolve some of the issues you're experiencing.
Yes. Thats the file I used and also the steps. I dont know what the deal is.
twatts723 said:
Yes. Thats the file I used and also the steps. I dont know what the deal is.
Click to expand...
Click to collapse
If you:
Wiped Internal SD
ODINd Stock Firmware
which flashed successfully
and are still having random rebooting.....
I can only suggest:
Check your device settings, if you haven't done so already to insure you're running:
Stock ROM
Stock modem/radio
And that all settings are stock.
If everything checks out, I can only suggest to:
Download the Samsung Stock Firmware file again
Check the md5 checksum
ODIN Samsung Stock Firmware again
And see how it goes.
So it turns out, if once you flash the stock firmware through odin, you just have to let it "settle in" for a couple days and all the problems go away. Thanks man.
twatts723 said:
So it turns out, if once you flash the stock firmware through odin, you just have to let it "settle in" for a couple days and all the problems go away. Thanks man.
Click to expand...
Click to collapse
Glad everything worked out for you.
Don't shy away from custom ROMs though, as you'll be missing out on some good stuff
As a note, there can be many thinks which can contribute to issues after the installation of a Custom ROM, Kernels, etc. such as:
Bad downloads, corrupted files, app conflicts, dirty flashes instead of Full wipes, etc., etc.
Another issue can be related to the Recovery you are using.
I had many, many issues regarding flashing ROMs which installed with Aroma.
Prior to ROMs w/Aroma, I had Zero issues.
I suggest using Philz Touch Recovery.
In case you don't have it installed and want to try it, I'll post a link to the download page.
Flash the proper file for your specific carrier.
Install the tar file with ODIN or
Flash the zip file with your Recovery......
Well, I come from sgs2. On that device, I could flash everything through cmw, and just use darkside super wipe and darkside cache wipe. No problem. Every rom from cm to amatuer custom blibbidy blobbidy, no problem. When I rooted my s4, I went straight to twrp because everyone said it was better. I flashed cm10.1.3 rc - rr. Infamous alpha v.7, which was supposed to be stable - rr. I went back to stock, rooted again, and kept stock tw, and only flashed ktoonz kernel, which is supposed to be one of the best for this device. Everything ran great, but guess what - rr. So I gave up. Went back totally stock. Working a lot of hours at work right now. We slow down after thanksgiving, so I'll probably start flashing again around that time. Thanks for thw help though
cheers.
What's up guys!
Using ROM installer I flashed vanir 4.4 along with 4.4 gapps on my sprint gs3 sph l710. I wiped the cache and it looked as if it were installing fine but winded up getting stuck in boot loop mode instead. Now when I try to boot into recovery the twrp screen flashes and then it goes straight into bootlop mode from there. Now i cant acsess any of my backups. I can get into down load mode but unfortunately my computers messed up right now. I can't hit the run button on Odin because the screen is too big. I know it sucks!!! Does anyone know some tricks I can use or have any recommendations. Your help would be greatly appreciated! BTW.. I was running illusion 4.3 when this happened.
ddray said:
What's up guys!
Using ROM installer I flashed vanir 4.4 along with 4.4 gapps on my sprint gs3 sph l710. I wiped the cache and it looked as if it were installing fine but winded up getting stuck in boot loop mode instead. Now when I try to boot into recovery the twrp screen flashes and then it goes straight into bootlop mode from there. Now i cant acsess any of my backups. I can get into down load mode but unfortunately my computers messed up right now. I can't hit the run button on Odin because the screen is too big. I know it sucks!!! Does anyone know some tricks I can use or have any recommendations. Your help would be greatly appreciated! BTW.. I was running illusion 4.3 when this happened.
Click to expand...
Click to collapse
Can you try using this? http://forum.xda-developers.com/showthread.php?t=1746680
Maybe that'll work, you can use it to return to stock, and if anything I would recommend going back to stock before doing anything else. Also, it may not be the consensus of the site here but in my own opinion, I don't like using rom installer or goo manager or anything. I like doing it all myself in recovery. I've heard one too many stories of people getting hardbricked because their rom installer or whatever downloaded the international version of the rom they wanted :/ always best to check your own md5 checksums and make sure you're downloading the rom for your phone from your phone's forum.
As for the exact reason your phone did that? I couldn't tell you, maybe with a little more info someone more knowledgeable here could tell you
So i got my computer fixed. I havent tried the tool kit in the thread you recommeded. I decided first to use a stock file i have on odin first that has saved me from softbricks in the past. I set everything up hit start, watched the process complete with the pass. Now it shows the stock boot animation but still stuck in bootloop mode. I put it into recovery,which is now stock instead of twrp, wiped cache, davlik cache and factory reset then i reconnected to odin and reflashed the stock file. Still stuck in bootloop mode!!!! Plain reboot and same thing :/ so for the hell of it, i wanted to see if i can to my backups by restoring twrp. So i flashed my cf auto root and then flashed my twrp file and bam!!!! Twrp was full functioning with all my backups!!! :laugh: next i restored my latest illusion 4.3 rom and wala! Ive got a fully functioning rooted phone with a custom rom. I flipped through everything to make sure it looks good and it does. Except.... any photos and music that are saved to phone and not sd card are gone I dont understand, everthing else is backed. Contacts, call logs, messages, text messages, apps, customised settings etc...I even flashed my carbon rom that had the same music and pics. When i open gallery it shows the photo count in snapseed and others im looking for but then they all start dissapearing!!! i also dont understand why the stock file which has saved me from softbricks before didnt work. I dont know anything about checking md 5 checksums but if its worth the time ill do my research! Im happy i got my phone working but i would like to be more solid in what im doing. Maybe someone can help shed some light on this.
Hey all,
I have read all over the place on how to get this working but I honestly get more confused the more I read. I wanted to switch to another OS since my phone was starting to become bogged down (too many pictures, videos, old files, etc etc etc; My phone is my work tool since I'm a field sales engineer)
So I went ahead and rooted it with ODIN 3 v1.85 and I317-UCUBMK6.tar.md5. I also installed TWRP although I have no clue which version it is. I suppose it's the latest one. My bootloader is LJ2.
I always do the full swipe and a NANDROID back up. However, when I flash a custom ROM, I always end up stuck on the Samsung Galaxy Note II screen. It won't go.
I have tried to install the following ROM's:
DN3 - Always says "Failed" when I try to flash, even when following instructions of reboot recovery and flash again.
JEDI X 20 - Go through the entire aroma installer - it installs - asks for reboot - when rebooting, stuck as Samsung Galaxy Note 2 screen
and it pretty much happens with all of them. I have decided to back to stock (because I was a retard and accidentally deleted my NANDROID backup) and now I find my WIFI is broken.
I pretty sure this has all been discussed in various threads but I rather bring it all into one so that all that are having the same issue as me (I read a lot of people complaining about this issue with very scattered replies) can have a single thread that addresses how to fix this.
Any help will be greatly appreciated.
alkaroth said:
Hey all,
I have read all over the place on how to get this working but I honestly get more confused the more I read. I wanted to switch to another OS since my phone was starting to become bogged down (too many pictures, videos, old files, etc etc etc; My phone is my work tool since I'm a field sales engineer)
So I went ahead and rooted it with ODIN 3 v1.85 and I317-UCUBMK6.tar.md5. I also installed TWRP although I have no clue which version it is. I suppose it's the latest one. My bootloader is 4.3 (I think; I go to About Device and I see the android version 4.3)
I always do the full swipe and a NANDROID back up. However, when I flash a custom ROM, I always end up stuck on the Samsung Galaxy Note II screen. It won't go.
I have tried to install the following ROM's:
DN3 - Always says "Failed" when I try to flash, even when following instructions of reboot recovery and flash again.
JEDI X 20 - Go through the entire aroma installer - it installs - asks for reboot - when rebooting, stuck as Samsung Galaxy Note 2 screen
and it pretty much happens with all of them. I have decided to back to stock (because I was a retard and accidentally deleted my NANDROID backup) and now I find my WIFI is broken.
I pretty sure this has all been discussed in various threads but I rather bring it all into one so that all that are having the same issue as me (I read a lot of people complaining about this issue with very scattered replies) can have a single thread that addresses how to fix this.
Any help will be greatly appreciated.
Click to expand...
Click to collapse
Try this method flash the odin version and update the bootloader ne5 and you should be fine
http://forum.xda-developers.com/showthread.php?t=2802189
210
Thanks man. That post brought a lot to light. So I have the MK6 firmware but the LJ2 bootloader. I'll try doing what Zen Arcade says there but unfortunately I cant download his files. The website he's hosting the files from has severe lag and the files stop downloading.
I'll get back to you on how this goes once I'm able to download them.
terpin32 said:
Try this method flash the odin version and update the bootloader ne5 and you should be fine
http://forum.xda-developers.com/showthread.php?t=2802189
Click to expand...
Click to collapse
Finally downloaded it. Installed it and got that particular operating system working. I will try to get some customs roms installed. Thanks for the help man!
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
i have a samsung galaxy note 2 GT-N7100 international. i have been rooted for
over a year and have successfully loaded more than 10-15 ROM's. most of these
are in the 4.4.1 - 4.4.4 OS range. these load OK.
my problem is with most all of the rom's ported for the N-7100 coming from 5.0
to 6.0+ OS's. most of these are based off of cyangen mods compiles. the
symptom i have is: after following the directions in the compiler's post, i
get to the boot splash screen yet no further. no boot loop: it just never
boots up. i have waited 10" min for first boot. i waited 30" on 2 of them.
they just wont boot up. ever. my details are as follows below. im looking
for help on this because i know the problem must be on my end....all of these
compilers cannot all be wrong.
- im following OP directions always to the T; usually these include factory
reset (cache, dav cache, data wipes), sometimes they want system wiped too.
then you flash the ROM, then gapps. then you reboot.
this is standard. but sometimes they want you to also wipe cache + dav cache
AGAIN after the reload, then, reboot. in my mind, such a complete ROM install
removes all error from users like me...what more can you wipe?
- im always using ROM's designated only for the GT-N7100 int version note 2.
always.
roms that have NOT installed lately:
- [OFFICIAL][6.0.1][v6.0][STABLE]BlissRoms
- [ROM][5.1.1][Haxynox] AOSP for n7100
- [ROM][6.0.1][n7100]RESURRECTION REMIX 5.6.x[CM13]
- Alliance ROM for Galaxy Note 2 GT-N7100
roms that DO LOAD:
- Criskelo ROM for Galaxy Note GT-N7100
- Sungsonic HD ROM for Galaxy Note 2 GT-N7100
- DN4 ROM GT-N7100
- [ROM][GT-N7100][TW 4.4.4] Eclipse By AC
again: i need help with this problem which is my problem: in the list above
the unsuccessful rom's boot only to the splash screen, then hang. for 30+
min. no boot loop's, they dont boot at all.
i CAN later reboot into recovery or bootloader OK. i can re-install from previous
nandroid backup OK. i just CANNOT get them to boot. even after wiping both
caches and data and system before flashing, and, even after wiping both caches
afterwards.
more details:
1) im using both twrp 2.8.7.0 and latest cwm 6.0.4.3 touch recoveries. i
prefer and use twrp. ive tried loading the above failed roms above with both
recoveries, no help. i didnt think it mattered which recovery was used until
one time, the system partition didnt mount on twrp after a failed rom install.
it would'nt wipe nor format on twrp. i could not reinstall my nandroid
backup and was stuck.
i later flashed cwm 6.0.4.3 and it fixed it (the system partition problem,
but, cwm never installed the above rom's either). so there is a difference
after all but not much.
2) my roms are stored on my ext sd card. not sure if that's impt.
what's my problem?
1) if it's me please help
2) is it my phone? my GT-N7100 was bought in turkey. is my hardware really
different (ie chipset) from other international GT-N7100's. if so, what does
samsung mean by an international version?
i think the problem is on my end because other posters have said they loaded
same rom's OK.
any advice would be appreciated. im trying to upgrade to the 5.0+ OS's
because the new API's contained therein would open up the full manual camera
setting controls on the note 2...provided thru various apps that require 5.0+
android releases. granted, the note 2 camera wouldn't stop a clock, but it's
the phone i have. now. i like photograghy.
rather than buy a note 5 for $600, im trying to get these above rom's to
install. thanks all.
noted: im also looking into buy a nice camera for $600 that would take better
pics than a new phone: just pls help me with the above problem.