Database Info

In QHSUSB_DLOAD Mode, nothing working

Hi everyone,
Whilst trying to test a custom bootloader I made, I tried to flash a PJ40IMG.zip in RUU Mode. It started flashing, then froze completely. It displayed finished, but remained frozen on the phone screen. Then the screen disappeared. Upon insertion again, the phone went on to QHSUSB_DLOAD mode.
I have QPST, but no idea how to use it, and don't have the Qualcomm drivers installed, since they are only for x64 machines.
I have tried the unbrick thread in the development section. It flashed the HBOOT, then stood stuck on waiting for /dev/sdb12 I tried holding down POWER again, but didn't recognize the device like it did previously. Now, if I try again and spam
Code:
ls /dev/sd*
the partitions are no longer seen, no matter how fast I try and do it. I have attempted this multiple times, even tried the PblClear tool from unlimited.io, to no avail.
Any ideas? I think I will have a permanent paperweight at this stage.

usaff22 said:
Hi everyone,
Whilst trying to test a custom bootloader I made, I tried to flash a PJ40IMG.zip in RUU Mode. It started flashing, then froze completely. It displayed finished, but remained frozen on the phone screen. Then the screen disappeared. Upon insertion again, the phone went on to QHSUSB_DLOAD mode.
I have QPST, but no idea how to use it, and don't have the Qualcomm drivers installed, since they are only for x64 machines.
I have tried the unbrick thread in the development section. It flashed the HBOOT, then stood stuck on waiting for /dev/sdb12 I tried holding down POWER again, but didn't recognize the device like it did previously. Now, if I try again and spam
Code:
ls /dev/sd*
the partitions are no longer seen, no matter how fast I try and do it. I have attempted this multiple times, even tried the PblClear tool from unlimited.io, to no avail.
Any ideas? I think I will have a permanent paperweight at this stage.
Click to expand...
Click to collapse
I don't want to kick you while you're down but you tried to write a custom hboot then tried to install it with the PJ40IMG.zip method? That method has never been used on the One S. No one does it that way. The only reason it worked now was that you have S-OFF and look what happened. How come you didn't try to fastboot flash it?
Back to your question. I've never seen someone recover from the partitions not being enumerated. You're going to need to unbrick it with JTAG. I recommend you use these people http://mobiletechvideos.mybigcommerce.com/htc-one-s-jtag-brick-repair/

dc211 said:
I don't want to kick you while you're down but you tried to write a custom hboot then tried to install it with the PJ40IMG.zip method? That method has never been used on the One S. No one does it that way. The only reason it worked now was that you have S-OFF and look what happened. How come you didn't try to fastboot flash it?
Back to your question. I've never seen someone recover from the partitions not being enumerated. You're going to need to unbrick it with JTAG. I recommend you use these people http://mobiletechvideos.mybigcommerce.com/htc-one-s-jtag-brick-repair/
Click to expand...
Click to collapse
No, the plugin gave me a PJ40IMG.zip which I then flashed in RUU mode, the same way that a fastboot zip would, since I knew flashing it via the PJ40IMG method wouldn't work without a USB Y Cable, since it only works with a device that supports microSD.
fastboot oem rebootRUU
and then
fastboot flash zip PJ40IMG.zip

usaff22 said:
No, the plugin gave me a PJ40IMG.zip which I then flashed in RUU mode, the same way that a fastboot zip would, since I knew flashing it via the PJ40IMG method wouldn't work without a USB Y Cable, since it only works with a device that supports microSD.
fastboot oem rebootRUU
and then
fastboot flash zip PJ40IMG.zip
Click to expand...
Click to collapse
I'm glad you learned that! I had seen you recommend to others that you can just put it on your sdcard and it would work. My mistake that I assumed you did it yourself.
I know you've been waiting a long time for S-OFF, sorry to hear you bricked your phone so quickly after finally getting it. Good luck with the jtag. Or if you find another solution let us know.

