Never activated Samsung Galaxy Tab S2 semi-bricked after phone apps removed - Galaxy Tab S2 Q&A, Help & Troubleshooting

PLEASE NOTE the tab will not do a factory reset, when I try that it tells me it has successfully erased all the data but when I reboot it it still comes up with the same screens as described below
Got a new S2 8 inch from Sprint but couldn't remember my password so I never activated it ... it worked fine. Great. No activation fee, no monthly access charge, no running up excess minutes accidently.
Truth is all I ever wanted was a pure WiFi tab to replace a Nexus 9. I just bought from Sprint because they were having a sale. Without activation I had exactly the tablet I wanted.
Than I got greedy ... decided to streamline performance by tossing out all the superfluous phone apps and system stuff ... this seemed to work well to ... or at least it did before I rebooted the phone. Now I get a black screen with a flashing red message: Kernel is not SE Android enforcing. Custom binary blocked by FHP block.
All this is Greek to me, but that aside when I try to boot up I get one of two options depending on what hard key compos I hold. One is an endless download loop, the other is the standard Android mini recovery boot page. Of all the options, the seemingly easiest delete cache and restore default system doesn't work. The other potentially useful items .... update from file, update via download, etc. require an ADB connection to work. I have tried to establish an ADB connection using many different cables on both a Win 19 and a Win 7 PC ... in each case I get the dread "wouldn't open Code 10) message .... I have tried it with specific adb drivers and generic ones ... the results are always the same.
A fw other tips, the Android System Recovery LMY47x.T817PVPS2A0L1 screen says:. in yellow at the bottom of the screen, dm-verification failed ... update from ADB blocked and gives similar messages under"apply update from external storage, and and apply update from cache
Meanwhile, back at the downloading loop page we are told:
ODEN MODE
DOWNLOAD SPEED : FAST
PRODUCT NAME SM T817P
CURRENT BINARY: SAMSUNG OFFICIAL
FAP LOCK: ON
Secure Download: Enabled
Knox Warranty Void: ZERO
HP: SWHEV: B:2 K:8 S:0
So please, please, please does anyone have any idea what's going on here and how I can fix it ... would it, for example., be possible to reinstall the ROM and OS via a USB stick and OTR cable ... if so how would you do it .......
Thank you, thank you, thank you

Forgot to mention Samsung G6 phone connects to PC correctly through same cable ... Device Manager shows Code 10 message when nothing Android is connected to a USB port or when the S2 is connected does not show Code 10 and works perfectly when G6 is connected .... would it be possible to boot and restore the tablet via a USB stick and OTR cable? Thanks again

Hi, Guys, girls, men and women ... I'm not to proud to beg ... one of you must have an answer to this puzzle ... if you do and it works I'll use the my G6 to send you a video of me pushing a peanut around with my nose. Is there really no way to bot or restore this thing via a USB flash drive?

this seems like it could definitely help you

If you can boot into download mode (press volume down and home button as you power on the tablet. Continue holding the buttons down until you get the download warning message).
If successful, download the latest version of Odin to your computer. Also go to sammobile.com and search for your device in the firmware section. Download the appropriate firmware to your computer. You will also need the Samsung drivers for your device on your computer as well.
You should be able to flash it back to stock with Odin. There several threads on xda that give instructions on how to use Odin.

Related

Galaxy TAB P1000 NOT Detecting in ODIN

