Won't boot up after flashing CM12 or CM13 - Moto E Q&A, Help & Troubleshooting

So I've never had to post anything before as everything I need to find is already here but this one has got me befuddled. I rooted my Moto E (1st gen) and installed clockwork mod recovery. First I installed cm13 to see what 6.0 looks like and it seem to install just fine from cwmod and then I rebooted saw the nice cmMod bootup animation and waited and waited. I got nervous so I looked up a couple Youtube videos and it looks like it can take up to 20 minutes. OK, no big deal as its a pretty low powered phone. Two hours later, I'm in the same place with the boot animation. I eventually just turned it off and restored it back to the factory image without issue. I then attempted to flash cm12 on it and had the same result. Any help or insight is appreciated.

That happened to me the first time you install cm , also I was nervous but I happened to install a custom kernel to see if it worked and it worked !!! if you do not work for you

hetor99 said:
That happened to me the first time you install cm , also I was nervous but I happened to install a custom kernel to see if it worked and it worked !!! if you do not work for you
Click to expand...
Click to collapse
So. how did you fix it? I'm not quite sure what you're trying to say.

sasquatch606 said:
So I've never had to post anything before as everything I need to find is already here but this one has got me befuddled. I rooted my Moto E (1st gen) and installed clockwork mod recovery. First I installed cm13 to see what 6.0 looks like and it seem to install just fine from cwmod and then I rebooted saw the nice cmMod bootup animation and waited and waited. I got nervous so I looked up a couple Youtube videos and it looks like it can take up to 20 minutes. OK, no big deal as its a pretty low powered phone. Two hours later, I'm in the same place with the boot animation. I eventually just turned it off and restored it back to the factory image without issue. I then attempted to flash cm12 on it and had the same result. Any help or insight is appreciated.
Click to expand...
Click to collapse
hey, it's a common problem and don't worry it can be easily solved...
you just need to flash cm11 (you can easily find it here - by percy_g2), you don't have to flash KitKat gapps. flash cm11, let it boot for the first time, once it boots, just reboot to recovery,wipe everything (except internal storage and sdcard ofcourse ) flash cm12 (of course with lollipop gapps) or cm13 (with marshmallow gapps) and the rom will boot just fine.. it'll take some time for the first boot (because android now use ART runtime), but it'll boot,
just for the record gapps must be flashed right after the rom. use opengapps....
and last but not the least - use latest TWRP 2.8.7.0 (ofcourse - can also be found on xda) since many roms doesn't support CWM nowadays
and just for the info, once you flash cm11 and let it boot, you won't need to do that again, you can flash any rom after that anytime, ofcourse unless you WANT to use cm11

booo159159 said:
hey, it's a common problem and don't worry it can be easily solved...
you just need to flash cm11 (you can easily find it here - by percy_g2), you don't have to flash KitKat gapps. flash cm11, let it boot for the first time, once it boots, just reboot to recovery,wipe everything (except internal storage and sdcard ofcourse ) flash cm12 (of course with lollipop gapps) or cm13 (with marshmallow gapps) and the rom will boot just fine.. it'll take some time for the first boot (because android now use ART runtime), but it'll boot,
just for the record gapps must be flashed right after the rom. use opengapps....
and last but not the least - use latest TWRP 2.8.7.0 (ofcourse - can also be found on xda) since many roms doesn't support CWM nowadays
and just for the info, once you flash cm11 and let it boot, you won't need to do that again, you can flash any rom after that anytime, ofcourse unless you WANT to use cm11
Click to expand...
Click to collapse
Thanks for this. I'll give it a go.

sasquatch606 said:
Thanks for this. I'll give it a go.
Click to expand...
Click to collapse
That worked. I'll honestly probably keep it at cm11 unless I can think of a real reason to upgrade. Thanks again!

