One plus 7 pro (Gm1910) stuck in Qualcomm crashdump mode. - OnePlus 7 Pro Questions & Answers

So my problem began after updating my phone, I was using the official build. Not the beta. 2 days later my phone crashed while using reddit. I forced it to reboot, it didn't boot back up, it was getting stuck after the one plus logo screen, I took it to a repair shop and they tried to flash it but screwed it up, they gave me back my phone with a new error message-
QUALCOMM crashdump mode
Attempted to kill iniT
Exit code -0x000000b.
I didn't root or had the bootloader unlocked, My phone does boot into fastboot mode but I don't know what to do.
Is my phone past the point of no return?

Have you tried the msm tool?

Yes I tried msm it did not work

Shomoyy said:
Yes I tried msm it did not work
Click to expand...
Click to collapse
When in fastboot mode have you tried adb commands? First I would try fastboot devices and see if your device is listed. Then oem unlock. If that is successful try fastboot boot recover.img with the recovery of your choice. I suggest pitch black recovery.
---------- Post added at 03:19 PM ---------- Previous post was at 03:19 PM ----------
Also what happens you you tried to use msm tool.

Bastafari said:
When in fastboot mode have you tried adb commands? First I would try fastboot devices and see if your device is listed. Then oem unlock. If that is successful try fastboot boot recover.img with the recovery of your choice. I suggest pitch black recovery.
Yes I have but when i type adb devices my phone is not showing up. heres the message in cmd-
C:\>adb reboot bootloader
error: device '(null)' not found
C:\>fastboot oem unlock-go
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.010s
Also what happens you you tried to use msm tool.
Click to expand...
Click to collapse
It flashes successfully but still gets stuck on Crashdump mode.
also apologies for late replay.

Ok so when youre, in recovery, try erasing data (type yes). Then reboot to fastboot and fastboot recovery again. Fish a rom and recovery again then reboot to system. But tell me what happens with msm tool. I've used it once or twice and if you don't do something correctly it doesn't work.

Related

Cannot flash another recovery please help

