Hi everyone!
Is there somebody out there who can share a kernel backup img for 11.2.2.2 BA for flashing in fastboot? Need it to awake my bricked OP9P. Unfortunately there is still no MSM tool to bring it back to life. Which fastboot command should I use? Thanks in advance.
corneo said:
Hi everyone!
Is there somebody out there who can share a kernel backup img for 11.2.2.2 BA for flashing in fastboot? Need it to awake my bricked OP9P. Unfortunately there is still no MSM tool to bring it back to life. Which fastboot command should I use? Thanks in advance.
Click to expand...
Click to collapse
fastboot flash boot <filename>
stock boot img (BA)
patched boot img (BA)
zoman7663 said:
fastboot flash boot <filename>
stock boot img (BA)
patched boot img (BA)
Click to expand...
Click to collapse
Ok, it didn't work. So something else must have happened. So now I have to wait for an MSM tool. Hopefully one will come soon. Thank you anyway
corneo said:
Ok, it didn't work. So something else must have happened. So now I have to wait for an MSM tool. Hopefully one will come soon. Thank you anyway
Click to expand...
Click to collapse
No problem. What happened? Did you try to change slots on fastboot?
zoman7663 said:
No problem. What happened? Did you try to change slots on fastboot?
Click to expand...
Click to collapse
Yes, I tried that. Changing the slot also works. But then I don't get any further. The device always ends up in fastboot. I was a little curious and tried to undervolt gpu a bit on max frequency with KonaBess. The backed up stock image cannot be restored and that is the result. It doesn't work with the extracted boot.img from the official package either. Only the MSM tool seems to help. I do not know how to continue
corneo said:
Yes, I tried that. Changing the slot also works. But then I don't get any further. The device always ends up in fastboot. I was a little curious and tried to undervolt gpu a bit on max frequency with KonaBess. The backed up stock image cannot be restored and that is the result. It doesn't work with the extracted boot.img from the official package either. Only the MSM tool seems to help. I do not know how to continue
Click to expand...
Click to collapse
Gotcha, I tried messing with that also and couldn't get it to work. Changed slots and had to reflash full update package to restore slot to functioning again. I think it has something to do with the vendor_boot.img. But even with that pulled from the update zip I couldn't successfully fastboot flash that either and just reflashed the ROM.
zoman7663 said:
Gotcha, I tried messing with that also and couldn't get it to work. Changed slots and had to reflash full update package to restore slot to functioning again. I think it has something to do with the vendor_boot.img. But even with that pulled from the update zip I couldn't successfully fastboot flash that either and just reflashed the ROM.
Click to expand...
Click to collapse
Can I maybe ask for instructions? I just want to get the device working. Could you maybe write a short how-to please?
corneo said:
Can I maybe ask for instructions? I just want to get the device working. Could you maybe write a short how-to please?
Click to expand...
Click to collapse
I understand your pain, but if you already switched slots in fastboot and the device doesn't boot from either slot unfortunately I don't have any suggestions. I'm pretty sure without TWRP or the device booted into the OS there isn't a way to flash the ROM zip, until a fastboot flashable ROM is made or MSM tool is available.
Edit: I guess you could fastboot flash the various partitions from a payload dump of the ROM. But honestly I'm not sure what partitions are actually compromised from the KonaBess attempts. My guess is the vendor_boot.img (which is what gets backed up when you choose that in the app), but I couldn't get it to flash in fastboot, I kept getting a no such partition error. Which is funny cause it's in the ROM zip.
Maybe you can try fastboot flash boot_a\b, vendor_boot_a\b [file-path]. Try at your owm risk.
Ok, it worked. I flashed vendor_boot partition again (without a/b) and it boots now. Thanks for the quick and friendly help.
Any Idea where I could find vendor_boot for the op9? I fell into the same situation unfortunately.
I incorrectly assumed vendor_boot and boot would be the same .img and now i cannot leave fastboot mode.
It can I flash the European version over global?
I was basically fine changing the voltage but after getting a stable UV I got greedy for a higher clock frequency.
deadzombieseverywhere said:
Any Idea where I could find vendor_boot for the op9? I fell into the same situation unfortunately.
I incorrectly assumed vendor_boot and boot would be the same .img and now i cannot leave fastboot mode.
It can I flash the European version over global?
I was basically fine changing the voltage but after getting a stable UV I got greedy for a higher clock frequency.
Click to expand...
Click to collapse
Yes. EU version was tested by other members and will work. You can at the very least use it as a temporary measure.
deadzombieseverywhere said:
Any Idea where I could find vendor_boot for the op9? I fell into the same situation unfortunately.
(...)
Click to expand...
Click to collapse
Use the payload dumper to unpack payload.bin in the full OTA. In the output folder you will then find the vendor_boot.img. You then flash this via adb with the command "fastboot flash vendor_boot vendor_boot.img". Has worked for me
I want to thank everyone in the thread, firstly. I never thought I'd be tiptoeing into Python to get a phone working again. At the moment I'm fighting with Microsoft Visual distributions, but at least there's a path to follow.
Update: got it running and was able to dump the payload but come time to flash it says partition size unknown so I tried formatting and it wouldn't.
Time to wait for MSM I guess..
deadzombieseverywhere said:
[...]
Update: got it running and was able to dump the payload but come time to flash it says partition size unknown so I tried formatting and it wouldn't.
Time to wait for MSM I guess..
Click to expand...
Click to collapse
Have you already tried to change the slots? I switched from A to B and then flashed the vendor_boot image. Maybe try again, it could work ...
corneo said:
Have you already tried to change the slots? I switched from A to B and then flashed the vendor_boot image. Maybe try again, it could work ...
Click to expand...
Click to collapse
Yeah I tried switching slots. I tinkered with it a bit more, made sure I had the latest platform tools, tried different variations and slots. Wiped it in fastboot. Might try a different computer/usb cord tonight. But overall, I think I'm out of luck.
I finally got it running again. Had to use the AA which released today.
Related
Hi
Can anyone help with this ?
I am stuck on a Linux logo on my screen
I am unable to go into recovery or Bootloader mode
However if I Fastboot, it recognize the device
I tried flashing the recovery image and It Flashed successfully; Yet I cannot boot into Recovery
I tried Flashing the the Bootloader and the same
Funny thing is all Fastboot commands seem to work, like rebooting the Bootloader, but it goes straight to the Linux logo
see picture attached
Thank you.
Voyebanm said:
Hi
Can anyone help with this ?
I am stuck on a Linux logo on my screen
I am unable to go into recovery or Bootloader mode
However if I Fastboot, it recognize the device
I tried flashing the recovery image and It Flashed successfully; Yet I cannot boot into Recovery
I tried Flashing the the Bootloader and the same
Funny thing is all Fastboot commands seem to work, like rebooting the Bootloader, but it goes straight to the Linux logo
see picture attached
Thank you.
Click to expand...
Click to collapse
Did you erase the system? If not try to flash for fastboot just boot.img, maybe help you, if don't reboot flash the entire rom image
I was testing volte.zip. I already tried flashing the boot file, still nothing. I tried flashing miui global fastboot with miflash still no luck. It sees the device but flashed for 5s and then said successful.
did u check "clean all" and try edl mode (just a reminder,it happened to me many times,i was impatient/panicked forgot to check "clean all")
Voyebanm said:
I was testing volte.zip. I already tried flashing the boot file, still nothing. I tried flashing miui global fastboot with miflash still no luck. It sees the device but flashed for 5s and then said successful.
Click to expand...
Click to collapse
I have never seen this linux logo before on Mi Max and I can assure you I am on top of everything happening around it...
I think you did something hmmm... excuse me but stupid... That volte.zip is for kenzo and it flashes all partitions that you are not supposed to flash with anything but hydrogen specific images... Your only option is EDL mode flashing and I am not even sure if it is going to work.
Good luck...
nijel8 said:
I have never seen this linux logo before on Mi Max and I can assure you I am on top of everything happening around it...
I think you did something hmmm... excuse me but stupid... That volte.zip is for kenzo and it flashes all partitions that you are not supposed to flash with anything but hydrogen specific images... Your only option is EDL mode flashing and I am not even sure if it is going to work.
Good luck...
Click to expand...
Click to collapse
No Luck so far.
Voyebanm said:
No Luck so far.
Click to expand...
Click to collapse
That seem be a similar case at inverse (Hydrogen on Helium) but maybe help you: http://forum.xda-developers.com/showpost.php?p=68205960&postcount=24
SubwayChamp said:
That seem be a similar case at inverse (Hydrogen on Helium) but maybe help you: http://forum.xda-developers.com/showpost.php?p=68205960&postcount=24
Click to expand...
Click to collapse
I will give that a try. Thanks
http://en.miui.com/a-234.html
Install MiFlash from Xiaomi, download fastboot image and unpack it.
http://xiaomitips.com/guide/how-to-put-mi-max-into-edl-mode/
Boot to EDL mode with hard keys method, screen stays black, but Qualcomm QH USB device shows up in Device Manager/Ports. MiFlash fastboot image.
If you have 8 or newer Windows, you have to boot it driver signature verification disabled before MiFlash install:
http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
SubwayChamp said:
That seem be a similar case at inverse (Hydrogen on Helium) but maybe help you: http://forum.xda-developers.com/showpost.php?p=68205960&postcount=24
Click to expand...
Click to collapse
Thank you all for the suggestions, but this helped me to fix the problem and it was easy to perform
PS: I spoke too fast now my SIM card is not detected, in both slots
Voyebanm said:
Thank you all for the suggestions, but this helped me to fix the problem and it was easy to perform
PS: I spoke too fast now my SIM card is not detected, in both slots
Click to expand...
Click to collapse
What did you do to understand, maybe wrong firmware, maybe just a problem of modem partition, if you are using DualBootPatcher try with a CM based rom like primary, other possibility is to flash just NON-HLOS.bin of corrrect rom in fastboot mode, maybe wrong file in Update Firmware folder (in zip rom), go with a file explorer to /data/nvram if it`s generated for the new rom, take a backup first and delete after, reboot device (if this is the case) and check again your sim.
SubwayChamp said:
What did you do to understand, maybe wrong firmware, maybe just a problem of modem partition, if you are using DualBootPatcher try with a CM based rom like primary, other possibility is to flash just NON-HLOS.bin of corrrect rom in fastboot mode, maybe wrong file in Update Firmware folder (in zip rom), go with a file explorer to /data/nvram if it`s generated for the new rom, take a backup first and delete after, reboot device (if this is the case) and check again your sim.
Click to expand...
Click to collapse
Thank you though, I was able to resolved it by flashing the EFS backup that I had.
Problem SOLVED !!!
Thanks again for your Help.
I got a bricking when I tried flashing MIUI EU ROM over CM on a locked bootloader. Is there a way to flash the latest firmware files without also flashing a new boot image which could brick the phone? I had to do an EDL flash using MiFlash last time, I don't want to go through the hassle again.
I installed the 8.1 dp on my pixel 2 xl and I have decided to go back to android 8.0. I signed out of the beta and the OTA showed up as it was supposed to, from there I tried to install the downgrading OTA but it came up with a generic error (update was not able to be installed) from there I decided to try flashing the factory image and this error came up
writing 'bootb'...
FAILED (remote: No such partition.)
and when I rebooted it booted fine but was still on android 8.1. I also tried manually flashing the system partition as I noticed the script made no mention of flashing system, it came up with the error
sending sparse 'systemb' 1/4 (524284 KB)...
OKAY [ 16.552s]
writing 'systemb' 1/4...
FAILED (remote: No such partition.)
and once again after a reboot it went back to android 8.1. Any help is appreciated, thanks.
Download and flash the entire Factory image from Google's factory image page. That should work. However, this will wipe your phone.
I did flash the factory image which is what resulted in the partition error.
If you updated OTA, you can opt out of the beta, then go back to Software updates on your phone, and it will downgrade you back to 8.0.
Make sure you have the latest version of fastboot and flash the entire factory image using the flashall script. Should work.
Moostafa29 said:
If you updated OTA, you can opt out of the beta, then go back to Software updates on your phone, and it will downgrade you back to 8.0.
Click to expand...
Click to collapse
I already tried downgrading through the OTA, it came up with a generic error.
clnzx2 said:
Make sure you have the latest version of fastboot and flash the entire factory image using the flashall script. Should work.
Click to expand...
Click to collapse
It's been a while since i've updated adb, that might be the issue. I'll try it when i get home.
I think you're missing underscores. The partitions that you are flashing to should be boot_b and system_b. Also, it is crucial to use the latest version of fastboot (adb is not used).
I always open the flash all script to read the text then I do exactly that manually, and of course I skip the -w (which will wipe) through fastboot. Usually works great but I haven't tried yet on the Pixel 2 XL,
TheSt33v said:
I think you're missing underscores. The partitions that you are flashing to should be boot_b and system_b. Also, it is crucial to use the latest version of fastboot (adb is not used).
Click to expand...
Click to collapse
I'll update fastboot, maybe the flash-all script that is provided is incorrectly formatted so I'll try editing it to have underscores.
TheDonXR said:
I always open the flash all script to read the text then I do exactly that manually, and of course I skip the -w (which will wipe) through fastboot. Usually works great but I haven't tried yet on the Pixel 2 XL,
Click to expand...
Click to collapse
I tried doing this somewhat, I'll try going through this all the way but with the underscores as suggested above.
Afriendlytrashcan said:
I'll update fastboot, maybe the flash-all script that is provided is incorrectly formatted so I'll try editing it to have underscores.
I tried doing this somewhat, I'll try going through this all the way but with the underscores as suggested above.
Click to expand...
Click to collapse
I just downloaded the most recent factory image and the flash-all script doesn't mention flashing the boot image at all. It uses the update command to flash all of the necessary images. If you are looking at a script that flashes things differently, it's probably the wrong script.
If I had to take a guess, I'd say that the new version of fastboot knows to flash things differently with the new Pixels than with other devices, so the update command means something different to the old version than it does to the new version. When you tried the flash-all script initially, you were using the old version of fastboot so it tried to flash the image in a way that is not correct for the current pixels. My bet is that if you use the flash-all script with the newer fastboot, things will go better for you.
Afriendlytrashcan said:
I already tried downgrading through the OTA, it came up with a generic error.
It's been a while since i've updated adb, that might be the issue. I'll try it when i get home.
Click to expand...
Click to collapse
That is your problem. Update to latest tools and it will work. :good:
TheSt33v said:
I just downloaded the most recent factory image and the flash-all script doesn't mention flashing the boot image at all. It uses the update command to flash all of the necessary images. If you are looking at a script that flashes things differently, it's probably the wrong script.
If I had to take a guess, I'd say that the new version of fastboot knows to flash things differently with the new Pixels than with other devices, so the update command means something different to the old version than it does to the new version. When you tried the flash-all script initially, you were using the old version of fastboot so it tried to flash the image in a way that is not correct for the current pixels. My bet is that if you use the flash-all script with the newer fastboot, things will go better for you.
Click to expand...
Click to collapse
clnzx2 said:
That is your problem. Update to latest tools and it will work. :good:
Click to expand...
Click to collapse
Sounds good! I'll try it a bit later, my fingers have never been more crossed.
It worked! After updating fastboot the flash-all zip worked perfectly. Thanks everyone for your help!
Hey everyone. Just tried 9 DP1 and wanted to revert to 8.1 and just ran into this.
Since it can be overread easily: for the next one who's searching for this:
Edit the "flash-all.bat" (or .sh on Linux) and delete the "-w" after the fastboot command that flashes the ZIP.
You can wipe with fastboot or within recovery. If the system dows not boot, the Pixel 2 XL starts the recovery automatically and asks if you want to wipe.
Wasten over an hour, it's f*late and I'm tired, it's 1:16 AM here right now.
EDIT: You of course need to unlock and relock twice on the 2 XL
fastboot flashing unlock_critical
fastboot flashing unlock
fastboot flashing lock_critical
fastboot flashing lock
TimeTurn said:
Hey everyone. Just tried 9 DP1 and wanted to revert to 8.1 and just ran into this.
Since it can be overread easily: for the next one who's searching for this:
Edit the "flash-all.bat" (or .sh on Linux) and delete the "-w" after the fastboot command that flashes the ZIP.
You can wipe with fastboot or within recovery. If the system dows not boot, the Pixel 2 XL starts the recovery automatically and asks if you want to wipe.
Wasten over an hour, it's f*late and I'm tired, it's 1:16 AM here right now.
EDIT: You of course need to unlock and relock twice on the 2 XL
fastboot flashing unlock_critical
fastboot flashing unlock
fastboot flashing lock_critical
fastboot flashing lock
Click to expand...
Click to collapse
Sooooo....you were able to get back to 8.1 and then locked then unlocked the bootloader???
Badger50 said:
Sooooo....you were able to get back to 8.1 and then locked then unlocked the bootloader???
Click to expand...
Click to collapse
He said he was tired...
galaxys said:
He said he was tired...
Click to expand...
Click to collapse
Well shucks! ???
so actualy there is option to go back in versions?
that's nice!
I7210I said:
so actualy there is option to go back in versions?
that's nice!
Click to expand...
Click to collapse
It should be possible since the PDP1 is not yet official. More than likely, you'll need to do a full wipe, and clean flash to get back to 8.1 ?
Badger50 said:
It should be possible since the PDP1 is not yet official. More than likely, you'll need to do a full wipe, and clean flash to get back to 8.1 [emoji50]
Click to expand...
Click to collapse
so it's not quite works now?
in nexus it was worked right away
Sent from my Pixel 2 XL using Tapatalk
Hi, I manually updated my honor 7x (BND AL10 INDIAN) to EMUI 8 following the other post in this forum and after that I went on to flash TWRP recovery again from another post "complete_twrp_ramdisk.img" so that I could take full Nand backups and what not. But Here's the problem, When I try to flash the stock recovery back "BND_RECOVERY_NOcheck" which I flashed during upgrading to EMUI 8, it says "size of image is large than target device"
I tried this using boot fastboot command "fastboot flash recovery_ramdisk recovery.img" and also using the TWRP. It doesn't work either way. So I'm basically stuck with TWRP. The reason I want stock recovery is because
1. I can install OTA UPDATES on EMUI 8 (I actually got one)
2. I may want to just be on complete stock like locked bootloader, sock recovery etc...
Could any one help?? Maybe I need the right stock recovery file ?
BTW It's my first post ever so please go easy if I did any mistakes.
Could you share your twrp? Thanks!
Thetpcguy said:
Hi, I manually updated my honor 7x (BND AL10 INDIAN) to EMUI 8 following the other post in this forum and after that I went on to flash TWRP recovery again from another post "complete_twrp_ramdisk.img" so that I could take full Nand backups and what not. But Here's the problem, When I try to flash the stock recovery back "BND_RECOVERY_NOcheck" which I flashed during upgrading to EMUI 8, it says "size of image is large than target device"
I tried this using boot fastboot command "fastboot flash recovery_ramdisk recovery.img" and also using the TWRP. It doesn't work either way. So I'm basically stuck with TWRP. The reason I want stock recovery is because
1. I can install OTA UPDATES on EMUI 8 (I actually got one)
2. I may want to just be on complete stock like locked bootloader, sock recovery etc...
Could any one help?? Maybe I need the right stock recovery file ?
BTW It's my first post ever so please go easy if I did any mistakes.
Click to expand...
Click to collapse
"BND_RECOVERY_NOcheck" is nouget stock recovery.
Oreo update replaces all the partitions, including the recovery that you flashed in order to install the update.
The stock recovery can be extracted from "update.app" , the one inside the oreo "updateL22.zip"
holds said:
Could you share your twrp? Thanks!
Click to expand...
Click to collapse
It's here https://forum.xda-developers.com/honor-7x/development/oreo-twrp-complete-backup-t3764500
mrmazak said:
"BND_RECOVERY_NOcheck" is nouget stock recovery.
Oreo update replaces all the partitions, including the recovery that you flashed in order to install the update.
The stock recovery can be extracted from "update.app" , the one inside the oreo "updateL22.zip"
Click to expand...
Click to collapse
Hi, I'm downloading that UPDATEL22.ZIP right now and Can I extract this with any unzip/unrar program? What will be the name of that recovery? is it going to be "recovery"? The thing is I've never extracted anything from a ROM so I have not idea.
Thetpcguy said:
Hi, I'm downloading that UPDATEL22.ZIP right now and Can I extract this with any unzip/unrar program? What will be the name of that recovery? is it going to be "recovery"? The thing is I've never extracted anything from a ROM so I have not idea.
Click to expand...
Click to collapse
you should already have the update.zip.
use same one you "manualy" installed.
winrar did not work for me but 7-zip did.
there is also rom extractor built into "multi-tool" and stand alone extractor around here some where.
I found it here
the name is just like the twrp you flashed and just like the partition that you flashed. (recovery_ramdisk.img)
Thetpcguy said:
Hi, I'm downloading that UPDATEL22.ZIP right now and Can I extract this with any unzip/unrar program? What will be the name of that recovery? is it going to be "recovery"? The thing is I've never extracted anything from a ROM so I have not idea.
Click to expand...
Click to collapse
Hi, so I figured Huawei update extractor app is the way to do it but I have a Mac and there doesn't seem to be a Mac version? is there a way to do it on android or Mac?
mrmazak said:
you should already have the update.zip.
use same one you "manualy" installed.
winrar did not work for me but 7-zip did.
there is also rom extractor built into "multi-tool" and stand alone extractor around here some where.
I found it here
the name is just like the twrp you flashed and just like the partition that you flashed. (recovery_ramdisk.img)
Click to expand...
Click to collapse
Hi, Thanks for all your replies. After doing a bit of search, I managed to get it extracted on my android using zarchiver app and I copied the recovery_ramdisk.img from that BNDL22.ZIP and when I tried flashing it using the fastboot command "fastboot flash recovery_ramdisk recovery.img" It went ok and It got installed but when I tried to boot into recovery, I got this screen "ERROR MODE" ATTENTION ETC.. I don't know where I'm going wrong?
Thetpcguy said:
Hi, Thanks for all your replies. After doing a bit of search, I managed to get it extracted on my android using zarchiver app and I copied the recovery_ramdisk.img from that BNDL22.ZIP and when I tried flashing it using the fastboot command "fastboot flash recovery_ramdisk recovery.img" It went ok and It got installed but when I tried to boot into recovery, I got this screen "ERROR MODE" ATTENTION ETC.. I don't know where I'm going wrong?
Click to expand...
Click to collapse
I dont know.
The new way to boot to recovery was written in other thread as "hold both volume buttons & power button"
not sure if it was a problem with extraction or not, but attached is the recovery I extracted. do not have it installed. I dont even have oreo installed., I'm still pulling files together and reading the update-scripts and trying to convince myself if it is worth trying it.
https://www.androidfilehost.com/?w=files&flid=262391
I have now jumped on board and did oreo conversion on L24, then flashed RR. I went and installed the oreo recovery, then back to this stock recovery. It worked fine for me.
mrmazak said:
I dont know.
The new way to boot to recovery was written in other thread as "hold both volume buttons & power button"
not sure if it was a problem with extraction or not, but attached is the recovery I extracted. do not have it installed. I dont even have oreo installed., I'm still pulling files together and reading the update-scripts and trying to convince myself if it is worth trying it.
https://www.androidfilehost.com/?w=files&flid=262391
I have now jumped on board and did oreo conversion on L24, then flashed RR. I went and installed the oreo recovery, then back to this stock recovery. It worked fine for me.
Click to expand...
Click to collapse
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Thetpcguy said:
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Click to expand...
Click to collapse
i am wipeiing my data it always show faild plss help my device is dead
Thetpcguy said:
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Click to expand...
Click to collapse
Which perticular file should i flash for stock recovery please. There are 4-5 files. Pl help. I am on RR and want to flash system.img to go back to oreo beta. But i think i do not have stock recovery as i had tried to flash twrp. Pl help
Thetpcguy said:
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Click to expand...
Click to collapse
Hey bro thefe are too many files there will it flash through fastboot or twrp and how to flash one by one pls help me
Hello all,
thanks for all the info in this thread.
I bricked my Honox 7x (BND-LC21) by trying to go Oreo.
The installation went halfway through, but now I can't complete (missing info howto flash bootloader / kernel) and I also can't go back as the partition layout has already changed to oreo style.
Steps done so far:
- unlocked boot loader
- installed twrp
- extract system image and recovery image from oreo update zip
getting the phone in fastboot mode i can successfully run
fastboot flash recovery_ramdisk recovery_ramdisk.img (i can also flash old recoveries this way, but none of them will successfully boot into recovery mode)
fastboot flash system system.img
either way, the system will not boot afterwards.
how do I manually flash bootloader / kernel on the oreo partition layout?
erecovery and hisuite won't recover my phone either...
Any hints appreciated
Aibiman
mrmazak said:
I dont know.
The new way to boot to recovery was written in other thread as "hold both volume buttons & power button"
not sure if it was a problem with extraction or not, but attached is the recovery I extracted. do not have it installed. I dont even have oreo installed., I'm still pulling files together and reading the update-scripts and trying to convince myself if it is worth trying it.
https://www.androidfilehost.com/?w=files&flid=262391
I have now jumped on board and did oreo conversion on L24, then flashed RR. I went and installed the oreo recovery, then back to this stock recovery. It worked fine for me.
Click to expand...
Click to collapse
Can I flash just the stock recovery to my phone and if so is it the recover_ramdis.img, or do I need to flash them all. I'm on mostly stock bnd-l24. Unlocked bootloader TWRP and magisk for root. There's a new update and i wanted to flash stock recovery so I could update.
kingd421 said:
Can I flash just the stock recovery to my phone and if so is it the recover_ramdis.img, or do I need to flash them all. I'm on mostly stock bnd-l24. Unlocked bootloader TWRP and magisk for root. There's a new update and i wanted to flash stock recovery so I could update.
Click to expand...
Click to collapse
Yes that is the recovery.
But if you have root, update not going to work
mrmazak said:
Yes that is the recovery.
But if you have root, update not going to work
Click to expand...
Click to collapse
Will uninstalling magisk fix that or does the boot image have to be reflashed. Thank you for the quick response
kingd421 said:
Will uninstalling magisk fix that or does the boot image have to be reflashed. Thank you for the quick response
Click to expand...
Click to collapse
From magisk manager app should be a restore images option
mrmazak said:
From magisk manager app should be a restore images option
Click to expand...
Click to collapse
Sounds good. I appreciate it.
aibiman said:
Hello all,
thanks for all the info in this thread.
I bricked my Honox 7x (BND-LC21) by trying to go Oreo.
The installation went halfway through, but now I can't complete (missing info howto flash bootloader / kernel) and I also can't go back as the partition layout has already changed to oreo style.
Steps done so far:
- unlocked boot loader
- installed twrp
- extract system image and recovery image from oreo update zip
getting the phone in fastboot mode i can successfully run
fastboot flash recovery_ramdisk recovery_ramdisk.img (i can also flash old recoveries this way, but none of them will successfully boot into recovery mode)
fastboot flash system system.img
either way, the system will not boot afterwards.
how do I manually flash bootloader / kernel on the oreo partition layout?
erecovery and hisuite won't recover my phone either...
Any hints appreciated
Aibiman
Click to expand...
Click to collapse
can you in to TWRP?
Due to limitations with my chromebook i am force to flash a factory image manually. flash all causes an I/O error. can someone list all the commands to flash it all manually. was on dp3 and tried to boot a custom rom.
i would like to go back to most current june update if possible.
everything i have found online is for older devices
motcher41 said:
Due to limitations with my chromebook i am force to flash a factory image manually. flash all causes an I/O error. can someone list all the commands to flash it all manually. was on dp3 and tried to boot a custom rom.
i would like to go back to most current june update if possible.
everything i have found online is for older devices
Click to expand...
Click to collapse
How did you get to DP3? Did you enroll in the beta program?
Badger50 said:
How did you get to DP3? Did you enroll in the beta program?
Click to expand...
Click to collapse
yes and weirdly using a factory image on my Mi A1 gave no error
motcher41 said:
yes
Click to expand...
Click to collapse
Then just unenroll from the beta program. You'll then get an OTA that will wipe your phone, and put you back on 8.1 :good:
Badger50 said:
Then just unenroll from the beta program. You'll then get an OTA that will wipe your phone, and put you back on 8.1 :good:
Click to expand...
Click to collapse
i would but i am currently soft bricked. have access to bootloader only
even tried to sideload an ota image but no luck there either. either have to flash it all manually or buy a real pc
motcher41 said:
even tried to sideload an ota image but no luck there either. either have to flash it all manually or buy a real pc
Click to expand...
Click to collapse
Oh boy, your in pickle then! Then I suppose you'll have to....
fastboot format userdata
Then fastboot each image, which I think there are 21 of them if memory serves.
The command lines aren't that hard, just a lot of them. Start with the bootloader, then radio, then just start going down the list, ie.......
fastboot flash bootloader bootloaderxxxxx.img
fastboot reboot bootloader
fastboot flash radio radioxxxxxxx.img
fastboot reboot bootloader
Then just start flashing all the images from the secondary zip you'll find in the factory image.
but are they all the same target as the .img name
Badger50 said:
Oh boy, your in pickle then! Then I suppose you'll have to....
fastboot format userdata
Then fastboot each image, which I think there are 21 of them if memory serves.
The command lines aren't that hard, just a lot of them. Start with the bootloader, then radio, then just start going down the list, ie.......
fastboot flash bootloader bootloaderxxxxx.img
fastboot reboot bootloader
fastboot flash radio radioxxxxxxx.img
fastboot reboot bootloader
Then just start flashing all the images from the secondary zip you'll find in the factory image.
Click to expand...
Click to collapse
wow that actually worked....the flashing of everything to slot by name except the system_other
format userata command gave an error too
motcher41 said:
wow that actually worked....the flashing of everything to slot by name except the system_other
format userata command gave an error too
Click to expand...
Click to collapse
Hey, as long as it worked your good. Welcome :good:
Yeah my format userdata may have been off. I was going by memory from my 6p. P2XL might be different. Sorry.
Yesterday it happend suddenly: Battery 5% left, just a quick newsarticle before bed and it left me.
At first it didn't even take any charge. Booted in recovery and it's at 40% now.
But booting doesn't work.
OP Logo, bootanimation for around 20 seconds, repeat...
What I tried:
Power off, reboot
changed active slot
Flash the boot image what was last downloaded by me a while ago (semed to be Boot 12.C44_BA, not sure)
Flash the magisk image
Flashed a C47 image
no difference at all, same boot pattern.
A little sidenote:
I have magisk on my op9p, worked fine. a recent ota update failed repeatedly installing in defaulkt way. at boot i had to switch active slot in fastboot a few times. then it booted to current firmware.
I am wondering why i get the same issue independent from the boot.img.
Why did the low battery started this problem at all? How can i be sure to have the right boot.img flashed.
And most important: how can i boot into andoird again?
let me know if you need more information.
Thanks in advance!
edit:
is it possible to install twrp and backup/restore later the important data?
use msm tool and make all new
ChrisFeiveel84 said:
use msm tool and make all new
Click to expand...
Click to collapse
thanks for the hint! I read about this tool. But this means a full wipe of system and user data, right? any chance to avoid this and rescue images before setting up new?
I see a few possibilities to get closer:
i can boot twrp via fastboot. wiping data seemed to not help.
mounting userdata doesn't work because it needs a pin code which is not my system code.
maybe i have the wrong boot.img? can i find out which firmware version is installed via twrp and flash the right image afterwards?
Speaka said:
I see a few possibilities to get closer:
i can boot twrp via fastboot. wiping data seemed to not help.
mounting userdata doesn't work because it needs a pin code which is not my system code.
maybe i have the wrong boot.img? can i find out which firmware version is installed via twrp and flash the right image afterwards?
Click to expand...
Click to collapse
TWRP doesn't work with A12 only A11 at the moment.
Have you tried getting your hands on the C.62 firmware to local update?
luckylui said:
TWRP doesn't work with A12 only A11 at the moment.
Have you tried getting your hands on the C.62 firmware to local update?
Click to expand...
Click to collapse
thanks for pointing that out!
did not try yet. can you please point me to a howto thread?
what would be the way to update if i have no system access?
Speaka said:
thanks for pointing that out!
did not try yet. can you please point me to a howto thread?
what would be the way to update if i have no system access?
Click to expand...
Click to collapse
Google search "Tool ALL IN ONE" download it and install. Download the C.62 firmware from one of the threads in the forum. Open the tool you installed earlier select generic device from the pop-up. Click on "advanced options" in the tool and that'll bring you to "adb sideload". I hope that works for you!
This sounds promising. I will try that later. To be sure: This will keep personal data like an usual ota update?
Edit: I'm still stuck. Heres what i do: Boot twrp (not install) from fastboot. in twrp start adb sideload. open the toolaio, generic device, advanced options, select firmware.zip and click flash under sideload. Than it prompts "phone is not in adb or fastboot mode". In the main window it show the device id and "adb sideload".
what am i missing?