I've tried to put a new ROM using Clockwork Recovery 6.0.1.2, during process it stuck for 4 hours and was turned off by power button.
After that tab don't react on power button, on pwr+vol up, pwr+vol down, pwr+ both vol buttons, nothing.
It even doesn't show battery icon when charging - screen is always black.
Any advices?
Thanks in advance.
I think the method described here will do the trick: http://forum.xda-developers.com/showthread.php?t=1478361
kallt_kaffe is having the same problem and he describes the procedure as: "basically tape down the power button to force a reboot cycle."
Aecidz said:
I've tried to put a new ROM using Clockwork Recovery 6.0.1.2, during process it stuck for 4 hours and was turned off by power button.
After that tab don't react on power button, on pwr+vol up, pwr+vol down, pwr+ both vol buttons, nothing.
It even doesn't show battery icon when charging - screen is always black.
Any advices?
Thanks in advance.
Click to expand...
Click to collapse
1. Put on your computer headphones and turn the volume up.
2. Plug your tablet into your computer via USB.
3. Hold the power button & Vol - keys together (Volume - is the side that is closest to the power button)
4. Listen for the "USB device connected" or "USB device disconnected" sound on your PC
5. If you can hear that, something has gone bad within the bootloader and the display does not initialize properly. Edit: The ICS installation does indeed attempt to patch the bootloader
6. If there is no sound, then the tablet is stuck in limbo, so go ahead and do the battery drain procedure as described in the above post.
7. If, however, your computer detects a device connecting and makes the sound, you can most likely still enter Download mode. You will have to do it blindfolded though:
-open ODIN 1.85 and see if it shows a connected device. If your PC made a connected sound, then there will most likely be a yellow COM port in ODIN.
- Hold [Power] & [Volume Down] together for 15 seconds or longer whilst monitoring your Device Manager windows to see if you can get the tablet out of APX mode and have it appear as another type of Device. Then press Volume+ several times with 1.5 sec. intervals. With luck, this should get you into Download mode, and ODIN will shine yellow for you.
- While doing all of the above keep your headphones on and listen for connected or disconnected sounds from your PC.
- Make sure you have this firmware for the P7300 which contains a bootloader, which is essential: http://www.hotfile.com/dl/162686792/c693269/P7300ZSKK2_P7300ZZHKK2_TGY.zip.html
- Flash with "Bootloader update" checked in ODIN and see if device is resuscitated. If the tablet boots, it will be in Hong-Kongish, but just select a language you recognize from the dropdown, it has them all.
- It may be a good idea to also throw in a .pit file and check Repartiton
N.B. The firmware link that I have provided is for the Tab 8.9 3G P7300 only! Do not flash it on another version of the 8.9!
You will need to search for a firmware that contains a bootloader.bin.md5 file for your tablet model.
Again, all of this will only be possible if the device registers with your PC on connecting the USB cable.
de3pkeeper said:
1. Put on your computer headphones and turn the volume up.
2. Plug your tablet into your computer via USB.
3. Hold the power button & Vol - keys together (Volume - is the side that is closest to the power button)
4. Listen for the "USB device connected" or "USB device disconnected" sound on your PC
5. If you can hear that, something has gone bad within the bootloader and the display does not initialize properly.
6. If there is no sound, then the tablet is stuck in limbo, so go ahead and do the battery drain procedure as described in the above post.
7. If, however, your computer detects a device connecting and makes the sound, you can most likely still enter Download mode. You will have to do it blindfolded though:
Click to expand...
Click to collapse
Ok, I've disassembled the device, and removed a battery connector for a time.
Didn't help though.
When I'm connecting tab to PC and holding pwr+vol_down, I hear that connect-disconnect sound and there is a device called
NVIDIA USB Boot-recovery driver for Mobile devices blinking in Device Manager with those sounds.
Odin shows no yellow com, all are empty, so download mode is not available.
you are stuck in APX mode , First go to this link and follow the instructions : http://forum.xda-developers.com/showthread.php?t=1130574]
if you get this in nvflash :
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
this means your device is locked and the battery draining is that last thing that might work for you .
i still didn't try it, but i only disconnected the battery and connect it again but my device still dead for a month now .
DSHV said:
you are stuck in APX mode , First go to this link and follow the instructions : http://forum.xda-developers.com/showthread.php?t=1130574]
if you get this in nvflash :
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
this means your device is locked and the battery draining is that last thing that might work for you .
i still didn't try it, but i only disconnected the battery and connect it again but my device still dead for a month now .
Click to expand...
Click to collapse
I'm getting exactly what you posted:
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
and right after that tab disconnects from pc and disappear from devices list.
is it possible, that some Samsung Service Center will help me? I think that what I did voids the warranty, but anyway, I'm in Ukraine and getting official support here is almost mission impossible.
Aecidz said:
I'm getting exactly what you posted:
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
and right after that tab disconnects from pc and disappear from devices list.
is it possible, that some Samsung Service Center will help me? I think that what I did voids the warranty, but anyway, I'm in Ukraine and getting official support here is almost mission impossible.
Click to expand...
Click to collapse
unfortunately the sbk (secure boot key) for locked Samsung devices is unknown and i was hoping that someone will be able to provide it since it's now increasing problem for 8.9 and 10.1 tabs especially after ics update . actually this is well known mode(apx) with all Nvidia Tegra devices such as acer a100 tablet and asus transformer ee pad but developers there were able to find the sbk for these devices .
if you are covered by warranty and the battery drain method didn't solve the problem you should go to Samsung and good luck . i am not covered by warranty and the only solution i found after connecting Samsung here in Egypt is replacing the mainboard costing almost as a new device (even Samsung couldn't fix it) .
DSHV said:
the only solution i found after connecting Samsung here in Egypt is replacing the mainboard costing almost as a new device (even Samsung couldn't fix it) .
Click to expand...
Click to collapse
Not very reassuring... Hope they will fix mine. I don't see any way to do it by myself.
Aecidz said:
Not very reassuring... Hope they will fix mine. I don't see any way to do it by myself.
Click to expand...
Click to collapse
Sounds like they want to get your cash.
If things went to sh*t software-wise, they can be fixed the same way.
They could just UART into the board and restore the bootloader. I don't have to expertise to do it, but they should have it.
1. Put on your computer headphones and turn the volume up.
2. Plug your tablet into your computer via USB.
3. Hold the power button & Vol - keys together (Volume - is the side that is closest to the power button)
4. Listen for the "USB device connected" or "USB device disconnected" sound on your PC
5. If you can hear that, something has gone bad within the bootloader and the display does not initialize properly.
6. If there is no sound, then the tablet is stuck in limbo, so go ahead and do the battery drain procedure as described in the above post.
7. If, however, your computer detects a device connecting and makes the sound, you can most likely still enter Download mode. You will have to do it blindfolded though:
Click to expand...
Click to collapse
1-7 okay. And device is "NVIDIA USB Boot-recovery driver for Mobile devices", not APX (because i installed special driver).
But nothing happend when i try to enter Download mode.
USB Disconnect > Connect > Pressing power and vol button for ~7 seconds (why 15+?.. So 15 i tried too) > Sound > Pressing V+ 10 times... Nothing glows in Odin.
eskimono said:
1-7 okay. And device is "NVIDIA USB Boot-recovery driver for Mobile devices", not APX (because i installed special driver).
But nothing happend then i try to enter Download mode.
USB Disconnect > Connect > Pressing power and vol button for ~7 seconds (why 15+?.. So 15 i tried too) > Sound > Pressing V+ 10 times... Nothing glows in Odin.
Click to expand...
Click to collapse
I had a broken bootloader and my display was dead the same way all of youse with bricked tabs describe.
It appears that in your case the bootloader is so badly messed up, that a fail-safe kicks in and sends the tab into APX mode directly.
Consider disassembling your device to disconnect the battery, press Power a few times with ti disconnected and keep it disconnected for a minute or so to force discharge of all capacitors, then reconnecting and attempting a reboot.
Disassembly is really easy - get a plastic knife and stick it under the display near the charging port and work your way around the whole unit. The entire display comes out of the back cover. Flip the display around and there you will notice where the battery connects to the main board, unplug the connector.
Have you tried?
And wut i must do after that?
---------- Post added at 11:46 AM ---------- Previous post was at 11:11 AM ----------
Disassemble, disconnect battery, press power, short + and - (on device, not on battery lol)... After that connect battery and connect via usb ... the same. cant enter download menu.(
Will try this > http://forum.xda-developers.com/showthread.php?t=1478361
If wont work - service center
Aecidz said:
I've tried to put a new ROM using Clockwork Recovery 6.0.1.2, during process it stuck for 4 hours and was turned off by power button.
After that tab don't react on power button, on pwr+vol up, pwr+vol down, pwr+ both vol buttons, nothing.
It even doesn't show battery icon when charging - screen is always black.
Any advices?
Thanks in advance.
Click to expand...
Click to collapse
Hi, may I know what new ROM did you flash? And your previous ROM before flashing. So that we can all avoid that ROM until somebody can fix this mess cause by brickbug. Thanks.
Nah. Samsung service sucks.
They said that motherboard should be replaced.
I don't understand how software problem couldn't be fixed w/o hardware replacement.
Screw that, I'll go get Nexus 7.
nexus_g said:
Hi, may I know what new ROM did you flash? And your previous ROM before flashing. So that we can all avoid that ROM until somebody can fix this mess cause by brickbug. Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1789464 <- that one. Version with N7UI (Build 11 Beta 9: (link) (Stable Build)(N7UI))
Not sure if it's ROM problem though.
Maybe it's just my karma.
Aecidz said:
http://forum.xda-developers.com/showthread.php?t=1789464 <- that one. Version with N7UI (Build 11 Beta 9: (link) (Stable Build)(N7UI))
Not sure if it's ROM problem though.
Maybe it's just my karma.
Click to expand...
Click to collapse
Actually it turns out to be the problem with CWM 6.0.1.2. You should use 6.0.0.8 or less.
manpete said:
Actually it turns out to be the problem with CWM 6.0.1.2. You should use 6.0.0.8 or less.
Click to expand...
Click to collapse
too late anyways.
but thanks for the info.
de3pkeeper said:
I had a broken bootloader and my display was dead the same way all of youse with bricked tabs describe.
It appears that in your case the bootloader is so badly messed up, that a fail-safe kicks in and sends the tab into APX mode directly.
Consider disassembling your device to disconnect the battery, press Power a few times with ti disconnected and keep it disconnected for a minute or so to force discharge of all capacitors, then reconnecting and attempting a reboot.
Disassembly is really easy - get a plastic knife and stick it under the display near the charging port and work your way around the whole unit. The entire display comes out of the back cover. Flip the display around and there you will notice where the battery connects to the main board, unplug the connector.
Click to expand...
Click to collapse
My tab was bricked and I followed your post but there is ghost, my tab is still on after 4 hours without the big battery, the secondary battery is so strong (I dont know where its placed)... I dont know how to drain it fastest.
the big battery connector are 5 wires, 2 red, 1 blue and 2 black, are they????
de3pkeeper said:
7. If, however, your computer detects a device connecting and makes the sound, you can most likely still enter Download mode. You will have to do it blindfolded though:
-open ODIN 1.85 and see if it shows a connected device. If your PC made a connected sound, then there will most likely be a yellow COM port in ODIN.
- Hold [Power] & [Volume Down] together for 15 seconds or longer whilst monitoring your Device Manager windows to see if you can get the tablet out of APX mode and have it appear as another type of Device. Then press Volume+ several times with 1.5 sec. intervals. With luck, this should get you into Download mode, and ODIN will shine yellow for you.
- While doing all of the above keep your headphones on and listen for connected or disconnected sounds from your PC.
- Make sure you have this firmware for the P7300 which contains a bootloader, which is essential: http://www.hotfile.com/dl/162686792/c693269/P7300ZSKK2_P7300ZZHKK2_TGY.zip.html
- Flash with "Bootloader update" checked in ODIN and see if device is resuscitated. If the tablet boots, it will be in Hong-Kongish, but just select a language you recognize from the dropdown, it has them all.
- It may be a good idea to also throw in a .pit file and check Repartiton
Click to expand...
Click to collapse
My tab has a blank screen and went through the steps you mentioned. ODIN has a yellow com port and when I try to flash the firmware+bootloader ODIN stops in "SetupConnection".. I tried to change port, cable, odon version to no avail. Any ideas? Thanks!
Hello for Everyone!
I've a SAM Galaxy TAB 8.9 (GT-P7300) branded for T-Mobile (TMH). There are few of strange things about it.
The first: can not communicate with my PC and with my laptop. On PC runs WIN7 x86, on laptop I use Ubuntu 10.4 (Studio). I had installed the USB drivers for WIN, and the only thing is happened after plugging the USB-cable WIN wrote: "Can't identifying the plugged in Android device". The Ubuntu doesn't recognize my tablet
The second: I can not reach the Bootloader mode, download mode. When I push the VOL down at same time with the POWER ON nothing happens.:crying:
The third: after some minutes of sleeping mode of the device (for example: charging, not using) it POWER OFF. Or...something like this...blank black display and nothing happens if I push any of the buttons. Pushing about 20 secs of POWER ON button resulting a reboot.
The device is in stock 3.2 .
Any ideas what can I do for rooting process nad for custom ROM?
simpleimage said:
Hello for Everyone!
I've a SAM Galaxy TAB 8.9 (GT-P7300) branded for T-Mobile (TMH). There are few of strange things about it.
The first: can not communicate with my PC and with my laptop. On PC runs WIN7 x86, on laptop I use Ubuntu 10.4 (Studio). I had installed the USB drivers for WIN, and the only thing is happened after plugging the USB-cable WIN wrote: "Can't identifying the plugged in Android device". The Ubuntu doesn't recognize my tablet
The second: I can not reach the Bootloader mode, download mode. When I push the VOL down at same time with the POWER ON nothing happens.:crying:
The third: after some minutes of sleeping mode of the device (for example: charging, not using) it POWER OFF. Or...something like this...blank black display and nothing happens if I push any of the buttons. Pushing about 20 secs of POWER ON button resulting a reboot.
The device is in stock 3.2 .
Any ideas what can I do for rooting process nad for custom ROM?
Click to expand...
Click to collapse
On your second point, to reach bootloader, turn on tab, wait until the moment the samsung logo pops up, then press volume down (the one closer to power button).
To root, add custom recovery and ROM, read the stickies in the android development forum. These may help your other problems. There are several reasons why your computers fail to recognize your tab. I would try different usb ports and cords if you can. I would install kies on the windows pc and see if that recognizes the tab. If none of that works, it may be a hardware problem.
upconvert said:
On your second point, to reach bootloader, turn on tab, wait until the moment the samsung logo pops up, then press volume down (the one closer to power button).
To root, add custom recovery and ROM, read the stickies in the android development forum. These may help your other problems. There are several reasons why your computers fail to recognize your tab. I would try different usb ports and cords if you can. I would install kies on the windows pc and see if that recognizes the tab. If none of that works, it may be a hardware problem.
Click to expand...
Click to collapse
Thanx for your quick reply. There are few cganges about the problems. Here they are:
The second problem about the bootloader and download mode is off. I picked parts of the device and there was a liitle problem with the VOL buttons...repaired and everything is fine with it.
The first problem about the communication is half-solved. On SAMSUNG laptop without (!!!) any drivers works fine the device. Flashed with a "stock" 4.0.4 (Checz) no boot, just splashed on the SAMSUNG logo. After ODIN-flashed one-file other ROM it was very nice...everything goes.
But the third problem is here after the good-flashing, too. In sleep mode or long not-usage periods it is something like POWER OFF.... During the picking to parts period some of the pieces (battery, flexes) were supervised...everything is normal. I think the device's main panel is wrong, but I don't know how I could look at it and fix it.
Hi , since my previous phone just broke i was thinking of repairing one of the bricked lumias i have instead of buying a new phone. I chose the Lumia 535,and it seems it can come back to life even without JTAG. The MicroUSBPort is a bit faulty, but i can make it connect correctly by moving the cable to the right,but this is not the real problem it gives.
Here's the problem it gives:
When i plug the charger,the phone vibrates, does not display anything,and then restart and vibrates again each 40 seconds.
When i plug in a PC ,the phone vibrates exactly as it does on the charger but my pc:
First detects the phone as "USB Input Device" before it vibrates.
After the phone vibrates it is detected as QHUSB_BULK, then
when it restarts and vibrates again i hear the device unplug sound from pc
and it detects it as USB Input Device then QHUSB_BULK then it loops until i unplug cable/charger.
I tried(and failed):
To recover using WDRT Lastest Version,but it fails because the phone cannot be detected.
To recover using Thor2 trying to flash a ffu but. THOR2_NO_DEVICE_WITHIN_TIMEOUT.
Seems like there's hope using thor2 because i din't try reflashing bootloader/putting in red screen mode.
Please help me, i'm without phone now!:crying::crying:
So im trying to unbrick my 3t, its my 2nd device.. and i tried with MSM tool. i keep getting errors such as firehouse communiocation handshake failed, sahara communication etc. For some reason when i just hold vol up by itself it doesnt show up as qualcomm in device manager. i have to hold power as well. but i keep getting different errors
The correct way to enter Qualcomm restore is by making sure the phone is 100% turned off and wait some more. Then keep pressing volume up while connecting cable until device shows up as the Qualcomm restore device. If it doesn't work, choose an USB 2.0 port instead of 3.0 or the other way aroune if possible or try another USB-C cable. And if it still doesn't work, maybe the PCB or USB connector of phone is broken in hardware.
pitrus- said:
The correct way to enter Qualcomm restore is by making sure the phone is 100% turned off and wait some more. Then keep pressing volume up while connecting cable until device shows up as the Qualcomm restore device. If it doesn't work, choose an USB 2.0 port instead of 3.0 or the other way aroune if possible or try another USB-C cable. And if it still doesn't work, maybe the PCB or USB connector of phone is broken in hardware.
Click to expand...
Click to collapse
I did. i keep getting firehousecheckrsp failed
xHvlios said:
I did. i keep getting firehousecheckrsp failed
Click to expand...
Click to collapse
You can try pressing and holding down the power button for 40 seconds when phone is on, this should force shutdown your phone without entering quickboot powersave as I think you will get this firehousecheckrsp error if phone was shutdown normal from OxygenOS ROM.
After this, startup the Qualcomm tool on PC, hold volume up and connect USB-cable. Check Windows Device Manager that the Qualcomm device is there and that the driver is working without any exclamation mark on it.
Bricked OP3T
pitrus- said:
The correct way to enter Qualcomm restore is by making sure the phone is 100% turned off and wait some more. Then keep pressing volume up while connecting cable until device shows up as the Qualcomm restore device. If it doesn't work, choose an USB 2.0 port instead of 3.0 or the other way around if possible or try another USB-C cable. And if it still doesn't work, maybe the PCB or USB connector of the phone is broken in hardware.
Click to expand...
Click to collapse
Hello, happy greetings to you and I hope you are safe. I also keep getting firehousecheckrsp failed sahara communication etc even if my device is surely 100% off (as it has no indicator whatsoever even if connected to the power brick, no vibration, just plain black screen). Also did hold the power button for more than 40 secs just to be sure. Though a bit of good news I guess is that my device can be detected as Qualcomm 9008 in Ports & Com in Device Manager when I hold the volume up button for several seconds.
Btw, these are the tools I used but none of them worked.
https://forum.xda-developers.com/on...ck-tool-3t-unbrick-data-babloo-t3737791/page3
https://forum.xda-developers.com/on...k-unbrick-tutorial-oneplus-3t-t3515306/page71
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Do hope to hear from you soon. Thank you.
Have you followed the complete guide?
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
But for sure it has Something to do with your usb version. Try diverent cable's for sure usb 2.0 is far more stable!
Followed guide
reef2009 said:
Have you followed the complete guide?
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
But for sure it has Something to do with your usb version. Try diverent cable's for sure usb 2.0 is far more stable!
Click to expand...
Click to collapse
Hello, thanks for noticing my question. I did follow the guide, changed USB ports, used another cable, and I still have the FirehoseCheck RSP Failed errorno:258 also Last Communication Status: Downloading cache.img Failed.
Also tried ones from Android 8 from this thread:
[OP3T][LATEST 9.0.6] Collection of unbrick tools
https://forum.xda-developers.com/oneplus-3t/how-to/op3t-collection-unbrick-tools-t3896765/page2
Is there another way for this?
Do hope to hear from you again. Thank you.
Aleatory YouTube videos explaining the problem and possible fixes, I don't recommend this channel, I don't know the YouTuber.
ROG2 here turns off and not power on again after gaming and charging same time (it's dead). Someone here tried one of this with success?
Change IC PM8150B
Reballing the CPU
Hello there!
I have no experience with your problem. Just going to say that from the top. I've never torn a phone down, and when hardware components need replacing that's when I usually decide I need to pick up a new phone.
I just recommend you make sure the phone you're trying to fix like this actually needs it. I've messed with my tencent rog ii quite a bit lately and I have had the phone go completely black - thinking I had thoroughly destroyed my phone, but I was able to get it running again.
It's possible that the complete "power off" that you are reporting is the phone being in EDL mode as the phone gives no indication whatsoever that it is on when in EDL mode. As a hail mary maybe you should quickly try this before tearing your phone down.
go to this guide, and download the zip file in the main post.
Repair your ROG2 phone with EDL mode，Official firmware！
Success is disgusted by some people, and will not share any files for free in the future.
forum.xda-developers.com
extract the zip, then go the the folder "qpst.win.2.7_installer_00453.2" and run "QPST.2.7.453.msi" - this installs the drivers necessary to communicate with your phone when in EDL mode (this may not be necessary, as your pc may identify a usb connection without this, but just to check 100% I'd install the drivers anyway.)
charge your phone for at least 30 minutes. just to make sure it's got juice.
use a DIFFERENT USB-C <-> USB-A cable than came with your phone (pick one up at the shop if you're not sure. ALSO plug your [charged] phone into your PC using the side USB port on the phone (Not the bottom usb port). This is because ASUS's cables don't seem to support flashing, so I'm suspicious if they'd work appropriately in this case, and because the side port is the only one that works for flashing and the like.
now open device manager (press windows key, type "device manager"). with that screen open, plug your phone in. On device manager you're hoping that a device appears under the menu "Ports (COM & LPT)" probably named something to do with Qualcomm.
if nothing shows up, unplug the usb port from the side and hold all three side buttons down for 20 seconds (vol +, vol -, and pwr) and keep an eye on the upper left side of the device where you MAY see a red light flash indicating signs of life. then plug it in again. if nothing happens unplug the phone, and hold the power button for 5 seconds, and plug it in again. if nothing happens, unplug it and try holding down just power and volume up for 20 seconds, then plug in again. If nothing happens, try power and volume down for 20 seconds, then plug in again. (you see where I'm going?) just make absolutely sure your phone has a hardware problem and can't connect to your PC in any way before performing surgery. If the device does show up under this "Ports (COM & LPT)" device it means your phone OS is thoroughly trashed. check out that same guide I linked, as well as this youtube for some ideas how to get it going again.
If your phone doesn't connect no matter what, and you're certain you've gotta get into the hardware, then I wish you the best of luck. I really wish I could be of any further assistance with regards to hardware. maybe if you do take that road let us know how it goes.
good luck!