Develop Bugs

[Q][help] bricked badly after failed encrypt - fastboot and ODIN can't write to flash

hi all,
i've managed to get my g-nex (vz lte) pretty badly bricked and am hoping that someone here will be able to help. here's what i did initially on the phone:
1. ran 4.0.2 update from carrier
2. installed adb sdk etc on win 7, verified connectivity and function
3. oem unlock
4. rooted phone
5. installed apps, etc.
6. used phone for a few days, rebooted at will, all working as expected, no issues
7. fully charged phone and in the settings kicked off the encryption process, entered PIN, everything looked good.
8. this morning i woke up to a failed encryption (unfortunately i didn't catch the error message) which needed to be rebooted to move on.
9. after choosing reboot, the screen went very strange - it had grainy horizontal lines that shifted in color somewhat and got dim
10. after waiting for a bit without anything happening, pulled the power and battery
11. the phone rebooted into fastboot, couldn't get into recovery to restore cwm backup, couldn't really do anything
phone shows the following:
fastboot mode - no boot or recovery img
product name - tuna
variant - toro
hw version - 9
bootloader version - primekkk15
baseband version - i515.ek02 cdma - i515.ek05
carrier info - none
serial number - XX_redacted_XX
signing - production
lock state - unlocked
here's what i've tried:
adb commands - doesn't show as there from adb devices
fastboot commands - shows up with fastboot devices, flash commands seem to start but never stop
ODIN mode - connects but writes fail to complete
different usb ports/cables, doesn't seem to make a difference
what i've found to somewhat work - but not really do much - is to oem lock and unlock the phone, once there i can fastboot flash boot boot.img, etc. but if i do a recovery and try and boot into it, it just hangs at the google screen (with the lock unlocked).
i would like maybe reformat the phone completely and reinstall, i've tried the fastboot -w and erase boot / recovery thinking that i could write a clean image to them once they had been cleared, no dice.
if anyone has some suggestions, i'd really appreciate it.
take care,
philo

Have you tried a clean install of the factory image found here? http://code.google.com/android/nexus/images.html#mysidicl53f

i have tried going back to factory, unfortunately that set of images didn't work either. i was able (after an oem lock/unlock) to flash the img files, but it errored on the fastboot reboot-bootloader command with the oddly lined screen. i've attached a picture of the screen for reference.

philo_enyce said:
i have tried going back to factory, unfortunately that set of images didn't work either. i was able (after an oem lock/unlock) to flash the img files, but it errored on the fastboot reboot-bootloader command with the oddly lined screen. i've attached a picture of the screen for reference.
Click to expand...
Click to collapse
I hope you flashed the LTE version and not the GSM
You need this one https://dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz and you must first flash bootloader then radio and then the update img

i have been using the lte, same as your link. i can get the bootloader on, but a reboot-bootloader gives that weird screen, if i try and flash the radio without rebooting i get:
unknown partition 'radio'

philo_enyce said:
i have been using the lte, same as your link. i can get the bootloader on, but a reboot-bootloader gives that weird screen, if i try and flash the radio without rebooting i get:
unknown partition 'radio'
Click to expand...
Click to collapse
Check here http://forum.xda-developers.com/showthread.php?t=1392336
Its the cwm for cdma edition.Check if you can flash it and in this way have access to cwm recovery

i've tried that as well, same lines even if i use the menu to go to recovery after flashing rather than reboot to bootloader first.

So long as it's back to stock, and you've locked the bootloader, it's off for a replacement you go if it was me

EddyOS said:
So long as it's back to stock, and you've locked the bootloader, it's off for a replacement you go if it was me
Click to expand...
Click to collapse
+1 to this

interestingly, i can't get the fastboot oem lock to take either. it reverts back to unlocked after the reboot fails and i have to pop the battery.
does anyone know how to straight up repartition/reformat the flash? i'm assuming that the failed encryption of the flash has put it into an unusable state and would be happy enough just wiping the damn thing clean...

It looks the encryption screwed up because of the different recovery partition which might of also messed up the partition table.
Best bet is to plead ignorance and get a replacement phone.

problem "solved"
i called samsung and pleaded for the pit + factory image with no luck, so i went over to my local vzw and had them replace the phone for me.
i'm not going to try and encrypt this one, hopefully this was just a fluke and won't affect anyone else...

nice work... let them try to fix that shiz!

Darn, I was hoping for a solution...
I am having a similar issue with a Nexus 5. Phone was working fine, started the encryption process and went to bed and woke up with a bricked phone. I can get into the Bootloader and had figured no problem, I'll just do a factory wipe. Whether trying to boot the phone or get it to do the factory restore it sits there and bootloops with the Google logo. Wish programmers would put in status messages the way we did in the 'old days.'
I was able to get a little further was able to reflash, format the partitions etc. but no luck. I am wondering if perhaps the user data may have an indicator or flag that states it is encrypted even though it isnt at this point encrypted. Figured the factory restore would have been more than enough. WUG makes a nice Root Toolkit that automates a lot of the process but even letting do what I already didnt help.
philo_enyce said:
i called samsung and pleaded for the pit + factory image with no luck, so i went over to my local vzw and had them replace the phone for me.
i'm not going to try and encrypt this one, hopefully this was just a fluke and won't affect anyone else...
Click to expand...
Click to collapse

philo_enyce said:
interestingly, i can't get the fastboot oem lock to take either. it reverts back to unlocked after the reboot fails and i have to pop the battery.
does anyone know how to straight up repartition/reformat the flash? i'm assuming that the failed encryption of the flash has put it into an unusable state and would be happy enough just wiping the damn thing clean...
Click to expand...
Click to collapse
Yep , if you can get into recovery , you can adb shell , then list the partitions with "cat proc/mounts" , from there you'll have a list of your partitions and you can use the ext4 tools to manually repartition . I believe the command is makefs_ext4 <whatever partition you wanna do > I'll try to find the exact command but you can do it .
Also if you simply type "fastboot " when at the bootloader it'll give you the help text and it should tell you how to wipe partitions from fastboot
Hack The Tuna

The same issue here ! memory locked
I ve got the same scenario on a phone i just got , brand new but with the same issue , this one boots up but its impossible to factory reset it , odin , cyanogenmod , fastboot adb flashes .... everything fails somehow .... once you reboot the phone everything comes back ! stock software with the applications and old data .... theres no way to erase it ... it seems the previous owner of the phone encrypted it and then used clockworkmod or something like that ..... the nand on the device is like hardlocked .... doesnt let you do anything !

Find 7 (x9076) soft bricked, misread by device manager,

Hey Everyone,
I have a Find 7 (X9076). A while back I updated to the "stable version " of ColorOSi and ever since my usb doesn't charge the phone and vol down key doesn't work. Additionally it is being misread by the computer device manager as a "Samsung Android Device" when it is in boot loader mode.
I suspected it was a software/kernel issue because when I checked the registry I found the original oppo drivers, so I attempted to flash a new kernel to the device and ended up soft bricking it (no image). Now even though it is soft bricked I am still able to get into boot loader mode (no image). Please Help?
I have used Find 7 recovery installer and FASTBOOT (CMD) as well as trying to use ADB and a Find 7 unbricking tool in Windows 7 test mode the last two didn't work/didn't recognize my phone at all. I refuse to abandon my device so what do I do?

Given you have adb access, you could extract the contents of the current (2.x?) color os image, and fastboot flash the partitions manually.
I recently did this and 'recovered' my device.

adb didnt recognize my device -but how do I do that just in case I'm able to get it working?

Midnight247 said:
adb didnt recognize my device -but how do I do that just in case I'm able to get it working?
Click to expand...
Click to collapse
I flashed a kernel once and the phone just died. I fixed it by following the unbrick thread in oppo forum.

ADB, FastBoot and the USB
I don't know if I was clear in my explanation as to how and when my device (FIND7 X9076) is recognized ONLY by the following: my Computer (Windows 7), the Device Manager, Fast-Boot and on the FIND7 Recovery Installer. I have been able to enter fast-boot mode on any version of the ColorOS I flashed, 1.2 - 2.5.1, (stable version) and work within the confines of that mode. However when the USB is connected in anything other mode (recovery-main OS) it ceases functionality (sending information to comp for recognition, charging, etc.). Also the charger doesn't work and nor does the notification light. Now I may be wrong, but for these reasons I believe the problem is likely software related. I am open to any opinions and advice.
-Thank You Everyone

tropical cactus said:
I flashed a kernel once and the phone just died. I fixed it by following the unbrick thread in oppo forum.
Click to expand...
Click to collapse
If this http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra= is the guide you are referring to I have downloaded the tool but I cannot seem to get it to recognize my device. I went into test mode downloaded and installed all of the drivers but my FIND7 still doesn't show. Have you had this problem?? What should I do??

Midnight247 said:
If this http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra= is the guide you are referring to I have downloaded the tool but I cannot seem to get it to recognize my device. I went into test mode downloaded and installed all of the drivers but my FIND7 still doesn't show. Have you had this problem?? What should I do??
Click to expand...
Click to collapse
Try the guide by cpthero on pg 28. It worked for me but didn't for the last person who tried it. You have to keep trying. For me, installing drivers was the hard part. After that, it just sailed through. Good luck.

tropical cactus said:
Try the guide by cpthero on pg 28. It worked for me but didn't for the last person who tried it. You have to keep trying. For me, installing drivers was the hard part. After that, it just sailed through. Good luck.
Click to expand...
Click to collapse
Okay, I will. To be honest that is one of the struggles I have been having (drivers installing). I am about to try erasing the false drivers that keep popping up ("Samsung Android Device") from my windows registry. Did you go this far? What did you do to resolve the problem? Thank you for your feedback, I will keep everyone posted.

Midnight247 said:
Okay, I will. To be honest that is one of the struggles I have been having (drivers installing). I am about to try erasing the false drivers that keep popping up ("Samsung Android Device") from my windows registry. Did you go this far? What did you do to resolve the problem? Thank you for your feedback, I will keep everyone posted.
Click to expand...
Click to collapse
Step 7-9 is crucial. If not done, the rest of the process cannot be carried out. Remove battery as well.

tropical cactus said:
Step 7-9 is crucial. If not done, the rest of the process cannot be carried out. Remove battery as well.
Click to expand...
Click to collapse
hmm okay, i see I will keep you posted

**IMPORTANT UPDATE**
***MAKE OPPO FIND 7 OPERABLE****
following commands in fastboot mode:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
By using the afformentioned commands in fastboot (of course) I was able to restore my phone to almost full functionality. It operates noramally and I fixed the notication light, But I say almost because I cannot charge my phone or have it recognized by my computer through any charger or usb connection when it is on normally or in recovery mode so if any one is familiar with this problem please respond or simply voice ideas.

If you got enough functionality to use it, is it on ColorOS? If so, can it be updated? If you have stock recovery you could flash it with AOSP or Spectrum, get full function back then work toward whichever ROM you really want.

RobboW said:
If you got enough functionality to use it, is it on ColorOS? If so, can it be updated? If you have stock recovery you could flash it with AOSP or Spectrum, get full function back then work toward whichever ROM you really want.
Click to expand...
Click to collapse
I do, have full functionality : ) everything but the USB is performing properly, but to be honest I dont know what AOSP is.....also this will repair functionality to the USB?

