Database Develop

[Q] Dead/Bricked GNote - Omap Flash on n7000 possible or not?

I would appreciate if anyone could share his knowledge in this matter. GNote doesn't show any signs of life except warming near camera when connected to the charger (to tell the truth it's warm even if it's not connected). Tried restarting, download mode etc. Nothing works. I'm waitng for the JIG I bought today but would like to know if this Omap Flash could save me or is it only for i9000 i9250 and such.
It didn't turn on after failed attempt to flash TWRP kernel using ROM Customizer (which worked for me many times before). Phone didn't went to CWM to flash kernel, simply went straight to GT-N7000 black splash screen and froze. When I tried to restart it, it switched off. And couldn't power on afterwards.

Try if odin detects it even if the screen stays black
Sometimes the fastboot loads which might just be enough to flash
If not you will need to wait for the jig.

friedje said:
Try if odin detects it even if the screen stays black
Sometimes the fastboot loads which might just be enough to flash
If not you will need to wait for the jig.
Click to expand...
Click to collapse
Nope, Odin didn't detect anything. Does the version of Windows could have some impact on this? I'm on Windows 8 x64.

Not really, i supose the same windows machine detected it before ?
The samsung usb drivers are present ? (Kies installed)

friedje said:
Not really, i supose the same windows detected it before ?
Click to expand...
Click to collapse
I don't really remember as last time I used it was to root my sgn about 9 months ago. But I'm pretty sure I wasn't using Windows 8 only Windows 7. But don't remember which version - x86 or x64.

In that case best uninstall and reinstall the latest kies
and then try again to put the phone in download mode
after having started odin. Even if the screen stays black.
It's worth the try.
I suppose you also tried to take out the battery for a few minutes and put it back ?

friedje said:
In that case best uninstall and reinstall the latest kies
and then try again to put the phone in download mode
after having started odin. Even if the screen stays black.
It's worth the try.
I suppose you also tried to take out the battery for a few minutes and put it back ?
Click to expand...
Click to collapse
Yeah. Did all of that (reinstalled kies just now too). But nothing works. That's why I'm curious about this Omap Flash. I don't like the idea of giving my GNote to service center to JTAG it. I still hope that JIG will help, but I also try to prepare for worse case.

Binary version of ROMs? where can we find them? does it work with zip /tar formats?

nokiamodeln91 said:
but without Roms in binary form it's useless...
Click to expand...
Click to collapse
Really? I thought that it might somehow help me to boot in download mode. I must have misunderstood what's written here http://forum.xda-developers.com/showpost.php?p=32508726&postcount=10

Afwasmassi said:
when i connect my phone to the pc it shows up as omap4440 in device manager, then it disconnects and reconnects every 2 seconds..
Click to expand...
Click to collapse
Does it happen to you too? Did you check what extension of rom can be flashed using that tool?

nokiamodeln91 said:
Does it happen to you too? Did you check what extension of rom can be flashed using that tool?
Click to expand...
Click to collapse
Nope, when I connect SGN to my laptop there is nothing new in Device Manager. So I thought that maybe on n7000 it works a bit different or something, that's why I asked.

Omap flash is for flashing phones using a Texas Instruments OMAP Cpu, which is not the case for the Note which is based on Exynos 4210

friedje said:
Omap flash is for flashing phones using a Texas Instruments OMAP Cpu, which is not the case for the Note which is based on Exynos 4210
Click to expand...
Click to collapse
Thx. So at least I can exclude this option. It's getting on my nerves I would understand if the phone bricked during bad flashing but not like this.
Is it possible that my brick happened because I was flashing different kernel while the phone was charging (battery was on 42% while it happened)? But still... it booted a bit afterwards and stopped on GT-n7000 splash screen... I don't understand any of it.

No i often flash while charging.
The kernel on a note has it's own partition
Just like the bootloaders and the recovery do.
While flashing a kernel even if it fails, SBL1 and 2 and Recovery
shouldn't be affected....
There are people wo got out of this by leaving their phone without battery for 24 hours. But I have my doubts myself on that method

