Hello!
This is about an old model of phone, so chances are I am in trouble.. but will describe the problem specifically.
Was a normal S4 mini without modifications - turned on USB debugging, installed Samsung Kies, and Odin, and got started on this guide: (https://forum.xda-developers.com/t/root-samsung-galaxy-s4-mini.2387341/)
Went into "download mode", ran Odin, it detected my device, installed "GT-I9195_MF5_870901_kernel.tar.md5" as PDA within Odin (all files are on the forum post linked above)
After this, device rebooted, as per the guide.. then I had trouble getting into the "download"/"recovery" environment again for some reason, and in frustration, unplugged/plugged cable, and after this didn't work, closed and reopened Odin. Now the problem is the guide explicitly says "Do not close Odin", and this is where the issue came up.
Holding volume up + power + home, takes me to "android system recovery <3e>", which I'm guessing is where I should be, but however Odin does not recognise the device now, and in fact, in this recovery environment, I don't think it's recognised by my PC even, so I guess that's why both install steps had to be done in one go... Now, my phone has options such as "reboot system now", "apply update from ADB", etc, and other stuff, but I am not able to figure out what to do next, and so as a result, the phone is just not useable for me. (blurry picture attached)
Some notable details from the blurry picture are:
"KOT49H.I9195XXUCOE4" (at the top of the screen)
"# MANUAL MODE "
--- Appling Multi-CSC...
Applied the CSC-code : KOR
Successfully applied multi-CSC." (at the bottom of the screen)
Notably if I let the phone try to boot normally, it does get detected by my PC and by odin, but if I try to install something to the device with Odin, it falls over, something to do with being unable to establish connection probably because the phone is in the wrong mode. It would not be the end of the world if the phone was bricked forever but man would I feel like ****
Update: turns out there are two different things you can boot to, via the volume up + down buttons, my stupid ass didn't clock this, so got very confused. Now was able to follow the steps in their entirety, however phone is still not booting into OS, despite now having custom recovery.
After doing some research, seems that the issue stems from this:
BOOT LOADER AP SWREV:2
Apparently REV:2 can't be flashed with anything custom, and bricks the phone, and rev:2 is what I have. Whilst this will certainly put an end to my days of referencing old forum posts for stuff like this, at the very least I have a broken S4 mini with a perfect 16 Gb motherboard I can swap out, my bro's old one, he's not too happy but understands.
Related
Ok,I tried to install a different OS, on my phone via ODIN, i couldnt get it right the first couple of times so i kept doing more research. SO after i THOUGHT i had a solution i tried again. i was on the last step of the finalization and it said " about two minutes left" or something like that, and i waited about 40 minutes and it still said the same thing. so i thought i'd UNPLUG IT AND TRY AGAIN. well now after i do so,
i try to plug my device in again and it doesn't read it at all, This ALL HAPPENED AFTER THE PHONE ENCOUNTERED THE FIRMWARE PROBLEM WITH THE PHONE... WARNING SIGN... AND COMPUTER.
the only thing i was able to do was go to recovery mode, or download mode. CAN NOT GET INTO THE PHONE. now i'm smart enough to click an option on the recovery menu, but my power button or home button, or ANY Button, would not respond, besides the volume buttons to go up and down. So since the computer will not detect it, i dont know what to do, and i am using the factory cables, and i tried KIES AND ODIN. I have uninstalled drives in and out. still no solution, i read posts ever since last morning until now and decided to create my own posts for my own problems and seek help from people like ones on here who ACTUALLY KNOW WHAT THEY ARE DOING.
it starts up as Samsung GT-i9100 and they goes to Android System Recovery <3e>
and below reads in yellow,
Deleting Cryptoin Meta Data
--Copying media files...
Successfully copied meida files.
# MANUAL MODE #
--Updating application...
Successfully updated application.
--Appling Multi-CSC...
Successfully applied multi-CSC.
and shows and android robot with a white triangle and Orange ! mark in the middle.
The crazy thing about it is that i could use a button as an (Enter key) before i tried to flash my phone , before that i just cleaned the memory,
and once again after i removed phone from ODIN at about 98% im guessing, after i waited 40 minutes when it said about 2 minutes remaining. i was not able to try any other solution or connect to my laptop. and ive tried others, and my other phone connects fine. so i know i did something wrong....
Please Assist me, i'd really appreciate the time and effort,
I rooted my phone successfully, tweaked a couple roms successfully as well. The last rom I tweaked was I think something to do with init.d. After I tweaked the rom, I restarted my phone and bam... that $H1T stood stuck at the boot animation loop a.k.a BRICKED.
I downloaded odin and some tars, but before that I deleted partition erased in recovery mode holding up and power button. I went to download mode using down and power button. I failed 9 times using odin, and then eventually I got the box screen to display "PASS" with a green color. I restarted the phone and it had a different model lol. However my phone still did not get back to the way its suppose to start up. I tried using new files for ODIN, and everything seemed about right until it said: Wait about 2 minutes, it was the last step I think and I was actually waiting 15 minutes, so I got anxious and unplugged it and restarted my phone and it shows a different model instead of SPH-D710 it shows GT-19100 and goes straight into recovery mode.
All I can do is scroll up and down using volume buttons but I cant hit the (ok button) which is the (power button) to attempt the action I want. I have a boost mobile samsung galaxy S2. Also Odin, Kies and my Computer does not recognize my phone anymore through usb. I tried usb samsung drivers update, and I even tried a bunch of different versions of ODIN including a different computer. My downloads folder is literally packed with a whole bunch of tool aid kits for my phone lol. OH and by the way before I used odin I did end the process of Kies in the task manager so yup. I do not know what else to do, I tried different computers I think I am pretty much PHUCKED over now. Unless someone has another solution.
I do not understand why I cant enter nothing in recovery mode all of sudden, I can only move up or down. I can only go into either recovery mode or download mode. In recovery mode it says:
Deleting Cryption Meta Data
-- Copying media files...
Successfully copied meida files.
# MANUAL MODE #
-- Updating application...
Successfully updated application.
-- Appling Multi-CSC...
Successfully applied multi-CSC.
If it shows I9100 on the boot screen instead of SPH-D710 you've obviously used firmware for the I9100 on your device, and there's a fair possibility you'll be making a trip to a service centre.
Find stock SPH-D710 firmware, flash that with Odin. Where ? No idea, like most people here know almost nothing about this model; try the usual haunts - Samfirmware, AndroidFirmwares.Net, Samsung-updates.com, Google search),.
To start off, I suffered, what seems to be a common problem, of the fingerprint unlock on Samsung Galaxy S6 Edge randomly being unable to recognise my fingerprint. Followed by my back-up password not being accepted. Unfortunately, I turned off my data and wifi before the phone locked so the problem doesn't seem to be able to resolve itself unless I Factory Reset the phone.
This i am happy to do as long as I can find some way to retrieve the media files from the phone (just pictures and videos). I read up and watched some videos where some people were able to use ADB through Recovery Mode or Field Test mode, and pull the files from the phone. These people however were using older models of Android phones but I decided to read numerous pages etc and go ahead and try.
I set up everything (I believe) i needed on my Mac Book pro in order to use the Adb Terminal. However when I tried to connect my phone Adb couldn't detect my device. I then decided (after reading somewhere to do so) to press "Apply update using ADB" on the Recovery menu. Again, Adb did not detect my device.
i left this screen up on my phone which resulted in "dm-verity verification failed..." appearing at the bottom of the screen. It then switched back to the Recovery menu and continues to show "dm-verity verification failed..." at the base of the screen. Now when I try and power up the phone normally, the start up screen just repeatedly flashes and it goes no further than that.
Im not completely brain dead when it comes to this stuff but I obviously don't fully understand what I am doing, So Im wondering if there is a genius out there who, even after what I've done, can help me pull the files from my phone before I have to Factory Reset!
The problem is, that you don't have the ability to use adb pull through the stock recovery. This kind of thing can only be done via a custom recovery like TWRP, CWM, or Philz. Now that it's not booting, pretty much the only thing to try is to install a custom recovery and boot directly into it before it tries to restart. Make sure you find one for the correct variant of your phone. If yours is a VZW or ATT version, you're in trouble because they don't have custom recoveries like that for them.
I've followed these instructions to the tee but have not had any luck with getting this to work. The flash always just results in my phone getting stuck on the "recovery booting.... recover is not seandroid enforcing - Set Warranty Bit : Recovery" screen. Odin reads as "PASS!" but my phone seems like it's just stuck. I've scoured over dozens of forums searching for answers but what works for others just doesn't seem to be working for me.
The instructions all seems so clear, and multiple forums' instructions gave me confidence that this would work no problem as long as I followed the instructions precisely. I guess that wasn't the case. I can't afford a new phone right now, but I'm sure my phone isn't completely bricked. There's gotta be a way! Can you please help me, xda community?
EDIT: I forgot to mention that I also tried the "uncheck the Auto Reboot option" method, and I'm a little confused about the last sentence. See below:
NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
I'm confused about the "This will start the install process" sentence. I flash, let it finish until Odin says "Pass!", remove the battery, boot into recovery, and then I have two options from there - I can either go into download mode again, or I can start the phone normally. Starting the phone normally just brings me right to the recovery mode which gets stuck there indefinitely. I've left it there for 15+ minutes and it still just stays stuck there.
EDIT 2: Exactly how long is it suppose to take to boot up after it's been flashed?
EDIT 3: IT WORKS. So, If you just sort of hold down all the buttons at the same time, the phone will restart a few times and eventually bring you into the TWRP menu. This is what I was unaware of before. I'm not exactly sure what the specific method or timing is for that, but just tinker with holding all the buttons, and I think you can let go when you see little blue letters on the top left that says recovery or something. Of course, being able to access the TWRP menu means you must first have flashed the TWRP thing, which I did using Odin. Just download the latest TWRP .tar file and flash it with Odin.
EDIT4: SUCCESS! I am now successfully rooted! I reflashed the twrp-3.0.2-2-klte.img.tar and then I was able to access the actual GUI. I guess what I had before was some super stripped down version of the TWRP that only gave me access to a command-line looking interphase in recovery mode, with very limited options. So there you go, if you find yourself looking at pictures on forums of a supposed TWRP with an actual GUI you can navigate, that's because it does exist! Download the one I just mentioned, flash it using Odin, and boot it up by holding VolumeUP, Home, and Power. From there you can flash Zip files, just put the zip files into an sd card. I put my zip right into the sd card, not even in it's own folder or anything.
that version (8/26/2016) does not work at all for g900t, Maybe Chainfire wants to shut down CF_auto_root method.
you need to try the previous version (02/28/2016), I doubt you can find the old version in their website, Try google it on internet.
goog888 said:
that version (8/26/2016) does not work at all for g900t, Maybe Chainfire wants to shut down CF_auto_root method.
you need to try the previous version (02/28/2016), I doubt you can find the old version in their website, Try google it on internet.
Click to expand...
Click to collapse
Interesting, thanks for the info! Funny enough, while I was at Best Buy last night, I decided "what the heck" and asked a Geek Squad guy about my phone, and told him how I attempted to root and now it wouldn't boot, etc. He took my phone, and just sort of held all the buttons together and it restarted a few times, and he just kept fidgeting with it until eventually it came up to the TWRP recovery menu! So, I did a factory reset and started up the phone. It is currently on 5.1.1. I have since been able to get myself into the TWRP recovery menu by fidgeting like he did, even though I'm not entirely sure what exactly the timing or button combos are. The Geek Squad guy said he just held down ALL buttons, even VolumeUp and VolumeDown at the same time. So whatever, TWRP menu IS accessible finally.
At this point, I'd prefer to flash CM13 to it, and apparently I can just put the CM13 file on my phone storage/sd card, and then flash it through the TWRP recovery menu. But since I factory reset my phone back to 5.1.1, should I first update my radios? A techy friend of mine introduced me to a new fear - that if you flash a ROM that is incompatible with an older radio, it could "hard brick" my device. So now that's where I'm at. I want to flash a rom to gain simple root access, but don't want to risk bricking my device.
Here is my phone's information:
SM-G900T
Android 5.1.1
Baseband version G900TUVU1FOG6
Build Number LMY47X.G900TUVU1FOG6
I don't know how to mark this solved, but it is, as described my my 4th edit in the original post.
**The problem as it stands**
My Galaxy S6 Active is stuck in a sort of bootloop, except it never seems to attempt a boot. If it was turning on, without any combination of keys, it would go to the "No Command" screen. From there all I can do is force reset (power + volume down) to get it to restart to the same place or as it displays the Samsung splash screen, press volume up + power + home, it goes to the download screen. From the download screen, I can use my pc to flash a rom (that may not be correct) to the device and according to Odin, that is a success but my device freezes on "erasing".
Imgur album with pictures of the accessible screens (http://imgur.com/a/Rd9ND)
**Description of the problem when it was booting**
At seemingly random times, the device would freeze and the only way to get it to do anything was to reset it. Sometimes it would enter a bootloop but through key combinations, I would be able to get it out. One time after a bootloop, I had the sense to back up the device's storage, so luckily I have that.
**What I've done**
- I have tried wiping the storage in device recovery -- when it was accessible, I can no longer get to it.
- I have tried using Kies/Smart Switch emergency software recovery -- but when provided with the model name and serial number they would both crash.
- When the device booted, I tried using the standard recovery feature in Smart Switch. I can't remember the exact message but it was something along the lines of "This device does not support initializing"
- I have tried using Odin to flash ROMs (again, I may be using this incorrectly) to the device. I have only tried Samsung release ROMs, meaning ones that have not been modified by a 3rd party. I followed the second and third methods of a guide on XDA forums (https://forum.xda-developers.com/ga...e/downloading-flashing-att-galaxy-s6-t3260744). Odin never throws an error and it always says it was successful. During the device's initialization with this new ROM, it gets to 32% then goes to "Erasing". A few seconds later the animation freezes. I can leave the device here for hours but nothing happens. So I believe more than the animation is frozen.
- I tried using ADB recovery via the device's recovery mode (when it was accessible) but from what I can gather, Samsung uses a proprietary ADB interface that would not work with what I was trying to do (I was following method 3 of the previously mentioned guide (https://forum.xda-developers.com/ga...e/downloading-flashing-att-galaxy-s6-t3260744). I would always get a message saying "ADB server out of date".
I may have done more than that but that's what I can recall.
Any help would be appreciated. Even if you know of a better place to post this, let me know.
Thanks
My s6 active did the same thing on 08/24/17. I have not yet found a solution.