dc211 said:
I'm glad you learned that! I had seen you recommend to others that you can just put it on your sdcard and it would work. My mistake that I assumed you did it yourself.
I know you've been waiting a long time for S-OFF, sorry to hear you bricked your phone so quickly after finally getting it. Good luck with the jtag. Or if you find another solution let us know.
Click to expand...
Click to collapse
Thanks, I knew it wouldn't work after I saw someone on the One XL forums who tried it on his with a USB Y Cable, and didn't look for the zip on the internal storage. I used to think it would work after doing it on my brother's Sensation, but it was a no go for me.
At this stage I think I will have to visit my carrier. Hopefully they can give me a replacement or get it fixed somehow.

This should be helpfull
http://forum.xda-developers.com/showthread.php?t=1990043&highlight=downgrade

Fofff said:
This should be helpfull
http://forum.xda-developers.com/showthread.php?t=1990043&highlight=downgrade
Click to expand...
Click to collapse
I tried that, my partitions won't show so it is of no help to me unfortunately.

[Q] Android noob Moto G bricked?

Hello, I've bricked my device (( moto g xt1032, I bought the device from Tesco back in 2013 and I just wanted to get the lollipop update on my phone, I looked online and found this video: watch?v=-L44JqysUy8 it didnt do as intended it rebooted and my device was ok, so I looked again and came accross a thread here on XDA: http://forum.xda-developers.com/moto-g/general/gpe-ota-lrx21z-5-0-1-xt1033-xt1032-t2969847
first mistake I made was doing step 2.1 instead of going straight to 2.2, my phone rebooted and got stuck in a boot loop (i think, it was a black powered by android screen) I looked on google yet again and found an article that told to clear the cache in recovery I did that and it didnt work, boot loop again, then I found a forum post saying that having bluestacks on your machine will cause a conflict I uninstalled that and started from scratch with the same problem, I re did the steps seen in the above youtube video thinking that would put my device back to normal and still stuck in bootloop with the blue motorola m logo, I cant enter recovery of the fast boot menu anymore and my battery doesnt seem to be charging, its essentially a paperweight.

paulh2k8 said:
Hello, I've bricked my device (( moto g xt1032, I bought the device from Tesco back in 2013 and I just wanted to get the lollipop update on my phone, I looked online and found this video: watch?v=-L44JqysUy8 it didnt do as intended it rebooted and my device was ok, so I looked again and came accross a thread here on XDA: http://forum.xda-developers.com/moto-g/general/gpe-ota-lrx21z-5-0-1-xt1033-xt1032-t2969847
first mistake I made was doing step 2.1 instead of going straight to 2.2, my phone rebooted and got stuck in a boot loop (i think, it was a black powered by android screen) I looked on google yet again and found an article that told to clear the cache in recovery I did that and it didnt work, boot loop again, then I found a forum post saying that having bluestacks on your machine will cause a conflict I uninstalled that and started from scratch with the same problem, I re did the steps seen in the above youtube video thinking that would put my device back to normal and still stuck in bootloop with the blue motorola m logo, I cant enter recovery of the fast boot menu anymore and my battery doesnt seem to be charging, its essentially a paperweight.
Click to expand...
Click to collapse
im now back to the boot loop thing not much better lol, is it fixable or should i just not bother

If it is booting up, then probably it is soft bricked. Not hard bricked.

If it can detect in ADB, re-flash the recovery?

Thankyou both for your replies, I dont know why I bothered back in the day symbian was so much easier lol, im an absolute noob when it comes to this so how would i go about getting to the recovery you mention, i can get to the fastboot menu but after selecting recovery the phone just loops at the boot logo

SInce it is bootlooping, I'm not sure which ROM is currently on your phone.
Try and flash the recovery from the ROM you tried to install by finding the recovery.img file, boot the phone into fastboot, and type "fastboot flash recovery recovery.img" or, if using mfastboot commands, type "mfastboot flash recovery recovery.img".
If you can't get into recovery, flash the recovery from your original ROM.
If you still can't get into recovery, flash your stock ROM, one partition at a time.
In fastboot, which bootloader version is on your phone?

