Related
Hi,
My H815 always suffered from this problem: http://forum.xda-developers.com/g4/help/fastboot-download-mode-problem-t3466649 - the only way I could have fastboot was from an adb shell.
Well, that was not a problem until today: CM14's nightly broke (booting just loops at the moving logo) and now I have no way to go back to fastboot. And if I try the recovery mode, I just have a blurry circle saying "erasing" for a few seconds, then a looping CM logo.
Anyone has a way out of this mess ?
bestouff said:
Hi,
My H815 always suffered from this problem: http://forum.xda-developers.com/g4/help/fastboot-download-mode-problem-t3466649 - the only way I could have fastboot was from an adb shell.
Well, that was not a problem until today: CM14's nightly broke (booting just loops at the moving logo) and now I have no way to go back to fastboot. And if I try the recovery mode, I just have a blurry circle saying "erasing" for a few seconds, then a looping CM logo.
Anyone has a way out of this mess ?
Click to expand...
Click to collapse
When you say you try the recovery mode how do you try to get into it? Btw do you have twrp installed?
Same thing happened to me, tried to install, just got put straight back in to TWRP after boot. Tried installing a stock ROM, CM ROM & using LG Bridge to recover, to no avail. Help appreciated, (i'm assuming LGUP is going to come up a lot)
Tycoon282 said:
Same thing happened to me, tried to install, just got put straight back in to TWRP after boot. Tried installing a stock ROM, CM ROM & using LG Bridge to recover, to no avail. Help appreciated, (i'm assuming LGUP is going to come up a lot)
Click to expand...
Click to collapse
The OP has another issue pls do not hijack.
steadfasterX said:
The OP has another issue pls do not hijack.
Click to expand...
Click to collapse
Sorry, it's nearly the same issue though, CM14.1 broke phones today.
Today's update broke mine as well. Looking for solutions. Will follow your thread and progress.
Same for me. Tried download mode with lgup to flash stock which worked once - but I kind of bricked it again by trying to install cm14.1 again. Then i tried to go back to stock using lgup again, but now lgup it just crashes. The phone now goes automatically to download mode after turning it on, the progress bar stays at 0%, the phone says "633A B100" and lgup crashes after 9% "prepare dlmode" or something similar. any ideas? :/
Some people seem to have fixed this issue by flashing the official Cyanogenmod Recovery.
thewild said:
Some people seem to have fixed this issue by flashing the official Cyanogenmod Recovery.
Click to expand...
Click to collapse
After flashig the CM Recovery via TWRP, i can't use the recovery anymore. If i boot into CM-Recovery the display shows "Ereasing" and start the system. After that i got a bootloop.
Is it possible to use fastboot??
You guys should also check CM14.1 thread because people there are talking about the same problem. The latest post says the only solution was to flash an official kdz with LGUP.
thewild said:
You guys should also check CM14.1 thread because people there are talking about the same problem. The latest post says the only solution was to flash an official kdz with LGUP.
Click to expand...
Click to collapse
Did that. Worked once. Then i tried to flash cm again and had the same problems, so i wanted to flash stock again... now lgup crashes at 9% and the phones goes directly to download mode after turning it on.
onlyolli said:
Did that. Worked once. Then i tried to flash cm again and had the same problems, so i wanted to flash stock again... now lgup crashes at 9% and the phones goes directly to download mode after turning it on.
Click to expand...
Click to collapse
And the two times you tried to flash CM, that was with the same recovery ?
Can you go into fastboot mode ?
thewild said:
And the two times you tried to flash CM, that was with the same recovery ?
Can you go into fastboot mode ?
Click to expand...
Click to collapse
Yes, it was with cm recovery 20161130, if i remember correctly.
Sadly now, i can not go into fastboot. The phone goes directly into download mode. My windows vm detects the phone, and tries to flash a recent kdz, but lgup crashes at 9%. The phone still shows "0%".
Oh that's bad. What about another kdz ?
thewild said:
Oh that's bad. What about another kdz ?
Click to expand...
Click to collapse
Already tried like 3-4.... Its always the same. If the tool would at least give me a little bit more information, but it just stops.
I don't know then. Some users seem to have had the same problem (stuck at 9%) : http://forum.xda-developers.com/search/forum/4233?query=lgup 9%
I had the same issue, tried several things, my final solution was:
- Start in download mode (Volumen up and then plug in cable)
- use "LG Brigde" on Mac to install stock Rom ( Software update tab in APP ) guess should also work with Windows
- Boot original android
- enable usb debug
- Start bootloader via ADB
- fastboot flash recovery to twrp 3.0.2
- Boot in recovery via power and vol down (first factory reset from stock appears but after this twrp is starting)
- install cm nighty of 1 DEC via ADB sideload
- reboot and done
In the meantime i updated to twrp 3.0.2-1., installed gapps etc. everything is now working fine again.
Hope this is also working for you.
Which version of cm14 did u download and install? Can u please post the exact version?
Mmh ... LGUP is the Windows utility right ? How do I do if I only have a Linux machine ?
steadfasterX said:
When you say you try the recovery mode how do you try to get into it? Btw do you have twrp installed?
Click to expand...
Click to collapse
I'm trying to get to it via power+down, I get to the double "do you want to factory reset ?" question, but then :
- sometimes the CM recovery just says "erasing" for a few seconds and reboots to (non-working) CM
- sometimes it just plainly boots to (non-working) CM
I used to have TWRP installed but it didn't work with CM update, so I let CM install its own recovery.
Hello guys,
my Oneplus 3 is hard bricked, I tried the methods in the Mega Unbrick guide, my device already gets shown as Qualcomm 9008 ... in Device Manager, so I started the MSM DownloadTool and it flashed anything without errors. But when the phone reboots I get a black screen and the white led is on.
I can't even boot to stock recovery (Volume down + power doesn't work and rebooting to recovery through fastboot doesn't work, too....) my bootloader is locked and all attempts to unlock the bootloader are failing with the error "remote: oem unlock is not allowed"
So at the moment I'm stuck in fastboot and nothing else works -.-
Can someone please help me?
The unbrick tool has an old firmware, can I replace the files with files from a newer firmware?
Thanks!
Have you tried the exact steps from Method 2? Maybe unzip it? If that doesn't work which is highly unlikely then there is not much you can do.
Puddi_Puddin said:
Have you tried the exact steps from Method 2? Maybe unzip it? If that doesn't work which is highly unlikely then there is not much you can do.
Click to expand...
Click to collapse
Yeah I tried it as I said, the MSM DownloadTool showed me Completed and the phone tried to boot up after that.
I'm now contacting the OP Customer Support, I've read a few times that they have other files to unbrick the phone with the MSM Tool.
min-dfreak said:
Yeah I tried it as I said, the MSM DownloadTool showed me Completed and the phone tried to boot up after that.
I'm now contacting the OP Customer Support, I've read a few times that they have other files to unbrick the phone with the MSM Tool.
Click to expand...
Click to collapse
Ye thats the only thing you can currently do... May i ask what you have done how did it get bricked?
I just updated AICP ota and after flashing the update my phone didn't boot up. The screen went black immediately.
So I thought that it is maybe a Problem with the ROM and I tried to go back to stock.
Flashed the stock recovery and locked the bootloader, but I couldn't boot to the stock recovery.
There it started...
Switch off the phone, connect usb ,open unbrick tool full ( method 2),Press vol up,down and power buttons same time ,tool will recognize phone then start , you must unbrick now.
NEVER LOCK YOUR PHONE.
drmuruga said:
Switch off the phone, connect usb ,open unbrick tool full ( method 2),Press vol up,down and power buttons same time ,tool will recognize phone then start , you must unbrick now.
NEVER LOCK YOUR PHONE.
Click to expand...
Click to collapse
Please read, I already did that.
The tool completed it successfully, but still black screen after a reboot.
Only the LED is flashing white.
I already contacted the support, they will do it remotely tomorrow.
min-dfreak said:
Please read, I already did that.
The tool completed it successfully, but still black screen after a reboot.
Only the LED is flashing white.
I already contacted the support, they will do it remotely tomorrow.
Click to expand...
Click to collapse
Never but never lock your bootloader...
If recovery, boot or system partition is modified. There's no harm in re locking otherwise..
Hi guy i have a big problem i buy a one plus 3 i was using it 1 month and there was a update i don't remember what it was oreo or nougat when the update downloaded i install it and the i got a bootloop 2 hours didn't boot and my device is not rooted and didn't enable developer option i tried to install stock rom by adb and fastboot with sideload it load but it stuck on 50% then it say failed tried to install recovery in fastboot i installed drive oneplus 3 ect but can't flash it i think because i have oem locked i trien to unlocked it says failed 00.6s ect and i don't have guarantee i have dash and cable charger i can charge it and go to fastboot and recovery but when i boot my phone normally i show logo one plus then the two red bullet who move then it power off
Dsn Fouad said:
Hi guy i have a big problem i buy a one plus 3 i was using it 1 month and there was a update i don't remember what it was oreo or nougat when the update downloaded i install it and the i got a bootloop 2 hours didn't boot and my device is not rooted and didn't enable developer option i tried to install stock rom by adb and fastboot with sideload it load but it stuck on 50% then it say failed tried to install recovery in fastboot i installed drive oneplus 3 ect but can't flash it i think because i have oem locked i trien to unlocked it says failed 00.6s ect and i don't have guarantee i have dash and cable charger i can charge it and go to fastboot and recovery but when i boot my phone normally i show logo one plus then the two red bullet who move then it power off
Click to expand...
Click to collapse
I'm assuming your device is OnePlus3 and not 3T
Okay. Firstly give a try to Oneplus3 openbeta Nougat special edition.
Oneplus3 : http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Method 1 : specific recovery for open beta24 available in Oneplus downloads
https://downloads.oneplus.com
Find legacy roms and find openbeta 24
Method 2: latest TWRP
If your bootloader is locked this isn't gonna work. But if it is still in unlocked .
Download TWRP for Oneplus3 from official TWRP site
Flash the recovery you choose using fast boot.
Now using asn command, try to flash the special edition.
Mostly this solves your issue. It helped me.
Let me know whether you face any issues.
Note: in this method you may lose every data you have on the phone. It boots up (if at all ? ) with fresh firmware and fresh storage (sometimes)
SivaMaxwell said:
I'm assuming your device is OnePlus3 and not 3T
Okay. Firstly give a try to Oneplus3 openbeta Nougat special edition.
Oneplus3 : http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Method 1 : specific recovery for open beta24 available in Oneplus downloads
https://downloads.oneplus.com
Find legacy roms and find openbeta 24
Method 2: latest TWRP
If your bootloader is locked this isn't gonna work. But if it is still in unlocked .
Download TWRP for Oneplus3 from official TWRP site
Flash the recovery you choose using fast boot.
Now using asn command, try to flash the special edition.
Mostly this solves your issue. It helped me.
Let me know whether you face any issues.
Note: in this method you may lose every data you have on the phone. It boots up (if at all ? ) with fresh firmware and fresh storage (sometimes)
Click to expand...
Click to collapse
Yeah i have oneplus 3 my bootloader is locked can't flash anything im going to try method 1
By the way why beta 24 why not lastest update ? And whene i download it do you want me to flash it with sideload like #adb sideload openbeta24.zip ?
Dsn Fouad said:
Yeah i have oneplus 3 my bootloader is locked can't flash anything im going to try method 1
By the way why beta 24 why not lastest update ? And whene i download it do you want me to flash it with sideload like #adb sideload openbeta24.zip ?
Click to expand...
Click to collapse
The file I gave link to is a special edition by Oneplus for Openbeta-Nougat. You can go to Nougat from any rom.
Rom: http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Specific recovery should be downloaded from Oneplus website.
You can sideload using adb or store internal storage and flash.
I tried with latest TWRP recently and it worked.
Note that all your data gets wiped if you use oneplus-recovey and asn sideload
SivaMaxwell said:
The file I gave link to is a special edition by Oneplus for Openbeta-Nougat. You can go to Nougat from any rom.
Rom: http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Specific recovery should be downloaded from Oneplus website.
You can sideload using adb or store internal storage and flash.
I tried with latest TWRP recently and it worked.
Note that all your data gets wiped if you use oneplus-recovey and asn sideload
Click to expand...
Click to collapse
The problem is i dont have store internal storage and when i try to flash anything it say oem locked not allowed and when i flash a rom with adb sideload jfjd.zip it stuck on 60% will it be complete if i use your beta ?
Dsn Fouad said:
The problem is i dont have store internal storage and when i try to flash anything it say oem locked not allowed and when i flash a rom with adb sideload jfjd.zip it stuck on 60% will it be complete if i use your beta ?
Click to expand...
Click to collapse
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
SivaMaxwell said:
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
Click to expand...
Click to collapse
Thanks i will download and give it a try
SivaMaxwell said:
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
Click to expand...
Click to collapse
Before that i downloaded msm download tool 3.0.8 i tested it and it boot but it say enter pin password i dont know what is the pin i didn't use a pin before it was working
Dsn Fouad said:
Before that i downloaded msm download tool 3.0.8 i tested it and it boot but it say enter pin password i dont know what is the pin i didn't use a pin before it was working
Click to expand...
Click to collapse
Simply reboot to recovery and say yes to wipe every data.
Note1:
all your internal data is wiped in the method I suggested. I can recall there is a method to recover data only if bootloader is unlocked. If your bootloader is locked there is no other way.
Note2: your data will be formatted to f2fs file system. If you want to flash any custom ROM, YOU SHOULD CHECK COMPATIBILITY WITH F2FS in that ROM forums.
It's better to always have EXT4 file system. You can change this file system with TWRP
SivaMaxwell said:
Simply reboot to recovery and say yes to wipe every data.
Note1:
all your internal data is wiped in the method I suggested. I can recall there is a method to recover data only if bootloader is unlocked. If your bootloader is locked there is no other way.
Note2: your data will be formatted to f2fs file system. If you want to flash any custom ROM, YOU SHOULD CHECK COMPATIBILITY WITH F2FS in that ROM forums.
It's better to always have EXT4 file system. You can change this file system with TWRP
Click to expand...
Click to collapse
Bootloader is locked i tryed to flash the 24 beta yoi give me but it stuck on 47 and say failed im just going to sell it
Dsn Fouad said:
Bootloader is locked i tryed to flash the 24 beta yoi give me but it stuck on 47 and say failed im just going to sell it
Click to expand...
Click to collapse
Even if the bootloader is locked, you can boot into the current rom and unlock simply by going to advanved options.
It is a very simple process.
HONOR 7X ( indian variant )
Phone is in a boot loop.
It shows Honor Logo and then the Error screen with the following message :
ERROR MODE
Attention!
Please update system again
Error!
Func NO : 15 (bl31 image)
Error NO : 1 (security verify failed!)
I tried to manually update to Oreo and was successful.
But VoLTE was not working properly.
So, i decided to roll back to EMUI 5.0 (Nougat) and got stuck in Boot Loop.
Initially both twrp and fastboot was working.
I tried to flash Stock recovery for oreo using fastboot.
But it didn't work.
At that point i lost both twrp and stock recovery.
It went into ERROR mode with different error codes saying "No Recovery Image" and "Load Failed"
I tried to Erase recovery and re-flash it.
I tried erasing System and flashing the system.img for oreo which was extracted from UPDATE.APP
I tried Multi tools.
I tried dload method.
Nothing worked. Same error mode.
Then i finally tried flashing the stock recovery again and relocked the oem.
Now, I can't even get into Fastboot.
It just displays the ERROR Screen.
I tried draining the battery to 0% and restarting it.
I tried all button combinations.
No luck.
Nothing works.
Now, i have a bricked phone with no recovery and no fastboot.
And i don't know whether they will accept this in the service center.
Is there someone who could really help me get my phone back?
rahulrk.2303 said:
HONOR 7X ( indian variant )
Phone is in a boot loop.
It shows Honor Logo and then the Error screen with the following message :
ERROR MODE
Attention!
Please update system again
Error!
Func NO : 15 (bl31 image)
Error NO : 1 (security verify failed!)
I tried to manually update to Oreo and was successful.
But VoLTE was not working properly.
So, i decided to roll back to EMUI 5.0 (Nougat) and got stuck in Boot Loop.
Initially both twrp and fastboot was working.
I tried to flash Stock recovery for oreo using fastboot.
But it didn't work.
At that point i lost both twrp and stock recovery.
It went into ERROR mode with different error codes saying "No Recovery Image" and "Load Failed"
I tried to Erase recovery and re-flash it.
I tried erasing System and flashing the system.img for oreo which was extracted from UPDATE.APP
I tried Multi tools.
I tried dload method.
Nothing worked. Same error mode.
Then i finally tried flashing the stock recovery again and relocked the oem.
Now, I can't even get into Fastboot.
It just displays the ERROR Screen.
I tried draining the battery to 0% and restarting it.
I tried all button combinations.
No luck.
Nothing works.
Now, i have a bricked phone with no recovery and no fastboot.
And i don't know whether they will accept this in the service center.
Is there someone who could really help me get my phone back?
Click to expand...
Click to collapse
I was gonna do a roll back too. Maybe I need to re exam your problem first.
Like why did you flash the Oreo system image after you rolled back?
Sorry, but I don't know of any steps forward for you, but can you tell the steps you did in the "Roll-back" and try to be detailed.
Please take a full back up before you roll back.
mrmazak said:
I was gonna do a roll back too. Maybe I need to re exam your problem first.
Like why did you flash the Oreo system image after you rolled back?
Sorry, but I don't know of any steps forward for you, but can you tell the steps you did in the "Roll-back" and try to be detailed.
Click to expand...
Click to collapse
I didn't succeed rolling back. I flashed the system.img and stock recovery of emui 5.0. But it got me the error.
Maybe the system partitions of emui 8.0 and 5.0 are different.
For example, The recovery partition has changed to recovery_ramdisk in emui 8.0.
Then, I tried flashing system.img and recovery of emui 8.0.
I got stuck in a bootloop.
But fastboot was accessible.
I tried flashing twrp for 8.0 by openkirin. It didn't work too.
Then i thought maybe i should flash the stock recovery and relock the oem and i did it.
Now i ended up with a locked bootloader, no recovery. Just the error message and the bootloop.
Somebody please help.
rahulrk.2303 said:
I didn't succeed rolling back. I flashed the system.img and stock recovery of emui 5.0. But it got me the error.
Maybe the system partitions of emui 8.0 and 5.0 are different.
For example, The recovery partition has changed to recovery_ramdisk in emui 8.0.
Then, I tried flashing system.img and recovery of emui 8.0.
I got stuck in a bootloop.
But fastboot was accessible.
I tried flashing twrp for 8.0 by openkirin. It didn't work too.
Then i thought maybe i should flash the stock recovery and relock the oem and i did it.
Now i ended up with a locked bootloader, no recovery. Just the error message and the bootloop.
Somebody please help.
Click to expand...
Click to collapse
OK, yes there is different partition table for oreo, so more that those partitions was needed.
one thing you might be able to try, is a manuael update.
put the oreo update.zip in the root of sd card. put card in phone, and hold both volume buttons together with power button.
mrmazak said:
OK, yes there is different partition table for oreo, so more that those partitions was needed.
one thing you might be able to try, is a manuael update.
put the oreo update.zip in the root of sd card. put card in phone, and hold both volume buttons together with power button.
Click to expand...
Click to collapse
I've already tried the dload method. But holding both volume buttons + power button didn't work. It loads into the error mode screen again. Maybe I'll copy the update.zip into the root of SD card and try again. But i think the phone won't boot into software update mode.
Is it hard bricked or soft bricked?
Should i try taking it to the service center?
People
Dont try to roll back from Oreo to Nougat on update ZIPs...
Partitions changed on Oreo System. The available update to Oreo it must read the previous partitions and configure the new partitions.
If you try to do it AFTER installing the update, the installation will get error cause can't read the Nougat partitions.
rahulrk.2303
With the phone powered off, press Vol Down key and insert the USB cable.
What happens?
RSGI said:
People
Dont try to roll back from Oreo to Nougat on update ZIPs...
Partitions changed on Oreo System. The available update to Oreo it must read the previous partitions and configure the new partitions.
If you try to do it AFTER installing the update, the installation will get error cause can't read the Nougat partitions.
rahulrk.2303
With the phone powered off, press Vol Down key and insert the USB cable.
What happens?
Click to expand...
Click to collapse
Nothing. It vibrates. Honor logo. Again the same error screen. I know it's supposed to go into fastboot mode. But unfortunately, it doesn't.
rahulrk.2303 said:
Nothing. It vibrates. Honor logo. Again the same error screen. I know it's supposed to go into fastboot mode. But unfortunately, it doesn't.
Click to expand...
Click to collapse
There is Oreo downgrade proceedure on Chinese huiwei club website. But your device needs full firmware package available.
There is full downgrade packages for al00 al10 and tl10.
rahulrk.2303 said:
Nothing. It vibrates. Honor logo. Again the same error screen. I know it's supposed to go into fastboot mode. But unfortunately, it doesn't.
Click to expand...
Click to collapse
Man... The FASTBOOT partiton is also screwed up...
The only change you got, other take the phone to the Huawei Service Center, is the dload method.
But for that you'lll need full packages.
mrmazak
Can you share a link to those packages?
RSGI said:
Man... The FASTBOOT partiton is also screwed up...
The only change you got, other take the phone to the Huawei Service Center, is the dload method.
But for that you'lll need full packages.
mrmazak
Can you share a link to those packages?
Click to expand...
Click to collapse
I have downloaded updateL22.zip for oreo and tried the dload method. It didn't work. It still boots to the same error mode. Is this condition hard brick or soft brick? I don't think there is a problem with the motherboard because the screen is turning on and it's in a bootloop. But i can't access recovery or fastboot. I'm confused. Maybe it's a software issue. But there is no way i could access the phone in order to flash something. I'm planning to take it to the service center and act innocent. Any suggestions? Will they find out that i unlocked or rooted and messed with the partitions. Is there any chance they could fix it?
RSGI said:
Man... The FASTBOOT partiton is also screwed up...
The only change you got, other take the phone to the Huawei Service Center, is the dload method.
But for that you'lll need full packages.
mrmazak
Can you share a link to those packages?
Click to expand...
Click to collapse
the three marked as full
b192
dated 3-28
http://pro-teammt.ru/firmware-database/?firmware_model=bnd-&firmware_page=0
mrmazak said:
the three marked as full
b192
dated 3-28
http://pro-teammt.ru/firmware-database/?firmware_model=bnd-&firmware_page=0
Click to expand...
Click to collapse
That's the one i tried.
The BNDAL10 one.
rahulrk.2303 said:
I have downloaded updateL22.zip for oreo and tried the dload method. It didn't work. It still boots to the same error mode. Is this condition hard brick or soft brick? I don't think there is a problem with the motherboard because the screen is turning on and it's in a bootloop. But i can't access recovery or fastboot. I'm confused. Maybe it's a software issue. But there is no way i could access the phone in order to flash something. I'm planning to take it to the service center and act innocent. Any suggestions? Will they find out that i unlocked or rooted and messed with the partitions. Is there any chance they could fix it?
Click to expand...
Click to collapse
If you take it to the service center, it wont matter how you play it...
The phone just dont get that way unless, somehow, the warranty was voided...
The less you say, the less you will pay for they to fix it... I believe that over those Service Centers they can fix almost everythng.
That package is not a full package! you need a Full Package
mrmazak said:
the three marked as full
b192
dated 3-28
http://pro-teammt.ru/firmware-database/?firmware_model=bnd-&firmware_page=0
Click to expand...
Click to collapse
Here´s a noob question:
What update.zip should i download?
1 - The one in the filelist section
2 - The one at the update section
Please, dont tell me that they're the same....
RSGI said:
If you take it to the service center, it wont matter how you play it...
The phone just dont get that way unless, somehow, the warranty was voided...
The less you say, the less you will pay for they to fix it... I believe that over those Service Centers they can fix almost everythng.
That package is not a full package! you need a Full Package
Click to expand...
Click to collapse
Is there nothing more i could do?
And what do you think the problem is?
Software issue or Hardware?
rahulrk.2303 said:
Is there nothing more i could do?
And what do you think the problem is?
Software issue or Hardware?
Click to expand...
Click to collapse
How the phone end up this way?
What were you trying to do?
How the heck you screw Fastboot? just kidding
If were trying to update, flash something to the device, its most likely a software issue.
If the phone fell down, bumped into something... well this increases the change that some hardware may by screwed also...
RSGI said:
If you take it to the service center, it wont matter how you play it...
The phone just dont get that way unless, somehow, the warranty was voided...
The less you say, the less you will pay for they to fix it... I believe that over those Service Centers they can fix almost everythng.
That package is not a full package! you need a Full Package
Here´s a noob question:
What update.zip should i download?
1 - The one in the filelist section
2 - The one at the update section
Please, dont tell me that they're the same....
Click to expand...
Click to collapse
but i think the update.zip listed in file list is same , don't really know.
all three are needed for full package.
RSGI said:
How the phone end up this way?
What were you trying to do?
How the heck you screw Fastboot? just kidding
If were trying to update, flash something to the device, its most likely a software issue.
If the phone fell down, bumped into something... well this increases the change that some hardware may by screwed also...
Click to expand...
Click to collapse
I flashed Oreo update successfully.
I wanted to Rollback.
I flashed system and recovery of nougat and locked the oem.
The problem is that we can't rollback from oreo to nougat because of different partitions.
I realized that only after locking the oem.
And now there's nothing i could do.
Btw, this is only due to flashing. So, i hope it's not a Motherboard problem.
The cost of flashing Software from service center is very less, even if my warranty is void.
rahulrk.2303 said:
I flashed Oreo update successfully.
I wanted to Rollback.
I flashed system and recovery of nougat and locked the oem.
**The problem is that we can't rollback from oreo to nougat because of different partitions.
Click to expand...
Click to collapse
???Well to be true you did not flash a roll-back(did you?) you only replaced system and recovery. The true roll-back "update.zip" should do more than that.???
I realized that only after locking the oem.
And now there's nothing i could do.
Btw, this is only due to flashing. So, i hope it's not a Motherboard problem.
The cost of flashing Software from service center is very less, even if my warranty is void.
Click to expand...
Click to collapse
mrmazak said:
???Well to be true you did not flash a roll-back(did you) you only replaced system and recovery. The true roll-back "update.zip" should do more than that.???
Click to expand...
Click to collapse
Tbh, i did everything one by one because nothing seems working.
I've tried every single method, trust me.
Hello
I was trying to flash AEX 6.3 on z2 plus and i get the error " E20001: failed to update vendor image" and
updater process ended with error 7.
How can i resolve this problem?
Also i get the message " your device software can't be checked for corruption", please lock the boot loader.
This message comes after an update and prior to that it was working fine.
Phone is struck at ZUK logo and does not boot.
Any suggestion to solve this issue?
Thanks and much appreciated.
flash V2F .. reboot to recovery.. use compatible twrp.. or upgrade bootloader to 4.0 .. qpst to zui 4.0
sanjay.2704 said:
flash V2F .. reboot to recovery.. use compatible twrp.. or upgrade bootloader to 4.0 .. qpst to zui 4.0
Click to expand...
Click to collapse
did v2f. installed latest official twrp. same situation and no change.
did not do the second part.
the following message still appears.
" your device software can't be checked for corruption", please lock the boot loader.
It was a working device and this happened after an OTA update.
Don't understand why this happens? can you give more specific instructions and point me to any links that can help.
thanks.
" your device software can't be checked for corruption", please lock the boot loader. This is because you unlocked your bootloader and installed the custom recovery.
ramadurair said:
did v2f. installed latest official twrp. same situation and no change.
did not do the second part.
the following message still appears.
" your device software can't be checked for corruption", please lock the boot loader.
It was a working device and this happened after an OTA update.
Don't understand why this happens? can you give more specific instructions and point me to any links that can help.
thanks.
Click to expand...
Click to collapse
Today I flashed the newest OOS 10.0.3. After I had flashed it+TWRP through Magisk and rebooted, Vanced Youtube was not able to be installed correctly. I have fixed this earlier by uninstalling the Youtube app through a root-uninstaller app. Then flash Vanced in Magisk, and reboot.
After doing this, my phone would only bootloop into TWRP/Fastboot. So I tried to boot into TWRP, flash OOS 10.0.3, TWRP then Magisk, in TWRP, but no success. The phone would just bootloop. So I tried my final attempt without having to wipe the whole phone - Flash an old backup (I think it was from October, probably OOS 10.0.1). After doing a full recovery in TWRP with the old backup, my phone boots into Qualcomm CrashDump Mode with a message displaying
dm-verity device corrupted Force Dump
Kernel_restart
Click to expand...
Click to collapse
By holding power+volume up for 10 seconds, my phone reboots displaying the warning message about my phone's bootloader being unlocked, then shows the quoted message above.
Could anyone please help me fix this?
---
Update:
So after trying to reboot for 15+ times, my phone somehow booted into TWRP. What would be the best step now?
Wipe all, flash OOS 10.0.3, Flash TWRP and Flash Magisk?
Which specific model do you have, region? Which twrp was used?
Werchio said:
Today I flashed the newest OOS 10.0.3. After I had flashed it+TWRP through Magisk and rebooted, Vanced Youtube was not able to be installed correctly. I have fixed this earlier by uninstalling the Youtube app through a root-uninstaller app. Then flash Vanced in Magisk, and reboot.
After doing this, my phone would only bootloop into TWRP/Fastboot. So I tried to boot into TWRP, flash OOS 10.0.3, TWRP then Magisk, in TWRP, but no success. The phone would just bootloop. So I tried my final attempt without having to wipe the whole phone - Flash an old backup (I think it was from October, probably OOS 10.0.1). After doing a full recovery in TWRP with the old backup, my phone boots into Qualcomm CrashDump Mode with a message displaying
By holding power+volume up for 10 seconds, my phone reboots displaying the warning message about my phone's bootloader being unlocked, then shows the quoted message above.
Could anyone please help me fix this?
---
Update:
So after trying to reboot for 15+ times, my phone somehow booted into TWRP. What would be the best step now?
Wipe all, flash OOS 10.0.3, Flash TWRP and Flash Magisk?
Click to expand...
Click to collapse
TWRP?! There are no working twrps for 7T series.
gpz1100 said:
Which specific model do you have, region? Which twrp was used?
Click to expand...
Click to collapse
Oneplus 7, EU region (guacamoleb). TWRP that I have managed to boot into is 3.3.1-70.
Aswin08 said:
TWRP?! There are no working twrps for 7T series.
Click to expand...
Click to collapse
My bad. It is a Oneplus 7 Guacamoleb, TWRP version is 3.3.1-70
Oneplus 7T Qualcomm CrashDump Mode
Hi Everyone,
My OnePlus 7T got stuck in QUALCOMM CRASHDUMP MODE.
First, i wanted to know the reason why this crash is happening as i can see many users reporting the same in many forums.
Note : It is my brand new phone purchased 2 days back.
Thanks !!
Restor your firmware with the msmtool
Here are the drivers that are installed on my PC ( I enabled hidden devices, in order to see them ) These were recognizing prior to " qualcomm crash dump" .
Now ADB,Fastbootd and Windows 10 / Mac OSx do not see my device, let alone recognize
It's possible that your phone is corrupted. Double freezer bag phone, express all excess air out from bag, zip both bags tightly, stick phone in freezer for 1 hr to deplete battery, then try buttons and msmtool