Hi everyone,
If your phone does not react on any of yours actions. You may have the same problem. This is an instruction how to fix it.
If you have a last version of Windows 10 you can easily check if it is your case (You will have "Qualcomm HS-USB QDLoader 9008" device at your Windows devices' list.
How to Fix:
1. Download Drivers Qualcomm_QDLoader_HS-USB_Driver_64bit_Setup.zip and install it.
2. Download firmware link1 or link2
3. Install the driver
4. Unpack a firmware archive
5. Power off your phone by pressing Voice Down + Power Buttons (If your phone would be in this state too long the script would not works).
6. Start update_image_EDL.bat script - it will recreate all of the partitions
7. After the script will finish you will see the bootloader
8. Start script flashall_AFT.cmd - it will install firmware to the new partitions
9. Download fresh official firmware from asus site and put the archive at your memory card.
10. Start bootloader
11. Go to a standard recovery mode and install this firmware form the card
12. restart and repeat 10-11 (it will install software at the second state)
13. The problem is fixed. Congratulations!
Common problems:
Exception: System.DLLNotFoundException: DLL "QMSL_MSVC10R.dll": Module was not found. (HRESULT: 0x8007007E) can not be loaded.
Solution: You need to install Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package MFC. Thanks to Genim
can you please update the post with the links to the software? thanks
admirdante said:
can you please update the post with the links to the software? thanks
Click to expand...
Click to collapse
I tried, but this was my first message, so I could not manage to do it (I need at least 10 messages). However, I report it to a moderator teams. I hope they will do it for me.
Hi OP,
I have edited the links into first post for you. Enjoy.
Jerry
Forum Moderator
Thank you so much OP. You saved my phone. It's been in Edl mode for about 2 months. Now it's up and running again.
Guys if I can add one thing to the OP post .. Make sure you plug the phone in and let it charge for awhile before attempting. Once you get to the fastboot mode it will not allow you to continue if your battery is too low. I understand that you can't tell what percentage the battery is but just let it charge for 2 hours and then do the whole process. I had to stop when I got to the fastboot stuff. And then continue after 2 hours on the charge.
st3wart said:
Thank you so much OP..
Click to expand...
Click to collapse
You are welcome. It took some time, so I decided to publish it.
st3wart said:
I understand that you can't tell what percentage the battery is but just let it charge for 2 hours and then do the whole process.
Click to expand...
Click to collapse
In fact I can. I intentionally bricked my phone 3 times to write the simplest possible tutorial (my first solution was too long, because I could not understand why the problem was fixed).
I could not implement this solution when I had 6 per cent of battery, but it worked ok when I had 11 per cent. I can guess, that if it more than 10% - it is ok to implement this tutorial.
st3wart said:
Thank you so much OP. You saved my phone.
Click to expand...
Click to collapse
I'm glad it worked for you! I made it into FastBoot Mode, but when I select Recovery, it puts me back into FastBootMode.
Am I missing something or did something not work properly? Don't know how to flash the official firmware now.
In fastboot mode... Go to the extracted files and double click on the flashall_aft file and sit back and wait until it finishes.
st3wart said:
In fastboot mode... Go to the extracted files and double click on the flashall_aft file and sit back and wait until it finishes.
Click to expand...
Click to collapse
I did click it. It opened and closed cmd too fast for me to read though.
That's what it did when my battery was low... Go plug your phone in with the original charger for an hour and then go directly to your PC and plug it in and double click that file and it should do it's job.
Also check to make sure your antivirus isn't blocking the file. Mine blocked access to it for whatever reason.
I did click it. It opened and closed cmd too fast for me to read though.
Click to expand...
Click to collapse
It looks like st3wart's answer is correct. I faced the same behavior when my phone had 6 per cent of battery. This problem was fixed as soon as my phone had 11 per cent of the battery. Thus you should try to charge it before starting the script.
Furthermore, if you would still face this problem you can copy files fastboot_.log and test1.txt and share all of logs with us (or just find the error by yourself).
error from fastboot_.log:
"Writing 'partition:0'...
FAILED (remote: Warning: battery's capacity is very low)"
I did charge it for 2+ hrs with the original charger though. When I unplug it, turn it off and back on again it gives a low battery error. When I plug it back in, it goes straight back into FastBootMode.
But it seems to not charge the battery for some reason.
I did charge it for 2+ hrs with the original charger though.
Click to expand...
Click to collapse
Did you charge it in EDL mode?
For some reasons it did not work for me either. I just booted to bootloader, then power-off the phone and saw the animation of charging. You can also try to flash TWRP (using their instructions) and charge your phone in this mode.
If it does not work - please check your charger.
goldman1993 said:
Did you charge it in EDL mode?
Click to expand...
Click to collapse
As soon as I charge the phone, the FastBoot screen comes up. When I select power off, it comes right back into FastBootMode. Is there a way to force shut down so i can charge it?
Also tried installing twrp, but when I select RecoveryMode it puts me back into FastBootMode again.
When I select power off, it comes right back into FastBootMode. Is there a way to force shut down so i can charge it?
Click to expand...
Click to collapse
It is a bit abnormal behavior. I'm not sure, why it happens, to be honest. Have you tried to use different cable or charger (I'm not sure what is the reason, so I would try to change something)?
Genim said:
As soon as I charge the phone, the FastBoot screen comes up. When I select power off, it comes right back into FastBootMode. Is there a way to force shut down so i can charge it?
Also tried installing twrp, but when I select RecoveryMode it puts me back into FastBootMode again.
Click to expand...
Click to collapse
Press power button for long time to power off.
Then try flashing every image of that link:
https://forum.xda-developers.com/ze...ne-6-proton-kernel-v1-0-t3963948/post80405617
goldman1993 said:
Have you tried to use different cable or charger?
Click to expand...
Click to collapse
I have.
I unplugged the phone and let the battery run comepletely empty until the phone shut off.
Then I plugged it back in and it charged for a minute (could see the charging symbol).
It then turned itself back on into FastBoot and stopped charging again.
---------- Post added at 07:29 PM ---------- Previous post was at 07:29 PM ----------
EMJI79 said:
try flashing every image of that link
Click to expand...
Click to collapse
I did flash them, but for some images it gave me the following error:
FAILED (remote: 'Error flashing partition : volume full')
Genim said:
I did flash them, but for some images it gave me the following error:
FAILED (remote: 'Error flashing partition : volume full')
Click to expand...
Click to collapse
Not good...
Then I plugged it back in and it charged for a minute (could see the charging symbol).
It then turned itself back on into FastBoot and stopped charging again.
Click to expand...
Click to collapse
Well, we can try to brick it one more time (put it into EDL mode). Then you can try to power it up in this state and unbrick it one more time.
Firstly you need to load to bootloader and write
.\fastboot.exe --set-active=b
Then you need to reboot your phone.
I believe, that you would not successfully load to bootloader (IT would be the same EDL mode), so you can try to charge it in this state or try tutorial one more time. (After a 30 minutes of your charging process you can try tutorial one more time).
goldman1993 said:
.\fastboot.exe --set-active=b
Click to expand...
Click to collapse
I ran that command and it bricked the phone again.
But I did wait too long before running the script. I'm getting an Sahara error.
How should I proceed? Can I just run that line again?
Related
I flashed a RUU for wildfire s, everything seems to be fine.
But after it finished and told me your phone will now restart............---------> only the screen turns on and off, on and off.
Nothing else. I cannot go into bootloader or start the phone, no htc logo... nothing =(
I pulled the battery and tried to restart the phone, restarting into bootloader, connecting to fastboot, flashing ruu again, but nothing worked.
No connection to pc at all and no signal on the phone. Only: background light turns on and off, turns on and off.
What can i do ?
Please help me.
I am happy for any replies.
I will pay 20 Euros, if someones solution works.
You might want to take a look at this.
http://forum.xda-developers.com/showthread.php?t=1622178
Hope that helps.
cortezthekiller said:
You might want to take a look at this.
http://forum.xda-developers.com/showthread.php?t=1622178
Hope that helps.
Click to expand...
Click to collapse
Thanks a lot, but i have already known this thread.
The guy, B3NJY, with same problem, could not solve it. At least he sent his phone to repair service.
Maybe someone else knows how to unbrick a softbricked wildfire s.?
I flashed a lot and know how to use fastboot etc., ....
Like i said, backlight is working but nothing else.
appyleptiker said:
I flashed a RUU for wildfire s, everything seems to be fine.
But after it finished and told me your phone will now restart............---------> only the screen turns on and off, on and off.
Nothing else. I cannot go into bootloader or start the phone, no htc logo... nothing =(
I pulled the battery and tried to restart the phone, restarting into bootloader, connecting to fastboot, flashing ruu again, but nothing worked.
No connection to pc at all and no signal on the phone. Only: background light turns on and off, turns on and off.
What can i do ?
Please help me.
I am happy for any replies.
Click to expand...
Click to collapse
I think you flash wrong RUU. Before flash RUU 100% confirm about it. Otherwise you will lost your device. Anyway let's begin...
[WARNING: PLEASE DON'T TRY THIS WITHOUT HAVING GOOD ENOUGH KNOWLEDGE !! BE SURE TO CHOOSE THE RIGHT RUU OR THIS MAY HARM/BRICK YOUR DEVICE !! I AM NOT RESPONSIBLE FOR ANYTHING !!]
Before you start, you will need to set up your computer to properly recognize the device. You probably did this when rooting originally, but just in case... Install SDK tools for Android, Java runtime, and HTC Sync (only for USB drivers). Make sure that HTC Sync is not running in the background when this process is ongoing. To kill that you can use "Task Manager in Windows"
:cyclops: Do step by step: :cyclops:
1. Download the correct RUU for your device from Here and please 100% confirm you are downloading right RUU for your device. Make sure you download a Marvel_C RUU for a CDMA device (no sim card) or a Marvel RUU for a GSM device (uses a sim card)!! Also make sure you get the correct RUU for your carrier.
2. Charge the battery above 80%. If the battery dies during the flashing process, you could hard brick the phone!
3. Run the RUU until the wizard comes up (step 1). While the RUU wizard is open, don't do anything. Just find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be two folders with long encrypted names. In one of them you will find ROM.zip. Copy that and keep it on another location. Close the RUU wizard.
Now, open ROM.zip with 7zip and extract "System, Boot and recovery img's" [.img file/s]. Put it in the location were you've installed Android SDK tools.
4. Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
5. Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools.
Flash the stock recovery, boot, system img's using the following command/s:
step by step
For recovery
Code:
fastboot flash recovery recovery.img
For boot
Code:
fastboot flash boot boot.img
For system
Code:
fastboot flash system system.img
Now go back to device recovery and DO FACTORY RESET and reboot your device.
If everything done perfectly then the phone will booted normally on STOCK ROM! Remember Now bootloader is UNLOCKED but NOT rooted. Don't worry, you can root your device and also install CWM as before.
Hope this method will solve your issue.
Thank you very much testmasterbd =) , for this excellent description.
But..... i can`t start my phone into the bootloader. The phone turns on (only seeing the backlight) and suddenly it turns off (again the backlight). It does this ever and ever again until i pull out the battery . =(
how can i get into the bootloader? volume down and power doesn`t work anymore.
Maybe i can connect the phone to the pc, not via usb but via other contacts. Or is there another way to get the phone into fastboot mode?
Try this
Remove and reinsert the battery [don't press the power button of your device, that's means device should be turned off]
Plug it into a computer via USB cable
Wait and see if the computer detects it
If it does, then - Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools.
Code:
adb devices
See if it shows up or not.
I am not sure about your device get hard brick.
---------- Post added at 10:30 PM ---------- Previous post was at 10:12 PM ----------
I forgot to ask one thing :silly:
Did your device vibrate when you pressed the power button for normal boot?
testmasterbd said:
Try this
Remove and reinsert the battery [don't press the power button of your device, that's means device should be turned off]
Plug it into a computer via USB cable
Wait and see if the computer detects it
If it does, then - Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools.
Code:
adb devices
See if it shows up or not.
I am not sure about your device get hard brick.
---------- Post added at 10:30 PM ---------- Previous post was at 10:12 PM ----------
I forgot to ask one thing :silly:
Did your device vibrate when you pressed the power button for normal boot?
Click to expand...
Click to collapse
You are very friendly.
But i cannot power off the phone. It turns only off if i remove battery =)
When i plug in the usb cable while the phone is off, after some seconds, it turns on - shows its backgound light - and turns off and again on, like a turn signal. no vibration at all.
When i type in windows command adb devices it shows:
C:\android>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
but no device is listed =(
so it should be hard bricked!?
Damn it.
thanks a lot for your help and wasted time.
i am sorry
have a nice day
appyleptiker said:
You are very friendly.
But i cannot power off the phone. It turns only off if i remove battery =)
When i plug in the usb cable while the phone is off, after some seconds, it turns on - shows its backgound light - and turns off and again on, like a turn signal. no vibration at all.
When i type in windows command adb devices it shows:
C:\android>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
but no device is listed =(
so it should be hard bricked!?
Damn it.
thanks a lot for your help and wasted time.
i am sorry
have a nice day
Click to expand...
Click to collapse
If it is then, you need an expert who is capable for JTAG repairs. So find someone in your place. You can get an idea from HERE.
Good luck
testmasterbd said:
If it is then, you need an expert who is capable for JTAG repairs. So find someone in your place. You can get an idea from HERE.
Good luck
Click to expand...
Click to collapse
Yeah, thanks a lot.:good: Luck is what i need. But i don`t think that it will be too easy to repair. :silly:
appyleptiker said:
Yeah, thanks a lot.:good: Luck is what i need. But i don`t think that it will be too easy to repair. :silly:
Click to expand...
Click to collapse
It is don't be frustrated
Hi everyone, today my Elephone p8000 with stock rom (no root nor recovery installed) proposed me an OTA update, and I did it.
After installing the update the phone is stuck at the boot animation logo. If I boot in factory mode (volume down + power button) I am presented with a bunch of options in Chinese, which I don't understand. If I go in recovery mode (volume down + power button) it says "no command".
What can I do? What are my options? Is it bricked?
Yup mine too. Mine has root, with no custom recovery. Get the same boot loop and the sad open Android 'no command'.
Haven't had a chance to dig around for a solution but I suspect it is a case of using the flash tool to wipe and load a standard ROM? Hopefully an easier way.
kevvyboy said:
Yup mine too. Mine has root, with no custom recovery. Get the same boot loop and the sad open Android 'no command'.
Haven't had a chance to dig around for a solution but I suspect it is a case of using the flash tool to wipe and load a standard ROM? Hopefully an easier way.
Click to expand...
Click to collapse
Damn. I had huge problems with the flash tool in the past (I don't have a Windows PC) and the idea of spending the weekend trying to get the damn thing work is not a fun one.
Got this issue too this morning on way to work, I guess my phones useless today until I get home to try and flash it.
seem to be able to get to the boot select screen but nothing is different anyway, also managed to get into a "PCBA" mode that did a load of tests to the phone but thats it.
it now just died, not powering on, think its bricked :crying:
skea said:
it now just died, not powering on, think its bricked :crying:
Click to expand...
Click to collapse
Probably just out of power. Try charging it for a while and/or download and flash entire rom using sp flash except for data-partition so as you don't lose your data.
pitrus- said:
Probably just out of power. Try charging it for a while and/or download and flash entire rom using sp flash except for data-partition so as you don't lose your data.
Click to expand...
Click to collapse
thanks it was out of power lol
I just had the same problem. Did you solved it?
Like, exactly the same... Crazy
Another one
My p8000 also in bootloop after ota update. Only have an old vista PC w8ll dust it off tonight and see what happens
mines doing the same i thought it was too good to be true and it was lol
Cannot get pc (win 10) to install all the drivers, PC cannot see the phone so unable to run flash tool.
Suggestions? I presume the ROM cannot be flashed through the recovery (standard)?
EDIT: Driver package installed by disabling 'driver verification' setting in Windows. Phone only recognised as a MTP USB Device in devide manager, and flash tool does not seem to want to do anything. Might try this on a Win 7 laptop tomorrow. HJow you guys getting on with this?
Success - I Have a Working Phone
(or, How Chest Pains and Rage Focused the Mind)
So. This is what worked for me. Win 10. P8000 bootloop.
1) put p8000 into recovery, chose 'power off'. (I couldn't seem to stop it rebooting using the power button)
2) installed driver pack by disabling the Windows install signed drivers only setting. Rebooted. This turns the setting back on, but the drivers have alrwady been installed, no issue with that.
3) installed the flash tool. Brief panic at Chinese chars, located English. Calmed down.
4) loaded flash tool, with ROM ready to go.
5) this is the biggie, this is what brought it all together.........connected the powered down p8000 via USB and IMMEDIATELY hit the download button in the flash tool - ie BEFORE a new instance of USB bing-bong-device-connected sound.
6) once all downloaded, disconnect phone, reboot. Took an extended time (few mins) to boot, enough time to almost start swearing under my breath, but it just needed some patience.
Now, what I spent some time unsuccessfully trying to fix - needlessly as it turns out - was what my phone appeared under 'Device Manager'. It still lists it as an MTP USB Device under the 'Portable Devices' submenu. It did not seem to matter, as long as all the driver were installed.
I wish you all the best of luck in solving your issues, hopefully some of what I wrote can be helpful.
pitrus- said:
download and flash entire rom using sp flash except for data-partition so as you don't lose your data.
Click to expand...
Click to collapse
I have the same boot loop after ota. I did no backup before, so data partition contains my apps right ?
I never used the flash tool , where should I start , any good link for beginners ?
I read some things about the flash options months ago, must I disable/uncheck some options ?
Thanks for help.
same issue
Hi everyone!
I've got the same issue: I allowed the OTA update to 20151105 firmware release from previous version (20150725), after the upgrade, the phone keeps in a bootloop with a new colored Elephone logo.
I can't find a valid set of drivers, I tried a lot over the night, but windows don't recognize the phone.
PLEASE some kind soul could link a valid driver package to use SP tool ?
thanks a lot in advance!
mr..speed said:
I have the same boot loop after ota. I did no backup before, so data partition contains my apps right ?
I never used the flash tool , where should I start , any good link for beginners ?
I read some things about the flash options months ago, must I disable/uncheck some options ?
Thanks for help.
Click to expand...
Click to collapse
kevvyboy said:
Success - I Have a Working Phone
(or, How Chest Pains and Rage Focused the Mind)
So. This is what worked for me. Win 10. P8000 bootloop.
1) put p8000 into recovery, chose 'power off'. (I couldn't seem to stop it rebooting using the power button)
2) installed driver pack by disabling the Windows install signed drivers only setting. Rebooted. This turns the setting back on, but the drivers have alrwady been installed, no issue with that.
3) installed the flash tool. Brief panic at Chinese chars, located English. Calmed down.
4) loaded flash tool, with ROM ready to go.
5) this is the biggie, this is what brought it all together.........connected the powered down p8000 via USB and IMMEDIATELY hit the download button in the flash tool - ie BEFORE a new instance of USB bing-bong-device-connected sound.
6) once all downloaded, disconnect phone, reboot. Took an extended time (few mins) to boot, enough time to almost start swearing under my breath, but it just needed some patience.
Now, what I spent some time unsuccessfully trying to fix - needlessly as it turns out - was what my phone appeared under 'Device Manager'. It still lists it as an MTP USB Device under the 'Portable Devices' submenu. It did not seem to matter, as long as all the driver were installed.
I wish you all the best of luck in solving your issues, hopefully some of what I wrote can be helpful.
Click to expand...
Click to collapse
kevvyboy said:
Success - I Have a Working Phone
(or, How Chest Pains and Rage Focused the Mind)
So. This is what worked for me. Win 10. P8000 bootloop.
1) put p8000 into recovery, chose 'power off'. (I couldn't seem to stop it rebooting using the power button)
2) installed driver pack by disabling the Windows install signed drivers only setting. Rebooted. This turns the setting back on, but the drivers have alrwady been installed, no issue with that.
3) installed the flash tool. Brief panic at Chinese chars, located English. Calmed down.
4) loaded flash tool, with ROM ready to go.
5) this is the biggie, this is what brought it all together.........connected the powered down p8000 via USB and IMMEDIATELY hit the download button in the flash tool - ie BEFORE a new instance of USB bing-bong-device-connected sound.
6) once all downloaded, disconnect phone, reboot. Took an extended time (few mins) to boot, enough time to almost start swearing under my breath, but it just needed some patience.
Now, what I spent some time unsuccessfully trying to fix - needlessly as it turns out - was what my phone appeared under 'Device Manager'. It still lists it as an MTP USB Device under the 'Portable Devices' submenu. It did not seem to matter, as long as all the driver were installed.
I wish you all the best of luck in solving your issues, hopefully some of what I wrote can be helpful.
Click to expand...
Click to collapse
pretty much did the same thing and it worked!! Cheers!! (also had the rage and it took ages to find english on the tool lol :laugh: )
when you get the android with the "no command" message, let go of the volume and power buttons. Then hold the POWER BUTTON for 1-2 seconds and TAP VOLUME UP while still holding the power button. this will open the recovery options
omg!!
disabling the Windows install signed drivers only setting!!
i thought we wouldnt have to do things like this since Windows 95
Lol
Worked for me
Had I only found this tutorial before yesterday... it took me hours to figure this out.
I can, however, now confirm this works.
Regarding point 5):
(i) Power down phone (ii) start flash tool/go to download tab (iii) select scatter file (iv) hit "download" with no phone attached (v) attach the powered down phone
...and things will be fine. Doing anything fast is not required.
The point is to install SP_Drivers_v2.0 first, as described here. After this, everything goes smooth.
kevvyboy said:
Success - I Have a Working Phone
(or, How Chest Pains and Rage Focused the Mind)
So. This is what worked for me. Win 10. P8000 bootloop.
1) put p8000 into recovery, chose 'power off'. (I couldn't seem to stop it rebooting using the power button)
2) installed driver pack by disabling the Windows install signed drivers only setting. Rebooted. This turns the setting back on, but the drivers have alrwady been installed, no issue with that.
3) installed the flash tool. Brief panic at Chinese chars, located English. Calmed down.
4) loaded flash tool, with ROM ready to go.
5) this is the biggie, this is what brought it all together.........connected the powered down p8000 via USB and IMMEDIATELY hit the download button in the flash tool - ie BEFORE a new instance of USB bing-bong-device-connected sound.
6) once all downloaded, disconnect phone, reboot. Took an extended time (few mins) to boot, enough time to almost start swearing under my breath, but it just needed some patience.
Now, what I spent some time unsuccessfully trying to fix - needlessly as it turns out - was what my phone appeared under 'Device Manager'. It still lists it as an MTP USB Device under the 'Portable Devices' submenu. It did not seem to matter, as long as all the driver were installed.
I wish you all the best of luck in solving your issues, hopefully some of what I wrote can be helpful.
Click to expand...
Click to collapse
What if no Windows?
Edit: Never mind, I got myself a windows computer and succeeded. Thanks for all the orientation!
Hi all,
Thanks a lot for posting a solution to this problem so quickly. I am affected by the same issue. Looking to buy some LSD to better enjoy the psychtrip my phone seems to be stuck in. Also looking to fix the phone.
Unfortunately, I'm running Ubuntu 14.04 LTS. I did find a guide to use the flash tool on Ubuntu, but my phone does not seem to connect. I'm guessing this has something to do with that pack of drivers 2.0, for which I have no equivalent. I would really appreciate any ideas!
I might end up returning my phone to Amazon, though. It's only been a few days since I've had it, and you can imagine that although I was really liking it, I'm beginning to change my mind.
Your advice?
EDIT: I am getting the following error message:
BROM ERROR: S_COM_PORT_OPEN_FAIL (1013)
[COM]: Failed to open COM port.
[HINT]:
I did some googling, but didn't find anything worth mentioning.
yslsl said:
Had I only found this tutorial before yesterday... it took me hours to figure this out.
I can, however, now confirm this works.
Regarding point 5):
(i) Power down phone (ii) start flash tool/go to download tab (iii) select scatter file (iv) hit "download" with no phone attached (v) attach the powered down phone
...and things will be fine. Doing anything fast is not required.
The point is to install SP_Drivers_v2.0 first, as described here. After this, everything goes smooth.
Click to expand...
Click to collapse
Ahh good stuff. Connect phone last after hitting download - thanks for the heads up. Got my wife's p8000 today so will be doing some flashing later.
Cheers!
My phone battery stays at 100% for ages and when it get to 20 / 30 % it turns off with no warning .
Can anybody help with calibrating the battery.
karlzberg said:
My phone battery stays at 100% for ages and when it get to 20 / 30 % it turns off with no warning .
Can anybody help with calibrating the battery.
Click to expand...
Click to collapse
If u have TWRP
First fully charge phone +keep it plugged in for say 30min
Then land into twrp and disconnect charger
Then >file manager>data>system>here delete this file batterystat.bin
Then come out to starting window and here choose reboot into bootloader option keep phone in bootloader mode for say 1-2min than reboot to system
Check if issue solve or not and share the result
Starchm said:
If u have TWRP
First fully charge phone +keep it plugged in for say 30min
Then land into twrp and disconnect charger
Then >file manager>data>system>here delete this file batterystat.bin
Then come out to starting window and here choose reboot into bootloader option keep phone in bootloader mode for say 1-2min than reboot to system
Check if issue solve or not and share the result
Click to expand...
Click to collapse
Thank you I'll try later and let you know :good:
Done that @Starchm I'll see how it goes tomorrow ?
Starchm said:
If u have TWRP
First fully charge phone +keep it plugged in for say 30min
Then land into twrp and disconnect charger
Then >file manager>data>system>here delete this file batterystat.bin
Then come out to starting window and here choose reboot into bootloader option keep phone in bootloader mode for say 1-2min than reboot to system
Check if issue solve or not and share the result
Click to expand...
Click to collapse
Thanks again @Starchm
Battery back to normal
Ran down battery last night till it got to the 15% warning :good:
Done it again at 26% after updating some apps must be a connection to app updating ?
Starchm said:
If u have TWRP
First fully charge phone +keep it plugged in for say 30min
Then land into twrp and disconnect charger
Then >file manager>data>system>here delete this file batterystat.bin
Then come out to starting window and here choose reboot into bootloader option keep phone in bootloader mode for say 1-2min than reboot to system
Check if issue solve or not and share the result
Click to expand...
Click to collapse
where 's the option for reboot into bootloader at twrp? tq
Hi there,
I am looking for some guidance on my bricked Pixel 6 Pro.
I transfered the data from my old pixel, but then decided to do a full flash to refresh. Downloaded the stock image from google, used the fastboot-all script to flash the phone, but as soon as it was done, I never reboot. my phone is looking completely dead since.
Attempt # 1
- black screen, with no sound to any actions of response to any key combination (power or volume keys).
- tried holding the power button for 60 secs, no response
- tried holding power and volume down, no response
- tried holding power and volume up, no response
- when I plug the phone on charge, no response. neither the charging display.
Atempt # 2
- Only time the phone shows some sign of life, is when I connect the phone to my PC, it makes a sound of detecting a device, but then instantly it get a disconnect sound, (in 2-3 sec).
- I tried holding the power button, while plugged in. it makes a sound of usb detection, (but no visual response on the phone) after holder for 30 secs, it makes another sound of usb detach.
- While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone.
Not sure, if I have bricked the bootloader, and if yes, what can be done? Any guidance in this regards will be highly appreciated.
Thanks
Call whoever you bought the phone from and do warranty claim.
I struggled with a soft bricked / bootlooping phone after removing Magisk. Although my phone at least booted to bootloader and a connection via fastboot was working, the factory images wouldn't flash properly. Google support couldn't help me and I thought I had to send it to repair.
In the end I could solve the issue by switching to the Android SDK 31. I know your case is different, because your phone is bricked worse than mine was, but you could give it a try.
Baumhouse said:
I struggled with a soft bricked / bootlooping phone after removing Magisk. Although my phone at least booted to bootloader and a connection via fastboot was working, the factory images wouldn't flash properly. Google support couldn't help me and I thought I had to send it to repair.
In the end I could solve the issue by switching to the Android SDK 31. I know your case is different, because your phone is bricked worse than mine was, but you could give it a try.
Click to expand...
Click to collapse
rao_hamza said:
Hi there,
I am looking for some guidance on my bricked Pixel 6 Pro.
I transfered the data from my old pixel, but then decided to do a full flash to refresh. Downloaded the stock image from google, used the fastboot-all script to flash the phone, but as soon as it was done, I never reboot. my phone is looking completely dead since.
Attempt # 1
- black screen, with no sound to any actions of response to any key combination (power or volume keys).
- tried holding the power button for 60 secs, no response
- tried holding power and volume down, no response
- tried holding power and volume up, no response
- when I plug the phone on charge, no response. neither the charging display.
Atempt # 2
- Only time the phone shows some sign of life, is when I connect the phone to my PC, it makes a sound of detecting a device, but then instantly it get a disconnect sound, (in 2-3 sec).
- I tried holding the power button, while plugged in. it makes a sound of usb detection, (but no visual response on the phone) after holder for 30 secs, it makes another sound of usb detach.
- While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone.
Not sure, if I have bricked the bootloader, and if yes, what can be done? Any guidance in this regards will be highly appreciated.
Thanks
Click to expand...
Click to collapse
rao_hamza said:
Hi there,
I am looking for some guidance on my bricked Pixel 6 Pro.
I transfered the data from my old pixel, but then decided to do a full flash to refresh. Downloaded the stock image from google, used the fastboot-all script to flash the phone, but as soon as it was done, I never reboot. my phone is looking completely dead since.
Attempt # 1
- black screen, with no sound to any actions of response to any key combination (power or volume keys).
- tried holding the power button for 60 secs, no response
- tried holding power and volume down, no response
- tried holding power and volume up, no response
- when I plug the phone on charge, no response. neither the charging display.
Atempt # 2
- Only time the phone shows some sign of life, is when I connect the phone to my PC, it makes a sound of detecting a device, but then instantly it get a disconnect sound, (in 2-3 sec).
- I tried holding the power button, while plugged in. it makes a sound of usb detection, (but no visual response on the phone) after holder for 30 secs, it makes another sound of usb detach.
- While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone.
Not sure, if I have bricked the bootloader, and if yes, what can be done? Any guidance in this regards will be highly appreciated.
Thanks
Click to expand...
Click to collapse
Bootloader unlocked?
cultofluna said:
Bootloader unlocked?
Click to expand...
Click to collapse
If I remeber correctly flashing factory images forces you to unlock the device. So yes, the bootloader of rao_hamza's device should be unlocked.
From memory you can revive it through QPST and orher Qualcomm utilities, however hard part is to get the files. the phone is too new and many shops dont have the unlock tools yet.
" While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone. " - this is still good news, as phone is being detected by windows, try to install Qualcomm drivers and see if you can get it to boot into EDL. GOOD LUCK.
Pixel 6 uses Google's own new Tensor chip - so no Qualcomm tools
Like @Baumhouse I went through something similar. Two things for me: it took way longer to hold power and volume down than any other phone I've owned. I was seriously concerned I wasn't going to get there. Two, the factory images all made it to fastbootd and then failed all because I hadn't updated to the latest SDK.
Just throwing this out in hopes you don't have to send it back.
What @ridobe said. Make sure you're using the latest official Google Platform Tools (there's a link in my thread at the top of my signature below if you need it, or just Google for it). If I had a nickel every time someone didn't update the tools when they went to use them...
roirraW edor ehT said:
What @ridobe said. Make sure you're using the latest official Google Platform Tools (there's a link in my thread at the top of my signature below if you need it, or just Google for it). If I had a nickel every time someone didn't update the tools when they went to use them...
Click to expand...
Click to collapse
This and a bad/wrong cable seem to be the most common culprits
ridobe said:
Like @Baumhouse I went through something similar. Two things for me: it took way longer to hold power and volume down than any other phone I've owned. I was seriously concerned I wasn't going to get there. Two, the factory images all made it to fastbootd and then failed all because I hadn't updated to the latest SDK.
Just throwing this out in hopes you don't have to send it back.
Click to expand...
Click to collapse
Any idea how long you had to hold that button combinaiton? I tried longer, maybe 60 sec, but still no response from the phone.
tids2k said:
From memory you can revive it through QPST and orher Qualcomm utilities, however hard part is to get the files. the phone is too new and many shops dont have the unlock tools yet.
" While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone. " - this is still good news, as phone is being detected by windows, try to install Qualcomm drivers and see if you can get it to boot into EDL. GOOD LUCK.
Click to expand...
Click to collapse
What is EDL? and had the Google usb drivers installed, to get the fastboot working.
Baumhouse said:
I struggled with a soft bricked / bootlooping phone after removing Magisk. Although my phone at least booted to bootloader and a connection via fastboot was working, the factory images wouldn't flash properly. Google support couldn't help me and I thought I had to send it to repair.
In the end I could solve the issue by switching to the Android SDK 31. I know your case is different, because your phone is bricked worse than mine was, but you could give it a try.
Click to expand...
Click to collapse
Yes, I don't know who to get into a bootloader in this situation, if that were working I would have some hope.
If you can get to the bootloader you can use google's flashing website, flash.android.com. I just use that to go back to stock, even with an unlocked bootloader.
pysklona said:
If you can get to the bootloader you can use google's flashing website, flash.android.com. I just use that to go back to stock, even with an unlocked bootloader.
Click to expand...
Click to collapse
Thanks @pysklona. you are right, but the problem is I can't get into the bootloader. This is what I am seeking help for.
rao_hamza said:
Thanks @pysklona. you are right, but the problem is I can't get into the bootloader. This is what I am seeking help for.
Click to expand...
Click to collapse
Sorry, misread the post.
@pysklona came here because I'm in the same boat, hard-bricked my device after running the flash-all script. Was using the most recent version of platform tools and the brand new cable that came with the phone.
Was getting the same result, attaching it to a windows pc makes the attached device chime, but disconnects after a few seconds. It came up first as "Setting up Pixel ROM Recovery". I let it sit overnight and now it doesn't auto-disconnect and I get a serial device under com3 on windows. Attaching it to macos gives me a "Pixel ROM Recovery" device. Despite "recovery" in the name, I think it's actually in EDL mode, not recovery mode. No devices come up for adb or fastboot on windows, linux or macos. Screen is completely blank no matter what.
Not being a Qualcomm chip makes this whole process from here a bit of an unknown, but will assume the process for recovery is more or less the same. Looking into QPST/MsmDownloadTool/OpenPST, although as pointed out, I'm not sure any of those tools will work since this isn't a qualcomm chip. MsmDownloadTool is for oneplus, but maybe something can be modded.
ootri said:
@pysklona came here because I'm in the same boat, hard-bricked my device after running the flash-all script. Was using the most recent version of platform tools and the brand new cable that came with the phone.
Was getting the same result, attaching it to a windows pc makes the attached device chime, but disconnects after a few seconds. It came up first as "Setting up Pixel ROM Recovery". I let it sit overnight and now it doesn't auto-disconnect and I get a serial device under com3 on windows. Attaching it to macos gives me a "Pixel ROM Recovery" device. Despite "recovery" in the name, I think it's actually in EDL mode, not recovery mode. No devices come up for adb or fastboot on windows, linux or macos. Screen is completely blank no matter what.
Not being a Qualcomm chip makes this whole process from here a bit of an unknown, but will assume the process for recovery is more or less the same. Looking into QPST/MsmDownloadTool/OpenPST, although as pointed out, I'm not sure any of those tools will work since this isn't a qualcomm chip. MsmDownloadTool is for oneplus, but maybe something can be modded.
Click to expand...
Click to collapse
Thanks for sharing your experience. I just returned the device and got myself a new one.
anyways, i am not sure what is causing this hard brick. thats is something we all should be careful about it.
same thing here. pixel 6 from google store. magisk installed on the december update and i downgraded to the november one using the flash-all.bat script. phone reboots and am told the software is corrupt
reboot back into fastboot mode, run the script again. and get this software is corrupt message again
this time I cant' even boot into fastboot/bootloader mode. and plugging the phone into windows gives me the "pixel rom recovery" message
phone seems dead (black screen, not responding to hardware buttons)
any other solutions than to get it replaced?
Hmm, maybe plug it in to a PC via USB to supply it with power (maybe the battery is down) and just do a very long press of the power button - at least 30 seconds - until the phone starts up. If it does and isn't in fastboot you could try "Power-VolDown" to get into fastboot...
If it just doesn't react to all of this and waiting a bit (in case the battery was at 0% and needs some minimal charge) I think a replacement is the only way to go....
Enddo said:
same thing here. pixel 6 from google store. magisk installed on the december update and i downgraded to the november one using the flash-all.bat script. phone reboots and am told the software is corrupt
reboot back into fastboot mode, run the script again. and get this software is corrupt message again
this time I cant' even boot into fastboot/bootloader mode. and plugging the phone into windows gives me the "pixel rom recovery" message
phone seems dead (black screen, not responding to hardware buttons)
any other solutions than to get it replaced?
Click to expand...
Click to collapse
You could try Official Google Android Flash Tool. It's merely another method of doing what you effectively tried, but from what I've read, it's helped some folks. Sadly, others have reported that the Official Google Pixel Update and Software Repair hasn't been updated for the P6P yet.
If that doesn't help, hang in there. There are others in here who will likely have even better advice.
roirraW edor ehT said:
You could try Official Google Android Flash Tool. It's merely another method of doing what you effectively tried, but from what I've read, it's helped some folks. Sadly, others have reported that the Official Google Pixel Update and Software Repair hasn't been updated for the P6P yet.
If that doesn't help, hang in there. There are others in here who will likely have even better advice.
Click to expand...
Click to collapse
appreciate the links. right now, I can't even get into fastboot/bootloader mode. so neither of those tools detect the phone.
@s3axel the battery definitely isn't low. I charged it up before all this specifically so that I know it had plenty of juice (was at 93% or something).
I'm thinking maybe after letting the battery die, charging it back up will let me boot into a special boot mode
but any other ideas, please, I'm all ears
I recently installed ArrowOS to my F3 and everything went well. Then I tried returning back to MIUI, flashing it through recovery didn't work so I used the MiFlash tool. Unfortunately I accidentally chose the Erase all and lock option but I exited the application halfway. Now my phone is stuck in fastboot and doesn't turn off, holding down the power button only resets and returns to fastboot. I tried reflashing MIUI both in fastboot and Miflash but both failed. I also checked if my phone was still unlock through MiUNlock and said it was unlocked, though the unlock icon isn't present when the phone is resetted. Is there a way to fix my issue, I'm really concerned if this will permanently break my device and possibly burin in the fastboot logo on my display. Any bit of advice and help is appreciated.
Lol , help you how?
Guess what's wrong ?
What error? Post everything first
Your phone is not locked if you removed it before end
Rstment ^m^ said:
Lol , help you how?
Guess what's wrong ?
What error? Post everything first
Your phone is not locked if you removed it before end
Click to expand...
Click to collapse
I'm stuck in fastboot and restarting does not work since it only goes back to fastboot.
AM3471_ said:
I'm stuck in fastboot and restarting does not work since it only goes back to fastboot.
Click to expand...
Click to collapse
Open mi flash , send error message
Rstment ^m^ said:
Open mi flash , send error message
Click to expand...
Click to collapse
Its just stuck in this step in both keep data and wipe all data.
Looks like usb cable contact issue to me , could even be locked if your halfway is 10min into flash or something... It also happens when you flash consecutively without rebooting
Check pc usb port , plug into usb 2.0 port
Check cable , use original cable
Reboot phone before every flash attempt
If one firmware doesn't work download and try another one ( Only if it spits out crc error : step 7/9 , any other error or lower step like 4/9 re insert usb cable into phone and don't touch it , the phone is losing contact ). Crc error is a real bich , you are on your own figuring that out , don't even bother with guides like removing crc check.
You are failing at the very first step , open mi flash logs from it's dropdown menu and either send screenshot or zip the whole folder and attach it here
1. Make sure ur device is unlocked bootloader
2. Download and extract this file https://t.me/PocoF3ID/494392
3. Double click hentai_go_away.bat it will help you out of fastboot and get you to twrp. From there u can install whatever rom u want.
armuttaqin said:
1. Make sure ur device is unlocked bootloader
2. Download and extract this file https://t.me/PocoF3ID/494392
3. Double click hentai_go_away.bat it will help you out of fastboot and get you to twrp. From there u can install whatever rom u w
Click to expand...
Click to collapse
He already used twrp and messed everything up , it won't work even if he gets into it.
Here are the logs of the Miflash, I used two versions the first being more recent.
AM3471_ said:
Its just stuck in this step in both keep data and wipe all data.
Click to expand...
Click to collapse
Reboot phone by holding power button for 10-15seconds , hold power down as well , don't let it try booting up at all.
Your best bet is to boot it straight into fastboot , not let it fail the boot and enter fastboot by itself
Rstment ^m^ said:
Looks like usb cable contact issue to me , could even be locked if your halfway is 10min into flash or something... It also happens when you flash consecutively without rebooting
Check pc usb port , plug into usb 2.0 port
Check cable , use original cable
Reboot phone before every flash attempt
If one firmware doesn't work download and try another one ( Only if it spits out crc error : step 7/9 , any other error or lower step like 4/9 re insert usb cable into phone and don't touch it , the phone is losing contact ). Crc error is a real bich , you are on your own figuring that out , don't even bother with guides like removing crc check.
You are failing at the very first step , open mi flash logs from it's dropdown menu and either send screenshot or zip the whole folder and attach it here
Click to expand...
Click to collapse
I used two version of Miflash, the first being the newest.
AM3471_ said:
I used two version of Miflash, the first being the newest.
Click to expand...
Click to collapse
Sorry I accidentally resent.
Rstment ^m^ said:
Reboot phone by holding power button for 10-15seconds , hold power down as well , don't let it try booting up at all.
Your best bet is to boot it straight into fastboot , not let it fail the boot and enter fastboot by itself
Click to expand...
Click to collapse
It only boots to fastboot, and trying to shut it off only restarts it to fastboot.
I reflashed miui and this error popped up.
AM3471_ said:
Sorry I accidentally resent.
Click to expand...
Click to collapse
Reboot phone , remove usb cable from phone , rotate it 180° and plug it in again. Don't touch the phone at all after that. Move away from pc table , click start and watch it from distance.
Fastboot commands are not going through correctly from what I've seen in the logs of one folder.
Send screenshot if it errors out again, and logs...
Honestly idk what to tell you , bring the phone under light and inspect the usb port, same with pc port and cable , if all is good keep rebooting the phone and plugging in the cable in and put after every flash.
I had the same issue before , my usb port had water dmg and would act the same way. Flashing fine one time , and other time erroring out in many different ways.
AM3471_ said:
I reflashed miui and this error popped up.View attachment 5509325
Click to expand...
Click to collapse
Send logs for that
This is 100℅ bad connection between phone and pc imo. Somerhing is not quite right , either you have junk in pc/phone/cable ports or there's corrosion covering the pins inside
37216a9f]:err:sending sparse 'super' 3/9 (781964 KB)...
[8:14:35 pm 37216a9f]:err:FAILED (data transfer failure (Unknown error))
Rstment ^m^ said:
Send logs for that
Click to expand...
Click to collapse
This will be my last post for now, I need to get some sleep since its late here, if i dont find any fix tomorrow I'll just send to a repair shop.
Rstment ^m^ said:
This is 100℅ bad connection between phone and pc imo. Somerhing is not quite right , either you have junk in pc/phone/cable ports or there's corrosion covering the pins inside
37216a9f]:err:sending sparse 'super' 3/9 (781964 KB)...
[8:14:35 pm 37216a9f]:err:FAILED (data transfer failure (Unknown error))
Click to expand...
Click to collapse
I'll try using a different PC tomorrow to see what the problem is.
AM3471_ said:
This will be my last post for now, I need to get some sleep since its late here, if i dont find any fix tomorrow I'll just send to a repair shop.
Click to expand...
Click to collapse
That's not the log file for error above... But I found similar one in folders above.
Clean the ports before you sleep... Power off everyrhing , phone pc , remove usb cable from charger and clean them all with cotton - if you have 97℅ or higher alchohol you can soak the cotton in it and clean the ports.
If not just send it back to service... They will prolly replace your motherboard if the flashing fails on their end as well , usb port will only be replaces at the very end of their troubleshooting.