Hello xda users,
I need HELP !
I have a galaxy tab P1000
currently froyo 2.2
wanted to upgrade to GB
Tried the Odin way from another link on this site (MANUAL updation for galaxy tab(p1000) into 2.3.3 gingerbread ), it failed and the Tab got soft bricked,
somehow managed to unbrick it, now its back to its original fw, but it keeps restarting in a loop until i switchd the damn thing off completely
I have tried to go in download mode to flash but odin doesnt recognise it , tried differnt computers too, no use.
I have gone in recovery mode, hard reset, wipe cache , still when i switch it on, it goes in a reboot loop.
tried to use heimdall. cant get sucess as i might not understand how to use it properly
Please help.
Sincere thanks to you if you can help me get my tab up and running., if not in GB atleast back in froyo.
(PS- i im not worried about my data , and i have not backed up the rom etc before doing any of these)
Try to reinstall or install a usb driver from samsung
tried that before , didnt work
anyway now i managed to get it detected on ODIN and flashed it to GB
Libon
Yeah, happened to me too, nearly had a sh*t my pants when Odin didn't recognise my Tab.
I would recommend -
charge the Tab fully using wall adapter (4 hrs+)
plug it in with Odin open and using USB cable
don't expect Odin to recognise the Tab immediately
check back after 5 mins or so (I don't know, does Odin refresh?)
I was able to restore my Tab from the PC - ! - Marvin screen.
I don't want to go back there again though!
yea dude.. same here
i kept it on charge for a couple of hours and then tried.. bam it conencts..
Libon
Tab not turning on
HI Guys I have Galaxy 1000 .I was updating it by using kies in between the process my computer shut down and when I am trying to connect my tab again its not turning on .can some one help me please ?
Waiting no charge baterry 2 3 j
Run odin
Connect tab . Wait Long time 20 30min
Tab is. Détect go flashing
Sorry for my english
I m.. French
Envoyé depuis mon GT-P1000
GT P1000 Odin wont detect
hi guys can you help me on my GT P1000 odin wont detect it even after 2-3hrs. tried everything but odin wont detect my device.
thanks in advance...
iamkakers said:
hi guys can you help me on my GT P1000 odin wont detect it even after 2-3hrs. tried everything but odin wont detect my device.
thanks in advance...
Click to expand...
Click to collapse
do u have samsung kies installed in your pc? if does, kill the kies process (Ctrl+Alt+Del). close, and open odin3, put your tab into download mode, and then plug it into usb port. try to change different ports.
i always had this problems.. if all if that didn't work, i'll format my pc
Sent from my GT-P1000
odin3
hi
i also have a gt p1000 and odin3 doesnt detect the tab. i've been trying to root my tab for a while, tried odin and it doesnt detect, tried doomlord and it doesnt even get past the first step. i tried uninstalling kies on my windows 8 laptop and still no luck im not too sure what to do. is there something that i might be doing wrong because i follow all the info thati get from here.
is there another rooting app i can try that doesnt brick my device? and or is there an app that i can get that i am able to use a ps3 controller on my device that does not require a rooted device. please help
thanks
My Galaxy tab also doesn't connect to usb after cache wiped humber os flash
Thanks in advance guys!..
Earlier I was using Cyanogen mode 10 Custom ROM but has few issues like recognize SD card.
later I flashed to Humber OS caused real problem.
It was clock work recovery installed but my tab tab boots stays on screen humber OS.
It goes to recovery mode, and also to some unknown recovery mode.
Either the way not recognized by computer. I tried all options like heimtal an Odin. No help.
Friends any help, would be highly appreciated.
BUMP
Any solution to this given the fact that usb drivers have been installed?
Are you sure it is recognised by the computer before trying Odin or Heimdall?
I seen this in a post:
#################################################################################
4 Reasons Why Odin is Not Detecting Your Android Device:
Reason 1: No drivers installed for your phone
Most of the time Odin is not able to detect your phone, simply because you haven’t installed the drivers for your phone. Normally windows would automatically download the respective drivers for your phone from the internet and install it. But in case it isn’t able to do so, you need to download the drivers from your phone manufacturer’s website.
Reason 2: Inferior quality or damaged USB cable
Odin is very sensitive to low quality or damaged USB cables, which is a major reason why odin will detect your android phone in file transfer mode but fail to detect it in download mode. You might have a genuine USB cable that came with your Android phone but with time its quality will depreciate, which is why you might have to get a new USB cable.
Reason 3: Odin is corrupted
This happened once with a reader on my blog, we tried everything to solve his problem, but in the end using a different version of Odin worked out for him.
Reason 4: USB port is defective
Defective USB ports can also be a reason for Odin not detecting your Android phone. This was a problem faced by one of my readers and plugging the USB cable in another USB port worked out for him.
#######################################################################
and I need install cwm recovery on a twrp recovery and just do that with this app:
ROM Manager
if you want do same job; you can download it from google play easily!
and install recovery,rom or restore backup with it.
farza(db)astany said:
I seen this in a post:
#################################################################################
4 Reasons Why Odin is Not Detecting Your Android Device:
Reason 1: No drivers installed for your phone
Most of the time Odin is not able to detect your phone, simply because you haven’t installed the drivers for your phone. Normally windows would automatically download the respective drivers for your phone from the internet and install it. But in case it isn’t able to do so, you need to download the drivers from your phone manufacturer’s website.
Reason 2: Inferior quality or damaged USB cable
Odin is very sensitive to low quality or damaged USB cables, which is a major reason why odin will detect your android phone in file transfer mode but fail to detect it in download mode. You might have a genuine USB cable that came with your Android phone but with time its quality will depreciate, which is why you might have to get a new USB cable.
Reason 3: Odin is corrupted
This happened once with a reader on my blog, we tried everything to solve his problem, but in the end using a different version of Odin worked out for him.
Reason 4: USB port is defective
Defective USB ports can also be a reason for Odin not detecting your Android phone. This was a problem faced by one of my readers and plugging the USB cable in another USB port worked out for him.
#######################################################################
and I need install cwm recovery on a twrp recovery and just do that with this app:
ROM Manager
if you want do same job; you can download it from google play easily!
and install recovery,rom or restore backup with it.
Click to expand...
Click to collapse
reason 1: my phone is samsung and it's detected by ODIN, kies and I transfer files from and to my computer without problems. also tried reinstalling just in case but nothing, so I guess this is not the answer for my problem
reason 2: tried with original cable, but as I didn't use the tablet for a long time I also thought it could be the cable, so I asked a friend of mine if he could lend me one cable, but that didn't work. pity. :/
reason 3: tried 3 different versions of ODIN, and in every version my phone (mentioned above) is detected. shame. :S
reason 4: tried the 3 different USB ports in my laptop. two 2.0 USB ports and one 3.0 USB port, so again I doubt this is the reason of my problem.
extra reason: ~~~ maybe it's the OS version ~~~ // this laptop came with windows 8 preinstalled. nothing. then, I updated to win 8.1. again nothing. now I'm running windows 10 and the same, nothing is detected neither by ODIN nor the computer. also tried in 4 different computers running win xp, win 7 and other with win 8.1.
btw, thank you anyway for your apportation; this may help other people, but unfortunately, it's not my case, so can anybody else join me to think about a new reason and a way to solve it? thank you very much :good: :highfive: :fingers-crossed:
~~~~~~~~~~~~ EDIT ~~~~~~~~~~~~
I have continued researching and found a software. it didn't work for me, but maybe it works for other people.
-first, you have to make sure you have java installed on your computer.
-second, extract the oneclick.rar file on an easy-access directory.
-third, put your tab on download mode (while charging icon when tab is turned off, press power + volume down until a yellow triangle appears).
-fourth, click start unsoft-brick and let the magic begin! 8)
note: if a warning error pops up, trust the software and click on resolution center and follow the instructions of one of the three "alternative ways".
download: https://www.dropbox.com/s/8ix6yygu23a1kjn/OneClick.rar?dl=0
good luck!!
help
blizzard_boy said:
tried that before , didnt work
anyway now i managed to get it detected on ODIN and flashed it to GB
Libon
Click to expand...
Click to collapse
hi can you plz help me out with the processess you followed to as im suffring the same problum only CWM working and even it shows sd card mount error also not installing any rom via SD card showing error and odin not detecting it nothing happening only CWM and blank screen
blizzard_boy said:
tried that before , didnt work
anyway now i managed to get it detected on ODIN and flashed it to GB
Libon
Click to expand...
Click to collapse
How did you did it im having the same error???
i did the same thing with my tab exactly like yours plzzzz help me recover it

