Hello Guys,
My Lenovo P1A42 is stuck in Lenovo logo bootloop.
I tried to flash the stock rom "P1a42_S288_160721_ROW_RAW_QFIL" with QFIL.
So with QFIL, I see the Qualcomm HS-USB QDLoader 9008 (COM3).
I select "P1a42_S288_160721_ROW_RAW_QFIL\prog_emmc_firehose_8936.mbn" for programmer path.
I select build "P1a42_S288_160721_ROW_RAW_QFIL"
I also select rawprogram0.xml and patch0.xml.
It takes about 10 minutes to download and in the end "Download succeed. Finish download" message appears.
After this step, I press power+vol up+vol down together for around 12 secs to let the phone start with the downloaded new rom but again the phone goes to lenovo logo bootloop.
I have been continuosly searching for the solution but I still could not find it.
Probably I am missing a very small detail.
Can somebody please help me with this problem?
Thanks in advance.
Regards.
After a lot of trials I could solve the problem, but I dont know what I did different.
I did everything the same.
Anyway thanks to everybody who read.
Regards.
hagiwatt said:
Hello Guys,
My Lenovo P1A42 is stuck in Lenovo logo bootloop.
I tried to flash the stock rom "P1a42_S288_160721_ROW_RAW_QFIL" with QFIL.
So with QFIL, I see the Qualcomm HS-USB QDLoader 9008 (COM3).
I select "P1a42_S288_160721_ROW_RAW_QFIL\prog_emmc_firehose_8936.mbn" for programmer path.
I select build "P1a42_S288_160721_ROW_RAW_QFIL"
I also select rawprogram0.xml and patch0.xml.
It takes about 10 minutes to download and in the end "Download succeed. Finish download" message appears.
After this step, I press power+vol up+vol down together for around 12 secs to let the phone start with the downloaded new rom but again the phone goes to lenovo logo bootloop.
I have been continuosly searching for the solution but I still could not find it.
Probably I am missing a very small detail.
Can somebody please help me with this problem?
Thanks in advance.
Regards.
Click to expand...
Click to collapse
Please follow Getting Ready and Flashing ROM from the link https://forum.xda-developers.com/vibe-p1/development/qpst-flashing-vibeui-3-1-s272-rom-t3386650 . Once Success, The system/Phone reboots itself, You need not hold any combination of keys to reboot
Primarily make sure Your PC?Laptop detects QComm Driver when you Hold Vol Up+USB. If the device is detected and Driver not installed, You can install the same from the above link.
Verify the above using Device manager.
pavanpilot94 said:
Please follow Getting Ready and Flashing ROM from the link https://forum.xda-developers.com/vibe-p1/development/qpst-flashing-vibeui-3-1-s272-rom-t3386650 . Once Success, The system/Phone reboots itself, You need not hold any combination of keys to reboot
Primarily make sure Your PC?Laptop detects QComm Driver when you Hold Vol Up+USB. If the device is detected and Driver not installed, You can install the same from the above link.
Verify the above using Device manager.
Click to expand...
Click to collapse
Dear pavanpilot94,
Thank you for your message.
I had already made the procedure following the instructions in the link you sent to me. In the end of the download "Download succeed. Finish download" message appeared, but it did not restart automatically.
That is why as mentioned in the instructions you sent; ("If "ready" message appears and device does not go to reboot, then hold Volume UP + Power buttons for ~12 sec.")), I had to make the key combination.
But everytime the device went to reboot the old Android in the device, so flashing was not successful.
I do not know where the problem was. After many trials, I could flash successfully, but everytime I had to do the same things. I did not make anything different.
Anyway the problem is solved now, but next time flashing, I do not know how to avoid this problem.
Thank you very much.
hagiwatt said:
Dear pavanpilot94,
Thank you for your message.
I had already made the procedure following the instructions in the link you sent to me. In the end of the download "Download succeed. Finish download" message appeared, but it did not restart automatically.
That is why as mentioned in the instructions you sent; ("If "ready" message appears and device does not go to reboot, then hold Volume UP + Power buttons for ~12 sec.")), I had to make the key combination.
But everytime the device went to reboot the old Android in the device, so flashing was not successful.
I do not know where the problem was. After many trials, I could flash successfully, but everytime I had to do the same things. I did not make anything different.
Anyway the problem is solved now, but next time flashing, I do not know how to avoid this problem.
Thank you very much.
Click to expand...
Click to collapse
I now understand very clearly hagiwatt,
I'm happy that Device is back!!! :good::good::highfive:
On a Guess from the above understood there might be corrupt emmc locations, For this to be verified we might have to format the entire emmc. I'm too stuck with Logo Screen now, Unfortunately my Device is not getting detected by the Computer(Qcomm QDLoader) to have it flashed.
Trying to Fix it, I did a entire Format & Verified any Bad sectors as suggested by one of the developer, Unfortunately still not able to get the device detected.
pavanpilot94 said:
I now understand very clearly hagiwatt,
I'm happy that Device is back!!! :good::good::highfive:
On a Guess from the above understood there might be corrupt emmc locations, For this to be verified we might have to format the entire emmc. I'm too stuck with Logo Screen now, Unfortunately my Device is not getting detected by the Computer(Qcomm QDLoader) to have it flashed.
Trying to Fix it, I did a entire Format & Verified any Bad sectors as suggested by one of the developer, Unfortunately still not able to get the device detected.
Click to expand...
Click to collapse
I struggled for it since I wanted to send the device to warranity for vibration problem. I am happy that I could flash with the raw rom. I also wanted to reset the binary counter but no way.
Triangle Away does not support Lenovo.
I hope they are not checking the binary counter in the service center.
Does anyone have an experience about it?
Thanks.
hagiwatt said:
I struggled for it since I wanted to send the device to warranity for vibration problem. I am happy that I could flash with the raw rom. I also wanted to reset the binary counter but no way.
Triangle Away does not support Lenovo.
I hope they are not checking the binary counter in the service center.
Does anyone have an experience about it?
Thanks.
Click to expand...
Click to collapse
Hi Everybody!
I have just recieved the phone from service center. They fixed the vibration problem under warranity.
So binary counter did not affect the warranity status.
I dont know if they checked the counter or not.
For information to anyone who has the same issue.
Regards.
pavanpilot94 said:
Please follow Getting Ready and Flashing ROM from the link https://forum.xda-developers.com/vibe-p1/development/qpst-flashing-vibeui-3-1-s272-rom-t3386650 . Once Success, The system/Phone reboots itself, You need not hold any combination of keys to reboot
Primarily make sure Your PC?Laptop detects QComm Driver when you Hold Vol Up+USB. If the device is detected and Driver not installed, You can install the same from the above link.
Verify the above using Device manager.
Click to expand...
Click to collapse
and if the pc did not detecte the phone and i cant see any thing new in device manager ,plz help me
Related
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!
Hey everyone,
We have an LG G3 D855 here which has been interrupted midway through flashing a KDZ file,
Powering on the device gives us,
"Cause : Boot certification verify (secure booting error)"
Followed by the screen going off and the blue red LED flashing endlessly.
Download mode does not work,
Recovery mode does not work,
However, the factory reset screen appears, but when selecting yes it reverts to the LG logo and reboots.
Here is a screen shot of what appears in device manager on my PC after I attempt to enter download mode.
As you can see, it is "QHSUSB_BULK" in device manager.
We have tried adapting this guide for the G2 with Ubuntu, but the device is not recognized by Ubuntu. http://forum.xda-developers.com/showthread.php?t=2582142
If we can get into fastboot somehow we will be fine, but nothing seems to be responding. Any advice would be fantastic.
We also have another idea, of super hard bricking the device somehow so that we can follow this tested method of getting out of the brick,
http://forum.xda-developers.com/lg-g3/general/fix-unbrick-lg-g3-stuck-qualcomm-hs-usb-t2933853 not sure how to get either of these though so some help would be great.
The same problem has been described here, http://forum.xda-developers.com/lg-g3/help/lg-g3-d855-rooted-download-mode-t3003988
EDIT : After 10 hours of working on this problem we found the solution and posted our fix and explanation here http://forum.xda-developers.com/lg-...nload-mode-t3273824/post64377399#post64377399
Thanks to all parties involved.
Orcam said:
Hey everyone,
We have an LG G3 D855 here which has been interrupted midway through flashing a KDZ file,
Powering on the device gives us,
"Cause : Boot certification verify (secure booting error)"
Followed by the screen going off and the blue red LED flashing endlessly.
Download mode does not work,
Recovery mode does not work,
However, the factory reset screen appears, but when selecting yes it reverts to the LG logo and reboots.
Here is a screen shot of what appears in device manager on my PC after I attempt to enter download mode.
As you can see, it is "QHSUSB_BULK" in device manager.
We have tried adapting this guide for the G2 with Ubuntu, but the device is not recognized by Ubuntu. http://forum.xda-developers.com/showthread.php?t=2582142
If we can get into fastboot somehow we will be fine, but nothing seems to be responding. Any advice would be fantastic.
We also have another idea, of super hard bricking the device somehow so that we can follow this tested method of getting out of the brick,
http://forum.xda-developers.com/lg-g3/general/fix-unbrick-lg-g3-stuck-qualcomm-hs-usb-t2933853 not sure how to get either of these though so some help would be great.
The same problem has been described here, http://forum.xda-developers.com/lg-g3/help/lg-g3-d855-rooted-download-mode-t3003988
Click to expand...
Click to collapse
Have a look here >> http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 <<
Follow the guide above
tallman43 said:
Have a look here >> http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 <<
Click to expand...
Click to collapse
Thanks mate, are there no software alternatives to this problem? We have been looking literally for hours.
It works! I have found a diffrent package at web. The "Device is not in DL mode" issue is much better with! If the DL breaks, reject the USB-cable and klick start again the process should start without probs. For prevent the app to freeze exclude cust.mbn, system.mbn, userdata.mbn, cache.mbn every .mbn bigger then 50mb. This files we can flash later with Flashtool after the device is back to life
Files: https://mega.nz/#!fRwD1a4Z!Et6aea3XInKW4frrNs-GqGz5diIQdjNBjOg6uTiG6Hk
Hope it would help...
greets and very Christmas to all!
Hello ..
I have a big problem !! I try to flash the Smartzen rom for try and after when my phone reboot..I have a bootloop
But the problem it's -> I don't acces to the bootloader and the recovery
I make power and volume + and i have vibration and just that
When i put the phone with the usb cable the phone doesn't charge.. and sometimes yes
And sometimes the phone reboot with a bootloop
I can't flash a new rom because my pc don't recognize the phone( just the sound when a device is connected) (it's normal i don't have access to bootloader)
And on the tutorial for the unbrick it's say " Ash back to the Zenfone 2, shutdown, press simultaneously the key "source" + "volume +", of course you will see a screen hanging cables. " but i don't have that...i have NOTHING
What is the solution please ?? Because i don't see any solution..
quadeur06 said:
Hello ..
I have a big problem !! I try to flash the Smartzen rom for try and after when my phone reboot..I have a bootloop
But the problem it's -> I don't acces to the bootloader and the recovery
I make power and volume + and i have vibration and just that
When i put the phone with the usb cable the phone doesn't charge.. and sometimes yes
And sometimes the phone reboot with a bootloop
I can't flash a new rom because my pc don't recognize the phone( just the sound when a device is connected) (it's normal i don't have access to bootloader)
And on the tutorial for the unbrick it's say " Ash back to the Zenfone 2, shutdown, press simultaneously the key "source" + "volume +", of course you will see a screen hanging cables. " but i don't have that...i have NOTHING
What is the solution please ?? Because i don't see any solution..
Click to expand...
Click to collapse
If you cant access bootloader i would suggest to use xfstk to reflash the bootloader. follow this guide. I had same problem and successfully recovered from a hard brick.
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
sharkie545 said:
If you cant access bootloader i would suggest to use xfstk to reflash the bootloader. follow this guide. I had same problem and successfully recovered from a hard brick.
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
Click to expand...
Click to collapse
Thank to you're answer...but xfstk doesnt launch on my computer and i see that on the tutorial
back to the Zenfone 2, shutdown, press simultaneously the key "source" + "volume +", of course you will see a screen hanging cables. "
I dont have that
quadeur06 said:
Thank to you're answer...but xfstk doesnt launch on my computer and i see that on the tutorial
back to the Zenfone 2, shutdown, press simultaneously the key "source" + "volume +", of course you will see a screen hanging cables. "
I dont have that
Click to expand...
Click to collapse
Basically as long as you followed the drivers install process correctly under device manager for a quick seccond you will see under IntelSOC you will see moorefield appear then disconnect. If that is good then your on your way.
Simply open xfstk follow the steps link to the proper files for your device, then hit begin download. While the counting is going down, turn on your phone as described in the steps and it should begin flashing.
here is a good video tutorial that helps - credit to timbernot
http://forum.xda-developers.com/zenfone2/general/unbrick-vid-tutorial-restore-serial-t3411064
sharkie545 said:
Basically as long as you followed the drivers install process correctly under device manager for a quick seccond you will see under IntelSOC you will see moorefield appear then disconnect. If that is good then your on your way.
Simply open xfstk follow the steps link to the proper files for your device, then hit begin download. While the counting is going down, turn on your phone as described in the steps and it should begin flashing.
here is a good video tutorial that helps - credit to timbernot
http://forum.xda-developers.com/zenfone2/general/unbrick-vid-tutorial-restore-serial-t3411064
Click to expand...
Click to collapse
Thank you my friends so much!!
same prob here. in my case, I have installeds all things successfuly bt xfstk cant flash after first step. 20 tries and then stop the process. any help?
vyaskd said:
same prob here. in my case, I have installeds all things successfuly bt xfstk cant flash after first step. 20 tries and then stop the process. any help?
Click to expand...
Click to collapse
Usually when this happens xfstk lost communication with the device. Typically I encountered this when xfstk continued to flash the OS file.
In this case the fix is
To Go to Options to change the value in the Value section Override Flag GP 0x80000807. (Note the guide calls for 5 0's but only 4 0's will work)
sharkie545 said:
Usually when this happens xfstk lost communication with the device. Typically I encountered this when xfstk continued to flash the OS file.
In this case the fix is
To Go to Options to change the value in the Value section Override Flag GP 0x80000807. (Note the guide calls for 5 0's but only 4 0's will work)
Click to expand...
Click to collapse
I've done this already before flashing, as told in guide. any other trick to make fone stay connected for little longer? may be some change in xxx807 value?
vyaskd said:
I've done this already before flashing, as told in guide. any other trick to make fone stay connected for little longer? may be some change in xxx807 value?
Click to expand...
Click to collapse
This happened to me too - I solved it the dumbest way possible. The first time I set it up and ran it and it got through the first part and then failed to do the second. I just happened to have to go pick up a pizza at the time, so I went and got the pizza, came back, touched nothing, ran xFSTK again, and it worked! After that, I always ran it once, let it fail, then waited 10 minutes touching nothing, and ran it again. That always works for me (don't know why, and I know it doesn't make sense, but hey it works for me all the time)
Hi,
I somehow managed to get myself into a bootloop situation (it keeps rebooting and showing the asus logo until I shut it down). I had flashed the droidimg.img recovery.img and boot.img files from the latest official stock rom, but that seemed to not work and now I'm in a bootloop. I do not have fastboot or recovery or anything else. It's stuck at the logo and keeps rebooting.
To fix it, I tried to follow the "unbrick" guide (https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785), but I can't see the MOOREFIELD device show up for long enough to even click it (only shows up for a split second under "Other Devices" section). And I can't see "Inter SOC" in device manager at all. Also, xFSTK-Downloader doesn't run (doesn't show up when I click it) at all. This is on Windows 10. I have looked at other guides and they seem to have followed the "unbrick" guide, which doesn't work for me.
Is the phone done for good or is there hope?
fengshaun said:
Hi,
I somehow managed to get myself into a bootloop situation (it keeps rebooting and showing the asus logo until I shut it down). I had flashed the droidimg.img recovery.img and boot.img files from the latest official stock rom, but that seemed to not work and now I'm in a bootloop. I do not have fastboot or recovery or anything else. It's stuck at the logo and keeps rebooting.
To fix it, I tried to follow the "unbrick" guide (https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785), but I can't see the MOOREFIELD device show up for long enough to even click it (only shows up for a split second under "Other Devices" section). And I can't see "Inter SOC" in device manager at all. Also, xFSTK-Downloader doesn't run (doesn't show up when I click it) at all. This is on Windows 10. I have looked at other guides and they seem to have followed the "unbrick" guide, which doesn't work for me.
Is the phone done for good or is there hope?
Click to expand...
Click to collapse
please don't make multiple thread uselessly. please read the guide properly. that question have already been answered multiple time. connect you phone to pc. turn it off by pressing power button long time. now run xfstk load files tick gpflags override. then click ok. and click begin download it will start waiting for device. now simply click power button to turn on device. xFSTK will force it into required mode and will start download. repeat steps as required
Greetings,im Akmal and today I will be sharing some helpful solution to unbrick your Oppo Find 7/7A.Short Story(myb a lil bit longer)¬
So my find 7A got soft bricked when I install custom rom without using TWRP(pretty stupid to do so)
After rebooting my phone keeps on booting to fastboot mode and no matter it happen the same if i press vol up/vol down and power button.
At this stage I knew my phone is soft bricked.So I found the solution to it through some old posts which you have to extract the ColorOS blablabla and adb thingy(I dont wanna go through it here)
But I dont realised that i forget to flash a file name "TZ.MBN"
Now that my phone wont ever boot or even to fastboot which resulted to hard brick.
No recovery screen.
No Charging status screen
No Fastboot screen
No sign of vibrating when i push the power button
-So here is the solution-
Disclaimer-I am not responsible for what ever happen to your device after this-
-there are already some other posts like this but I make this post to let you know that its still working.
1a)First,download the OPPO UNBRICK TOOL HERE
bit.ly/OPPOUNBRICK
1b)goto Google and search for Qualcomm qd loader.download,install and restart your pc.
2)After restarting,Extract the file from OPPO UNBRICK TOOL and open "Msm8974DownloadTool.exe"
3)as you may have notice,its chinese language or some aliens language but dont worry it isn't corrupted,just follow through↓
4)disconnect your device battery,then open the software and press start,after that connect the phone to your pc/laptop (WITHOUT BATTERY) and hold volume up button
5)please wait patiently as it is reflashing stock rom to your device.
6)as you may have noticed maybe your device disconnected but DONT GET PANICKED! press again the power button until its downloading again on the software.
7)If it has done downloading,some row should be in a Green colour.
8)disconnect your cable and try turning on your device again.
That's it!Any comment or curiosity I will try helping you through the comment section but I not guaranteed everything I can answer
P/S:if your device is softbricked,you just should disconnect your battery,and then open the software and press start,then connect the phone to your pc/laptop (WITHOUT BATTERY) and hold volume up button.
If your device is hard bricked(like mine)only holding the power button could work as well
*UPDATE* 24/2/2019
-If you guys still have any concerns kindly contact me through twitter (0728mal)
*UPDATE* 4/7/2020
-yes it is still working guys,no worries kayy
-no you don't need internet for it to work,the software already has all the files needed to flash the device,which is why the file is pretty big.
best regards,
Akmal
Link updated :good:
akmlfhm said:
Greetings,im Akmal and today I will be sharing some helpful solution to unbrick your Oppo Find 7/7A.Short Story(myb a lil bit longer)¬
So my find 7A got soft bricked when I install custom rom without using TWRP(pretty stupid to do so)
After rebooting my phone keeps on booting to fastboot mode and no matter it happen the same if i press vol up/vol down and power button.
At this stage I knew my phone is soft bricked.So I found the solution to it through some old posts which you have to extract the ColorOS blablabla and adb thingy(I dont wanna go through it here)
But I dont realised that i forget to flash a file name "TZ.MBN"
Now that my phone wont ever boot or even to fastboot which resulted to hard brick.
No recovery screen.
No Charging status screen
No Fastboot screen
No sign of vibrating when i push the power button
-So here is the solution which make my phone came to life again-
Disclaimer-I am not responsible for what ever happen to your device after this-
-there are already some other posts like this but I make this post to let you know that its still working.
-make sure to charge the phone first even if you do not know if it charging or not
1)First,download the OPPO UNBRICK TOOL HERE
bit.ly/OPPOUNBRICK
2)Extract the file and open "Msm8974DownloadTool.exe"
3)as you may have notice,its chinese language or some aliens language but dont worry its not corrupted,just follow through
4)Connect your phone to PC and press the power button until you heard some like mounted usb alert on windows.(its ok aslong windows does not detect it on device manager but its ok if you can hear the alert sound.
5)back to the software,no need to mess around with it.Click on start until its downloading a "new life" to your phone.
6)as you may have noticed maybe your device disconnected but DONT GET PANICKED! press again the power button until its downloading again on the software.
7)If it has done downloading,some row should be in a Green colour.
8)disconnect your cable and try to turning on your device again.
That's it!Any comment or curiosity I will try helping you through the comment section but I not guaranteed everything I can answer
best regards,
Akmal
Click to expand...
Click to collapse
hi im having this problem as well. my find 7a is hard bricked after i flash coloros v2.1.5i without twrp. the problem is, my computer does not detect my phone at all even after i hard reset and hold power button for 30 seconds. i dont think the battery is drained because before this happened, my phones battery was about 90% and i try recharging the phone for 30 minutes, and nothing happened. so the debrick tool cannot be used. can you suggest anything for my problem?
Got excited when I read this post! Is there an Oppo Unbrick tool for Mac? I don't have a Windows machine so I can't run the .exe file... Is there an equivalent for those of us not on Windows? Thank you
Shadician said:
Got excited when I read this post! Is there an Oppo Unbrick tool for Mac? I don't have a Windows machine so I can't run the .exe file... Is there an equivalent for those of us not on Windows? Thank you
Click to expand...
Click to collapse
On Mac's OS, you can always install Windows on its proprietary virtual machine and get the process going that way.
babyenchantress said:
hi im having this problem as well. my find 7a is hard bricked after i flash coloros v2.1.5i without twrp. the problem is, my computer does not detect my phone at all even after i hard reset and hold power button for 30 seconds. i dont think the battery is drained because before this happened, my phones battery was about 90% and i try recharging the phone for 30 minutes, and nothing happened. so the debrick tool cannot be used. can you suggest anything for my problem?
Click to expand...
Click to collapse
hello there!I'm really sorry for not checking this that often and really sorry if i let you down because im too busy with my schools work
btw before my computer can detect my phone i have to download a driver which detect qualcomm processor for my oppo then it can be detected by my pc therefore i can do the unbrick process:good:
Shadician said:
Got excited when I read this post! Is there an Oppo Unbrick tool for Mac? I don't have a Windows machine so I can't run the .exe file... Is there an equivalent for those of us not on Windows? Thank you
Click to expand...
Click to collapse
yeah you can try WINE also but i never have any experience with mac os before so i cant guarantee that it will work considering that you're configuring your drivers,which can go wrong if not done correctly
So I have bricked my phone (X9006) while trying to install TWRP recovery. It is stuck on logo and adb/ fastboot does not recognise it anymore. I have tried the above-mentioned tool, but this program also does not do anything for a long time. Am I missing something in applying this solution?
Edit: I am an Windows 10 and I might not have the Qualcomm drivers installed. I don't know how to install
true_friend2004 said:
So I have bricked my phone (X9006) while trying to install TWRP recovery. It is stuck on logo and adb/ fastboot does not recognise it anymore. I have tried the above-mentioned tool, but this program also does not do anything for a long time. Am I missing something in applying this solution?
Edit: I am an Windows 10 and I might not have the Qualcomm drivers installed. I don't know how to install
Click to expand...
Click to collapse
Hello there.have you tried downloading the "Qualcomm"
Driver software on your PC?
is it necessary to remove the battery? I don't have tools for opening my phone and it's battery is non-removable
Perhaps an important step is missing. The Qualcomm qd loader driver is may not signed. I had to boot into the extended start menu on Windows 10 and disable the driver signature check - point 7 - and could now successfully debrick my find7.