Hi Guys,
My OnePlus 2 has this issue where if i restart the phone it gets stuck on the Boot Screen which shows OnePlus Logo powered by Android.
I can boot my phone to Fastboot and i can only boot into the phone by using command "fastboot continue"
When i try to use command "fastboot oem unlock" the phone reboots and gets stuck on the OP logo
Fastboot oem device-info shows
... INFO Device tampered: true
INFO Device unlocked: false
INFO Device is_verified: false
INFO Charger screen enabled: false
INFO Display panel:
INFO console_locked: 1
INFO exec_console_unconsole: 0
OKAY
and if i try to install twrp recovery by using the command "fastboot flash recovery recovery.img" i get the following message
sending 'recovery' (25956 KB)... OKAY
writing 'recovery'... FAILED (remote: device is locked. Cannot flash images)
Please help
http://forum.xda-developers.com/oneplus-2/general/guide-oneplus-2-mega-unbrick-recover-t3397257
I have tried all those methods and none of them worked for me
pankaj2m said:
I have tried all those methods and none of them worked for me
Click to expand...
Click to collapse
Go to oneplus website & download official rom zip file. Push it into sdcard using fastboot. Go to stock recovery (vol_down + power) & flash the zip file.
I can't boot into to recovery hence can't flash.. I have the official rom zip from oneplus but can't flash it as I can't boot into recovery.. That's the problem
Can anyone please help me with this?? :'(
pankaj2m said:
Hi Guys,
My OnePlus 2 has this issue where if i restart the phone it gets stuck on the Boot Screen which shows OnePlus Logo powered by Android.
I can boot my phone to Fastboot and i can only boot into the phone by using command "fastboot continue"
When i try to use command "fastboot oem unlock" the phone reboots and gets stuck on the OP logo
Fastboot oem device-info shows
... INFO Device tampered: true
INFO Device unlocked: false
INFO Device is_verified: false
INFO Charger screen enabled: false
INFO Display panel:
INFO console_locked: 1
INFO exec_console_unconsole: 0
OKAY
and if i try to install twrp recovery by using the command "fastboot flash recovery recovery.img" i get the following message
sending 'recovery' (25956 KB)... OKAY
writing 'recovery'... FAILED (remote: device is locked. Cannot flash images)
Please help
Click to expand...
Click to collapse
Try the first method in this page https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Its worked in my mobile, when i lost everything (even fastboot also gone). Its surely work. It will flash Oneplus 2 official recovery. You should ensure that your device is detected in your computer and Its shows as Qualcomm 9008
eldos777 said:
Try the first method in this page https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Its worked in my mobile, when i lost everything (even fastboot also gone). Its surely work. It will flash Oneplus 2 official recovery. You should ensure that your device is detected in your computer and Its shows as Qualcomm 9008
Click to expand...
Click to collapse
I followed the all the 3 methods from the post you mentioned.
When i run MSM8994DownloadTool and START, it just stays there. I waited for 1hr for something to happen but nothing.
It Doesnot work for me.
For now, i use Fastboot Continue command in fastboot in case my devices shuts down
pankaj2m said:
I followed the all the 3 methods from the post you mentioned.
When i run MSM8994DownloadTool and START, it just stays there. I waited for 1hr for something to happen but nothing.
It Doesnot work for me.
For now, i use Fastboot Continue command in fastboot in case my devices shuts down
Click to expand...
Click to collapse
Thats means your device is not detected, Did you check device manager in your computer? Is is showing your mobile as Qualcomm 9008?? If it is not please follow the steps on the website, I already given. No need wait 1 hr. If your device is detected, then you can see a green line, and it will finish within 5mnts.
eldos777 said:
Thats means your device is not detected, Did you check device manager in your computer? Is is showing your mobile as Qualcomm 9008?? If it is not please follow the steps on the website, I already given. No need wait 1 hr. If your device is detected, then you can see a green line, and it will finish within 5mnts.
Click to expand...
Click to collapse
Hi Eldos,
In device manager it shows as RELINK HS-USBQDLoader 9008 (COM8)
i followed your instructions but it still does not work. When i run the MSM8994DownloadTool, it does not do anything.
Anything else i can try. I am stuck in this big problem. When my phone switches off, the only way i can boot is by going to FASTBOOT and running command "fastboot continue" only then my phone boots.
Please help.
Thanks,
Pankaj
pankaj2m said:
Hi Eldos,
In device manager it shows as RELINK HS-USBQDLoader 9008 (COM8)
i followed your instructions but it still does not work. When i run the MSM8994DownloadTool, it does not do anything.
Anything else i can try. I am stuck in this big problem. When my phone switches off, the only way i can boot is by going to FASTBOOT and running command "fastboot continue" only then my phone boots.
Please help.
Thanks,
Pankaj
Click to expand...
Click to collapse
Can you come in Team Viewer??
eldos777 said:
Can you come in Team Viewer??
Click to expand...
Click to collapse
Yes, sure.. how do i talk to you?
pankaj2m said:
Yes, sure.. how do i talk to you?
Click to expand...
Click to collapse
Give me your Teamviewer ID and Password
eldos777 said:
Give me your Teamviewer ID and Password
Click to expand...
Click to collapse
ID: 527533613
Password: 6953
pankaj2m said:
Can anyone please help me with this?? :'(
Click to expand...
Click to collapse
PM me
Problem Solved
Deep problem
I have gone through all the unbrick guides, even with a Oneplus technician but we weren't able to unbrick it. I'm guessing that after the oxygen 3.0.2 update, I wiped out the partition (not sure). The phone was unlocked with some TWRP version before that. I totally forgot to update it the right way. I can get use fastboot to go into the OS, but trying to flash doesn't work since it's locked. Trying to unlock it supposedly works but it remains locked. We tried the Qualcomm drivers, installed the certificates and the device is seen as Qualcomm 9800 yadda, yadda, yadda, but the MSM8994DownloadTool.exe doesn't detect the device, therefore it stays there doing nothing. Yes, we changed the developer options in the settings but nothing seems to work. The LTE doesn't work properly either...it shows an exclamation mark, so I have to switch to 3G. I'm in dire need of help, and if anyone can help me, you'd certainly qualify for a master tech support agent or something cause not even they could help me with this. Thanks in advance if any of you can help! I'm using a Windows 10 on a Mac, using Parallels VM...
CharlieVasquez said:
I have gone through all the unbrick guides, even with a Oneplus technician but we weren't able to unbrick it. I'm guessing that after the oxygen 3.0.2 update, I wiped out the partition (not sure). The phone was unlocked with some TWRP version before that. I totally forgot to update it the right way. I can get use fastboot to go into the OS, but trying to flash doesn't work since it's locked. Trying to unlock it supposedly works but it remains locked. We tried the Qualcomm drivers, installed the certificates and the device is seen as Qualcomm 9800 yadda, yadda, yadda, but the MSM8994DownloadTool.exe doesn't detect the device, therefore it stays there doing nothing. Yes, we changed the developer options in the settings but nothing seems to work. The LTE doesn't work properly either...it shows an exclamation mark, so I have to switch to 3G. I'm in dire need of help, and if anyone can help me, you'd certainly qualify for a master tech support agent or something cause not even they could help me with this. Thanks in advance if any of you can help! I'm using a Windows 10 on a Mac, using Parallels VM...
Click to expand...
Click to collapse
I finally got the MSM tool to detect the phone. While still in Qualcomm mode, I disconnected it and connected it to the to Mac usb ports and kept clicking on the tool to start. The green lights finally showed and I'm waiting to see what happens. I will keep you updated.
CharlieVasquez said:
I finally got the MSM tool to detect the phone. While still in Qualcomm mode, I disconnected it and connected it to the to Mac usb ports and kept clicking on the tool to start. The green lights finally showed and I'm waiting to see what happens. I will keep you updated.
Click to expand...
Click to collapse
K, I finally booted normally into the OS, went back and rooted the phone. Now we're good to go again. Not even the tech support agents were able to help me with this one.
Related
Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!
alpheus said:
Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!
Click to expand...
Click to collapse
It looks like your device is not recognized in Fastboot mode...
Have you turned on USB Debugging while connecting PC and Allow in Device when Prompt some message ..
Go to fastboot mode and write this command... fastboot devices
If it will give you a message like this
List of devices
1235456785164
Then your devices is successfully recognized...:good:
It is not recognized by adb devices, but:
fastboot devices - gives the following output:
ERROR: could not get pipe properties
3331E6EBCA6000EC fastboot
Click to expand...
Click to collapse
fastboot oem unlock - gives the following:
ERROR: could not get pipe properties
...
FAILED (remote: Erase Fail)
finished. total time: 4.753s
Click to expand...
Click to collapse
alpheus said:
It is not recognized by adb devices, but:
fastboot devices - gives the following output:
fastboot oem unlock - gives the following:
Click to expand...
Click to collapse
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
Thanks, I tried 3 different cables on 3 different operating systems, with the same problem unlocking the fastboot. When I send fastboot oem unlock the device opens a prompt with Yes or No choice, but after choosing Yes, it stays Locked
Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too
demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
demkantor said:
Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too
Click to expand...
Click to collapse
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!
alpheus said:
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!
Click to expand...
Click to collapse
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..
UPDATE (resolved)
Here is an update. Hope this would help others with similar issue, as I've read many threads and folks complaining that they weren't able to unlock fastboot and further root their Nexus S, and who can't boot the phone, which stacked with Google Logo (soft loop). This was the case with my device and finally I got it resolved. I've read some guy tried to hit the phone and after that he was able to boot phone normally. It related to some hardware electrical circle issue. Anyways, I tried to hit my phone by placing it under the direct sun in balcony for some time until the phone got hot and then power it on. And ooops, my phone started booting passed by that Google Logo which was the good sign. Once the phone booted up, I went ahead and activated USB debugging and restarted the phone into the Fastboot mode. while the phone was still hot and in Fastboot mode I run "fastboot oem unlock" and hey, fastboot is Unlocked! Again, this was done while the phone was hot, any previous attempts (read above) weren't successful. From that point, I went ahead and rooted my Nexus S by Nexus Root Toolkit, available on wugfresh.com/nrt, without a slightest problem. Now my phone is fully rooted, bootable and working fine. I thank all who replied to my thread and tried to help and hope this info would help someone with the similar issue.
Rushabh22 said:
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..
Click to expand...
Click to collapse
Thank you for your help and suggestions.
Q Mobile X 32
bootloader oem unlock problem
plz help
Q-mobile said:
Q Mobile X 32
bootloader oem unlock problem
plz help
Click to expand...
Click to collapse
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923
Setting.Out said:
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923
Click to expand...
Click to collapse
can you help me in rooting Qmobile x32
Q-mobile said:
can you help me in rooting Qmobile x32
Click to expand...
Click to collapse
That thread didn't help?
Here's what the guide says...
Hi guys, I'm having a weird problem with my zenfone 5 (a501cg). I have searched a lot but still can't find out a proper solution So I post it here and try to provide as much information as possible so hopefully developers at xda can help me.
My phone is rooted and I'm currently using modded rom called "bazzrom pinaslang" in the forum. Recently I want to use another rom so I decide to use adb sideload again.
However, the problem occurs: using adb sideload only show "error" message". BUT Adb devices show the phone.
Then I decide to use adb reboot fastboot to enter fastboot. But the phone only show a usb icon, and using "fastboot devices" doesn't show the device anymore.
I try other way by enter recovery mode "adb reboot recovery". The phone show resting android with "no command" message. I also try hold power and press down volumn after that but nothing happend. I try anything with that "power" + "volumn" combo but nothing happend (or it just shutdowns the phone).
Also, using "power" + "up volumn" to enter Droid boot doesn't work.
Driver is install. In device manager it shows "Android composite adb interface".
The only good news is my phone still boots normally and I can use it. Please help me get back my fastboot so I can upgrade my phone to Lollipop and other modded ROM.
Thank you so much !!!!
techgeard said:
Hi guys, I'm having a weird problem with my zenfone 5 (a501cg). I have searched a lot but still can't find out a proper solution So I post it here and try to provide as much information as possible so hopefully developers at xda can help me.
My phone is rooted and I'm currently using modded rom called "bazzrom pinaslang" in the forum. Recently I want to use another rom so I decide to use adb sideload again.
However, the problem occurs: using adb sideload only show "error" message". BUT Adb devices show the phone.
Then I decide to use adb reboot fastboot to enter fastboot. But the phone only show a usb icon, and using "fastboot devices" doesn't show the device anymore.
I try other way by enter recovery mode "adb reboot recovery". The phone show resting android with "no command" message. I also try hold power and press down volumn after that but nothing happend. I try anything with that "power" + "volumn" combo but nothing happend (or it just shutdowns the phone).
Also, using "power" + "up volumn" to enter Droid boot doesn't work.
Driver is install. In device manager it shows "Android composite adb interface".
The only good news is my phone still boots normally and I can use it. Please help me get back my fastboot so I can upgrade my phone to Lollipop and other modded ROM.
Thank you so much !!!!
Click to expand...
Click to collapse
Hi,
Have you tried to boot into your system, enable USB debugging and run
Code:
adb reboot-bootloader
?
dgadelha said:
Hi,
Have you tried to boot into your system, enable USB debugging and run
Code:
adb reboot-bootloader
?
Click to expand...
Click to collapse
Hi dgadelha, thanks for your reply.
I have tried your suggestion before but phone only reboots and display usb icon. I also try power volumn combi like i did in my post but still nothing happened.
Usb debugging is enabled.
Techgeard.
techgeard said:
Hi dgadelha, thanks for your reply.
I have tried your suggestion before but phone only reboots and display usb icon. I also try power volumn combi like i did in my post but still nothing happened.
Usb debugging is enabled.
Techgeard.
Click to expand...
Click to collapse
In that case, follow the "Last resort" part of this guide http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=33800
It will reinstall your fastboot when the USB icon appears
dgadelha said:
In that case, follow the "Last resort" part of this guide
It will reinstall your fastboot when the USB icon appears
Click to expand...
Click to collapse
Hi dgadelha,
I have seen your link before my post, but I still wonder because the "last resort" in the link is used for "bricked" phone or the one that doesn't start up or stuck in somewhere. My phone can still boot and use quite normal : ( except one thing that my sd card always unmounted in this Pinaslang modded rom.
TG.
UPDATE I decide to try xFSTK but my computer still recognizes the device as "adb..." . if I turn off developer mode it becomes "portable device" in Window Device Manager.
The xFSTK can't recognize any Cloverfieldplus. (it shows "CLOVERFIELDPLUS...: 0")
TG.
techgeard said:
Hi dgadelha,
I have seen your link before my post, but I still wonder because the "last resort" in the link is used for "bricked" phone or the one that doesn't start up or stuck in somewhere. My phone can still boot and use quite normal : ( except one thing that my sd card always unmounted in this Pinaslang modded rom.
TG.
Click to expand...
Click to collapse
Hi,
Because the last resort will use a hardware function (xFSTK way) to update your dnx, ifwi and fastboot images. This way you can restore your fastboot.
Thanks.
techgeard said:
UPDATE I decide to try xFSTK but my computer still recognizes the device as "adb..." . if I turn off developer mode it becomes "portable device" in Window Device Manager.
The xFSTK can't recognize any Cloverfieldplus. (it shows "CLOVERFIELDPLUS...: 0")
TG.
Click to expand...
Click to collapse
You must instal the drivers it mentioned.
Also it will appear as Cloverview when the USB logo appears
Thanks!
dgadelha said:
Hi,
Because the last resort will use a hardware function (xFSTK way) to update your dnx, ifwi and fastboot images. This way you can restore your fastboot.
Thanks.
You must instal the drivers it mentioned.
Also it will appear as Cloverview when the USB logo appears
Thanks!
Click to expand...
Click to collapse
Hi dgadelha,
After a while I can start the xFSTK and begin download. However, after some attempts it always say error. The same messages show up as below:
Code:
start
sending dner
writeoutpipe dner
writeoutpipe 0
write----> dner
windriver Error: 0x20000015, Timeour expired
LogError
Error Code:1 - Connection Error
Failed to start Dldr state matchine, aborting...
void CloverviewPlusDownloader::do_abort()
Abott
FAIL
.....
techgeard said:
Hi dgadelha,
After a while I can start the xFSTK and begin download. However, after some attempts it always say error. The same messages show up as below:
Click to expand...
Click to collapse
Hi techgeard,
Looks like it's a driver timeout.
Which OS are you using? I see they used Windows 7 or before on the tests.
Also you should try getting xFSTK developers (on SourceForge) to help about this issue.
Thanks.
dgadelha said:
Hi techgeard,
Looks like it's a driver timeout.
Which OS are you using? I see they used Windows 7 or before on the tests.
Also you should try getting xFSTK developers (on SourceForge) to help about this issue.
Thanks.
Click to expand...
Click to collapse
Iam using Win7x64. The same with the guy posting in the link.
TG.
hi yesterday i was far from home with 5% battery and i take some calls some photos and battery 0%
when i got home i plugged in and battery is too laow message screen appear and after the message:
The boot loader is unlocked and software integrity cannot be guaranteed. Any data stored on the device may be available to attackers. Do not store any sensitive data on the device.
Visit this link on another device to learn more:
g.co/ABH
can.t be power off when this message appear, i need to let battery drain and power key do nothing
and msmdownloand show nothing
Oneplus 6T on latest beta
Windows 10 i don.t know if has all drivers needed for a unbricked process
amkulcsar said:
hi yesterday i was far from home with 5% battery and i take some calls some photos and battery 0%
when i got home i plugged in and battery is too laow message screen appear and after the message:
The boot loader is unlocked and software integrity cannot be guaranteed. Any data stored on the device may be available to attackers. Do not store any sensitive data on the device.
Visit this link on another device to learn more:
g.co/ABH
can.t be power off when this message appear, i need to let battery drain and power key do nothing
and msmdownloand show nothing
Oneplus 6T on latest beta
Windows 10 i don.t know if has all drivers needed for a unbricked process
Click to expand...
Click to collapse
I've had this before. If your phone has fully discharged and you plug in the charger the phone will boot up and stay on that message.
Just leave it to charge for five minutes, unplug the charger, then force reboot it by holding the power and volume down buttons together until it reboots. It should then boot normally and then you can plug in and continue charging.
ebproject said:
I've had this before. If your phone has fully discharged and you plug in the charger the phone will boot up and stay on that message.
Just leave it to charge for five minutes, unplug the charger, then force reboot it by holding the power and volume down buttons together until it reboots. It should then boot normally and then you can plug in and continue charging.
Click to expand...
Click to collapse
SOLVED
wait till screen get of install drivers correctly then press volume keys (+ and -) and connect to pc, in device manager appear at ports as qualcom... and open msmdownload tool and press start
amkulcsar said:
SOLVED
wait till screen get of install drivers correctly then press volume keys (+ and -) and connect to pc, in device manager appear at ports as qualcom... and open msmdownload tool and press start
Click to expand...
Click to collapse
Yeah you didn't need to do that. Just disconnect the charger and hard reboot and you would have been fine like I said, but oh well.
amkulcsar said:
SOLVED
wait till screen get of install drivers correctly then press volume keys (+ and -) and connect to pc, in device manager appear at ports as qualcom... and open msmdownload tool and press start
Click to expand...
Click to collapse
Did you manage to get rid off the corrupted screen message doing this?
That's a standard message if you've unlocked your bootloader. It doesn't signify corruption or an actual issue. You won't get rid of it without locking your bootloader.
Hello everyone, I unlocked my bootloader, but unfortunately I made an error when unlocking it but flashing it. so that he writes me when starting qualcom crashdump mode. and I don't know how to get out of it. also where I get the original onplus6 t software. and i work with linux via terminal. who can help me with this? on the one hand, where can I get the original os9 andriod software? and the second question is how I get the whole thing back on my cell phone and that it comes out of this warning from the grass dump
Hello. Please look on XDA for MSM tool for your device (enchilada or fajita depending on 6 or 6t). It will reinstall OOS back on your phone and relock the bootloader. There are a few videos on YouTube that will guide you through the process. It's a (short) but stressful process, but it does really work.
carrabelloy said:
Hello everyone, I unlocked my bootloader, but unfortunately I made an error when unlocking it but flashing it. so that he writes me when starting qualcom crashdump mode. and I don't know how to get out of it. also where I get the original onplus6 t software. and i work with linux via terminal. who can help me with this? on the one hand, where can I get the original os9 andriod software? and the second question is how I get the whole thing back on my cell phone and that it comes out of this warning from the grass dump
Click to expand...
Click to collapse
If your original plan was to get custom firmware don't bother with msm tool and getting stock, it's unnecessary. Twrp can be booted from fastboot if your bootloader is unlocked and you can do anything you need to do from there.
carrabelloy said:
Hello everyone, I unlocked my bootloader, but unfortunately I made an error when unlocking it but flashing it. so that he writes me when starting qualcom crashdump mode. and I don't know how to get out of it. also where I get the original onplus6 t software. and i work with linux via terminal. who can help me with this? on the one hand, where can I get the original os9 andriod software? and the second question is how I get the whole thing back on my cell phone and that it comes out of this warning from the grass dump
Click to expand...
Click to collapse
I'm in the same boat. Have you found any solution yet? I also use linux.
Brettroth said:
If your original plan was to get custom firmware don't bother with msm tool and getting stock, it's unnecessary. Twrp can be booted from fastboot if your bootloader is unlocked and you can do anything you need to do from there.
Click to expand...
Click to collapse
This was my plan and I soon realized I was not ready. I have unlocked the phone and the bootloader but I'm stuck, not able to get twrp to flash. Here's my error message:
[email protected]:/home/chad/Downloads# fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (32628 KB)...
OKAY [ 0.973s]
writing 'recovery'...
FAILED (remote: No such file or directory)
finished. total time: 0.975s
[email protected]:/home/chad/Downloads#
ce_lloyd said:
This was my plan and I soon realized I was not ready. I have unlocked the phone and the bootloader but I'm stuck, not able to get twrp to flash. Here's my error message:
[email protected]:/home/chad/Downloads# fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (32628 KB)...
OKAY [ 0.973s]
writing 'recovery'...
FAILED (remote: No such file or directory)
finished. total time: 0.975s
[email protected]:/home/chad/Downloads#
Click to expand...
Click to collapse
Should be fastboot boot (path and filename of twrp.img) once it boots then you can flash twrp from within.
I have done that as well. It appears to work, but then I get QUALCOM CrashDump Mode Attempted to kill init! wxitcode=0x0000000b complete..and..exit
This is a T-Mobile branded phone, does that matter or change anything?
ce_lloyd said:
I have done that as well. It appears to work, but then I get QUALCOM CrashDump Mode Attempted to kill init! wxitcode=0x0000000b complete..and..exit
This is a T-Mobile branded phone, does that matter or change anything?
Click to expand...
Click to collapse
If you are on a11 you have to use the twrp.img that is posted on the cross development thread that works for opt6 and 6t. TWRP-3.6.0_11-OP6xT.img
As the title says, my phone just boots till asus logo and switches off. The battery was 15% at night. I woke up and there was no juice left. So I kept my phone for charging. The phone just boot loops with big battery icon with no charging animation. Even the recovery doesn't work. I tried flashing via fastboot mode. My phone was already unlocked. But during fastboot, it says FAILED (remote: 'Error flashing partition : Write Protected'). Any help? Yes, I'm using usb 2.0 port.
anagramgenius said:
As the title says, my phone just boots till asus logo and switches off. The battery was 15% at night. I woke up and there was no juice left. So I kept my phone for charging. The phone just boot loops with big battery icon with no charging animation. Even the recovery doesn't work. I tried flashing via fastboot mode. My phone was already unlocked. But during fastboot, it says FAILED (remote: 'Error flashing partition : Write Protected'). Any help?
Click to expand...
Click to collapse
Try following this tutorial all over again.
https://telegra.ph/Guide-to-unlock-bootloader-flash-custom-recovery-and-root-ASUS-Max-Pro-M2-03-06
Anubhav_singh said:
Try following this tutorial all over again.
https://telegra.ph/Guide-to-unlock-bootloader-flash-custom-recovery-and-root-ASUS-Max-Pro-M2-03-06
Click to expand...
Click to collapse
My phone is already unlocked. And now the fastboot isn't working. I already tried unlocking again. I get the above mention error while flashing via fastboot.
anagramgenius said:
My phone is already unlocked. Add now the fastboot isn't working. I already tried unlocking again. I get the above mention error while flashing via fastboot.
Click to expand...
Click to collapse
You get the unlocked bootloader warning while rebooting the device now.?
Anubhav_singh said:
You get the unlocked bootloader warning while rebooting the device now.?
Click to expand...
Click to collapse
Yes. But it doesn't boot to system. It just switches off after displaying asus logo.
anagramgenius said:
Yes. But it doesn't boot to system. It just switches off after displaying asus logo.
Click to expand...
Click to collapse
Join the device group on telegram, it would be easy to get help there as it might be a lengthy process.
Anubhav_singh said:
Join the device group on telegram, it would be easy to get help there as it might be a lengthy process.
Click to expand...
Click to collapse
Yes I have already joined. But I don't have a backup smartphone. So I'll have to wait I guess.
EDIT: Seems no one knows a solution in telegram group either. I asked about this problem there and one or two replied and they stopped replying.
anagramgenius said:
Yes I have already joined. But I don't have a backup smartphone. So I'll have to wait I guess.
EDIT: Seems no one knows a solution in telegram group either. I asked about this problem there and one or two replied and they stopped replying.
Click to expand...
Click to collapse
Okay, try flashing the fastboot rom. It will relock the bootloader and will flash the stock oreo rom. See if this works.
Anubhav_singh said:
Okay, try flashing the fastboot rom. It will relock the bootloader and will flash the stock oreo rom. See if this works.
Click to expand...
Click to collapse
It shows the same error. Nothing can be flashed via fastboot mode.
Was anyone able to resolve this?
mitrokin said:
Was anyone able to resolve this?
Click to expand...
Click to collapse
No.
anagramgenius said:
No.
Click to expand...
Click to collapse
You might need to visit the service center, as recovery can't be booted, also nothing can be flashed as device is write protected.
try to unlockbootloader again and try flashing then
nishant6577 said:
try to unlockbootloader again and try flashing then
Click to expand...
Click to collapse
No fastboot command is working. So I can't unlock bootloader again.(it is already unlocked btw)
anagramgenius said:
No fastboot command is working. So I can't unlock bootloader again.(it is already unlocked btw)
Click to expand...
Click to collapse
Check whether your usb port is 3.0, fastboot needs usb 2.0 ports for fastboot commands.
V9_6b said:
Check whether your usb port is 3.0, fastboot needs usb 2.0 ports for fastboot commands.
Click to expand...
Click to collapse
Yup. It's usb 2.0 port.
Bro,I have same problem as you have.how can I solve it even edl method also shows firehose qloader failed error .how I solve bro!!!
Anyone? Please help us, I'm also in this kind of situation with OP. I still can't use Asus Flash Tool because it needs internet connection I'm just borrowing my cousin's PC and they don't have internet broadband either.
I'm wondering if it also gives an error "write protected" like on Fastboot CMD. And if it does I think our last resort is to flash with QFIL.
If I am right, you'll updated to the 073 pie version of the stock software, which bricked the devices.?
blood1995 said:
Anyone? Please help us, I'm also in this kind of situation with OP. I still can't use Asus Flash Tool because it needs internet connection I'm just borrowing my cousin's PC and they don't have internet broadband either.
I'm wondering if it also gives an error "write protected" like on Fastboot CMD. And if it does I think our last resort is to flash with QFIL.
Click to expand...
Click to collapse
Unable to flash with QFIL either.
Hello, im new to the forums and i would like to get some help with this huawei on what to do. I recieved this phone already bricked from a friend, so i would like to see if i can make it work again. I dont know how the phone got bricked and i have no idea of what to do. The problem is that the phone starts in the huawei logo and then goes to a black screen and turns itself off again. The phone doesnt make it past that point. I tried to make a reset from recovery, but it doesnt work. In download mode i tried to download the latest recovery, but it says failed to download. In fastboot mode the phone says "Phone unlocked" in red letters and "FRP locked" in green letters.
Any idea of what to do in order to recover the phone ?.
BrattPitlord said:
Hello, im new to the forums and i would like to get some help with this huawei on what to do. I recieved this phone already bricked from a friend, so i would like to see if i can make it work again. I dont know how the phone got bricked and i have no idea of what to do. The problem is that the phone starts in the huawei logo and then goes to a black screen and turns itself off again. The phone doesnt make it past that point. I tried to make a reset from recovery, but it doesnt work. In download mode i tried to download the latest recovery, but it says failed to download. In fastboot mode the phone says "Phone unlocked" in red letters and "FRP locked" in green letters.
Any idea of what to do in order to recover the phone ?.
Click to expand...
Click to collapse
Hello and welcome !
Just thinking you should try to start a fresh & clean install
rolling back to android 6 regardless of the current firmware.
Took a look inside the UNIFIED HELP THREAD but didn't find
any L23 rollback package...
However, I found another LINK that looks promising.
Good luck :fingers-crossed:
For further explanations try asking here.
Dadditz said:
Hello and welcome !
Just thinking you should try to start a fresh & clean install
rolling back to android 6 regardless of the current firmware.
Took a look inside the UNIFIED HELP THREAD but didn't find
any L23 rollback package...
However, I found another LINK that looks promising.
Good luck :fingers-crossed:
For further explanations try asking here.
Click to expand...
Click to collapse
Nice, i will try this and inform back later.
Dadditz said:
Hello and welcome !
Just thinking you should try to start a fresh & clean install
rolling back to android 6 regardless of the current firmware.
Took a look inside the UNIFIED HELP THREAD but didn't find
any L23 rollback package...
However, I found another LINK that looks promising.
Good luck :fingers-crossed:
For further explanations try asking here.
Click to expand...
Click to collapse
Well it didnt work. It says "incompatibility with this version"
BrattPitlord said:
Well it didnt work. It says "incompatibility with this version"
Click to expand...
Click to collapse
Hi,
you should use the follovinq commands in fastboot mode and then post the results please:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar version
fastboot getvar vendorcountry
Can you access Recovery ? (Power + Volume Up)
-Alf- said:
Hi,
you should use the follovinq commands in fastboot mode and then post the results please:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar version
fastboot getvar vendorcountry
Can you access Recovery ? (Power + Volume Up)
Click to expand...
Click to collapse
im new to this, so i put those commands in windows CMD with the phone connected or how ?
I can get to the stock recovery from huawei.
BrattPitlord said:
im new to this, so i put those commands in windows CMD with the phone connected or how ?
I can get to the stock recovery from huawei.
Click to expand...
Click to collapse
Use ADB commands.
Open developers option and turn on the USB debugging. Connect your device to PC in MTP/FILES mode. Run command
ADB reboot bootloader
(the device will reboot to fastboot mode)
Now you can type fastboot commands.
-Alf- said:
Use ADB commands.
Open developers option and turn on the USB debugging. Connect your device to PC in MTP/FILES mode. Run command
ADB reboot bootloader
(the device will reboot to fastboot mode)
Now you can type fastboot commands.
Click to expand...
Click to collapse
How do i turn debugging if the phone is bricked ? I cant get past the huawei logo. However, i do have access to fastboot mode.
BrattPitlord said:
How do i turn debugging if the phone is bricked ? I cant get past the huawei logo. However, i do have access to fastboot mode.
Click to expand...
Click to collapse
Oh, sorry, my mistake . Okay, install on your PC "Minimal ADB and fastboot" , open it , connect the device in fastboot mode, and run commands.