[SOLVED] Bricked OnePlus 7pro GM1917 - MSMtool Error - OnePlus 7 Pro Guides, News, & Discussion

So I bricked my phone attempting to flash twrp. Dowloaded msmtool, installed the driver so it would show up, and it does. Downloaded what I believe in the proper firmware package, but when I hit start, i only runs for a few seconds before erroring out saying "Sahara Communication Failed, please try again after power off phone"...I've tried several times, with different cords, usb port, etc. Please Help !

CrimsinXIII said:
So I bricked my phone attempting to flash twrp. Dowloaded msmtool, installed the driver so it would show up, and it does. Downloaded what I believe in the proper firmware package, but when I hit start, i only runs for a few seconds before erroring out saying "Sahara Communication Failed, please try again after power off phone"...I've tried several times, with different cords, usb port, etc. Please Help !
Click to expand...
Click to collapse
You could try to do what the error message says. Press and hold the phone Power button right after clicking the app Start button. Or you could try to press and hold Vol+ and Power buttons together (up to 30 sec) while in the app seeing this error message. Release the buttons when the status column commence changing.

I definitely did try that, figured it might be worth a shot, cuz I mean the program itself telling me to do so was good motivation. Alas, no luck. I did fix it tho, so thank you for your attempt at help (?)

@CrimsinXIII
How did you fixed it?

I don't ever use the power button to get into EDL mode, just both the volume buttons

Related

Stuck in bootloop after downgrade

Hi all
As the title states my phone appears to be stuck in a boot loop of sorts.
So I loaded the German V20N via KDZ updater last week and that worked perfectly.
I decided I wanted to use Zeus v2.1 by Huexxx, but I needed a rooted device for this.
So I put the phone into update mode by pressing vol+ and power button.
I then used KDZ updater once again using V10B. This also appeared to update fine.
However when the phone finally booted up I got many many errors of:
"process system root is not responding".
I tried to force close them but to no avail, so I removed the battery.
I powered the phone on yet again and then it shows the LG logo then reboots possibly a few times.
After that it eventually lands up showing the Unlock screen but the touch keys at the bottom are flashing. It will then reboot again and do the same thing.
I tried removing the battery pressing vol+ and power and then plugging it into the USB to get the software update mode. However the phone just turns on instead of showing the update screen.
I have also tried pressing vol- and power. It also just appears to turn the phone on.
Other errors received are:
"The process android.process.acore has stopped unexpectedly. Please try again"
The errors pop up and and eventually the phone will hang and restart before I can actually do anything on it.
The computer doesn't seem to pick up anything when it's plugged into the USB either
http://forum.xda-developers.com/showthread.php?t=1448803
I did see that thread, but I was under the impression that because I could not get to the software update mode that it wouldn't work.
As it turns out... You must not press vol+ and power when plugging into usb. Just the vol+ key.
Will let you know if it works via SmartFlashTool.
Thanks
Feel rather silly now...
It seems to be working!
Hopefully I will not screw it up again.

Error message when starting

