Related
EDIT: I flashed again, without the MicroSD card (I don't know if that had to do with it), but after several tries, I was able to get to TWRP and root
Hey everyone!
I followed this post:
http://forum.xda-developers.com/tab-4/general/root-galaxy-tab-4-7-t230-t2835264
I tried twice, first with the auto reboot option checked in Odin, then, unchecked.
Both times I can't enter download mode.
When I try, I see the Team Win logo for a fraction of a second and then it resets.
Team Win logo
Any ideas?
Thanks!
Anyone? I'm afraid of trying other downloader and messing things up, since TWRP seems to be corrupted. I've checked the MD5 hash of the file before flashing, BTW.
Could be a device compality issue? What device do you have? Did you make sure of flashing the right one? It looks like it flashed correctly but doesnt work on your device.
Hey, thanks for the reply.
Well, I have SM-T230NU (compatible) with build KOT49H.T230NUUEU0ANE2, for which I haven't found any mention regarding whether or not it should work. I guess it should, it's not the latest.
Any ideas on how to proceed? TWRP is the only way to root, right? I haven't found any.
Hello my fellow XDA Members. I am stuck in a tight spot and after reading and re-reading some things the situation doesn't look very promising. I hope this is the moment that Karma shows up and I can get some help on this. Here it goes.
Specs - LG G2 D801 Variant > TWRP V2.8.3.1 > NO OS Currently
I was running Cloudy G3 Rom smoothly and got bored and decided to flash that new rom that is a 5.0 Rom all variants. Did the usual back ups and flashed it. Something happened when I flashed the rom. It went through the Aroma installer and then said "successful" but stuck in a bootloop. I tried it again and nothing happened. Then I tried to wipe everything again and started getting an E: Cannot mount (data or system I forget which as that error went away after I completely formatted data, wiped everything and reflashed Cloudy Stock. )
> Cloudy stock bootlooped and nothing is happening in TWRP. I Am using the USB OTG method of getting files on the phone and getting it charged but anytime I try to do anything (flash a rom, an older version of TWRP) it just immediately restarts TWRP and thats that. I have No OS at all.
> I tried to use one of the methods to get into download mode and flash a stock KDZ but the phone acts like it is going into DL mode (shows the little blue transition screen) but never gets into the ACTUAL download mode where the PC or flash tool can recognize it.
So in a nutshell > No OS > I can get into TWRP but it does nothing > No Download Mode > Don't want a new phone > Don't want to take it apart and try to short circuit anything if possible. LOL.
I am totally stuck here. I am done alot of work and even helped friends and family out with their devices over the years. I am just not sure if I need to consider it a done deal and get a new phone or maybe one of you guys know of something easy and obvious (please let it be the latter) I am missing. Thanks for any help you can offer. I Will be standing by.
Have you tried to reflash bootloader? If not, do that and reflash cloudy right away
wisefreakz said:
Have you tried to reflash bootloader? If not, do that and reflash cloudy right away
Click to expand...
Click to collapse
I haven't thought about flashing a bootloader. How would I flash the bootloader if I can not the phone into either DL mode and or TWRP doesn't do anything either? Is a bootloader file just a flashable file like any other .zip file?
jcnbama said:
I haven't thought about flashing a bootloader. How would I flash the bootloader if I can not the phone into either DL mode and or TWRP doesn't do anything either? Is a bootloader file just a flashable file like any other .zip file?
Click to expand...
Click to collapse
@jcnbama
Have you tried this or this?
euphoria360 said:
@jcnbama
Have you tried this or this?
Click to expand...
Click to collapse
The first one I can not do as I do not have any knowledge at all of Ubuntu, Linux, or any of that. It would take forever to get a working knowledge of that software in order to get things going again. I would probably just have to either take it to a cellphone repair shop or get another phone before I could do the first link.
I have not tried the second one but it is a viable option. I was looking at it online and trying to talk myself down from having to do that. I would reallllllllly rather not have to take my phone apart if I can keep from so that's kind of what this post is all about. Just trying to see if anyone knows of ANYTHING else before I go taking apart my phone.
Can you describe more about "twrp doesnt do anything"?
Does twrp boot up?
Can u see/wipe partitions?
Can u install any rom in twrp? Does it finish?
euphoria360 said:
Can you describe more about "twrp doesnt do anything"?
Does twrp boot up?
Can u see/wipe partitions?
Can u install any rom in twrp? Does it finish?
Click to expand...
Click to collapse
TWRP boots and I can go into wipe, advanced wipe, and format data and it says it's successful. I can use file manager and move items back and forth from USB OTG. If I try to flash anything it just reboots TWRP immediately so I can't install any .zip files at all.
My guess is that your bootloader is damaged.
The only option i can see for you is that Ubuntu thing i shared with you. So, lets stop acting lazy and do what needs to be done. Dont scare since there is nothing to loose. LG G2 is unbrikable
Booting up ubuntu or any other linux os is so easy. And there is nothing much to learn. Trust me.
Go to ubuntu website and download their newest iso file. Burn it on dvd and boot it up. You dont have to install it, just choose "live mode" and it boots up. Just like that. Then yiu can proceed with tutorial mentioned above and it shouldnt take more than an hour from you. Its all typing some commands in terminal (remember CMD in windows!).
Just make sure to download the files mentioned in that tutorial before proceeding.
euphoria360 said:
My guess is that your bootloader is damaged.
The only option i can see for you is that Ubuntu thing i shared with you. So, lets stop acting lazy and do what needs to be done. Dont scare since there is nothing to loose. LG G2 is unbrikable
Booting up ubuntu or any other linux os is so easy. And there is nothing much to learn. Trust me.
Go to ubuntu website and download their newest iso file. Burn it on dvd and boot it up. You dont have to install it, just choose "live mode" and it boots up. Just like that. Then yiu can proceed with tutorial mentioned above and it shouldnt take more than an hour from you. Its all typing some commands in terminal (remember CMD in windows!).
Just make sure to download the files mentioned in that tutorial before proceeding.
Click to expand...
Click to collapse
First of all calling people lazy is not nice. I'm not lazy I am trying to play it safe. I wouldn't want to brick it to the point to where I don't even have recovery and it can not even be charged any longer. I have Ubuntu on my desktop upstairs. I have used it a little. It's not that I am completely ignorant to Ubuntu I am just a total novice. Also the issue described in that post doesn't exactly match my situation. I am not in a black screen. It's more like a bootloop that I can not get out of because TWRP is not doing what it needs to do and I can not flash TWRP a ROM or get into DL mode at all. Also that post says,
"VERY IMPORTANT!!!!!!! You must use the img files that correspond to the ROM you have installed before getting the problem to avoid breaking your phone."
I don't have a rom on my phone soooo...
You didn't answer my question well. If on TWRP you can finish installing rom without any error, and you keep coming to twrp after restarts, that's another situation. Try this:
http://forum.xda-developers.com/showthread.php?t=2451696
But if you cant even finish install in twrp (twrp gives you errors or just restarts before giving you "successful", either you have problem in rom you try to flash or you need to build everything up from start.
That lazy thing was for encouraging you to do it.
And you cant brick your device. There is always a way on G2.
For img files: find them from last stock rom that was working on your phone.
Deleted
First want to say hi and that this site is full of knowledge so any help with my subject will be great.
Got a att s4 sgh-i337 phone. I rooted it before the lollipop ota update was out and everything went fine. Then the lollipop update came out and I followed one of the methods on keeping root and updating to 5.0.1 lollipop on the phone. Everything went fine with that. Still showed root status and never did the phone brick or have any issues in the updating.
At some point though, I did run triangle away because I would have the custom logo and opened padlock when the phone would boot up. I knew it wasn't a huge deal but the counter showed correct and never could just figure out how to get it to go away. Either way, I did run it and I think rebooting twice, the factory loading image came back to it. Now it shows my current status as 0 for the counter and the binary is Official.
I have not tried to load any roms or nothing like this to the phone, just followed the instructions to give it root access so I could run a few different apps and adaway for when I listen to Spotify.
One day, I was trying to install a new version of Words with Friends and it failed because I think wwf was open, but I did go back and install it. For some reason now, my phone never notifies my with a wwf notification when somebody plays me. Every now and then, it might pop up when I restart the phone but that is it. I don't think facebook notifies me everytime also but was more worried about words with friends.
Searching google, it says to go into recovery mode and flash the cache of the phone there. I have done the cache memory in the phone but that has not fixed my problem. When trying to go to recovery, it never works, it would always show, recovery booting and then load the phone up as normal.
I have download quick boot and rom manager since they all have an option to boot into recovery rather than pressing the buttons but it always does the same thing. Reading the web though, it seemed like I needed to install a different recovery than the factory I guess, so using rom manager, I tried twrp and that didn't work so I installed ClockworldMod 6.0.4.7. Rom manager shows that as the current recovery method.
When I try to boot into recovery, it still shows that recovery is booting and then goes straight to loading the phone as it should normally.
Now though, every time I restart my phone, it says recovery is trying to boot but never does.
How do I fix my phone to be able to boot into recovery and it not try to boot every time it powers on. I have tried searching google but I just just can find an answer to my direct problem. I know how to hold the buttons and go to recovery but does not work, and I also know how to get to it from the different app programs(rom manager and quick boot) but they do not work either. It would be nice to get the wwf notifications to work properly again also.
If you need any information from my phone, please ask. Thanks for any help on my matter,
Charlie
Odin stock and start over.
Apparently, you are not aware that the boot loader is locked, preventing the installation of a custom kernel. You can not use twrp, or rom manager. Rom manager itself may cause issues.
I agree you should flash back to stock and start over to get a clean install. Hopefully, this will solve the issues with notifications as well. You can use the "[GUIDE]Odin to Stock, Updating, Rooting, and Installing Safestrap" by guut13 in the general forum for files and instructions.
creepyncrawly said:
Apparently, you are not aware that the boot loader is locked, preventing the installation of a custom kernel. You can not use twrp, or rom manager. Rom manager itself may cause issues.
I agree you should flash back to stock and start over to get a clean install. Hopefully, this will solve the issues with notifications as well. You can use the "[GUIDE]Odin to Stock, Updating, Rooting, and Installing Safestrap" by guut13 in the general forum for files and instructions.
Click to expand...
Click to collapse
Thanks for the replies guys, I really don't know a whole lot about rooting other than following instructions about it. I was unaware you could not use the twrp or cwr as a recovery. My recovery did not work before so that is why I was trying to install those. I knew you could not install custom roms but I did not know that you could not use rom manager to install custom recoveries.
I appreciate the help so far and I will look into that thread you mentioned. I haven't read it but will this take me back to stock lollipop 5.0.1 and I just reinstall apps or will I have to re-root the phone.
Charlie
please delete, sorry
Charlie
You have to go back to 4.4.4, to the nb1 base, root with towelroot, and then use the keeproot method to get back to 5.0.1 rooted. The instructions are in the guide, and also a link to the keeproot thread is there.
By the way, for future reference, questions, help and troubleshooting issues should go in the Q&A forum, not the general forum.
not having any luck
Ok guys,
I am trying to follow the guide but not having much luck.
I downloaded the I337UCUFNB1_4.4_Stock_Odin_tar and put it in the AP Odin file. I'm not sure if I should be using it or the other file named I337UCUFNB1_4.4_Rootable_Stock_Odin_tar to begin with. The instructions said to use the first one so that is the one I was trying to use.
After putting the first file in the AP slot of Odin and hitting start, it begins to try to do it's thing and then says it fails!
What do I do now? Am I doing something wrong or what because I'm trying to follow instructions but not having much luck.
Please help. Sorry for posting in the wrong area also in the beginning.
Charlie
I'm screwed
Now when I turn my phone on, it says Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again?
doing better now
Pretty sure I got it going finally. I changed cords and then changed ports on my computer and it finally did go back to stock without an error. I'm currently back on Lollipop and rooted so now is the fun of reinstalling contact info and anything else. So far I have not rebooted but it was not showing the recovery booting option when it did reboot. Hoping my notifications work properly now also!
Thanks!!!
Charlie
Started off by unlocking the bootloader on the December update (just got device the other day)
Used @munchy guide to install twrp and root the device
everything looked great
backed up stock
flashed everything but internal storage
installed lastest version of AOSiP
crashed during install so I thought ok, bad download. did a restore and got an error that system wasn't mounted. unchecked the box under mount, and restored. I reboot and all hell has broken loose. Fore close left and right. I go back to try and get to TWRP, and it's stock Recovery.
Follow guide again and get back into TWRP. I see that all my stuff is still there. So I do some reading and saw some folks having similar problems with TWRP not sticking, so I find some instructions in the TWRP thread that I need to flash the TWRP image to both slots, run the install patcher and should be all set. I do that...wipe again, restore and now I am in a continuous bootloop. I tried to switch slots, do a restore on the other slot....bootloop.
I feel really stupid and really bummed out that even with all my years and experience, I somehow found myself in this noob trap. Is anyone able to help me at least get back to just stock? All I really want at this point is to be back on stock with root so I can run an ad blocker. Thanks everyone
Mods - could you please close? I know have a hardware issue (lol), a rubber ring on the inside of USB port has come out and wedged inside the port, rendering the device defective. Thank you
Okay, so this is an interesting story...
I helped a friend out because he wanted to root his tablet bad for some reason, he knew I was a nerd, so he trusted me with this task. It's a delicate process, I know, but the next day I gave it back to him, successfully rooted (TWRP recovery and Magisk installed) a few days later he gave it back to me again saying I should adapt the storage. Samsung locked this function long ago, I told him it's risky, but he still insisted on doing it. I used a program called Root Essentials. It needs a plugin to use adaptive storage. This is where the tablet started acting up. I couldn't install the plugin, or for that matter anything in TWRP, because it constantly failed. The installation through Root Essentials failed immediately, it just booted my device into TWRP recovery, doing nothing. I tried making a backup, failed, because it couldn't access the "/data partition" or whatever. I tried going back to Root Essentials and I must have accidentally clicked on something I shouldn't have, because after I turned off the tab, it wouldn't boot again. It would put me in ODIN mode saying
"Invalid boot image header
Can't get fdt" (I have a pic of this)
Twrp still works, tried everything from wiping the cache to wiping the full device and factory reset it. Considered flashing a new boot image, but I'm not sure where to get it from. (i can't confirm the build number and stuff like that)
I hope I could give y'all a decent explanation, because I honestly have no clue where I messed up.
We're talking about a Samsung Galaxy Tab A (2017) SM-T380
Whoever helps me out, god bless you...
MrUncle said:
Okay, so this is an interesting story...
I helped a friend out because he wanted to root his tablet bad for some reason, he knew I was a nerd, so he trusted me with this task. It's a delicate process, I know, but the next day I gave it back to him, successfully rooted (TWRP recovery and Magisk installed) a few days later he gave it back to me again saying I should adapt the storage. Samsung locked this function long ago, I told him it's risky, but he still insisted on doing it. I used a program called Root Essentials. It needs a plugin to use adaptive storage. This is where the tablet started acting up. I couldn't install the plugin, or for that matter anything in TWRP, because it constantly failed. The installation through Root Essentials failed immediately, it just booted my device into TWRP recovery, doing nothing. I tried making a backup, failed, because it couldn't access the "/data partition" or whatever. I tried going back to Root Essentials and I must have accidentally clicked on something I shouldn't have, because after I turned off the tab, it wouldn't boot again. It would put me in ODIN mode saying
"Invalid boot image header
Can't get fdt" (I have a pic of this)
Twrp still works, tried everything from wiping the cache to wiping the full device and factory reset it. Considered flashing a new boot image, but I'm not sure where to get it from. (i can't confirm the build number and stuff like that)
I hope I could give y'all a decent explanation, because I honestly have no clue where I messed up.
We're talking about a Samsung Galaxy Tab A (2017) SM-T380
Whoever helps me out, god bless you...
Click to expand...
Click to collapse
Just flash the latest stock firmware. The build number doesn't matter...
you can get the stock firmware here: https://www.sammobile.com/samsung/galaxy-tab-a-2017/firmware/#SM-T380
JJcoder said:
Just flash the latest stock firmware. The build number doesn't matter...
you can get the stock firmware here: https://www.sammobile.com/samsung/galaxy-tab-a-2017/firmware/#SM-T380
Click to expand...
Click to collapse
Ur like 9months late replying lol way to revive dead thread