In my case, I can't see anything in my screen.
sasquatch606 said:
So I've never had to post anything before as everything I need to find is already here but this one has got me befuddled. I rooted my Moto E (1st gen) and installed clockwork mod recovery. First I installed cm13 to see what 6.0 looks like and it seem to install just fine from cwmod and then I rebooted saw the nice cmMod bootup animation and waited and waited. I got nervous so I looked up a couple Youtube videos and it looks like it can take up to 20 minutes. OK, no big deal as its a pretty low powered phone. Two hours later, I'm in the same place with the boot animation. I eventually just turned it off and restored it back to the factory image without issue. I then attempted to flash cm12 on it and had the same result. Any help or insight is appreciated.
Click to expand...
Click to collapse
In my case, I can't even access the boot-loader in my mobile. May be very rare and bad situation in my case. I am not able to understand, what to do.

Related

[Q] Newly Androwook flashed Rom, stuck at intro crawl

Greetings
As the tittle points outs, I flashed the latest Androwook Rom(2.1) and it always stucks at the Intro Crawl. I re-downloaded it, flashed it again, but had had no success.
The Prime has been unlocked since May, and it was running the Cyanogen Nightly Rom, before I tried the Wook one. I wiped Cache and Delvik, and tried an older build as well with no success. I use the latest TWRP, 2.1.3. I also tried all availlable kernels and options during the installation with no success.
Can anyone give me a hint as to what is the problem? I can always go back to CM Rom, but I would feel like I accepted defeat.
Also, why does the installation always wipe my internal sd card , when no such option is selected?
drsane1984 said:
Greetings
As the tittle points outs, I flashed the latest Androwook Rom(2.1) and it always stucks at the Intro Crawl. I re-downloaded it, flashed it again, but had had no success.
The Prime has been unlocked since May, and it was running the Cyanogen Nightly Rom, before I tried the Wook one. I wiped Cache and Delvik, and tried an older build as well with no success. I use the latest TWRP, 2.1.3. I also tried all availlable kernels and options during the installation with no success.
Can anyone give me a hint as to what is the problem? I can always go back to CM Rom, but I would feel like I accepted defeat.
Also, why does the installation always wipe my internal sd card , when no such option is selected?
Click to expand...
Click to collapse
jumping from one rom to another needs a full wipe i guess... when you said wiping your internal sd card, that's the reason why you're stuck into crawling? so i guess you use adb to push the ROM, then flash again?
in my case, when i had a bootlop, i push fullwipe.zip first, flash it, then push Androwook.zip, then flash it... it all came back alive..
First of all, thank you for your reply!
Now, to adress each step
jumping from one rom to another needs a full wipe i guess.
Click to expand...
Click to collapse
Yup, did one (factory reset+system wipe) before trying to flash AW Rom.
when you said wiping your internal sd card, that's the reason why you're stuck into crawling? so i guess you use adb to push the ROM, then flash again?
Click to expand...
Click to collapse
After the first three unsuccessfull attempt to flash the ROM did I wipe my internal SD, so it isn't the crawling looping intro's problem. And yes, I push ROMs via Adb, and trying flashing.
in my case, when i had a bootlop, i push fullwipe.zip first, flash it, then push Androwook.zip, then flash it... it all came back alive..
Click to expand...
Click to collapse
That was actually the last step I tried before asking for help. Even after I typed this post, I did it again. Flashed it, pushed AW, and flashed again. No success.
*Edit: I have forgotten a primary Troubleshooting technique. Downloading AW2.1 from a different source, will update.
sorry but im not much of a help i can see... hope somebody could. don't lose hope though...
Intentions matter
Thanks for your time anyway!
After two more failed flashes, I got it to boot!
Apparently the starting animation was causing some kind of problem, which I cannot ever imagine. After I checked the option to have the uggly original boot animation, the rom booted normally and I am now using it.
I am quite happy to get it to work, but if anyone has any solution to the boot problem, I would be really glad to hear him!
drsane1984 said:
Intentions matter
Thanks for your time anyway!
After two more failed flashes, I got it to boot!
Apparently the starting animation was causing some kind of problem, which I cannot ever imagine. After I checked the option to have the uggly original boot animation, the rom booted normally and I am now using it.
I am quite happy to get it to work, but if anyone has any solution to the boot problem, I would be really glad to hear him!
Click to expand...
Click to collapse
Hello Everybody! Guys, sorry for my english!!!!!
First of all, I have to present myself, my name is Marco, I'm italian, 25 years old and I'm in the Android world since about 12 Years.
I started whit a Galaxy S2, and after I bought an Asus Transformer Prime.
After just two week, I decided to put in a Custom ROM, on my devices, and I understood how the system work better instead of a Stock ROM!
And after, I understood, how the XDA Developers Forum is important for me, and expecially for all the people who like to learn about the Android World.
So, I just want to Thanks with all of you for the support that i receive EVERY DAY to solve my problems!
One of these was with flashing the Androwook, weeks ago I flashed the Team EOS 2.0, that was really amazing, but after a While, I found some slowdowns in some action on the system, so i decided to try a rom based on the stock rom, but with improvement and tweaks, so what's better then the Androwook?
The problem was, the same explained on this post, after all wipes, the prime was not boot, and stuck in bootanimation!
I solved, checking the box "Install custom ROM" as drsane1984 have done, and now the ROM is booted perfectly!!
Thanks another time! I'am convinced that if you are able to seach, you'll find for sure the solution to your problems! If not, just ask!
Bye!