friedje said:
No i often flash while charging.
The kernel on a note has it's own partition
Just like the bootloaders and the recovery do.
While flashing a kernel even if it fails, SBL1 and 2 and Recovery
shouldn't be affected....
There are people wo got out of this by leaving their phone without battery for 24 hours. But I have my doubts myself on that method
Click to expand...
Click to collapse
Worth a try. I was charging battery overnight to check if this helps, so I can also leave it alone for a day. Not much use of a brick anyway.

Well if it would change anything, the only explanation is that the powerchip is left in an instable state,not giving enough power to boot. Hence why it's running hot. Normally it is 'set' by it's driver inside the kernel. Maybe after 24 hours it will reset itself. As you say, it's worth a try even if it is a long shot.

friedje said:
Well if it would change anything, the only explanation is that the powerchip is left in an instable state,not giving enough power to boot. Hence why it's running hot. Normally it is 'set' by it's driver inside the kernel. Maybe after 24 hours it will reset itself. As you say, it's worth a try even if it is a long shot.
Click to expand...
Click to collapse
Seems quite logical to me. Thx.

My SGN is still dead even after one day off battery. I got my JIG finally and this doesn't work at all. Odin doesn't detect anything, there is no sound of connection etc. Tested on two laptops.
I have one question though. Is there any possibility to erase my personal data on internal memory before I send my phone to Samsung service center? I don't like the idea that some totally unknown/random people would have access to my stuff.

Only by connecting it to a riffbox, but for that you would need to open the phone and loose your warranty. So I guess you have to believe that they got something better to do then to scrutenize your memory

friedje said:
Only by connecting it to a riffbox, but for that you would need to open the phone and loose your warranty. So I guess you have to believe that they got something better to do then to scrutenize your memory
Click to expand...
Click to collapse
Yeah, but the problem is I don't have papers on my phone. It was bought on an internet auction from a guy who bought it on police auction. Is it possible that JTAG repair would be done instantly without leaving the phone in service shop? Or is it a normal practice to leave a phone for repair?

[Q] HTC One GPE - RUU Install - Phone Shut Down

Hello,
Yesterday @alray was helping me reboot my phone since I was stuck on the Bootloader and it kept rebooting to "no
command" I ended up installing the RUU via the adb htc_fastboot, and it worked!
Here is the link to that thread: http://http://forum.xda-developers.com/htc-one/help/htc-one-m7-gpe-command-t3151389/page3#post61741252
So when I started my phone and I started to register my account again since everything was wiped clean, everything was fine then all of a sudden the phone froze and then it completely turned off. I do not know why. I was in the settings page when it froze. Now it will not turn on anymore. I have no idea why it's doing this. When I plug in the charger, no green light indicator comes on. It all seemed fine. Your help would be greatly appreciated!

LATOKYO said:
Hello,
Yesterday @alray was helping me reboot my phone since I was stuck on the Bootloader and it kept rebooting to "no
command" I ended up installing the RUU via the adb htc_fastboot, and it worked!
Here is the link to that thread: http://http://forum.xda-developers.com/htc-one/help/htc-one-m7-gpe-command-t3151389/page3#post61741252
So when I started my phone and I started to register my account again since everything was wiped clean, everything was fine then all of a sudden the phone froze and then it completely turned off. I do not know why. I was in the settings page when it froze. Now it will not turn on anymore. I have no idea why it's doing this. When I plug in the charger, no green light indicator comes on. It all seemed fine. Your help would be greatly appreciated!
Click to expand...
Click to collapse
Is it detected when you connect it to your computer? What does it says when you go in windows device manager with the phone connected?

alray said:
Is it detected when you connect it to your computer? What does it says when you go in windows device manager with the phone connected?
Click to expand...
Click to collapse
It's really Interesting. Each time I plug in the device, this comes up:
Forge HS-USB QDLoader 9008 (COM4) Installed

LATOKYO said:
It's really Interesting. Each time I plug in the device, this comes up:
Forge HS-USB QDLoader 9008 (COM4) Installed
Click to expand...
Click to collapse
Then its really bad news, sorry.
If your phone randomly shut down and now detected as dload mode its an hardware failure.

alray said:
Then its really bad news, sorry.
If your phone randomly shut down and now detected as dload mode its an hardware failure.
Click to expand...
Click to collapse
But why? It was completely fine yesterday. The battery was perfect. Why does it completely fail after I do the RUU?