Where is the write protection switch?

I've been trying to unbrick my Pixel C and I believe the only way I can is to disable the write protection. I have read the front camera flex is the switch and to disable it, the camera has to be removed. Can someone point out to me which part it is? I don't want to mess up my tablet more than I have already. Also, is it safe to remove the front camera and close the tablet up?

Have you tried this before ?
viii_xvi said:
I've been trying to unbrick my Pixel C and I believe the only way I can is to disable the write protection. I have read the front camera flex is the switch and to disable it, the camera has to be removed. Can someone point out to me which part it is? I don't want to mess up my tablet more than I have already. Also, is it safe to remove the front camera and close the tablet up?
Click to expand...
Click to collapse
Man i think you haven't tried this for your tablet : Pixel c can boot images directly from fastboot !
Just do fastboot boot TWRP.img
That's it !

Samt434 said:
Man i think you haven't tried this for your tablet : Pixel c can boot images directly from fastboot !
Just do fastboot boot TWRP.img
That's it !
Click to expand...
Click to collapse
I've already tried what you're suggesting and get "remote: image verification failed". I've tried overwriting the recovery partition with TWRP but get "remote: unsupported command". I also have no recovery so I cannot run the fwtool command.
I didn't mean for that to sound passive aggressive (if it did) but I've been trying to unbrick it for the past 3 weeks. I wouldn't resort to opening up my tablet unless it's the last thing I could do. Unluckily for me, it is the only thing I haven't tried.

