[Q] please help, softbricked galaxy s5 active - General Questions and Answers

i made a extremely poor decision and was trying to change the boot animation loader when i actually changed the boot cmd and now it boots to samsung then to download everytime,. i can get into the onboard recovery yet i cant access safestrap and none of the many many drivers ive tried i cant get the phone to show to connect, its listed as unknown device in my device manager and ive hand picked the ones im supposed to have to other ones. ADB doesnt see it either and i was wondering if there is cmd for adb to find myu device, if you help me guys i promise ill only practice on hand me down smart phones. Ty:cyclops: [email protected] SM-G870A

This may be a dumb question, but have you tried Odin? I have had situations similar to this with my Samsung devices and always thought i bricked. But as long i could get into download mode, i could Odin back to stock and start over.

MrAwesome75 said:
This may be a dumb question, but have you tried Odin? I have had situations similar to this with my Samsung devices and always thought i bricked. But as long i could get into download mode, i could Odin back to stock and start over.
Click to expand...
Click to collapse
ya but i havent even tried loading a file into odin cause it wont see my device
and i have installed the samsung drivers but after this happened my pc wont see the phone

has to be a way to get a connection between the pc and phone

I'm not an expert so I'm not sure. Do you have the correct drivers installed on PC?
---------- Post added at 06:34 AM ---------- Previous post was at 06:30 AM ----------
Try different Odin versions. And make sure you have the proper drivers installed on the PC.

ya ive actually read that it probably doesnt have the function running to talk with the pc cause it cant boot. im all set up to reset the phoone. just need it to appear in my odin
..does kies still work?

[email protected] said:
i made a extremely poor decision and was trying to change the boot animation loader when i actually changed the boot cmd and now it boots to samsung then to download everytime,. i can get into the onboard recovery yet i cant access safestrap and none of the many many drivers ive tried i cant get the phone to show to connect, its listed as unknown device in my device manager and ive hand picked the ones im supposed to have to other ones. ADB doesnt see it either and i was wondering if there is cmd for adb to find myu device, if you help me guys i promise ill only practice on hand me down smart phones. Ty:cyclops: [email protected] SM-G870A
Click to expand...
Click to collapse
When you boot to system
It doesn't show anything right ??
but the touch is still functioning
Sent from my GT-i9300 running cm11 using tapatalk.

when i just boot it goes to download mode and says "could not do do normal boot"

i can access recovery mode and download mode but i cant get drivers to show it, and it used to show it until i did this, can i put a file on my micro SDcard from my pc via card reader then install it in recovery mode ? like firmware or a memory wipe reset?

If you can get into recovery, I believe that would be possible. Couldn't hurt to try. As long as you can get into recovery and all the recovery functions work, I don't see why you couldn't.

fixed it!
well after two nights of reading i got my pc to discover the device by changing ports three different times to find one that seamed to like it. and also installed kies and installed the drivers from them, (figured couldnt go wrong after as many as ive used from samsung and others). so win7 pro / altered boot command and only stock options afterwards sucks big time. ty all for helping me

never let up

Related

[Q] I've tried everything to get out of boot loop