was with the original rom lg. and then went instalr the recovery of the cyanogen rom manager app, and then hung up the phone and now the message appears in red at the top of the screen
"Critical Failure: Unable to start Kernel.
Unrecoverable bootloader error (0x00000002)"
and I can not get into download mode to install the original rom again.
and now what do I do? I lost my phone?
you flashed cwm without unlocking your bootloader. re-flash latest jellybean kdz file for your phone using http://forum.xda-developers.com/showthread.php?t=2069723, then read some more about unlocking bootloader, and then start again.
Flying_Bear said:
you flashed cwm without unlocking your bootloader. re-flash latest jellybean kdz file for your phone using http://forum.xda-developers.com/showthread.php?t=2069723, then read some more about unlocking bootloader, and then start again.
Click to expand...
Click to collapse
but now I am unable to get into download mode on the phone. is
" Now just hold down vol - key ( hold hold hold dont release !!!! ) and plug the USB cable until you get screen like this :-"
he does not. whenever I do this it only vibrates strong and goes to the screen with the error message. I do not know why that. remember one time it happened to me already but can not remember how I resolved it is possible to even lose the download mode?
Its not possible afaik. Are you sure you are holding only vol - key and plugging in? Dont hold power key!
yes, I'm almost the whole day trying to get into download mode by pressing volume down + connecting the usb. and whenever it vibrates strong and hangs on lg logo. tried to volume up + usb connect. and no download mode. I'm going crazy with this phone. otherwise hesitate to hard reset? or other shortcut to download mode?
Rafael20. said:
yes, I'm almost the whole day trying to get into download mode by pressing volume down + connecting the usb. and whenever it vibrates strong and hangs on lg logo. tried to volume up + usb connect. and no download mode. I'm going crazy with this phone. otherwise hesitate to hard reset? or other shortcut to download mode?
Click to expand...
Click to collapse
hard reset wont help you, as far as i know, you somehow need to enter s/w upgrade screen. did you try it with battery out?
he battery of the same error, and no battery it does nothing, or vibrate, or flash screen, nothing happens
Will I not be able to see my optimus running again? :crying:
it is not possible to load the kernel, what could I do?
Critical Failure: Unable to start Kernel. Unrecoverable bootloader error (0x00000002)
Rafael20. said:
it is not possible to load the kernel, what could I do?
Click to expand...
Click to collapse
Hi Raphael20 and everyone else,
Did you manage to figure out a solution to this? I have the same issue, i.e. cannot start my phone by holding the power button. Not even when people suggest to get to the S/W Update screen by holding the Volume down + plug into the computer.
I got to this error when I tried to do a factory reset. I installed the ClockworkMod Recovery. Then the factory reset via Volume up + Power button gave me the "Critical Failure: Unable to start Kernel" error. I somehow managed to get access to my phone by holding the Volume down + plug into the computer. Then tried to do a factory reset via the system settings of my phone. My phone restarted and then gave me the "Critical Failure: Unable to start Kernel" screen of death! Now Volume down + plug into the computer gives me the "Critical Failure: Unable to start Kernel", no matter whether I have restarted my computer and I have tried another computer. It seems that the bootloader is wrecked.
Does anyone have any suggestions?
Thanks!

Can't unbrick my Lenovo K3 Note (K50-t5)