BACKGROUND INFO: I am trying to install color os rom using twrp recovery and it gives me "failed" when i flash it. I have heard that if you use CWM recovery it will work. i have installed TWRP recovery using toolbox that i downloaded from XDA. when i went back to toolbox to install CWM recovery it told me to boot into fastboot mode and I did. i also clicked attached devices under adb options and it gives my device number in CMD. when i select CWM recovery in toolbox and i hit flash it says make sure your device is in fastboot mode and i clicked ok. then it said within a few seconds your device will boot selected recovery and CMD pops up and it says FAILED. DEVICE NOT UNLOCKED CANNOT FLASH OR ERASE. i think this is because bootloader is locked but when i hit unlock boot loader in toolbox it says make sure your device is in fastboot mode and when i click ok, CMD pops for a second, then it closes and my device reboots immediately to TWRP recovery. also my device is ROOTED. i am able to install other ROMS such as mahdi and rom from OP. someone said that if i flash philz recovery.zip using TWRP recovery i will be able to install color os but still the same error. now i am stuck with philz recovery and i am unable to flash other recoveries. someone said that it is the oem lock and i went to CMD and typed fastoot oem unlock while my device was in fastboot mode and it said OK in cmd and the device booted right into philz recovery and still i am not able to flash another recovery. i went to CMD and typed fastboot oem device-info and it said device tempered- true, bootloader unlocked- false, charger screen enabled- false. I DONT KNOW IF ITS LOCKED BOOTLOADER, THAT I AM NOT ABLE TO UNLOCK, OR OEM LOCK, WHICH I TRIED TO UNLOCK AND IT SAID OK IN CMD, THAT IS NOT ENABLING ME TO FLASH BACK TO TWRP OR STOCK RECOVERY BECAUSE I HAVE MY ROM BACKUPS IN TWRP. PLEASE HELP ME TO GO BACK TO TWRP RECOVERY OR ANY RECOVERY.
Firstly, use paragraphs. Secondly, ditch the toolbox. Issue this fastboot command:
Code:
fastboot oem device-info
What's the output?
Transmitted via Bacon
timmaaa said:
Firstly, use paragraphs. Secondly, ditch the toolbox. Issue this fastboot command:
Code:
fastboot oem device-info
What's the output?
Transmitted via Bacon
Click to expand...
Click to collapse
device tempered- true, bootloader unlocked- false, charger screen enabled- false
Your bootloader is indeed locked. You can unlock it:
Code:
fastboot oem unlock
This will erase all user data on the device.
Transmitted via Bacon
timmaaa said:
Firstly, use paragraphs. Secondly, ditch the toolbox. Issue this fastboot command:
Code:
fastboot oem device-info
What's the output?
Transmitted via Bacon
Click to expand...
Click to collapse
Agreed with the paragraphs. OP did post the output of device-info in his OP post.
Calm down op, no need to use caps lock. Okay so anyways,
Do what timmaaa said, if that doesn't work try the following,
Do you have a copy of TWRP on your computer in the fastboot.exe folder? http://techerrata.com/browse/twrp2/bacon download 2.7.1.1
Go into fastboot mode, type in fastboot boot openrecovery-twrp-2.7.1.1-bacon.img
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
adb sideload that, then unlock your bootloader (fastboot oem unlock) in fastboot mode. then your phone will probably reboot, get into bootloader mode again then type fastboot flash recovery openrecovery-twrp-2.7.1.1-bacon.img and you will permanently flash twrp
timmaaa said:
Your bootloader is indeed locked. You can unlock it:
Code:
fastboot oem unlock
This will erase all user data on the device.
Transmitted via Bacon
Click to expand...
Click to collapse
i tried it nothing happens. the phone reboots into recovery and nothing erases. read my issue first. i already mentioned this. NOTHING HAPPENS WHEN I TYPE FASTBOOT OEM UNLOCK. IT SAYS OK. THEN THE PHONE BOOTS INTO RECOVERY AND NOTHING IS DELETED.
zephiK said:
Agreed with the paragraphs. OP did post the output of device-info in his OP post.
Calm down op, no need to use caps lock. Okay so anyways,
Do what timmaaa said, if that doesn't work try the following,
Do you have a copy of TWRP on your computer in the fastboot.exe folder? http://techerrata.com/browse/twrp2/bacon download 2.7.1.1
Go into fastboot mode, type in fastboot boot openrecovery-twrp-2.7.1.1-bacon.img
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
adb sideload that, then unlock your bootloader (fastboot oem unlock) in fastboot mode. then your phone will probably reboot, get into bootloader mode again then type fastboot flash recovery openrecovery-twrp-2.7.1.1-bacon.img and you will permanently flash twrp
Click to expand...
Click to collapse
when i flashed fastboot boot openrecovery-twrp-2.7.1.1-bacon.img it said ok in cmd and the device is still in fastboot mode and the logo of fastboot got more brighter. also what timaaaa said did not work. it said ok when i typed fastboot oem unlock in cmd and the device booted right to philz recovery and nothing got deleted.
zephiK said:
Agreed with the paragraphs. OP did post the output of device-info in his OP post.
Calm down op, no need to use caps lock. Okay so anyways,
Do what timmaaa said, if that doesn't work try the following,
Do you have a copy of TWRP on your computer in the fastboot.exe folder? http://techerrata.com/browse/twrp2/bacon download 2.7.1.1
Go into fastboot mode, type in fastboot boot openrecovery-twrp-2.7.1.1-bacon.img
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
adb sideload that, then unlock your bootloader (fastboot oem unlock) in fastboot mode. then your phone will probably reboot, get into bootloader mode again then type fastboot flash recovery openrecovery-twrp-2.7.1.1-bacon.img and you will permanently flash twrp
Click to expand...
Click to collapse
can you please explain me the steps in details. i downloaded 3 zip files that were in the link that you gave me. what should i do next? i found the steps confusing in the link.
My output is: device tempered- true, bootloader unlocked- true, charger screen enabled- false. Is it right? Thank you
MAX 94 said:
My output is: device tempered- true, bootloader unlocked- true, charger screen enabled- false. Is it right? Thank you
Click to expand...
Click to collapse
Yes. You are lucky dude. I can't unlock my bootloader.
So, I am the "lucky" one too
I did facktory reset and full wipe as I wanted to install back the CM11s, but I ended up in the "bricked" One :crying:
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
The command: fastboot oem unlock
Reset One to the TWRP, but it does not unlock it
Any falstboot command ends up with: Device not unlocked cannot flash or erase
I already playing with it over 20 hours, but I didnt find how to fix it
I had the same issue that could not unlock bootloader neither flash any room after brick. I used the computer downloaded color os and pushed it to my oneplus SD memory with cmd. But before that I installed twrp 2.7.1 in order to be able to flash os. The only rom was color os that I had success to install. Still bootloader not unlocked but color os rom has root privileged. But at least I have working phone. I installed twrp temporarily with toolkit from xda.
I succeeded to install the latest CyanogenMod 4.4.4. It is pain in the ass. But did it. Most implant is to unlock boot loader with flashing files from twrp. Then used toolkit and installed the rom and Chinese fastboot is gone.
[email protected] said:
I succeeded to install the latest CyanogenMod 4.4.4. It is pain in the ass. But did it. Most implant is to unlock boot loader with flashing files from twrp. Then used toolkit and installed the rom and Chinese fastboot is gone.
Click to expand...
Click to collapse
I have same problem as OP.
Code:
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.019s]
finished. total time: 0.019s
When i do "fastboot oem unlock" when my phone is in fastboot mode, the CMD tells me
Code:
E:\adt-bundle-windows\sdk\platform-tools>fastboot oem unlock
...
OKAY [ 0.005s]
finished. total time: 0.006s
E:\adt-bundle-windows\sdk\platform-tools>
Than he auto reboots into TWRP. I don't do anything there. I boot to android. I shut down. And I Boot to fastboot again. Than when i try to do a fastboot flash or boot he tells me "DEVICE NOT UNLOCKED cannot BOOT"
So every time i unlock it, he puts it immediatly in lock.
What to do?
Search for my post on the OnePlus.net forum...
And welcome to my 28 hours nightmare
djha53k said:
Search for my post on the OnePlus.net forum...
And welcome to my 28 hours nightmare
Click to expand...
Click to collapse
That's incredibly vague. If you really want to help you should provide a link.
Transmitted via Bacon
Sorry... the search for my nick on OnePlus forum gives you 5 results: https://forums.oneplus.net/search/2437238/?q=djha53k&o=relevance&c[node]=26
anyway here we go: https://forums.oneplus.net/threads/recovery.82350/page-8#post-6054985
edit: I wrote that post from bed at 12:55 AM on Tapatalk... and OnePlus forum is not there...
ever figured out how to fix this problem?
djha53k said:
So, I am the "lucky" one too
I did facktory reset and full wipe as I wanted to install back the CM11s, but I ended up in the "bricked" One :crying:
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
The command: fastboot oem unlock
Reset One to the TWRP, but it does not unlock it
Any falstboot command ends up with: Device not unlocked cannot flash or erase
I already playing with it over 20 hours, but I didnt find how to fix it
Click to expand...
Click to collapse
quackoman said:
ever figured out how to fix this problem?
Click to expand...
Click to collapse
Yes, long long loooooooooooooooooooooong time ago...
Suddenly the engl version of my post was already removed :crying:
I have only the czech version now
http://androidforum.cz/jak-opravit-chybu-device-not-unlocked-cannot-flash-or-erase-t59365.html
use google translator then :angel:
I fixed it by :starting up twrp... then I went to install and searched for the recovery (for me i had to go up a lvl and go to sdcard and it was the stock recovery.img)i wanted to flash but you have to chanege to images at the bottom left then I flashed it as recovery .. it failed then i flashed it as boot and then again as recovery and it worked then i reboted it i was promted with the normal recovery .. wiped data and applyd the oneplus ota update .. now it works grat and is fully unlocked IDK IF THAT WILL WORK FOR U OR EVEN HELP.... not responsible..