If I am reading your posts correctly.
the fastboot boot twrp did not work
yet you have tried with twrp to overwrite the partition.... later stating that you have no recovery installed.
leading me to believe that you can boot into twrp. at some point.
If that is the case I say walk the TWRP version backwards until you find one that allows you to get past the write protection.
Just a thought
viii_xvi said:
I've already tried what you're suggesting and get "remote: image verification failed". I've tried overwriting the recovery partition with TWRP but get "remote: unsupported command". I also have no recovery so I cannot run the fwtool command.
I didn't mean for that to sound passive aggressive (if it did) but I've been trying to unbrick it for the past 3 weeks. I wouldn't resort to opening up my tablet unless it's the last thing I could do. Unluckily for me, it is the only thing I haven't tried.
Click to expand...
Click to collapse

parakleet said:
If I am reading your posts correctly.
the fastboot boot twrp did not work
yet you have tried with twrp to overwrite the partition.... later stating that you have no recovery installed.
leading me to believe that you can boot into twrp. at some point.
Click to expand...
Click to collapse
Let me clarify. By overwrite, I meant flash TWRP through fastboot. As I have foolishly deleted my recovery, I am left with fastboot. Like I stated before, flashing TWRP or booting TWRP through fastboot doesn't work. So, I have turned to disabling the write protection switch.
Suggesting fixes is not the focus of the thread. Pointing out the hardware write protection is. If you can kindly return to that topic, it would be appreciated. I mentioned my tablet being bricked as context to why I am asking for the write protect to be pointed out.