Dear XDA-members,
please try helping me with my problem before redirecting me to some tutorials. I think I already tried all of them and I even opened a thread in a german forum... noone could solve my problem there, yet.
Here's the deal:
-Bootloop in starting screen
-Stock recovery freezes to on boot
-Vol- and Power leads to "Have been in meta mode, long press the power button and the normal boot"
-Yes, I used the new drivers, SP Flash tool and several ROM's
-Yes I disabled driver signature verification
- In SP Flash Tool I checked "DA DL All"
- My OS is Win10x64
If I load a scatter and press "Download" there appears a red bar with "Download DA 100%" followed by "S_FT_DOWNLOAD_FAIL (4008)". I used Google to solve the problem but no succes...
SO if I try "Firmware Upgrade or Format All", the red bar changes to "Format 0%" followed by "BROM ERROR : S_FT_FORMAT_FAIL (4010)".
By now I tryed 3 different PC's and 2 cables. My father's K3 Note could be flashed without any problems on this PC's.
I hope someone can help me please.
DaimonTay said:
Dear XDA-members,
please try helping me with my problem before redirecting me to some tutorials. I think I already tried all of them and I even opened a thread in a german forum... noone could solve my problem there, yet.
Here's the deal:
-Bootloop in starting screen
-Stock recovery freezes to on boot
-Vol- and Power leads to "Have been in meta mode, long press the power button and the normal boot"
-Yes, I used the new drivers, SP Flash tool and several ROM's
-Yes I disabled driver signature verification
- In SP Flash Tool I checked "DA DL All"
- My OS is Win10x64
If I load a scatter and press "Download" there appears a red bar with "Download DA 100%" followed by "S_FT_DOWNLOAD_FAIL (4008)". I used Google to solve the problem but no succes...
SO if I try "Firmware Upgrade or Format All", the red bar changes to "Format 0%" followed by "BROM ERROR : S_FT_FORMAT_FAIL (4010)".
By now I tryed 3 different PC's and 2 cables. My father's K3 Note could be flashed without any problems on this PC's.
I hope someone can help me please.
Click to expand...
Click to collapse
Can't say proper..
But have you tried "adb"..?
adikri said:
Can't say proper..
But have you tried "adb"..?
Click to expand...
Click to collapse
I tried adb flashtool but it doesn't find device...
Nonetheless the phone is recognised by the PC itself.
DaimonTay said:
I tried adb flashtool but it doesn't find device...
Nonetheless the phone is recognised by the PC itself.
Click to expand...
Click to collapse
Is anything related to phone or android showing in windows device manager..?
If not then maybe driver problem..
And even after falshing ptocedure its say "factory mode" then maybe it'll light up by adb command..
adikri said:
Is anything related to phone or android showing in windows device manager..?
If not then maybe driver problem..
And even after falshing ptocedure its say "factory mode" then maybe it'll light up by adb command..
Click to expand...
Click to collapse
Device-Manager shows "Portable Devices>MTP-USB-Device".
I don't believe it's a driver problem because I installed so many of them already and I had the same errors in SP Flash Tool everytime.
When I type "adb devices" in adb flashtool there are no devices shown, though it recognises my other smartphone.
DaimonTay said:
Device-Manager shows "Portable Devices>MTP-USB-Device".
I don't believe it's a driver problem because I installed so many of them already and I had the same errors in SP Flash Tool everytime.
When I type "adb devices" in adb flashtool there are no devices shown, though it recognises my other smartphone.
Click to expand...
Click to collapse
I know this is not the topic but maybe atlesst you can read it..
So after doing the first trick of putting the Lenovo S880 into safe mode (or meta mode?), I tried pressing the Volume Up button. But it’s not working. This time I tried pressing the "Power button and the Volume Up button" and to my surprise a menu suddenly appears. It’s the Factory Mode screen menu of the Lenovo S880!
To cut it short, you should choose ‘Clear eMMC’ to reset your Lenovo S880. You can do this by pressing the Volume Up button to navigate the menu. After choosing the ‘Clear eMMC’ option, press the Volume Down button to perform software reset on the Lenovo S880. It will be quick and short erasing the internal memory of your smartphone and will reboot automatically. After the reboot, the annoying ‘locked’ unlock screen will disappear.
adikri said:
I know this is not the topic but maybe atlesst you can read it..
So after doing the first trick of putting the Lenovo S880 into safe mode (or meta mode?), I tried pressing the Volume Up button. But it’s not working. This time I tried pressing the "Power button and the Volume Up button" and to my surprise a menu suddenly appears. It’s the Factory Mode screen menu of the Lenovo S880!
To cut it short, you should choose ‘Clear eMMC’ to reset your Lenovo S880. You can do this by pressing the Volume Up button to navigate the menu. After choosing the ‘Clear eMMC’ option, press the Volume Down button to perform software reset on the Lenovo S880. It will be quick and short erasing the internal memory of your smartphone and will reboot automatically. After the reboot, the annoying ‘locked’ unlock screen will disappear.
Click to expand...
Click to collapse
Thanks for your effort.
When I press Vol+ nothing happens. Vol+ and Power leads to the meta mode I think (smth in chinese and "Have been in meta mode, long press the power button and the normal boot" appears) as I already mentioned. When I press Vol+ or Vol+ and Power again either nothing happens or the Phone turns off again.
I can't even get into recovery mode becaus my phone freezes at "K3 recovery" screen.

Brick/Bootloop Huawei P8 Lite 2017