the last thing I flashed was the link provided in the youtube vdeo if that helps, ive done the recovery thing and it still loops, my bootloader hmm im not sure heres the details from the fast boot screen..
AP Fastboot Flash Mode (S)
41.13 (sha-7dc8e78, 2014-06-16 16:33:29)
Device is locked Status Code (0)

is it because my bootloader is locked, I fail

You need to unlock your bootloader via the motorola website.

Thanks for your reply it turns out its not eligible for unlock for some reason so I'm deciding its a decent paper weight and giving up, I really appreciate the replies and the time the posters have taken out to help, I'll know to take my time to read every detail if I decide to do this again, thankyou!!

Are you sure it's not eligible? I thought my Telus xt1032 was not eligible but it turns out I mistyped a couple of numbers.
I tried a few hours later and I got the code from Motorola.

audit13 said:
Are you sure it's not eligible? I thought my Telus xt1032 was not eligible but it turns out I mistyped a couple of numbers.
I tried a few hours later and I got the code from Motorola.
Click to expand...
Click to collapse
I copied and pasted direct from the cmd, I read on another forum that you needed to be logged into the phone with the Motorola account which I didn't

I don't recall logging into the phone, I just recall logging into the Moto site with a google ID.

Don't worry bro just try and you will be successful. I'm also bricked my Micromax Canvas A1 on first try.

audit13 said:
I don't recall logging into the phone, I just recall logging into the Moto site with a google ID.
Click to expand...
Click to collapse
Thanks ill try it again

lol i need to wake up, I had spaces when iIcopied from the cmd its working now... and I have the code!!!

and im unlocked ! so what do i do know, i dont want to ruin it all now

Excellent. Boot into fastboot and post your bootloader version. It should be 41.xx.

41.13 ? thats on the second line in the boot menu

You have a KK bootloader. I suggest downloading the stock 4.4.4 ROM for your carrier and flash everything except the gpt and motoboot file. Once you finish flashing all partitions via fastboot, use the phone's volume button to boot into recovery, wipe perform a full wipe, and reboot.

[Q] Nexus 5 stuck on google logo boot loop

Hello everybody here at XDA, ( this is my first post here so bare with me here)(english is not my native language either)
My device:
Nexus 5 - hammerhead D821(H) 16GB
BL version - HHZ12h
BB version M8974A-2.0.50.2.26
Secure boot enabled
lock state unlocked
today i got a "broken" nexus 5 that is in boot loop with the google logo and it wont boot into any .img
At the start i read the pinned posts and found this tutorial: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
followed it step by step. but unfortunatly it didnt help my situation. there werent any errors or such kind.
i also tried this tutorial with other images but nothing worked.
When i go to the recovery mode and press the power button the phone get into the google logo and i can see some sort of strange stripes in like a milisecond but then it just gets into the boot loop.
i really think ive tried everything accept for relocking the bootloader but cant imaging that this could be the problem.
If you guys need more info please just ask me.
Hope you guys can help me out here.
Martin

Really thought XDA forums would be able to help me.
Any admins or mods or any other veteran that could help me out?

If that's not working for you, you can try using the Nexus Root Toolkit just to be sure.
If that doesn't work, than it could be hardware related, and not much you can do about that.

Hi All,
I have boot-loop problem for Nexus5 as described earlier .
As I was able to boot in Fastboot
I went for factory reset, and saw FAILED (remote: flash write failure).
I have tried to flash countless time with same error.
Then I read this thread and considered phone memory is toasted.
LG service-center have quoted me around $180 for mother board replacement.
Today I tried twrp project to boot in openrecovery and start an adb shell.
I was able to see file system of my phone.
These following folders are empty:
/boot
/cache
/data
In system folder there is only bin folder and which is empty.
/system
I have gotten this far, is internal memory roasted
Any direction or suggestions welcomed :good:

mesh120673 said:
Hi All,
I have boot-loop problem for Nexus5 as described earlier .
As I was able to boot in Fastboot
I went for factory reset, and saw FAILED (remote: flash write failure).
I have tried to flash countless time with same error.
Then I read this thread and considered phone memory is toasted.
LG service-center have quoted me around $180 for mother board replacement.
Today I tried twrp project to boot in openrecovery and start an adb shell.
I was able to see file system of my phone.
These following folders are empty:
/boot
/cache
/data
In system folder there is only bin folder and which is empty.
/system
I have gotten this far, is internal memory roasted
Any direction or suggestions welcomed :good:
Click to expand...
Click to collapse
Are you sure your bootloader is unlocked?
When you boot the phone in Fastboot mode, does the "lock state" say UNLOCKED?
If so, then yeah, your internal memory could be huffed.

spookytay said:
Are you sure your bootloader is unlocked?
When you boot the phone in Fastboot mode, does the "lock state" say UNLOCKED?
If so, then yeah, your internal memory could be huffed.
Click to expand...
Click to collapse
It says Locked.
I unlock it using ./fastboot oem unlock

I just got my N5 and was messing around. Rooted it and loaded a rom, but it would just seem to hang at the spinning dots forever. Though I didn't wait THAT long like some users did and had success.
I can't find the link I used, but googling around should get you there. I ended up restoring a factory image via fastboot. I ended up using THIS PROGRAM to root the phone. This program also has a restore option and gives an option to check in case you are in boot loop status. Give it a shot.
Yes I do believe you have to unlock the bootloader as well.

Nurmi_CEO said:
I just got my N5 and was messing around. Rooted it and loaded a rom, but it would just seem to hang at the spinning dots forever. Though I didn't wait THAT long like some users did and had success.
I can't find the link I used, but googling around should get you there. I ended up restoring a factory image via fastboot. I ended up using THIS PROGRAM to root the phone. This program also has a restore option and gives an option to check in case you are in boot loop status. Give it a shot.
Yes I do believe you have to unlock the bootloader as well.
Click to expand...
Click to collapse
Yes the bootloader must be unlocked before you can do ANYTHING to the phone, it's what's there to protect it from being hacked/changed or whatever. So before you can write anything to your phone, you need to make sure you OEM UNLOCK the bootloader.