Hard brick help 911

I'm in a big predicament. A few weeks ago I installed the MOAR ROM on my Note 5. After installing this ROM I was no longer able to connect my phone to PC. I tried a Windows 8 PC which says I have an unrecognized USB device plugged in. I tried going into Developer settings to set USB mode to MTP but the option didn't exist. I had all USB drivers installed as well. My wife's phone is recognized no problem. When plugging the phone into my linux machine absolutely nothing happened. It used to show the phone in the left navigation panel in my window manager but after installing MOAR ROM it was no longer detected.
Anyway, today I was trying to play Cartoon Wars 3 and since my phone is rooted it wouldn't let me play. I decided to go into the Super User app and disable it to see if the game would work and it didn't. When I went to re-enable the app it said installation failed and asked me to reboot. I clicked reboot and was sent into a boot loop. I thought okay no big deal, I'll just restore a backup in TWRP. When I go to restore the backup and select the backup file it asks which partitions to restore, but there are no boxes to check. It usually has options like system and data but now it's just blank. I tried a factory reset and I'm still in a bootloop. I'm at a complete loss. I don't know what else to do. I've tried download mode and everything but no matter what I do my phone isn't detected by my pc.
I appreciate any help. I don't know what to do. I'm out of a phone right now and don't have a backup. Not to mention I'm in between jobs right now and can't afford a new one right now.
Just flash a stock rom from sammobile.com
Pre req:
*Odin(any vers)
*Stock rom
Steps
*Extract the downloaded stock rom in your PC
*In twrp wipe everything except internal, then boot in to download mode.
*Once in download mode, connect your phone to your pc, then open Odin.
*In Odin, check the "AP" section and locate the downloaded stock rom(the extracted one)
*Hit start.
Hpe that helps
herculesPh said:
Just flash a stock rom from sammobile.com
Pre req:
*Odin(any vers)
*Stock rom
Steps
*Extract the downloaded stock rom in your PC
*In twrp wipe everything except internal, then boot in to download mode.
*Once in download mode, connect your phone to your pc, then open Odin.
*In Odin, check the "AP" section and locate the downloaded stock rom(the extracted one)
*Hit start.
Hpe that helps
Click to expand...
Click to collapse
Thank you for your reply but it seems you didn't read my post. My phone is not recognized by any pc.
What is the terminal command to restore a backup? That's pretty much my last ditch effort.
Well I broke my recovery so I'm screwed. I contacted Samsung and they said they would service it for free. Wish me luck.
What would cause the phone to stop being recognized by the PC? I narrowed it down to the MTP software or the micro usb charge port. My Windows computer says Device Descriptor Request Failed. Linux box does nothing. No USB devices are listed when I run lsblk.
weinerwad3000 said:
I'm in a big predicament. A few weeks ago I installed the MOAR ROM on my Note 5. After installing this ROM I was no longer able to connect my phone to PC. I tried a Windows 8 PC which says I have an unrecognized USB device plugged in. I tried going into Developer settings to set USB mode to MTP but the option didn't exist. I had all USB drivers installed as well. My wife's phone is recognized no problem. When plugging the phone into my linux machine absolutely nothing happened. It used to show the phone in the left navigation panel in my window manager but after installing MOAR ROM it was no longer detected.
Anyway, today I was trying to play Cartoon Wars 3 and since my phone is rooted it wouldn't let me play. I decided to go into the Super User app and disable it to see if the game would work and it didn't. When I went to re-enable the app it said installation failed and asked me to reboot. I clicked reboot and was sent into a boot loop. I thought okay no big deal, I'll just restore a backup in TWRP. When I go to restore the backup and select the backup file it asks which partitions to restore, but there are no boxes to check. It usually has options like system and data but now it's just blank. I tried a factory reset and I'm still in a bootloop. I'm at a complete loss. I don't know what else to do. I've tried download mode and everything but no matter what I do my phone isn't detected by my pc.
I appreciate any help. I don't know what to do. I'm out of a phone right now and don't have a backup. Not to mention I'm in between jobs right now and can't afford a new one right now.
Click to expand...
Click to collapse
you can try this code and test if it work
*#0808#
Familiaaa said:
you can try this code and test if it work
*#0808#
Click to expand...
Click to collapse
The phone does not boot. Recovery does not boot. The only thing the phone does is go into download mode. The phone does not connect to any computer so I cannot use odin.
weinerwad3000 said:
The phone does not boot. Recovery does not boot. The only thing the phone does is go into download mode. The phone does not connect to any computer so I cannot use odin.
Click to expand...
Click to collapse
when your phone is in download mode,it doesn't work to connect it with samsung kies on your pc?
You could try using the Kies software to reload the stock firmware. Here's an overview of what to do:
- if you don't already have the Kies software installed on your PC, download it (just search Google) and install it. The first time it runs it'll update itself to the latest version so make sure you run it once before proceeding.
- put your phone in Download mode: with the phone completely off, press and hold the Volume Down and Home and Power buttons simultaneously, and release them all when you see the Samsung splash screen
- connect the phone to your PC with the USB cable that came with the phone
-- if you've never had the phone connected to your Windows-based computer before, you'll see messages about installing drivers, etc - just wait until this is done (may take 5 or 10 minutes) [I don't know what happens if you have a Mac - it probably just works]
- in the Kies software, select the second item in the Tools menu and just follow the prompts to enter the model number (in CAPS) and IMEI/Serial Number (both found under the battery - it's ok to remove the battery at this point)
- the Kies software should start downloading the correct firmware for your phone from the Internet; once that's done (depending on your Internet connection speed) it'll begin downloading that to the phone (this probably takes 10 minutes or so)
jubei79 said:
when your phone is in download mode,it doesn't work to connect it with samsung kies on your pc?
You could try using the Kies software to reload the stock firmware. Here's an overview of what to do:
- if you don't already have the Kies software installed on your PC, download it (just search Google) and install it. The first time it runs it'll update itself to the latest version so make sure you run it once before proceeding.
- put your phone in Download mode: with the phone completely off, press and hold the Volume Down and Home and Power buttons simultaneously, and release them all when you see the Samsung splash screen
- connect the phone to your PC with the USB cable that came with the phone
-- if you've never had the phone connected to your Windows-based computer before, you'll see messages about installing drivers, etc - just wait until this is done (may take 5 or 10 minutes) [I don't know what happens if you have a Mac - it probably just works]
- in the Kies software, select the second item in the Tools menu and just follow the prompts to enter the model number (in CAPS) and IMEI/Serial Number (both found under the battery - it's ok to remove the battery at this point)
- the Kies software should start downloading the correct firmware for your phone from the Internet; once that's done (depending on your Internet connection speed) it'll begin downloading that to the phone (this probably takes 10 minutes or so)
Click to expand...
Click to collapse
Kies doesn't work either. I already tried that. When I hook up the phone It says "Device Descriptor Request Failed". It used to connect to my computers until I put MOAR ROM on the phone. Since then it stopped being recognized by my computers. There's either something wrong with the connection or something got corrupted.
weinerwad3000 said:
Kies doesn't work either. I already tried that. When I hook up the phone It says "Device Descriptor Request Failed". It used to connect to my computers until I put MOAR ROM on the phone. Since then it stopped being recognized by my computers. There's either something wrong with the connection or something got corrupted.
Click to expand...
Click to collapse
What have you already tried?
- are you sure you're using a data cable and not a charging-only cable?
- have you tried a different computer?
- have you installed the Kies software?
- what does Device Manager show when the phone is connected?
- assuming that the phone is working normally, does the phone show anything when you connect it?
- do you have try windows 8 or 10?
can be you found a solution in this forum
http://forums.androidcentral.com/sa...-not-being-recognised-download-mode-odin.html
jubei79 said:
What have you already tried?
- are you sure you're using a data cable and not a charging-only cable?
- have you tried a different computer?
- have you installed the Kies software?
- what does Device Manager show when the phone is connected?
- assuming that the phone is working normally, does the phone show anything when you connect it?
- do you have try windows 8 or 10?
can be you found a solution in this forum
http://forums.androidcentral.com/sa...-not-being-recognised-download-mode-odin.html
Click to expand...
Click to collapse
I've tried 4 different cables. My wife's S5 works perfectly fine on all computers. I have tried in Windows 7, 8, 8.1, and 10. I've also tried in Linux Mint. It used to work until I installed MOAR Rom. Windows says Device Descriptor Request Failed. Linux doesn't do anything when hooked up. lsblk doesn't show the device either.
I have a bit of an update. Apparently something happened with all my data cables. I hooked up my wife's phone the other day and I was all of a sudden receiving the same error as the note 5. I went out and bought a new data cable and now her phone connects again. I'm waiting for the Note 5 to charge up so I can try Odin. I'll post back my results.
I apologize to those who told me it was the cable. I just didn't see that it was conceivable that all 4 of my data cables were all of a sudden damaged. Never underestimate the ability of children to destroy every working cable you own.
Well I'm still getting the error. I have some usb cables coming in the mail so once i try those out I'll get back to everyone.
weinerwad3000 said:
Well I'm still getting the error. I have some usb cables coming in the mail so once i try those out I'll get back to everyone.
Click to expand...
Click to collapse
Were you able to fix your issue. I have the same issue. Note 5 N9208, I can get into Recovery (TWRP) and Download mode, but can not boot. The USB connection is showing USB Device Descriptor failed. I have tried 5 different cables and Windows 7/10 Ubuntu and cant get the phone to show up on the PC. I also have changed the USB port of the phone. Any insight would be helpful.
musab_bari said:
Were you able to fix your issue. I have the same issue. Note 5 N9208, I can get into Recovery (TWRP) and Download mode, but can not boot. The USB connection is showing USB Device Descriptor failed. I have tried 5 different cables and Windows 7/10 Ubuntu and cant get the phone to show up on the PC. I also have changed the USB port of the phone. Any insight would be helpful.
Click to expand...
Click to collapse
I ended up trying to replace the port and accidentally cut the ribbon for the LCD screen. Ended up getting a new phone.

OP3T Bootloop - no way to flash new firmware?

Hello!
I am a happy owner of a OP3T 128GB version, but I've currently ran into an interesting issue . I am familiar with rooting android, fastboot, adb and stuff and I have limited experience (a begginer, but a quick learner ) with some other android phones. I hope I'm not creating a duplicit question - I am really sorry if I am, but I haven't found a solution to my problem even after hours spend behind the desk.
Long story short - accidentaly did an Advanced wiped in TWRP (3.1.1-0) and wiped my system (OS) and everything in the phone. I don't really care about the data, but checking the Sysem box in Advanced wipe menu has brought me into serious trouble it seems. Of course, I got a bootloop - my bad, right , nothing I can't fix I thought... But when I approached to try to flash a zip or .img of a system file/stock ROM respectively, I found literally no way to do so. My phone isn't recognized by my PC(s) (Windows and Mac) and I tried everything I could. The device isn't even a Qualcomm or sth. in the device manager - simply nothing, I can only get the device to charge sometimes when connected to the PC (seen in TWRP). I cannot connect an USB key to it via OTG either in TWRP to flash from there - TWRP just does not seem to know I even plugged a USB into the phone. I tried OP drivers, adb naked drivers, the phone and the PC just don't seem to be communicating at all.
The device can boot into fastboot, recovery (TWRP) and if proceeded TWRP prompts with "No OS installed" and I get a bootloop as expected. Is there any way I could try to flash the device with proper firmware? I do have the firmware and everything, I just can't seem to find a way how to flash it . I am a young student who just likes to play with tech stuff and devices and messed up and cannot help myself and I am really hopeless at this point . Any advice is greatly appriciated.
Thank you so much.
Matus
If you can flash/boot into TWRP, then probably nothing is lost. While in TWRP, if you connect your phone with PC, what happens? Do you hear the usual USB connection sound? If yes, what appears in the device manager?
Even if it doesn't appear in device manager, don't worry.
Boot into TWRP, go to storage, DISABLE MTP and enable it again. I know it sounds dumb, but just try it. It will be recognized as long as you have the proper drivers installed.
After that copy the zip of an OxygenOS based ROM like FreedomOS and flash it. Don't wipe anything. It will boot fine. I've done that a few times, never had a problem.
Thanks for the advice guys - no, no sound, nothing - as I said, I only get the charging (+) icon in twpr next to the battery percentage.
I did disable and enable MTP before - although not plugged in a pc during the process - will try if I have the chance.
One more thing that might ring a bell for someone - I tried the key combo for hard reset today(power + vol down) for a couple second and moments later I got a fuzzy (random colored pixels) screen and a red led. Weird, if you ask me.
P.S.: Today I tried to chat with OP a bit - 230 Eur for a new MB (64GB) and 255 Eur for my 128GB version - I just wanted to know, I'm still not admitting failure though. But as a student, these numbers from the support literally hurt me when reading...
grello said:
Hello!
I am a happy owner of a OP3T 128GB version, but I've currently ran into an interesting issue . I am familiar with rooting android, fastboot, adb and stuff and I have limited experience (a begginer, but a quick learner ) with some other android phones. I hope I'm not creating a duplicit question - I am really sorry if I am, but I haven't found a solution to my problem even after hours spend behind the desk.
Long story short - accidentaly did an Advanced wiped in TWRP (3.1.1-0) and wiped my system (OS) and everything in the phone. I don't really care about the data, but checking the Sysem box in Advanced wipe menu has brought me into serious trouble it seems. Of course, I got a bootloop - my bad, right , nothing I can't fix I thought... But when I approached to try to flash a zip or .img of a system file/stock ROM respectively, I found literally no way to do so. My phone isn't recognized by my PC(s) (Windows and Mac) and I tried everything I could. The device isn't even a Qualcomm or sth. in the device manager - simply nothing, I can only get the device to charge sometimes when connected to the PC (seen in TWRP). I cannot connect an USB key to it via OTG either in TWRP to flash from there - TWRP just does not seem to know I even plugged a USB into the phone. I tried OP drivers, adb naked drivers, the phone and the PC just don't seem to be communicating at all.
The device can boot into fastboot, recovery (TWRP) and if proceeded TWRP prompts with "No OS installed" and I get a bootloop as expected. Is there any way I could try to flash the device with proper firmware? I do have the firmware and everything, I just can't seem to find a way how to flash it . I am a young student who just likes to play with tech stuff and devices and messed up and cannot help myself and I am really hopeless at this point . Any advice is greatly appriciated.
Thank you so much.
Matus
Click to expand...
Click to collapse
1) try to update the twrp to the official 3.1.1.0. Then flash the latest modem firmware for your device and try to flash a custom rom like lineage os (a 7.x rom)
If you connect the phone to PC in TWRP and your phone is not recognized, chances are good that either your phone's USB or the cable (or the USB port on the computer) is not working. You can try to download the adb driver installer from here, just to check if your phone is listed by the installer: http://adbdriver.com/downloads/
Update - tried the MTP Enable/disable option in TWRP (in the Mount menu) while plugged into the PC, with no luck
IvanPrince - have you actually read the description of my problem? I have the 3.1.1-0 and even if not, how should I actually flash another version of twrp? The problem here is I cannot seem to find a WAY how to flash ANYTHING on the device.
I'll see about the adb drivers and update.
Thanks all,
Does the phone show up as anything on the PC when you boot to fastboot? I re-read but didn't see anything about it.
Nope - nothing. By now, I believe it is a hardware problem as the phone indeed got wet before my mistake with the advanced wipe. It appears to work just fine though, apart from the connectivity issue, so I believe the MB should be ok as everything else, including the screen is.
I just have one, perhaps a little courageous thing I'd like to ask from someone kind enough. Anyone with a Oneplus 3 or 3T who's not afraid to open the phone for a couplne minutes and has a multimeter alongside with a USB cable should be able to help me. :angel:
Could you, my awesome stranger, check where the 4 USB pins (on the side where you plug them into the PC) lead (make contact/'BEEP' on the multimeter) with the actual phone motherboard? It would REALLY help me in troubleshooting and perhaps saving 250 Eur. So far, I have this: (same color means contact) at that point. See picture.
BLACK - GND (all the heatsinks are connected to GROUND as well)
GREEN - DATA +
YELLOW - DATA -
RED - VCC
If anyone decides to open up their phone and help out a fellow xda guy, it will be greatly appriciated. :angel:
Hey Bro I was curious to know if you tried this method of recovering from a hard brick... When I first got my 3t something similar happened to me. I can't remember all the details of my hard brick but I thought I was f***ed. Please try this if you have not already.
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Might be a dumb question, but you did remember to mount the USB when you connected the otg right?
If the bootloader is unlocked, you can save it.
I would flash the stock recovery and the latest factory image (4.1.7)
Download them both from here:
http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.7/
After flashing the stock recovery using fastboot, boot to stock recovery and sideload through ADB the stock factory image.
Reboot and after checking that everything is working fine, feel free to relock the bootloader if you wish to stay 100% stock.
If the computer doesn't recognize it at all then it's a driver problem, not the phone... at least that's what I think.
try to use the program to fix my oneplus 3t it said download complete. try to restart
try to use the program to fix my oneplus 3t it said download complete. try to restart it and can press the screen and it keep rebooting it like the screen is frozen
please help me out

Odin stuck on "system.img.ext4" Help please?

Hi All,
I tried to flash my phone from VZW firmware to unlocked firmware and my odin3b has been stuck on system.img.ext4.
I realized I hadn't installed the samsung drivers the first time around. I attempted to restart the phone as it was stuck on system.img.ext4 - following that my phone shows the screen:
"Software Update Failed Your device didn't update successfully. Use the Verizon Software Upgrade Assistant on a computer to repair your device and complete the update."
I'm unable to re-boot or do anything, when I hold power, bixby, volume down it presents me the warning screen before entering download mode. If I press Volume Up or Volume Down - I hit the same warning screen I typed up above. I am able to view the barcodes by pressing the bixby screen...
When I went back to Odin it still showed as "Added" when I plugged in the phone. I attempted the process again but it's still stuck on the same part.
Anybody have any suggestions of what I should attempt? I've been reading but have been unable to see any solutions.
Thanks for reading.
I Havnt played with the note 9 in terms of flashing or rooting as I have the SM-N960W Canadian Snapdragon version and there is no way yet. I've used Odin many times to flash and it can be fussy for a few reasons, I rooted my Galaxy S7 and nexus 5 and a few others. My tips would be....
First Uninstall Samsung driver.
Then Download "usbdeview" on your pc and Uninstall any previous USB connections labeled Android or Samsung or related, as this will allow you to start off as if it's a fresh connection.
Re-Install Samsung USB drivers, then....
Plug in Using stock OEM Samsung Note USB cord and wait for it to connect.
If no luck try a different USB port. USB 2.0 May work if your using USB 3.0 and it isn't.
Try a different version of odin, there are many, also running odin as administrator may help but not necessarily for sure.
If all this fails try on another computer or laptop. Make sure you only select the proper/necessary options in odin.
It sucks when things don't go as planned but that's the risk you take when you don't stay stock & update OTA. The steps I've written for you have fixed any issues I have ever run in to with odin & flashing but if yours was an incomplete flash and disconnected or interrupted mid way you may be stuck with an expensive paperweight I'm sad to say. Try contacting Samsung for proper odin version & odin settings, I wish you the best of luck. I am in no way a mobile phone technician but I've rooted many phones and always made it work. I hope you can too!
Best of luck!
flash back your official firmware to get back access to fone
if none of this works use smartswitch( it will reinstall drivers)
then tey again with odin 13.3 b using u1 firmware
also to get to dl mode power off the fone. if you have access to recovery ( reboot fone with vol down Bixby and power and quicly change to vol up bixy and pwr when you see it reboot)go there and choose shutdown phone. or let battery die and charge it for 10 mins and do while phone is off :
hold vol down and Bixby with one had and with the other plug the usb cable from rhe pc to fone.
The same problem happened with me. I wonder if anyone knows how to solve it?
Sukrus said:
The same problem happened with me. I wonder if anyone knows how to solve it?
Click to expand...
Click to collapse
Try your luck with different odin versions, different cable, different pc, different firmwares
As above first step Samsung USB drivers and Samsung USB cable .

[SOLVED] Bricked GT-S5830 - USB device malfunctioned and Windows does not recognise it?

Hi all,
my first post! I stupidly messed around with my recently obtained GT-s5830 (The shop says its and 830i but the device says it's an 830 - shoulda checked the bloody firmware!)
Stupidly I didn't follow good procedure even though I know better and just tried updating from .zip via SD with a new OS but can't remember which atm as the only copy is on the SD and I can't access that right now. This install caused a bootloop and i then tried to install cwm. But alas now my phone boots to black, my bootloader is blue screening and I can only get to the download screen. But Windows can't start the device. I had a BOS error before and now after lots of trying different things its saying "A device which does not exist was specified." in Device Manager.
Honestly I didn't think lots about it cause it's a cheapy phone and I thought I'd just flash it back to the original firmware (which I now can't source online) and it'd be fine, done this before right? But thinking about it, i couldn't see the device in Windows 10 before i flashed it, so I'm wondering if the USB connection is buggered anyway, and now I can't get to the SD or boot screen to use the SD. I can't remember if I definitely switched USB debugging back on before I flashed last.
I know I've been an idiot but can someone help please? I really want to try the new OSs for teh device and see if I can get a faster, lightweight device. But I just can't get windows 10 to see it!!! I've tried changing the power settings, manually updating the drivers with nearly any driver I can find, deleting upper and lower filters in regedit, creating an ignore on the bos descriptor in Regedit (not sure if it's done correctly though)....Please help!
Just to let people know in case they're looking for a fix - this registry key stops the error and I can now see my device in ODIN. Can't see it in adb or fastboot yet but getting there
file courtesy of this site:
How to Install a Samsung Galaxy ACE GT-S5830 Stock Rom (Firmware) using ODIN - 8Bit Mammoth
This guide is about how to install a Samsung Galaxy ACE GT-S5830 stock rom (firmware) using ODIN.
www.8bitmammoth.com

Categories

Resources