Hi Hope someone can help.
History of what I did.
Im on BPA1
1. Rooted with Kingroot
2. Ran ADB Commands step by step.
3. Booted into Download mode, phone showed Developer
4. Booted into Android phone was fine.
5. Booted back into Download Mode.
6. Flashed TWRP with Odin.
7. Phone went into bootloop would not go past Galaxy note 4 screen.
This went on for an hr so I decided to flash stock BPA1 to try get phone back to original state. It flashed fine in ODIN but its still boot looping and wont go passed Note 4 screen.
Im getting very worried. Can someone help please
gersrt said:
Hi Hope someone can help.
History of what I did.
Im on BPA1
1. Rooted with Kingroot
2. Ran ADB Commands step by step.
3. Booted into Download mode, phone showed Developer
4. Booted into Android phone was fine.
5. Booted back into Download Mode.
6. Flashed TWRP with Odin.
7. Phone went into bootloop would not go past Galaxy note 4 screen.
This went on for an hr so I decided to flash stock BPA1 to try get phone back to original state. It flashed fine in ODIN but its still boot looping and wont go passed Note 4 screen.
Im getting very worried. Can someone help please
Click to expand...
Click to collapse
MAke sure you dont have the memory card used when unlocking bootloader, inside the phone. It will cause bootloop. IF bootloop persists, flash stock firmware, go to recovery and clear cache/data etc. It should boot.
For perfect root and twrp, refer my post #501 (http://forum.xda-developers.com/not...der-unlock-t3358913/post66386928#post66386928)
felixtaf said:
MAke sure you dont have the memory card used when unlocking bootloader, inside the phone. It will cause bootloop. IF bootloop persists, flash stock firmware, go to recovery and clear cache/data etc. It should boot.
For perfect root and twrp, refer my post #501 (http://forum.xda-developers.com/not...der-unlock-t3358913/post66386928#post66386928)
Click to expand...
Click to collapse
Cheers Mate, I'm sure I've already tried this, I will try again when I get home.
Thanks for your input.
Il let ya know.
felixtaf said:
MAke sure you dont have the memory card used when unlocking bootloader, inside the phone. It will cause bootloop. IF bootloop persists, flash stock firmware, go to recovery and clear cache/data etc. It should boot.
For perfect root and twrp, refer my post #501 (http://forum.xda-developers.com/not...der-unlock-t3358913/post66386928#post66386928)
Click to expand...
Click to collapse
First and foremost... THANK YOU!
I've been pulling my hair out for weeks trying to get my phone to boot, but this boot loop has been driving me insane! I've probably flashed 7 different factory ROMs in Odin no less than 5 times each!
And all I had to do was pull my SD card out??
Second:
How did you know that???
Sent from my SM-G900V using XDA-Developers mobile app
Wired4Fun said:
First and foremost... THANK YOU!
I've been pulling my hair out for weeks trying to get my phone to boot, but this boot loop has been driving me insane! I've probably flashed 7 different factory ROMs in Odin no less than 5 times each!
And all I had to do was pull my SD card out??
Second:
How did you know that???
Sent from my SM-G900V using XDA-Developers mobile app
Click to expand...
Click to collapse
It's a common mistake.
Well, thank you again....
Sent from my SM-G900V using XDA-Developers mobile app
Tiny little explanation, When rooting and unlocking your bootloader via ADB, the script wipes your SD card and puts a special code in it to backup your phones original CID. This may be used to unbrick your phone one day. So your NEWLY unlocked phone is using a new CID and your SD card is on the old one. Hence the boot loop. So when reading the OP, I thought the same thing. I didn't seem his say he pulled out his SD card after rooting. Hopefully you guys got it working again.
Lol, Honestly I dint figure it out. I read somewhere in the forums about it. Dont remember exactly who suggested it. But, it worked for me.
Did it work for you?
I have same problem, was on BPA1, unlocked bootloader, flashed twrp, something went wrong had to flash stock again, CPL1 loads up fine but when flashing back to BPA1 runs into bootloop, help.
you rock
felixtaf said:
MAke sure you dont have the memory card used when unlocking bootloader, inside the phone. It will cause bootloop. IF bootloop persists, flash stock firmware, go to recovery and clear cache/data etc. It should boot.
For perfect root and twrp, refer my post #501 (http://forum.xda-developers.com/not...der-unlock-t3358913/post66386928#post66386928)
Click to expand...
Click to collapse
you rock mate ... itried this for 2 hrs and all i had to so is take the damn sd out...thanks
Related
Hi all. I'm in a real pickle here and hoping someone can tell me how to get out of this mess. It's a bit of a long story, but I'll summarise as best I can.
I've had my Galaxy Note 2 LTE (N7105) for a year and I rooted it pretty much the day after I got it. I'm not new to rooting at all (fourth Android device since 2010, all rooted), but I still feel like a noob at times. Over this 2014 Easter period I had time off so I decided to change ROMs.
I was previously using CM 11, which I had been using pretty much since I rooted. And I had updated CM at least once a month, sometimes more frequently. So I was looking for some new ROMs, downloaded about 5 and tried them out. The last two I tried was OmniROM (a 4.4.2 ROM) and CM 11 Remix (also a 4.4.2 ROM). I was using TWRP 2.7.0.2 to do the wipes, caches, flashes, etc. I had no issues flashing OmniROM, but when I flashed CM 11 Remix, I couldn't get in the first time. I was stuck in a boot loop. I pulled the battery, got back into recovery and tried flashing again. Still boot looping. I think the mistake I made was a Data Format. Either way, I finally got CM 11 Remix to load by first wiping, flashing the ROM, GApps, a sensor fix, a camera fix, Devil Kernel and then Super SU. However once in the ROM I was getting constant Google Play Store / Services FCs. Oh, and yes, I went through the typical brand new Android setups, entering my Google account and so on... I found that if I cleared data / caches on both Google Play Store app and Google Play Services app, it gave me temporary joy but as soon as I tried to download any app in Google Play I'd get the FC. Also, my signal was totally gone. I tried flashing back to OmniROM as it was my last known good and working ROM, but now that was boot looping. I even tried some of the other ROMs from that bunch I had, including AOKP. All would boot loop.
So after much trying different GApp packages, I decided to best thing to do would be restore it to stock, root again, then go for the custom ROM (hopefully CM 11 Remix) from a nice clean slate. So I did this. I downloaded the Android 4.3 stock ROM from SamMobile here. Installed Odin 3.07, then loaded it up and flashed the stock ROM. All seemed to go great, but when the ROM was done and phone rebooted, I get stuck in another boot loop! This time at the white "Samsung" logo with the glowing blue edges. Not the model number screen. Also my LED light is on blue, if that means anything.
So I found this thread (post at top of page) which suggests I need to flash the PIT file during the stock ROM installation with Odin. So I found the PIT file here, and I'm ready to flash this along with the stock ROM... HOWEVER, I read something somewhere (can't find it now) that implied if I'm on Android 4.3, flashing a PIT is a bad move. Can anyone comment on that? I guessing since the stock ROM is 4.3, I'm technically on 4.3 (even though I can't get into it).
Or if anything else I'm doing immediately stands out as a seriously stupid move, please let me know. I've been without normal use of my phone for a couple days now and ironically I'm at the point where I'm considering going without a phone for the rest of my life... LOL! AS IF I COULD!
Anyways, any help will be much appreciated!
EDIT: I just realised I should have posted in Troubleshooting, not General Questions... If mods want to move this, please do.
i just suggest that you flash the stock odin without the pit and see if its working out or not. sometimes playing with pit files can screw up your device even more...
btw... next time you play flashing... i'm suggesting you make a backup of your working custom. its will save you lots of time if this kind of problem happen.
edan1979 said:
i just suggest that you flash the stock odin without the pit and see if its working out or not. sometimes playing with pit files can screw up your device even more...
btw... next time you play flashing... i'm suggesting you make a backup of your working custom. its will save you lots of time if this kind of problem happen.
Click to expand...
Click to collapse
I don't have any working ROM. All I have now is a boot loop.
invertedskull said:
I don't have any working ROM. All I have now is a boot loop.
Click to expand...
Click to collapse
I had a problem with my device where I was stuck at boot loader as well, but it was from the rar file of the rom(cm 11) cause I tried downloading it again and it worked.
I suggest you prepare Odin and the stock firmware, wipe factory/cache dalvik, system (advanced), then flash stock firmware, to bring everything back to normal.
Banutu said:
I had a problem with my device where I was stuck at boot loader as well, but it was from the rar file of the rom(cm 11) cause I tried downloading it again and it worked.
I suggest you prepare Odin and the stock firmware, wipe factory/cache dalvik, system (advanced), then flash stock firmware, to bring everything back to normal.
Click to expand...
Click to collapse
Hmmm, I'm not stuck at boot loader, just boot loop. Maybe you meant that?
To clarify, all I can do now is...
1. Boot normally and end up in a boot loop (at "Samsung" white logo with glowing blue edges).
2. Boot into Download mode and from there I can use Odin to flash / install.
3. Boot into stock recovery, which I've never used before (only ever used custom recovery).
I've prepped Odin again, ready to flash the stock firmware, but I've never done a wipe / factory reset with Odin. I don't see any Advanced settings? Did you mean I can do it elsewhere? Cos I see I can do wipes / factory reset from stock recovery.
So should I do that AND then go into Download mode and flash stock firmware with Odin?
invertedskull said:
Hmmm, I'm not stuck at boot loader, just boot loop. Maybe you meant that?
To clarify, all I can do now is...
1. Boot normally and end up in a boot loop (at "Samsung" white logo with glowing blue edges).
2. Boot into Download mode and from there I can use Odin to flash / install.
3. Boot into stock recovery, which I've never used before (only ever used custom recovery).
I've prepped Odin again, ready to flash the stock firmware, but I've never done a wipe / factory reset with Odin. I don't see any Advanced settings? Did you mean I can do it elsewhere? Cos I see I can do wipes / factory reset from stock recovery.
So should I do that AND then go into Download mode and flash stock firmware with Odin?
Click to expand...
Click to collapse
ohhh my bad, I meant boot loop (stuck at samsung logo), mine was stuck there but then after it restarts and goes into recovery mode
do these following steps and you should be fine with your device.
1. Go into recovery mode
2. Wipe factory/reset
3. Wipe cache
4. Wipe dalvik
5. Advance > format/system
Now you have no rom or any OS to load,
1. Power off the device
2. Open Odin on your PC(right click run as administrator)
3. power on your note in Download Mode
4. Connect your device to your PC via USB
5. odin should recognize your device, something blue like " ID" or something there, you should be familiar with that.
6. click PDA, and find the official stock firmware zip you got it from samsung website, and make sure it fits your device(for example if you have your note from italy you should have ITV)
7. Hit Start and it should finish in 5-10 minutes.
Its the cleanest way with Odin, I did some crap on my device and that's how I return it to normal.
Banutu said:
ohhh my bad, I meant boot loop (stuck at samsung logo), mine was stuck there but then after it restarts and goes into recovery mode
do these following steps and you should be fine with your device.
1. Go into recovery mode
2. Wipe factory/reset
3. Wipe cache
4. Wipe dalvik
5. Advance > format/system
Now you have no rom or any OS to load,
1. Power off the device
2. Open Odin on your PC(right click run as administrator)
3. power on your note in Download Mode
4. Connect your device to your PC via USB
5. odin should recognize your device, something blue like " ID" or something there, you should be familiar with that.
6. click PDA, and find the official stock firmware zip you got it from samsung website, and make sure it fits your device(for example if you have your note from italy you should have ITV)
7. Hit Start and it should finish in 5-10 minutes.
Its the cleanest way with Odin, I did some crap on my device and that's how I return it to normal.
Click to expand...
Click to collapse
All good! Cheers man!
I actually went ahead and booted into stock recovery and did the factory reset and partition wipe before I saw your post. And the stock firmware I'd flashed with Odin previously is now booting and I'm finally back in!!! WOOOOOOOOO!!!
Just need to root this bad boy and get back to a nice shiny custom ROM.
Thanks for the advice everyone!
invertedskull said:
All good! Cheers man!
I actually went ahead and booted into stock recovery and did the factory reset and partition wipe before I saw your post. And the stock firmware I'd flashed with Odin previously is now booting and I'm finally back in!!! WOOOOOOOOO!!!
Just need to root this bad boy and get back to a nice shiny custom ROM.
Thanks for the advice everyone!
Click to expand...
Click to collapse
I'm glad to hear that man, peace ^^
Banutu said:
I'm glad to hear that man, peace ^^
Click to expand...
Click to collapse
I have another hurdle... Some built in security is stopping SuperSU from running. It's not Knox, but something like it. I get this error message:
"Unauthorized access to a secured area has been blocked. Tap here for more info."
How can I disable this? I've searched on Google already but so far nothing is helping and I can mostly only find info about Knox...
EDIT: It was goddamn Knox all along... And I just disabled it by means of SuperSU. Finally!
invertedskull said:
I have another hurdle... Some built in security is stopping SuperSU from running. It's not Knox, but something like it. I get this error message:
"Unauthorized access to a secured area has been blocked. Tap here for more info."
How can I disable this? I've searched on Google already but so far nothing is helping and I can mostly only find info about Knox...
EDIT: It was goddamn Knox all along... And I just disabled it by means of SuperSU. Finally!
Click to expand...
Click to collapse
Lolol, see your finding your way on your own ^_^, I was about to give you this link and suggest you to read the comments as well
http://www.w0lfdroid.com/2013/12/Fix-Root-Problem-on-Android-4.3-for-Galaxy-S3-S4-Note2-Note3.html
Unfortunately for me I don't have Note 2 =(, I have an S II Plus, I hope to get Note 2 next month can't wait =S
Banutu said:
Lolol, see your finding your way on your own ^_^, I was about to give you this link and suggest you to read the comments as well
http://www.w0lfdroid.com/2013/12/Fix-Root-Problem-on-Android-4.3-for-Galaxy-S3-S4-Note2-Note3.html
Unfortunately for me I don't have Note 2 =(, I have an S II Plus, I hope to get Note 2 next month can't wait =S
Click to expand...
Click to collapse
Heh, yeah, all is well in my world once again!
The Note 2 is a great device man. I am sure you'll love it. The Note 3 looks great also, but I don't like the ribbed sides (I'm fussy) and last I read there's an eFuze that goes off once rooted or something along those lines. That's sh!t.
invertedskull said:
Heh, yeah, all is well in my world once again!
The Note 2 is a great device man. I am sure you'll love it. The Note 3 looks great also, but I don't like the ribbed sides (I'm fussy) and last I read there's an eFuze that goes off once rooted or something along those lines. That's sh!t.
Click to expand...
Click to collapse
What do you think about the new oneplus one, do you think I should get that instead?
Sent from my GT-I9105P using Tapatalk
Banutu said:
What do you think about the new oneplus one, do you think I should get that instead?
Sent from my GT-I9105P using Tapatalk
Click to expand...
Click to collapse
Hmmm, I haven't seen that one... Feel free to PM me a link.
Help Me!
Banutu said:
I'm glad to hear that man, peace ^^
Click to expand...
Click to collapse
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)
mroldman281 said:
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)
Click to expand...
Click to collapse
If you have access to anything, and don't get JUST the boot loop, then you DO NOT have the same case I was in. You are probably able to recover from this. Try posting on the Tf Forums. The guys over there are "specialists" in Asus Tf tablets, and as you'll see on this thread (http://www.transformerforums.com/fo...-boot-loop-after-doing-routine-cm-update.html), they gave me a lot of help. Not that I was able to recover, but they were awesome dudes.
mroldman281 said:
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)
Click to expand...
Click to collapse
mroldman281, You didn't post again, so I don't know, If You found solution, but since I had same simptoms, and after four days of reinstalling different stock roms, wiping and even messing with PIT via Odin etc..I can say, that in my case the reason for boot loop was faulty battery. The phone worked when it was plugged in and restarted soon after i unplugged USB cable, and just lopped afterwards. Replacement battery put everything back in order. And I am one happy Camper!
Hope this info helps someone else with boot loop problem
same problem stuck in bootloop
hey guys i have the same problem bootloop all the time i tryied stock firmware but nothing happend avec i rooted my note 2 and intalled a costom recovery and a many roms but stuck in bootloop i didn't chage baterry , by the way i wiped cache and reset factory and clear dalvick cache but the same always bootloop
what u suggest i do
ps : i can acces to bootloader or download mode it charge normally
woow get back my note 2 lte alone
hey guys i get back my note 2 i don't know how but it was a succes :victory:
first : i tried so many afficial firmware 4.4.2 and costom roms but didn't change the problem of bootloop
then i remembred what version i was in it was 4.1.1 so i download it from sammobiles thenks to them flash it and boooom the note 2 lte start like a charm
i want to thanks everyone for their help even if they didn't help directly but this past 3 days i read almost all the threads about note 2
well i thinks one of the selutions here is to revert back the the original stock firmware like i did so maybe will fix the bootloop
:crying: This problem started when I tried to install ResurrectionRemix Rom for the The LS980, I had a ZVE Radio on my phone, before I rooted my device, I used StumpRoot to root my phone, then after that I installed autorec to be able to use TWRP, then after that i backed up my device so that I can start flashing the Rom, so after that I wiped Dalvik/Cache/Data, etc, except for internal storage, then i install the Rom, and after that I installed the Gapps for the Rom, and after that I wiped Dalvik and Cache and restarted my device, and its now going into a bootloop, so at this point I'm still able to go into TWRP so that I can be able to restore my backup, but it wasn't there, so I went back to the Install tab and it looked different like it was less files than before, it's like the system on my phone re-wrote itself, idk, so then I went into the file manager that is in TWRP to search for my backup file, I found it along with all my other files, but I didn't know how to be able to restore it, so (I think this is were I made things worse for myself) I went to the Install Tab to install the ZVC Radio, because I thought the Rom wasn't working because of the different Radios my device had, so then I restart my phone, and now it's just a blank screen, that keeps looping, so I started searching on XDA if anyone else is facing this issue, and I found this thread http://forum.xda-developers.com/showthread.php?t=2582142 it helped me get out of the deep brick whereas there was no recovery mode before, But I'm still in a Hard Brick whereas the LG Logo is shown for several seconds and then it says LG Security Error and shuts down and I still dont have download mode, but if I'm connected to a computer it just goes into a bootloop with the same message on the screen, so I installed LG drivers and ADB Drivers for my phone to be recognized on the computer, and the computer recognizes the device when I'm in recovery mode, but at this point I don't know what to do, and I certainly don't want to spend 150.00$ for a replacement, so if anyone can help me, I will very much appreciate it.
Images Below (Forgive me if the image quality is a little fuzzy, these images were taken using my Nexus 4)
TechGirl90 said:
:crying: This problem started when I tried to install ResurrectionRemix Rom for the The LS980, I had a ZVE Radio on my phone, before I rooted my device, I used StumpRoot to root my phone, then after that I installed autorec to be able to use TWRP, then after that i backed up my device so that I can start flashing the Rom, so after that I wiped Dalvik/Cache/Data, etc, except for internal storage, then i install the Rom, and after that I installed the Gapps for the Rom, and after that I wiped Dalvik and Cache and restarted my device, and its now going into a bootloop, so at this point I'm still able to go into TWRP so that I can be able to restore my backup, but it wasn't there, so I went back to the Install tab and it looked different like it was less files than before, it's like the system on my phone re-wrote itself, idk, so then I went into the file manager that is in TWRP to search for my backup file, I found it along with all my other files, but I didn't know how to be able to restore it, so (I think this is were I made things worse for myself) I went to the Install Tab to install the ZVC Radio, because I thought the Rom wasn't working because of the different Radios my device had, so then I restart my phone, and now it's just a blank screen, that keeps looping, so I started searching on XDA if anyone else is facing this issue, and I found this thread http://forum.xda-developers.com/showthread.php?t=2582142 it helped me get out of the deep brick whereas there was no recovery mode before, But I'm still in a Hard Brick whereas the LG Logo is shown for several seconds and then it says LG Security Error and shuts down and I still dont have download mode, but if I'm connected to a computer it just goes into a bootloop with the same message on the screen, so I installed LG drivers and ADB Drivers for my phone to be recognized on the computer, and the computer recognizes the device when I'm in recovery mode, but at this point I don't know what to do, and I certainly don't want to spend 150.00$ for a replacement, so if anyone can help me, I will very much appreciate it.
Images Below (Forgive me if the image quality is a little fuzzy, these images were taken using my Nexus 4)
Click to expand...
Click to collapse
All non stock require zv8 radio. If your highlighted image in recovery says update by adb. You may be able to grab official zve update from sprint g2 general.
Or hit the wipe data and see if it goes to TWRP.
secret.animal said:
All non stock require zv8 radio. If your highlighted image in recovery says update by adb. You may be able to grab official zve update from sprint g2 general.
Or hit the wipe data and see if it goes to TWRP.
Click to expand...
Click to collapse
It didn't go through.[emoji20] Installation aborted, I think I messed up big time.[emoji20] I appreciate the help though.
Sent from my Nexus 4 using Tapatalk
TechGirl90 said:
It didn't go through.[emoji20] Installation aborted, I think I messed up big time.[emoji20] I appreciate the help though.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Which part or both fail? The wipe data to TWRP, is a shot in the dark in going to recovery. Adb side load official update was also.
I read somewhere of repairing the partitions by pushing them. I'll see if I can find that thread.
secret.animal said:
Which part or both fail? The wipe data to TWRP, is a shot in the dark in going to recovery. Adb side load official update was also.
I read somewhere of repairing the partitions by pushing them. I'll see if I can find that thread.
Click to expand...
Click to collapse
Both failed, the wipe data just freezes and goes no further, and I can't get to twrp, I just have the basic recovery mode.
Sent from my Nexus 4 using Tapatalk
TechGirl90 said:
Both failed, the wipe data just freezes and goes no further, and I can't get to twrp, I just have the basic recovery mode.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Let's hope I find that thread.
---------- Post added at 04:04 PM ---------- Previous post was at 03:48 PM ----------
TechGirl90 said:
Both failed, the wipe data just freezes and goes no further, and I can't get to twrp, I just have the basic recovery mode.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2681089
Try this one which I got from
http://forum.xda-developers.com/sprint-g2/help/ls980-bricked-black-screen-fastboot-t2976744
He quoted 2 threads he tried. I clicked the one I have above first and looked like a good help.
TechGirl90 said:
Both failed, the wipe data just freezes and goes no further, and I can't get to twrp, I just have the basic recovery mode.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Have you been able to resurrect your phone?
secret.animal said:
Have you been able to resurrect your phone?
Click to expand...
Click to collapse
Nope, the phone's dead, I really damaged the phone's software really bad, I didn't follow the instructions correctly as stated on the RessurectionRemix Rom Thread , so I've brought this upon myself, Thankfully I've received a replacement today, but now I'm feeling iffy about rooting my phone and flashing roms again, because I don't want to go through this predicament again.
Update: Thank You for helping me try to get the device back into a functional state, I really appreciate it
on same boat
hey, techgirl90,
on same boat only have stock recovery
pls help me if you have find anyone
I'm having one hell of a time with this tablet. This is pushing a month and I'm still not satisfied with my tablet.
Tonight I finally tracked down what I had hoped was a stock firmware for my tablet. Halfway through the download it timed out and when I went to download it again, the same thing happened.
So I tried to take my tablet that isn't "properly rooted" anymore and use Odin 9, instead of Odin 10, and place kitkat on my device rather than be stuck with Lollipop 5.0.2. All of this because The Sims Freeplay app isn't working and I can't find another soul on the face of the earth who can give me an answer to why this is happening.
Now I'm stuck on the samsung logo. I managed to get it back in download mode and that's where I flashed Lollipop 5.0.2 through Odin 10. I figured that would solve my problem. It didn't, but at least I got TWRP back on my device.
I never recovered anything that came with my tablet. I did not think I'd ever go back to unroot nor did I know how to back it up in the first place. So there's nothing in my recovery I can boot from. So what I did was I came back here and I downloaded the recovery for TWRP. I flashed it from my SD card, it told me it was successful... now what? I've rebooted and my device still loads to the samsung logo...and just stays there. The little confetti animation happens behind the logo, but that's it. It doesn't turn off. It doesn't reset itself.
CAN SOMEONE PLEASE TELL ME WHAT I'M DOING WRONG?!
I've already voided the warranty on this device and I regret almost daily that I decided to root in the first place. I say this only because I think rooted devices are top-notch, but I haven't been having very much luck with them. It took me a week to root. When I finally rooted then my favorite app game stopped working. Then I figured I could flash the stock firmware easily (but it seems like every place I go to find kitkat or even stock lollipop I can't find or I do, but files are corrupt or sites are full of ads).
I can't use my device at all now except click around in TWRP which isn't doing me any good.
I just want my tablet back. I spent 500 dollars on this thing and I haven't had time to even enjoy it. It's only two months old.
Please. Again. Someone HELP me. I want to figure this out and I don't want to accept that I bricked my device because I've watched plenty of videos on youtube and people are stuck with a phone that's resetting and all they do is fix it right there in front of my eyes.
Why can't I fix this? What is it that I'm not doing properly?
geekery15 said:
I'm having one hell of a time with this tablet. This is pushing a month and I'm still not satisfied with my tablet.
Tonight I finally tracked down what I had hoped was a stock firmware for my tablet. Halfway through the download it timed out and when I went to download it again, the same thing happened.
So I tried to take my tablet that isn't "properly rooted" anymore and use Odin 9, instead of Odin 10, and place kitkat on my device rather than be stuck with Lollipop 5.0.2. All of this because The Sims Freeplay app isn't working and I can't find another soul on the face of the earth who can give me an answer to why this is happening.
Now I'm stuck on the samsung logo. I managed to get it back in download mode and that's where I flashed Lollipop 5.0.2 through Odin 10. I figured that would solve my problem. It didn't, but at least I got TWRP back on my device.
I never recovered anything that came with my tablet. I did not think I'd ever go back to unroot nor did I know how to back it up in the first place. So there's nothing in my recovery I can boot from. So what I did was I came back here and I downloaded the recovery for TWRP. I flashed it from my SD card, it told me it was successful... now what? I've rebooted and my device still loads to the samsung logo...and just stays there. The little confetti animation happens behind the logo, but that's it. It doesn't turn off. It doesn't reset itself.
CAN SOMEONE PLEASE TELL ME WHAT I'M DOING WRONG?!
I've already voided the warranty on this device and I regret almost daily that I decided to root in the first place. I say this only because I think rooted devices are top-notch, but I haven't been having very much luck with them. It took me a week to root. When I finally rooted then my favorite app game stopped working. Then I figured I could flash the stock firmware easily (but it seems like every place I go to find kitkat or even stock lollipop I can't find or I do, but files are corrupt or sites are full of ads).
I can't use my device at all now except click around in TWRP which isn't doing me any good.
I just want my tablet back. I spent 500 dollars on this thing and I haven't had time to even enjoy it. It's only two months old.
Please. Again. Someone HELP me. I want to figure this out and I don't want to accept that I bricked my device because I've watched plenty of videos on youtube and people are stuck with a phone that's resetting and all they do is fix it right there in front of my eyes.
Why can't I fix this? What is it that I'm not doing properly?
Click to expand...
Click to collapse
I just skimmed through all this reading, so I may have missed a few things. The thing I didn't see if factory resetting. You need to factory reset in twrp. Just go to wipe and factory reset. Now reboot and wait at least 20 minutes as it does take quite a while to boot.
If doesnt do, transfer a custom stock based ROM for your device (any KK ROM should do) to your SD card. Factory reset in twrp and flash ROM. Now reboot and wait.
Typically, flashing with Odin takes 20 minutes to boot up for the first time. Just be sure you factory reset.
Sent from my SM-T800 using Tapatalk
DUHAsianSKILLZ said:
I just skimmed through all this reading, so I may have missed a few things. The thing I didn't see if factory resetting. You need to factory reset in twrp. Just go to wipe and factory reset. Now reboot and wait at least 20 minutes as it does take quite a while to boot.
If doesnt do, transfer a custom stock based ROM for your device (any KK ROM should do) to your SD card. Factory reset in twrp and flash ROM. Now reboot and wait.
Typically, flashing with Odin takes 20 minutes to boot up for the first time. Just be sure you factory reset.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
Ok. I just factory resetted. Then I went to reboot and clicked "system". Now it restarted and brought me back to the same samsung logo... do I wait 20 minutes on that screen?
geekery15 said:
Ok. I just factory resetted. Then I went to reboot and clicked "system". Now it restarted and brought me back to the same samsung logo... do I wait 20 minutes on that screen?
Click to expand...
Click to collapse
Yep.
Sent from my SM-T800 using Tapatalk
DUHAsianSKILLZ said:
Yep.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
By any chance does it take longer than 20 minutes?
It's been 28 minutes and I'm still on the Samsung logo.
geekery15 said:
By any chance does it take longer than 20 minutes?
It's been 28 minutes and I'm still on the Samsung logo.
Click to expand...
Click to collapse
Sometimes. Try and wait 10 more minutes.
If it doesn't boot, I think you may have to flash a custom stock based ROM and flash it from your SD card in twrp.
Sent from my SM-T800 using Tapatalk
DUHAsianSKILLZ said:
Sometimes. Try and wait 10 more minutes.
If it doesn't boot, I think you may have to flash a custom stock based ROM and flash it from your SD card in twrp.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
Custom Stock Based Rom? Does that mean I'll push myself further away from a stock firmware? Also... where do I find one and are there instructions for it? I thought roms were firmwares up until like 4 hours ago and I've been reading of roots for a little over a month now.
I see you've got the same tablet. By any chance are you running 5.0.2 lollipop and do you happen to know having a rooted device is the reason why The Sims Freeplay won't get past it's splash screen or if it's the app itself and it's newest update that made it wiggy?
I'll flash whatever at this point, but my main reasons for continuing to mess with my tablet was because of not being able to play the sims on there. Every other game I play works.
geekery15 said:
Custom Stock Based Rom? Does that mean I'll push myself further away from a stock firmware? Also... where do I find one and are there instructions for it? I thought roms were firmwares up until like 4 hours ago and I've been reading of roots for a little over a month now.
I see you've got the same tablet. By any chance are you running 5.0.2 lollipop and do you happen to know having a rooted device is the reason why The Sims Freeplay won't get past it's splash screen or if it's the app itself and it's newest update that made it wiggy?
I'll flash whatever at this point, but my main reasons for continuing to mess with my tablet was because of not being able to play the sims on there. Every other game I play works.
Click to expand...
Click to collapse
The only thing I can suggest is download this to your SD card and flash it in twrp. http://forum.xda-developers.com/showthread.php?p=56345482
The Sims may not work because its uncomptiple with lollipop.
Simply, hit wipe in twrp, hit advanced wipe, and tick system, dalivk and cache. Then go back and install the Cm11 zip and reboot. Hopefully it gets you booting
Sent from my SM-T800 using Tapatalk
I'd actually flash this as its more like stock just debloated.
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
You need to wipe system, dalvik, cache and data then Install via twrp.
Wait at least 10 to 15 mins after install for initial boot up.
For future reference whenever you go back to kitkat from lollipop you need to wipe the data and cache partition first.
By the way some apps and games do not work on rooted devices for security reasons.
DUHAsianSKILLZ said:
Yep.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
DUHAsianSKILLZ said:
Sometimes. Try and wait 10 more minutes.
If it doesn't boot, I think you may have to flash a custom stock based ROM and flash it from your SD card in twrp.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
ashyx said:
I'd actually flash this as its more like stock just debloated.
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
You need to wipe system, dalvik, cache and data then Install via twrp.
Wait at least 10 to 15 mins after install for initial boot up.
For future reference whenever you go back to kitkat from lollipop you need to wipe the data and cache partition first.
By the way some apps and games do not work on rooted devices for security reasons.
Click to expand...
Click to collapse
I understand that. That is why I clicked unroot in supersu and tried the game app, but it still wouldn't work. On my galaxy note 3 I run 5.0 lollipop and my game works fine. My phone isn't rooted and I never decided to root it and then unroot it.
Is an app smart enough to know when a device has been rooted and if are those that hack their actual game on rooted devices uses cloak or xposed or both to by pass their root?
I rather be unrooted for the sake of the game, but how does one find the stock firmware? Or is it not possible at this point?
Sorry for any confusion.
ashyx said:
I'd actually flash this as its more like stock just debloated.
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
You need to wipe system, dalvik, cache and data then Install via twrp.
Wait at least 10 to 15 mins after install for initial boot up.
For future reference whenever you go back to kitkat from lollipop you need to wipe the data and cache partition first.
By the way some apps and games do not work on rooted devices for security reasons.
Click to expand...
Click to collapse
Okay. I installed or flashed ironrom to my tablet from twrp. i followed the directions it told me and I decided to pick the regular rom above the custom one that was close to stock. Then it told me that it was going to reboot; which it did. When it came back it got stuck on the same samsung loading screen so I powered it off, went back into TWRP (because powering off now isn't possible, more like restart) and I went to "Reboot " and then I clicked "power off".
I guess I'll be waiting for 10 to 15 minutes.
I Pray I did this correctly.
geekery15 said:
Okay. I installed or flashed ironrom to my tablet from twrp. i followed the directions it told me and I decided to pick the regular rom above the custom one that was close to stock. Then it told me that it was going to reboot; which it did. When it came back it got stuck on the same samsung loading screen so I powered it off, went back into TWRP (because powering off now isn't possible, more like restart) and I went to "Reboot " and then I clicked "power off".
I guess I'll be waiting for 10 to 15 minutes.
I Pray I did this correctly.
Click to expand...
Click to collapse
Thanks for all the help! I'm finally back to where I want to be and the ss freeplay seems to be working. I can't thank you both enough.
geekery15 said:
Thanks for all the help! I'm finally back to where I want to be and the ss freeplay seems to be working. I can't thank you both enough.
Click to expand...
Click to collapse
Why did you reboot back into twrp? You should have just let it do its thing after it rebooted.
So for any others that may happen upon this thread.
What was your solution?
ashyx said:
Why did you reboot back into twrp? You should have just let it do its thing after it rebooted.
So for any others that may happen upon this thread.
What was your solution?
Click to expand...
Click to collapse
I did because I thought it had to be shut down before I powered it on and waited. I realized afterwards that you probably meant to just let it sit for 10 to 15 minutes.
Are you asking me my solution or other peoples solution?
geekery15 said:
Are you asking me my solution or other peoples solution?
Click to expand...
Click to collapse
Your solution.
cant reboot after failed encryption
I was trying to encrypt my galaxy tab s, which is rooted and has lollipop 5.0. Afrer reading encryption failed. I tried to reboot in recovery via twrp. My device doesn't reboot, it just acts like its going thru the motions. Only to return to twrp recovery menu. How do I reboot the system clearing the failed encryptions. I am a noob and any suggestions would be much appreciated.
You will have to go into recovery and wipe the data and cache partition then reboot.
It may take a while to boot up after that.
Well I thought my solution was using IronRom... but i'm not too sure now.
I just got back from work and I went to turn on my tablet and it took me to the same loading screen and then after about 5 minutes it tells me that the system can't respond. It asks me to click "ok" or "wait" ... clicking either just turns my tablet off.
Now the screen has dimmed. It's turning on when it wants and sometimes it'll show me the time in the upper right hand corner, but it won't let me do anything because it's a black screen.
What does all of this mean?
I just noticed if I click the "power button" it just flashes my tablet desktop then goes back to black, but it shows me the battery percentage and the time in the upper right hand corner...
smt 800 stuck in logo
SAMSUNG GALAXY TAB S 10.5 WIFI WHAT IT CAN AND CANT DO
i HAD ROOTED AND INSTALLED LOLLIPOP 5.0 WITH SUPER SU AND TWRP RECOVERY.
I THEN TRIED TO ENCRYPT WHICH FAILED.
MY DEVICE SAID TO REBOOT SYSTEM AND THEN TRY TO ENCRYPT AGAIN. AFTER REBOOTING, MY DEVICE IS STUCK WITH (logo screen)THE SAMSUNG TAB S NAME AT THE TOP OF THE SCREEN AND ANDROID ON THE BOTTOM. I then rerooted with cf auto root thru odin. Odin and my tablet went thru the motions. When everything was complete and device should have initialize, but didn't. This part of the process didn't happen.
I am able to go into DOWNLOAD MODE and can get to manual mode, but I seem to have lost recovery. Here is the info.
android system recovery <3e>
kot49h_t800xxu1af8..
the binary reads: samsung official
system status: custom
Do you have any suggestions.
So I used this guide:
https://www.reddit.com/r/galaxynote4/comments/4f8cgc/guide_a_noobs_guide_to_permanent_rootunlocked/
When I got to step 8, the phone would freeze. Super Sume wasn't doing anything. Then the whole phone would freeze. I looked into what it was supposed to do, and I read that this step was just uninstalling the app due to spyware. I figured "I'll worry about that once I get root. Then I can install a whole new rom, and it won't be there regardless." So I moved onto the next step. I got all the way down to step 10, and the adb wouldn't connect. So, I went to reboot the phone, and it says "root is not available, would you like twrp to root?" or something like that. I said yes. Now the phone is in a boot loop. I don't know if I have root or not. I tried doing a factory reset, by wiping. That didn't work. Still boot looping. I know my device isn't lost, but I don't know what the next steps are to getting it back.
I'm also currently downloading http://www.sammobile.com/firmwares/download/65392/N910VVRU2BPA1_N910VVZW2BPA1_VZW/
this, in case I need to start all over with my phone.
Can anyone help me at least get past the bootloop sequence? It goes samsung galaxy screen, samsung animaltion, verizon red screen, then bootloop.
Did you format you're SD card?
Sent from my SM-N920F using Tapatalk
Lost My Mind said:
So I used this guide:
https://www.reddit.com/r/galaxynote4/comments/4f8cgc/guide_a_noobs_guide_to_permanent_rootunlocked/
When I got to step 8, the phone would freeze. Super Sume wasn't doing anything. Then the whole phone would freeze. I looked into what it was supposed to do, and I read that this step was just uninstalling the app due to spyware. I figured "I'll worry about that once I get root. Then I can install a whole new rom, and it won't be there regardless." So I moved onto the next step. I got all the way down to step 10, and the adb wouldn't connect. So, I went to reboot the phone, and it says "root is not available, would you like twrp to root?" or something like that. I said yes. Now the phone is in a boot loop. I don't know if I have root or not. I tried doing a factory reset, by wiping. That didn't work. Still boot looping. I know my device isn't lost, but I don't know what the next steps are to getting it back.
I'm also currently downloading http://www.sammobile.com/firmwares/download/65392/N910VVRU2BPA1_N910VVZW2BPA1_VZW/
this, in case I need to start all over with my phone.
Can anyone help me at least get past the bootloop sequence? It goes samsung galaxy screen, samsung animaltion, verizon red screen, then bootloop.
Click to expand...
Click to collapse
Did you get it working??
Sent from my SM-N920F using Tapatalk
I did. I followed that guide about 4 times, and each time I had to reflash to stock with odin. As all this was happening, on a second computer I was researching why it was bootlooping. Well, as it turns out, the guide is bad. The reason I was bootlooping is because 5.1.1 has a special security detection that if it detects root, it will bootloop. You need a different kernal, but his guide said to turn the phone back on after root but before flashing the new kernal.
So, eventually I just tried my own way. I got the bootloader unlocked, and then went into twrp, to flash the new kernal and supersu from zip. It worked.
As I type this, I'm backing up my real SD card (I used a smaller temporary one for the root process), because I'm going to format this, and only put my pictures/old apks/music on it. That should clear up 90% of the space. After I have it backed up, formatted, and files moved to the SD card I will be flashing my first rom.
I have chosen http://forum.xda-developers.com/not...rom-dr-ketan-rom-dr-ketan-rom-l16-n5-t3370495
this to be my new Rom
Lost My Mind said:
I did. I followed that guide about 4 times, and each time I had to reflash to stock with odin. As all this was happening, on a second computer I was researching why it was bootlooping. Well, as it turns out, the guide is bad. The reason I was bootlooping is because 5.1.1 has a special security detection that if it detects root, it will bootloop. You need a different kernal, but his guide said to turn the phone back on after root but before flashing the new kernal.
So, eventually I just tried my own way. I got the bootloader unlocked, and then went into twrp, to flash the new kernal and supersu from zip. It worked.
As I type this, I'm backing up my real SD card (I used a smaller temporary one for the root process), because I'm going to format this, and only put my pictures/old apks/music on it. That should clear up 90% of the space. After I have it backed up, formatted, and files moved to the SD card I will be flashing my first rom.
I have chosen http://forum.xda-developers.com/not...rom-dr-ketan-rom-dr-ketan-rom-l16-n5-t3370495
this to be my new Rom
Click to expand...
Click to collapse
Please help! what was your own way and what did you do to get the bootloader unlocked?
So i have searched all over the internet and havent found ant help. My phone is in a bootloop and i can't get out of it, i have tried with Nexus root tool kit to factory reset but just bootloop have tried it twice. Also tried to install factory with TWRP but still bootloop. I have an unlocked bootloader, I also tried to lock it and start with a new factory image but didnät work either . So please help me if you can i'm willing to try anything can't afford a new phone right now.
BIG UPDATE
So now after some work with trying to fx this i have found the problem with it. It's that my phone dosen't install the files that i install with either adb or TWRP. I found this by putting pure nexus rom on the phone and installing it with TWRP and then remove it from the storage. That was when the storage on the phone said it was still zero even when i had choose to install a new rom on the phone. but it still bootloop with the google logo and the four dots that pulse and then reboots.
Another Update
So i tried with installing the pixel rom from the xda forum and it all went well and all with the insallation no errors what so ever but my boot animation changed to pixels but still continue to bootloop still don't know whats happening.
I'm not sure what state your device is in right now. Is the bootloader locked or unlocked? When you tried to lock it, don't try that again, did it lock or did it remain unlocked when you re-booted into the bootloader? Were you able to successfully flash the factory image?
I'd suggest you carefully read thru this and pay particular attention to how to flash a factory image, http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Sent from my Nexus 9 using XDA-Developers mobile app
Not really
jd1639 said:
I'm not sure what state your device is in right now. Is the bootloader locked or unlocked? When you tried to lock it, don't try that again, did it lock or did it remain unlocked when you re-booted into the bootloader? Were you able to successfully flash the factory image?
I'd suggest you carefully read thru this and pay particular attention to how to flash a factory image, http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Sent from my Nexus 9 using XDA-Developers mobile app
Click to expand...
Click to collapse
Whell when i locked the bootloader it got locked but then when it bootlooped for one to two hours i opened it again and went to ask the pros at xda. I also read through the guide you linked me and did as said in the tutorial but my phone is still bootlooping right now.
Did you successfully manually flash each of the image files in the latest factory image? Bootloader, radio, system, boot, etc.
jd1639 said:
Did you successfully manually flash each of the image files in the latest factory image? Bootloader, radio, system, boot, etc.
Click to expand...
Click to collapse
Yes i succesfully flashed everyone that was said in the guide.