[A700] Booting failed

Hi to XDA comunity
... and happy festive season
I tried to install a new ROM. So, I followed tutorials and I have a huge problem
I passed to unlock the tablet
But, when I tried to install the new Recovery, the installation failed and now, the tablet doesn't want to boot
When I boot normaly, in recovery mode or Fastboot mode, I get this message :
Code:
Bootloader Version JB-653b3d3 (Unlock Mode)
Entering boot menu mode
Booting failed
Bootloader VJB-653b3d3(UnlockMode): Starting Fastboot USB download protocol
When I send "Fastboot device", the device is shown
When I send "Fastboot flash recovery twrp-2.6.3.0_a700.img"
Code:
sending 'recovert' <5736 KB>...
But still indefinitely
So I stop and retry and I obtain
downloading 'boot.img'...
FAILED <commande write failed <Unknow error>>
finished. total time: 0.???s
i tried to erase recovery and retry.
Tried with several USB cables.
I don't know what to do...
I guess it's a fastboot problem ? How can I found a fastboot file ?
Thanks for any help !
grimnnir said:
Hi to XDA comunity
... and happy festive season
I tried to install a new ROM. So, I followed tutorials and I have a huge problem
I passed to unlock the tablet
But, when I tried to install the new Recovery, the installation failed and now, the tablet doesn't want to boot
When I boot normaly, in recovery mode or Fastboot mode, I get this message :
Code:
Bootloader Version JB-653b3d3 (Unlock Mode)
Entering boot menu mode
Booting failed
Bootloader VJB-653b3d3(UnlockMode): Starting Fastboot USB download protocol
When I send "Fastboot device", the device is shown
When I send "Fastboot flash recovery twrp-2.6.3.0_a700.img"
Code:
sending 'recovert' <5736 KB>...
But still indefinitely
So I stop and retry and I obtain
downloading 'boot.img'...
FAILED <commande write failed <Unknow error>>
finished. total time: 0.???s
i tried to erase recovery and retry.
Tried with several USB cables.
I don't know what to do...
I guess it's a fastboot problem ? How can I found a fastboot file ?
Thanks for any help !
Click to expand...
Click to collapse
make sure you have the a700 and not the a701 or a510 etc etc....
also, you could try booting directly into fastboot:
1. power off
2. hold power and volume down, while you're doing that, constantly change the rotation switch from lock unlock lock unlock.... keep doing it for about 5 seconds
try flashing from here... it might give you the same result but worth a try.
other possible problems:
1. the recovery you downloaded is corrupt
2. the recovery you downloaded was not a working version
3. you might not have the right usb drivers installed
4. you might have used the wrong recovery commands
5. command (sometimes) needs to be Run as Administrator on Windows (right click)
6. you might have waited too long to reboot to recovery, or used the wrong method to do it
it might make it easier for you if you just rename recovery on computer to recovery.img (so you can just type fastboot flash recovery recovery.img)
also, I have uploaded a copy of the recovery I'm using (it's newer)
you can also try (while in fastboot)
Code:
fastboot boot twrp.img
(or any custom recovery)
It should boot without flashing, and from there you're will be able to flash firmware, ROM, etc...
Shreps said:
you can also try (while in fastboot)
Code:
fastboot boot twrp.img
(or any custom recovery)
It should boot without flashing, and from there you're will be able to flash firmware, ROM, etc...
Click to expand...
Click to collapse
it might be fine but personally I would not try that... recovery and boot are not to be confused and bootloaders are not to be messed with

