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
over the last few days I've flashed a number of ROMs, mostly the Google Edition 4.2.2 and 4.3 ones and every single one of them eventually fails to boot hanging on the Samsung bootloader screen. and i say eventually because the first boot is almost always flawless, but then each time i reboot or power down, its almost guaranteed to loop.
I've tried so many different combinations that there's really not a single path I've taken every time, but the general steps are:
-root original firmware using motochopper
-install TWRP via GooManager
-reboot recovery and wipe everything, typically I do Advanced and select everything, then format Data
-then flash through ADB sideload, I do this since I wipe everything before flashing and I don't have an external SD card
-immediately after flashing ROM, I flash loki-doki also through ADB sideload. some of the ROMs I tried said they were lokied, but I still got the ATT invalid ROM message, so I reflashed with loki and it worked.
-then reboot system and the first time it comes up and works fine on every ROM I've tried
But if I power down or restart, on a very rare occasion it'll come up, but almost every time it hangs on bootloader screen. I also noticed once it's stuck on bootloader, power button becomes unresponsive, sometimes holding it powers down device, sometimes does nothing (have to press and hold twice)
If I flash back to stock using Odin, it works, boots, reboots, powers down just fine.
I've also tried flashing with a ROM and then immediately after with the stock ATT kernel, also booted up fine, but looped on restart.
Could this be hardware issue?
I'm about to give up on this and go back to stock for good, which would be really disappointing, can anyone help?
Flash a KT kernel and see what happens, I suppose you know which one correct?
TheAxman said:
Flash a KT kernel and see what happens, I suppose you know which one correct?
Click to expand...
Click to collapse
I assume KT means http://forum.xda-developers.com/showthread.php?t=2292341 ?
I've tried that too with jamal2367's 4.2.2 GE ROM (http://forum.xda-developers.com/showthread.php?t=2341794). It refused to boot all together.
First time I flashed with AOSP version since I thought that was an AOSP ROM, then reading more comments in the other thread it said I needed the TW version for GE ROMs, so I tried that too. Either way, neither of them booted at all, even the first time, so I gave up on KT and only used either ROMs' included kernels or ATT stock.
It is not a hardware issue, I am guessing that you have a US ATT G4 correct? I would odin back to stock, and restart the process again, this is assuming you tried the correct TW kernels. Because I know this error and all it requires is a simple flash of the correct kernel.
TheAxman said:
It is not a hardware issue, I am guessing that you have a US ATT G4 correct? I would odin back to stock, and restart the process again, this is assuming you tried the correct TW kernels. Because I know this error and all it requires is a simple flash of the correct kernel.
Click to expand...
Click to collapse
OK I'll try one more time from scratch, can you verify I'm using the right stuff though for US ATT Galaxy S4:
ROM: http://forum.xda-developers.com/showthread.php?t=2341794
Kernel: http://forum.xda-developers.com/showthread.php?t=2292341 (TW one, specifically http://goo.gl/SiDjB)
And any idea why the ROM's kernel wouldnt work after being lokied?
collegebored said:
OK I'll try one more time from scratch, can you verify I'm using the right stuff though for US ATT Galaxy S4:
ROM: http://forum.xda-developers.com/showthread.php?t=2341794
Kernel: http://forum.xda-developers.com/showthread.php?t=2292341 (TW one, specifically http://goo.gl/SiDjB)
And any idea why the ROM's kernel wouldnt work after being lokied?
Click to expand...
Click to collapse
You know, I don't even look at anything that says loki anymore, I flash the rom I want and use MY carriers kernel, bootloops and hangs are just not there, I do not see these issues everyone has, because, I have this procedure everytime. So...
Btw, your good on your files you want to flash, but, if this does not work ie, GE and that kernel, try a TW rom with the kernel, bet it boots properly. I do not give a rats
a$$ about goole roms. They are not worth it. Btw, I use this procedure on TW and aosp roms, no issues. Just because it says it loki'ed, flash the kernel you know works, loki just confuses people.
The Ax says again an again..My opinion only!
Good luck sir.
BTW, I ran that rom with the kernel you chose, it should work just fine. Remember, flash the TW version.
Thanks Ax for your help here, your welcome.
Normally I take for granted that the answer is out there in a forum or some tech blog. I've looked everywhere and unfortunately every guide I followed or Google combination I've tried didn't help.
Just can't get any custom rom to install and boot up, they all hang at the Samsung logo with text in the upper right corner telling me the kernel isn't senforcing.
I have a sgh i337m, it's an mk6 build number if that helps. Currently on stock 4.3 and rooted using saferoot. My carrier is telus and the phone is Sim locked still (is that the issue?)
I have twrp 2.6.1 installed and have flashed multiple roms for the jfltecan which I trust is the right model I need based on goo.manager
I've tried cm11, cm10, gummyrom for 4.4.2, omnirom also for 4.4.2 and they all hang at the splash screen. My method for flash is based on the ultimate guide that is stickied which is to wipe system, data and both the caches. Then flash the zip and the gaaps. I even tried the lokidoki zip in other combinations
Then I tried using cwmod recovery thinking perhaps it is twrp's fault and got the same hanging at the splash screen
I'm now just back to rooted stock 4.3 after restoring my nandroid
Any insights out there that can be deciphered from my rambling would be very much appreciated!!! Frustrated as hell. My nexus 7 was such a breeze and did not expect this to happen on my s4.
wondakson said:
Normally I take for granted that the answer is out there in a forum or some tech blog. I've looked everywhere and unfortunately every guide I followed or Google combination I've tried didn't help.
Just can't get any custom rom to install and boot up, they all hang at the Samsung logo with text in the upper right corner telling me the kernel isn't senforcing.
I have a sgh i337m, it's an mk6 build number if that helps. Currently on stock 4.3 and rooted using saferoot. My carrier is telus and the phone is Sim locked still (is that the issue?)
I have twrp 2.6.1 installed and have flashed multiple roms for the jfltecan which I trust is the right model I need based on goo.manager
I've tried cm11, cm10, gummyrom for 4.4.2, omnirom also for 4.4.2 and they all hang at the splash screen. My method for flash is based on the ultimate guide that is stickied which is to wipe system, data and both the caches. Then flash the zip and the gaaps. I even tried the lokidoki zip in other combinations
Then I tried using cwmod recovery thinking perhaps it is twrp's fault and got the same hanging at the splash screen
I'm now just back to rooted stock 4.3 after restoring my nandroid
Any insights out there that can be deciphered from my rambling would be very much appreciated!!! Frustrated as hell. My nexus 7 was such a breeze and did not expect this to happen on my s4.
Click to expand...
Click to collapse
I too have been plagued by this same issue,
but only on a blue moon so to speak, I kept rebooting
and eventually my phone booted through that silly splash screen!
wondakson said:
Normally I take for granted that the answer is out there in a forum or some tech blog. I've looked everywhere and unfortunately every guide I followed or Google combination I've tried didn't help.
Just can't get any custom rom to install and boot up, they all hang at the Samsung logo with text in the upper right corner telling me the kernel isn't senforcing.
I have a sgh i337m, it's an mk6 build number if that helps. Currently on stock 4.3 and rooted using saferoot. My carrier is telus and the phone is Sim locked still (is that the issue?)
I have twrp 2.6.1 installed and have flashed multiple roms for the jfltecan which I trust is the right model I need based on goo.manager
I've tried cm11, cm10, gummyrom for 4.4.2, omnirom also for 4.4.2 and they all hang at the splash screen. My method for flash is based on the ultimate guide that is stickied which is to wipe system, data and both the caches. Then flash the zip and the gaaps. I even tried the lokidoki zip in other combinations
Then I tried using cwmod recovery thinking perhaps it is twrp's fault and got the same hanging at the splash screen
I'm now just back to rooted stock 4.3 after restoring my nandroid
Any insights out there that can be deciphered from my rambling would be very much appreciated!!! Frustrated as hell. My nexus 7 was such a breeze and did not expect this to happen on my s4.
Click to expand...
Click to collapse
First off I am hoping you are flashing from recovery and not trying something through goo manager. Second, it sounds as though you are skipping the wiping step before installing a new rom, you absolutly have to wipe cache/dalvik/ and factory reset all before flashing any rom.... also I wipe the system too to make it a clean install, make sure you put the rom of choice on the external sd and make sure you have a nanroid backup with your installed recovery twrp or cwm.....
PS lokidokie and saftey starp only apply to US versions (I337) not the Canadian I337M use only the roms build of this model.... I haven't had very good luck with cm based roms in the past so I tend not to flash those... I flashed one rom and the phone got super hot ... not sure what the issue was ... nand back to stock starter over with a differnet rom
Adizzzle said:
I too have been plagued by this same issue,
but only on a blue moon so to speak, I kept rebooting
and eventually my phone booted through that silly splash screen!
Click to expand...
Click to collapse
How long did you wait at the splash screen before booting again and again? After a new installation does the phone take extra time at the splash screen or is it at a different screen?
wondakson said:
How long did you wait at the splash screen before booting again and again? After a new installation does the phone take extra time at the splash screen or is it at a different screen?
Click to expand...
Click to collapse
Please... you need to provide some more info for people to help you..... rom you tried to install and the steps.. not tryin to be mean just hard to help without details....
Ahh I know the problem if your flashing all of them from the att section. It could be that all of those roms you tried have loki built into the kernel and is stopping you from booting. Are u choosing ones that say they are specifically for the Canadian model or the ones for att?
I would also suggest booting once first before flashing gapps. I am using this Carbon rom http://forum.xda-developers.com/showthread.php?t=2568699 and it's universal, for US or CA models. I highly recommend it.
I've recently flashed NAE modem via Odin 3.09, also flashed Philz latest recovery. I was doing this so i could flash Rawintellects Stock(ish) ROM.... which seemed so badass. Really wish i could have got it working. Anyway, on to the problem.
Firmware flash went fine, Philz reovery went fine, ROM flash went fine. Now... I BELIEVE (can't remember) that i was coming from a MDL firmware, not sure though. After ROM flash, things were glitchy. No wifi (fixed after following suggestions in his thread. No 3g... fixed after a clean wipe 3X's and fresh ROM flash. And NO SOUND... never fixed. I spent half a day trying to get it right, never could.
So I decided to try another ROM, next was Negalites WondROM. Seemed cool, but had all the same issues. Exact same. Locking up, swipe screen locking up. System crashes, random reboots. NO SOUND. Figured, WTF.... tried another ROM same issues. At this point I thought maybe all these ROMS had the same kernal and that was the issue, so i flashed dif kernals compitable and recommended for dif ROMS. ALL SAME ISSUES. From here I figured it was the NAE modem the phone didn't like for whatever reason.
So now I'm stuck. I want to start over, want to flash MDL modem again, want to put the ROM i had back on here (I believe it was BluKuban or something). I am fairly certain there is now ay to take this phone back to the store and have them repair it, they will surely find something that will void the warranty even though im also fairly certain there is no warranty left on the phone. This phone is a business phone on our business account (one of 6 phones) and we've had buisiness with this sprint location for over a decade so i amy be able to persuade a repair.
Need help guys =(
Fixed
Battery below 40 percent made this phone do some wonky things, after being fully charged this morning, i was able to use download mode and flash stock modem and revert all changes and get factory image. Lost root, recovery, and roms. But everything is back to normal.
Got the info i needed to do this from this guys thread, the only other thread that i found with the same symptoms and issues as me: http://forum.xda-developers.com/showthread.php?t=2662491
WOOHOOO!!:good::good:
ograyray said:
Battery below 40 percent made this phone do some wonky things, after being fully charged this morning, i was able to use download mode and flash stock modem and revert all changes and get factory image. Lost root, recovery, and roms. But everything is back to normal.
Got the info i needed to do this from this guys thread, the only other thread that i found with the same symptoms and issues as me: http://forum.xda-developers.com/showthread.php?t=2662491
WOOHOOO!!:good::good:
Click to expand...
Click to collapse
NAE wont work on my phone with any ROM, same issues. MF9 works just fine so I don't bother. You could have just ODIN'ed the modem only rather than losing everything.
tensux said:
NAE wont work on my phone with any ROM, same issues. MF9 works just fine so I don't bother. You could have just ODIN'ed the modem only rather than losing everything.
Click to expand...
Click to collapse
Thanks, at that point I was happy to get anything to work, nothing lost really, just maybe 4 or 5 roms, a few GAPS packages, dealing with realizing I flashed a 4.4.3 image though.... And reading through everything looks like there is no root method available for 4.4.3 yet.... BUT HEY, got the phone functional and usable.
You can still root your phone...nothing you have done is final
Sent from my SPH-L720 using XDA
tensux said:
You can still root your phone...nothing you have done is final
Sent from my SPH-L720 using XDA
Click to expand...
Click to collapse
I like two things. 1. Phone works 2. 4.4.3 is fast and battery life is awesome so far. I do hate the bloatware and bright ass yellow splash screen on boot. But i believe i can stick with this until root for 4.4.3 is out.
Gonna miss my ROMs till then. Unless you can find root method for 4.4. It's out for S5 but not S4. I'd be shocked if i was wrong.
You should read up a bit... No reason you can't be rooted on 4.4.3
Sent from my SPH-L720 using XDA
running stock rom on stock rom slot everything works fine, when i install a custom rom to rom slot 1 and boot to custom rom the rom works and does everything it should but i am not able to reboot or power off my phone. it does this if i am on custom rom or stock rom. when rebooting or powering off it gets stuck right after logo of rom goes away and stays there with led light, back arrow and open apps keys lit up. i have to remove battery and boot that way. after i wipe/ delete custom rom from rom slot 1 and everything works fine ??????
Dpike698 said:
running stock rom on stock rom slot everything works fine, when i install a custom rom to rom slot 1 and boot to custom rom the rom works and does everything it should but i am not able to reboot or power off my phone. it does this if i am on custom rom or stock rom. when rebooting or powering off it gets stuck right after logo of rom goes away and stays there with led light, back arrow and open apps keys lit up. i have to remove battery and boot that way. after i wipe/ delete custom rom from rom slot 1 and everything works fine ??????
Click to expand...
Click to collapse
If you would have read numerous threads on the issue you would have known. Instead you found out the same way I did some weeks ago!! There are known bug issues with Safestrap that cause the problems you are experiencing when using a rom slot. Use the stock slot only and all will work well. Yes, this means you have to wipe out your stock S5 system, but you can always odin back to stock.
Chopstix9 said:
If you would have read numerous threads on the issue you would have known. Instead you found out the same way I did some weeks ago!! There are known bug issues with Safestrap that cause the problems you are experiencing when using a rom slot. Use the stock slot only and all will work well. Yes, this means you have to wipe out your stock S5 system, but you can always odin back to stock.
Click to expand...
Click to collapse
With our build you pretty much have to treat safestrap like any other custom recovery. Most other recoveries that I'm aware of don't have various slots for you to dual boot stock and custom roms. Making a backup within safestrap is definitely recommended before you wipe the stock rom slot that way if you want to go back, you won't need to recover with odin. Not saying that's a bad way to go, just a little inconvenient.
Sad to say the developer of our recovery if off doing other things. I don't know if this rom slot one issue is something that can be patched within the recovery, or it's it's more of a ROM developer kind of thing, but I don't see that getting fixed any time soon.
DJNads said:
With our build you pretty much have to treat safestrap like any other custom recovery. Most other recoveries that I'm aware of don't have various slots for you to dual boot stock and custom roms. Making a backup within safestrap is definitely recommended before you wipe the stock rom slot that way if you want to go back, you won't need to recover with odin. Not saying that's a bad way to go, just a little inconvenient.
Sad to say the developer of our recovery if off doing other things. I don't know if this rom slot one issue is something that can be patched within the recovery, or it's it's more of a ROM developer kind of thing, but I don't see that getting fixed any time soon.
Click to expand...
Click to collapse
No it won't... Hash said in the safestrap thread that he was shutting down deveopment work on it... the only hope would be that another dev dives in to it.
Chopstix9 said:
No it won't... Hash said in the safestrap thread that he was shutting down deveopment work on it... the only hope would be that another dev dives in to it.
Click to expand...
Click to collapse
Considering it's open source, I'm hoping it won't be too long before another developer picks it up. (PlayfulGod maybe? )