Using Galaxy Nexus ToolKit v3.0, I have unlocked my GNex, flashed CWM and was attempting to flash CM9 KANG when all hell broke loose.
I have wiped all data and trying to get stock 4.0.2 back on here, eventually trying to get to CM9 KANG.
Willing to slide $25 to someone who can work with me to get a working phone again.
PM me or email me at gmail.com.
Did you flash the "toro/mysid" version of CM9?
Wiping Data consists of: factory, cache, dalvik.
The file name was "update-cm-9.0.0-RC0-GN-CDMA-KANG-01082012-signed.zip". I got the file from the CDMA specific GNex forum.
I just attempted to flash stock image 4.0.2 again (I did nothing different than the previous 50 attempts), and when it was finished it rebooted on it's own (again, something it hasn't done in the previous 50 or so attempts.
Now I'm boot looped on the startup animation. So maybe one step further than I was 20 minutes ago.
mtoomey79 said:
The file name was "update-cm-9.0.0-RC0-GN-CDMA-KANG-01082012-signed.zip". I got the file from the CDMA specific GNex forum.
I just attempted to flash stock image 4.0.2 again (I did nothing different than the previous 50 attempts), and when it was finished it rebooted on it's own (again, something it hasn't done in the previous 50 or so attempts.
Now I'm boot looped on the startup animation. So maybe one step further than I was 20 minutes ago.
Click to expand...
Click to collapse
So what are you wanting to do? Return to stock? Flash another ROM?
I don't know what I just did, but it now just boot to stock and has the stock welcome screen.
Now, how can I safely (and sanely) get the CM9 KANG?
mtoomey79 said:
I don't know what I just did, but it now just boot to stock and has the stock welcome screen.
Now, how can I safely (and sanely) get the CM9 KANG?
Click to expand...
Click to collapse
Note that CM9 is still in early development. It doesn't have your everyday CM features, I personally use another ROM but I'm sure CM9 is functional.
Get the latest http://fitsnugly.euroskank.com/skankwich/toro/ (You're going to need gapps as well)
You're able to get into bootloader mode, recovery mode just fine correct?
Have Clockwork Recovery installed as well?
Edit: here are the gapps, http://www.mediafire.com/download.php?ak6g0f0l9joh1n1
Problem solved.
Thanks zephiK!
Hello everyone,
First of all my problem. Since about 2 weeks I started getting random crashes. The phone is unresponsive and the screen goes from really bright to a greenish/grey color (hard to explain). I googled but I didn't find an answer. If anyone here knows the problem that'd be great but I doubt it since there are so many this that could cause this. So now my question is, how can I be certain it's not an software issue? Further info: My phone is rooted, and I didn't change the ROM. However, I don't actually have root permissions and when I open SuperSU it asks me to update the binary which always fails. I tried to Root it again with the Galaxy Toolkit and it says it's already rooted. Also, Under the google logo is a unlocked lock sign.
Thanks
I would recommend you to try some custom stable ROM, based on 4.1.2. CM, AOKP are among top ones.
better make a backup using recovery, and flash a new ROM. It will give you a fresh start with SU too.
If you dont like using a custom ROM, restore an earlier backup if you already have..
marcusabu said:
Hello everyone,
First of all my problem. Since about 2 weeks I started getting random crashes. The phone is unresponsive and the screen goes from really bright to a greenish/grey color (hard to explain). I googled but I didn't find an answer. If anyone here knows the problem that'd be great but I doubt it since there are so many this that could cause this. So now my question is, how can I be certain it's not an software issue? Further info: My phone is rooted, and I didn't change the ROM. However, I don't actually have root permissions and when I open SuperSU it asks me to update the binary which always fails. I tried to Root it again with the Galaxy Toolkit and it says it's already rooted. Also, Under the google logo is a unlocked lock sign.
Thanks
Click to expand...
Click to collapse
ahsanali.pk said:
I would recommend you to try some custom stable ROM, based on 4.1.2. CM, AOKP are among top ones.
better make a backup using recovery, and flash a new ROM. It will give you a fresh start with SU too.
If you dont like using a custom ROM, restore an earlier backup if you already have..
Click to expand...
Click to collapse
My only expercience with custom roms got me into a boot loop, so I don't prefere that. I actually want a "out-of-the-box" phone without any modifications. Therefore I tried a factory reset but that keeps the root and unlock.
marcusabu said:
My only expercience with custom roms got me into a boot loop, so I don't prefere that. I actually want a "out-of-the-box" phone without any modifications. Therefore I tried a factory reset but that keeps the root and unlock.
Click to expand...
Click to collapse
ok, if you want to get the total old look, relock the bootloader, and install official GNex image that comes straight from Google. Hope this sorts the issue out.
Yes, Custom ROMs are a bit time taking to setup in the start, but thats the whole point - a lot of options. I flashed alot of ROMs and luckily, I have had no boot issue still. I think following the proper instructions(which are simply wiping and formatting data, cache, and dalvik) are easily gonna keep the boot loops away.
You can rule out a sw issue by starting fresh.
http://forum.xda-developers.com/showthread.php?t=1626895
Sent from my i9250
Hi.
My son's Galaxy Nexus (Verizon) is having some serious issues. HE has been crack flashing everything under the son (Just like his data) and recently he tried a 4.3 rom (Not sure which one). He started to get random crashes so he flashed back to one of the 4.2.2 rom. Then the phone started crashing all the time so I hooked it up the the Nexus toolkit (I assume it is the one everyone uses) and decided to do a full wipe. The phone was basically two folders and would not boot past the Google logo.
When I hooked it up to the tool kit software it was recognized and I flashed the stock (VZ) rom, no root. When I booted the phone it would go to the start screen looking for WiFi and when I tried to go through the start up process the phone would lock up and reboot. I cannot get past this point to do any troubleshooting.
So is this a hardware issue (The phone is toast) or am I missing something as far as doing a complete wipe to get back to bone stock?
Thank you for your help. (I have as well as my son have been trolling this site and others looking for answers but since I can boot up most did not apply, I think)
mlfca said:
Hi.
My son's Galaxy Nexus (Verizon) is having some serious issues. HE has been crack flashing everything under the son (Just like his data) and recently he tried a 4.3 rom (Not sure which one). He started to get random crashes so he flashed back to one of the 4.2.2 rom. Then the phone started crashing all the time so I hooked it up the the Nexus toolkit (I assume it is the one everyone uses) and decided to do a full wipe. The phone was basically two folders and would not boot past the Google logo.
When I hooked it up to the tool kit software it was recognized and I flashed the stock (VZ) rom, no root. When I booted the phone it would go to the start screen looking for WiFi and when I tried to go through the start up process the phone would lock up and reboot. I cannot get past this point to do any troubleshooting.
So is this a hardware issue (The phone is toast) or am I missing something as far as doing a complete wipe to get back to bone stock?
Thank you for your help. (I have as well as my son have been trolling this site and others looking for answers but since I can boot up most did not apply, I think)
Click to expand...
Click to collapse
Right off the bat, do NOT use toolkits anymore. Please. You need to learn how to use Fastboot.
The best thing to do is start completely fresh. Download latest Galaxy Nexus factory images and fastboot them.
If you have no idea how to use fastboot, I suggest going to this thread and reading up my man: [GUIDE]New To Adb And Fastboot Guide
Any other questions or help I can gladly answer.
Hello guys, this is the first time I am posting anything so if I am doing anything wrong, sorry just say what it was and I will try to correct it. Well due to some unfortunate events I needed to get my GSM Galaxy nexus running again, I rooted it a long time ago when I was trying to get into roms and mods, but I had to leave that aside due to some other projects that demanded a little more attention at the time. Since my device was having some battery problems I thought that by updating it the problem could be fixed, at the time it was running CyanogenMod 10.2.1 if my memory is right. I went into the update tab under settings in the phone itself and tried installing CM11 from there. the phone prompted me if I would like to do it and I hit yes, it booted into CWM and it proceeded with the installation. But then it gave the status 7 error and the instalation could not be completed (from what I've read this problem happens when the device is not the one compatible with the Rom being installed, I went in the script and checked it, but it was maguro the same I had used for some time , since my device is a GALAXY NEXUS GSM model. Well I went to bootloader again and then do CWM and found the Rom I was using earlier (the CM 10.2), I flashed it and it was all "nice" and working but the battery was discharging way too fast and I tried it again but this time, for some reason (some times I do stupid things) I deleted some folders from the inumerous 0/ folders my device was accumulating and the CM 10.2 was among them. After I that I tried flashing another CM 11 Rom, an older one to try and see if it went well. sigh.... It did not. The same problem occured and now I cannot flash the working Rom. The Phone boots but it does not get past the google logo and then turns off and boots again going directly into CWM , I tried using Wug Fresh's Nexus Root Tollkit, but since I can't go into the settings of my phone I can't configure the drivers properly and if I try to use the Flash Stock + Unroot option with soft-Bricked/Bootloop option checked it returns that a fastboot device was not found. And hence I can't do anything else. Well I don't know what to do and my knwoledge is fairly limited, so anything can help. I have already searched some solution in other treads but none have given results. Does anyone can guide me where to look or some thing I should do?
Thank you very much for any time spent helping.
Hi,
I will have your thread moved to your device section so the experts who own your device can help.
Good luck!
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