Related
So, I've been trying to flash CyanogenMod 12.1, since I'm still stuck on EMUI 3.1, because I can't flash OTA updates (I've tried everything, dload method, and yes I have unrooted and used the stock recovery)
Every time I try to flash a ROM via TWRP it turns off for a second and then boots back to TWRP starting screen. Also, when I boot my phone the boot animation's Honor H is red for some reason.
Thanks in advance!
Fonku said:
So, I've been trying to flash CyanogenMod 12.1, since I'm still stuck on EMUI 3.1, because I can't flash OTA updates (I've tried everything, dload method, and yes I have unrooted and used the stock recovery)
Every time I try to flash a ROM via TWRP it turns off for a second and then boots back to TWRP starting screen. Also, when I boot my phone the boot animation's Honor H is red for some reason.
Thanks in advance!
Click to expand...
Click to collapse
Are you sure you have the right boot.img and recovery.img?
Usually that symptoms are due to messed partitions.
Did you flash current img files or did you got them from a different rom version?
zinko_pt said:
Are you sure you have the right boot.img and recovery.img?
Usually that symptoms are due to messed partitions.
Did you flash current img files or did you got them from a different rom version?
Click to expand...
Click to collapse
Well, actually I once bricked my phone and had to restore through a TWRP backup, that only had the System and Boot partitions and it was the B130 version when I had B140, but it worked. So, do I need to completely flash everything or can I just pick up some files from somewhere?
Fonku said:
Well, actually I once bricked my phone and had to restore through a TWRP backup, that only had the System and Boot partitions and it was the B130 version when I had B140, but it worked. So, do I need to completely flash everything or can I just pick up some files from somewhere?
Click to expand...
Click to collapse
No, you need to have all the files from the same version.
Flash boot, recovery, cust and system.
zinko_pt said:
No, you need to have all the files from the same version.
Flash boot, recovery, cust and system.
Click to expand...
Click to collapse
So, is there a FULL KIW-L21C432B140 restore packet somewhere?
Thanks for your help!
Fonku said:
So, is there a FULL KIW-L21C432B140 restore packet somewhere?
Thanks for your help!
Click to expand...
Click to collapse
http://forum.xda-developers.com/honor-5x/how-to/repository-honor-5x-file-depot-t3328288
You can use B130 as it is also Lollipop. But all the img from the same rom. You can update to B350 manually after, but first you need a stable rom working.
Let us know man if you fixed your phone. So if not, we can give firther recommendations.
Sent from my Galaxy Tab 3 using XDA Labs
I just received the OTA update from 7.1.1 DP2 to MNF26F.
Here is the OTA url to download:
https://android.googleapis.com/pack.../2c6f100d0f9ef8ccee10d661b7454adb7161aa0e.zip
You can sideload it into your device and you will be on the official 7.1.1 release.
Just got it too. Only 27 megabytes.
Just download it... Where the downloaded OTA file located in our file system?
deani77 said:
Just download it... Where the downloaded OTA file located in our file system?
Click to expand...
Click to collapse
/data/data/com.google.android.gms/app_download/
If rooted on dp2 I can just download and install through TWRP, no?
I installed this and I got a boot loop, so careful. First time ever with an issue and I didn't bring my cable
thedead69 said:
I installed this and I got a boot loop, so careful. First time ever with an issue and I didn't bring my cable
Click to expand...
Click to collapse
Any more info? What version were you on before? Rooted? Used TWRP? What version of TWRP?
RaceFaceXC said:
If rooted on dp2 I can just download and install through TWRP, no?
Click to expand...
Click to collapse
No. ota only installs on stock images.
http://forum.xda-developers.com/showthread.php?p=62924118
Points 12/ and 13/
RaceFaceXC said:
Any more info? What version were you on before? Rooted? Used TWRP? What version of TWRP?
Click to expand...
Click to collapse
Rooted with SuperSU on DP2. Using flashfire
I got this OTA this afternoon. Stock DP2 on Verizon.
rchtk said:
No. ota only installs on stock images.
http://forum.xda-developers.com/showthread.php?p=62924118
Points 12/ and 13/
Click to expand...
Click to collapse
Thank.
I think I knew this at some point. Wasn't sure so that's why I asked.
thedead69 said:
Rooted with SuperSU on DP2. Using flashfire
Click to expand...
Click to collapse
Can you or someone help me??
Yesterday I received the notification. Download the file from here, as I am rooted, twrp and custome kernel.
I tried to flash this via flashfire, but after phone reboots, nothing happens... am I doing something wrong??
I open flashfire, choose Flash ZIP or OTA, choose the file, on the options I don't change anything (it only has Restore boot and recovery images ticked) and then on the main screen I press Flash. Then phone reboots and nothing happens, it enters again on android.
Someone??
onesolo said:
Can you or someone help me??
Yesterday I received the notification. Download the file from here, as I am rooted, twrp and custome kernel.
I tried to flash this via flashfire, but after phone reboots, nothing happens... am I doing something wrong??
I open flashfire, choose Flash ZIP or OTA, choose the file, on the options I don't change anything (it only has Restore boot and recovery images ticked) and then on the main screen I press Flash. Then phone reboots and nothing happens, it enters again on android.
Someone??
Click to expand...
Click to collapse
Can you enter bootloader or recovery with power/vol dn? If so, try sideloading a stock image? Or, if you can get into recovery restore with a nandroid backup?
Link ota for NEXUS 5X PLEASE
Link ota for NEXUS 5X PLEASE
hanibioud said:
Link ota for NEXUS 5X PLEASE
Click to expand...
Click to collapse
Wrong forum. This is for the Nexus 6P.
RaceFaceXC said:
Can you enter bootloader or recovery with power/vol dn? If so, try sideloading a stock image? Or, if you can get into recovery restore with a nandroid backup?
Click to expand...
Click to collapse
I didn't even try, cause I can enter on twrp fine. As I said, I have twrp and root. My sys is obviously modified. I'm not even trying to sideloaded over bootloader cause it wont work. The same thing on TWRP. I think that sideloading on TWRP only works with full OTAs and not with this one, that is an incremental OTA file, unless I'm completely wrong (I wish).
Anyone's got a changelog for those 26 MB of 'system stability and performance' ?
onesolo said:
Can you or someone help me?? Someone??
Click to expand...
Click to collapse
Download the full Google image- not OTA and flash that. If you can still boot the OS, use FF to flash boot, system, vendor. If you cannot boot OS, use ADB Fastboot to flash those partitions. Yes, I used the full image to go from DP2 to Public Release using FF. If more details are needed, check out the FF thread.
v12xke said:
Download the full Google image- not OTA and flash that. If you can still boot the OS, use FF to flash boot, system, vendor. If you cannot boot OS, use ADB Fastboot to flash those partitions. Yes, I used the full image to go from DP2 to Public Release using FF. If more details are needed, check out the FF thread.
Click to expand...
Click to collapse
yep, that is what I'm going to do... I guess not even FF can flash an mere incremental OTA (only full OTAs). bad luck
onesolo said:
yep, that is what I'm going to do... I guess not even FF can flash an mere incremental OTA (only full OTAs). bad luck
Click to expand...
Click to collapse
I didn't think flashing a ota over a rooted os, let alone a highly modified os/kernel/etc was a good idea with any utility.
Hi all.
Honor 9 with unlocked bootloader and FRP. I'm on 8.0.0.366, rooted via Magisk's modded ramdisk and stock recovery.
AFAIK Otas should not work anymore.
According to Huawei Firmware Finder, OTA update to .368 is available and approved for my IMEI.
I tried to upgrade putting main update.app file (from the full-ota-mf) in SDCARD\dload and booting in software update mode. Process fails with software update error at 5%.
Same with 367.
Furthermore there are multiple update.app in the downloadable files, how to flash all updates?
Is there a way to manually upgrade the phone without factory resetting it?
I would avoid installing a custom recovery, maybe in beta.
I'm also comfortable with bare fastboot, could I flash all needed images just skipping data?
Thanks
I had the same problem with update.
I used this tutorial https://forum.xda-developers.com/honor-9/how-to/how-to-root-honor-9-stf-l09c432b360a-t3778110 and flashed newest official ROM and Proto 8 kernel and it's awesome.
You can backup your data with hisuite and recover after fleshing. Worked for me very well.
procent said:
I had the same problem with update.
I used this tutorial https://forum.xda-developers.com/honor-9/how-to/how-to-root-honor-9-stf-l09c432b360a-t3778110 and flashed newest official ROM and Proto 8 kernel and it's awesome.
You can backup your data with hisuite and recover after fleshing. Worked for me very well.
Click to expand...
Click to collapse
Yep, I did the same. Got from b360 to b369 without factory reset. No issues.
1. TWRP 2. HuRUpdater with b369 from Firmware Finder 3. Magisk 4. Proto8 kernel+Split injector
All flashed from TWRP. TWRP flashed from fastboot. The same TWRP was renamed and put in the HuRUpdater folder.
sinraal said:
Yep, I did the same. Got from b360 to b369 without factory reset. No issues.
1. TWRP 2. HuRUpdater with b369 from Firmware Finder 3. Magisk 4. Proto8 kernel+Split injector
All flashed from TWRP. TWRP flashed from fastboot. The same TWRP was renamed and put in the HuRUpdater folder.
Click to expand...
Click to collapse
Just a bit curious....what is "split injector"??
Also HiSuite has option to upgrade and it worked for me.
badadam said:
Just a bit curious....what is "split injector"??
Click to expand...
Click to collapse
My bad, it is Spectrum injector and it is explained in the proto8 kernel thread.
sinraal said:
My bad, it is Spectrum injector and it is explained in the proto8 kernel thread.
Click to expand...
Click to collapse
Aha! OK, thanks for the reply
buteo said:
Hi all.
Honor 9 with unlocked bootloader and FRP. I'm on 8.0.0.366, rooted via Magisk's modded ramdisk and stock recovery.
AFAIK Otas should not work anymore.
Click to expand...
Click to collapse
OTA still should work with stock recovery, don't matter magisk
buteo said:
According to Huawei Firmware Finder, OTA update to .368 is available and approved for my IMEI.
I tried to upgrade putting main update.app file (from the full-ota-mf) in SDCARD\dload and booting in software update mode. Process fails with software update error at 5%.
Same with 367.
Furthermore there are multiple update.app in the downloadable files, how to flash all updates?
Click to expand...
Click to collapse
SDCARD\dload won't work with update.app from Full-ota-mf ; maybe the full-ota-mf-pv but it's not sure. I believe it only work in firmware mode (dload) with 'service repair firmware'.
buteo said:
Is there a way to manually upgrade the phone without factory resetting it?
Click to expand...
Click to collapse
normal ota(IF WORKING) or 'HuRUpdater + twrp'
Hey,
Has someone figured out how to root the phone after bootloader unlock? I saw some attempts in the GSI thread but it wolud be nice if somebody who done it publish a guide. [here or in the new thread]
This way it will be easier to find for future people to follow.
hi, i couldn't find a stock boot.img so far. seems we will have to wait some more time to be able to download latest firmware as full rom to get the boot.img, which we can then patch with magisk.
eagerly waiting for it, as i cannot hide my unlocked bootloader so far and some apps refuse to work now (also safetynet check fails)
juergenh99 said:
hi, i couldn't find a stock boot.img so far. seems we will have to wait some more time to be able to download latest firmware as full rom to get the boot.img, which we can then patch with magisk.
eagerly waiting for it, as i cannot hide my unlocked bootloader so far and some apps refuse to work now (also safetynet check fails)
Click to expand...
Click to collapse
You can use the Oxygen Updater app on google play to download the latest full rom. then use https://github.com/vm03/payload_dumper
to get the boot.img.
Manugamé said:
You can use the Oxygen Updater app on google play to download the latest full rom. then use https://github.com/vm03/payload_dumper
to get the boot.img.
Click to expand...
Click to collapse
Oxygen Updater says the Oneplus Nord 2 is not supported, and i couldn't find a Download of latest FullRom.
If you are already unlocked, download the boot image, patch with magisk etc Do you have to factory reset again?
moisthat said:
If you are already unlocked, download the boot image, patch with magisk etc Do you have to factory reset again?
Click to expand...
Click to collapse
That's the point....where and how to download the latest boot.img??
Bootloader is unlocked already.
That's why I want the latest full rom to extract it from that.
juergenh99 said:
That's the point....where and how to download the latest boot.img??
Bootloader is unlocked already.
That's why I want the latest full rom to extract it from that.
Click to expand...
Click to collapse
My reply was confusing, and I wasn't actually replying to you. Sorry about that. I don't know how or where to download the boot.img.
I am trying to ask the community if we need to factory reset again when we flash the patched boot.img. Or if the reset we did during unlock is the only reset needed.
moisthat said:
My reply was confusing, and I wasn't actually replying to you. Sorry about that. I don't know how or where to download the boot.img.
I am trying to ask the community if we need to factory reset again when we flash the patched boot.img. Or if the reset we did during unlock is the only reset needed.
Click to expand...
Click to collapse
unlocking the bootloader means to do a reset. flashing the boot.img does not cause a reset.
you just have root and working magisk after flashing and reboot
juergenh99 said:
unlocking the bootloader means to do a reset. flashing the boot.img does not cause a reset.
you just have root and working magisk after flashing and reboot
Click to expand...
Click to collapse
Well then, now I have joined you in the hunt for this bloody boot.img
HofaTheRipper said:
I am not respondible if you brick your device as there is no full rom download to revert all this.
i have done this:
- installed magisk on the phone and transfered the attached boot.img to the phone.
- patched it with magisk and transfered it to pc
Flashing:
- Unlock bootloader
- Reboot into bootloader
- Download https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
- `fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img`
- `fastboot flash boot magisk_patched_boot.img`
rebootet and root worked but wifi/bt was broken due some version conflict
Fix for wifi/bt for me was:
- unpack vendor.xz
- reboot to bootloader
- `fastboot reboot fastboot`
- `fastboot flash vendor vendor`
- reboot
My Build Version is DN2103_11_A.08.
Thanks to @phhusson for his help and for his files!
Click to expand...
Click to collapse
Found in this thread. Hope it will work for further updates.
There is a new OTA so please check that your still on may or july patch before using these:
***First and foremost I am NOT responsible for anything you do with the information posted, nor do I know how to help you unbrick your device, this is for testing purposes ONLY. If you cannot source the stock boot image for your current build/security patch wait for someone to post it and patch it yourself.****
It's always best to pull your own stock image and patch it with magisk YOURSELF. This is just to save some time for people who know exactly what their doing. If you have any doubt whatsoever DO NOT FLASH.
***Warning this MAY BRICK YOUR DEVICE IF YOUR NOT ON THE RIGHT SECURITY PATCH ***""
You will lose radios if you flash this to the wrong device, I have successfully recovered by flashing the correct boot image and have helped someone else recover with mismatching images by flashing the correct modems. I do not have the time to find the modems and troubleshoot your device so be careful please.
Flashing boot images from mismatching security patches on this device leads to no-boot and/or loss of radio functionality(cellular,wifi,Bluetooth).
The May patched boot image does NOT work for devices with the the latest security patch. Confirm that you are on the May 05, 2022 security patch BEFORE flashing MAY image. ( NOT JUNE OR JULY)
Works on build number GN2200_11_A.05
Only tested on TMOBILE variant and probably won't work for anything else(Metro apps are installed but disabled on the TMobile variant so it's possible that it MIGHT work for those devices but don't take that as any kind of reassurance that it would work***
The same boot image should work for both A and B slot but dont do anything unless you have a backup to recover from.
If you have read all the above and are 100% sure of what your doing, Flash the boot image, reboot and install magisk app as usual.
Magisk patched May boot image(should work for A/B):
magisk_boot_b.img
drive.google.com
[/URL]
here are the July (GN2200_11_A.06)Images:
Stock:
https://drive.google.com/file/d/1eALH0BxkhGPEBVSMLXfSOwp0xtySXLe4/view?usp=sharing
Magisk Patched July Image:
n20julybootmagisk.img
drive.google.com
**Edit**: According to JWhitley the images DO work for Metro by T-Mobile devices"
updated with july boot images
Darn, probably should've rooted first before updating to August patch.
PsYk0n4uT said:
updated with july boot images
Click to expand...
Click to collapse
You, kind stranger, are amazing! Thanks!
Rogo00 said:
You, kind stranger, are amazing! Thanks!
Click to expand...
Click to collapse
Flash vbmeta with
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
If you have issues and that should at least get you going if security checks prevent booting.
PsYk0n4uT said:
Flash vbmeta with
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
If you have issues and that should at least get you going if security checks prevent booting.
Click to expand...
Click to collapse
Where is the vbmeta image?
PsYk0n4uT said:
There is a new OTA so please check that your still on may or july patch before using these:
***First and foremost I am NOT responsible for anything you do with the information posted, nor do I know how to help you unbrick your device, this is for testing purposes ONLY. If you cannot source the stock boot image for your current build/security patch wait for someone to post it and patch it yourself.****
It's always best to pull your own stock image and patch it with magisk YOURSELF. This is just to save some time for people who know exactly what their doing. If you have any doubt whatsoever DO NOT FLASH.
***Warning this MAY BRICK YOUR DEVICE IF YOUR NOT ON THE RIGHT SECURITY PATCH ***""
You will lose radios if you flash this to the wrong device, I have successfully recovered by flashing the correct boot image and have helped someone else recover with mismatching images by flashing the correct modems. I do not have the time to find the modems and troubleshoot your device so be careful please.
Flashing boot images from mismatching security patches on this device leads to no-boot and/or loss of radio functionality(cellular,wifi,Bluetooth).
The May patched boot image does NOT work for devices with the the latest security patch. Confirm that you are on the May 05, 2022 security patch BEFORE flashing MAY image. ( NOT JUNE OR JULY)
Works on build number GN2200_11_A.05
Only tested on TMOBILE variant and probably won't work for anything else(Metro apps are installed but disabled on the TMobile variant so it's possible that it MIGHT work for those devices but don't take that as any kind of reassurance that it would work***
The same boot image should work for both A and B slot but dont do anything unless you have a backup to recover from.
If you have read all the above and are 100% sure of what your doing, Flash the boot image, reboot and install magisk app as usual.
Magisk patched May boot image(should work for A/B):
magisk_boot_b.img
drive.google.com
[/URL]
here are the July (GN2200_11_A.06)Images:
Stock:
https://drive.google.com/file/d/1eALH0BxkhGPEBVSMLXfSOwp0xtySXLe4/view?usp=sharing
Magisk Patched July Image:
n20julybootmagisk.img
drive.google.com
Click to expand...
Click to collapse
posting as a confirmation that the . img files provided here do play nice on the Metro by T-Mobile phone versions with currently
JWhitley said:
posting as a confirmation that the . img files provided here do play nice on the Metro by T-Mobile phone versions with currently
Click to expand...
Click to collapse
Thanks I was thinking they might since it's basically the same carrier but I didn't want to encourage anything untested
iKlover said:
Where is the vbmeta image?
Click to expand...
Click to collapse
Please see the response in the other thread
hawk1500 said:
Darn, probably should've rooted first before updating to August patch.
Click to expand...
Click to collapse
You can use DSU sideloader and boot a prerooted GSI, pull your stock images from whatever patch your on, easy way is to just use Partitions Backup and Restore app from playstore if you don't wanna use command line tools much. Install magisk and patch the extracted boot.img. save all your backups to your PC and flash the patched image in fastboot
PsYk0n4uT said:
You can use DSU sideloader and boot a prerooted GSI, pull your stock images from whatever patch your on, easy way is to just use Partitions Backup and Restore app from playstore if you don't wanna use command line tools much. Install magisk and patch the extracted boot.img. save all your backups to your PC and flash the patched image in fastboot
Click to expand...
Click to collapse
What "Partitions Backup and Restore app" are you talking about? This one? https://play.google.com/store/search?q=partitions+backup+and+restore&c=apps
famewolf said:
What "Partitions Backup and Restore app" are you talking about? This one? https://play.google.com/store/search?q=partitions+backup+and+restore&c=apps
Click to expand...
Click to collapse
yep