Hello everyone, I saw a few posts on this forum about other bricked phones, but my case is different (if its not then please link me the thread, Thanks).
Story: Today I decided that my unrooted phone wasn't enough for me, so I said: "Why not root?" . I have to add that I owned a LG Magna 3G before this Huawei P8 LIte 2017 and oh boi was the rooting procedure WAY HARDER(the huawei procedure)... I did well with my LG, but not so well with my Huawei. To be honest I was almost done but because I couldnt boot into TWRP, I decided to follow a guide I cant find cause I followed so many that my History is a mess (if anyone requests I will do some digging though). The guy suggested to someone that couldnt boot into TWRP (like me) that he should falsh TWRP>relock his OEM>Shutdown>Press a combination to go into recovery mode>???>Profit. I did just that but my device is now a 180 Euro brick.
Probelm: My device bootloops. Every time I shut it down (hold power key for 10sec), it reboots and gets stuck on the famous "Your device has been locked and can't be trusted. To learn more, BLAH BLAH BLAH. Your device is booting now...
I tried several key combinations, but whatever I do, when I hold my power key for 10sec, The huawei logo pops up for a second or two and then I get stuck on this screen again...
Sadly, I seem to have no connection between my PC and my device (adb can't find any connected device).
I also want to add that, after I was promted to relock my OEM, I removed the USB cable whoopsie.
What Im looking for:
A way to regain contact between my PC (adb) and my phone
A way to shutdown my device for now (and not forever... just for the night)
Someone to tell me that he had the same issue and took the following steps (Need clear answers and steps)
Anything else whatsoever
I don't think it's necessary to provide the files I used, since the reason my device is like this is because of my own stupidity:silly:
Thank you for your time.
You have to hold Power and Volume Up button pressed to boot into erecovery, not only power, check it.
grgzz said:
You have to hold Power and Volume Up button pressed to boot into erecovery, not only power, check it.
Click to expand...
Click to collapse
Sorry for replying after 2 hours, I didn't get a notification.
I tried:
1. Holding the buttons until I see the "your device is booting..." message
2.Holding the buttons until it vibrates
3.Holding the buttons until I see the Huawei logo
Thanks for your time anyway
You press Volume Up + Power simultaneously, when you see the Huawei logo you release Power and hold Volume Up only until it boots to erecovery.
grgzz said:
You press Volume Up + Power simultaneously, when you see the Huawei logo you release Power and hold Volume Up only until it boots to erecovery.
Click to expand...
Click to collapse
Tried this several times, no result.
Is there a more drastic solution to my stubborn phone?
Aneom7331 said:
Tried this several times, no result.
Is there a more drastic solution to my stubborn phone?
Click to expand...
Click to collapse
The most drastic solution is the DC Phoenix software, not for free, if i am right they ask 15€ for 72 hours.
Not going to bother with this one tho... if I am very desperate, I might try to "borrow" it, but Im gonna seek other solutions until then.
Thanks for your time
On the "your device has been unlocked" hold the Volume up button until you boot to eRecovery. From there connect to wifi and restore stock rom. Afaik, erecovery should boot on bootlooped device. Give it a try
If this doesnt work, plug in to pc, and hold volume up + power, on huawei logo leave power button and hold volume up until you get to erecovery
aciupapa said:
On the "your device has been unlocked" hold the Volume up button until you boot to eRecovery. From there connect to wifi and restore stock rom. Afaik, erecovery should boot on bootlooped device. Give it a try
If this doesnt work, plug in to pc, and hold volume up + power, on huawei logo leave power button and hold volume up until you get to erecovery
Click to expand...
Click to collapse
Hello, thanks for replying
My device is now good, only gapps are missing but I don't care too much. Here is what happened:
So, I left my phone unplugged from any power source during the night (meanwhile the screen couldn't turn off), although I swear I did this 20 times already, when I booted my device after I came back from my University, my phone booted into eRecovery... I downloaded the latest package and it seems to work just fine now, the only problem is that the gapps need to be flased via TWRP (that I don't think I have anymore, how ironic).
Thanks to all of you who cared about giving me a solution :victory: Have a fantastic day
If you want to have a complete working system, i suggest you to try to update using erecovery again. It should download full firmware with gapps etc
Aneom7331 said:
Hello, thanks for replying
My device is now good, only gapps are missing but I don't care too much. Here is what happened:
So, I left my phone unplugged from any power source during the night (meanwhile the screen couldn't turn off), although I swear I did this 20 times already, when I booted my device after I came back from my University, my phone booted into eRecovery... I downloaded the latest package and it seems to work just fine now, the only problem is that the gapps need to be flased via TWRP (that I don't think I have anymore, how ironic).
Thanks to all of you who cared about giving me a solution :victory: Have a fantastic day
Click to expand...
Click to collapse
aciupapa said:
If you want to have a complete working system, i suggest you to try to update using erecovery again. It should download full firmware with gapps etc
Click to expand...
Click to collapse
Well, that was what we told you to do at first time. Erecovery can bring it back to life easily. Now as you have already been told erecovery flashes the complete firmware, including gapps.
You can also try to update it through the settings menu, in the system update settings you press the three dots menu on the upper right corner and select download latest complete package.
grgzz said:
Well, that was what we told you to do at first time. Erecovery can bring it back to life easily. Now as you have already been told erecovery flashes the complete firmware, including gapps.
You can also try to update it through the settings menu, in the system update settings you press the three dots menu on the upper right corner and select download latest complete package.
Click to expand...
Click to collapse
I know you told me first but, the difference was that, my phone had to ran out of battery to do this. In the end of my last reply I said thanks to all of you who cared, including you, you cared the most actualy
Aneom7331 said:
I know you told me first but, the difference was that, my phone had to ran out of battery to do this. In the end of my last reply I said thanks to all of you who cared, including you, you cared the most actualy
Click to expand...
Click to collapse
Well, at least it works now.

Could not do normal boot. Invalid KERNEL LENGTH.

This message I get when I try to power up my Note 9 N960F/DS.
I got it this way: Been running the same ROM for 2 years. Time to upgrade. Upgraded TWRP via the app. After downloading the ROM image to SD card, I tapped an app called Reboot, with the Recovery option. I suspect this app is from some old installation, and ended up on this unit via data restore. Now all I get is this message on a black screen. No logo, nothing. Message flashes once. If I plug into PC, message flashes repeatedly. Cannot boot to recovery using Vol-+Pwr, Vol++Pwr ineffective.
I suspect I bricked the phone, but I seem to remember once breaking out of this 2 years back, I think. Any ideas, clues, anything?
Try this, power off phone. Press volume up and bixby button and while pressing buttons insert data cable, phone should go to downlaod mode. OPen odin and flash stock firmware.
OK, tried it, display showed the same message until I released the buttons, then flashed the message every 4 seconds until disconnected.
OK, got it into download mode, reflashed twrp, now it's in a boot loop. Will continue working this.
It took a few tries, but I not only got everything working, I restored my data backup and upgraded to Android 10. Thanks all!
Munawar Mehmood said:
Try this, power off phone. Press volume up and bixby button and while pressing buttons insert data cable, phone should go to downlaod mode. OPen odin and flash stock firmware.
Click to expand...
Click to collapse
Thanks so much for this,you saved me.
hello, how about if my buttons arent working?
please help
tristemono said:
OK, got it into download mode, reflashed twrp, now it's in a boot loop. Will continue working this.
Click to expand...
Click to collapse
HOW DID YOU DO THIS, I HAVE THE EXACT SAME ISSUE AND AFTER HOURS OF SEARCHING YOU'RE THE ONLY OTHER PERSON WHO'S HAD THIS ISSSUE. PLEASE HELP, I CANNOT GET INTO DOWNLOAD MODE NO MATTER WHAT I DO

Categories

Resources