Delete

viii_xvi said:
Let me clarify. By overwrite, I meant flash TWRP through fastboot. As I have foolishly deleted my recovery, I am left with fastboot. Like I stated before, flashing TWRP or booting TWRP through fastboot doesn't work. So, I have turned to disabling the write protection switch.
Suggesting fixes is not the focus of the thread. Pointing out the hardware write protection is. If you can kindly return to that topic, it would be appreciated. I mentioned my tablet being bricked as context to why I am asking for the write protect to be pointed out.
Click to expand...
Click to collapse
Is this post any use https://forum.xda-developers.com/showpost.php?p=67094250&postcount=9

Can't flash anything to Pixel C with `fastboot flash`, and fwtool is nowhere to be found
This is driving me nuts. I am trying (without success) to install LineageOS on my Pixel C. As a first step, I am trying to install TWRP. I have enabled Developer Mode, and the bootloader is unlocked. However, attempting to flash TWRP (or...
forum.xda-developers.com

I removed the display and disconnected the front camera flex.
But no luck: the device is still secure!
> fastboot getvar secure
yes

Honor 7x with Lineage and TWRP, stuck in limbo

Hi all,
I installed TWRP on my Honor 7x, that went well.
Yesterday I decided to try to get Lineage working so:
- I installed EMUI 8, that went pretty smooth
- I installed Lineage OS 15.1. (without GApps)
- I flashed TWRP.
The issue I have now is that:
1) I can't install any APK in Lineage. Probably needs a factory reset/dalvik cache wipe.
2) I can't boot into TWRP. It stays stuck on the splash screen forever. This also means I can't install OpenGapps, SuperUser access (afaik), or anything else that requires root.
3) The bootloader is saying "FRP: Locked", which means I can't flash a new TWRP or a different ROM. When I try it fails with "command not allowed"
3) "fastboot oem unlock" fails saying I need to enable it in the developer options, but it's grayed out in the developer options because it's already unlocked.
4) I wanted to try the "dload" method but I can't find a good explanation on how to do it, and Huawei recently took all their downloads down, which means I can't find any UPDATE.app even if I knew how.
5) The other solution that *might* work is using "fastboot oem frp-unlock", but I need an unlock code for that (I assume the same one that you request for an OEM unlock from Huawei), and Huawei closed down the site that generated the codes.
So I'm stuck in a weird limbo where I can't move forward (install Gapps and use my phone as normal) nor backwards (go back to EMUI8).
Does anyone have any idea how I can fix this situation?

