Related
So I recently rooted my LTE Tab 10.1 after some errors on my part. I finally got root, and the bootloader unlocked (thanks to six5alive's post here) Here's what I have:
CWM recovery
unlocked bootloader
Rom Manager installed
SU permissions
I've tried flashing two different ROMs, and both flash without a problem. But when I attempt to reboot, I get the Samsung logo and a yellow triangle below it, and then the tablet shuts down. At first I thought it was just the ROM, but after flashing two, I'm getting suspicious. I have a Nandroid backup of the stock rooted ROM, and that restores & boots properly every time.
What am I doing wrong?
You might have root but from the sounds of it the tab does not like the insecure kernel hence the yellow triangle on the logo screen. On a tab, I am not sure how to get around this.
Why not run stock and use TiBu to get rid of the bloatware until you can find a solution? Keep a Nandroid of bone stock then another for your custom settings...
Mardenator said:
So I recently rooted my LTE Tab 10.1 after some errors on my part. I finally got root, and the bootloader unlocked (thanks to six5alive's post here) Here's what I have:
CWM recovery
unlocked bootloader
Rom Manager installed
SU permissions
I've tried flashing two different ROMs, and both flash without a problem. But when I attempt to reboot, I get the Samsung logo and a yellow triangle below it, and then the tablet shuts down. At first I thought it was just the ROM, but after flashing two, I'm getting suspicious. I have a Nandroid backup of the stock rooted ROM, and that restores & boots properly every time.
What am I doing wrong?
Click to expand...
Click to collapse
What roms did u flash...?
Sent from my GT-P7500 using XDA App
Strange, when I flashed the ISI-Galaxy rom on my P7100 i got then same thing as you, when i turned the device off it automatically went back on with the same result. I had the idea that i was going to have to bring it back to the shop for repairs but... This happened while i was at work. So i placed the Tab in my backpack but when i got home a half an hour later the device was functioning again. So maybe yours needs some time to get over this 'boot up'.
ZangetsuNX-01 said:
Strange, when I flashed the ISI-Galaxy rom on my P7100 i got then same thing as you, when i turned the device off it automatically went back on with the same result. I had the idea that i was going to have to bring it back to the shop for repairs but... This happened while i was at work. So i placed the Tab in my backpack but when i got home a half an hour later the device was functioning again. So maybe yours needs some time to get over this 'boot up'.
Click to expand...
Click to collapse
Tried this, got the same result I've been getting..
I flashed these, wiped after flashing each one obviously.
http://forum.xda-developers.com/showthread.php?t=1372432
and
http://forum.xda-developers.com/showthread.php?t=1155023
Both caused the triangle issue, so I just restored the rooted stock ROM I'm running.
Mardenator said:
I flashed these, wiped after flashing each one obviously.
http://forum.xda-developers.com/showthread.php?t=1372432
and
http://forum.xda-developers.com/showthread.php?t=1155023
Both caused the triangle issue, so I just restored the rooted stock ROM I'm running.
Click to expand...
Click to collapse
Next time please use the edit button.
I think I have an explanation as to why its crashing. The ISI-Galaxy Rom and P7500XWKK4 Galaxy Tab 10.1 / HC 3.2 ROM are for the P7100 model. Yours is the SCH-I905 model so the roms you tried to flash are incompatible.
Just realized that ZangetsuNX-01 is right, I've been flashing WiFi-only ROMs, not ROMs for the Tab 10.1 LTE. Downloading http://forum.xda-developers.com/showthread.php?p=17858660#post17858660 now, will flash and post results here asap.
UPDATE: got a leaked TW ROM to install via Odin and boot, posting this from the tablet. Added a screenshot for kicks.
BTW, for anyone with an LTE Tab, flash this via ODIN NAO!!!!
http://rootzwiki.com/topic/10463-ro...x-leak-build-for-vzw-galaxy-tab-101-lte-only/
It's unrooted, with stock recovery, but you can follow the directions on the page to get root, it's simple. Just Odin a recovery .tar file, go to recovery, flash SU zip, and voila. Running it at 1.4GHz max, 1GHz min, and it's awesome. TouchWiz is also a nice step up from stock HC.
@Mardenator
your screenshot a looke liek from my adwluncher from my tab...
Lol I'm using ADW Ex.
ok i dont untersant waht you with them post, sorry.
Conan179 said:
ok i dont untersant waht you with them post, sorry.
Click to expand...
Click to collapse
I'm not sure what the question here is, but I was suggesting that if you have an LTE Galaxy Tab 10.1, you should flash the ROM that I provided a link to. It's a good ROM, and I've been running it for 2 days now.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
Hi!
So I followed Djembeys guide to root my s4 back when ME2/MF2(or smthn in that matter)was the newest firmware avable. But now I wanted to go back to stock and update my phone and as stated in the guide that would be no problem, well OTA didn't work so i did it via Kies. It worked as expected for a while before my phone started freezing and rebooting itself forever, like as soon as i get into the launcher.
Things I've tryed to do:
*Checking in download mode that everything is official, it is, and the phone doesn't seem to reboot while in download mode, should I flash a stock rom, I mean, what if the phone shuts off in the middle of the process?
*Doing a factory data reset via stock recovery, the "android" in recovery falls down and a triangle at his stomach. However the data reset worked, but it didn't solve the problem, still reboots but now when the phone is trying to set itself up.
What can i do guys? You think i can send it back to the store seeing everything is official in download mode?
NidexX said:
Hi!
So I followed Djembeys guide to root my s4 back when ME2/MF2(or smthn in that matter)was the newest firmware avable. But now I wanted to go back to stock and update my phone and as stated in the guide that would be no problem, well OTA didn't work so i did it via Kies. It worked as expected for a while before my phone started freezing and rebooting itself forever, like as soon as i get into the launcher.
Things I've tryed to do:
*Checking in download mode that everything is official, it is, and the phone doesn't seem to reboot while in download mode, should I flash a stock rom, I mean, what if the phone shuts off in the middle of the process?
*Doing a factory data reset via stock recovery, the "android" in recovery falls down and a triangle at his stomach. However the data reset worked, but it didn't solve the problem, still reboots but now when the phone is trying to set itself up.
What can i do guys? You think i can send it back to the store seeing everything is official in download mode?
Click to expand...
Click to collapse
Which s4 is this? This is the sprint variant. Post it in the appropiate s4 of your carrier. You can try to odin back to stock.
Sent from my SPH-L720 using xda app-developers app
ROMANTiC KiD said:
Which s4 is this? This is the sprint variant. Post it in the appropiate s4 of your carrier. You can try to odin back to stock.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Aww really, i totally missed that this was for sprint:/. I have the NEE version(unbranded GT-I905). Are you sure i can flash stock, what if it would reboot while flashing? It is already stock, just that I have this damn problem with the reboots;(
Mine did some of that kind of thing when I first went to MF9 a few days ago. I think the reason I had the problem was because I did a nandroid recovery using a custom recovery (TWRP). I think (but have no proof) that it overwrote some of the MF9 stuff with MDL stuff. So to fix it, I redid everything and recovered my apps and data through Titanium Backup instead. All good now.
Follow the directions I posted yesterday in the following thread to get to unrooted, stock MF9:
http://forum.xda-developers.com/showthread.php?t=2427006
jejb said:
Mine did some of that kind of thing when I first went to MF9 a few days ago. I think the reason I had the problem was because I did a nandroid recovery using a custom recovery (TWRP). I think (but have no proof) that it overwrote some of the MF9 stuff with MDL stuff. So to fix it, I redid everything and recovered my apps and data through Titanium Backup instead. All good now.
Follow the directions I posted yesterday in the following thread to get to unrooted, stock MF9:
http://forum.xda-developers.com/showthread.php?t=2427006
Click to expand...
Click to collapse
It worked fine and your phone didn't reboot in download mode? I've tested to be inside download mode for around 10 min, so i guess it's fine if i flash stock rom.
NidexX said:
It worked fine and your phone didn't reboot in download mode? I've tested to be inside download mode for around 10 min, so i guess it's fine if i flash stock rom.
Click to expand...
Click to collapse
I'm not exactly sure what you're asking, but the phone worked fine once I redid it. Before that, it would have random boots, and then multiple boots like a boot loop. But it never did more than 2 boots before actually coming up. But it would reboot after a while. BlueTooth would not turn on, stuff like that. It just was not right. But the redo with the TiBu restore worked great. I'm now very stable on MF9, rooted, stock rom.
jejb said:
I'm not exactly sure what you're asking, but the phone worked fine once I redid it. Before that, it would have random boots, and then multiple boots like a boot loop. But it never did more than 2 boots before actually coming up. But it would reboot after a while. BlueTooth would not turn on, stuff like that. It just was not right. But the redo with the TiBu restore worked great. I'm not very stable on MF9, rooted, stock rom.
Click to expand...
Click to collapse
nvm dude, seems like it's hardware failure. I tried flashing it with stock MGA firmware and the problem remains, as well as the screen ****ing up just before it is about to reboot. Well, thanks anyway!
sph-l720 4.3 rooted by cf auto root
I put system files in the phones framework folder to hack free hotspot. I rebooted and the phone was stuck on the yellow sprint logo. I pulled the battery and used odin to i guess flash mf9, then cf auito root. last time i was stuck on this screen this worked.
But now i'm screwed.
I tried a wipe factory reset and it still didn't help.
I flashed a kernel zip file using odin by accident (KERNEL - SPR _ L720vpuamf9-1372121308)
now it boots and gets stuck at the same screen but the screen is blank. only the blue light lights up.
any clues???
now it says set warranty bit kernel, when it used to say set warranty bit recovery
You cannot go back with Odin to MF9 once you are on MjA.
Sent from my SPH-L720 using Tapatalk
.....
EDIT NEVER MIND I didn't see that first part about 4.3!
Hello Sprint I've got a TEP claim for you.
Okay well maybe not totally there yet. There are a couple threads on how to get 4.3 to boot do spend some time searching reading, and then read and look some more. Good place to start would be here
brewmanate said:
sph-l720 4.3 rooted by cf auto root
I put system files in the phones framework folder to hack free hotspot. I rebooted and the phone was stuck on the yellow sprint logo. I pulled the battery and used odin to i guess flash mf9, then cf auito root. last time i was stuck on this screen this worked.
But now i'm screwed.
I tried a wipe factory reset and it still didn't help.
I flashed a kernel zip file using odin by accident (KERNEL - SPR _ L720vpuamf9-1372121308)
now it boots and gets stuck at the same screen but the screen is blank. only the blue light lights up.
any clues???
now it says set warranty bit kernel, when it used to say set warranty bit recovery
Click to expand...
Click to collapse
Flash KT kernel 4.3 if you are on mja, that should fix it, if not, make sure you have a custom recovery(not TWRP) and flash the stock 4.3 rom in the dev section
thank you...
negamann303 said:
Flash KT kernel 4.3 if you are on mja, that should fix it, if not, make sure you have a custom recovery(not TWRP) and flash the stock 4.3 rom in the dev section
Click to expand...
Click to collapse
i just have to get it replaced.
I never fully rooted. I had stock recovery and binary ond kernel. I just has su.
I screwed the pooch on this one. Thanks anyway guys. I will get a new one. Or maybe a note 3 in its place. What do you think?
If you can get to download mode it's not bricked
Sent from my SPH-L720 using Tapatalk
Your not bricked
This is exactly the same issue I had. You tried to downgrade after upgrading and flashed some stuff to fix it right? Yeah bad idea. Anyway.
Go to this thread http://forum.xda-developers.com/showthread.php?t=2506562
Follow it step by step. It solved my issues.
I already sent it out to be replaced
I have insurance through a 3rd party, so it might be forgiven that I rooted it. If not, and they send it back to me, I will have to rely on all your helpful guidance. I am very grateful. You guys rock.
Just so its as clear as can be, here is a list of my mistakes. LOL
1. I did try to take the OTA update. It didnt take and only messed with storage for some reason. Not broke yet.
2. Flashed back to MF9 with Odin 3 v.1.87. Oops.
3. Flashed MF9 and CF auto root a few times back and forth trying to get it to take.
4. It is a bit hazy here, but I tried to use odin 3.07 to go back to mf9, but it wouldn't work. I instead used odin to root the f#cker and to my amazement it worked. Now I was rooted on 4.3! MJA I got the idea from this thread>>>>>>>>http://forum.xda-developers.com/showthread.php?t=2511209
5. Then it was all gravy for a few days minus the annoying security notifications every so often about an app trying to access the system..blah blah blah. I wanted my hotspot hack back (the entire reason for the root) so I placed the altered system files in the framework to allow for hotspot service
and rebooted. Thats when **** got real. it booted up to the full yellow screen that shows the sprint logo. The blue led was strobing slowly and it just stayed that way for a few minutes. I got scared and tried going through steps 1 through 4 again to no avail.
6. Then I really messed up and flashed the MF9 Kernel zip file by mistake or maybe more out of desperation, and all that did was make the screen black after the samsung logo, but the blue led still illuminated.
All well, I already sent it out. I should get a new one soon.
If they dont let me swap it I will upgrade to the note 3.
Any ideas about the note 3 vs the sgs4, except for the obvious size and Ghz difference?
So I rooted my phone months ago, found a KK ROM I was happy with and never had any issues, until last night.
My battery died. When I went to plug it in and power it on, it went to the Samsung Galaxy Note 3 screen with the pad lock unlocked on it. I then noticed on the top right it said recovery booting. I figured no biggie, I'd let it boot to recovery and then reboot. Well it never got into recovery, and restarted, yielding the same results after a restart. So basically, my phone is on for about 5 seconds, then shuts off and tries again.
I tried to pull the battery and left it out over night. This morning I pushed the recovery button sequence to make sure the power was completely drained then reinserted the battery. As soon as I put the battery in, it starts to boot, shows booting recovery, then loops. I tried plugging in to my PC to see what happened and that didn't help. Is my phone screwed or what should I do to try to fix this?
Can you get into download mode
waco2hot33 said:
Can you get into download mode
Click to expand...
Click to collapse
Yes I can! Wasn't abled to last night but now I can. What version of odin do I need and what firmware do I flash?
instant3 said:
Yes I can! Wasn't abled to last night but now I can. What version of odin do I need and what firmware do I flash?
Click to expand...
Click to collapse
Nc4 firmware and odin 3.09
waco2hot33 said:
Nc4 firmware and odin 3.09
Click to expand...
Click to collapse
After I falsh in ODIN, do I have to reroot, reinstall safestrap, etc?
instant3 said:
After I falsh in ODIN, do I have to reroot, reinstall safestrap, etc?
Click to expand...
Click to collapse
That is correct.
gmskking said:
That is correct.
Click to expand...
Click to collapse
I am thinking I want to try out JasmineROM 2.4 out. Do I need to flash the unified KK firmware in ODIN prior to install? I tried flashing without doing this and it just fails immediately. I see that the unified KK firmware is there so I was just wondering. Also, when I flash that, do I just do it in ODIN in the PDA box, same as I flashed the nc4 firmware yesterday? Thanks for your help, fellow Iowan!
I had this happen recently. I had to go back to a complete stock NC4 stock 4.4.2 and reroot and go from there. I used a newer version of Odin though.
Hey wassup. So yesterday I rooted my phone and tried to install CM13 on it. Took a few tries since the rom I got was corrupted but I got it to work. Then I noticed it was guzzling the battery like lemonade (this EXACT same thing happened on my previous S4 too) so I gave up on it and decided to revert back to the stock rom. Everything went well... NOT. I downloaded the stock firmware (3gigs... zzz) and I flashed it with Odin and the phone restarted. The little android robot from the default unrooted recovery popped up and it had below it this: "Installing system update..." and then out of the blue it said "Erasing" and it's gear started rotating backwards. THEN, when it finished the normal Samsung Galaxy Note 4 logo popped up, went away and then CAME BACK AGAIN FOR LIKE 500 TIMES AND COUNTING. AOSP roms work just fine, it's just that touchwiz ones won't work whatsoever (even tried sixperience, no luck)... What should I do? I already lost my S4 due to this...
install TWRP custom recovery, boot up in recovery format system dalvik cache and internal storage then try flashing stock with odin hopefully it will work.
Try to remove battery first.from tsoch recovery wipe data cache and see if it works
dork997 said:
install TWRP custom recovery, boot up in recovery format system dalvik cache and internal storage then try flashing stock with odin hopefully it will work.
Click to expand...
Click to collapse
Been there, done that. Nope, still refuses to work :/
bumpity bump bump
Did you backup your efs partition before you flashed cm13? If not you corrupted your efs and your phone is a wifi tablet now because you cant use your modem.
travis82 said:
Did you backup your efs partition before you flashed cm13? If not you corrupted your efs and your phone is a wifi tablet now because you cant use your modem.
Click to expand...
Click to collapse
this never happened to me with my old s2 or s4
why is it happening now ?
Didn't backup. Now it just won't even work with odin. Whenever I try to just flash anything with it goes off and says 0 successes and 0 fails. What I did notice though was that whenever I installed a stock rom it starts this "Installing system update" with the android robot twingling it's antennaes and then out of nowhere it's blue bar goes away and it says "Erasing" then... bootloop. Now odin won't even work (explained above). Should I just give up and send it in for repairing? Or can ANYONE send me the twrp restore file, please...
Peontikos_Desmos said:
Didn't backup. Now it just won't even work with odin. Whenever I try to just flash anything with it goes off and says 0 successes and 0 fails. What I did notice though was that whenever I installed a stock rom it starts this "Installing system update" with the android robot twingling it's antennaes and then out of nowhere it's blue bar goes away and it says "Erasing" then... bootloop. Now odin won't even work (explained above). Should I just give up and send it in for repairing? Or can ANYONE send me the twrp restore file, please...
Click to expand...
Click to collapse
Hi
Same problem
Any ideas !!!
Hey,
I have the same problem it turns out after flashing, i cant remember, maybe dytto note 4 rom, it got stuck in continous bootloops and the only way it is working for me is when its charging. I know it sounds crazy but its the only way for me, ive tried installing stock different countries firmware and bunch of custom rom with no luck. I sent it to the place where i bought the phone and made myself look dumb asking why it is like that and i told them i had not do anything. After only a week they phoned me and said it was rooted (i did get the root out when i gave it but they somehow knew it was... later i understood that it is all about that stupid Know thing) and refused to cover my warranty. They said that the only way i can get it to work is to pay 300$ for new chip :,(
senon said:
Hey,
I have the same problem it turns out after flashing, i cant remember, maybe dytto note 4 rom, it got stuck in continous bootloops and the only way it is working for me is when its charging. I know it sounds crazy but its the only way for me, ive tried installing stock different countries firmware and bunch of custom rom with no luck. I sent it to the place where i bought the phone and made myself look dumb asking why it is like that and i told them i had not do anything. After only a week they phoned me and said it was rooted (i did get the root out when i gave it but they somehow knew it was... later i understood that it is all about that stupid Know thing) and refused to cover my warranty. They said that the only way i can get it to work is to pay 300$ for new chip :,(
Click to expand...
Click to collapse
ffs i'm not paying another phone's worth in a ****ing motherboard. I tried:
-Flashing the stock bootloader, fails at sboot.img:NAND Write start fail
-Flashing the PIT file, just... wont flash. Successes 0/Fails 0
-Flashing the stock AP file, bootloop
-Flashing the CP and the CSC stock files, serial(com) port cannot be opened.
****ing garbage. For some reason my phone's the only exception to the rule that phones able to boot into download mode are salvageable. It's going in for a repair and if it's more than $50 I'm not rooting again even at gunpoint.
Quick update:
I found a toolkit that has a flash stock boot image option. Had to recover to my cm13 backup to enable usb debugging. Will post results
Nothing of course...
try this step by step,
1. Download stock firmware THE LATEST ONE (n910c v5.1.1) from sammobile.com
2. Download newest Odin and Samsung USB; installed Samsung USB
3. I am assuming you have installed twrp recovery. Boot to twrp recovery and do a full wipe; wipe all!
4. Boot to downloading mode and install stock via odin. That is it.
Ps.... in case of failure, make sure you have installed Samsung USB! Or just reconnect usb cable with other usb ports untill it is working.
Never flach cm if doesn'T HAVE a efs backup if not you will stuck with cm
Oliva.raiders said:
1. Download stock firmware THE LATEST ONE (n910c v5.1.1) from sammobile.com
2. Download newest Odin and Samsung USB; installed Samsung USB
3. I am assuming you have installed twrp recovery. Boot to twrp recovery and do a full wipe; wipe all!
4. Boot to downloading mode and install stock via odin. That is it.
Ps.... in case of failure, make sure you have installed Samsung USB! Or just reconnect usb cable with other usb ports untill it is working.
Click to expand...
Click to collapse
Well, crap I already sent it in for repairing but if the fuqing robbers decide to change the motherboard instead of doing anything to it and charge me 500$ to do so I'm getting it back and I'm trying this one. Already did but it wouldn't hurt retrying... BTW FOR THE LOVE OF GOD DOES SOMEONE HAVE A TWRP BACKUP FILE ON STOCK TOUCHWIZ? JESUS
radium56ad said:
Never flach cm if doesn'T HAVE a efs backup if not you will stuck with cm
Click to expand...
Click to collapse
Is there absolutely NO workaround?
i had the same issue, this is how i solved this (you won't like it):
-deleted efs partition
-restored 5.1.1 coj5 via odin
-then took it to a samsung repair center to restore the imei
paid them like 50 bucks...that sucks. after this im backing up efs folder before flashing a rom.
radium56ad said:
Never flach cm if doesn'T HAVE a efs backup if not you will stuck with cm
Click to expand...
Click to collapse
JuanWilliman said:
i had the same issue, this is how i solved this (you won't like it):
-deleted efs partition
-restored 5.1.1 coj5 via odin
-then took it to a samsung repair center to restore the imei
paid them like 50 bucks...that sucks. after this im backing up efs folder before flashing a rom.
Click to expand...
Click to collapse
Oh that's nothing man. The fuqing scammers told me the whole freaking board had to be replaced...
There's one thing I've noticed though that's PROBABLY gotta be the culprit. Whenever I install a touchwiz rom, the phone boots up fine for once, shows the robot with the "Installing system update" and then it goes off with "Erasing" followed by the bootloop. Could anyone please elaborate on this? I have a feeling this is what's causing this ****fest