alray said:
Then its really bad news, sorry.
If your phone randomly shut down and now detected as dload mode its an hardware failure.
Click to expand...
Click to collapse
There needs to be a way to solve this issue. It cannot be coincidental that it just fails now.

LATOKYO said:
But why? It was completely fine yesterday.
Click to expand...
Click to collapse
No it wasn't completely fine yesterday, don't you remember why you had to flash a ruu? Your phone, for an unknown reason, randomly shut down and was only able to boot in recovery mode. Maybe the emmc chip was starting to act weird and some data got corrupted, flashing the ruu fixed that until the emmc died completely today, that is one possibility.
The battery was perfect. Why does it completely fail after I do the RUU?
Click to expand...
Click to collapse
If it had something to do with the RUU, the phone wouldn't have booted and it would still be stuck at the same point it was yesterday.
---------- Post added at 01:52 PM ---------- Previous post was at 01:39 PM ----------
If you want you can try the unbrick project but like explained in that guide, it will only work if the phone went in this mode directly after flashing an incompatible firmware which is not possible on your phone since it's S-ON. Anyway it worth a try before sending it for repair / garbage but don't expect this to work....

alray said:
No it wasn't completely fine yesterday, don't you remember why you had to flash a ruu? Your phone, for an unknown reason, randomly shut down and was only able to boot in recovery mode. Maybe the emmc chip was starting to act weird and some data got corrupted, flashing the ruu fixed that until the emmc died completely today, that is one possibility.
If it had something to do with the RUU, the phone wouldn't have booted and it would still be stuck at the same point it was yesterday.
---------- Post added at 01:52 PM ---------- Previous post was at 01:39 PM ----------
If you want you can try the unbrick project but like explained in that guide, it will only work if the phone went in this mode directly after flashing an incompatible firmware which is not possible on your phone since it's S-ON. Anyway it worth a try before sending it for repair / garbage but don't expect this to work....
Click to expand...
Click to collapse
I am not going to accept the fact that it has completely failed interns of hardware. I will find a solution.

LATOKYO said:
I am not going to accept the fact that it has completely failed interns of hardware. I will find a solution.
Click to expand...
Click to collapse
Do you even know what is qualcomm download mode? It mean that the phone can't boot because of hardware damage (probably the emmc) or corrupted bootloader. To possibly fix a corrupted bootlaoder on a M7 you'll need to send your phone to a JTAG service, if its an hardware failure you'll need a new motherboard. You are not the first one in this situation, hundred of M7 died this way here and same for other devices using qualcomm's chipset. Unfortunately, I never heard of someone being able to push a new bootloader using QPST like its possible on some other qualcomm devices to fix a possibly corrupted bootloader.

alray said:
Do you even know what is qualcomm download mode? It mean that the phone can't boot because of hardware damage (probably the emmc) or corrupted bootloader. To possibly fix a corrupted bootlaoder on a M7 you'll need to send your phone to a JTAG service, if its an hardware failure you'll need a new motherboard. You are not the first one in this situation, hundred of M7 died this way here and same for other devices using qualcomm's chipset. Unfortunately, I never heard of someone being able to push a new bootloader using QPST like its possible on some other qualcomm devices to fix a possibly corrupted bootloader.
Click to expand...
Click to collapse
I know it's happened before, but ill try everything before I have to acquiesce. I also read posts with how some people their phone did not turn for 2 days, but then all of a sudden, it comes back on. I am being super optimistic as you can tell.... I am not mad at you or anything, I truly appreciate your help.
I will let you know if anything updates after tonight or tomorrow.

LATOKYO said:
I know it's happened before, but ill try everything before I have to acquiesce. I also read posts with how some people their phone did not turn for 2 days, but then all of a sudden, it comes back on. I am being super optimistic as you can tell.... I am not mad at you or anything, I truly appreciate your help.
I will let you know if anything updates after tonight or tomorrow.
Click to expand...
Click to collapse
Don't worry, I wasn't thinking that you was mad at me, I know its frustrating when an expensive piece of hardware fails....
I also read posts with how some people their phone did not turn for 2 days, but then all of a sudden, it comes back on.
Click to expand...
Click to collapse
Yep and in some cases also went back again in dload mode later....
Anyway good luck