[Q] LS990 only boots into recovery

I'm using an LS990 that I've had since about when they came out. When Stumproot came out I rooted it, and I had installed the original TWRP Bump when that came out, but I've been running the rom it came with (ZV4 I believe, though I cannot check). Nothing had been unusual until today, when I put the phone in my pocket after using it for normal daily stuff, then when I later took it out it seemed to be in TWRP. I had almost never even booted into it on the G3 other than a very few times when I first installed it (I had been waiting for a CM12 that was stable enough for my liking).
No matter what I do, it seems to be stuck in recovery. I've updated to the latest TWRP (2.8.4.0) and that seemed to take just fine. However, when I try flashing a rom, it just flashes like normal, log says it's great, then....reboot takes me back into recovery. I tried the ZV4 base at first, then the ZV6 base, both with and without wiping all the appropriate partitions, but nothing seems to change. I am getting ready to try non-stock roms, but I thought I'd ask here first to see if anyone has any ideas? Any help much appreciated!
(not worried about my data, I had daily TB backups running which uploaded to Dropbox, so it's all saved, willing to wipe anything and everything)
Click "format data" under the "wipe" section this will wipe EVERYTHING so make sure you have the latest twrp then on your computer save a rom. Wipe the phone via twrp and then plug the phone it and wait for either Adb sideload or mtp. Personally I feel that mtp is the best just because you can move anything to your phone. Then just move the rom you want to the root of the sdcard (Every folder will be gone). Then flash it and hope that fixes it but if it dosent you may need to use the lg flash tool (windows) and flash the zv4 files. This will make you back on zv4 meaning restump root reflash twrp. The whole nine yards, just try the twrp thing first and if that dosen't work then do the flash tool. I am not responsible if you listen to me and your device breaks
bucketachicken said:
I'm using an LS990 that I've had since about when they came out. When Stumproot came out I rooted it, and I had installed the original TWRP Bump when that came out, but I've been running the rom it came with (ZV4 I believe, though I cannot check). Nothing had been unusual until today, when I put the phone in my pocket after using it for normal daily stuff, then when I later took it out it seemed to be in TWRP. I had almost never even booted into it on the G3 other than a very few times when I first installed it (I had been waiting for a CM12 that was stable enough for my liking).
No matter what I do, it seems to be stuck in recovery. I've updated to the latest TWRP (2.8.4.0) and that seemed to take just fine. However, when I try flashing a rom, it just flashes like normal, log says it's great, then....reboot takes me back into recovery. I tried the ZV4 base at first, then the ZV6 base, both with and without wiping all the appropriate partitions, but nothing seems to change. I am getting ready to try non-stock roms, but I thought I'd ask here first to see if anyone has any ideas? Any help much appreciated!
(not worried about my data, I had daily TB backups running which uploaded to Dropbox, so it's all saved, willing to wipe anything and everything)
Click to expand...
Click to collapse
Have you tried this?
http://forum.xda-developers.com/lg-...trying-ota-t2907508/post56061720#post56061720
Thanks, I did get it working. I have no idea how, but my data was all still there, despite wiping several times....but the recovery fix is what worked. I also got that lg flash tool setup so hopefully that will be helpful if I run into future problems. I honestly think after all that mess I may try the CM12 roms now, even if they still have some daily bugs, cause I was almost sad to see it boot back up into the LG stock rom...
Thanks again!
I honestly think after all that mess I may try the CM12 roms now, even if they still have some daily bugs, cause I was almost sad to see it boot back up into the LG stock rom...
Thanks again![/QUOTE]
Here is a cm12 rom that is almost perfic: http://forum.xda-developers.com/sprint-lg-g3/orig-development/cyanogenmod-12-beta-ls990-t2958197
It's the one I use everyday and I have seen almost no bugs

[Q] Rooted, but can't install custom recovery...

Ok, so I've rooted and put custom roms on numerous phones. I've been trying to put a custom recovery, twrp or cwm, whatever, on my wife's phone, but have got a wall. I know for sure, 100% that I am rooted. I tired to install twrp and cwm via their respective apps, ends up in either bootloop trying to boot into recovery (and FYI, the screen shows that a custom recovery is installed, just doesn't load into recovery and restarts). And tried both via Odin, but got the same result. Have never ran into this problem before with any of my phone's, all of the galaxy's and Galaxy Note's since the S2. Any help would be greatly appreciated. Thanks homies!
Just to add, yes I made sure double checked, triple checked that I was installing the correct recovery for the phone model. Also, she has done all the ota updates that sprint has pushed as of last week (2/9/15).
Psychotic-Cerebellum said:
Ok, so I've rooted and put custom roms on numerous phones. I've been trying to put a custom recovery, twrp or cwm, whatever, on my wife's phone, but have got a wall. I know for sure, 100% that I am rooted. I tired to install twrp and cwm via their respective apps, ends up in either bootloop trying to boot into recovery (and FYI, the screen shows that a custom recovery is installed, just doesn't load into recovery and restarts). And tried both via Odin, but got the same result. Have never ran into this problem before with any of my phone's, all of the galaxy's and Galaxy Note's since the S2. Any help would be greatly appreciated. Thanks homies!
Just to add, yes I made sure double checked, triple checked that I was installing the correct recovery for the phone model. Also, she has done all the ota updates that sprint has pushed as of last week (2/9/15).
Click to expand...
Click to collapse
OK, from your post it looks like you have done this before. To be sure lets go through the motions one more time.
Your device is updated to 4.4.4 NK4 the latest KitKat version. It's rooted you have supersu icon and run a root checker. First download again ( in case you got a bad download ) a copy of Philz CWM version 6.48.4 here is the link https://goo.im/devs/philz_touch/CWM_Advanced_Edition/hlte/ use "phil'z_touch_6.48.6-hlte.tar.md5" . I like to use odin version v1.85 it's little older but very stable, here is a link https://mega.co.nz/#!oA5xzTAL!LXoVWB...ZlOMSWdRGVX6Uo now flash the .tar file with odin. Make sure you let device boot up on it's own back to the OS, do not pull the cable and boot the device yourself. Then try and boot into recovery.
If it bootloops again, I would backup all your data to the PC desktop, and then do a factory reset get back to bone stock ( that means when your in download mode it says Samsung Official status not custom ) so many times I have seen folks with an unrooted device where the bootloader still says custom and you end up with a dirty flash or worse. It may take a couple factory resets to get back to stock, it doesn't always take the first time. When I flash a custom rom and then decide to go back to stock, I flash the rom two or three times to make sure I'm bone stock.
If the factory reset doesn't work you may have to flash a new stock NK4 OS. Then root again and install the recovery. Here is my thread with all the info you need http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 , Enjoy !!!
Thanks for taking the time to give me a detailed response. Sounds like I'm gonna have to wait till Wednesday or Thursday when im off work and have some time to do this, but yeah, I was thinking maybe just a factory reset, but I'll use your links and try it one more time first. I'll let ya know. Thanks again
Do you have another link to the older Odin (1.85).the link says the file isn't there... Thanks again
Never got to test it out, but she didn't really want a custom rom anyway, just the WiFi hotspot, and I finally found a method that works, big shout out to idone for his awesome app. If anyone else is looking for WiFi hotspot without root that sees this, check out his tread in the apps and themes, for this phone. Worked like a charm. Thanks again jimzweb1. Much appreciate the reply!
Psychotic-Cerebellum said:
Never got to test it out, but she didn't really want a custom rom anyway, just the WiFi hotspot, and I finally found a method that works, big shout out to idone for his awesome app. If anyone else is looking for WiFi hotspot without root that sees this, check out his tread in the apps and themes, for this phone. Worked like a charm. Thanks again jimzweb1. Much appreciate the reply!
Click to expand...
Click to collapse
Awesome, Ya idone is the man when it comes to enabling the mobile hotspot be careful what you click with app. I will correct that link. Thanks
Psychotic-Cerebellum said:
Ok, so I've rooted and put custom roms on numerous phones. I've been trying to put a custom recovery, twrp or cwm, whatever, on my wife's phone, but have got a wall. I know for sure, 100% that I am rooted. I tired to install twrp and cwm via their respective apps, ends up in either bootloop trying to boot into recovery (and FYI, the screen shows that a custom recovery is installed, just doesn't load into recovery and restarts). And tried both via Odin, but got the same result. Have never ran into this problem before with any of my phone's, all of the galaxy's and Galaxy Note's since the S2. Any help would be greatly appreciated. Thanks homies!
Just to add, yes I made sure double checked, triple checked that I was installing the correct recovery for the phone model. Also, she has done all the ota updates that sprint has pushed as of last week (2/9/15).
Click to expand...
Click to collapse
That's the problem Knox security is getting harder flash engineering boot loader again then try rashr in app store to flash philz