Shadowsalyer said:
Hi all,
I installed TWRP on my Honor 7x, that went well.
Yesterday I decided to try to get Lineage working so:
- I installed EMUI 8, that went pretty smooth
- I installed Lineage OS 15.1. (without GApps)
- I flashed TWRP.
The issue I have now is that:
1) I can't install any APK in Lineage. Probably needs a factory reset/dalvik cache wipe.
2) I can't boot into TWRP. It stays stuck on the splash screen forever. This also means I can't install OpenGapps, SuperUser access (afaik), or anything else that requires root.
3) The bootloader is saying "FRP: Locked", which means I can't flash a new TWRP or a different ROM. When I try it fails with "command not allowed"
3) "fastboot oem unlock" fails saying I need to enable it in the developer options, but it's grayed out in the developer options because it's already unlocked.
4) I wanted to try the "dload" method but I can't find a good explanation on how to do it, and Huawei recently took all their downloads down, which means I can't find any UPDATE.app even if I knew how.
5) The other solution that *might* work is using "fastboot oem frp-unlock", but I need an unlock code for that (I assume the same one that you request for an OEM unlock from Huawei), and Huawei closed down the site that generated the codes.
So I'm stuck in a weird limbo where I can't move forward (install Gapps and use my phone as normal) nor backwards (go back to EMUI8).
Does anyone have any idea how I can fix this situation?
Click to expand...
Click to collapse
small chance you enable root from developer options. (i think it will be adb only)
if so , maybe can use adb shell and "dd" to write recovery to correct partition.
problem is many of the available twrp do not boot on custom rom .
example code. (if you do wrong , it may be bad)
Code:
dd if=/ext_sdcard/twrp_Recovery_ramdisk.img of=/dev/block/mmcblk0p32

It seems like I'm allowed to use dd in ADB shell, but before I run it, what do you mean by " problem is many of the available twrp do not boot on custom rom . "? I thought recovery was independent of the ROM? And does it mean flashing twrp like that could brick my phone?

Shadowsalyer said:
It seems like I'm allowed to use dd in ADB shell, but before I run it, what do you mean by " problem is many of the available twrp do not boot on custom rom . "? I thought recovery was independent of the ROM? And does it mean flashing twrp like that could brick my phone?
Click to expand...
Click to collapse
Like what you have , twrp stuck on splash screen

I managed to unlock the FRP with DC-unlocker. Sucks that it costs money but it worked!
Now Im stuck in a TWRP boot loop though.

Shadowsalyer said:
I managed to unlock the FRP with DC-unlocker. Sucks that it costs money but it worked!
Now Im stuck in a TWRP boot loop though.
Click to expand...
Click to collapse
At this point you should have access to fastboot though, right? I'd try a different TWRP instead. Perhaps try this one: https://drive.google.com/file/d/1ZYo7Ndte3vlLcUSadD6jIgfBi1oxa0Pb/view?usp=drivesdk