alray said:
Don't worry, I wasn't thinking that you was mad at me, I know its frustrating when an expensive piece of hardware fails....
Yep and in some cases also went back again in dload mode later....
Anyway good luck
Click to expand...
Click to collapse
So now when I plug in the device, it says " USB input device"
Good news, bad news?

Tablet dead after booting from Windows 10 pen drive

I've inserted my pen drive with Win10, and a keyboard, onto a hub with the OTG cable that came with the tablet. I opened the BIOS with Esc, booted from the pen drive. It was stuck with the teclast chinese letters logo for about 2-3mins before displaying a Windows error message / blue screen with a face and the following error code: ACPI_BIOS_ERROR. I turned it off by pressing the power button for 8 seconds, then tried to boot again. Nothing. Zero. No reaction. I've plugged it into the charger and it's still dead. What the actual hell? What have I done that I can't even power the tablet on? I hope I didn't hardbrick it.... What happened and what can I do?
EDIT: I mean what the actual hell I bought a tablet, I boot from a pen drive, and it goes dead?? Doesn't even power on even when I plug it into the wall?? Guys what the f**, what happened? I'm freaking out a bit.
EDIT 2: I completely forgot: the tablet is an Air III (m5c5). Thanks for any help!

Sounds like you tried to boot from a x64 edition image and hardbricked the device.

cscz23 said:
Sounds like you tried to boot from a x64 edition image and hardbricked the device.
Click to expand...
Click to collapse
Okay, so what do I do now? How do I recover it?

Your BIOS has been corrupted as you've tried to boot an x64 image from an x86 EFI.
You'll have to replace/reprogram the BIOS chip on your device to unbrick.

cscz23 said:
Your BIOS has been corrupted as you've tried to boot an x64 image from an x86 EFI.
You'll have to replace/reprogram the BIOS chip on your device to unbrick.
Click to expand...
Click to collapse
Well, I didn't know that merely attempting to boot a x64 image hardbricked the tablet... :S Anyways, thanks. Do you have any guide on how to do that? I assume you need an EEPROM programmer, right? Also any guides on how to open up the tablet? Thanks.
Isn't there any other way to do it, that doesn't involve opening the tablet and buying a reprogrammer?

andrepd said:
Well, I didn't know that merely attempting to boot a x64 image hardbricked the tablet... :S Anyways, thanks. Do you have any guide on how to do that? I assume you need an EEPROM programmer, right? Also any guides on how to open up the tablet? Thanks.
Isn't there any other way to do it, that doesn't involve opening the tablet and buying a reprogrammer?
Click to expand...
Click to collapse
you can buy a ch341a on ebay or use an arduino or raspberry pi if you have one of those to reprogram the bios. The three of them will work. If you want the easiest method, go for the ch341a

iscle said:
you can buy a ch341a on ebay or use an arduino or raspberry pi if you have one of those to reprogram the bios. The three of them will work. If you want the easiest method, go for the ch341a
Click to expand...
Click to collapse
I have a raspberry pi. But apparently it works at 3.3V while the BIOS chip works at 1.8V. Is this a problem?

andrepd said:
I have a raspberry pi. But apparently it works at 3.3V while the BIOS chip works at 1.8V. Is this a problem?
Click to expand...
Click to collapse
no, it shouldn't be. the ch341a works on 3v3 also and it has worked for everybody. I think in XDA there is a tutorial for using the rpi as a bios flasher for the teclast.

iscle said:
no, it shouldn't be. the ch341a works on 3v3 also and it has worked for everybody. I think in XDA there is a tutorial for using the rpi as a bios flasher for the teclast.
Click to expand...
Click to collapse
There is, but someone was mentioning on that thread that the rpi GPIO working at 3.3V was a problem, that's why I asked just to make sure. Thanks!

andrepd said:
There is, but someone was mentioning on that thread that the rpi GPIO working at 3.3V was a problem, that's why I asked just to make sure. Thanks!
Click to expand...
Click to collapse
try it and tell us how it went!

CM13 and future son in law bricked my Lg G2