Hello everybody,
I am new to the forum and also new to Androids. After years of using iPhones and finally becoming fed up Apple, I've decided to try something new (please don't judge my prior smartphone selection and start posting opinions about the 2 operating systems, I do not want this thread to turn into one of the "battle of the phones" thread that I've experienced many times on iPhone forums). My friend recently got an S3 and had no use for his Galaxy S 4g, so he gave it to me so that I could try out an Android. There was one issue though, he said that the phone would not get past the Galaxy S screen and would keep re-booting itself (stuck in a boot loop). He said if I could figure out a way to fix it then it's mine.
That being said, here's my dilemma. I've tried many different methods to get the phone out of a boot loop. The first method I tried was putting the phone into restore mode and selecting the "reinstall packages" option. After this executes I get the message:
E:Can't mount /dev/block/mmcblk0p1
(no such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted.
After some further research I discovered a nice little program called Odin I read a lot about Odin and how to properly use it. After trying at least 5 different methods to get the phone into download mode with no success, I purchased a jig. The jig did the trick and instantly put me into download mode, I was ecstatic and hopeful that I could now fix the phone with Odin. I connected the phone to my PC in download mode, but Odin still didn't recognize the phone (I tried many versions of Odin, 1.85, 1.87, and the most recent 3.07). I do have the latest drivers for this phone, which I downloaded from Samsung's website. The phone will charge through the computer but the computer does not recognize it otherwise and will not allow me access its mass storage (I am running Windows 7 64 bit). I have tried using a different USB cable, and I have tried to use a different PC, the other PC I used popped up with a message saying that Windows could not successfully download the drivers (that was after I downloaded the drivers from Samsung's webpage and plugged the phone into the computer). I've even tried transferring stock firmware onto an external SD card and loading it onto the phone from restore mode (is that even possible to do?). I have also tried running Odin in compatibility mode, still didn't detect the phone. I should probably also mention that Kies Mini also does not recognize the phone. I asked my friend if he ever tried rooting this phone and he said no, so I'm assuming this issue has nothing to do with a failed attempt to root.
I really want to get this phone working, but I have run out of options to try. I am hoping that someone on here has a solution for me from a similar experience. After reading through the forum, I have noticed that people on here are very helpful and also very friendly; something that I can say is very different from some of iPhone forums I've used. I apologize if there is already a similar thread to mine, I've read through many threads and none of the solutions have worked for me. I also apologize for my first post being so lengthy, I just wanted to state all of the methods that I've tried to fix this phone. Thanks for your replies.
Hi hubbs134
You have come to the right place.
First,
I suggest you read a little bit about this phone and how to put it in Recovery (by holding Volume Up + Volume Down + Power until you see the SGS4G splash screen) and Download modes, it will help you in the future.
You can find it all in the Wiki.
Second, use this guide to One-Click Heimdall your way to Stock KJ6 2.3.6 Gingerbread ROM (latest official ROM for this phone).
If you use this file (instead) with that guide, you will also get phone rooted, or else you will need to make another flash of a rooted kernel (as the guide suggests).
Now, if you have the official latest stock, but still want some ICS/JB lovin', if you have CWM recovery v5 (you will see the recovery info once you're in that mode), you can flash CM9/AOKP/HebMIUI/UltraGen/RemICS/CM10/Slimbin/etc. etc. etc. ROMs.
Enjoy and welcome aboard!
P.S what the @#%#$ were you doing with an iphone ?
itzik2sh said:
Hi hubbs134
You have come to the right place.
First,
I suggest you read a little bit about this phone and how to put it in Recovery (by holding Volume Up + Volume Down + Power until you see the SGS4G splash screen) and Download modes, it will help you in the future.
You can find it all in the Wiki.
Second, use this guide to One-Click Heimdall your way to Stock KJ6 2.3.6 Gingerbread ROM (latest official ROM for this phone).
If you use this file (instead) with that guide, you will also get phone rooted, or else you will need to make another flash of a rooted kernel (as the guide suggests).
Now, if you have the official latest stock, but still want some ICS/JB lovin', if you have CWM recovery v5 (you will see the recovery info once you're in that mode), you can flash CM9/AOKP/HebMIUI/UltraGen/RemICS/CM10/Slimbin/etc. etc. etc. ROMs.
Enjoy and welcome aboard!
P.S what the @#%#$ were you doing with an iphone ?
Click to expand...
Click to collapse
Thanks for your reply, I have read a lot about this phone and know how to get into download and recovery mode. I tried the method you mention, however, when running the command window I get errors for both roms you suggested (i attatched a screen shot of the errors I'm getting). Do you know how I can fix these errors so that I can proceed with the rest of the tutorial? Thanks.
PS I only had an iPhone because I had yet to discover how bad a** Androids are
It sounds like you can't use Odin because of a windows issue. Try installing linux. I use ubuntu
Sent from my HTC One X+ using xda app-developers app
---------- Post added at 07:48 AM ---------- Previous post was at 07:47 AM ----------
You can also run as live CD or in a virtual machine
Sent from my HTC One X+ using xda app-developers app
hubbs134 said:
Thanks for your reply, I have read a lot about this phone and know how to get into download and recovery mode. I tried the method you mention, however, when running the command window I get errors for both roms you suggested (i attatched a screen shot of the errors I'm getting). Do you know how I can fix these errors so that I can proceed with the rest of the tutorial? Thanks.
PS I only had an iPhone because I had yet to discover how bad a** Androids are
Click to expand...
Click to collapse
No need to replace PC OS...
1. Uninstall all your Java versions and Samsung drivers and reboot.
2. Reinstall Java 1.7u..
3. Follow the guide, it should work.
When you reinstall the driver through Heimdall - it will appear as Gadget device.
Good luck !
itzik2sh said:
No need to replace PC OS...
1. Uninstall all your Java versions and Samsung drivers and reboot.
2. Reinstall Java 1.7u..
3. Follow the guide, it should work.
When you reinstall the driver through Heimdall - it will appear as Gadget device.
Good luck !
Click to expand...
Click to collapse
I second this... This should fix your driver issues.
Thanks for both of your replies. Odin detected my friends GS3 so I know it's not a Windows issue.
itzik2sh I did what you suggested and now got the command to function properly. I am going to try and finish the tutorial, I will be back soon with results. Thanks.
The phone is in download mode with Heimdall One-click 1.3.1 running and nothing is popping up in the command window. Neither is showing that the device is connected. Any suggestions? Thanks
Irish Enigma said:
I second this... This should fix your driver issues.
Click to expand...
Click to collapse
I forgot to mention that I can here the sound that a device was just connected to the computer via USB, and a message pops up saying USB device not recognized. When I click on the message it says "One of the USB devices connected to this computer has malfunctioned, and Windows does not recognize it."
Tried a different port? Tried second different port with a different USB cable?
itzik2sh said:
No need to replace PC OS...
1. Uninstall all your Java versions and Samsung drivers and reboot.
2. Reinstall Java 1.7u..
3. Follow the guide, it should work.
When you reinstall the driver through Heimdall - it will appear as Gadget device.
Good luck !
Click to expand...
Click to collapse
Theraze said:
Tried a different port? Tried second different port with a different USB cable?
Click to expand...
Click to collapse
Ok I got the device connected and I got Zadig running, however, there is no option for "Samsung USB Composite Driver" on the drop down list, on "gadget Serial", "Gadget Serial Control (interface 0), and "1.3 HD Webcam (Interface 0)'. What should I do?
On the one-clicks, you don't actually want to use zadig. Apparently it conflicts, which is awesome for something that gets released WITH the tool.
If you're doing manual Heimdall, make sure you've told zadig to list all devices in the menus. Your phone should show up after that.
If you're using a one-click, make sure you're using a USB port on your computer where you have NOT installed zadig, Kies, or Samsung official drivers. Follow the steps in the one-click religiously, and it should cooperate.
Follow the guide %100 then Odin should work
Sent from my HTC One X+ using xda app-developers app
Ok I ended up getting the phone to register in Odin. I flashed it with the stock rom in Odin and it said success. The phone booted and it seemed like it was going to work but then the recovery menu came up. I posted a screen shot of what it says, what action should I take from here? Thanks
I am also in a different boot loop now, before it would load to the first screen (black screen saying samsung galaxy 4g) then restart, now it boots to past the splash screen to where it says "Samsung" and then reboots back to the screen where the pink letters roll across the whole screen. I don't need to flash bootloaders do I?
Looks like recovery is broken or the updater script on the ROM you're trying to flash is messed up. Flash a new and the proper recovery via Odin then download a new Rom and either sideload it or mount usb from recovery and push it... Or you could just use Odin XD
EDIT: Samsung's are easy to brick and hard to debrick it may take a couple of trys
Sent from my HTC One X+ using xda app-developers app
Irish Enigma said:
Looks like recovery is broken or the updater script on the ROM you're trying to flash is messed up. Flash a new and the proper recovery via Odin then download a new Rom and either sideload it or mount usb from recovery and push it... Or you could just use Odin XD
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
OK GREAT NEWS! After flashing with Odin and that screen popping up, I clicked update from SD card, which failed. I then click system reboot, which brought me into the new boot loop. I put back into download mode and re-flashed with One-Click. Same recovery menu came up as before but when I clicked reboot system it hung at the "Samsung" black screen (after the splash screen) for about 20-30 seconds and then booted up I'm afraid to turn the phone off and see if it reloads lol. Is it safe to say that it is fixed? Or should I still follow your advice and run the proper recovery in Odin and then sideload a new rom? Or take different action? Thanks for all your help guys! Everyone gets a thanks click for being so helpful and friendly on an unhappy/confused/pissed off/ now happy new Android user!
Ok I just put my Tmobile simcard in and the phone is not detecting the sim. Any suggestion?
The IMEI number and baseband both say "unknown", I'm assuming this has to do with the simcard not registering?
hubbs134 said:
The phone is in download mode with Heimdall One-click 1.3.1 running and nothing is popping up in the command window. Neither is showing that the device is connected. Any suggestions? Thanks
Click to expand...
Click to collapse
What Heimdall package are you applying ?
After JAR package runs you are ready to go.
As I wrote, according to guide you can reinstall "Gadget" driver.
EDIT :
Enigma, if you're not an owner of an SGS 4G please stop advising.
Odin is not the common way since we have MTD ROMs and it had its problems.
hubbs134,
blank IMEI is a serious problem. without a proper IMEI your device is everything but a phone.
Try this : take battery off, press the POWER button for 10 seconds, leave device untouched for 15 minutes and then put battery back and power up.
This could bring your IMEI back to life. If not... maybe another flash will help.
P.S
The 3e recovery image you put on post #14 is a snapshot of the the stock unrooted ROM recovery.

[Q] phone bricked and not getting detected on computer

Hi,
my friend's Nexus S was stuck in a bootloop. i went into recovery mode and hard reset the phone, so that the phone would come back to stock. however, the phone was being reset when the battery of the phone came off, switching it off.
the phone fails to start. there is no response when i try charging it. Also, it does not go into DOWNLOAD mode or FASTBOOT, so i cant even run any utilities to flash the stock rom back. adb commands as well as the nexus toolkit show that there is no device connected.
can anybody suggest me what to do?? i was gonna try odin but i read somewhere that it is only useful for custom recoveries, not to flash stock roms.
i've gotten some usb drivers mentioned at some thread, saying i would have to update my 'android' device listed in the device manager using them, but i cant seem to find any device mentioned in my device manager either.
any suggestions as to what i should do??
Morphie said:
Hi,
my friend's Nexus S was stuck in a bootloop. i went into recovery mode and hard reset the phone, so that the phone would come back to stock. however, the phone was being reset when the battery of the phone came off, switching it off.
the phone fails to start. there is no response when i try charging it. Also, it does not go into DOWNLOAD mode or FASTBOOT, so i cant even run any utilities to flash the stock rom back. adb commands as well as the nexus toolkit show that there is no device connected.
can anybody suggest me what to do?? i was gonna try odin but i read somewhere that it is only useful for custom recoveries, not to flash stock roms.
i've gotten some usb drivers mentioned at some thread, saying i would have to update my 'android' device listed in the device manager using them, but i cant seem to find any device mentioned in my device manager either.
any suggestions as to what i should do??
Click to expand...
Click to collapse
Something like this happened to me a week ago. I have Nexus S 4G. So, I ordered USB Jig from usbjig.com and now I have download mode. It worked! :laugh:
You can buy USB Jig from that site, or build it yourself, or borrow it from someone.

[Q] Bricked Qualcomm's secondary bootloader, what to do?

Hello everybody,
I got my hands on this phone and I tampered too much with Qualcomm's FAT partition with the secondary bootloader, hardbricking the phone itself.
Trying to turn the phone on, shows the Samsung logo for some seconds then shuts down and disconnects, Download Mode is unaccessible but with VolUP+Home+Power the phone just stays connected (with the screen being black), but ignores any attempt to flash, Odin staying stuck on "SetupConnection...".
What I've tried already:
- Flashing with Heimdall -- phone isn't even recognized
- Removing the battery "trick" etc, etc, etc
- Changing .tar.md5 package
- Forcing a repartition with the .pit
Any clue might be useful, thanks in advance to anyone replying.
LucentW said:
Hello everybody,
I got my hands on this phone and I tampered too much with Qualcomm's FAT partition with the secondary bootloader, hardbricking the phone itself.
Trying to turn the phone on, shows the Samsung logo for some seconds then shuts down and disconnects, Download Mode is unaccessible but with VolUP+Home+Power the phone just stays connected (with the screen being black), but ignores any attempt to flash, Odin staying stuck on "SetupConnection...".
What I've tried already:
- Flashing with Heimdall -- phone isn't even recognized
- Removing the battery "trick" etc, etc, etc
- Changing .tar.md5 package
- Forcing a repartition with the .pit
Any clue might be useful, thanks in advance to anyone replying.
Click to expand...
Click to collapse
in my opinion go to coustmer service and you know it but i think 
 @ShadowsDie can help you
LucentW said:
Hello everybody,
I got my hands on this phone and I tampered too much with Qualcomm's FAT partition with the secondary bootloader, hardbricking the phone itself.
Trying to turn the phone on, shows the Samsung logo for some seconds then shuts down and disconnects, Download Mode is unaccessible but with VolUP+Home+Power the phone just stays connected (with the screen being black), but ignores any attempt to flash, Odin staying stuck on "SetupConnection...".
What I've tried already:
- Flashing with Heimdall -- phone isn't even recognized
- Removing the battery "trick" etc, etc, etc
- Changing .tar.md5 package
- Forcing a repartition with the .pit
Any clue might be useful, thanks in advance to anyone replying.
Click to expand...
Click to collapse
You shouldnt had to play with the bootloader neither the SBL
Im sorry to tell you that if your phone doesnt acces neither recovery and download mode it is hard bricked
that is why odin doesnt recognize the device
however, USB JIG is the best solution (the other one is changing the motherboard)
You can follow this instructions http://forum.xda-developers.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707 to build one
using this SHOULD work but its even possible your bootloader is so messed up that will not open
You told me there about download mode, what about recovery mode? althought it should not work maybe God gives you a second chance
ShadowsDie said:
You shouldnt had to play with the bootloader neither the SBL
Im sorry to tell you that if your phone doesnt acces neither recovery and download mode it is hard bricked
that is why odin doesnt recognize the device
however, USB JIG is the best solution (the other one is changing the motherboard)
You can follow this instructions http://forum.xda-developers.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707 to build one
using this SHOULD work but its even possible your bootloader is so messed up that will not open
You told me there about download mode, what about recovery mode? althought it should not work maybe God gives you a second chance
Click to expand...
Click to collapse
Actually ODIN recognizes the phone, but hangs on "SetupConnection...", sure the simplest solution might be the jig if there's a secondary bootloader in situ.
Obviously the recovery mode is dead, but still, I saw that it bypasses Samsung's logo and just reboots.
Since it's Qualcomm, probably the microSD emergency procedure used on the S3s might be a fair try.
If someone has still a working phone, can please do a dd image of the first 100 MB of the EMMC so I can see if this option is viable?
Might be a nice solution for hard bricked Qualcomm-based Samsung phones to unbrick those.
LucentW said:
Actually ODIN recognizes the phone, but hangs on "SetupConnection...", sure the simplest solution might be the jig if there's a secondary bootloader in situ.
Obviously the recovery mode is dead, but still, I saw that it bypasses Samsung's logo and just reboots.
Since it's Qualcomm, probably the microSD emergency procedure used on the S3s might be a fair try.
If someone has still a working phone, can please do a dd image of the first 100 MB of the EMMC so I can see if this option is viable?
Might be a nice solution for hard bricked Qualcomm-based Samsung phones to unbrick those.
Click to expand...
Click to collapse
First, for the SetupConnection try changing the ports but first BE SURE Kies is closed or end the task as Kies closes your connections using third-party programs
then reinstall samsung usb drivers or even adb drivers are good.
if you will find anyway to execute the command adb reboot-bootloader you could probably save the phone
2. I just read about the microSD procedure, it looks like a pretty clever idea
I wonder how do you know how many MB's you need
so i have done here a 70MB IMG, and with 100 didnt worked so I did a 99 MB one
Remember you need Class10 16 GB Card
If somehow this solved your problem, i will do a post in our General Section
Good Luck, i'll stay tuned.
EDIT: I just noticed the files have 169 MB so I can't post them here, tell me your email and i send you, my email is [email protected]
ShadowsDie said:
First, for the SetupConnection try changing the ports but first BE SURE Kies is closed or end the task as Kies closes your connections using third-party programs
then reinstall samsung usb drivers or even adb drivers are good.
if you will find anyway to execute the command adb reboot-bootloader you could probably save the phone
2. I just read about the microSD procedure, it looks like a pretty clever idea
I wonder how do you know how many MB's you need
so i have done here a 70MB IMG, and with 100 didnt worked so I did a 99 MB one
Remember you need Class10 16 GB Card
If somehow this solved your problem, i will do a post in our General Section
Good Luck, i'll stay tuned.
EDIT: I just noticed the files have 169 MB so I can't post them here, tell me your email and i send you, my email is [email protected]
Click to expand...
Click to collapse
I don't have Kies installed, since I never kept any Samsung phone with the stock TouchWiz ROM, but only the USB Drivers package for ODIN and so on.
I sent you a PM with my e-mail address, but you could upload the img to MEGA or whatever file locker service...
In the case this get sorted, I'll upload the IMG over my server and drop the link, so you don't need to worry about the link expiring or whatever
LucentW said:
I don't have Kies installed, since I never kept any Samsung phone with the stock TouchWiz ROM, but only the USB Drivers package for ODIN and so on.
I sent you a PM with my e-mail address, but you could upload the img to MEGA or whatever file locker service...
In the case this get sorted, I'll upload the IMG over my server and drop the link, so you don't need to worry about the link expiring or whatever
Click to expand...
Click to collapse
check your email
ShadowsDie said:
check your email
Click to expand...
Click to collapse
Tried to burn the SD card, it seems that the 7227A doesn't support boot-from-SD.
Anyways, I ordered off eBay for some change a jig dongle, as soon as I get that I'll try that way, but I think that it won't work since most of the hardware components (except for the NAND) are not made by Samsung.
I'll let you know how it proceeds

(SOLVED) Custom binary blocked by FRP lock message when i try to boot my phone

Edit: It seemed as it solved itself, look in the replies for details
So i have had my gs7 rooted for a year or longer. Yesterday i rebooted my phone and got the error message "Custom binary blocked by FRP lock". Sadly, when i enter download mode and plug it into a pc with odin installed, it is not recognised. Odin does not say anything about a phone plugged in, and windows says the usb is not recognized.
What i think have caused this:
I downloaded an app that allowed me to record internal audio
I turned off developer options, and my stupid ass did not realize that is where oem unlock is located.
What i have tried:
Resetting to factory settings (from recovery mode)
Deleting cache (from recovery mode)
Using odin, but odin does not even recognize my phone
Tried using another computer with odin
tbh, looking at the other posts, i think i messed up. I dont want to send it in for repairing because i will have to pay a lot of money. I have tried sending it in for repairing a while ago. Then my problem was that i could not call with it, but they wanted me to pay the price for a new phone to repair my old phone, since i had rooted it. I did not accept it so i got my phone back, and managed to fix the issue myself. I hope i manage to fix the issue this time aswell.
There are lots of guides online on how to resolve this issue, please Google and read. Please make sure you have Samsung USB drivers installed on your pc
cooltt said:
There are lots of guides online on how to resolve this issue, please Google and read. Please make sure you have Samsung USB drivers installed on your pc
Click to expand...
Click to collapse
I have samsung usb drivers installed, and download mode has always been working and has always been recognized by odin ever since this happened. And online all i find is that i should boot into download mode and try using odin, but odin does not recognize my phone, nor does my computer.
10krlan said:
I have samsung usb drivers installed, and download mode has always been working and has always been recognized by odin ever since this happened. And online all i find is that i should boot into download mode and try using odin, but odin does not recognize my phone, nor does my computer.
Click to expand...
Click to collapse
Please pay attention to guides when messing about with your phone, OEM and Debugg are critical to being able to modify.
Look here for a solution.
https://www.mobikin.com/android-backup/computer-does-not-recognize-android-phone.html
cooltt said:
There are lots of guides online on how to resolve this issue, please Google and read. Please make sure you have Samsung USB drivers installed on your pc
Click to expand...
Click to collapse
SOLVED!
The issue fixed itself, im not sure what i did. I was suddenly able to connect my phone to odin. Just incase someone reads this with the same problem. This is what i did: installed smart switch and rebooted my computer. Uninstalled and reinstalled samsung usb drivers.
Before i did those things the issue was still there, i was ready to use smart switch, but i tried odin one last time and it worked. Now samsung pass tells me my phone is rooted, even though it is not (my root dissapeared after resetting my phone), its not that big of an issue, just thought id let you know

Firmware Upgrade Encountered an Issue. Tab 2 7 (P3110)

Hi,
Yes, I know, there's a million topics about this and I'm pretty sure I tried them all!
Long story short: been running Lineage OS on my Tab 2 for a while but it's been sitting in a drawer. Saw a video about using old tablets for emulating retro consoles and the Tab works a dream for that. So I bought a Bluetooth controller for better gameplay but it just wouldn't work under Lineage so thought I'd flash the original ROM back onto it to see if that would work. I'm not a n00b, but haven't done it for a while so thought to be safe I'd follow a guide. All seemed to be working well when Odin crashed and left me with the Firmware Upgrade Failed error.
I've been trying for about four hours to get it back, but having no luck. I've tried the latest version of Odin, as well as the old 1.7 version I was using; tried Kies, tried uninstalling Kies; tried uninstalling the stock drivers MS installed when connected, no go. Interestingly Odin doesn't seem to see the Tab at all now, so I tried the UniversalADB installer, tried installing ADB drivers as well as Samsung drivers manually, but nothing works, it just sits at "connecting" but never actually does. Also tried different stock ROMs to no avail. I think my issue is with the ADB drivers, just don't know how to fix it.
I don't know what to try now. Any advice?
Using MS Surface Pro (2017) running Win10.
Not allowed to post screenshots, but do have some.
Thanks.
How is the tab behaving after this crash?
Can you use the tab as usual? But you are still in LineageOS? If Yes, what version of LineageOS?
Can you still get into Recovery Mode? If Yes, what Recovery and version do you have?
Download Mode seems Ok, but not Odin at the PC end. Correct?
The more info you can give the better. Also if you prepared the tab in any way other than just entering download mode.
Did you enable USB Debugging for example? (but I'm not sure how important that is)
Or wiped anything in recovery?
I'm not sure if I can help, but surely there must exist someone here that can. I'm new to the android world, but used to work in IT Support and Network Administration.
And 100 years ago I blogged with Blogger, but sat and amended the xml-file to get the design I wanted more than creating blog entries
Anyway, I hope it gets sorted.
Tab_Triggerhappy said:
How is the tab behaving after this crash?
Can you use the tab as usual? But you are still in LineageOS? If Yes, what version of LineageOS?
Can you still get into Recovery Mode? If Yes, what Recovery and version do you have?
Download Mode seems Ok, but not Odin at the PC end. Correct?
The more info you can give the better. Also if you prepared the tab in any way other than just entering download mode.
Did you enable USB Debugging for example? (but I'm not sure how important that is)
Or wiped anything in recovery?
I'm not sure if I can help, but surely there must exist someone here that can. I'm new to the android world, but used to work in IT Support and Network Administration.
And 100 years ago I blogged with Blogger, but sat and amended the xml-file to get the design I wanted more than creating blog entries
Anyway, I hope it gets sorted.
Click to expand...
Click to collapse
Hi,
Thanks for your reply and sorry it's taken me so long to respond; I've got several health issues I have to work around!
I can't get into the OS at all, it's just stuck at the "Firmware upgrade..." screen and there's nothing else I can do with it.
It was rooted and I was running TWRP recovery, but can't access it at all now. I did a wipe in TWRP but was still able to boot into it before I ran Odin. Odin worked fine, then it just stopped for reasons unknown and now there's nothing I can do with the Tab at all.
I see this in Device Manager: samsung mobile usb cdc composite device. Have tried manually installing driver but nothing seems to work.
Have tried it on my Mum's Win7 machine, but to no avail. I really need ADB drivers but I can't install them without turning on debugging on the Tab and I can't do that because I can't get out of this blasted error screen!
There's literally nothing else I can say about it as this is all that's happening.
Annnnd, now it doesn't seem to want to hold a charge. :crying:
Thanks again.
I've tried following a few tutorials, but I can't get past the ADB issue. Does anyone know of, or can link to, a solution to this please? I really want my Tab back!
Thanks!
Tabby22020 said:
I've tried following a few tutorials, but I can't get past the ADB issue. Does anyone know of, or can link to, a solution to this please? I really want my Tab back!
Thanks!
Click to expand...
Click to collapse
Maybe a longshot, but you can test if this free version can access the tab:
https://www.tenorshare.com/products/reiboot-for-android.html
No use buying if it can't.
But since Device Manager sees something it's worth a shot.
Do you have to longpress power button to turn it off?
If so... when the screen goes off, have you tried to quickly let go of the power button and immediately press it again together with Volume Up?
Or down, for download instead of Recovery.
With my P3100 it was much easier with no charger plugged in...
Edit:
Tried the software and my tab is OK, but no connection established anyway. Only result was that I couldn't access tab in File Explorer and MTP state... only PTP.
In Device Manager I got a new Android Device: Something like Google Nexus ADB... sorry but I uninstalled it directly without noting exact name.
Replugged USB cable and MTP working again.

Categories

Resources