[Q] Can not reboot into recovery, only into download.

So I originally had issues with my S4 when it updated to 5.0 I got a new one from the inusrance company and i wanted to root and rom it right away. Well it took me a wile to root it, I had to find the right (or what I thought was the right) Kernel's to use. I rooted it finally with Towelroot, I then tried to install TWRP and reboot to recovery and load a Rom, however my phone will never reboot to recovery now. It will only reboot to download. TWRP does not seem to work and if I mess it with it it will reboot to download and it won't do anything ells until I use Odin to reinstall the Kernel. If I try the button combo to reboot to recovery it still reboots to download. So I think that keeps me from using SafeStrap as well.
I am at a loss, I just want to get the Hyperdrive+RLS21+KK+S4 Rom on my phone so I don't get the stupid 5.0 that ruins my phone. Is there anyone who can help me out with this? Also I did try to do a factory data reset and that did not work either as it just rebooted to download and I had to use Odin to load the Kernel again and it just rebooted to the same un-reset OS I was in.
Brad
Bshade said:
So I originally had issues with my S4 when it updated to 5.0 I got a new one from the inusrance company and i wanted to root and rom it right away. Well it took me a wile to root it, I had to find the right (or what I thought was the right) Kernel's to use. I rooted it finally with Towelroot, I then tried to install TWRP and reboot to recovery and load a Rom, however my phone will never reboot to recovery now. It will only reboot to download. TWRP does not seem to work and if I mess it with it it will reboot to download and it won't do anything ells until I use Odin to reinstall the Kernel. If I try the button combo to reboot to recovery it still reboots to download. So I think that keeps me from using SafeStrap as well.
I am at a loss, I just want to get the Hyperdrive+RLS21+KK+S4 Rom on my phone so I don't get the stupid 5.0 that ruins my phone. Is there anyone who can help me out with this? Also I did try to do a factory data reset and that did not work either as it just rebooted to download and I had to use Odin to load the Kernel again and it just rebooted to the same un-reset OS I was in.
Brad
Click to expand...
Click to collapse
You do know that OC1 is still locked down(5.0.1)?
No root, no downgrade, no ROMs, no safestrap. No TWRP unless you happen to have MDK(4.2 Jellybean)
You will have to flash a stock 5.0.1 ROM and life with it.
I had an S4 that did upgrade to OC1 I got a new S4 with my insurance that was not upgraded to OC1 it was still 4.4.2 NK1. I loaded the Kernel NC5 and used Towelroot then back to NK1 but I cant get TWRP to work and boot to recovery to flash the ROM it only boots to Download. I really want to ROM it so that it does not go back to OC1 as when it was OC1 on my old phone that I don't have it was useless, I could not make phone calls or install anything on the phone or it would just lock up and restart constantly.
I can not figure out why it won't boot to recovery, and why if I try to do a factory reset i have to reload the Kernel to make the phone work again.
Thanks,
Brad
THIS IS A TEST PROCESS!!
I just posted a set of service files to try and downgrade...I pretty sure it might work! [emoji14]
http://forum.xda-developers.com/galaxy-s4-verizon/help/testing-revert-to-nk1-t3124096
It Worked! now I just have to figure out how to re root I tried once with Towelroot and it did no work then tried to load the Kernel that Towelroot worked with and it got all bugy so i reloaded your Kernel and it was still bugy so I did the whole process over again and it worked a second time. LOL
Thanks so much,
Brad
Bshade said:
It Worked! now I just have to figure out how to re root I tried once with Towelroot and it did no work then tried to load the Kernel that Towelroot worked with and it got all bugy so i reloaded your Kernel and it was still bugy so I did the whole process over again and it worked a second time. LOL
Thanks so much,
Brad
Click to expand...
Click to collapse
TWRP will not work on anything above 4.2.2(MDK). You have to use Safestrap.
Do a FULL wipe to nc5, not the workaround. THEN towelroot, install Busybox(IMPORTANT) and Safestrap(modded version of TWRP SPECIFICALLY for devices with locked Bootloader), install Hyperdrive or ROM of choice.
Well I got all the way through, I got the Safestrap to work and boot to recovery. I did a wipe factory reset and wipe cache and Dalvik. I then try to install rom, now it says to install in a working and setup rom slot? I think that is where I have and issue. If I just try the instal it does not work as I get the error "no MD5 file found" and then "error flashing zip" Do you think this is due to the wrong Rom Slot or am I missing something that I am not doing?
Thanks so much for your help so far, I am so close and at the very last step in this whole ordeal, or at least I hope.
Brad
Bshade said:
Well I got all the way through, I got the Safestrap to work and boot to recovery. I did a wipe factory reset and wipe cache and Dalvik. I then try to install rom, now it says to install in a working and setup rom slot? I think that is where I have and issue. If I just try the instal it does not work as I get the error "no MD5 file found" and then "error flashing zip" Do you think this is due to the wrong Rom Slot or am I missing something that I am not doing?
Thanks so much for your help so far, I am so close and at the very last step in this whole ordeal, or at least I hope.
Brad
Click to expand...
Click to collapse
hmmmmmmm
Did you put the ROM on the SD card. Make sure to use the STOCK ROM SLOT!!!
Yeah, both of those things. On the SD card as a zip file and the stock ROM slot. I did try last night to flash another ROM quick to see if it would work and I got the same error so I don't think its my ROM but something I am doing wrong on the phone.
Thanks for your all your help so far,
Brad
Finally got it, took some time and lots of rework. I soft bricked it so many times I cant count them. I got this down though now, I am just playing with the rom to see what setup I like now.
Thanks so much again for your help.
Brad
Bshade said:
Finally got it, took some time and lots of rework. I soft bricked it so many times I cant count them. I got this down though now, I am just playing with the rom to see what setup I like now.
Thanks so much again for your help.
Brad
Click to expand...
Click to collapse
I think we have all been there at some point. Good job getting it all going. Takes some patience and effort. Don't forget to have some fun!
Sent from my SCH-I545 using XDA Free mobile app

Stuck at Sprint Screen; have details on what I did.

Hi, Followed all the amazing walk through like normal. Not sure what 4.x.x.x I was on, never really check to be honest.
First time this phone has been rooted. (I rooted because I was having problems with the phone, last phone I rooted and was able to fix the problems).
1. Used the download file and instructions by qking...
2. Same with TWRP
3. It rebooted, somehow it screwed up MicroSD card, would no longer read it. Then it rebooted again..
4. Stuck on Sprint screen for last couple hours.
I tried to get back into TWRP and do a factory clean and reset, when it rebooted it, sat at the Sprint Screen for hour or so. Then I searched and a few other people just had to use odin and redo it again and worked fine.
So I did odin again relfashed the file and at reboot it is stuck on Yellow Sprint screen..
That is where im stuck at now is Sprint Screen, thanks in advance!
Swaintan said:
Hi, Followed all the amazing walk through like normal. Not sure what 4.x.x.x I was on, never really check to be honest.
First time this phone has been rooted. (I rooted because I was having problems with the phone, last phone I rooted and was able to fix the problems).
1. Used the download file and instructions by qking...
2. Same with TWRP
3. It rebooted, somehow it screwed up MicroSD card, would no longer read it. Then it rebooted again..
4. Stuck on Sprint screen for last couple hours.
I tried to get back into TWRP and do a factory clean and reset, when it rebooted it, sat at the Sprint Screen for hour or so. Then I searched and a few other people just had to use odin and redo it again and worked fine.
So I did odin again relfashed the file and at reboot it is stuck on Yellow Sprint screen..
That is where im stuck at now is Sprint Screen, thanks in advance!
Click to expand...
Click to collapse
OK first pull battery, now reinsert bat and hold the power, home, and volume down buttons at the same time, then press the volume up button to get into download mode. Don't bother trying to get back to TWRP your past that. While in download mode check the status of the device. Is it Official or custom? Let me know the status.
Now lets flash a fresh stock OS with Odin, to save me a lot of typing go here. http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440
Download the version of odin you want both work fine. Download the version of the KK OS you want to flash, I like NK4. You can follow the steps on my thread listed above to flash an OS with one EXCEPTION!!!
EVEN IF THE DEVICE BOOTS UP AFTER YOU FLASH THE OS THE FIRST TIME, ONCE YOU GET PAST THE SET UP FOR FIRST TIME USE WHICH ( STARTS ABOUT 3-5 MIN AFTER THE SAMSUNG LOGO SCREEN BY THE WAY BE PATIENT ) POWER DOWN THE DEVICE GET BACK INTO DOWNLOAD MODE AND ODIN FLASH THE OS AGAIN !!!
This should get you back to bone stock OS. Once it boots up and get passed first time use set up. Now your ready to root, the way I root is first grab a copy of SuperSU ( latest version is fine its on my thread ) with your PC copy and paste it on the SD card. Next power down completely and boot into download mode, Odin flash a custom recovery TWRP is a good one. The device should boot up after the recovery is flashed on its own, don't try boot up the device yourself to soon, give the recovery a chance to flash completely. Now completely power down the device, hold the power, home, and volume up buttons and boot into recovery. Then flash the SuperSu zip then reboot device you should be off and running . . . .
Here is the first part, im working on the rest now.
Current Binary: Custom
System Status: Custom
Swaintan said:
Here is the first part, im working on the rest now.
Current Binary: Custom
System Status: Custom
Click to expand...
Click to collapse
Ok cool, remember that everything has to fit. Meaning depending on what OS you run i.e. KitKat, Lollipop etc everything should updated to match.
Example : If you run KK NC5 OS then Philz CWM recovery 6.9.12 and later works. TWRP 2.8.3.0 or later works.
If you run Lollipop OC5 then Philz CWM recovery 6.48.4 works. ( link is broken I have a copy if you need it ) TWRP 2.8.6.0 or later works.
As for SuperSU you could go all the way back to v 1.94 and still root the binarys will update automatically. The latest (stable ) version is 2.46 from chainfire.
TY Ill keep you updated, file is taking a long time to download, still sitting at 1 hr to finish up download. Once its downloaded ill continue with the rest of the steps and post updates.
Not been very happy with sprint lately, latest update to my Wifes note 2 screwed her phone way up, only way to fix it was root it. So as soon as I saw mine doing the same thing I hurried to root it, but looks like it was to late. Hopefully this fixes it all, I really do appreciate it.
Swaintan said:
Hi, Followed all the amazing walk through like normal. Not sure what 4.x.x.x I was on, never really check to be honest.
First time this phone has been rooted. (I rooted because I was having problems with the phone, last phone I rooted and was able to fix the problems).
1. Used the download file and instructions by qking...
2. Same with TWRP
3. It rebooted, somehow it screwed up MicroSD card, would no longer read it. Then it rebooted again..
4. Stuck on Sprint screen for last couple hours.
I tried to get back into TWRP and do a factory clean and reset, when it rebooted it, sat at the Sprint Screen for hour or so. Then I searched and a few other people just had to use odin and redo it again and worked fine.
So I did odin again relfashed the file and at reboot it is stuck on Yellow Sprint screen..
That is where im stuck at now is Sprint Screen, thanks in advance!
Click to expand...
Click to collapse
Forgot to say why you flash twice, when the device is corrupted or bootloops. 9 times out of 10 its because something was left behind from the previous OS or something didn't flash in from the new OS. Flashing twice I found through ( trial and error pulling my hair out ) solves this problem.
When I get done with a flashaholic binge and need to get back to a daily user, I always flash back to Stock OS twice, install recovery, and root. Then install a custom OS if want run one this way you always start clean. This way if something doesn't work or stops working you right where to start looking for the problem.
---------- Post added at 07:03 AM ---------- Previous post was at 06:55 AM ----------
Swaintan said:
TY Ill keep you updated, file is taking a long time to download, still sitting at 1 hr to finish up download. Once its downloaded ill continue with the rest of the steps and post updates.
Not been very happy with sprint lately, latest update to my Wifes note 2 screwed her phone way up, only way to fix it was root it. So as soon as I saw mine doing the same thing I hurried to root it, but looks like it was to late. Hopefully this fixes it all, I really do appreciate it.
Click to expand...
Click to collapse
Ya I agree rooting stops the updates. Usually I read up on the update first to see what problems it may be causing. Then decide to unroot and take it, I still run my 4.4.4 NK4 deoexed no knox debloated OS just not a fan of Lollipop to many problems with it, besides there's no themes for it.
You are awesome! Followed your directions and links inside your siggy. So this is where I sit;
I installed (from your siggy)
-SPRINT KK 4.4.4 N900PVPUDNK4
Stock rom : DEODEXED, NO KNOX, and DEBLOATED ( #2 )
Busybox / Zipaligned
Rooted / Superuser
No Knox ( Disabled / Removed )
Volume Mod / 300+ Fonts ( Thanks DevilDog512 )
Custom Kernel ****
-SU 2.46 (it auto updated when I installed)
-TWRP Manager 8.0.1.8
-Recovery TWRP 2.8.7.0
Now I have to start redoing apps etc.. THANK YOU SO MUCH!!!
Edit: Add: Now should be safe to install Wicked Green Theme and get all family n friends to send contact info... that part will be harder then what you had me do, TY again!
Swaintan said:
You are awesome! Followed your directions and links inside your siggy. So this is where I sit;
I installed (from your siggy)
-SPRINT KK 4.4.4 N900PVPUDNK4
Stock rom : DEODEXED, NO KNOX, and DEBLOATED ( #2 )
Busybox / Zipaligned
Rooted / Superuser
No Knox ( Disabled / Removed )
Volume Mod / 300+ Fonts ( Thanks DevilDog512 )
Custom Kernel ****
-SU 2.46 (it auto updated when I installed)
-TWRP Manager 8.0.1.8
-Recovery TWRP 2.8.7.0
Now I have to start redoing apps etc.. THANK YOU SO MUCH!!!
Edit: Add: Now should be safe to install Wicked Green Theme and get all family n friends to send contact info... that part will be harder then what you had me do, TY again!
Click to expand...
Click to collapse
Cool, what stock version KK OS did you flash twice before installed my deodexed 4.4.4 NK4 ?
Not sure, i know i followed each one, so it took me to a site where I had to download it specifically for my phone. My dl history says file name was N900PVPUDNK4_SPR it was the bone stock md5, did that one twice.
Swaintan said:
Not sure, i know i followed each one, so it took me to a site where I had to download it specifically for my phone. My dl history says file name was N900PVPUDNK4_SPR it was the bone stock md5, did that one twice.
Click to expand...
Click to collapse
Cool, that will work fine.

Categories

Resources