So here is what I know, an attempt was made to update my G2 by someone other than myself. It now has a black screen and no recovery, it has also been attempted to be repaired by the same person. My pc no longer sees my phone, no download mode or anything else. Is there any hope for this device?

Well, any thoughts from the vast knowledge pooled on here?

godzilla61 said:
Well, any thoughts from the vast knowledge pooled on here?
Click to expand...
Click to collapse
Power on? Anything?
Sent from my Nexus 6 using XDA Free mobile app

31ken31 said:
Power on? Anything?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Downlad and run SRKtool_2.1_droidth with the correct drives.. All will be well again..

tried the srktool, no drives detected. the qhsusb_bulk driver loads so it does see something......

godzilla61 said:
tried the srktool, no drives detected. the qhsusb_bulk driver loads so it does see something......
Click to expand...
Click to collapse
When you start it pick #4 fixed then #5 unbrick.. You must have had USB Debugging mode Enable prior to bricking.. Also check device manager in windows and check ports.. Will try to help you the best I can, had the same issue 3 days after getting the phone.. If you get it to work after use th Lg program and do fix phone or you will have a lot of issues.

No JOY,
hankbizzo5 said:
When you start it pick #4 fixed then #5 unbrick.. You must have had USB Debugging mode Enable prior to bricking.. Also check device manager in windows and check ports.. Will try to help you the best I can, had the same issue 3 days after getting the phone.. If you get it to work after use th Lg program and do fix phone or you will have a lot of issues.
Click to expand...
Click to collapse
The problem I'm running into is there isn't a bunch of disks shown, only the fixed disks in my comp. So nothing is being seen or they are not there to see.

godzilla61 said:
The problem I'm running into is there isn't a bunch of disks shown, only the fixed disks in my comp. So nothing is being seen or they are not there to see.
Click to expand...
Click to collapse
That is what should happen.. You need the qhsusb QUALCOMM DRIVER..

it is seen as that and on com 7, tried the srktool, no drives detected. the qhsusb_bulk driver loads so it does see something......

Well, I guess it's dead if no one else has any suggestions....... what a shame I really liked this device.

godzilla61 said:
So here is what I know, an attempt was made to update my G2 by someone other than myself. It now has a black screen and no recovery, it has also been attempted to be repaired by the same person. My pc no longer sees my phone, no download mode or anything else. Is there any hope for this device?
Click to expand...
Click to collapse
Does your phone boot? Does it charges?

yes it charges. no it does not boot.

godzilla61 said:
yes it charges. no it does not boot.
Click to expand...
Click to collapse
I have the VS980 (Verizon version) and I was completely...and I mean completely dead (due to my own mistake) , no charge, no power, no download mode, no led, nothing at all. I had a full on 100% brick sitting on my desk. BUT.....I went here, http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404 and was able to bring it back to life. Now yes you do have to open the device and mess with inside parts but i was able to get mine going. The guide here is for the other models (specifically not the vs980) but I was able to finagle the inside parts to make it work the way I needed to. From there I was able to boot back up and i flashed all the way back to 10B and just OTA back up to lollipop and root again and install TWRP and I'm back up to where I was a few weeks ago, of course I lost everything (texts,photos) in the process but I am back up and running and I am happy I was able to pull that off thanks to the great folks who figure all this stuff up for us.
So I would say go for it and try it, or if not I could do it for you, and if not I'm am surely positive that someone here can help you figure it out with your current situation. Cheers.
PS, if you dont want to mess with it, just let me have it LOL!

Hard bricked stock HTC One M7

Hi, new to this forum so apologies in advance if I write something really noobish here.
So my old device HTC One M7 decided to kill itself for no reason, it's completely stock, I haven't tampered with it at all.
I had it on power saver mode because I had been on an interrail trip through Europe and then just one morning it died without warning, the night before I plugged it in to charge and when dawn breaks, it's dead.
I first thought it was the black screen of death that some Android might suffer from but I tried the steps of shining a bright light at the top left corner of the screen but nada, and then I plugged it into my laptop which saw it as "Qualcomm HS-USB QDLoader 9008" and I tried some steps from the guide that dexter93 posted and well it didn't work, I also tried to use a RUU but it always returned with that there wasn't any device connected to the USB port, however something happened because now it's not shown as the "Qualcomm HS-USB QDLoader 9008" but as the "QHSUSB-DLOAD".
I don't know what it means but I hope that my device hasn't passed the Gates of Valhalla.
If you need more specific information please do tell me /BTV

