Related
I'm a complete noob in dire need of help. I wanted to root my phone, and read the 3 procedures mentioned in the sticky thread. The 2nd one (nvflash) seemed very well explained and was sure to work with 2.3.4 so I decided to use that. As I was in my friend's house I used his pc and installed the drivers while my phone was connected in apx mode. Then I double clicked the "install internal xp" batch file which resulted in a black window with some texts, but seeing this my friend freaked out and closed the window before the process was finished. I told him he shouldn't have done that. I then disconnected the phone and switched it on. It seemed to switch on properly. So I then switched it off again and pressed and held the power and vol down switches to see if I got cwm. This showed LG screen for a few seconds and then the screen went off.
Now whatever I try to do I can only see the LG screen for a few seconds and then the screens goes off. No power on, no recovery, no nothing. And I can only attempt to even power on once, after the screen goes off I must remove the battery before the power button does anything again.
I tried to freshly nvflashing the recovery many times, but it made no difference. Does this mean my phone is bricked? Please tell me how I can solve this as I'm really worried.
NVFlashing the recovery again *should* have worked. So we first need to make sure you're trying to start CWM the correct way.
1) Unplug phone
2) Remove battery for 10 seconds.
3) Insert battery
4) Hold volume-down, do not let go, keep pressing it.
5) Press power button, keep it pressed.
If/when you get the second LG-logo, bluish halo, you can release both buttons, not before.
Nope, that was exactly what I was doing to access the recovery. I tried it again just now and it didn't work.
It just displayed the regular LG logo and then the screen went off. I'm not sure the phone completely shuts down 'cause if I keep it like that it gets quite hot and I can't use the power button again to try to power up. Only removing and re-inserting the battery gives me another attempt.
Is there any chance this is a hardware issue?
Hardly any chance this is hardware related if it was working before the first NVFlash.
Good, next step will be to NVFlash a complete stock ROM. You will unfortunately lose any data you might have on it, but that's the price to pay.
Go here, follow the instructions precisely, skip installation of apx-driver. Report back.
http://www.modaco.com/topic/335474-25-mar-nvflash-stock-rom-release-v10b-dated-1300166062-15032011/
Ok, so I just download the 200mb file, connect in apx mode and double click flash.bat, right? And will this rom work regardless of country/region? I'm from India and was running stock 2.3.4 with v20* (can't remember the letter. God, I hate myself).
sean8000 said:
Ok, so I just download the 200mb file, connect in apx mode and double click flash.bat, right? And will this rom work regardless of country/region? I'm from India and was running stock 2.3.4 with v20* (can't remember the letter. God, I hate myself).
Click to expand...
Click to collapse
It works, yes, but is the original Froyo. This is just a way to get the phone up and running again.
Later you have a few choices. Either install CWM, then install you ROM of choice, or upgrade it to the latest for your region by using the LG Update tool.
EDIT. Oh, and btw, it is better to open a command-window and type the flash.bat command. If there are any errors you will still have them on-screen.
Thank you for all the help and support. I didn't get a chance to flash the rom till now (being on a vacation without a smartphone sucks). But I'll try it asap and report back.
So, how did it go?
TrymHansen said:
So, how did it go?
Click to expand...
Click to collapse
I haven't flashed it yet. I've decided to do it after I return home. I'm at my friend's house for 2 more days.
Ok, bad news. I flashed the stock rom you linked. The process went pretty smoothly. After the window got closed and the lg logo on the phone was visible 2 times, I unplugged it and installed the battery. But switching it on wasn't fruitful. It just displayed the LG logo for a couple of seconds and then the screen went off (just like before, only faster). I tried repeating the whole process, even tried to nvflash cwm once again, but nothing happened.
So is it a hardware issue? My phone is no longer in warranty period, so a hardware problem would be really bad...
So is it a hardware issue?
Click to expand...
Click to collapse
I don't know.
What would be helpful is to get a copy of the output you get when you NVFlash, it's simply the only way to verify that the flash process went ok. If you have an aborted flash it of course won't work, and may display the behaviour you describe.
EDIT: Btw, early on there were some ROMs which refused to boot properly unless the baseband was of an early variety as well.
If you feel confident the NVFlash has been successfull, smartflash an old baseband as well, see if it boots then.
Its hardly a hardware problem. As you dont have the warranty anymore, and the bootloader is probably corrupted, i would recommend a Jtag service.
Please, dont be afraid of hitting thanks
gabriel2anjos said:
Its hardly a hardware problem. As you dont have the warranty anymore, and the bootloader is probably corrupted, i would recommend a Jtag service.
Please, dont be afraid of hitting thanks
Click to expand...
Click to collapse
Now what's this "Jtag service"? (edit- I googled it and it seems to be a method of un-bricking stuff with specialized hardware or something, but I'm not sure I can have that done where I live)
Is there any way to fix the bootloader by myself?
@Trym- So, I should download a v10 baseband and flash it with this "smartflash" tool, right?
sean8000 said:
@Trym- So, I should download a v10 baseband and flash it with this "smartflash" tool, right?
Click to expand...
Click to collapse
Yeah, as a last-ditch effort. I haven't the slightest hope it'll help, but it can't hurt to try.
TrymHansen said:
Yeah, as a last-ditch effort. I haven't the slightest hope it'll help, but it can't hurt to try.
Click to expand...
Click to collapse
Ok, I'll try that when I have the time.
So do you know anything about this corrupted bootloader thing? Does this mean my phone's hard bricked?
sean8000 said:
So do you know anything about this corrupted bootloader thing? Does this mean my phone's hard bricked?
Click to expand...
Click to collapse
If it is you're only the second person in this forum to ever brick his phone. Anything's possible I guess. Some flash cells may have been damaged the first time the power was yanked. But then we should presumably get some verification errors during flashing.
Anyway, I'm at my wits end, and I really do hope you get it up and running, but I don't have anything more to contribute. Good luck.
Corrupted bootloader means that your cellphone simply don't know what to do when you hit the power button, due to the damage. As the cell phone can't turn, the pc can't recognize it. If your cell phone were a samsung, you could try to use a jig to have acesso to the download mode. But I don't know if it would work for a LG. You could try anyway.
And if you live at big city, usually it's common to have some jtag services.
Please, dont be afraid of hitting thanks
Please, dont be afraid of hitting thanks
Ok, so I took the phone to the service center today. The guys there said its battery terminals are messed up. They said replacement terminals are not easily available, but they'll try to find some. And of course I'll have to pay for it. I guess it's still better than using the phone as a paperweight.
What do you guys think?
Good luck I managed to mess up my phone like you too. I'm from India. But the difference was that I was covered by warranty. I managed to get a bunch of hardware replaced and was up and running again.
hi.
so i think i need help. i updated the phone few days ago to the latest firmware. and the phoen was fine for the next 2 days. i never had to restart or anything. today one of my games wasnt working so i figured my phone might need a restart.
anyway i did. and now my phone is stuck in some service mode i assume ? its a triangle with screw driver inside and a blue moving bar under it.
i dont know what to do. my phone isnt rooted or anything. i didnt even attempt to root after the update. nothing. just restarting the phone :/
am i f**ked ? :/
How did you update, OTA or pushed via FlashTool?
Dinkoz said:
How did you update, OTA or pushed via FlashTool?
Click to expand...
Click to collapse
flashtool
The only thing you can do in situations like this, as told in every such thread, is reflash with the flashtool.
Will FlashTool pick it up when connecting via Vol -Up? If so, try pushing the FTF again,even a different FTF?
i will try when i get home to see if it will pickup the flashtool.
it kinda sucks tho. why it did this ? i didnt even install anything in the stupid thing aside from few games. jesus.
What FTF did you use ? I would suggest using another just in case, you may / may not need to wipe data
the one from the main thread :/. " not the one with the typo "
i think its from singapore one ? because it had some stuff from that country.
i will go home in 1 hour or so and try to flash without wipe.
finger crossed :/
its not accepting the flashtool.
i turn the device off. i click on the back botton. but nothing.
the log says the file is connected in fast boot mode. but there is nothing . i still get the pop screen that shows the instructions how to plug your device.
any help
ll_l_x_l_ll said:
its not accepting the flashtool.
i turn the device off. i click on the back botton. but nothing.
the log says the file is connected in fast boot mode. but there is nothing . i still get the pop screen that shows the instructions how to plug your device.
any help
Click to expand...
Click to collapse
Volume down and plug the usb.
Sent from my C6603 using xda premium
ok. by miracle i got it to work. but i am not sure what happened and why it did this.
all good i guess :/
also, i wonder if there is an official version of this. not bloated with weird stuff. like euro version or something.
also. one more question.
is there a root for this ?
Reinstall the software with sony update service is what you have to do
http://www.sonymobile.com/gb/tools/update-service/
glad to read that is fixed ..
I had this same issue yesterday. I installed the the update from the India c6602. Things were working fine the first day. I did a reset and then had the same issue as the OP had.
A re-flash with the flashtool didn't work the first time and the I tried the Sony companion fix option, and still had problems. Then I realized I had to install the drivers. Are you on windows 8? did you install the drivers that came with the flashtool? I did and then re-flashed, and now its fine again.
ll_l_x_l_ll said:
ok. by miracle i got it to work. but i am not sure what happened and why it did this.
all good i guess :/
also, i wonder if there is an official version of this. not bloated with weird stuff. like euro version or something.
also. one more question.
is there a root for this ?
Click to expand...
Click to collapse
Most people seem to have flashed the Global FTF, you could reflash the old firmware, then when you plug into PC Companion it should flick up the update for you/your region.
I would just flash Global
Hi
what i did.
I unlocked the Bootloader via Flashtool
Rooted the device
Installed TW Recovery.
Installed iHackers 4.
All was fine until i saw the i wasnt connected to my Network Provider .
AHH i forgot to flash "Xperia Z1 - C6903 - Kernel + Baseband [14.3.A.0.757].ftf"
So i went into flashtool and flashed it, excluding everything execpt Kernel and Baseband.
The flashtool finshed and the device shut down. And thats it. Since then nothing. Not even
the led or something is showing any lifesignal. I tryed every button combi. The red reset button.
Tryed to enter flashmode.. NOTHING!!! What the ?! ANy ideas what i can do?
Last time i checked the accu was @ 93 %. I have it now on the charger dock hoping it is just a battery issue. No combination (pwr+vol+ or pwr+vol- etc.) working so far.
thanx
Thomas
TommyX235 said:
Hi
what i did.
I unlocked the Bootloader via Flashtool
Click to expand...
Click to collapse
What is this?
Did you Backup TA? Did you followed this instructions HERE?
If you did not, then you was asking for troubles.
eclyptos said:
What is this?
Did you Backup TA? Did you followed this instructions HERE?
If you did not, then you was asking for troubles.
Click to expand...
Click to collapse
I started the Flashtool .. clicked on BLU and followed the instructions.
ANd the flashtool successfully unlocked the booloader
But thats not my problem. The Phone is dead.. I does not give
any lifesignes .. also the backup is useless if i cant get flashboot
or any way to use adb .. to work.
TommyX235 said:
I started the Flashtool .. clicked on BLU and followed the instructions.
ANd the flashtool successfully unlocked the booloader
But thats not my problem. The Phone is dead.. I does not give
any lifesignes .. also the backup is useless if i cant get flashboot
or any way to use adb .. to work.
Click to expand...
Click to collapse
Yes it is a problem.
Even in this Tutorial is all well explained that you have to use the OFFICIAL Sony way to unlock Bootloader,
http://forum.xda-developers.com/showthread.php?t=2440597
..you did not followed the instructions and you unlocked with Flashtool which probably did not do his job right.
Maybe I am wrong but this is how supposed to be to avoid issues.
Then you phone is bricked and you have to follow other instruction to check if still can be resurrected, there is many Threads on XDA about this.
TommyX235 said:
I started the Flashtool .. clicked on BLU and followed the instructions.
ANd the flashtool successfully unlocked the booloader
But thats not my problem. The Phone is dead.. I does not give
any lifesignes .. also the backup is useless if i cant get flashboot
or any way to use adb .. to work.
Click to expand...
Click to collapse
Well if you want to sell it then I might want it as my screen got cracked
Sent from my C6903 using XDA Premium 4 mobile app
TommyX235 said:
Hi
...
thanx
Thomas
Click to expand...
Click to collapse
Leave it on charge for 24 hours and then try turning it on.
Please let us know tomorrow if anything changes
eclyptos said:
Yes it is a problem.
Even in this Tutorial is all well explained that you have to use the OFFICIAL Sony way to unlock Bootloader,
http://forum.xda-developers.com/showthread.php?t=2440597
"..you did not followed the instructions and you unlocked with Flashtool which probably did not do his job right."
Maybe I am wrong but this is how supposed to be to avoid issues.
Then you phone is bricked and you have to follow other instruction to check if still can be resurrected, there is many Threads on XDA about this.
Click to expand...
Click to collapse
Wow i haven't thought that I get some nagging here instead of constructive suggestions. In any case i will let the phone on the charger for 24 hours and see if it helps. Also I DON'T THINK THIS IS A BOOTLOADER ISSUE!!! All worked fine.. I booted into ihackers 4 multiple times without any problems.. Also the Phone would show ANY signes of life, eg. LED RED or blinking etc..But nothing
ALSO:
"..you did not followed the instructions and you unlocked with Flashtool which probably did not do his job right."
In the "getting started" thread of z1 it is suggested to use the flashtool! And like i said .. it finished successfully..
Thank you for your answer and the nagging...
gregbradley said:
Leave it on charge for 24 hours and then try turning it on.
Please let us know tomorrow if anything changes
Click to expand...
Click to collapse
i'll give it a try! Thanx!
TommyX235 said:
Wow i haven't thought that I get some nagging here instead of constructive suggestions. In any case i will let the phone on the charger for 24 hours and see if it helps. Also I DON'T THINK THIS IS A BOOTLOADER ISSUE!!! All worked fine.. I booted into ihackers 4 multiple times without any problems.. Also the Phone would show ANY signes of life, eg. LED RED or blinking etc..But nothing
ALSO:
"..you did not followed the instructions and you unlocked with Flashtool which probably did not do his job right."
In the "getting started" thread of z1 it is suggested to use the flashtool! And like i said .. it finished successfully..
Thank you for your answer and the nagging...
Click to expand...
Click to collapse
Let us hear how it goes with it...
Sent from my C6903 using XDA Premium 4 mobile app
TommyX235 said:
"..you did not followed the instructions and you unlocked with Flashtool which probably did not do his job right."
In the "getting started" thread of z1 it is suggested to use the flashtool! And like i said .. it finished successfully..
Thank you for your answer and the nagging...
Click to expand...
Click to collapse
Ok, If you are so sure then Ok, but still weird, as I follow different instruction and never had a problem then people do on they way and later have problems. It can be a coincidence and maybe is not your case, but sometime thinking easy can compromise the whole process.
I flashed different patches on mine Kernel I kill my phone few times and mine was completely dead, no led nothing, but it boot into Flashmode or Fastboot, you have somehow go in that mode and flash again, this is the only soft solution.
If you will not be able to do so then you have to go with the Test Pins, open your back cover and try to resurrect it, the hard way.
eclyptos said:
Ok, If you are so sure then Ok, but still weird, as I follow different instruction and never had a problem then people do on they way and later have problems. It can be a coincidence and maybe is not your case, but sometime thinking easy can compromise the whole process.
I flashed different patches on mine Kernel I kill my phone few times and mine was completely dead, no led nothing, but it boot into Flashmode or Fastboot, you have somehow go in that mode and flash again, this is the only soft solution.
If you will not be able to do so then you have to go with the Test Pins, open your back cover and try to resurrect it, the hard way.
Click to expand...
Click to collapse
I don't understand what went wrong. After flashing the Kernel and Baseband the flashtool said everything went fine eand restarted the device. It turned off and nothing since then. I cant even get into flashboot or flashmode. It feels likt the accu is broken because there is nothing happening whatever i do. I think there is no power. I will not open the device because i still have 2 years of waranty (i hope they repair it as waranty case, if i am lucky) Else I will pay for the repair. We'll see. If this is an accu failure it should be a waranty case.
I had it for about 8 hours on the charger without any signs of "life" in the "machine". Sometimes i feel like trowing it against a wall to see if it reanimates it... But i can keep myself from doing it. =)
We'll see..
probably stupid guess: maybe ur phone just stucked on something and may not be completely switched off??
press vol+ and power button, see if ut vibrates 3 times
if it does, congrats an flash kernel again
TommyX235 said:
Hi
what i did.
I unlocked the Bootloader via Flashtool
Rooted the device
Installed TW Recovery.
Installed iHackers 4.
All was fine until i saw the i wasnt connected to my Network Provider .
AHH i forgot to flash "Xperia Z1 - C6903 - Kernel + Baseband [14.3.A.0.757].ftf"
So i went into flashtool and flashed it, excluding everything execpt Kernel and Baseband.
The flashtool finshed and the device shut down. And thats it. Since then nothing. Not even
the led or something is showing any lifesignal. I tryed every button combi. The red reset button.
Tryed to enter flashmode.. NOTHING!!! What the ?! ANy ideas what i can do?
Last time i checked the accu was @ 93 %. I have it now on the charger dock hoping it is just a battery issue. No combination (pwr+vol+ or pwr+vol- etc.) working so far.
thanx
Thomas
Click to expand...
Click to collapse
Is it getting red led when you try to charge it?
If not then its Sony's problem probably a faulty device. Send warranty and don't mention bootloader, root or ROM.
yup owns Z1 and stuff.
z1 completely dead
my z1 completely dead, I instaled hi hackers rom and went well after finishing flashing i did'nt get network of airtel and instaled baseband of 3rd party and it is completely dead nothing is working when i press volume+on button it vibrates 3 times thats it and nothing is displayed and when i put to the charge it shows red light and stops,can anbody help me out from this, please only 3 months old my z1 and sorry for my english ....and can anbody reply what to do next friends?
Hard reset.
Flash a stock FTF using flashtool.
If that does not work, leave it on charge overnight and try again tomorrow
gregbradley said:
Hard reset.
Flash a stock FTF using flashtool.
If that does not work, leave it on charge overnight and try again tomorrow
Click to expand...
Click to collapse
ok Dude i tried for flashing by pressing volume down button its not working .
while i try plug data cabel it will show blue led for a 2 seconds confirm its charging r i dont know? OK
I will try keeping overnight charge and i will try tomorrow. Thanks
---------- Post added at 09:20 PM ---------- Previous post was at 09:08 PM ----------
eclyptos said:
Ok, If you are so sure then Ok, but still weird, as I follow different instruction and never had a problem then people do on they way and later have problems. It can be a coincidence and maybe is not your case, but sometime thinking easy can compromise the whole process.
I flashed different patches on mine Kernel I kill my phone few times and mine was completely dead, no led nothing, but it boot into Flashmode or Fastboot, you have somehow go in that mode and flash again, this is the only soft solution.
If you will not be able to do so then you have to go with the Test Pins, open your back cover and try to resurrect it, the hard way.
Click to expand...
Click to collapse
how to use Test pins procedure by opening back cover give me the details?
srichinu said:
how to use Test pins procedure by opening back cover give me the details?
Click to expand...
Click to collapse
There is no test point on 2013+ devices
Try again in the morning and let me know how you get on, I will help you then
gregbradley said:
There is no test point on 2013+ devices
Try again in the morning and let me know how you get on, I will help you then
Click to expand...
Click to collapse
Ok sir i kept for charge for more than 6 hours but i think nothing charged i tried by all methods by volume+ and on button,flash mode by connecting data cabel by pressing volume down as a flash but still it is in same condition. please advice me what to do next.
thanks?
Go through the process of flashing a FTF and please post the output of flashtool here.
Sony PC Companion
Have you try Sony PC Companion program?
Just received the stock update to Sense 6. I am in Canada, on Telus, fully stock.
When the phone boots into the recovery to flash the update, I am getting a red triangle and the error is unexpected contents in settings.apk
Any suggestions on how to get this update working other than hard resetting before the update?
Thanks.
Can you reboot normally? Just select the Reboot system option? Also, if it insists on going to update, hold power button to forcefully restart and keep pressing the volume down button to get into bootloader mode.
Try restart from there.
As you are FULLY stock (no root, should say LOCKED on that bootloader screen) you can either consider going through the warranty OR trying it yourself to fix by unlocking bootloader OR take it to someone locally.
Unfortunately all options will lead to data loss.
SaHiLzZ said:
Can you reboot normally? Just select the Reboot system option? Also, if it insists on going to update, hold power button to forcefully restart and keep pressing the volume down button to get into bootloader mode.
Try restart from there.
As you are FULLY stock (no root, should say LOCKED on that bootloader screen) you can either consider going through the warranty OR trying it yourself to fix by unlocking bootloader OR take it to someone locally.
Unfortunately all options will lead to data loss.
Click to expand...
Click to collapse
Yes it reboots and yes I have a locked bootloader. I would hard reset before sending it out for servicing.
Any other people having this issue?
mfpreach said:
Yes it reboots and yes I have a locked bootloader. I would hard reset before sending it out for servicing.
Any other people having this issue?
Click to expand...
Click to collapse
Not heard of a problem while updating. You are special.
What are your guys thoughts on flashing a stock ruu and then trying to ota to sense 6?
mfpreach said:
What are your guys thoughts on flashing a stock ruu and then trying to ota to sense 6?
Click to expand...
Click to collapse
Great idea!
mfpreach said:
What are your guys thoughts on flashing a stock ruu and then trying to ota to sense 6?
Click to expand...
Click to collapse
Did your problem solved?
Haha I haven't been able to try, on my 8.1 box I get an error 170 when trying to connect the phone in ruu. On my win7 box the ruu just auto closes....
mfpreach said:
Haha I haven't been able to try, on my 8.1 box I get an error 170 when trying to connect the phone in ruu. On my win7 box the ruu just auto closes....
Click to expand...
Click to collapse
well error 170 is either because your drivers aren't installed correctly or because you have a bad usb cable/port
alray said:
well error 170 is either because your drivers aren't installed correctly or because you have a bad usb cable/port
Click to expand...
Click to collapse
Thanks,I will look into it tomorrow.
Are there even good drivers for 8.1 yet bearing in mind I don't have a USB 3 port?
mfpreach said:
Thanks,I will look into it tomorrow.
Are there even good drivers for 8.1 yet bearing in mind I don't have a USB 3 port?
Click to expand...
Click to collapse
hi, we have similar issues although mine is the soundhound_freemium.apk instead of settings.apk, I hope that you will get your issue settled and also update me and the rest of us who are having the issues here. good luck and thanks! (do check out my thread which I've just posted like 5 minutes back!)
Do not install sense 6 upgrade
I would recommend NOT installing the stock Sense 6 upgrade. I installed it a couple days ago and currently my phone is bricked because of it.
I posted about my issue in another thread. In case people want to read what's been going on i'll repost it here.
Kg810 said:
So I performed the Sense 6 upgrade a couple days ago, update went through fine, yesterday morning my phone started acting all weird (sluggish, random reboots, bunch of apps reporting errors, etc) and battery was draining fast.
I probably rebooted my phone 10 times, 5 times normally by just the power button and the remaining times through the light trick, power button and volume button. Once my phone finally got back to normal, I was typing on whatsapp and then suddenly it froze.
It froze for a couple minutes and then it turned off. I believe the battery was at 39%. I plugged the phone into my work computer and it would make the USB connection sound, then after a few seconds it would display drivers failed to install followed by 3 subtle sounds similar to the connection sound. So right away I checked Device Manager and it displayed QHSUSB_DLOAD.
Currently my phone has been charging all night, currently it is being charged at work and there has been no sign of life.
I've tried putting it in the freezer, the light trick, the laptop connecting/disconnecting trick, and the go ole punching the phone trick. None of them have worked.
The phone is definitely not charging at this point as it is stone cold when I hold it or touch the wall charger.
Any ideas what I can do? I don't want to contact Rogers and have to send it in. I've got so many songs, videos and pictures I have yet to backup.
Any help and/or suggestions welcome.
Click to expand...
Click to collapse
Kg810 said:
I would recommend NOT installing the stock Sense 6 upgrade. I installed it a couple days ago and currently my phone is bricked because of it.
Click to expand...
Click to collapse
Well your issue have nothing to do with the sense 6 update. You even said that you have updated the phone a couple of days before your phone died. QHSUSB_DLOAD mode mean your phone motherboard is dead, either because of an hardware failure or because you have flashed something really wrong (probably not your case). So how an hardware failure could be caused by a sofware update and only occur days later....? unfortunately, you must send your phone for repair.
---------- Post added at 05:23 PM ---------- Previous post was at 05:22 PM ----------
mfpreach said:
Thanks,I will look into it tomorrow.
Are there even good drivers for 8.1 yet bearing in mind I don't have a USB 3 port?
Click to expand...
Click to collapse
if you have a win7 computer, then use that one.
alray said:
Well your issue have nothing to do with the sense 6 update. You even said that you have updated the phone a couple of days before your phone died. QHSUSB_DLOAD mode mean your phone motherboard is dead, either because of an hardware failure or because you have flashed something really wrong (probably not your case). So how an hardware failure could be caused by a sofware update and only occur days later....? unfortunately, you must send your phone for repair.
Click to expand...
Click to collapse
Maybe I wasn't clear.
Tuesday night before I went to bed I performed the upgrade.
Wednesday morning, is when the issues started occuring.
Today is May 29th, Tuesday was May 27th, which is 2 days ago, hence why I said I performed the upgrade a couple days ago.
From the time I performed the install Tuesday night to Wednesday morning when I got into work, there was nothing done to the phone. The only thing that was done was the Sense 6 upgrade.
So you're trying to tell me that the upgrade has nothing to do with it?
Kg810 said:
So you're trying to tell me that the upgrade has nothing to do with it?
Click to expand...
Click to collapse
If your phone was 100% stock, I highly doubt the ota could hard brick it.
like I said QHSUSB_DLOAD = defect motherboard
in most cases because:
1- hardware failure
or
2- Flashing something that screwed your phone (i.e flashing something not meant for your phone with S-OFF)
I'm not saying its impossible, but I think it's more a coincidence
alray said:
If your phone was 100% stock, I highly doubt the ota could hard brick it.
like I said QHSUSB_DLOAD = defect motherboard
in most cases because:
1- hardware failure
or
2- Flashing something that screwed your phone (i.e flashing something not meant for your phone with S-OFF)
I'm not saying its impossible, but I think it's more a coincidence
Click to expand...
Click to collapse
I've had the phone for a little over a year and it has been 100% stock. Never tinkered with it in any way shape or form.
I just can't see how it is a mere coincidence that right after the update, my phone starts acting up, and then becomes bricked.
Kg810 said:
I've had the phone for a little over a year and it has been 100% stock. Never tinkered with it in any way shape or form.
I just can't see how it is a mere coincidence that right after the update, my phone starts acting up, and then becomes bricked.
Click to expand...
Click to collapse
Anyway, your only way out of this qhsusb brick is to send your phone for repair.
Sorry
mfpreach said:
Yes it reboots and yes I have a locked bootloader. I would hard reset before sending it out for servicing.
Any other people having this issue?
Click to expand...
Click to collapse
facing same problem with you. my problem haven't fix. from malaysia
akasi91 said:
facing same problem with you. my problem haven't fix. from malaysia
Click to expand...
Click to collapse
From Malaysia as well, hey mind telling me how big is your sense 6 update download size?
kuzumitaiga said:
From Malaysia as well, hey mind telling me how big is your sense 6 update download size?
Click to expand...
Click to collapse
6xxmb.
Hi,
So i thought i knew what i was doing and tried to root my 6gb Alpha but apparently i didn't know what i was doing and now i'm stuck in a bootloop with the phone complaining it is in redstate and insecure. I have tried the stock recovery and both cleared cache and factory reset and still nothing. The phone isn't rooted(obviously) anyone one with more knowledge on this have any ideas? I'm about to tear my hair out.
Would advise you flash the old stock ROM. You can find instruction on how to do that in one of many threads in Maze Alpha section of this forum.
Thanks, I tried that with flashtool,now when the phone powers on the backlight comes on and that's it oh I can adjust the volume and it clicks as if the phone is locking when I hit the power button but that's it no images on screen.
Azurewraith said:
Thanks, I tried that with flashtool,now when the phone powers on the backlight comes on and that's it oh I can adjust the volume and it clicks as if the phone is locking when I hit the power button but that's it no images on screen.
Click to expand...
Click to collapse
Sure you flashed the 6GB rom and not the 4GB one?
Maybe try it again and check if there are no errors visible during the flash.
Just found this on the Gearbest blog, which is worth trying first if you flashed the correct rom : https://www.gearbest.com/blog/how-to/solutions-to-maze-alpha-4g-phablet-problems-2018
If the problem still exists, try resetting your phone in the following steps (Note: back up all your important data on the phone, or the data will be wiped after the factory reset):
a. Power off your phone. Then press the Volume up key and Power key at the same time until it navigates to Recovery Mode.
b. Use Volume up/down key to select "Wipe data/Factory reset".
c. Use Power key to confirm.
d. Use Volume key to select "Yes - Delete Alluser".
e. Once the resetting is finished, your phone will reboot automatically. It will take a few minutes to recover. Please wait patiently.
Unfortunately I can't factory reset without a screen. I'll double check the Rom pretty sure it was the correct one, I think it may be a return and play dumb job.
Azurewraith said:
Unfortunately I can't factory reset without a screen. I'll double check the Rom pretty sure it was the correct one, I think it may be a return and play dumb job.
Click to expand...
Click to collapse
So screen doesn't come on at all? Ouch. then I would double check the rom and try to flash again.
I was planning to root my 6GB this weekend but these stories are no good.
Azurewraith said:
Thanks, I tried that with flashtool,now when the phone powers on the backlight comes on and that's it oh I can adjust the volume and it clicks as if the phone is locking when I hit the power button but that's it no images on screen.
Click to expand...
Click to collapse
Please, can you post information on where you downloaded your ROM from and got the instruction? The ROM posted in this thread link below seems to be for Maze Alpha 6GB.
https://forum.xda-developers.com/ma...rom-mazealphabv0420171018-maze-alpha-t3717082
pja1985430 said:
Please, can you post information on where you downloaded your ROM from and got the instruction? The ROM posted in this thread link below seems to be for Maze Alpha 6GB.
https://forum.xda-developers.com/ma...rom-mazealphabv0420171018-maze-alpha-t3717082
Click to expand...
Click to collapse
From the maze gdrive I couldn't get their app to work even following all of the instructions for some strange reason. When trying to root my phone I hit the bootloop then flashing the stock rom from the gdrive with flashtool got me the black screen issue.
Azurewraith said:
From the maze gdrive I couldn't get their app to work even following all of the instructions for some strange reason. When trying to root my phone I hit the bootloop then flashing the stock rom from the gdrive with flashtool got me the black screen issue.
Click to expand...
Click to collapse
So have you been able to flash it again?
lukesan said:
So have you been able to flash it again?
Click to expand...
Click to collapse
No change im afraid I think it's died a death. Its like the phone is fully functional except it just won't display anything.
Azurewraith said:
No change im afraid I think it's died a death. Its like the phone is fully functional except it just won't display anything.
Click to expand...
Click to collapse
Try to use the instruction on the link I posted earlier. It is not dead.
pja1985430 said:
Try to use the instruction on the link I posted earlier. It is not dead.
Click to expand...
Click to collapse
That's what I tried to do initially but their flash tool would never work out never once scanned but my comps where allways different numbers to the ones shown in the screen shots.
Azurewraith said:
That's what I tried to do initially but their flash tool would never work out never once scanned but my comps where allways different numbers to the ones shown in the screen shots.
Click to expand...
Click to collapse
Maybe try to take screenshots of what it is showing on the screen as what you write is very unclear.
Does it detect the phone.
What numbers ....
etc etc
lukesan said:
Maybe try to take screenshots of what it is showing on the screen as what you write is very unclear.
Does it detect the phone.
What numbers ....
etc etc
Click to expand...
Click to collapse
I'll see what I can do tomorrow when I get off work.