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
Hello, My desperation level is at it's climax.
I got my hands on "Galaxy S4 Black Edition GT-I9050" I wanted to install kitkat firmware, i did everything as usual, i deleted the system folder on my S4, When i wanted to install the ROM, I found out that my phone was not reading the SD Card on Recovery Mode... Clockwork recovery mode. I formatted my SD Card in all formats, FAT,Etc. Still no hope, Than i wanted to restore to the original firmware by flashing the phone with odin, because my phone wont boot, it's stuck at the boot screen.
I downloaded countless firmwares, some of them Fail at MDM, and other fail right of the bat
Things that i have done:
Installed Samsung Drivers, uninstalled them.
Tried Different USB Hubs, Cables.
Tried many versions of Odin.
Nothing works.. I am really sad.
My Device: Galaxy S4 Black Edition
Model: GT-I9505
Problem, Unable to Flash Back/Phone stuck at boot screen
PS: I did research on how to restore stock firmware, etc, But nothing helps.
I really need your help! Cheers
I believe, and don't quote me on it, but that the black edition version of the s4 have slightly different firmware. Have you looked on sammobile for firmware specified for the black edition?
Sent from my GT-I9505 using XDA Free mobile app
What happens when you try to flash with a different recovery? Try Philz or TWRP.
But the Black Editions model number is i9506, no?
Lennyz1988 said:
What happens when you try to flash with a different recovery? Try Philz or TWRP.
Click to expand...
Click to collapse
Thanks for replying, I Downloaded both, Only philz is working fine, however I still don't see my external SD Card, Only internal one is there..
I found black edition firmwares, but as i am downloading one by one, nothing worked so far.
The firmware is located here : androidromupdate.com/2014/02/06/i9505xxuena4-4-3-firmware-samsung-galaxy-s4-gt-i9505-black-edition
Edit: I found specific Black edition firmware on sammobile, once i try them, i will post back here,
I tired flashing again but still no hope. What i am doing wrong? is it the firmwares? please help.
mangomhf said:
I tired flashing again but still no hope. What i am doing wrong? is it the firmwares? please help.
Click to expand...
Click to collapse
Did you try wiping data for the bootloop issue? :/
Press Thanks if I helped
Sent from my Samsung Galaxy S4 via XDA app.
DeepankarS said:
Did you try wiping data for the bootloop issue? :/
Press Thanks if I helped
Sent from my Samsung Galaxy S4 via XDA app.
Click to expand...
Click to collapse
Things that i did:
1. Start your phone in CWM Recovery
2. Go to Advanced
3. Choose “Wipe dalvik-cache”
4. Now go to “Mounts & Storage”
5. Choose “Wipe /cache”
6. Reboot your phone
When i turn on my phone, i see the boot and on the top left corner i see a msg which says;
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: Kernel
Quick update, I finally managed to install Android 4.4 KITKAT Via SideLoad, It loaded fine, but now im facing another problem which is the Touch Screen is not working at all in the welcome menu. What could be the issue?
mangomhf said:
Quick update, I finally managed to install Android 4.4 KITKAT Via SideLoad, It loaded fine, but now im facing another problem which is the Touch Screen is not working at all in the welcome menu. What could be the issue?
Click to expand...
Click to collapse
Just do a factory reset in the recovery, but don't install the rom again.
mangomhf said:
Quick update, I finally managed to install Android 4.4 KITKAT Via SideLoad, It loaded fine, but now im facing another problem which is the Touch Screen is not working at all in the welcome menu. What could be the issue?
Click to expand...
Click to collapse
Told you. Data wipe!!!
Press Thanks if I helped
Sent from my Samsung Galaxy S4 via XDA app.
Hey everyone,
I came across a problem with my note. I was using _alexndr's rom and I thought I would give CM12 a try. I downloaded CM12 and checked the md5. The md5 was good so I made a nandroid of _alexndr's rom and installed CM12 using TWRP. As CM12 was booting for the first time, my note randomly turned off. When I tried to turn it back on, it showed the Note 4 splash screen and rebooted. It has been stuck in a bootloop ever since. I have tried using Odin to reset back to stock and I have using the emergency restore on Kies but still no luck. When I try to boot to recovery, it says recovery is booting but then it reboots to the Note 4 splash screen again. I have also tried flashing custom recoveries but it makes no difference. The only mode I can boot into is download mode. I have even tried re-partitioning using the N910F pit file but no difference. My phone is the SM-N910F (snapdragon) model. Also, I have tried searching but it seems like I'm the only person with this problem.
Anyone have any ideas? I've tried everything I can think of but nothing seems to make a difference :crying:
I'm having the same problem, but after i tried flashing twrp
thmart95 said:
I'm having the same problem, but after i tried flashing twrp
Click to expand...
Click to collapse
I haven't found a way to fix it I just sent it to Samsung and then they sent it back saying that its not in warranty anymore because its been rooted soooo... I've emailed them trying to get a quote on the cost of the repair but it takes about 3 business days for them to reply :/ I tried literally everything and I'm going to say its a hardware fault rather than software
Have you tried flashing a different recovery or flashing stock firmware again and seeing if that fixes it?
ash123456678 said:
I haven't found a way to fix it I just sent it to Samsung and then they sent it back saying that its not in warranty anymore because its been rooted soooo... I've emailed them trying to get a quote on the cost of the repair but it takes about 3 business days for them to reply :/ I tried literally everything and I'm going to say its a hardware fault rather than software
Have you tried flashing a different recovery or flashing stock firmware again and seeing if that fixes it?
Click to expand...
Click to collapse
Just flashed stock, and it worked
thmart95 said:
Just flashed stock, and it worked
Click to expand...
Click to collapse
I've flashed stock and I'm still stuck on a bootloop on either ROM or recovery mode .
Does anybody else have experience and other solutions?
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
Hi all Im a noob so apologies in advance as its the first time Ive rooted and used custom ROMS.
I rooted my phone a couple of months ago using ODIN, then successfully installed CM12.1 but found that this started to slow down and not perform well after a few weeks so I looked for other ROMs. In the end I installed BlissPop which is based on CM. This generally works really well but the software has been a big buggy as well with yesterday my main screen going black and not able to use the phone.
So ive been trying to install a different ROM and even tried to go back to the stock S5 firmware as i miss the camera in the stock firmware.
Now to install the ROMs Ive tried using CWM and TWRP with the same results.
Yesterday I tried to install The Galaxy Project ROM and the Stock Samsung ROM and in both cases made sure 100% i was using the correct version for my SM G900F .
What seems to happen is that it goes through the install process and says completed but when it boots it sits on the initial Samsung S5 boot screen and goes nowhere.
Since I rooted my phone on start up at this intial boot screen I get the below 2 messages at the top of the screen
Kernel is not seandroid enforcing
Set Warranty Bit Kernel
I'd like to add my phone is also encrypted as i had to encrypt it in order to use my gmail for work.
The only ROM that seems to work is BlissPop, i remember a message during installation of this ROM along the lines of "this install is block based" if that makes any sense.
Last week when i tried to install a new ROM on several occasions the phone would get to the first screen where it would ask me to unlock the phone but I would NOT be able to use the keyboard as no keyboard would appear.
This is driving me nuts so I really could do with some help please
Thanks Bart
Flash stock, boot into recovery, factory reset, see if it boots
just so im clear
do you mean
flash stock - via cwm or twrp in recovery
reboot into recovery
factory reset at this point
see if it boots?
bartjunited said:
just so im clear
do you mean
flash stock - via cwm or twrp in recovery
reboot into recovery
factory reset at this point
see if it boots?
Click to expand...
Click to collapse
You can't flash stock from recovery, you flash stock with ODIN - if you can flash it from recovery, it's not stock
Latest G900F Lollipop Stock ROM (BTU United Kingdom)
Code:
https://mega.nz/#!fVhhzRBC!A79uC8Fgg1mGCZOaujQCzBxcUUN9z_ctVVkigD8ffVM
Then boot into recovery and factory reset
ok well that could be my probllem
never flashed stock rom thru odin
do i set phone to download as normal , connect phone to pc and choose AP option in ODIN?
downloading the stock rom you sent a link for too
Yep, AP or PDA section in ODIN, same download mode method as anything else in ODIN
I assume that I don't need to extract the zip file and just select it to flash
Sent from my Samsung Galaxy S5 using xda-developers.com, powered by appyet.com
bartjunited said:
I assume that I don't need to extract the zip file and just select it to flash
Sent from my Samsung Galaxy S5 using xda-developers.com, powered by appyet.com
Click to expand...
Click to collapse
Yea, extract it, it needs to be .MD5
G900FXXU1BOJ1_G900FOXA1BOJ1_G900FXXU1BOJ1_HOME.tar.md5
.ZIP is for recovery flashing
Boy I'm making all the noob mistakes aren't I
??????
Sent from my Samsung Galaxy S5 using xda-developers.com, powered by appyet.com
Don't worry, we all learned from somewhere - as long as you ask before jumping in and bricking things, it's all good
Thanks appreciated
A side question but you can tell me to get lost if I'm taking the piss
I've got multiple g mail accounts, is there a file anywhere that saves all the credentials so that when I have to rebuild my phone for the umpteenth time I can restore this and not have to set each one up
Sent from my Samsung Galaxy S5 using xda-developers.com, powered by appyet.com
bartjunited said:
Thanks appreciated
A side question but you can tell me to get lost if I'm taking the piss
I've got multiple g mail accounts, is there a file anywhere that saves all the credentials so that when I have to rebuild my phone for the umpteenth time I can restore this and not have to set each one up
Sent from my Samsung Galaxy S5 using xda-developers.com, powered by appyet.com
Click to expand...
Click to collapse
If you have Google Backup enabled, it should restore your accounts and stuff once you log back into the main Google account your phone was logged into before you wiped/reset/reflashed I would assume (Not used it though)
arghhh bugger
so it seems to have flashed the rom correctly and booted.
however after boot as my phone is encrypted it asks me for my password to unlock the phone.
i put in my correct password but it doesnt accept it.
going round in circles - what can i do?
rebooted info recovery and factory reset it
now im in and looks like back to stock
will keep you posted
Im finally back in now
Thanks so much for your help
hopefully this runs better than the last stock rom as it started to seriosuly slow down hence looking at other roms
Good job