Database Users

[Q] Phone has no recovery and other issues.

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

Another noob to the slaughter... Softbricked my i9505. Any advice?

Note: Moved thread
Hey guys,
Sorry to be one of those d**ks who registers and first post is asking for help >_<
Take a seat and join me on this epic quest of failure, which has been my life for the last 12 hours.
Had this phone since release, over the years it has got more and more bogged-down with crap, even from the word go it had tonnes of bloatware installed, but I always avoided the temptation to root, just because I didn't want the hassle if something went wrong... lol.
Yesterday decided to finally take the plunge and root it, whatstheworstthatcouldhappen.jpeg
Here's how it went down....
1. Kingoroot via PC (first tried the apk but it wouldn't work).
2. Hated all the additional stuff that had been added to the phone (new wakeup screen with ads etc)
3. Used a guide to remove and replace kingoroot (kinguser, kingroot, kingmaster) with superuser. zidroid dot com/how-to-get-ride-and-replace-kinguser-with-supersu-app/ <<Here's the guide
4. Stuck on "Installing, please wait" (just after step 8 in the guide)... as the guide explains, if this happens then reboot. So I did...
5. Phone now won't get past the samsung logo (I die a little inside).
6. Google crap for a few hours (Boot into recovery mode etc) I clear cache, remove data.
7. Try loading a stock rom I downloaded and opening it from the sd card... no joy
8. Try Kies... no joy
9. Try Odin... no joy
10. During all of this frantic messing around I loose the option of booting into recovery mode, now I can only get to download mode.
11. Basically spent about 6 hours last night and a few hours this morning trying to get this fixed from all info I could find online... STILL NO JOY.
So now I'm biting the bullet and having to own up to the public, that's you guys.
Anyone here got a clue as to what may have gone wrong/what I can do to resolve this?
Not even fussed about keeping the phone stock, just need it running something!
As I'm sure you can tell I'm new to messing around with android, but I'm not entirely tech-naive so hopefully with some help I might be able to get this back to more than just a paperweight?
Cheers!

Altum said:
Note: Moved thread
Hey guys,
Sorry to be one of those d**ks who registers and first post is asking for help >_<
Take a seat and join me on this epic quest of failure, which has been my life for the last 12 hours.
Had this phone since release, over the years it has got more and more bogged-down with crap, even from the word go it had tonnes of bloatware installed, but I always avoided the temptation to root, just because I didn't want the hassle if something went wrong... lol.
Yesterday decided to finally take the plunge and root it, whatstheworstthatcouldhappen.jpeg
Here's how it went down....
1. Kingoroot via PC (first tried the apk but it wouldn't work).
2. Hated all the additional stuff that had been added to the phone (new wakeup screen with ads etc)
3. Used a guide to remove and replace kingoroot (kinguser, kingroot, kingmaster) with superuser. zidroid dot com/how-to-get-ride-and-replace-kinguser-with-supersu-app/ <<Here's the guide
4. Stuck on "Installing, please wait" (just after step 8 in the guide)... as the guide explains, if this happens then reboot. So I did...
5. Phone now won't get past the samsung logo (I die a little inside).
6. Google crap for a few hours (Boot into recovery mode etc) I clear cache, remove data.
7. Try loading a stock rom I downloaded and opening it from the sd card... no joy
8. Try Kies... no joy
9. Try Odin... no joy
10. During all of this frantic messing around I loose the option of booting into recovery mode, now I can only get to download mode.
11. Basically spent about 6 hours last night and a few hours this morning trying to get this fixed from all info I could find online... STILL NO JOY.
So now I'm biting the bullet and having to own up to the public, that's you guys.
Anyone here got a clue as to what may have gone wrong/what I can do to resolve this?
Not even fussed about keeping the phone stock, just need it running something!
As I'm sure you can tell I'm new to messing around with android, but I'm not entirely tech-naive so hopefully with some help I might be able to get this back to more than just a paperweight?
Cheers!
Click to expand...
Click to collapse
Your mistake was using Kingroot.
Use CF-Auto-Root next time.
And what does "Try Odin... No joy" mean?
Did it fail or did it successfully flash and still didn't boot?
The procedure to flash with Odin is something like:
Download a stock ROM (should have the .tar extension)
Get a good USB cable (preferably the original one) and connect it to a back USB port (any other ports can cause problems) and to the phone.
If flashing fails, try a gain.

You could have avoided this had you just downloaded the correct cf-auto root file and flashed it via Odin..

P9 Lite - can't access developer options and phone soft reboots when uninstalling app

Here's the story:
After I've broken my screen and voided my warranty. I've decided to root my phone. Some time after, I got a notification that a new system upgrade was released, which was supposed to update my phone to Nougat and EMUI 5.0. After I installed the update I've noticed that my root was gone. Eventually I've decided to root my phone back, but something went wrong.
Now I can't access developer settings, every time I click on it Settings crashes. And every time I go and try to uninstall an application the phone soft reboots.
I've tried to clear dalvik cache trough TWRP, didn't work.
I've done a factory data reset didn't fix anything.
I can't uninstall apps trough ADB since I need to enable USB debugging and I can't get to dev options.
I can't authorize the PC either because the authorization popup doesn't appear and I think it's because the dev options don't work. As such I can't use the toolkit to do anything.
I tried to follow the steps from the Unbricking tab from the toolkit: I flashed the boot, system, recovery, cust images and stopped at the point in the instructions where I had to use TWRP. I stopped because I can't flash TWRP anymore. I flashed it at least 10 times but it didn't work, every time I boot into recovery I get the stock huawei recovery.
Is there any way I can fix this, or is my phone "half bricked" for good?

Use dload to get back to mm and from mm use firmware finder and proxy instal b370 . PV . Don't instal anything else cuz everything else will make ur phone act like that again .

ScaleneVirus288 said:
Use dload to get back to mm and from mm use firmware finder and proxy instal b370 . PV . Don't instal anything else cuz everything else will make ur phone act like that again .
Click to expand...
Click to collapse
Sorry for taking so long, I've been pretty busy, but I finally got a chance to try what you said.
It worked, and it was very simple to do.
Thank you very much, I can use my phone as intended now.
I have one more question tough, if u don't mind. Since you said not to install anything else since the phone will act up again, does that mean there is no way to root my phone? And if there is, can you point me to a tutorial?
Again, thanks a lot.

ZePuff said:
Sorry for taking so long, I've been pretty busy, but I finally got a chance to try what you said.
It worked, and it was very simple to do.
Thank you very much, I can use my phone as intended now.
I have one more question tough, if u don't mind. Since you said not to install anything else since the phone will act up again, does that mean there is no way to root my phone? And if there is, can you point me to a tutorial?
Again, thanks a lot.
Click to expand...
Click to collapse
Sorry but I don't use xda much often . U can root it , I said don't instal anything else that .pv . I said it about Rom , u can eazy root it

Can get to CWM Recovery, but can't sideload

So, I can't remember what I did to this device, exactly. I got it already in a bootloop. I had seemingly fixed it for a few weeks, but then it started rebooting randomly and then eventually got into another bootloop. I can't remember if that just happened one day or if I was trying to fix the random reboots.
I stopped working on it when a family member gave me their old Nexus 5X. But the other day my Nexus 5X entered into a bootloop because of its well known hardware problem (I think anyway, I wasn't doing anything that should have bricked it). So I decided to pull out the old Galaxy s5 and see if I can fix that instead.
Normally when I flash ROMs onto devices, I do it when the process for the device is pretty well established. As we all know, Samsung devices aren't the easiest to work with. So I remember having to do a bunch of extra ****, download Odin and so forth.
By the way, I have the AT&T G900A version. I boot into recovery and see that it boots into CWM, thats good news obviously. I pick "update through adb". I run ADB through command prompt (btw, someone should update the guides on this site to mention that Powershell doesn't play nice with ADB commands, that was like 20 minutes of hair pulling frustration) and it recognizes the device. I wipe all the user data and cache etc and attempt to flash a custom ROM I found on this site: APTOS found here.
I get an
Finding update package. . .
Opening update package. . .
Verifying update package. . .
E:footer is wrong
E:signature verification failed
So then I downloaded the stock firmware ROM titled "SM-G900A 4.4.2 G900AUCU1ANCE Firmware.rar" and get the same errors.
So, obviously I am forgetting something. I know there are a lot of guides on here and the answer is probably out there somewhere, the problem is that most of those guides are for people starting at square 1 without CWM or TWRP installed. Can anyone help me from where I am at? I uninstalled Odin a while ago but could definitely reinstall it. Was hoping to do this from where I am at, since CWM is already installed.
Anyone have any ideas on what step I'm forgetting? Do I need to flash other things before the ROM? Should I just start completely over with ODIN and the rest of it?
P.S. I have more experience with TWRP than CWM but I remember having trouble getting TWRP to work but did manage to get CWM to install as an alternative.
Thanks in advance!

Help I broke my boot loader

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