Related
Hi everybody,
I'm relatively new to ROMs and I think I've made a mistake. I rooted my phone with CASUAL (because I'm a noob like that), and after about of week of playing around with my new features I decided to try and get a new ROM, CyanogenMod 10.1. I followed a video guide on youtube called "How to install CyanogenMod 10.1 Android 4.2.2 Jelly Bean on the Samsung Galaxy S III/3" (can't post links) and used GooManager to flash the ROM over. The phone rebooted and it took me to a teamwin loading screen followed by a menu with 8 options. I thought it was weird, as it wasn't in the video, but one of the options was "install" so I clicked that, it showed the .zip for the ROM so I hit "flash". It rebooted again now and now continuously displays the spinning loading screen for CyanogenMod. I remember reading something something about CM 10 not working with ICS bootloaders, but all of the guides I read about flashing CM made no mention of it, so I didn't think much of it. Is this my problem?
I made a ROM backup with CWM Recovery, app and data backups with Titanium root, and even backed up my EFS folder, so I'm not worried about any data loss involved in a factory wipe or reset, but I need help getting there. I've read things about a USB jig, is this what I need to do? If so, , do I just need to make/buy and plug in the jig? What do I do afterwards?
Any and all help will be appreciated
uberchinchillaz said:
Hi everybody,
I'm relatively new to ROMs and I think I've made a mistake. I rooted my phone with CASUAL (because I'm a noob like that), and after about of week of playing around with my new features I decided to try and get a new ROM, CyanogenMod 10.1. I followed a video guide on youtube called "How to install CyanogenMod 10.1 Android 4.2.2 Jelly Bean on the Samsung Galaxy S III/3" (can't post links) and used GooManager to flash the ROM over. The phone rebooted and it took me to a teamwin loading screen followed by a menu with 8 options. I thought it was weird, as it wasn't in the video, but one of the options was "install" so I clicked that, it showed the .zip for the ROM so I hit "flash". It rebooted again now and now continuously displays the spinning loading screen for CyanogenMod. I remember reading something something about CM 10 not working with ICS bootloaders, but all of the guides I read about flashing CM made no mention of it, so I didn't think much of it. Is this my problem?
I made a ROM backup with CWM Recovery, app and data backups with Titanium root, and even backed up my EFS folder, so I'm not worried about any data loss involved in a factory wipe or reset, but I need help getting there. I've read things about a USB jig, is this what I need to do? If so, , do I just need to make/buy and plug in the jig? What do I do afterwards?
Any and all help will be appreciated
Click to expand...
Click to collapse
If it does anything it isn't a hard brick. Never use rom manager or goo manager to flash something. That is a sure fire way to kill your phone.
If it was an out of date boot loader it wouldn't have flashed.
By the sounds of if your bootloop is from not wiping.
Go here
http://forum.xda-developers.com/showthread.php?p=38838122
Everything you need to know is there. Pay close attention to step 5a it's proper wiping for twrp. Re wipe, re flash and you'll be fine. Don't forget to flash the gappps. Those videos are good and bad. Especially if you have no idea what you're doing it's a real fast way to a brick.
Sent from my SGH-I747 using xda app-developers app
Hi there guys of XDA,
I have a major problem with my NOTE 2, after playing around with some ROMs, Cyanogenmod 11 4.4 NIGHTLY, 10.2 4.3 and Omni 4.4.1 NIGHTLY. I used CWM to load these ROMs with SUPERsu?. This is the first time i have flashed any ROMs onto my phone.
CM 11 was the first ROM i flashed on my NOTE 2 and that's when it started it couldn't detect my sim, It doesn't show me my IMEI number and my Baseband version. I didn't make a back-up of the stock because i didn't need one.
Now i'm stuck with a phone i can only use on Wifi is there anyone that can help? or if its happened to someone else? how did you sort it out?
Also can i restore this through KIES?
shirazi15 said:
Hi there guys of XDA,
I have a major problem with my NOTE 2, after playing around with some ROMs, Cyanogenmod 11 4.4 NIGHTLY, 10.2 4.3 and Omni 4.4.1 NIGHTLY. I used CWM to load these ROMs with SUPERsu?. This is the first time i have flashed any ROMs onto my phone.
CM 11 was the first ROM i flashed on my NOTE 2 and that's when it started it couldn't detect my sim, It doesn't show me my IMEI number and my Baseband version. I didn't make a back-up of the stock because i didn't need one.
Now i'm stuck with a phone i can only use on Wifi is there anyone that can help? or if its happened to someone else? how did you sort it out?
Also can i restore this through KIES?
Click to expand...
Click to collapse
I had this exact issue last week when flashing Kitkat AOSP ROM. Even restoring back to 4.3.1 no network connection was available, except for WiFi. Restoring your EFS will not even work. You just have to re-root your phone.
Not to worry, your phone is OK, perfectly OK. But just quite a bit of work needs to be done. Here: http://forum.xda-developers.com/showthread.php?t=2032849
1. Download original stock firmware for your country and telco
2. Download mode that firmware back to your phone using Odin
3. Download mode to install recovery, this will re-root your phone above steps will un-root your phone
4. Re-flash ROM of your choice, not Kitkat for now
After all i've gone through, and as much as i want to try Kitkat, i think this issue is recovery-related. Both TWRP and CWM needs updating for Android 4.4. I will wait until then.
All the best!
Gandicela said:
I had this exact issue last week when flashing Kitkat AOSP ROM. Even restoring back to 4.3.1 no network connection was available, except for WiFi. Restoring your EFS will not even work. You just have to re-root your phone.
Not to worry, your phone is OK, perfectly OK. But just quite a bit of work needs to be done. Here: http://forum.xda-developers.com/showthread.php?t=2032849
1. Download original stock firmware for your country and telco
2. Download mode that firmware back to your phone using Odin
3. Download mode to install recovery, this will re-root your phone above steps will un-root your phone
4. Re-flash ROM of your choice, not Kitkat for now
After all i've gone through, and as much as i want to try Kitkat, i think this issue is recovery-related. Both TWRP and CWM needs updating for Android 4.4. I will wait until then.
All the best!
Click to expand...
Click to collapse
Thanx for getting back to me at least someone can help. After i followed the things you told me to do. It didn't put the stock ROM back on there so i'm stuck with omni.
After Odin loaded everything to the phone it just keeps going into recovery mode? is that normal or am i doing it wrong because the link you posted up doesn't mention anything about that :-s and i followed everything that link said to do.
shirazi15 said:
Thanx for getting back to me at least someone can help. After i followed the things you told me to do. It didn't put the stock ROM back on there so i'm stuck with omni.
After Odin loaded everything to the phone it just keeps going into recovery mode? is that normal or am i doing it wrong because the link you posted up doesn't mention anything about that :-s and i followed everything that link said to do.
Click to expand...
Click to collapse
Mate, firstly this is the hard way of recovering from "Unknown Baseband" issue. Finally the simple solution was only to download and install an app called SELinux Mode Changer from PlayStore. Then using that app, change SELinux from Enforcing to Permissive resolved everything related to IMEI, EFS, and Unknown Baseband. So hard way I did; i didn't know any better then.
By the way the link is correct. Start from the procedure from the line that says "Installation Instruction [Mobile odin is now have support for NOTE2]"
You must be in download mode (Vol Down, Home, & Power button all pressed together) to flash the Stock ROM using Odin. But where is your status now? If in recovery, can you re-install a ROM? If u r able to reboot back up to OMNI, just install the SELinux app and u will be good to go.
Cheers!
shirazi15 said:
Hi there guys of XDA,
I have a major problem with my NOTE 2, after playing around with some ROMs, Cyanogenmod 11 4.4 NIGHTLY, 10.2 4.3 and Omni 4.4.1 NIGHTLY. I used CWM to load these ROMs with SUPERsu?. This is the first time i have flashed any ROMs onto my phone.
CM 11 was the first ROM i flashed on my NOTE 2 and that's when it started it couldn't detect my sim, It doesn't show me my IMEI number and my Baseband version. I didn't make a back-up of the stock because i didn't need one.
Now i'm stuck with a phone i can only use on Wifi is there anyone that can help? or if its happened to someone else? how did you sort it out?
Also can i restore this through KIES?
Click to expand...
Click to collapse
can you try what i did? http://forum.xda-developers.com/showthread.php?t=2567862&nocache=1
good luck.
"Just sharing my experience in solving this issue. Hopefully it will help solve those who have similar issues.
I flashed a file which messed up my EFS partition. I had a backup and tried to use the available programs to restore my EFS using my backup. None worked. I even brought it to the samsung store, but they said they would change the motherboard and reprogram, and replacement and service would cost more than half the cost of a new N7105. I purchased the phone in another country. The people who had stores to repair phones gave up on my phone. They also offered to replace the motherboard for US$175.00.
My phone was originally under a DMB2 rom (from Singapore I think). I flashed a DMC3 rom, and used this for five months, until i encountered the problem.
I initially gave up and got a note 3. But i could not believe the phone was junk and people in XDA (as I observed) do not seem to give up.
After two weeks, i found the solution below, which brought my phone to working condition.
1. I flashed the stock rom N7105ZHDMI2_N7105ZZHDMI2_TGY from sammobile.
2. I flashed a pit file using Odin. The pit file is found here:
http://forum.xda-developers.com/show....php?t=2137008
This restored the baseband. But IMEI was no longer NULL. However, it was still 0.
3. I downloaded and used the EFS Pro from this link:
http://forum.xda-developers.com/show....php?t=1308546
Before using EFS Pro, make sure you dial *#7284# and change the setting of Qualcomm USB Settings to
"RMNET + DM + MODEM"
I will not hurt your phone if you do, but EFS Pro will just not work. If you don't do this, the EFS Pro will display "Phone not responding" or something similar.
NOTE: I couldn't find the option with RMNET, but i used the option that also had an "RM*** + DM + MODEM".
After the phone is read, change back the IMEI to what it was originally.
Dial *#7284# again to change back to "MTP+ADB".
It's all working now.
Hope this is able to help someone. Now i have two working versions of Note.
Thanks to the authors of the program i used, and the people who uploaded the files used.
Cheers!
shirazi15 said:
Thanx for getting back to me at least someone can help. After i followed the things you told me to do. It didn't put the stock ROM back on there so i'm stuck with omni.
After Odin loaded everything to the phone it just keeps going into recovery mode? is that normal or am i doing it wrong because the link you posted up doesn't mention anything about that :-s and i followed everything that link said to do.
Click to expand...
Click to collapse
karlonicolas said:
can you try what i did? http://forum.xda-developers.com/showthread.php?t=2567862&nocache=1
good luck.
"Just sharing my experience in solving this issue. Hopefully it will help solve those who have similar issues.
I flashed a file which messed up my EFS partition. I had a backup and tried to use the available programs to restore my EFS using my backup. None worked. I even brought it to the samsung store, but they said they would change the motherboard and reprogram, and replacement and service would cost more than half the cost of a new N7105. I purchased the phone in another country. The people who had stores to repair phones gave up on my phone. They also offered to replace the motherboard for US$175.00.
My phone was originally under a DMB2 rom (from Singapore I think). I flashed a DMC3 rom, and used this for five months, until i encountered the problem.
I initially gave up and got a note 3. But i could not believe the phone was junk and people in XDA (as I observed) do not seem to give up.
After two weeks, i found the solution below, which brought my phone to working condition.
1. I flashed the stock rom N7105ZHDMI2_N7105ZZHDMI2_TGY from sammobile.
2. I flashed a pit file using Odin. The pit file is found here:
http://forum.xda-developers.com/show....php?t=2137008
This restored the baseband. But IMEI was no longer NULL. However, it was still 0.
3. I downloaded and used the EFS Pro from this link:
http://forum.xda-developers.com/show....php?t=1308546
Before using EFS Pro, make sure you dial *#7284# and change the setting of Qualcomm USB Settings to
"RMNET + DM + MODEM"
I will not hurt your phone if you do, but EFS Pro will just not work. If you don't do this, the EFS Pro will display "Phone not responding" or something similar.
NOTE: I couldn't find the option with RMNET, but i used the option that also had an "RM*** + DM + MODEM".
After the phone is read, change back the IMEI to what it was originally.
Dial *#7284# again to change back to "MTP+ADB".
It's all working now.
Hope this is able to help someone. Now i have two working versions of Note.
Thanks to the authors of the program i used, and the people who uploaded the files used.
Cheers!
Click to expand...
Click to collapse
Nice, thanks!
For all others that might face "unknown baseband" with 4.3 to 4.4 flashing of ROMS, SELinux Mode Changer app from Playstore will fix that problem. Install the app and set SELinux from Enforcing to Permissive.
i hope your problem is fixed.
i'm not too familiar with CM roms, as i have been using stock since gingerbread. but you have to first do a full wipe before flashing from CM to stock. did you do that? perhaps you can go to recovery, do a full wipe, include Dalvik and Cache. Then go to bootloader and flash your rom.
by the way, my chipset is qualcomm yours may be exynos. if so, then i'm not confident about this solution because i have tried this several times, but only on note 2 LTE.
good luck!
Hey guys!
I know the title of my new thread is probably something that's already been covered, but I feel my case is somewhat... special.
I have an AT&T Samsung Galaxy S III that I got out a few days ago for my friend to use, and I decided the ole TouchWiz wasn't cutting it speed-wise. So, I tried CyanogenMod Installer to quickly and easily install CyanogenMod. While the beginning process went well, the end was a bit different than what was supposed to happen. At the end of the install, when the Installer said "Congrats!", my phone didn't boot up into CyanogenMod. It asked a few question that required me to either use the physical keys or touch to select, though the menu looked just like Recovery Mode with the stock ROM. It asked me weird questions, like "ROOT might need repairing. Repair now?". I just said no to all of them, and the phone booted straight into stock. I tried the Installer several more times after a fresh wipe on the phone, but to no avail. I then went online to research any easier root methods that I could use with this phone, and came across KingoRoot. It rooted my phone perfectly fine! I then tried to flash a custom ROM using ROM Manager from the Play Store, but it said I needed a recovery, and tried to flash one, but it didn't work. By this point, I was tired of fighting an obviously loosing battle, so I hooked it up to Kies to do a complete fresh install, no root. It went fine, until Kies was in the middle of installing the software...
... and puts my phone into Emergency Mode.
I've figured out that it can't boot into Recovery Mode or any OS, but it could boot into download mode. I tried Emergency firmware recovery via Kies, but it didn't work. I also tried re-flashing stock OS using Odin, with a FAIL! message each time.
Can this be fixed? I'm running out of options here. Thanks.
What bootloader or Samsung ROM version was on your phone?
Download the latest tar.md5 version of Philz Touch recovery from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Download the latest cm11 for the d2lte from here: https://download.cyanogenmod.org/?device=d2lte. Save cm11 to an external SD card.
Download the Gapps from here: http://wiki.cyanogenmod.org/w/Google_Apps. Save the Gapps file to the external SD card. Place the SD card into the phone.
Boot the phone into download mode, uncheck everything in Odin except f.reset time. Connect the phone and flash Philz. When you see the word "reset" in the status window, remove the USB cable, remove the battery, replace the battery, boot into recovery, wipe data, cache, system, and Dalvik. Flash CM11, flash Gapps, boot phone.
I hope you get this solved, I personly have never seen this mode
Sent from my Nexus 7 using Tapatalk
It worked!
Thank you. I was getting really worried, but now it runs perfectly!
Sorry this respose was so late. I've been busy.
Which method worked? Let us know because it may benefit other users.
The exact method you posted. I did try the d2att Cyanogenmod version, but only d2lte worked.
indecisiveOS said:
The exact method you posted. I did try the d2att Cyanogenmod version, but only d2lte worked.
Click to expand...
Click to collapse
Before unification, there were separate builds for the ATT s3 (d2att) and Bell s3 (d2can). Unified builds for both phone versions are now developed under the d2lte label.
Oh, okay. That explains why d2att didn't work with my AT&T device, lol. I just assumed you were thinking of another build when you were typing the first response, so I just tried d2att first, only to realize that d2lte was the appropriate file.
Sent from my iPhone using Tapatalk
I don't have a d2att, I used to have the Bell version of the s3 (d2can). I haven't had an s3 for over 18 months!
I recommended the d2att hoping it would work on your phone.
Wow! I got my S3 as a Christmas gift of 2012. I use an iPhone now (gasp - iPhone user on XDA?!) but I sometimes dust off some of my older electronics for random purposes. I live in the U.S., so all my phones and electronics are highly subsidized, bloated, branded, and locked to whatever carrier/manufacturer. But I sure do miss my Galaxy. I made myself try an iPhone, and the experience just wasn't as exciting. The iPhone isn't loaded with carrier "goodies", which I like, but I just miss the experience. I just miss the old days.
I also had an iPhone 6 for a few days and didn't find it to my liking. I prefer the ability to customize the look of my ROM; however, apps on the iPhone just work, unlike some of the Play store apps due to several subtle variations of the OS.
I like the stability of the iPhone, but I love the customization, design elements, and nifty features of Android. Oh, and how could I ever forget my wonderful back and menu keys? But both do have their drawbacks. I just wish there was an OS that just worked, but could be personalized. But that'd be asking for world peace, too.
indecisiveOS said:
I like the stability of the iPhone, but I love the customization, design elements, and nifty features of Android. Oh, and how could I ever forget my wonderful back and menu keys? But both do have their drawbacks. I just wish there was an OS that just worked, but could be personalized. But that'd be asking for world peace, too.
Click to expand...
Click to collapse
The first link doesn't seem to work any more? Is there a new site to download Philz Recovery? Thanks.
lajeune69 said:
The first link doesn't seem to work any more? Is there a new site to download Philz Recovery? Thanks.
Click to expand...
Click to collapse
I think that was just a temporary URL shortener that only lasted for a little while.
indecisiveOS said:
I think that was just a temporary URL shortener that only lasted for a little while.
Click to expand...
Click to collapse
Goo is down.
lajeune69 said:
Goo is down.
Click to expand...
Click to collapse
Oh, really? I just thought it had a timestamp or something. My apologies. I clicked that link forever ago, but I think I still have the file. I can put it on a file sharing website later today. I'll share the link later.
You could also install the touch version of cwm from here: https://www.clockworkmod.com/rommanager
I think I'm screwed. I'm in a Cyrogenmod boot loop and nothing seems to work. I flash recoveries with Odin but it just goes back to the Cyrogenmod boot loop.
lajeune69 said:
I think I'm screwed. I'm in a Cyrogenmod boot loop and nothing seems to work. I flash recoveries with Odin but it just goes back to the Cyrogenmod boot loop.
Click to expand...
Click to collapse
That doesn't sound good. Can it boot into Recovery or Download mode?
I can get to download mode but my computer doesn't see it.
So I wanted to root this tablet, and I used a video online to help me do so.
I installed the USB drivers, got Odin 3, and loaded in CF_AutoRoot_Port_T700_BeansTown106.tar
It rooted my tablet and I was pretty happy about that. I then had update supersu, by getting the SU binaries.
So I came to this site and downloaded the recommended Supersu, and flashed it. It fixed that.
Well, then I wanted to get a custom ROM, so I flashed the Cyanogenmod 12, along with the component with it.
I found I didn't like it compared to my 5.0.2 Lolipop, and so I tried finding the stock ROM.
The gator download site everyone was showing refused to let me download anything, and just about all the ROMS seemed like they were from countries other than the U.S.
I searched for awhile, found nothing, then found a ROM called the Ironman Lolipop ROM, it was close enough to stock, so I flashed it.
Suddenly everything was normal, but then supersu needed binaries again, and after I flashed it again, it just stopped asking if it should grant permission, making the root useless.
Frustrated, I looked online again for ROMS, found a Canada one, decided to download, it would take two hours.
Well I'm not from Canada so I doubted it would work, and didn't want to wait two hours.
I decided to Flash back the Cyanogen.
Well unfortunately I went in and found out that I had deleted it earlier, whoops. And so my data wipe brought me back to Ironman ROM.
So, thinking that flashing to Iron Man screwed up my root I tried to re-root with Odin, the same way as the first.
It then had trouble booting, and when it did, it hung at the Samsung logo.
Now I've been stuck on this logo for about an hour, I can't turn it off. I'm assuming the only way to is to wait for it to run out of power.
I have been using TWRP this whole time.
I twice have backed up, and wiped data.
When I hit restore I saw no backups though, I'm not sure if they were for the ROM?
I don't know, I only have a year of experience.
Edit: I have an 8.1" T700 from Amazon.
pennylessz said:
So I wanted to root this tablet, and I used a video online to help me do so.
I installed the USB drivers, got Odin 3, and loaded in CF_AutoRoot_Port_T700_BeansTown106.tar
It rooted my tablet and I was pretty happy about that. I then had update supersu, by getting the SU binaries.
So I came to this site and downloaded the recommended Supersu, and flashed it. It fixed that.
Bla bla ......
Click to expand...
Click to collapse
Hi! To force reboot while in a soft brick, press and hold power+home button+ both volume buttons all at the same time.
Then when the screen goes black, quickly press the odin\download mode button combo or recovery comba if you wish.
Luckily, I have mirrored the latest firmware for the T700 to a faster hosting site. This is an UK firmware and is the latest one. It should flash fine as I have flashed different firmwares from different countries many times.
Download Firmware (fast download): https://www.androidfilehost.com/?fid=24052804347761130
Now, ironrom has problems with root sometimes. When I make roms I don't preroot them as they cause problems of binaries if you preroot them. Anyway feel free to flash the firmware with odin or load an custom ROM to your sd card and flash it.
Hope this helps!
DUHAsianSKILLZ said:
Hi! To force reboot while in a soft brick, press and hold power+home button+ both volume buttons all at the same time.
Then when the screen goes black, quickly press the odin\download mode button combo or recovery comba if you wish.
Luckily, I have mirrored the latest firmware for the T700 to a faster hosting site. This is an UK firmware and is the latest one. It should flash fine as I have flashed different firmwares from different countries many times.
Download Firmware (fast download):
Now, ironrom has problems with root sometimes. When I make roms I don't preroot them as they cause problems of binaries if you preroot them. Anyway feel free to flash the firmware with odin or load an custom ROM to your sd card and flash it.
Hope this helps!
Click to expand...
Click to collapse
Thank you for getting me out of the brick and back to stock.
However going into Supersu it says.
"There is no SU binary installed, and SuperSu cannot install it. This is a problem!
If you just upgraded to Android 5.0, you need to manually re-root- consult the relevant forums for your device!"
My question is, can I properly re-root it the way I had been?
I'm assuming if it soft bricks again I can just reinstall a stock ROM again.
Also all these ROMS and backups take up a lot of space, how would I go about deleting those when I'm done?
pennylessz said:
Thank you for getting me out of the brick and back to stock.
However going into Supersu it says.
"There is no SU binary installed, and SuperSu cannot install it. This is a problem!
If you just upgraded to Android 5.0, you need to manually re-root- consult the relevant forums for your device!"
My question is, can I properly re-root it the way I had been?
I'm assuming if it soft bricks again I can just reinstall a stock ROM again.
Also all these ROMS and backups take up a lot of space, how would I go about deleting those when I'm done?
Click to expand...
Click to collapse
In my files app, look for an folder called TWRP. Your backups are in there. To root simply install twrp and follow the twrp method to root. http://forum.xda-developers.com/showthread.php?p=59638836
You can delete your backups from within twrp. Just select restore, then the backup, then delete.
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