Related
Hi all,
I did some things with my phone this afternoon, but now when I try to boot it into recovery mode, it just boots into android.
The problem is, it won't boot into android either. It keeps showing the boot animation..
The recovery I use(d): CWM 5 by MoltenMotherboard
The ROM I use(d): Maclaw AOSP ICS Final 2
What do I have to do? I can still enter downloadmode so it's not hardbricked or something, but I have no idea what to do now.
Can I just flash the stock firmware with Odin?
The recovery I use is ext4 only, so that'd mean that when I'm back at the stock rom I can't use the recovery, right?
Update: At the moment I'm trying to flash this rfs+ext4 recovery via Odin, but it's already at 10 minutes and still no "Finish" message or something.. :/
Update 2: Flashed the stock rom via Odin, but now after it shows the blue glowing Samsung logo, it reboots and does it all over again.. It won't go into recovery either.. Please, can anyone help me!?
Update 3: Finally, after a pretty long time I finally got my phone working again.. I was so stupid to use the wrong combination to open the recovery (I used the CWM combination..) Thanks for "all your help" XD
LOL We were giving yo time to figure this out on your own. Good thing you followed your intuitions
Peteragent5 said:
LOL We were giving yo time to figure this out on your own. Good thing you followed your intuitions
Click to expand...
Click to collapse
Hehe, sorry for posting too quickly, but I haven't had any problems like this before so I was a bit scared and things like that
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
OK, I did search and found nothing. So, I need to ask this somewhere, hopefully this is the place. The similar threads search did not seem to help much.
I have a Tab S 8.4 WiFi. I rooted it and was running Cyanogen 12. I noticed the TWRP 2.8.3.0 update, so I went to install it. TWRP manager kept crashing, so I went to the TWRP site and downloaded the SM-T 700 klimti wifi img file. I used Flashify to flash this, as I have done numerous times. I wish I'd extracted and flashed the zip in TWRP, but I did not. Everything acted normal but when the tab went to boot up it got to the Black screen that announces Samsung Galaxy S, SM-T700, Powered by android. This was it. It flashed this screen constantly every second or so. Non stop. There was nothing any button combination would do. Except it will go into download mode. Nothing else. No hard reset, nothing. Download mode is it. I spent lots of time looking at various tutorials to see what I'd missed, nothing but download mode. So, I had Odin on the computer and the latest firmware from SamMobile, so I figured I could start over and get the tablet functioning. I've used Odin a fair amount before, including the original Galaxy, S III, S4, so I'm not unfamiliar with the process. I've yet (until now) had the privilege of having a wreck like this one.
So, Odin acts like it is doing its thing, runs through all the steps, says at the end Pass and all threads succeeded, none failed. At the end of the Odin process the tablet acts like it is booting. Up comes the Samsung name with the Bluish sparkly oval along with the standard Samsung tones we hear heading into the boot. That is as far as it goes. The blue and pink colors fade out and I am left with a black screen with SAMSUNG in the middle. Again, no button combination except download mode works at all. It just stays there. Pass showing proudly on the Odin screen (EDIT: I left it there for an hour or so to see if boot would finish before disconnection). I downloaded and tried flashing all of the various firmwares, same result. I even let the battery drain to zero hoping that would shut it off. It seemed to, but the results were the same, only the download mode combination will do anything. The power button starts up the phone in an initially normal manner, but it goes right to SAMSUNG in a black screen.
EDIT 2: I used the Cellular South firmware, saw nothing else US and thought I remembered reading this was what worked here.
There is likely user error here (and realize I might kick myself in the end...Oh wait, I already have), but I've run in circles enough to realize I'm probably doing the same sequence with the same error and I not able to see what it is.
Does anyone have any idea what is wrong or how to fix this? I hope it is fixable. I had hope since download and Odin at least go through the motions. I would greatly appreciate any advice, suggestions, or help. Thanks in advance.
Since you installed cm12 my guess is that its trying to switch back to davlik runtime. Have you tryed flashing twrp, then transfer another rom/custom rom too it and flash it with twrp?
DUHAsianSKILLZ said:
Since you installed cm12 my guess is that its trying to switch back to davlik runtime. Have you tryed flashing twrp, then transfer another rom/custom rom too it and flash it with twrp?
Click to expand...
Click to collapse
I did wonder about conflicts, including dalvik vs art. But I have a tab I can't do anything with except go to download. Since I tried stock firmware flashes, I imagine root is toast and so is flashing another TWRP, assuming I can do that with Odin. Never tried zip files with Odin. So short answer is no I have not tried flashing TWRP over Odin (which is now my only option). I also wondered if I was stuck with this paperweight until Samsung gets Lollipop to the Tab S, when I can get a stock 5.0 firmware from SamMobile, or someplace.
At any rate thank you.
SteveC485 said:
I did wonder about conflicts, including dalvik vs art. But I have a tab I can't do anything with except go to download. Since I tried stock firmware flashes, I imagine root is toast and so is flashing another TWRP, assuming I can do that with Odin. Never tried zip files with Odin. So short answer is no I have not tried flashing TWRP over Odin (which is now my only option). I also wondered if I was stuck with this paperweight until Samsung gets Lollipop to the Tab S, when I can get a stock 5.0 firmware from SamMobile, or someplace.
At any rate thank you.
Click to expand...
Click to collapse
What I mean is to flash twrp with odin then flash zips with twrp. If you cant reboot into recovery, if you installed adb then yoi can do adb reboot recovery.
I`m having same issues. I was on stock rooted ROM and flashed latest TWRP from the app. Now I`m stuck in bootloop.
EDIT: flashed TWRP 2.8.1.0 via Odin and everything works fine now.
senel said:
I`m having same issues. I was on stock rooted ROM and flashed latest TWRP from the app. Now I`m stuck in bootloop.
EDIT: flashed TWRP 2.8.1.0 via Odin and everything works fine now.
Click to expand...
Click to collapse
Thanks. When Christmas stuff winds down, I will give Odin a go. Thanks to both of you who answered. Merry Christmas.
OK, Odin says the TWRP is successful, goes through all motions, up to and including PASS. The tablet still will only go into Download Mode. At this point I'm wondering about trying Kies. Also thought what might happen if I unchecked Auto reboot in Odin and tried that again.
SteveC485 said:
OK, Odin says the TWRP is successful, goes through all motions, up to and including PASS. The tablet still will only go into Download Mode. At this point I'm wondering about trying Kies. Also thought what might happen if I unchecked Auto reboot in Odin and tried that again.
Click to expand...
Click to collapse
? You can boot into twrp? It should be power, home, vol up buttons. And to force reboot its power, home and vol up and down buttons at the same time.
DUHAsianSKILLZ said:
? You can boot into twrp? It should be power, home, vol up buttons. And to force reboot its power, home and vol up and down buttons at the same time.
Click to expand...
Click to collapse
No, the power, home, volume up does nothing, I even held it there for maybe 15 minutes. The power, home, and volume up/down gets the download screen, or rather it gets the warning screen about the dangers of flashing a custom OS. Continue goes into download and reboot get me the same old attempt to reboot then stuck on Samsung screen. That last is the ONLY button combination I can get to work.
I'll let the thing use up the battery and shut itself off and try the manual reboot to recovery again. I've chased this thing around so much I'm likely in a boot loop myself and can't see my error.
SteveC485 said:
No, the power, home, volume up does nothing, I even held it there for maybe 15 minutes. The power, home, and volume up/down gets the download screen, or rather it gets the warning screen about the dangers of flashing a custom OS. Continue goes into download and reboot get me the same old attempt to reboot then stuck on Samsung screen. That last is the ONLY button combination I can get to work.
I'll let the thing use up the battery and shut itself off and try the manual reboot to recovery again. I've chased this thing around so much I'm likely in a boot loop myself and can't see my error.
Click to expand...
Click to collapse
Hmm did you use the latest twrp? Ive alwayed use twrp 2.7. 1,1 Something. Never had problems in that version.
DUHAsianSKILLZ said:
Hmm did you use the latest twrp? Ive alwayed use twrp 2.7. 1,1 Something. Never had problems in that version.
Click to expand...
Click to collapse
Used 2.8.1.0. I had the issues trying to update to 2.8.3.0. I used 2.8.1.0 because it was working. I was thinking about trying the 2.8.3 because maybe I had a bad download and maybe a new flash might fix stuff.
Quick question, can Odin flash zip files? Never tried one.
SteveC485 said:
Used 2.8.1.0. I had the issues trying to update to 2.8.3.0. I used 2.8.1.0 because it was working. I was thinking about trying the 2.8.3 because maybe I had a bad download and maybe a new flash might fix stuff.
Quick question, can Odin flash zip files? Never tried one.
Click to expand...
Click to collapse
nope. Odin only flashes tars and files with md5 or a few otheres. You flash zips with twrp.
DUHAsianSKILLZ said:
nope. Odin only flashes tars and files with md5 or a few otheres. You flash zips with twrp.
Click to expand...
Click to collapse
Thanks, that's what I thought.
For whatever reason, this time the power, home, and volume up combination booted me into TWRP. Restored a backup and everything is up and running normally (at least so far).
I'm perfectly willing to admit error,but don't quite know where my error came in. I would swear I used the power, volume up, and home combination when I hit the download mode. But maybe not. I don't know why it worked now, except that I was inadvertently hitting the wrong combination, thinking I was doing it right. I remember thinking the first time it went to download mode, that I just did it wrong and used the wrong volume key. Thought I was more careful the succeeding tries.
At any rate thanks for the help. I will remember this particular lesson for a while .
hard brick
My sm-t700 hard brick with the last twrp... I don't know if it is the twrp but it's hard brick when I do a restore with twrp...now it is just dead... no power.. no nothing lol... j'ai été le échanger. . Vive future shop.. mais la j'ai peur de recommencer mon root et etc...
faztecnyk said:
My sm-t700 hard brick with the last twrp... I don't know if it is the twrp but it's hard brick when I do a restore with twrp...now it is just dead... no power.. no nothing lol... j'ai été le échanger. . Vive future shop.. mais la j'ai peur de recommencer mon root et etc...
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/showthread.php?t=2838473
DUHAsianSKILLZ said:
Try this http://forum.xda-developers.com/showthread.php?t=2838473
Click to expand...
Click to collapse
Thanks.. but I said hard brick and not soft brick..
SteveC485 said:
Used 2.8.1.0. I had the issues trying to update to 2.8.3.0. I used 2.8.1.0 because it was working. I was thinking about trying the 2.8.3 because maybe I had a bad download and maybe a new flash might fix stuff.
Quick question, can Odin flash zip files? Never tried one.
Click to expand...
Click to collapse
A lot of Tab S owners have had issue with TWRP 2.8.3. There is another thread on it. I installed 2.8.3 with Odin and it was pretty wonky. Went right back to 2.8.1.
If none of the methods worked for anyone try this. If your tablet keeps trying to boot into twrp or stuck at the galaxy tab s screen try this if you cant boot into download mode.
Let completely die. Then put it in the charger and quickly press the combination of buttons to get into download mode. That should over ride booting into twrp. another way is to plug it into your computer and try different combinations of buttons.
I have the samsung galaxy tab s 8.4 and I rooted it a few days ago and I thought to myself lets install a custom recovery, but before I did that I backed up my stock kernal and my stock recovery through flashify, also im on stock firmware, after I backed those things up I installed twrp 2.8.3.0 and I booted into recovery to back up my rom and data just in case I soft bricked my tablet like I used to do on my nexus 7, when trying to boot into twrp it went in to boot loop I have tried all button combination I know and have seen in this thread but none works except for going into download mode. I dont know if I should flash an older version of twrp and see if it works or should I install stock firmware on my device and im not sure what version of odin I should use if I flash a older version of twrp. The version I used to root my tablet is 3.07 of odin.
I ended up having to use CF auto-root, I was able to update cwm from within it.
After I tried rooting (didn't notice the guide I was using was 3 years old until it was too late) my phone got the "KERNEL IS NOT SEANDROID ENFORCING" and "SET WARRANTY BIT: KERNEL" . And it would not ****ing start up. My phone was 4.4.4 and I was trying to flash some 4.2.2 or later stuff onto it I guess, it messed my phone up. The only one and I mean ONLY one that would work was the 4.2.2 auto-root.
I was on kies before all of it and now kies won't even read my phone. Any way I can get my phone back to normal now, and possibly try the rooting again? It's slow and laggy now, my SD card won't be read, and my wifi doesn't work. I'm quite miserable but at least my phone works.. I have root access now so maybe I can fix it from within the phone? I appreciate the help!
EDIT: I tried getting cyanogen rom onto it and it got all messed up again after that, wouldn't get past cyanogen loading animation so I had to figure out how to fix it again for another 3 hours -.-
dameware said:
I ended up having to use CF auto-root, I was able to update cwm from within it.
After I tried rooting (didn't notice the guide I was using was 3 years old until it was too late) my phone got the "KERNEL IS NOT SEANDROID ENFORCING" and "SET WARRANTY BIT: KERNEL" . And it would not ****ing start up. My phone was 4.4.4 and I was trying to flash some 4.2.2 or later stuff onto it I guess, it messed my phone up. The only one and I mean ONLY one that would work was the 4.2.2 auto-root.
I was on kies before all of it and now kies won't even read my phone. Any way I can get my phone back to normal now, and possibly try the rooting again? It's slow and laggy now, my SD card won't be read, and my wifi doesn't work. I'm quite miserable but at least my phone works.. I have root access now so maybe I can fix it from within the phone? I appreciate the help!
EDIT: I tried getting cyanogen rom onto it and it got all messed up again after that, wouldn't get past cyanogen loading animation so I had to figure out how to fix it again for another 3 hours -.-
Click to expand...
Click to collapse
Go to this thread: http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
Download the NH7 or NK2 firmware (both are 4.4.4) and flash it using ODIN. Not sure why Kies isn't seeing your phone, it should, but ODIN should work. You may have to flash, pull battery, flash again, all without rebooting, for it to take.
This will get you back to stock. Then, if you want to root, get the CFAutoRoot for the phone, this will flash a non-stock recovery to give you root. This will give you the SEANDROID messages you were seeing. Use Triangle Away, if you want to get rid of them.
Rob
rlichtefeld said:
Go to this thread: http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
Download the NH7 or NK2 firmware (both are 4.4.4) and flash it using ODIN. Not sure why Kies isn't seeing your phone, it should, but ODIN should work. You may have to flash, pull battery, flash again, all without rebooting, for it to take.
This will get you back to stock. Then, if you want to root, get the CFAutoRoot for the phone, this will flash a non-stock recovery to give you root. This will give you the SEANDROID messages you were seeing. Use Triangle Away, if you want to get rid of them.
Rob
Click to expand...
Click to collapse
It won't read it because my phone is now too old of a device for the program (2.2.2 or whatever). Thank you very much I'm trying all this right now, finally a firmware download that doesn't take 6 hours because of horrible servers!
I will update on if this works or not, I'm guessing it will
I am having a similar situation. I used CM installer to root my S4 then the screen went white and the Installer stopped working. I tried to reset but only got the same Enforcing and warrant messages and the CyanogenMod loading screen.
I am trying to get to recovery mode by doing power+home+volume up button. I got into there and seeing a menu of commands. What should I do now? Will factory reset get me back into original state or I need to install a zip?
Lopakas said:
I am having a similar situation. I used CM installer to root my S4 then the screen went white and the Installer stopped working. I tried to reset but only got the same Enforcing and warrant messages and the CyanogenMod loading screen.
I am trying to get to recovery mode by doing power+home+volume up button. I got into there and seeing a menu of commands. What should I do now? Will factory reset get me back into original state or I need to install a zip?
Click to expand...
Click to collapse
EDIT:
Done and done! It all worked out, thank you thank you!
Now to try cyanogen and my device will be back to beast mode.
Just do what he says and you should be fine; factory reset never did anything for me :/
im coming from the old RR Rom and i did everything as told on the post i installed new twrp the new modem and firmware and everything seemed to install just fine but when i try to boot up for the first time the screen just is black no boot animations and i let it sit for a while but i know it isnt working and i read somewhere since im coming from a differnt kernel i have to flash the boot image first so im here trying to see if somewhere can point me to which file i have to download to flash since now if i try to do a restore i just get a black screen thanks for the help.
Ar3olaa said:
im coming from the old RR Rom and i did everything as told on the post i installed new twrp the new modem and firmware and everything seemed to install just fine but when i try to boot up for the first time the screen just is black no boot animations and i let it sit for a while but i know it isnt working and i read somewhere since im coming from a differnt kernel i have to flash the boot image first so im here trying to see if somewhere can point me to which file i have to download to flash since now if i try to do a restore i just get a black screen thanks for the help.
Click to expand...
Click to collapse
I am having this issue after updating to latest weekly on Moto X style.
did you ever figure out a solution?
HonestOtter said:
I am having this issue after updating to latest weekly on Moto X style.
did you ever figure out a solution?
Click to expand...
Click to collapse
I am having the same issue. It happens either when the screen times out or when the power button is pressed to turn off the screen.