Just to clarify, it gets stuck on TWRP splash screen. When I turn off the phone, it immediately boots up again into TWRP. I tried getting into fastboot mode with all kinds of combinations of button presses, but no luck. Not even Volume Up + USB cable works

smokinjoe2122 said:
At this point you should have access to fastboot though, right? I'd try a different TWRP instead. Perhaps try this one: https://drive.google.com/file/d/1ZYo7Ndte3vlLcUSadD6jIgfBi1oxa0Pb/view?usp=drivesdk
Click to expand...
Click to collapse
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.

Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
I have seen this happen before , solution was to wait for dead battery, or disassemble to unplug battery
---------- Post added at 04:51 PM ---------- Previous post was at 04:47 PM ----------
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
This is because after the frp unlock, it needed to see a factory reset, and it usually needs to be done with stock recvery.
So will have to wait till battery is dead and and plug in usb while holding volume button. Should then load to fastboot. Where it is best to flash stock recovery to clear the recovery bootloop. The bootloop is do to the fact yo unlocked frp and now phone needs to wipe/data

Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
it sucks this happened to yu but im glad i am not the only one that dc-unlocker deleted my fastboot after i unlocked the frp and i cant boot fastboot for nothing if you find a solution please contact me. my phone is doing the exact same thing booting straight too twrp no mater what combinations i use

dcraffam said:
it sucks this happened to yu but im glad i am not the only one that dc-unlocker deleted my fastboot after i unlocked the frp and i cant boot fastboot for nothing if you find a solution please contact me. my phone is doing the exact same thing booting straight too twrp no mater what combinations i use
Click to expand...
Click to collapse
i just took mine apart and discconected the battery and still no luck that program deleted my fastboot

Please can you tell me the process to install twrp I have the L24

I waited all the way till the battery drained, stuck in the USB, and it booted to ROM! Sadly it immediately shut off again because the battery is dead (even with keeping the USB in). I'm going to keep trying though.

I can't get into fastboot mode. I can get into the ROM by letting the battery drain completely on the TWRP splashscreen, and then sticking in the USB cable. However, no button combination or "adb reboot bootloader" or rebooting to bootloader from the ROM brings me to the bootloader. I wonder if it's still there. Any ideas?

Shadowsalyer said:
I can't get into fastboot mode. I can get into the ROM by letting the battery drain completely on the TWRP splashscreen, and then sticking in the USB cable. However, no button combination or "adb reboot bootloader" or rebooting to bootloader from the ROM brings me to the bootloader. I wonder if it's still there. Any ideas?
Click to expand...
Click to collapse
Seems to be a f-up situation either way.
You have adb DD available, found out before.
Don't know if maybe flashing stock recovery is good idea at this point.
I think fastboot.img can be flashed with DD too, but don't try till someone can confirm.
If flash stock recovery clears the loops, maybe best to do full-ota manual flashing.

I managed to get an UPDATE.APP file and extract fastboot.img from it, as well as all the other .img files. If someone can tell me what to flash and how (with dd), I think Im set.

