Was having wifi issues, found a tutorial on flashing firmware via usb, BUT downloaded an old firmware that made the whole device go to hell.
Has anyone managed to recover their device, or am I the only soul who was dumb enough to put myself in this situation.
I cannot get into fastboot, recovery, etc. booting leads to a blank screen.
Cheers
You will have to flash the stockrom files via Odin i am afraid
Sent from my SM-N920C using Tapatalk
Do you have any sort of instructions.
I'm sorta familiar with Odin, but I thought that fastboot was a requirement?
jewnersey said:
Was having wifi issues, found a tutorial on flashing firmware via usb, BUT downloaded an old firmware that made the whole device go to hell.
Has anyone managed to recover their device, or am I the only soul who was dumb enough to put myself in this situation.
I cannot get into fastboot, recovery, etc. booting leads to a blank screen.
Cheers
Click to expand...
Click to collapse
Hey were you able to fix this issue? I am having a similar issue currently and would appreciate any help.
jewnersey said:
Was having wifi issues, found a tutorial on flashing firmware via usb, BUT downloaded an old firmware that made the whole device go to hell.
Has anyone managed to recover their device, or am I the only soul who was dumb enough to put myself in this situation.
I cannot get into fastboot, recovery, etc. booting leads to a blank screen.
Cheers
Click to expand...
Click to collapse
Turns out i did the exact same and now i am in similar situation.
https://forum.xda-developers.com/google-glass/help/glass-wont-fastboot-mode-t3990575
did you manage to fix the problem?
Don't think it's fixable ?
[/COLOR]
jewnersey said:
Don't think it's fixable
Click to expand...
Click to collapse
I was able to make some progress. Whenever i tried to fastboot a device would popup for a second on the computer and then disappear. At first I thought it was fastboot interface but looking closely at the device "OMAP4430" with vid 0451 and pid D00F, turns out it is an interface used to flash new first stage and main bootloaders on various devices such as galaxy nexus and galaxy tab 2 along with pandaboard and certain lg phones. There are utilities such as OMAP flash (by Texas instruments) and OMAP4BOOT (unofficial open source) that could talk to the device using this protocol. People have made scripts around these utilities to unbrick other devices mentioned above. I have played with these tools and i am able to push first loader called MLO or " xloader" by TI, fortunately google provides xloader with XE23 but i am not been able to push the main bootloader perhaps someone with more experience can help write configuration scripts for these tools that would work on glass so that i can get to fastboot and restore my device.
Related
My milestone(Telus; BL 90.74) is pretty much bricked. I tried to do this, but like with everything else I do modding wise I failed horribly. It got to the point to where whenever I tried turning on my phone, it would stay frozen on the M logo. I've wasted my entire day searching from blogs to forums to videos trying to fix this but nothing worked. And now my phone won't even turn on unless I access the bootloader menu.
I know I have to reflash the sbf file, but the thing is my computer no longer detects my phone since the disaster. I'm really frustrated and stressed because of this. I thought doing a factory reset would do something but now all of my data on the phone is gone for nothing.
Can anyone please help? I know there's like 7 threads on this, but none of them help even if I follow the instructions step by step.
have made a backup? to open recovery?
Shoib said:
My milestone(Telus; BL 90.74) is pretty much bricked. I tried to do this, but like with everything else I do modding wise I failed horribly. It got to the point to where whenever I tried turning on my phone, it would stay frozen on the M logo. I've wasted my entire day searching from blogs to forums to videos trying to fix this but nothing worked. And now my phone won't even turn on unless I access the bootloader menu.
I know I have to reflash the sbf file, but the thing is my computer no longer detects my phone since the disaster. I'm really frustrated and stressed because of this. I thought doing a factory reset would do something but now all of my data on the phone is gone for nothing.
Can anyone please help? I know there's like 7 threads on this, but none of them help even if I follow the instructions step by step.
Click to expand...
Click to collapse
Do you get any error shown while going into bootloader mode?
Sent from my Milestone using Tapatalk
maybe try a diffrent computer first or try the official motorola update software?
press "up" on keyboard when power on, can it be detect by rsd now?
Sent from my Milestone using XDA App
max_avatar said:
have made a backup? to open recovery?
Click to expand...
Click to collapse
No, I haven't made a backup yet. I haven't accessed openrecovery either, the guide gave me a headache.
sileshn said:
Do you get any error shown while going into bootloader mode?
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
It says "Battery Ok
Ok to program
connect USB
Data Cable"
smokeymacweed said:
maybe try a diffrent computer first or try the official motorola update software?
Click to expand...
Click to collapse
I could try that by putting an official update.zip so the boot loader will accept. Problem is there isn't any updates further to what I have and froyo womn't come anytime soon unless you were referring to something else.
DummyPLUG said:
press "up" on keyboard when power on, can it be detect by rsd now?
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
Let me try this. I'm going to bed for now, Ill post results tomorrow.
You can try installing your usb drivers again and try.Since you did not get any error in the bootloader mode, it could be problems with your usb drivers.
Uninstall the usb drivers and reinstall them again. Then try.
BTW, which version of rsdlite are you using?
Helo
Maybe tray this:
- Download an RSD Lite (I use 4.7)
- Download an GOT firmware from: and-developers.com / sbf:milestone (bottom of site)
- Set the phone to bootloader mode
- Start RSD Lite with Administrator permissions
- Connect the phone
- Select the downloaded sbf file
- When U see phone connected click Start
Sorry for my english
xdazoli said:
Helo
Maybe tray this:
- Download an RSD Lite (I use 4.7)
- Download an GOT firmware from: and-developers.com / sbf:milestone (bottom of site)
- Set the phone to bootloader mode
- Start RSD Lite with Administrator permissions
- Connect the phone
- Select the downloaded sbf file
- When U see phone connected click Start
Sorry for my english
Click to expand...
Click to collapse
Ok, I did everything you said and flashed it with A853_Telus_Firmware_SHOLS_U2_03.10.0__USASHLSMR2TLSB1B2B505F.0R_1FF.sbf. But now it still gets stuck at the moto sign
Edit: I think I might have a solution as I flashed the phone with vulnerable_recovery_only_RAMDLD90_78.sbf which will let me use an update.zip. The only problem is I can't access my memory card and I don't have anything that could at home.
Edit: Ok, I fixed my phone and now it has 2.2.1. Thanks guys, I appreciate the help.
Actually my friend bricked his phone, he flashed the 5.1 bootloader and radio.then somehow he flasheed back to 5.0.1 stock. then he flashed Euphoria again. The phone rebooted fine and he went to sleep. Then woke up and found out his phone was dead. And all buttons combo didn't work at all. It's just a piece of dead body.When plugging into the PC, it shows qhsusb_bulk. There were devices that had same problems but they managed to unbrick it, But those methods don't apply to Shamu. Odd thing is I did the same thing so far my Nexus 6 is fine .I've started worrying, tho. We bought it from amazon.fr and I'm sure i dont want to send it back all the way from China to France.
Also , i read some dudes encountered the same problem after flashing Cm12 with 5.1 BL. I really need your help.
I tried Nexus Root Toolkit to flash the factory image, it didnt work. It's still using the fastboot, and ofc i don't get to go there.
I've installed the Qualcomm_QHSUSB_driver, but it doesn't seem to fix anything.
no one?
Mine has done the same thing. Went to flash 5.1 nexus image from the google dev site. The flash did boot and radio and failed size on system ( even re-downloaded). I plug my N6 into my linux machine and this what I get on lsusb "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)". I am also in need of help.
This updates been a nightmare
synapses said:
Mine has done the same thing. Went to flash 5.1 nexus image from the google dev site. The flash did boot and radio and failed size on system ( even re-downloaded). I plug my N6 into my linux machine and this what I get on lsusb "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)". I am also in need of help.
Click to expand...
Click to collapse
So you're like me, no way to enter bootloader right? I've seen some other phones with the same problems but they figured a way out to solve it. I don't know we'll get that
beachbum40 said:
This updates been a nightmare
Click to expand...
Click to collapse
I'm not sure it has anything to do with the update. My friend didn't flash the 5.1 google factory image . He flashed the 5.1 BL on a 5.0.2 aosp based rom then went back to stock 5.0.1 then flashed the same 5.0.2 aosp rom. Now it ends up dead.
This happened on Samsung devices too and it was a emmc issue, so the internal drive among others was no longer readable and writable and hardware like buttons was not working either. Unless someone comes with the golden tip you`ll have to turn it in for repair. Good luck guys
randy6644 said:
So you're like me, no way to enter bootloader right? I've seen some other phones with the same problems but they figured a way out to solve it. I don't know we'll get that
Click to expand...
Click to collapse
doing some reading and it seams to be a broken bootloader.
synapses said:
doing some reading and it seams to be a broken bootloader.
Click to expand...
Click to collapse
I'm also a g2 owner, some just broke their devices and ended up sth similar. But they managed to unbrick it. I don't know if we stand a chance to bring it back to life.
I'm still stuck. Any progress ?
synapses said:
doing some reading and it seams to be a broken bootloader.
Click to expand...
Click to collapse
Any progress? I tried several ways and none of them worked
I had to RMA
randy6644 said:
Actually my friend bricked his phone, he flashed the 5.1 bootloader and radio.then somehow he flasheed back to 5.0.1 stock. then he flashed Euphoria again. The phone rebooted fine and he went to sleep. Then woke up and found out his phone was dead. And all buttons combo didn't work at all. It's just a piece of dead body.When plugging into the PC, it shows qhsusb_bulk. There were devices that had same problems but they managed to unbrick it, But those methods don't apply to Shamu. Odd thing is I did the same thing so far my Nexus 6 is fine .I've started worrying, tho. We bought it from amazon.fr and I'm sure i dont want to send it back all the way from China to France.
Also , i read some dudes encountered the same problem after flashing Cm12 with 5.1 BL. I really need your help.
I tried Nexus Root Toolkit to flash the factory image, it didnt work. It's still using the fastboot, and ofc i don't get to go there.
I've installed the Qualcomm_QHSUSB_driver, but it doesn't seem to fix anything.
Click to expand...
Click to collapse
Something should be able to be done using QPST (i.e., to force flash the bootloader), but that is above my level of knowledge.
efrant said:
Something should be able to be done using QPST (i.e., to force flash the bootloader), but that is above my level of knowledge.
Click to expand...
Click to collapse
I'm going through similar with a dead Nexus 7. I think the eMMC died in it though, as it just went out without any tinkering. No sign of life on the device, but is picked up as a Qualcomm modem port and detected by QPST in download mode. I don't have/can't find the hex files required by QPST to flash it though.
I theorize that if a working device can be put in QPST "diag" mode, then QPST will allow exporting the storage contents in a flashable hex file, and that file could be used to restore the boot partitions on the dead device. I haven't been able to find information about this "diag"nostic mode, however.
Same issue guys, Upgraded to 5.1 OTA rooted and flashed cm12 tried to reboot. Nothing. Stuck in "Qualcomm HS-USB QDLoader 9008" QPST will recognize it in Download mode. If we can get these Hex files I will give it a shot. Thanks!
http://bbs.gfan.com/forum.php?mod=viewthread&tid=7863761
found sth here dont know if its useful, all written in Chine
randy6644 said:
http://bbs.gfan.com/forum.php?mod=viewthread&tid=7863761
found sth here dont know if its useful, all written in Chine
Click to expand...
Click to collapse
Cant find much relating to our issue but there may be relevant info there, we cant download or make an account on that site due to our american IP anyway.
i will upload them when im home. i read sth about qc diag interface,qcn stuff. but this thread is a tutorial for cracking the China Telecom band. Dont know if theres anything useful
randy6644 said:
i will upload them when im home. i read sth about qc diag interface,qcn stuff. but this thread is a tutorial for cracking the China Telecom band. Dont know if theres anything useful
Click to expand...
Click to collapse
If you are able to export the Hex file with everything we need to restore through QPST you will be saving alot of peoples ass as the number of hard bricks are growing hourly now! Or at least the threads being started about hard bricks are! Appreciate the help brother. AdA
im not sure if i can find the useful files you need. just trying my best to contact that op , if he knows sth. my ass will ne saved. but its 1 .30 am in China.i dont think hes awake. i will keep an eye on that.
Ok I need some help. As of right now my tab is dead, the only thing it does when powered on is loads to the Asus splash screen and that's all. I can not get it into Fastboot mode at all and Adb cant find it either. I have already tried Sp Flashtools to no avail. I have all the Vcom drivers installed, every where I searched the one driver that people talked about was the mtk6585 driver ( I think that's what it is ) , the one for me that popped up and went away really fast was a driver called CLOVERVIEW. So needless to say I cant get SP Flash tools to work, and without fastboot mode im really stuck. Ever since I first came across this site a few years back I have rooted, and put custom roms on countless devices, I would call myself an experienced flasher. Well this tab has me feeling like a real noob, I can not figure it out. So if someone can help me it would be greatly appreciated. Thank you XDA world.
Try this: http://forum.xda-developers.com/android/help/instructions-reviving-me170c-me170cx-t3017466
It worked for me.
silviu74 said:
Try this: http://forum.xda-developers.com/android/help/instructions-reviving-me170c-me170cx-t3017466
It worked for me.
Click to expand...
Click to collapse
Wont work for me. Like I said, I cant get into droidboot.
Downloading android studio and all sdk tools, hopefully something in this will help. I will post updates on any progress.
zMILWAUKEE said:
Downloading android studio and all sdk tools, hopefully something in this will help. I will post updates on any progress.
Click to expand...
Click to collapse
I just got myself into the same situation. If you can get to a point where CLOVERVIEW comes up, that can be fixed (I actually just added a howto to the general section). However, I don't know how to get out of the stuck splash screen, since it's an awkward medium between download and fastboot. I'm not even sure what I did to cause this; I had just flashed boot.img and splashscreen.img and issued a fastboot reboot-bootloader.
The device does indeed pop up in download mode for about a second while booting; doesn't seem long enough for a flash. I would really like to find out if there is any way to force this device to boot into download mode.
Hi Everyone,
First off I am a total novice and I put my hands up to say I should not have tried to root my phone. I merely wanted to root so that I could actually use the space on my SD card, which the HTC Desire doens't.
I did try to do this manually by reading a few guide and walkthroughs with no success. So then I used the sunshine app to unlock my bootloader and then WinDriod to load TWRP recovery and then hopefully root the phone. It does say ***unloacked*** on the fastboot menu. However, I sort of messed up my phone.
I cannot load into recovery mode - it goes to a HTC load screen then right back to fastboot usb menu.
I cannot factory restore the phone either.
Can anyone advise me how to return my phone to its normal state or advise on how to fix this problem?
Appreciate any help anyone can give me!
bbop107 said:
Hi Everyone,
First off I am a total novice and I put my hands up to say I should not have tried to root my phone. I merely wanted to root so that I could actually use the space on my SD card, which the HTC Desire doens't.
I did try to do this manually by reading a few guide and walkthroughs with no success. So then I used the sunshine app to unlock my bootloader and then WinDriod to load TWRP recovery and then hopefully root the phone. It does say ***unloacked*** on the fastboot menu. However, I sort of messed up my phone.
I cannot load into recovery mode - it goes to a HTC load screen then right back to fastboot usb menu.
I cannot factory restore the phone either.
Can anyone advise me how to return my phone to its normal state or advise on how to fix this problem?
Appreciate any help anyone can give me!
Click to expand...
Click to collapse
Hello,
Since you asked for help with returning the phone to it's normal state I have some questions. Does the phone work normally? Can you make calls, text, and do other things when you simply power your phone on or is the OS deleted? Are you just referring to obtaining stock recovery or do you still want to get TWRP? It sounds like some error happened when you tried to flash TWRP and now you have no recovery. Here is a great guide that shows you how to flash TWRP. You can use that same guide to flash the stock recovery. That channel also has videos with an alternate method to unlock your bootloader and how to root the phone.
My phone works fine, makes calls, texts etc, I just can't boot into recovery. I tried several methods, following online videos etc to no avail, but ill give this one a go this evening. I mentioned returning it to its original state so I could start over with the flashing process as nothing seems to allow me to load into twrp, so i wondered if there was a corrupt file or something preventing me from doing so. The phone's bootloader is unlocked I believe as it says so on the hboot screen.
Thanks for the suggestion, ill let you know how it goes.
bbop107 said:
My phone works fine, makes calls, texts etc, I just can't boot into recovery. I tried several methods, following online videos etc to no avail, but ill give this one a go this evening. I mentioned returning it to its original state so I could start over with the flashing process as nothing seems to allow me to load into twrp, so i wondered if there was a corrupt file or something preventing me from doing so. The phone's bootloader is unlocked I believe as it says so on the hboot screen.
Thanks for the suggestion, ill let you know how it goes.
Click to expand...
Click to collapse
The method in that video should work perfect. I doubt there was a corrupt file, but we'll find out soon enough. I have a love/dislike relationship with WinDroid. I love it, because of how easy it is to use and it requires little to no knowledge of what you are actually doing and it is just a beautiful looking program. I dislike the fact that you pretty much learn nothing when you use it, as it does all of the work. Also, if you use the adb drivers it provides and you already have adb drivers, you will receive an error that the adb server is out of date.
i have xperia zr cc5502 with 5.1.1 stock installed on it
i have tried to follow CM tutorial on thier site wiki.cyanogenmod.org/w/Install_CM_for_yuga
but when im trying to do fastboot im getting waiting for device's and i do have fastboot installed via android studio
and i managed to get my phone into fastboot mode(blue notification light)
thanks
Did you install the relevant drivers for the ZR? Easiest way to do this would be by installing Flashtool (by Androxyde), which includes a GUI for flashing images via fastboot.
SirVer said:
Did you install the relevant drivers for the ZR? Easiest way to do this would be by installing Flashtool (by Androxyde), which includes a GUI for flashing images via fastboot.
Click to expand...
Click to collapse
i have downloaded the program
i looked online to how to get scatter-loading file
and when i followed the instruction
its says i dont have mtd file or emmc
also i tired to follow the guide here developer.sonymobile.com/unlockbootloader/imei-verification/79e3de6c1cdcb72796f5497654fe1c6769602ea35174b9a25be5cab6f6d90919f8448ef693675ac8fd8b9aa0a0520820d90f6e15c7efd5b0934255d1b7f3ec95
but when i type fastboot devices
i get nothing i return (although i can see the blue light )
That's because you don't have the drivers installed. And I didn't mean SP Flashtool - that's for MediaTek devices. We use Flashtool by Androxyde (Google it) for Xperia devices, and it's a lot less difficult to use (no scatter files, for example). There are several guides on XDA for Flashtool, look for one. In those guides, you'll see how to install the drivers. Also, Flashtool can unlock your bootloader without wiping the internal data or anything, so it's preferable to the normal way.
SirVer said:
That's because you don't have the drivers installed. And I didn't mean SP Flashtool - that's for MediaTek devices. We use Flashtool by Androxyde (Google it) for Xperia devices, and it's a lot less difficult to use (no scatter files, for example). There are several guides on XDA for Flashtool, look for one. In those guides, you'll see how to install the drivers. Also, Flashtool can unlock your bootloader without wiping the internal data or anything, so it's preferable to the normal way.
Click to expand...
Click to collapse
okay i followed the instructions and it said everything went successfully
but from some reason the light switched from blue to red and then no light and now i cant enter any mode(fastboot or recovery)
i used the the instructions here orum.xda-developers.com/showthread.php?t=2658952
edit: if i pull out the battery and then turn it back in and then press the power button it vibrates for a second
edit 2: the phone began to heat up,now it's very hot and it's connected to anything
That's odd... Please state exactly what you did, what you flashed (if you did flash something), and if possible, the Flashtool output for the operations.
SirVer said:
That's odd... Please state exactly what you did, what you flashed (if you did flash something), and if possible, the Flashtool output for the operations.
Click to expand...
Click to collapse
i just gave it to some phone lab and they fixed it
styxxer said:
i just gave it to some phone lab and they fixed it
Click to expand...
Click to collapse
Nice. ?
Did they tell you what the problem was? How much did it cost you?
SirVer said:
Nice.
Did they tell you what the problem was? How much did it cost you?
Click to expand...
Click to collapse
it coast 51.12$ and they said there was a problem with the fastboot:angel:
Woah, $50?! The only way I can think of that justifies $50 for that repair would be if the motherboard was f**ked up and they had to replace it. If that's what happened, then congratulations; most phones don't recover from motherboard damage. ?
SirVer said:
Woah, $50?! The only way I can think of that justifies $50 for that repair would be if the motherboard was f**ked up and they had to replace it. If that's what happened, then congratulations; most phones don't recover from motherboard damage.
Click to expand...
Click to collapse
i dont know what they did,but im glad it's working
also i see when the phone starts up the Entel logo(which is Chilean telecommunications company), can you tell why?
Sounds like your phone magically became carrier customized, which probably means the motherboard was replaced, or a new bootloader/ROM specific to that carrier was flashed.
Thanks for help
Sent from my Lenovo K50a40