BorisTheViking said:
Hi, new to this forum so apologies in advance if I write something really noobish here.
So my old device HTC One M7 decided to kill itself for no reason, it's completely stock, I haven't tampered with it at all.
I had it on power saver mode because I had been on an interrail trip through Europe and then just one morning it died without warning, the night before I plugged it in to charge and when dawn breaks, it's dead.
I first thought it was the black screen of death that some Android might suffer from but I tried the steps of shining a bright light at the top left corner of the screen but nada, and then I plugged it into my laptop which saw it as "Qualcomm HS-USB QDLoader 9008" and I tried some steps from the guide that dexter93 posted and well it didn't work, I also tried to use a RUU but it always returned with that there wasn't any device connected to the USB port, however something happened because now it's not shown as the "Qualcomm HS-USB QDLoader 9008" but as the "QHSUSB-DLOAD".
I don't know what it means but I hope that my device hasn't passed the Gates of Valhalla.
If you need more specific information please do tell me /BTV
Click to expand...
Click to collapse
Dead motherboard

alray said:
Dead motherboard
Click to expand...
Click to collapse
How can you be so sure?

BorisTheViking said:
How can you be so sure?
Click to expand...
Click to collapse
3 years in this forum, saw hundreds of QHSUSB_DLOAD threads/posts.
Either caused by
flashing an incompatible firmware:
Flashed incompatible firmware, then rebooted the phone and went directly in QHSUSB_DLOAD mode.
Hardware problem:
Phone randomly shut-off and went in QHSUSB_DLOAD mode.
Most of the time, when its caused by #1, you can fix it using dexter93's Unbrick Project. If its #2 you'll have to send it for repair.
Yo can however try the Unbrick Project, just to be sure (maybe your firmware got corrupt for whatever reason and the hardware is still good)

alray said:
3 years in this forum, saw hundreds of QHSUSB_DLOAD threads/posts.
Either caused by
flashing an incompatible firmware:
Flashed incompatible firmware, then rebooted the phone and went directly in QHSUSB_DLOAD mode.
Hardware problem:
Phone randomly shut-off and went in QHSUSB_DLOAD mode.
Most of the time, when its caused by #1, you can fix it using dexter93's Unbrick Project. If its #2 you'll have to send it for repair.
Yo can however try the Unbrick Project, just to be sure (maybe your firmware got corrupt for whatever reason and the hardware is still good)
Click to expand...
Click to collapse
But that's the thing, it did randomly shut itself down but it entered Qualcomm HS-USB QDLoader 9008 mode instead of QHSUSB_DLOAD mode.
I myself managed to get it into QHSUSB_DLOAD mode.

BorisTheViking said:
But that's the thing, it did randomly shut itself down but it entered Qualcomm HS-USB QDLoader 9008 mode instead of QHSUSB_DLOAD mode.
I myself managed to get it into QHSUSB_DLOAD mode.
Click to expand...
Click to collapse
If dexter93's guide didn't helped then there's nothing more you can do. You're not the first one and not the last one to have this problem and unless it was caused by a bad firmware.zip flash (it wasn't) no one ever found a solution to revive their phone.
Sent from my HTC One using XDA Labs

alray said:
If dexter93's guide didn't helped then there's nothing more you can do. You're not the first one and not the last one to have this problem and unless it was caused by a bad firmware.zip flash (it wasn't) no one ever found a solution to revive their phone.
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
Not even JTAG?
And if I manage to open the phone, you wouldn't know where the internal storage is?

BorisTheViking said:
Not even JTAG?
And if I manage to open the phone, you wouldn't know where the internal storage is?
Click to expand...
Click to collapse
The internal storage is a tiny Samsung chip soldered on the motherboard.
Sent from my HTC One using XDA Labs

alray said:
The internal storage is a tiny Samsung chip soldered on the motherboard.
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
Right and that translates to that everything is burnt to a crisp?
So there is no way to retrieve anything from the internal storage?