Related
As the title says, RUU attempts booting my phone but it never comes back on. Even selecting restart boot loader in fastboot or a command it doesn't power itself back on. I have read through other forums and nothing has worked for me yet.
EDIT: I should probably clarify fastboot usb WORKS. Ruu must see my phone considering it detects the ROM version and turns the phone off in attempt to reboot. Anything that I do that requires a reboot doesn't work. I have tried unlocking the bootloader again, everything is fine until it comes to rebooting then I must turn the phone on myself and nothing changes...... IT DOESN'T REBOOT ITSELF therefore seemingly nothing wants to work. And the HTC boot screen is gone??
More background information: http://forum.xda-developers.com/showthread.php?p=39046436#post39046436
What we're your steps exactly? Did you relock your bootloader
a box of kittens said:
What we're your steps exactly? Did you relock your bootloader
Click to expand...
Click to collapse
Yes I did through fast boot with the oem lock command. I've tried installing RUU with a Windows 7 laptop (has HTC sync software) and Windows 8 desktop (basic drivers). Both failed, tried using Windows XP/Vista in compatibility modes and running as an admin with the same results.
Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.
iElvis said:
Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.
Click to expand...
Click to collapse
No luck. And I believe it does see the phone in the beginning of the installation. It makes it reboot to the boot loader and that's where it loses the connection. The phone just isn't booting itself back up. I appreciate the reply, if you have anymore ideas please let me know.
Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?
iElvis said:
Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?
Click to expand...
Click to collapse
Re-downloaded RUU and still no go. And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.
Does anybody else have some more ideas?
Okkoto said:
And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.
Click to expand...
Click to collapse
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.
redpoint73 said:
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.
Click to expand...
Click to collapse
Fastboot does see it but adb does not. And what I mean by rebooting the phone in my last post is RUU attempts rebooting it from the boot loader which does turn the phone off but it stays turned off. I've used other commands to reboot the phone from the fastboot screen and those too turn off the phone then again it doesn't come back on like a reboot should do.
I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.
Okkoto said:
I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.
Click to expand...
Click to collapse
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.
DvineLord said:
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.
Click to expand...
Click to collapse
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.
i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.
Okkoto said:
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.
Click to expand...
Click to collapse
when you say it shows connected through fastboot what do you mean?
how are you getting the device into fastboot - through recovery??
oh, and what was on your device before you tried loading the RUU?
kkm68 said:
i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.
Click to expand...
Click to collapse
Yes this + if you're on a usb3 port try usb2. Also make sure you're using the cable that came with the phone as I understand other cables may cause issues like this. Also, avoid using a hub or usb extension.
Solution to error 171
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!
diegoyabishh said:
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!
Click to expand...
Click to collapse
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.
jondon156 said:
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.
Click to expand...
Click to collapse
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita
Heisenberg said:
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita
Click to expand...
Click to collapse
hi all..
facing same problem with HTC Desire 816 n 4g... have anyone got any solution??
plz pass it..
thank you
Hi,
I got this tablet from a friend, and it's stuck at the boot logo. I've tried hard reset, reset via recovery, nothing seems to work.
How can I flash the latest official rom?
Can't seem to find a tool for it, and Asus suggest to flash with the tablet itself, but that's not possible for now.
Anyone?
Thx!
http://forum.xda-developers.com/showthread.php?t=1688012
Easyflasher to flash TWRP recovery > copy ROM to MicroSD card, flash ROM
Thanks! I can't seem to get him into APX mode, what is the exact procedure?
Connect the tab to USB > PC first
Power Off the Tab
Hold Volume Up & Power
Nothing will appear on the Tab screen, but the PC should sound the USB connect noise / device manager will show it has connected - only takes a few seconds to enter APX mode
I've tried that, doesn't seem to recognize it . Would you help me via IM of some sort?
It`ll be the drivers most likely, open device manager when its connected and in APX mode, and manually update the drivers using the Universal Naked Driver from the Easyflasher site
I don't have any IM installed unfortunately but I`ll help you out here
Ok, that would be wonderful. The problem is, I don't know when it's off. I can't get it to shut down, it keeps rebooting. I'm monitoring dev manager with sound high, but it's not coming up. Cable is working, because it will charge. Using the original cable. (Windows 7 x64)
Best thing to do would be connect it to the PC, then press and hold Power until it shuts off, then try for APX mode - you might even be able to enter APX from a powered on state by holding the same button combo, but Ive not tested that myself
And a cable that charges doesn't automatically mean it will work for Data, they use different pins, some for power and some for data, if the data pins are damaged, it will still charge
I can't seem to get it working . Any other ways to flash it?
Not without being able to get it to boot - you'll need APX mode to do anything in the state it's in now
A bad cable is a common problem though, might be worth grabbing another one from eBay
To bad. I'll try and let it drain till it's empty, and fully charge it then. Just ordered another cable.
Thx for the help!
If the System / Data partitions are corrupted, which generally causes the boot loop, then draining and recharging won't help
Plus be careful not to drain the battery to 0%, their design prevents them from recharging if they hit 0% - many people have had to buy new batteries after not using their tab for a few months and letting it drain completely
Good luck, so long as there is no hardware damage, once you have a working cable it should be pretty straight forward to get TWRP recovery and a new ROM flashed to it
Might be worth trying your current cable on another PC too
Thanks for the headsup! Will try!
Hello everyone,
Not to thread jack but I have a similar problem and instead of opening a new thread I decided to revive this one.
I have a similar problem that my TF101 has been working flawlessly for many years. It is rooted and was running 4.3 ROM. As of a couple of days ago it just won't boot at all. It has been stuck at the NVidia screen and just sits there. I tried to enter recovery mode by using volume(-) + power and the unit presents the TEAMWIN logo and just loops as well by showing the TWRP screen (3 seconds) then going blank for a second then showing TWRP screen again in a cycle.
I downloaded and tried Easyflasher and Brks toolkit and nothing can complete the flash. Tried different installed drivers as well. I can enter MTP mode which the computer can see the device but the manufacturer name and model are not-recognized. I can also enter APX mode but while trying to flash anything I get an error message (error, cannot flash bootloader) and the computer dings (device disconnects).
I have been trying for a days now and have run out of ideas.
Has the unit finally bit the dust? Does any one out there have any more ideas or suggestions on what to try next?
TIA for any help provided.
Anyone with any sort of help on my previous post? Time to retire it for real this time?
TIA
Sent from my VisionX powered SM-N900T.
Jayster0966 said:
Anyone with any sort of help on my previous post? Time to retire it for real this time?
TIA
Sent from my VisionX powered SM-N900T.
Click to expand...
Click to collapse
Have you tried a different / new cable in-case that's the reason all the flashing attempts and computer recognising the unit are failing ?
Good Evening all,
I am coming here after trying for well over 4 hours to fix this issue, I'll go into as much detail as possible here:
Stock Android 5.1.1
Had the phone since launch day
No warranty
So, yesterday afternoon I was trying to take a picture of this lock I came across.. however, when I opened the camera app it was unable to connect. meh, I've had this issue before! It is usually fixed by retrying, or making sure I don't have the flashlight on through the drag-down bar. The Flashlight icon was on, despite my flashlight not actually being enabled. I clicked to turn it off, and then it switched it on. Weird! I clicked it again, and the phone realised it was actually off and kept the icon as off.
I then went to use the Camera again to no avail. So, I quite simply turned the phone off and attempted to switch it on again. This is where the fun starts - I am then met with the Google balls spinning, and spinning, and spinning, and spinning. This has happened once before, and that was when I first installed Android 5.0 - it took a good 20 minutes before it booted up, so I decided to leave it for a while. Fast forward two hours, it is still going. Yep, it's not booting. I again switched it off and back on, in the hope it would miraculously fix itself - it didn't. I decided to leave it going overnight, in the hope that something was just really, really broken and required a lot of work to fix - no, still nothing. Just the annoying balls flying around.
So tonight I connected the device up to my PC, booted into recovery and attempted to install the latest device image (http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701). Now, I am running Windows 8.1, getting the official nexus drivers to work or to even get the device into fastboot is a massive chore - and took me a while. Once I finally got it going (and to note, it has always been that bad!) I hit the "flash-all.bat" file and away it went.
It then got to the point where it needed to reboot into the bootloader, it was at this point that Windows reported the device malfunctioned (with code 43), Device Manager reported the following: device descriptor request failed - I had to keep unplugging and replugging the device to get the bat file to continue, and it got to the end (without any visible problems within the commandline) and rebooted my device.
Now, I am back to these damn balls.
Can anyone offer any assistance with this? Have I bricked my device? I don't care about my data, I just need my device for work!
Thanks,
Jake
jake.Hall30 said:
Good Evening all,
I am coming here after trying for well over 4 hours to fix this issue, I'll go into as much detail as possible here:
Stock Android 5.1.1
Had the phone since launch day
No warranty
So, yesterday afternoon I was trying to take a picture of this lock I came across.. however, when I opened the camera app it was unable to connect. meh, I've had this issue before! It is usually fixed by retrying, or making sure I don't have the flashlight on through the drag-down bar. The Flashlight icon was on, despite my flashlight not actually being enabled. I clicked to turn it off, and then it switched it on. Weird! I clicked it again, and the phone realised it was actually off and kept the icon as off.
I then went to use the Camera again to no avail. So, I quite simply turned the phone off and attempted to switch it on again. This is where the fun starts - I am then met with the Google balls spinning, and spinning, and spinning, and spinning. This has happened once before, and that was when I first installed Android 5.0 - it took a good 20 minutes before it booted up, so I decided to leave it for a while. Fast forward two hours, it is still going. Yep, it's not booting. I again switched it off and back on, in the hope it would miraculously fix itself - it didn't. I decided to leave it going overnight, in the hope that something was just really, really broken and required a lot of work to fix - no, still nothing. Just the annoying balls flying around.
So tonight I connected the device up to my PC, booted into recovery and attempted to install the latest device image (http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701). Now, I am running Windows 8.1, getting the official nexus drivers to work or to even get the device into fastboot is a massive chore - and took me a while. Once I finally got it going (and to note, it has always been that bad!) I hit the "flash-all.bat" file and away it went.
It then got to the point where it needed to reboot into the bootloader, it was at this point that Windows reported the device malfunctioned (with code 43), Device Manager reported the following: device descriptor request failed - I had to keep unplugging and replugging the device to get the bat file to continue, and it got to the end (without any visible problems within the commandline) and rebooted my device.
Now, I am back to these damn balls.
Can anyone offer any assistance with this? Have I bricked my device? I don't care about my data, I just need my device for work!
Thanks,
Jake
Click to expand...
Click to collapse
You did not bricked your device, it bricked itself. Take a look at this.
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
bitdomo said:
You did not bricked your device, it bricked itself. Take a look at this.
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
Click to expand...
Click to collapse
Thanks for that, however, I am completely unable to use Recovery. I boot into it, and Windows flat out refuses to anything but complain:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB device descriptor failed.
Like I say, always had issues with adb on this machine. The device is recognized as an Android Fastboot Device when Windows does decide to play fair. Any ideas as to what I can do next? I am on Windows 8.1
I'm guessing it's pointless keeping the balls spinning?
Make sure you're using a USB 2.0 port... for some reason, USB 3.0 has problems with adb/fastboot sometimes.
jake.Hall30 said:
Thanks for that, however, I am completely unable to use Recovery. I boot into it, and Windows flat out refuses to anything but complain:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB device descriptor failed.
Like I say, always had issues with adb on this machine. The device is recognized as an Android Fastboot Device when Windows does decide to play fair. Any ideas as to what I can do next? I am on Windows 8.1
I'm guessing it's pointless keeping the balls spinning?
Click to expand...
Click to collapse
Try other usb ports and usb cables or even other PC
hey guys, thank you for the response!
Telyx said:
Make sure you're using a USB 2.0 port... for some reason, USB 3.0 has problems with adb/fastboot sometimes.
Click to expand...
Click to collapse
USB 2.0 is doing the same. Recovery just flat out does not work, Windows always reports the device malfunctions
bitdomo said:
Try other usb ports and usb cables or even other PC
Click to expand...
Click to collapse
I have tried different ports and cables, I am wondering - is it worth dual booting Windows 7 and having a bash there?
jake.Hall30 said:
hey guys, thank you for the response!
USB 2.0 is doing the same. Recovery just flat out does not work, Windows always reports the device malfunctions
I have tried different ports and cables, I am wondering - is it worth dual booting Windows 7 and having a bash there?
Click to expand...
Click to collapse
I would try if I were you
bitdomo said:
I would try if I were you
Click to expand...
Click to collapse
Windows 7 was a bust, as was a different computer. Windows reports the exact same error when trying to boot into recovery, thus preventing me from firing off any adb commands. I can use all fastboot commands, as the bootloader works fine.
Next steps? I really can't afford a new phone right now (plus I want to wait to see what google come up with this year!)
jake.Hall30 said:
Windows 7 was a bust, as was a different computer. Windows reports the exact same error when trying to boot into recovery, thus preventing me from firing off any adb commands. I can use all fastboot commands, as the bootloader works fine.
Next steps? I really can't afford a new phone right now (plus I want to wait to see what google come up with this year!)
Click to expand...
Click to collapse
Turn off the driver signature enforcement and use the naked usb drivers 0.73 for the recovery device.
If you type naked usb drivers 0.73 in google it will be the first link to its post on xda where you find the download link
bitdomo said:
Turn off the driver signature enforcement and use the naked usb drivers 0.73 for the recovery device.
If you type naked usb drivers 0.73 in google it will be the first link to its post on xda where you find the download link
Click to expand...
Click to collapse
I've actually managed to get into recovery and successfully use adb. I followed the instructions within the post you added, and I am now in a constant reboot cycle wherein it keeps going back to recovery, saying /data can't be mounted then rebooting before I can see what's going on.
Progress!
EDIT: Dude, i absolutely love you! Thank you so so much, just having someone to talk to about it has helped!
For anyone who comes across this looking for an answer, what I have done is install TWRP (custom recovery), used the adb commands found here: http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576 to fix the persistent partition, I then had a different boot loop, so I reinstalled the rom and voila! She's back!
Just a question: how did this happen, out of the blue, in the first place? is this something I did?
Thank you to the xda team, you guys are great
jake.Hall30 said:
I've actually managed to get into recovery and successfully use adb. I followed the instructions within the post you added, and I am now in a constant reboot cycle wherein it keeps going back to recovery, saying /data can't be mounted then rebooting before I can see what's going on.
Progress!
Click to expand...
Click to collapse
Restart your device to recovery again.
You can also try the fastboot boot <<whateverfilename>>.img instead of flastboot flash recovery <<whateverfilename>>.img
Hello guys.
My tab (GT-P3100) have been facing some problems lately.
Before this, my tab cannot be started up for some times although it is fully charged.
Last week, I managed to boot it up and then formatted the tab via "restore factory setting" while the tab is on.
Then, I intended to load custom rom into the tab. However all pc, usb, driver, and kies version cannot help me as the tab won't be recognized. It either not showing up entirely or it simply show an error.
Then, I figured that I must format the phone via recovery mode to get the usb working again.
Now is where this problem happened. While formatting, the system message is only stuck at "formatting cache".
It then took a long time until it turned off on its own. This is when the phone cannot be started.
Initially, I can still boot it up until the "samsung galaxy" screen or in download mode. This need to be done by charging it just for a short minute until the battery charging icon shows up. If the battery icon doesn't show up, the phone cannot be started by any means. Then, the boot screen cease to show up but the download mode can still be accessed. Now, the download mode cannot be accessed as well. Lastly, the batter icon won't even show up.
So this lead to my question, what is wrong with my tab. Is is because of corrupted OS, recovery mode. Or perharps faulty battery. Can it be solved by jtag?
kukuru said:
Hello guys.
My tab (GT-P3100) have been facing some problems lately.
Before this, my tab cannot be started up for some times although it is fully charged.
Last week, I managed to boot it up and then formatted the tab via "restore factory setting" while the tab is on.
Then, I intended to load custom rom into the tab. However all pc, usb, driver, and kies version cannot help me as the tab won't be recognized. It either not showing up entirely or it simply show an error.
Then, I figured that I must format the phone via recovery mode to get the usb working again.
Now is where this problem happened. While formatting, the system message is only stuck at "formatting cache".
It then took a long time until it turned off on its own. This is when the phone cannot be started.
Initially, I can still boot it up until the "samsung galaxy" screen or in download mode. This need to be done by charging it just for a short minute until the battery charging icon shows up. If the battery icon doesn't show up, the phone cannot be started by any means. Then, the boot screen cease to show up but the download mode can still be accessed. Now, the download mode cannot be accessed as well. Lastly, the batter icon won't even show up.
So this lead to my question, what is wrong with my tab. Is is because of corrupted OS, recovery mode. Or perharps faulty battery. Can it be solved by jtag?
Click to expand...
Click to collapse
So you aren't able to install any custom recovery neither being able to get your tab detected so I think you should try heidmall
Sent from my GT-P3100 using Tapatalk
---------- Post added at 05:17 AM ---------- Previous post was at 05:15 AM ----------
kukuru said:
Hello guys.
My tab (GT-P3100) have been facing some problems lately.
Before this, my tab cannot be started up for some times although it is fully charged.
Last week, I managed to boot it up and then formatted the tab via "restore factory setting" while the tab is on.
Then, I intended to load custom rom into the tab. However all pc, usb, driver, and kies version cannot help me as the tab won't be recognized. It either not showing up entirely or it simply show an error.
Then, I figured that I must format the phone via recovery mode to get the usb working again.
Now is where this problem happened. While formatting, the system message is only stuck at "formatting cache".
It then took a long time until it turned off on its own. This is when the phone cannot be started.
Initially, I can still boot it up until the "samsung galaxy" screen or in download mode. This need to be done by charging it just for a short minute until the battery charging icon shows up. If the battery icon doesn't show up, the phone cannot be started by any means. Then, the boot screen cease to show up but the download mode can still be accessed. Now, the download mode cannot be accessed as well. Lastly, the batter icon won't even show up.
So this lead to my question, what is wrong with my tab. Is is because of corrupted OS, recovery mode. Or perharps faulty battery. Can it be solved by jtag?
Click to expand...
Click to collapse
Have you tried restoring to stock rom or installing cwm?
Sent from my GT-P3100 using Tapatalk
shsagnik said:
So you aren't able to install any custom recovery neither being able to get your tab detected so I think you should try heidmall
Sent from my GT-P3100 using Tapatalk
---------- Post added at 05:17 AM ---------- Previous post was at 05:15 AM ----------
Have you tried restoring to stock rom or installing cwm?
Sent from my GT-P3100 using Tapatalk
Click to expand...
Click to collapse
Hello
I have downloaded the heimdall zip. However, the zadig.exe cannot find any samsung devices. I have followed the instruction where I have to uninstall kies and other usb drivers. but still no luck.
My ROM is still stock rom. And I can't install cwm because my tab can never be discovered..
kukuru said:
Hello
I have downloaded the heimdall zip. However, the zadig.exe cannot find any samsung devices. I have followed the instruction where I have to uninstall kies and other usb drivers. but still no luck.
My ROM is still stock rom. And I can't install cwm because my tab can never be discovered..
Click to expand...
Click to collapse
Try sideloading Samsung USB drivers using uh what's it's called uh yeah go to my computer, right click, mange, device manager, connect your device and see if it appears and try side loading drivers, just Google it on how to do it and tell me if it works
Sent from my GT-P3100 using Tapatalk
shsagnik said:
Try sideloading Samsung USB drivers using uh what's it's called uh yeah go to my computer, right click, mange, device manager, connect your device and see if it appears and try side loading drivers, just Google it on how to do it and tell me if it works
Sent from my GT-P3100 using Tapatalk
Click to expand...
Click to collapse
Tried and failed. Thanks for your suggestion though. I'm gonna try third usb cord after this. Will report later.
it is time for taking it to the service centre
kukuru said:
Hello guys.
My tab (GT-P3100) have been facing some problems lately.
Before this, my tab cannot be started up for some times although it is fully charged.
Last week, I managed to boot it up and then formatted the tab via "restore factory setting" while the tab is on.
Then, I intended to load custom rom into the tab. However all pc, usb, driver, and kies version cannot help me as the tab won't be recognized. It either not showing up entirely or it simply show an error.
Then, I figured that I must format the phone via recovery mode to get the usb working again.
Now is where this problem happened. While formatting, the system message is only stuck at "formatting cache".
It then took a long time until it turned off on its own. This is when the phone cannot be started.
Initially, I can still boot it up until the "samsung galaxy" screen or in download mode. This need to be done by charging it just for a short minute until the battery charging icon shows up. If the battery icon doesn't show up, the phone cannot be started by any means. Then, the boot screen cease to show up but the download mode can still be accessed. Now, the download mode cannot be accessed as well. Lastly, the batter icon won't even show up.
So this lead to my question, what is wrong with my tab. Is is because of corrupted OS, recovery mode. Or perharps faulty battery. Can it be solved by jtag?
Click to expand...
Click to collapse
i think this must be the fault in the os..
if you are lucky to go to the download mode i think you can solve it using odin.
go to sam mobile site and download the firmware for your device.
then install odin app in your pc
(this is my 5th post so i cannot add links)
now while in download mode connect your device to pc.
now open odin in your pc.
make sure you dont uncheck/check anything new in the app
now select PDA and browse the firmware you downloaded and click start.
this may take some time, and your device might reboot several times.
now once you are done there are slight chances for getting stuck in the bootlogo.
in this case you can go to recovery and do a factory reset. then you are all set to go.
NOTE:Charge your device fully before doing this process.
I think this might help you. if still any problem occurs -please notice me.
Zte blade l said:
i think this must be the fault in the os..
if you are lucky to go to the download mode i think you can solve it using odin.
go to sam mobile site and download the firmware for your device.
then install odin app in your pc
(this is my 5th post so i cannot add links)
now while in download mode connect your device to pc.
now open odin in your pc.
make sure you dont uncheck/check anything new in the app
now select PDA and browse the firmware you downloaded and click start.
this may take some time, and your device might reboot several times.
now once you are done there are slight chances for getting stuck in the bootlogo.
in this case you can go to recovery and do a factory reset. then you are all set to go.
NOTE:Charge your device fully before doing this process.
I think this might help you. if still any problem occurs -please notice me.
Click to expand...
Click to collapse
Thanks for taking your time to answer this. Actually, the tab cannot be detected on every pc I have used (3 different pc up to now). Even with drivers and Kies. Do you think it's a problem on the charger port?
I finally found the problem!!
Zte blade l said:
i think this must be the fault in the os..
if you are lucky to go to the download mode i think you can solve it using odin.
go to sam mobile site and download the firmware for your device.
then install odin app in your pc
(this is my 5th post so i cannot add links)
now while in download mode connect your device to pc.
now open odin in your pc.
make sure you dont uncheck/check anything new in the app
now select PDA and browse the firmware you downloaded and click start.
this may take some time, and your device might reboot several times.
now once you are done there are slight chances for getting stuck in the bootlogo.
in this case you can go to recovery and do a factory reset. then you are all set to go.
NOTE:Charge your device fully before doing this process.
I think this might help you. if still any problem occurs -please notice me.
Click to expand...
Click to collapse
After extensive research for weeks, I finally knew the problem! Its actually an emmc brick bug!
The symptoms are all the same. My tab started to brick after I formatted in recovery. Causing no booting, and only download mode and cannot be detected by PC. The funny thing is, the emmc chip have been replaced before by the previous owner I bought the tab from. ONLY FOR THE CHIP TO BE AN INSANE CHIP AGAIN.
Remember folks, the symptoms are:
Cannot boot, sometime boot only on logo. very rare though.
Can only access download mode but cannot be detected by PC. Even if it can, the odin flash will stuck half way.
Can be charged.
How to solve:
I don't know ****
So here is what happened, I installed TWRP on my device and completely wiped my phone so I can install bootleggers OS and Gapps on my Pixel 2 Walleye. But I accidentally booted into Boot slot B on twrp and now the only thing the device can boot into is the bootloader mode, recovery and download mode is completely useless, It gives me either operation denied error or Error slot unbootable. The worst part is no computer will recognize my pixel in device manager at all. Mac computer will not detect it either. Ant tips on how to fix this? And again my I have all drivers installed and platform tools are up to date. And devices bootloader is unlocked.
Anything helps!
RomBetaTester said:
So here is what happened, I installed TWRP on my device and completely wiped my phone so I can install bootleggers OS and Gapps on my Pixel 2 Walleye. But I accidentally booted into Boot slot B on twrp and now the only thing the device can boot into is the bootloader mode, recovery and download mode is completely useless, It gives me either operation denied error or Error slot unbootable. The worst part is no computer will recognize my pixel in device manager at all. Mac computer will not detect it either. Ant tips on how to fix this? And again my I have all drivers installed and platform tools are up to date. And devices bootloader is unlocked.
Anything helps!
Click to expand...
Click to collapse
Did you use the same USB cable each time? If yes try different ones, even if it seems to work with other devices. On your PC go to device manager, then view and then hidden devices. Remove anything that has to do with Android. Then try connecting your device. Does an andriod driver show up after you've connected your device?
I have tried 3 different cables. But will try another one
RomBetaTester said:
I have tried 3 different cables. But will try another one
Click to expand...
Click to collapse
Did you go to view, hidden files in device manager and delete all Android drivers? And if you did, did anything show up after connecting your device?
I am having a similar issue after trying to flash the March update. During the script, the System image failed to transfer completely. I tried again using deuce flash all script, and it got a little further (4/5) with the System image but ultimately failed. Things got worse when my computer stopped recognizing the phone. Now I can't even try anything else because there is no communication, similar to OP. I have tried three different computers, three different cables, and have tried deleting Android related drivers in the device manager. No luck, unfortunately. I tried installing USB drivers from Google which also did not help. I welcome any other ideas of what to try next and appreciate any help.
EDIT: I solved the problem by draining the battery completely. In order to drain the battery, I first left the barcode screen on until eventually just the battery image is displayed on-screen when pressing power. Then eventually there will not be enough power to light up the screen at all, but the LED indicator will blink red while holding the power button. Now, I set up my phone such that the power button was held pressed down and left it there until the LED stopped blinking. Now that the power is completely drained, I could successfully get my computer to recognize it! I followed the steps in this post:
https://forum.xda-developers.com/showpost.php?p=78726736&postcount=13
EDIT2: I should also note that the system image didn't flash successfully the first time and I had repeat step 12 which is flashing the update. Luckily it worked the second time!
I had something similar happen. Held down power for about 10 seconds or so until the phone vibrated, then it was recognised by the computer. Then flash stock image
https://forum.xda-developers.com/showpost.php?p=78744315&postcount=31
ricky56789 said:
I had something similar happen. Held down power for about 10 seconds or so until the phone vibrated, then it was recognised by the computer. Then flash stock image
https://forum.xda-developers.com/showpost.php?p=78744315&postcount=31
Click to expand...
Click to collapse
Man you just saved me =)