Shadowsalyer said:
I managed to get an UPDATE.APP file and extract fastboot.img from it, as well as all the other .img files. If someone can tell me what to flash and how (with dd), I think Im set.
Click to expand...
Click to collapse
Fastboot.img is the large part the bootloader. If flashing it goes bad, might be dead phone after, just rember that.
Will add a list of partition names and command s for you soon.
here is a list of oreo partitions and there /dev/blk/** number
and here is an example of code to save images with dd assuming you put the images on your extrnal-sdcard in folder called oreo-images
Code:
dd if=/dev/block/mmcblk0p5 of=/mnt/ext_sdcard/oreo-images/fastboot.img
Do that save first and compare the md5 of the file from update.app to this file.
or just check the md5 before making the copy
Code:
adb shell md5sum /dev/block/mmcblk0p5
If you are conviced you need to flash the images, here is example of writing the image assuming files are in sdcard folder oreo-update-images
Code:
dd if=/mnt/ext_sdcard/oreoupdate-images/fastboot.img of=/dev/block/mmcblk0p5
As I have said, this might be bad advise , I have not done fastboot.img flashing before. But on other devices it is same as lk.img or uboot.img, There is danger in flashing it incorrectly. That is why my suggestion was to flash no-check-recovery and do manael update with "echo -update_package" commands.
Along with the statement that fastboot.img is similar to lk.img or uboot.img on other phones, Your fastboot cannot be gone. because phone boots.
but do let us know how it goes.

I agree it would be better to flash recovery if possible. I assume I need the NoCheck-Recovery image from this thread? https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
And what partition do I have to flash it to? I'm guessing either /dev/block/mmcblk0p28 (erecovery ramdisk) or /dev/block/mmcblk0p32 (recovery ramdisk)? I'm not sure what the difference is between erecovery and normal recovery.
(didn't flash fastboot yet, wanted to see if recovery was doable).

Shadowsalyer said:
I agree it would be better to flash recovery if possible. I assume I need the NoCheck-Recovery image from this thread? https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
And what partition do I have to flash it to? I'm guessing either /dev/block/mmcblk0p28 (erecovery ramdisk) or /dev/block/mmcblk0p32 (recovery ramdisk)? I'm not sure what the difference is between erecovery and normal recovery.
(didn't flash fastboot yet, wanted to see if recovery was doable).
Click to expand...
Click to collapse
To recovery_ramdisk. 32
What about check md5 of fastboot partition, that will be helpful to know if it did get wiped out.?

Hmm seems like I'm not allowed to use dd after all:
HWBND-H:/ $ dd if=/storage/7C96-7E17/BND-RECOVERY-NoCheck.img of=/dev/block/mmcblk0p32
dd: /dev/block/mmcblk0p32: Permission denied
And here I was thinking I was close to solving it...
Also can't run md5sum on the fastboot partition, since that needs root as well.

X2 Pro: "Your device is corrupt. It can’t be trusted and may not work properly."

X2 Pro: "Your device is corrupt. It can’t be trusted and may not work properly."
Hi everybody,
my Aquaris X2 Pro worked fine with rooted BQ 1.7.3 firmware (Android 8.1 based) - Magisk was installed and worked fine and also the xposed framework.
Today the device was normally working as it suddenly just reboots
After that the usual "unlocked bootloader" screen appears but then it only shows a screen with the message "Your device is corrupt. It can’t be trusted and may not work properly."
I can select "continue" - but that only leads back to the "unlocked bootloader" warning screen --> a boot loop :crying:
Does anybody know how I can bring back my device back to work - without losing all my settings and stuff?
And any idea what happened (so that I can prevent it to do so in future)?

Hmm, I'm not 100% sure, but I think I saw that message / boot process once as I tried to root my X2 Pro.
I had done a
Code:
fastboot flashing unlock / unlock-critical
but no
Code:
fastboot oem unlock
(or the other way round? Definitely only done one of them - I was following instructions from a thread here)
and was trying to boot a magisk patched boot-img via
Code:
fastboot boot magisk_patched.img
So, it looked like the bootloader was "NOT fully" unlocked and it detected booting a "not correctly signed" bootloader.
Perhaps check your unlock status via
Code:
fastboot getvar all
But note - UNLOCKING again will wipe your data ... and can only be done if the setting in developer options is active (I fear that THAT may have changed on your device)
You could also try booting the second slot
Code:
fastboot getvar current-slot
and then
Code:
fastboot set_active a/b
(if current-slot gives a, boot b and vica versa).
Last idea: try flashing ONLY the stock boot.img. If you can do this, this should re-enable you to boot. You will loose root, but may be able to backup (most) of your settings via Helium

Thanks a lot for your help!
Inbetween I had to go the hard way and reflashed the newest BQ factory image v2.0.2 (based on Android 9) to both parts _a and _b - losing all my data...
after that I patched the boot.img for magisk and reflashed that to my _a boot partition (and still have the original boot.img in _b).
It did cost me a bit of my spare time - but it wasn't as hard as I expected...
I was able to restore a lot of my settings with Titanium backup....
merlinwv said:
I had done a
Code:
fastboot flashing unlock / unlock-critical
but no
Code:
fastboot oem unlock
Click to expand...
Click to collapse
That was exactly what I did - the first time I only did a "flashing unlock", no "unlock-critical" - so now I had to do it to flash the complete factory image, and therefore it wiped all my data again
merlinwv said:
I was following instructions from a thread here)
Click to expand...
Click to collapse
I used the BQ batch script to flash it, but did not execute the erase commands.
But that did not help to keep my data as I needed to execute a "unlock-critical"...
merlinwv said:
So, it looked like the bootloader was "NOT fully" unlocked and it detected booting a "not correctly signed" bootloader.
Click to expand...
Click to collapse
Hmm, it worked for several months without problems - don't know why it suddenly complained about it.
merlinwv said:
Perhaps check your unlock status via
Code:
fastboot getvar all
Code:
fastboot getvar current-slot
Click to expand...
Click to collapse
Very interesting commands which I didn't know - I already wondered how I can get that information
merlinwv said:
Last idea: try flashing ONLY the stock boot.img. If you can do this, this should re-enable you to boot. You will loose root, but may be able to backup (most) of your settings via Helium
Click to expand...
Click to collapse
That would be a great idea :good: which I could've tried - but I didn't...; maybe next time - although I hope the problem will never come back

Bodenseematze said:
Thanks a lot for your help!
...
I used the BQ batch script to flash it, but did not execute the erase commands.
But that did not help to keep my data as I needed to execute a "unlock-critical"...
Click to expand...
Click to collapse
You are most welcome
The erase commands are not the ones doing the factory-reset - if you want to keep your data during a "factory-flash" you need to comment/delete the lines which flash the userdata-partition.
But I do not know if you can flash the factory image without unlocked critical (=boot) flashing. I never tried this myself. Some phones allow flashing of correctly signed boot images even when critical is locked, others prevent ALL flashing then.
Of course, for "he who knows what he is doing" there is always the possibility to flash in EDL-mode (turn off, afterwards keep vol+, Vol- and Power pressed - will bring you to a special flash mode that allows flashing even when locked - but via a special serial interface etc. pp.). Google it - this would have helped you regarding "loose of userdata when doing unlock critical". But of course - you need to edit the file because in EDL mode, normally userdata is flashed, too.
Just something to keep in mind for the next time
Hmm, it worked for several months without problems - don't know why it suddenly complained about it.
That would be a great idea :good: which I could've tried - but I didn't...; maybe next time - although I hope the problem will never come back
Click to expand...
Click to collapse
I think that perhaps an update was installed (explanation for the reboot?!) that switched to the other boot-slot and did a more thorough check of the boot-chain. This was the reason to suggest trying the other boot-slot (which would then be the pre-update version, that may still boot - and even have root)

merlinwv said:
Of course, for "he who knows what he is doing" there is always the possibility to flash in EDL-mode
Click to expand...
Click to collapse
Again: very interesting information! :good:
merlinwv said:
I think that perhaps an update was installed (explanation for the reboot?!)
Click to expand...
Click to collapse
I hope that wasn't the reason, because I explicitly switched off all automatic updates. And I did not do a manual update!
merlinwv said:
that switched to the other boot-slot and did a more thorough check of the boot-chain. This was the reason to suggest trying the other boot-slot (which would then be the pre-update version, that may still boot - and even have root)
Click to expand...
Click to collapse
I tried to switch to the other slot and boot it - but that didn't help either and led to the same problem...
What I didn't tried was to only flash the boot.img - will do this next time