[Solved!] Nexus 5 boot loop at Google logo
I found a solution on Youtube comment (can't post url, too new user).
You just have to press quickly the Power button durint 1-2 minutes (continue untill the Android animation start, don't stop when the Google logo appear)3
As crazy as it sounds, IT WORKS

Wow .. i had the exact same problem (Startup loop on Nexus 5 that shows the Google logo and restarts, over and over), and i pressed the power button quicky about 30 or 40 time until after I saw the startup animation and my phone came back to life. I have been charging it with cables other than the one that came with the phone for a few months now, and it has been acting strangely while plugged in (randomly clicking things on the screen, and enabling my camera and taking pictures on its own, etc.). So, to avoid problems in the future, I think I'll invest in a wireless charger. Thanks JackNUMBER for the easy solution. I hope this works for others as well. Saved me a trip to the store.

Oneplus One Freezing On Startup

He there, just recently my phone had an update and i said yes to it. After the update completed It rebooted but never started back up.
When turned on, it just get up to the OnePlus One logo screen and stays there. I have tried a factory reset as I can access the recovery menu but the factory reset doesn't seem to do anything. I let the battery drain until the phone died and then charged it but it still will not start. Plugging it into my PC lets it charge but it does not let you access the storage. Its not a driver problem as it was working fine before the update.
I have tried fast boot but it just gets stuck on the fast boot screen.
I tried using OnePlus One Toolkit but it cant find the phone
I have read that I need to flash it but it would seem I need to transfer a file onto the phone but nothing recognizes the phone to transfer it to.
Can anyone help?
Thanks in advance,

Zastarx said:
He there, just recently my phone had an update and i said yes to it. After the update completed It rebooted but never started back up.
When turned on, it just get up to the OnePlus One logo screen and stays there. I have tried a factory reset as I can access the recovery menu but the factory reset doesn't seem to do anything. I let the battery drain until the phone died and then charged it but it still will not start. Plugging it into my PC lets it charge but it does not let you access the storage. Its not a driver problem as it was working fine before the update.
I have tried fast boot but it just gets stuck on the fast boot screen.
I tried using OnePlus One Toolkit but it cant find the phone
I have read that I need to flash it but it would seem I need to transfer a file onto the phone but nothing recognizes the phone to transfer it to.
Can anyone help?
Thanks in advance,
Click to expand...
Click to collapse
Your persist partition might be corrupt. Grab this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/view?usp=docslist_api
Then do this with fastboot:
Code:
fastboot erase persist
fastboot flash persist persist.img

Didn't work sadly. Maybe I should just flash everything?

Zastarx said:
Didn't work sadly. Maybe I should just flash everything?
Click to expand...
Click to collapse
Yeah, it's worth a shot. You can find full instructions in section 8 of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471

Yay!
It worked, thanks a lot!

Nexus 5 bootloop, stuck in Rom intro - Don't know how to connect it to my pc

First of all, I'm pretty noob this days on Android so I'm very sorry guys, also english is not my first language.
My nexus was working great until today. I ended a Whatsapp Call and get a black screen, phone looks frozen (happened before). Reboot it and works fine for 5-10 minutes, after that it started to reboot itself the whole time in bootlop, stuck in the rom intro, after the Google text. My rom is one of the very first roms from Slim Roms, I'm sorry I don't remember the Android Version, but is "old".
I can access to the recovery mode tho. I tried to wipe dalvik cache and the TWRP failed, wipe and factory reset, fail as well... I don't know what else to do. I don't have any image to install in the sd, or any backup. Windows 10 recognize an "android" but can't access to it so I can't copy any file to it.
Is my phone dead or can I do something? I love this phone :crying:

Any help please? I tried using ADB and get to copy some files into the phone but still every time I try to do a wipe cache, factory reset or what ever I get a Unable to mount Data / Cache / Storage... every time the same error.
I google it and found that some people could fix that error by repairing the file system and select ext4. But I can't do that, my TWRP build is quite old (v2.6.3.4) and doesn't have that option here. Any suggestions?
Thanks btw

Me again
I've been reading forums for more than 7 hours today and trying different solutions, and nothing. But found this guy here https://androidforums.com/threads/is-my-nexus-5-dead.1099076/
He basically had the same issue as me few years ago, exactly the same, He didn't find any luck apparently.
How is it possible that a phone that can get access to TWRP or copy/flash files via ADB/Fastboot can't be saved? Theoretically in this case this is not a hard bricked, right? So? This is so so weird

It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.

No OS but twrp working
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!

audit13 said:
It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.
Click to expand...
Click to collapse
I tried that already, it does the installation thing but always fail in the end
mevrik_007 said:
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!
Click to expand...
Click to collapse
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad

ekeixdurden said:
I tried that already, it does the installation thing but always fail in the end
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad
Click to expand...
Click to collapse
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.

audit13 said:
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.
Click to expand...
Click to collapse
I tried that with the Nexus root tool kit and the bootloader still is unlocked

ekeixdurden said:
I tried that with the Nexus root tool kit and the bootloader still is unlocked
Click to expand...
Click to collapse
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.

audit13 said:
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.
Click to expand...
Click to collapse
Shieeeet... So nothing to do I guess? I already ordered a new phone but if I can save this beauty would be great

It would be great to fix it but the simplest solution may be to buy a nexus 5 with a smashed screen and working motherboard. I've done this before and it's worked out well because the nexus 5 is pretty old by today's phone standards so I got it cheap.

hmm not a bad idea at all. Thank you!