Bricked for life? Partition error?

Hello!
I have a small problem. A week ago died my phone when i unlocked the lockscreen one evening. Thought that the battery was empty, i put it on the charger and started up the phone a few hours later and the only thing that happens is that Google logo is displayed, then it starts over again. I can go into recovery and fastboot, but it does not matter what i do there. Managed to get it to be connected as a USB drive so I got out the pictures from it. But if you make a complete factory reset including data and restarts there everything left! Tried to run "fastboot format cashe" but it only return "FAILED (remote: flash write failure) "
The phone is rooted and bootloader is unlocked, i had a custom rom installed, and it had worked since beginning of summer.
Have you already tried to reflash stock rom with fastboot? Maybe that will help to get your partitions working properly...
i followed a guide on androidrootz dot com, "how-to-unroot-nexus-5-complete-stock" but directly when i try to flash bootloader i get a error message.
Does the bootloader remain unlocked? What error are you getting when flashing stock?
audit13 said:
Does the bootloader remain unlocked? What error are you getting when flashing stock?
Click to expand...
Click to collapse
Yes! It remains unlocked! Heres the "print screen"
C:\UnrootNexus5>fastboot flash bootloader-hammerhead-HHZ11d.img
unknown partition 'bootloader-hammerhead-HHZ11d.img'
error: cannot determine image filename for 'bootloader-hammerhead-HHZ11d.img'
You could try Wug's Nexus Root Toolkit and get it back to working. If you can get to fastboot screen, then it can get you up and running again.
You'll have to google it, for some reason I got set back to a new user, even though I've been posting on this forum for quite awhile.
g90814 said:
You could try Wug's Nexus Root Toolkit and get it back to working. If you can get to fastboot screen, then it can get you up and running again.
You'll have to google it, for some reason I got set back to a new user, even though I've been posting on this forum for quite awhile.
Click to expand...
Click to collapse
I Have tried that also, here is the print from that:
Connectivity Status: Fastboot Device Connected
Flashing bootloader-hammerhead-HHZ11d.img to BOOTLOADER partition...
fastboot flash bootloader "C:\UnrootNexus5\bootloader-hammerhead-HHZ11d.img"
Rebooting your device into bootloader mode...
fastboot reboot-bootloader
But when it boots up again its still unlocked...
fastboot flash bootloader bootloader.img
Oh! I missed one word. Will try it tonight!
Nope.... Doesnt work either....
C:\UnrootNexus5>fastboot flash bootloader bootloader-hammerhead-HHZ11d.img
target reported max download size of 1073741824 bytes
sending 'bootloader' (2506 KB)...
OKAY [ 0.256s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.457s
Looks like the onboard memory chip is damaged or has failed.
My N5's bootloader would always relock on reboot so I could never flash a stock ROM.
i don't think you have unlocked bootloader , maybe there is some errors try with "fastboot oem unlock" and then try to flash everything
audit13 said:
Looks like the onboard memory chip is damaged or has failed.
My N5's bootloader would always relock on reboot so I could never flash a stock ROM.
Click to expand...
Click to collapse
Damn! thats what im afraid of....
ChocholateMaster said:
i don't think you have unlocked bootloader , maybe there is some errors try with "fastboot oem unlock" and then try to flash everything
Click to expand...
Click to collapse
The telephone is unlocked, the lock is open when i reboot the phone.
C:\UnrootNexus5>fastboot oem unlock
...
FAILED (remote: Already Unlocked)
finished. total time: 0.002s
what if you try "fastboot oem lock" and then again unlock it maybe will work
and @audit13 to get chip damaged? i'm not saying that is not possible but it's only few percent
oh and can you enter in recovery mode? if as you said yes firstly try to flash this http://d-h.st/VcCv
I don't know how it got damaged. One day, ti started bootlooping and the bootloader had re-locked on its own even though I unlocked it straight out of the box. I booted into fastboot, unlocked the bootloader, and it only too a few seconds to erase everything. I immediately rebooted in fastboot and the bootloader was locked again. This unlock/relock happened over and over.
I booted into recovery and tried a factory reset but recovery could not mount cache or data to perform the erase.
My phone just kept getting stuck at the Google logo or bootlooping.
ChocholateMaster said:
what if you try "fastboot oem lock" and then again unlock it maybe will work
and @audit13 to get chip damaged? i'm not saying that is not possible but it's only few percent
oh and can you enter in recovery mode? if as you said yes firstly try to flash this http://d-h.st/VcCv
Click to expand...
Click to collapse
I have tried that also, when im just type "FASTBOOT OEM LOCK" it lookes like this:
C:\UnrootNexus5>fastboot oem lock
...
OKAY [ 0.054s]
finished. total time: 0.054s
PERFECT!?!? But when i reboot its still unlocked.... if i do first lock, then unlock without rebooting, i get a new meny on the phone where i have to chose if i want to unlock my device. and if i chose yes it will reboot and its the same again....
How do i download that file??? I just got an EXE file, and i dont want to run that!
If it's not sticking on a reboot, that means the memory is most likely gone bad. I guess you could try using the diagnostic tool, which would confirm if the memory is bad.
http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
maybe it's just corupted bootloader @kardanmannen go to http://d-h.st/VcCv and press download now you should get .zip file which you can flash in recovery using adb sideload
---------- Post added at 03:41 PM ---------- Previous post was at 03:39 PM ----------
ChocholateMaster said:
maybe it's just corupted bootloader @kardanmannen go to http://d-h.st/VcCv and press download now you should get .zip file which you can flash in recovery using adb sideload
Click to expand...
Click to collapse
after flashing it can take up to 15 mins to turn on because of first boot
@kardanmannen any news?
I'm getting more and more sure that the memorymodule is faulty in the phone. If you reboot in Recovery and select filemanager, for example you remove a directory with files, if you restart the phone, the directory is there again! And when you start it up in recovery and connect it to the computer, theres a few directorys you can write/delete/. Similarly, if you run "fastboot oem lock" and reboot it, its locked the first time it is started up and then the second time it is unlocked again.
Lost hope a little there and went off and ordered a Nexus 6P, hoping it will arrive on Wednesday.

Honor 6 bricked.Is there any hope?

HI all, i own a Honor 6 L02 and i have the following brick problems.
1. in normal boot i get RESCUE MODE error! func no9 func_boot_kernel
2.when i try to boot in recovery i get RESCUE MODE error no 10 func_boot_recovery
3when i try 3 buttons i get the same as no2
4.when i try fastboot(my phone is unlocked) i cannot flash ANYTHING from pc because i get failed remote command not allowed.
which i think is the major problem
I think it all initiated when i was in 532 lollipop and flashed wrong recovery(recovery for L04) in order to flash superuser which i did and everything was okay indeed.Until i wanted to move back to 316 stable kitkat, but i couldnot flash stock recovery because of the fail command not alowed,so i Installed Flashify ,flashed TWRP and then tried to flash image through twrp.
After rebooting i got bricked.ANY solutions?
Nobody can suggest a solution ? smth to begin from?
pudup said:
Is your bootloader unlocked? If so then the fastboot commands should work. Does your phone show up when you type "fastboot devices"?
If all fastboot still doesn't work, try updating the drivers. Download the latest multi tool and use that. Just flash a stock rom with multi tool or flash all the individual img files with fastboot manually.
Click to expand...
Click to collapse
Thanks for the reply.My bootloader says phone unlocked ,so i supposse it is.My phone shows up when i type fastboot devices.
Im using the latest multitool (and also tried different versions) and have installed the drivers on a fresh formatted windows 8.1 laptop!
the disaster problem is that i cannot flash ANYTHING with fastboot flash commands.For example:
sending recovery okay
writing recovery Failed error remote command not allowed.im getting this error with every single image file(boot,cust , system,recovery stock or custom)
pudup said:
Can you try locking your bootloader? Lock your bootloader and then switch off. Then unlock it and try flashing a recovery.
Also try this command after placing, let's say the twrp.img file for kitkat, in the fastboot folder.
"fastboot boot twrp.img"
That boots directly into twrp without flashing it. See if that works.
Click to expand...
Click to collapse
This is what i get when i try to relock bootloader
* daemon not runnig.starting it now on port 5037
daemon started successfully
T2FDU1482900...... fastboot
...
Failed (remote:stat not match)
finished total time 0.003
If i try to unlock it (although it s written phone unlocked) i get
FAILED ( remoteassword wrong)
shouldnt i get smth like bootloader already unlocked?
The weird thing is im 100% sure that im using the correct bootloader password because i have gotten
it from 3 different sources(local huawei,chinese site huawei a year ago, and the tool a guy has posted here on xda)
Last i have copied twrp.img in the folder and tried the command
fastboot boot twrp.img
downloading 'boot.img'
OKAY [1.047s]
booting...
FAILED(remote:command not allowed)
Thank you for your help,i appreciate it
Using fastboot flash your rom recovery again and your rom recovery
---------- Post added at 07:59 PM ---------- Previous post was at 07:55 PM ----------
dimikon said:
This is what i get when i try to relock bootloader
* daemon not runnig.starting it now on port 5037
daemon started successfully
T2FDU1482900...... fastboot
...
Failed (remote:stat not match)
finished total time 0.003
If i try to unlock it (although it s written phone unlocked) i get
FAILED ( remoteassword wrong)
shouldnt i get smth like bootloader already unlocked?
The weird thing is im 100% sure that im using the correct bootloader password because i have gotten
it from 3 different sources(local huawei,chinese site huawei a year ago, and the tool a guy has posted here on xda)
Last i have copied twrp.img in the folder and tried the command
fastboot boot twrp.img
downloading 'boot.img'
OKAY [1.047s]
booting...
FAILED(remote:command not allowed)
Thank you for your help,i appreciate it
Click to expand...
Click to collapse
you flash TWRP RECOVERY in your BOOT partition it is Wrong
in fast boot do that
for Boot.img (your rom num)
fastboot flash boot boot.img
for recovery (your rom num)
fastboot flash recovery recovery.img
adhamamar said:
Using fastboot flash your rom recovery again and your rom recovery
---------- Post added at 07:59 PM ---------- Previous post was at 07:55 PM ----------
you flash TWRP RECOVERY in your BOOT partition it is Wrong
in fast boot do that
for Boot.img (your rom num)
fastboot flash boot boot.img
for recovery (your rom num)
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
My friend,,, every image i try to flash via fastboot (recovery,boot,system,cust) gives me FAILED error:remote command not allowed
what i did with the twrp.img was the thing that the other guy advised to see if it would work
do you have a TWRP backup of your rom? if yes try restore it ....
if not
Search on this site for TWRP backup for your build num and Change the serial number for the backup copy with your phone serial number (folder name and change inside recovery.log file) (http://4pda.ru/forum/index.php?showtopic=671958&st=920)
adhamamar said:
do you have a TWRP backup of your rom? if yes try restore it ....
if not
Search on this site for TWRP backup for your build num and Change the serial number for the backup copy with your phone serial number (folder name and change inside recovery.log file) (http://4pda.ru/forum/index.php?showtopic=671958&st=920)
Click to expand...
Click to collapse
Thank you very much , but how will i be able to restore it ??? i cannot boot into recovery ,i get error no FUNC_BOOT_RECOVERY
read this http://forum.xda-developers.com/showpost.php?p=56662843&postcount=2945
adhamamar said:
read this http://forum.xda-developers.com/showpost.php?p=56662843&postcount=2945
Click to expand...
Click to collapse
No luck,what this tool does is similar to the multitool unbrick,just tries to flash the images in an automated way,and gives me the
FAILED error remote command not allowed
pudup said:
Sorry but it seems your phone is hard bricked. Take it to a service center.
The "command not allowed" error usually comes up for locked bootloaders or in some cases when usb debugging is not switched on. There is nothing i can think of right now for you to do.
I suggest you lie to the people at the service center and tell them this happened while you were doing a normal update that was given to you OTA.
Click to expand...
Click to collapse
what do you think would be the cost for repairing? i have asked at the local Huawei but they wont repair it because it is not bought from E.U. ,is there any chance that somebody would repair it without sending it back to china(after all guarantee is lost ,i own it for 1,5 years)

I dont know how....(XT1952-6)

I am just glad it wasn't my everyday phone..I am new to the whole "rooting" process, i was trying it on my old moto g(7) play XT1952-6, and i wasn't have very much luck, i finally was able to fash it and tried to install a custom rom, when my phone rebooted it is now stuck on fastboot mode and my bootloader is now locked again...It is showing different specs on the device now also, when i looked it up it in reading as an M92 Desktop (ThinkCenter) type 2119ABF...I can no longer turn the device on and with the bootloader locked i can not flash again..the (LMSA) is not able to rescue it either...is there anything i can do to fix it?
can you enter fastboot?
wojtess said:
can you enter fastboot?
Click to expand...
Click to collapse
the phone itself is stuck in fastboot, it doesnt go into anything else...i had already unlocked the bootloader and enabled the usb settings but it locked everything up again..
Try this
Code:
mfastboot devices
mfastboot reboot
to exit Fastboot mode.
http://downloadmirror.co/android/29Sh/mfastboot-v2.zip
jwoegerbauer said:
Try this
Code:
mfastboot devices
mfastboot reboot
to exit Fastboot mode.
http://downloadmirror.co/android/29Sh/mfastboot-v2.zip
Click to expand...
Click to collapse
i tried this and didnt work...my phone does say "fastboot reason: failed to initialize partition table..

Categories

Resources