Hey!
Z2 owners that like to mess around with their phones are prone to get f#ked. I was there and I faced the problem some of you probably did - a hard brick. There are a ton of tutorials on how to fix it, but I believe I found a new way that doesn't envolve resetting it. I have only tried with twice on my phone, so I'm really looking forward to know if it's universal!
Scenario - Your phone has a black screen. The notification LED is on. If you hold the power button it flashes the ZUK logo and it vibrates. If you identify with this scenario, go forward!
1 - To turn off your device (if you haven't already), press the power + volume up. The phone will vibrate, flash the ZUK logo, turn off the LED and turn it on again. Continue holding both buttons. When the LED turns off again, REMOVE your fingers from both buttons right away. If done correctly, it won't come back again and the LED will be off
2 - Hold both Volume Up and Volume Down at the same time. Connect to the computer. You should encounter your Fastboot mode (with your baseband and other info blank).
3 - Go to your email and redownload the bootloader unlocker. Yes, remember that file? Use it. You can use one of those unlock bootloader tutorials online, but if you know what you're doing, here's the command:
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
4 - Right after that, run this other command
fastboot -i 0x2b4c oem unlock-go
That's it. You should be able to go to the recovery (flash it again just to be sure). Try it out and tell me how it goes.
not working...phone is gettin turned off...but holding up and down..then connecting is doin nothing..it just keeps on going on and off again
This method worked for me,thank a lot of,great trick
Sent from my Redmi Note 3 using Tapatalk
you my friend, are a god among men, i owe you a beer.
fastboot mode conncted and flash unlockbootloader.img file..but not boot mobile shows error msg .my bootloader is unlocked any suggestion plz
vardhan21 said:
fastboot mode conncted and flash unlockbootloader.img file..but not boot mobile shows error msg .my bootloader is unlocked any suggestion plz
Click to expand...
Click to collapse
Same thing happened to me..followed this link https://zukfans.eu/community/threads/how-to-unbrick-zuk-z2-from-diagnostic-port-900e.2856/ as my phone showed 900E mode in Qfil ...followed and unbricked..mine bootloader also showed as unlocked
paps2k3 said:
Same thing happened to me..followed this link https://zukfans.eu/community/threads/how-to-unbrick-zuk-z2-from-diagnostic-port-900e.2856/ as my phone showed 900E mode in Qfil ...followed and unbricked..mine bootloader also showed as unlocked
Click to expand...
Click to collapse
hey thnks bro...i successfully enabled 9008 port and flashed firmware
thanku so much
Where were you man I have to cut my wire and format my phone for flashing new firmware
My phone don't show the led light
No button combination works
I was restoring twrp backup and the next boot...And i was bricked
It shows diagnostic mode 900E
Please help
Finally done
vardhan21 said:
fastboot mode conncted and flash unlockbootloader.img file..but not boot mobile shows error msg .my bootloader is unlocked any suggestion plz
Click to expand...
Click to collapse
Had the same problem and first i went to download mode by following the the below link
https://zukfans.eu/community/threads/how-to-unbrick-zuk-z2-from-diagnostic-port-900e.2856/
then i downloaded the stock firmware and followed this guide
https://zukfans.eu/community/threads/how-to-unbrick-zuk-z2-from-diagnostic-port-900e.2856/
Both of them helped.:good::fingers-crossed: hope they work for you
Please tell me the process for recover from hard brick, because zukfans.eu is no longer available.
paps2k3 said:
Same thing happened to me..followed this link https://zukfans.eu/community/threads/how-to-unbrick-zuk-z2-from-diagnostic-port-900e.2856/ as my phone showed 900E mode in Qfil ...followed and unbricked..mine bootloader also showed as unlocked
Click to expand...
Click to collapse
What is the process??? Please tell me here because zukfans.eu is not accessable
Rit2005 said:
What is the process??? Please tell me here because zukfans.eu is not accessable
Click to expand...
Click to collapse
Hi ..very sorry..not using z2 plus for a long time..I forgot the process what I did..I followed the steps mentioned there.
Related
Hi guys,
Today I tried to flash a stock rom but my phone won't boot in recovery,
After several trys, I runned the command Fastboot oem device-info and it says that my bootloader was locked,
Or I unlocked it as soon as I received my OPT and since one hour it won't stop rebooting in bootloader (after lunching the command fastbood oem unlock, it says "OKAY")
What do you guys think I can do ? Should I just pack it and send it to OnePlus ? Or there is a way to fix this problem ? All I can do is access to the Fastboot Mode but my Bootloader seems locked... :'(
Thanks for you help !
Nelio_FakeGeek said:
Hi guys,
Today I tried to flash a stock rom but my phone won't boot in recovery,
After several trys, I runned the command Fastboot oem device-info and it says that my bootloader was locked,
Or I unlocked it as soon as I received my OPT and since one hour it won't stop rebooting in bootloader (after lunching the command fastbood oem unlock, it says "OKAY")
What do you guys think I can do ? Should I just pack it and send it to OnePlus ? Or there is a way to fix this problem ? All I can do is access to the Fastboot Mode but my Bootloader seems locked... :'(
Thanks for you help !
Click to expand...
Click to collapse
Unbelievable,the same problem....anyone can help us?Plz
Nelio_FakeGeek said:
Hi guys,
Today I tried to flash a stock rom but my phone won't boot in recovery,
After several trys, I runned the command Fastboot oem device-info and it says that my bootloader was locked,
Or I unlocked it as soon as I received my OPT and since one hour it won't stop rebooting in bootloader (after lunching the command fastbood oem unlock, it says "OKAY")
What do you guys think I can do ? Should I just pack it and send it to OnePlus ? Or there is a way to fix this problem ? All I can do is access to the Fastboot Mode but my Bootloader seems locked... :'(
Thanks for you help !
Click to expand...
Click to collapse
Try this guide,worked for me.
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
fonz83.sa said:
Try this guide,worked for me.
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Click to expand...
Click to collapse
Many thanks to you it worked !
How did you guys get your phone into this (QUALCOMM-HS USB Diagnostics 9006) mode in the device Manager? I only see "QHSUSB_BULK"... Bootloader locked and I won't get into the recovery mode. I only get bootloop.
moeblhaus said:
How did you guys get your phone into this (QUALCOMM-HS USB Diagnostics 9006) mode in the device Manager? I only see "QHSUSB_BULK"... Bootloader locked and I won't get into the recovery mode. I only get bootloop.
Click to expand...
Click to collapse
Hold the power key for 20 seconds to force turn off power. connect OPT to usb, hold volume+ and power until your PC finds a new hardware (if it doesn't work, try hold volume+ and volume- together.
It is step #2 in that guide.
moeblhaus said:
How did you guys get your phone into this (QUALCOMM-HS USB Diagnostics 9006) mode in the device Manager? I only see "QHSUSB_BULK"... Bootloader locked and I won't get into the recovery mode. I only get bootloop.
Click to expand...
Click to collapse
If you folow the guide here: http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449 after you instal the drivers the device will show ap as QUALCOMM-HS USB Diagnostics 9006!
moeblhaus said:
How did you guys get your phone into this (QUALCOMM-HS USB Diagnostics 9006) mode in the device Manager? I only see "QHSUSB_BULK"... Bootloader locked and I won't get into the recovery mode. I only get bootloop.
Click to expand...
Click to collapse
You have to random push Vol+ or/and Vol- to get a black screen instead of Fastboot screen during the bootloop.
Thank you guys! It finally worked. Like you said, I had to kind of randomly and really long push the + , - & power button!
Hello!
As title says i bricked my Axon :crying:
I followed http://forum.xda-developers.com/showpost.php?p=68738854&postcount=100 (and the german one that linked to this one) but couldnt do the fastboot unlock.
So i couldnt finish this and my phone required a pin number to start android: bootet and started up but wanted a pin code to start/enter system.
Wasnt able to fix that with googling for answers so i went back to edl mode and rewrote my backup boot/recovery images with axon7backup.
Had no errors with that but it wont start now:
After the ZTE Logo the display goes black but it connects as "handset diagnostic interface (DFU) (ComX)" to my computer.
I fiddled around with driver installing etc and forced the HS-USB QDLoader 9008 on it but no luck, axon7backup/root can not connect.
When i did the actual flashing yesterday it never connected with the hold both vol-keys and connect usb way either, always had to reboot into edl via adb.
I cant boot anything else (no twrp/recovery) it just goes to the diagnostic interface mode.
Thanks in advance
you can try to get into adb mode with this:
- power off your device
- hold the vol down key while plugin in the usb-c cable (connected to your pc)
- keep holding
- you should get a white box with FTM factory test mode
- you are free to use adb again - so you can get into edl mode as well....
for pin part that'S normal while unlocking your device encryption gets deleted and you have to abort and factory reset your device in twrp....
Starvirus said:
you can try to get into adb mode with this:
- power off your device
- hold the vol down key while plugin in the usb-c cable (connected to your pc)
- keep holding
- you should get a white box with FTM factory test mode
- you are free to use adb again - so you can get into edl mode as well....
for pin part that'S normal while unlocking your device encryption gets deleted and you have to abort and factory reset your device in twrp....
Click to expand...
Click to collapse
Thanks. I tried it but it wont go to FTM. Only goes to diagnostic com port.
It seems i cant even turn it off. The little red light on the front is on the whole time .
sadly the disadvantage of a built in battery, so you have to wait till the battery is empty and try my instructions then....if it's not realy off it won't work, the mode you are currently in you usually only reach if you switch it on while holding both volume buttons, the edl mode is sadly not reachable with a key combination directly on G models.
adb don't show your device?
Starvirus said:
sadly the disadvantage of a built in battery, so you have to wait till the battery is empty and try my instructions then....if it's not realy off it won't work, the mode you are currently in you usually only reach if you switch it on while holding both volume buttons, the edl mode is sadly not reachable with a key combination directly on G models.
Click to expand...
Click to collapse
Oh ok. I expected ftm to work from vol-down and power-button till restart.
@adb: sadly no connection possible since it goes straight to Comport Connection.
Edit:
Couldnt make that work. It was off and i connected the usb. So it showed me the loading battery picture where i cant do anything. held the vol-down the whole time. But as soon as it had some battery it went straight to comport-connection again
im sorry to say, but ur device is bricked to a degree where you would need ZTEs Flashtool to fix it. Unfortunately we dont have that tool, so you might have to send it in
i have the same exact problem :'(
Have u been able to fix it?? I'm in a situation that i cant even send it to ZTE to fix it :'(
nsabir said:
i have the same exact problem :'(
Have u been able to fix it?? I'm in a situation that i cant even send it to ZTE to fix it :'(
Click to expand...
Click to collapse
Hi,
couldnt fix it myself so i had to send it in.
Unless some tool/rom was released in the last few months to fix it yourself i would guess your device is bricked.
Hi I have almost the same problem, I tried to unlock bootloader and now I don't have the recovery, I can boot and use my mobile but I can't restore it or update it because I don't have the recovery
I try whit axon7tool to restore the recovery but I got a error.
MaxRink said:
im sorry to say, but ur device is bricked to a degree where you would need ZTEs Flashtool to fix it. Unfortunately we dont have that tool, so you might have to send it in
Click to expand...
Click to collapse
Hi, do you have any idea, if there will be such a flashtool to work with DFU mode? I'm thinking that there are a lot of guys have bricked their devices (including me).
((
EDL (Emergency Download) Mode has been removed/ disable from MIUI 8.1 onwards and Redmi 4A later Xiaomi devices. So you can flash MIUI Fastboot ROMs on your device by using Fastboot mode only, if your bootloader is unlocked. And, we can't use Qualcomm Jig Cable(s) also now.
So, we have only one way to know Qualcomm HS-USB QDLoader 9008 port from PC. It's Test Point Method. This method will work with every MIUI ROMs (Upgrade/ Downgrade) , Locked Bootloader/ Unlocked Bootloader and also work to recover from a Dead boot device (Bricked).
While touching these two points with a metal tweezers plugin the usb cable to the phone and PC will make the phone enter edl mode. You can then release the tweezers.
Bro edl mode is not removed. It's just moved to fastboot. You can enter edl easily by "fastboot oem edl" command. Hope this helped :laugh:
rkmadotra said:
Bro edl mode is not removed. It's just moved to fastboot. You can enter edl easily by "fastboot oem edl" command. Hope this helped :laugh:
Click to expand...
Click to collapse
Thanks for the explanation, in any case tere can be situations that fastboot it's not available, hard but possible, in that case that info is helpful...
TioCareca said:
Thanks for the explanation, in any case tere can be situations that fastboot it's not available, hard but possible, in that case that info is helpful...
Click to expand...
Click to collapse
In any case, the bootloader muz be unlocked to initiate EDL using ADB fastboot..
rkmadotra said:
Bro edl mode is not removed. It's just moved to fastboot. You can enter edl easily by "fastboot oem edl" command.
Click to expand...
Click to collapse
:laugh::laugh::laugh:
what make you think they are so lame ? the result is :
failed ! remote device is locked. eom edl is not allowed
adrenochrome25 said:
:laugh::laugh::laugh:
what make you think they are so lame ? the result is :
failed ! remote device is locked. eom edl is not allowed
Click to expand...
Click to collapse
What makes you think I'm so lame as well. I have used this command and flashed my mi max 2 with fastboot rom. Tho I don't remember if bootloader was locked or unlocked. Probably it was unlocked. But still no issues as anyone can unlock thier bootloader officially.
i wasnt intended at you. it seems they forgot some ways when they first deployed the edl blocking access but with the most recent "roms" they have blocked every access way to edl when bootloader is locked : adb, fastboot & cable
the only way left is from internal pins, but we can expect they will hide them even better on new phones.
Today it's much worth to wait 72h (+30days if you just already unlocked another one today) than opening the models that have "non removable" batteries and risking to leave traces/damages
it's really a shame that xiaomi lock their phone this way, it's a very bad message at the users (fastboot is so much restricted that you cant even switch between stable&dev anymore with locked bootloader) but we still have the chance that they allow unlocking and that this unlocking is a real one allowing full control
Fastboot rom isn't needed untill we brick our device and we can't brick the device untill we have unlocked bootloader. So basically edl mode will work when it's really needed.
It doesn't work for my MM2. Got it since 4/12/17. Didn't know i need to login to mi acc to register my device, set usb debugging, developer's mode, unlock status...I had the phone for less than 2 hrs after updating to MIUI 9 from ver 8 (using the updater app) before it suddenly froze up, crashed and went into bootloop. I tried contacting xiaomi svc ctr but those clowns refused to help saying my device is china export.
I cldn't even get them to help me register my device on my mi acc using the imei & s/n info. So if anyone could offer some suggestions as to how I could ressurrect my phone, I wld be most grateful. Failing which the only avenue is to bring it to a svc ctr in China to get them fix it.
Rgds
My test points don't seem to work
I opened up my mi max2 and followed the steps to short the testpoints but my pc doesn't seem to pick up the Qualcomm device.
Anyway to trigger the thing so that the Qualcomm device can be detected?
Nike Lee said:
I opened up my mi max2 and followed the steps to short the testpoints but my pc doesn't seem to pick up the Qualcomm device.
Anyway to trigger the thing so that the Qualcomm device can be detected?
Click to expand...
Click to collapse
I managed to short the test points and got the Qualcomm HSB device on the device mgr, flashed the mi max2 with the latest global stable (V9.2.1) rom. But the phone is still stuck at the Android logo with 3 dots...
I wld have thought EDL flashing wld have wiped out everything on the phone and start afresh?
I am now thinking of formatting the entire phone and reflashing it again. How wld I do that?
Thanks for any inputs.
Hi, Does EDL with test point flashing refresh the boot partitions?
I have shorted the test points and successfully reflash the phone with the latest stable global ROMs (even back to MIUI 8.5.6) but just couldn't get the phone past the MI/Android logo after restarting it
If the boot partition files have been messed up and EDL flashing is not refreshing these files, no matter how many times I try to EDL flash the device, it's not going to help. Pls correct me if I am wrong.
Any other options I can try?
rkmadotra said:
Bro edl mode is not removed. It's just moved to fastboot. You can enter edl easily by "fastboot oem edl" command. Hope this helped :laugh:
Click to expand...
Click to collapse
bro thank u so muchhhhhhhhhhhhhhhhhhhhhhhh. it worked im so happy now...........was trying since hours....but u helped me mannn
Guys I just hard bricked my MIA1 I think trying to install superSu! can anyone please tell me what are my options? the phone is literally dead the adb command line is not finding the phone no boot logo no lights in device manager just detects this as Qcom device. Please,Ii need help
Anantha47 said:
Guys I just hard bricked my MIA1 I think trying to install superSu! can anyone please tell me what are my options? the phone is literally dead the adb command line is not finding the phone no boot logo no lights in device manager just detects this as Qcom device. Please,Ii need help
Click to expand...
Click to collapse
Can you enter fastboot mode?
No
varben said:
Can you enter fastboot mode?
Click to expand...
Click to collapse
No i cant get into fastboot mode
I tried connecting to miflash application and pressed volume down + power the boot logo showed for a second and vanished does that mean i have hope?
Anantha47 said:
No i cant get into fastboot mode
I tried connecting to miflash application and pressed volume down + power the boot logo showed for a second and vanished does that mean i have hope?
Click to expand...
Click to collapse
You are in Diagnostics mode, it's pretty useless, you need to enter in EDL Mode and try a flash with MiFlashTool
Use "fastboot oem edl"
I don't know if your phone can receive fastboot commands in Diagnostics, just try...
Can you please elaborate what have you done prior to the device brick? An informative answer requires an informative question.
Alanjameson99 said:
Can you please elaborate what have you done prior to the device brick? An informative answer requires an informative question.
Click to expand...
Click to collapse
I tried to install super su from boooting twrp !
Anantha47 said:
No i cant get into fastboot mode
I tried connecting to miflash application and pressed volume down + power the boot logo showed for a second and vanished does that mean i have hope?
Click to expand...
Click to collapse
What about keeping power and volume +/- pressed together for at least 10 seconds?
Too, connect the charger, maybe the battery is drained.
At least try these simple things before moving to complicated ones.
varben said:
What about keeping power and volume +/- pressed together for at least 10 seconds?
Too, connect the charger, maybe the battery is drained.
At least try these simple things before moving to complicated ones.
Click to expand...
Click to collapse
im 100% sure battery is above 70
Anantha47 said:
im 100% sure battery is above 70
Click to expand...
Click to collapse
Another thing to try is this, connect your phone with your computer and run
adb reboot edl
You will not see anything in your phone, just black screen.
Open miflash tool and hit refresh. See if it recognizes the phone.
varben said:
Another thing to try is this, connect your phone with your computer and run
adb reboot edl
You will not see anything in your phone, just black screen.
Open miflash tool and hit refresh. See if it recognizes the phone.
Click to expand...
Click to collapse
Already tried that mate it's showing either "sahara read end error with status 9" or "object reference not set to an instance of an object" the thing is I cant go into fast boot mode adb isn't recognising my device or even fastboot
Anantha47 said:
Guys I just hard bricked my MIA1 I think trying to install superSu! can anyone please tell me what are my options? the phone is literally dead the adb command line is not finding the phone no boot logo no lights in device manager just detects this as Qcom device. Please,Ii need help
Click to expand...
Click to collapse
Bro this guy was having same issue as 900E mode...so refer to this post and do step by step procedure shown in video.
im sure u will recover ur phone 100% to normal mode.:good:
good luck.
https://forum.xda-developers.com/showpost.php?p=75750138&postcount=5
and plz let me know...
Anantha47 said:
Already tried that mate it's showing either "sahara read end error with status 9" or "object reference not set to an instance of an object" the thing is I cant go into fast boot mode adb isn't recognising my device or even fastboot
Click to expand...
Click to collapse
At least mi flash is recognizing the phone.
You can try with a different firmware, try with android 7 firmware.
P.s. now that I see better your phone is recognized as Qualcomm HS-USB Diagnostics 900E, it should be 9008
You should try to find the correct Qualcomm drivers...
I'm sorry you have to go through this.
om_latex said:
Bro this guy was having same issue as 900E mode...so refer to this post and do step by step procedure shown in video.
im sure u will recover ur phone 100% to normal mode.:good:
good luck.
https://forum.xda-developers.com/showpost.php?p=75750138&postcount=5
and plz let me know...
Click to expand...
Click to collapse
Can you please tell me or give m link for Qualcomm drivers I messed up drivers in the process
Anantha47 said:
Can you please tell me or give m link for Qualcomm drivers I messed up drivers in the process
Click to expand...
Click to collapse
Check this:
http://www.99mediasector.com/install-qualcomm-hs-usb-qdloader-9008-install/
varben said:
Check this:
http://www.99mediasector.com/install-qualcomm-hs-usb-qdloader-9008-install/
Click to expand...
Click to collapse
I couldn't install those drivers it says windows need 64 bit drivers
om_latex said:
Bro this guy was having same issue as 900E mode...so refer to this post and do step by step procedure shown in video.
im sure u will recover ur phone 100% to normal mode.:good:
good luck.
https://forum.xda-developers.com/showpost.php?p=75750138&postcount=5
and plz let me know...
Click to expand...
Click to collapse
There is a major diff in vid and for me! he has working fastboot and i dont so i cant use EDL too but thanks for suggesting
Anantha47 said:
I couldn't install those drivers it says windows need 64 bit drivers
Click to expand...
Click to collapse
Ok, try these:
https://www.dropbox.com/s/a3i7aqkwjonkwmu/QDLoader HS-USB Driver.7z?dl=0
varben said:
Ok, try these:
https://www.dropbox.com/s/a3i7aqkwjonkwmu/QDLoader HS-USB Driver.7z?dl=0
Click to expand...
Click to collapse
Thank you for your continuous support mate but my device is not listed in either adb or fastboot commands , hence that the method suggested my on_Latex is not going to work :'(
Anantha47 said:
Guys I just hard bricked my MIA1 I think trying to install superSu! can anyone please tell me what are my options? the phone is literally dead the adb command line is not finding the phone no boot logo no lights in device manager just detects this as Qcom device. Please,Ii need help
Click to expand...
Click to collapse
connect your mobile to pc using usb cable and try pressing volume down and power button( or just press all three vol+ ,vol- and powerbutton ) untill it gets to fastboot mode
at last you will go to fastboot
i tried the same thing when i was in the same situation it worked for me
let me know is it working for you or not
SrikanthMergu said:
connect your mobile to pc using usb cable and try pressing volume down and power button( or just press all three vol+ ,vol- and powerbutton ) untill it gets to fastboot mode
at last you will go to fastboot
i tried the same thing when i was in the same situation it worked for me
let me know is it working for you or not
Click to expand...
Click to collapse
That's the thing i cant get into fast boot! the screen turns on white mi logo appears and then goes black after i press vol down + power
My Asus Zenfone Max Pro M1 is stuck on the screen," Powered by Android". I have neither rooted nor unlocked the bootloader. I had received the error of "Your device is corrupted" and had followed the guide to remove that. For a month, my phone lagged and had a drop in battery. Restarting it has caused it to not work.Now, it's showing no signs of starting. Any help will be sincerely appreciated!
manav113 said:
My Asus Zenfone Max Pro M1 is stuck on the screen," Powered by Android". I have neither rooted nor unlocked the bootloader. I had received the error of "Your device is corrupted" and had followed the guide to remove that. For a month, my phone lagged and had a drop in battery. Restarting it has caused it to not work.Now, it's showing no signs of starting. Any help will be sincerely appreciated!
Click to expand...
Click to collapse
download 059 fastboot rom[search in forum you will find 059 fastboot rom. it is in-(how to use flashtool thread)]
unzip it.
connect your phone with pc as in fastboot mode.
double click on flashallAFT.bat or .cmd file from fastboot rom folder.
059 fresh installtion will be donw by this although you will lose all your data so please backup if possible.
after that if u still have that 'your device is corrupt' error follow my thread . corrupt state fix command dosnt mess with your system whatsoever. so either u deleted some files accidently or it got deleted during update. dont blame any buddy regarding that.
P53mutant said:
download 059 fastboot rom[search in forum you will find 059 fastboot rom. it is in-(how to use flashtool thread)]
unzip it.
connect your phone with pc as in fastboot mode.
double click on flashallAFT.bat or .cmd file from fastboot rom folder.
059 fresh installtion will be donw by this although you will lose all your data so please backup if possible.
after that if u still have that 'your device is corrupt' error follow my thread . corrupt state fix command dosnt mess with your system whatsoever. so either u deleted some files accidently or it got deleted during update. dont blame any buddy regarding that.
Click to expand...
Click to collapse
Thanks for Replying bro. TMy phone is not going to any mode ie neither fastboot nor recovery. Its only showing Powered by Android whatever combinations I go with.I am thinking to try the QFIL s/w.
manav113 said:
Thanks for Replying bro. TMy phone is not going to any mode ie neither fastboot nor recovery. Its only showing Powered by Android whatever combinations I go with.I am thinking to try the QFIL s/w.
Click to expand...
Click to collapse
go for qfil then but use 059 qfil otherwise 130 qfill u will lose your persist,factory,fsg partition. doownload 059 fastboot rom . it is combined fastboot qfill rom. use it same as other qfill rom but choose here ww_no-nfc_no-fsg raw program.
btw your device showing powered by android that means u can go into fastboot mode and recovery mode both. just press and hold power button untill u see restart of ur screen. as soon as u see that press violume up along with power key. u will def get acess to fastboot mode.
P53mutant said:
go for qfil then but use 059 qfil otherwise 130 qfill u will lose your persist,factory,fsg partition. doownload 059 fastboot rom . it is combined fastboot qfill rom. use it same as other qfill rom but choose here ww_no-nfc_no-fsg raw program.
btw your device showing powered by android that means u can go into fastboot mode and recovery mode both. just press and hold power button untill u see restart of ur screen. as soon as u see that press violume up along with power key. u will def get acess to fastboot mode.
Click to expand...
Click to collapse
Didn't worked.. QFIL s/w was not able to detect the port even after connecting the mobile.. Tried to completely discharge and recharge hoping it would work.. Now, its not even recharging.. Nothing works now..Feels like a motherboard problem now..Should I rebuy the 4GB version or look for another mobile?
Try asus service center
manav113 said:
Didn't worked.. QFIL s/w was not able to detect the port even after connecting the mobile.. Tried to completely discharge and recharge hoping it would work.. Now, its not even recharging.. Nothing works now..Feels like a motherboard problem now..Should I rebuy the 4GB version or look for another mobile?
Click to expand...
Click to collapse
motherboard issue not lead to sudden death of phone. did u encounter random reboot before every 10-20 mins if not no worry.
for qfill u have to turn off your phone and press vol + and vol - together and have to connect your hpone with pc. check device manager of pc it will show port and comt device 2-3 mins after successfull qualcomm diag port driver installation.
98har**** said:
Try asus service center
Click to expand...
Click to collapse
No response. They said they aren't able to fix it. Can give 1k for the lcd screen.. :crying:
P53mutant said:
motherboard issue not lead to sudden death of phone. did u encounter random reboot before every 10-20 mins if not no worry.
for qfill u have to turn off your phone and press vol + and vol - together and have to connect your hpone with pc. check device manager of pc it will show port and comt device 2-3 mins after successfull qualcomm diag port driver installation.
Click to expand...
Click to collapse
Didn't had any random reboot stuff. I thought voltage fluctuations might have affected it. I had charged it at the Airport the same day the phone gave up. The QFIL software was not able to detect port even while pressing vol+ and vol- .Service Centre tells me its a PCB problem and are asking 3k for repair. Looks like a new phone is somewhere in the line for future.
manav113 said:
Didn't had any random reboot stuff. I thought voltage fluctuations might have affected it. I had charged it at the Airport the same day the phone gave up. The QFIL software was not able to detect port even while pressing vol+ and vol- .Service Centre tells me its a PCB problem and are asking 3k for repair. Looks like a new phone is somewhere in the line for future.
Click to expand...
Click to collapse
well good riddance