Hi all! I have been trying to fix this tablet for weeks. It's an SM-T580 Galaxy Tab A 10.1 tablet. It's actually my girlfriend's tablet and she tried to root it first and she royally screwed it up and I am having a lot of trouble cleaning it up.
So, when I got to it, she already had it stuck on the downloader mode and if you tried to boot it, it went to the blue screen that says "An error has occurred while updating the device software. Use the Emergency recovery function in the smart switch PC software."
So here is everything I did as well as I can remember it:
1. Tried every version of smart switch and KIES software. It does not recognize it ever.
2. Tried to flash custom recovery, but FRP lock is still enabled. She must not have correctly changed the settings in the tablet before beginning the root.
3. Tried to flash stock firmware, but it says it needs to be repartitioned. I downloaded what I thought was the pit file, and repartitioned the chip, but it still won't successfully boot. I tried several different cables and ports.
4. Tried to flash probably 10 different firmwares to see if anything would stick. Used several different versions of Odin all the way from 1.3 up to 13.5. Nothing will successfully boot.
5. Found stock recovery (I believe) and got stock recovery on there but when i get to recovery it says it can't mount anything. It gets a huge list of errors like "can't mount E..." I am able to ADB sideload, but so far nothing I try to sideload works because it says it has the wrong footer and the wrong signature.
Am I boned? She left it plugged in for like a week at least, so my assumption is the emmc chip burned out. Any and all help massively appreciated!
Related
So yeah, i rooted my samsung galaxy fit earlier today with no issues, then proceeded to flash a rom. After receiving many errors (e-big partition size, usb not accessible etc) i now cannot turn my phone on as i get stuck at a screen with a picture of a phone and a computer with a warning sign inbetween them.
I've been doing this between two computers, reinstalled drivers numerous times, removed the sim and sd from the phone and tried again, rebooted computers etc.
I can only access download mode, and the other mentioned screen. I can't even access recovery mode.
Every time i have tried to flash using odin i have made sure samsung kies has been shut and it's processes have been ended via the task manager.
At this point i no longer care whether or not my phone is rooted, i just care about being able to use my phone.
I cannot get Samsung Kies to recognise the phone either, on both computers. I get stuck on 'connecting'. I've reinstalled drivers several times with the same result.
Just to clarify, odin does detect the phone, with the 'healthy' yellow box.
Any kind of help is appreciated, perhaps there's a way to force a restore to the stock rom?
I'm pretty desperate.
Issue now solved. I just wasn't aware that there was a version of odin specifically for use with Samsung Galaxy Fit, Pop and Mini.
Where to start...
First, as a disclaimer, I may use language or terms that sound noobish. I have rooted and run custom ROMs on several devices in the past, however generally when I get a ROM I like I stick with it, so I'm not constantly tinkering. I've done my best to search and find solutions so please go easy on me.
17 days ago I was running stock 4.3 on my SGNII when the battery died. Upon charging I found I was stuck in bootloop and had a bad /efs mount. I searched and searched and spent around 15 hours trying this and that but to no avail. I finally threw my hands in the air and got ahold of Josh at mobiletechvideos and he was able to fix the efs mount issue. However, he left me in factory mode which required me to root to get out of, and once I did this I was unable to activate data on my carrier (Ting). I was so happy to have my phone "back" though that I used it like this for 4 or 5 days. I could get on wifi and I could call and send text messages. I had been off the grid so this felt like something I'd fix fully later.
Well I kept reading and found "fix" after "fix", flashed this and that and still no dice. FINALLY, last night, I found this thread: http://forum.xda-developers.com/showthread.php?t=2086769 which helped immensely. I was able to get TWRP flashed by unchecking the "auto-reboot" option in Odin and pulling the battery after the update took, and via TWRP I was able to install the ROM. I booted up, the device activated, I was running 4.1.2, I made and received some calls, the birds were chirping, the air was sweet...
I had struggled for so long and I had finally achieved success! Then, for seemingly no reason at all, I accepted an OTA update which bricked my Note2. Devastation.
The current state of things...
* Cannot get past the initial "Samsung Galaxy Note 2" screen
* Cannot boot into recovery
* I CAN get into dl mode,
* but, I CANNOT successfully flash anything. TWRP will flash like it took, but upon reboot I'm not able to boot into it. I'm also able to flash a ROM but it fails when it gets to sbin, and upon rebooting I'm greeted by the screen "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
When I try to use Kies it doesn't find the device. I've installed all of the most recent drivers and I'm running Kies as administrator. I select Tools > Emergency Firmware Recovery, THEN connect my device as instructed.
I'm at the apex of frustration. I beg thee to help!!
Hey im new here so please excuse me if this is in the wrong category
hi, i currently have a Samsung s2 skyrocket which was rooted and recently acting up so i tried factory resetting it, after factory resetting it the phone kept freezing at the boot up so i looked up possible solution for this problem which only made it worse. after trying to load my stock firmware back onto my phone using Odin i got an error afterwards from accidentally disconnecting it which read "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again" I've tried connecting to Kies only for my computer to not recognize my phone even after running the connection error solution in the Kies application. i cant even get into recovery mode for my phone only shows a blank screen and starts to vibrate.
Hello,
Welcome to XDA.
Samsung Kies should have correctly installed your drivers and you should still be able to flash the stock firmware via Odin even in this state. I've had to do this more than a few times on S2, try doing a google search for "USB drivers for samsung phones" and install them manually if you haven't tried that already, sometimes you have to uninstall the drivers then reinstall them, try other USB ports also. Are you certain that you have the correct firmware, just to be sure before you start?
Once you have the drivers properly installed and your PC recognizes the device, charge the battery to full if you can even if you have to do it with an external charger(you don't want it dying in the middle of flashing), open Odin, try to boot to download mode, when the "connect to kies" screen or if download mode comes up then connect to Odin(don't use Kies), if recognized you'll get a blue or yellow comm# box and it will say <ADDED!> in the dialogue box, select the AP tab in Odin, browse to the stock firmware file and select it, when back in Odin screen select Start, give it a few to flash, when done you'll get a green PASS and the device will reboot, give it time to load into system, sign in to google account and you should be good to go. sometimes you have to flash a couple of times to get it. I hope this helps. Good luck.
get into recovery, install the newest twrp, either through custom recovery already on your phone via zip or through odin using a tar.
reboot into recovery again (should be the newest twrp at this point)
if you still have anything on your internalSD, back it up through mount>mount as usb, plug phone into pc, browse, backup, or use file manager
wipe everything except externalSD
install rom then suggested gapps pack for that rom
reboot to system
wait like 15 mins for phone to do its thing during first boot
good luck
Hi all. I have been trying to update my VS980 to Lollipop for a week now; I've tried absolutely everything I can think of / find in the forums, and nothing works.
The basic problem is this: I have a rooted (via Stump Root) Verizon G2 running stock 4.4.2. I wanted to upgrade it to Lollipop, so I unrooted with SuperSU and tried to OTA update it, but somehow it still knows it was once rooted, so the OTA fails. I have tried MANY things to fix/work around this, but here are the highlights:
Hard reset. The hard reset procedure completed ok, but when I try to then install the OTA update, it fails with "Err: 1117008." Settings -> About Phone still shows "Status: Rooted," even though I don't actually have root control anymore.
Use LG FLash Tool to flash back to factory stock: VS980011A_01.tot. Tried two different computers, using both Vista and Windows 10. Failed because the proper LGE Mobile USB Serial Port driver was never found/installed by Windows (despite it clearly working in the video).
Copied a text file called RCT_security containing "forel.lee" onto the SD card, b/c somehow that's supposed to reset the status to "unrooted." It didn't.
Re-rooted with Stump Root, manually installed TWRP to try to flash a ROM that way. Phone is now rooted again, but attempts to boot into recovery result in "secure boot error," and no TWRP.
Installed Quick Boot to boot directly into recovery. Fails with same "secure boot error."
Installed FreeGee and TWRP Manager, b/c now I'm just grasping at straws. FreeGee hangs on a black screen and does nothing. TWRP Manager tells me that TWRP is already installed; haven't tried using it to flash a new ROM from here, b/c that feels brickish.
Use AutoRec to fix the "secure boot error." Fails b/c running AutoRec results in it hanging at "checking for loki....installing," When I backed out after many minutes, I got an error that said "Tried to install Loki Tool, no luck."
I am out of ideas. I am pulling my hair out. The phone is working fine, except that it's stuck on 4.4.2. When I started, all I wanted was a working version of Lollipop, even if it was stock/unrooted. At this point, I'm so mad at Verizon/LG/Android for making this process so painful that I really just want to flash the latest CyanogenMod just for spite. But really -- I'll take anything.
Help?
jackpurrton said:
Hi all. I have been trying to update my VS980 to Lollipop for a week now; I've tried absolutely everything I can think of / find in the forums, and nothing works.
The basic problem is this: I have a rooted (via Stump Root) Verizon G2 running stock 4.4.2. I wanted to upgrade it to Lollipop, so I unrooted with SuperSU and tried to OTA update it, but somehow it still knows it was once rooted, so the OTA fails. I have tried MANY things to fix/work around this, but here are the highlights:
Hard reset. The hard reset procedure completed ok, but when I try to then install the OTA update, it fails with "Err: 1117008." Settings -> About Phone still shows "Status: Rooted," even though I don't actually have root control anymore.
Use LG FLash Tool to flash back to factory stock: VS980011A_01.tot. Tried two different computers, using both Vista and Windows 10. Failed because the proper LGE Mobile USB Serial Port driver was never found/installed by Windows (despite it clearly working in the video).
Copied a text file called RCT_security containing "forel.lee" onto the SD card, b/c somehow that's supposed to reset the status to "unrooted." It didn't.
Re-rooted with Stump Root, manually installed TWRP to try to flash a ROM that way. Phone is now rooted again, but attempts to boot into recovery result in "secure boot error," and no TWRP.
Installed Quick Boot to boot directly into recovery. Fails with same "secure boot error."
Installed FreeGee and TWRP Manager, b/c now I'm just grasping at straws. FreeGee hangs on a black screen and does nothing. TWRP Manager tells me that TWRP is already installed; haven't tried using it to flash a new ROM from here, b/c that feels brickish.
Use AutoRec to fix the "secure boot error." Fails b/c running AutoRec results in it hanging at "checking for loki....installing," When I backed out after many minutes, I got an error that said "Tried to install Loki Tool, no luck."
I am out of ideas. I am pulling my hair out. The phone is working fine, except that it's stuck on 4.4.2. When I started, all I wanted was a working version of Lollipop, even if it was stock/unrooted. At this point, I'm so mad at Verizon/LG/Android for making this process so painful that I really just want to flash the latest CyanogenMod just for spite. But really -- I'll take anything.
Help?
Click to expand...
Click to collapse
VICTORY IS MINE. Here's what I did:
I decided to focus on the LG Flash Tool as my best potential for a successful outcome, and I further decided to focus on the LG drivers, which didn't seem be installing properly. So:
Nuked my computer and installed a fresh version of Windows 10, to ensure no errant drivers were present.
Installed LG United drivers from the top of this page: [link deleted b/c xda won't let me post it] (LG VZW_United_WHQL_v2.16.1.exe)
Connected the phone in Media Sync mode and waited while Windows installed some more drivers.
Connected the phone in Internet Connection -> Ethernet mode and waited while Windows installed yet more Drivers. (I think this may be the step I missed in all previous attempts; once this was done, the correct LG driver appeared in Device Manager.)
Installed LG Flash Tool 2014 (download link in the description of the below video).
Followed the instructions in this video: [link deleted b/c xda won't let me post it] ...
... to install VS98027A_05.kdz, which I found somewhere, but now can't remember where. But it's around.
Once all those elements were in place, it worked perfectly. Got a completely stock phone, just like the day I bought it. Immediately installed 3 software updates and am now on Lollipop.
I'm still not sure which parts of this puzzle mattered and which didn't, but I *think* the key was installing those specific drivers (and not the many other versions of the same that I came across while researching), and THEN connecting the phone in MTP mode (ethernet) -- because that's when I finally had the correct drivers appear in Device Manager. Once I got there, the LG Flash Tool worked the first time.
Right. I hope this helps someone. I lost two weeks of my life to this (and a perfectly good CentOS box).
Last thing: download mode for me doesn't work quite the way anyone describes it. I have to turn it off, hold the UP volume button, plug it in, then let go of the UP button briefly and then hold it down AGAIN. No one mentions that last part.
Hello all.
I'm new to modifying my android (Galaxy S7 G930A) and could use some help. I have successfully rooted my phone, but have had some issues trying to flash a custom recovery. I was trying to flash TWRP but for some reason it didn't work, and I would always boot into the stock recovery.
Today, I screwed something up while trying to figure out my host of issues (I was also trying to figure out why I kept getting a "dm-verity verification failed" notice when flashing). Using the TWRP Manager app, I tried to install the recovery that way and it kept giving me an error that it was either already installed or encountered an issue of some kind. Knowing it wasn't installed, I looked for a different route. Long story short, I downloaded Flashify and then manually downloaded and flashed the TWRP recovery img and a "no-verity-opt-encrypt" file - which I read would fix the dm-verity error I was receiving.
I believe that's all I did before this recovery boot issue starting occurring.
Now, when attempting to boot into recovery (no matter what way, through an app, manually, etc) the blue text "Recovery Booting..." appears for half a second and then disappears. If I'm holding down the buttons it will flash again and disappear again, over and over. If I don't hold down the buttons, when it disappears the phone boots up as normal. So now I can't seem to access recovery at all. I wanted to try going the hard/factory reset route, but obviously can't because I can't access recovery.
Also, I don't know if this is related or not, but now my laptop will not recognize my phone at all. Doesn't give me any options - it will charge, but no connection. I was hoping to load it into Odin and do a stock reset to start from scratch before flashing a custom ROM.
Edit: I tested and connected to a different computer just fine, so there's obviously some miscommunication going on between my phone and laptop.
Can anyone help me out here? Sorry for the long post, I'm just really frustrated. :crying: