It seems that boot.img was changed in 8.1 update as I got Red State after flashing it on my phone. This one solved the problem.
https://mega.nz/#!c9IQjaaA!DlDzOlR7g8754jbR7mb6GbxOSojGfa9pWoV6-8nva-c
Related
i had the latest COS12 stock rom (rooted)
few days ago my battery ran out and after charging, the device got into bootloop.
i tried the onplus fix (https://forums.oneplus.net/threads/fix-stuck-at-boot-logo-boot-loop-random-reboot.160199/) which indeed fixed my bootloop and flashed KTU84Q (4.4.4), however, my wifi doesn't turn on now:
https://youtu.be/xchjcNl3pPk
i've tried clean flash again (with lolipop i get bootloop again)
i've also tried flashing color os (kitkat) and also no wifi
so far my problem seems to be:
on lolipop - bootloop
on kitkat - no wifi
any one has any idea?
matanp said:
i had the latest COS12 stock rom (rooted)
few days ago my battery ran out and after charging, the device got into bootloop.
i tried the onplus fix (https://forums.oneplus.net/threads/fix-stuck-at-boot-logo-boot-loop-random-reboot.160199/) which indeed fixed my bootloop and flashed KTU84Q (4.4.4), however, my wifi doesn't turn on now:
https://youtu.be/xchjcNl3pPk
i've tried clean flash again (with lolipop i get bootloop again)
i've also tried flashing color os (kitkat) and also no wifi
so far my problem seems to be:
on lolipop - bootloop
on kitkat - no wifi
any one has any idea?
Click to expand...
Click to collapse
A few questions:
What method are you using to switch between KK and LP? Fastboot (flashing stock images) or recovery?
If it's recovery, are you flashing the correct firmware/modem?
Are you still able to see your baseband and IMEI in About Phone?
IF you haven't flashed the stock images with fastboot that's the first thing you should try. I have detailed instructions in my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
first, thanks for your reply
second:
at first i did a clean flash from fastboot like this: https://forums.oneplus.net/threads/tutorial-flashing-a-factory-image-from-scratch.142870/
i also tried the oneplus one fix for bootloops that also use fastboot from here: https://forums.oneplus.net/threads/fix-stuck-at-boot-logo-boot-loop-random-reboot.160199/
later, i tried flashing from recovery, also the colorOS rom
the common for all is LP = bootloop \ KK = no wifi
when i'm on KK the phone works got, getting calls in and out
when i've flashed from recovery i've flashed only one zip file. didn't flash firmware nor modem
matanp said:
first, thanks for your reply
second:
at first i did a clean flash from fastboot like this: https://forums.oneplus.net/threads/tutorial-flashing-a-factory-image-from-scratch.142870/
i also tried the oneplus one fix for bootloops that also use fastboot from here: https://forums.oneplus.net/threads/fix-stuck-at-boot-logo-boot-loop-random-reboot.160199/
later, i tried flashing from recovery, also the colorOS rom
the common for all is LP = bootloop \ KK = no wifi
when i'm on KK the phone works got, getting calls in and out
when i've flashed from recovery i've flashed only one zip file. didn't flash firmware nor modem
Click to expand...
Click to collapse
Have you flashed the latest Lollipop build with fastboot as outlined in my guide?
not with your guide but with the guide in the link in my last post
also i don't remember seeing a userdata 64GB file in the lolipop image i had
matanp said:
not with your guide but with the guide in the link in my last post
also i don't remember seeing a userdata 64GB file in the lolipop image i had
Click to expand...
Click to collapse
That's because the LP images don't usually contain it, but the ones I link to do.
i'll try and report
thanks
i just got a message from oneplus support:
Hi Matan,
Thank you for reaching out. Sorry for the inconvenience that has caused to you. Rest assured that we will be providing you solutions in solving the issue.
You can also try to flash the device to the latest Oxygen OS, it is designed to fix common bugs that causes the issue.
To install OxygenOS on your OnePlus One, you need to flash the device. You may follow the guidance here:
https://forums.oneplus.net/threads/oxygenos-is-here-installation-guide.289398/
Please also note that since OxygenOS is a product from OnePlus therefore it is currently only available for OnePlus One.
Please don't hesitate to contact us for any update and feedback.
Thank you and have a good day.
Regards,
Jefflee
Click to expand...
Click to collapse
can i flash oxyOS (to check if it solve the problem) and after that flash your COS12 img with the fastboot commands or is there anything else i should know about?
flashed the latest COS12 version with your guide and i still have bootloops
Having this exact problem.... No wifi in CM11 and when updating tot CM12 getting boot looped.
Found a solution to your problem?
It's because of the modem files.. When u downgrade or upgrade from/to lollipop/kitkat u must flash the appropriate files!! Pm me if u want more info
Sent from my A0001 using Tapatalk
yes, i've open a ticket with oneplus one and their tech guy installed oxygenOS and it works well
Hey guys. I just rooted my PH-1 with magisk v-16 after updating to the OTA oreo 8.1 beta from essential. I've tried to flash an image file of the 8.1 beta image but when I boot back up it boot into nougat and my wifi is broken. Any help would be greatly appreciated.
pschambers.89 said:
Hey guys. I just rooted my PH-1 with magisk v-16 after updating to . I've tried to flash an image file of the 8.1 beta image but when I boot back up it boot into nougat and my wifi is broken. Any help would be greatly appreciated.
Click to expand...
Click to collapse
So you flashed the boot image of oreo on nougat?.. it's probably a missmatch that is happening. You should flash the same boot image that's made for the nougat build you're on.
Arju said:
So you flashed the boot image of oreo on nougat?.. it's probably a missmatch that is happening. You should flash the same boot image that's made for the nougat build you're on.
Click to expand...
Click to collapse
Sorry, I left this out of my original post. I had updated to the OTA oreo 8.1 beta from essential before rooting. So it was an 8.1 to 8.1 flash.
pschambers.89 said:
Hey guys. I just rooted my PH-1 with magisk v-16 after updating to the OTA oreo 8.1 beta from essential. I've tried to flash an image file of the 8.1 beta image but when I boot back up it boot into nougat and my wifi is broken. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Sounds like you are flashing one slot and booting in the the other slot.
Unlock the BL and manually flash the 8.1 rom image.
It flashes both slots.
Do you still have TWRP after installing Magisk? If so, you missed the step where you were supposed to flash the stock boot image in via TWRP (thus overwriting twrp) before installing Magisk.
I haven't messed this up yet on Oreo, but last time I did it on 7.1.1, this was the issue - OS looked more or less okay, but no wifi.
Hey guys,
Hopefully someone can help me with my problem. So i did the following:
To get rid of the 7 day Block of oem-unlocking on my s8+ i downgraded back to Nougat. From here on I flashed TWRP + rooted my device with magisk. After That i flashed the RENOVATE_ICE_G95X-7.5 rom + the Flashable_G95xF_FD_Firmware_TWRP_AQL5_r8 Firmware. I've let my Phone start up and went back to TWRP To Update the rom to RENOVATE_ICE_G95X-10.1. To this point everything Worked fine, the Phone Boots completely fine. Now to my problem: im Sitting on the actual stable rom but with the Baseband-version of Nougat which is AQL5. When i try to Flash the actual Firmware (CRC7 or CRD7) via TWRP my Phone gets stuck on the first Samsung Logo and Shows the following red Message: "Only official released binaries are allowed to be flashed". I would be glad for any help.
If you can find a standalone modem file from the ROM you mentioned you should be able to flash it in TWRP recovery. Last time I did this was on a Note 3. I think that the process should be the same with S8.
Can't seem to find one, but i found out that the same error occurs when installing other custom-roms like the King Oreo Rom which installs the newest Bootloader and Modem via Aroma installer. Only solution after that is to Flash Nougat again via Odin.
I wanted to know if someone successfully rooted Global MIUI with android 10. I tried flashing via twrp and patching boot.img (Magisk 20.3), but both failed, giving me bootloop.
Edit: https://github.com/topjohnwu/Magisk/issues/2492#issuecomment-593149828 This solved the issue.
Was this on miui 11.0.3.0. (QEEMIXM) I've been trying the normal way but the bootloop is happening.
TLDR
anyone get twrp 3.4 working with android 10? twrp released version 3.4 which supposedly supports android 10 and pixel 3a is a supported device. i flashed twrp and now twrp boots but nothing else does. its not a problem i can give it a try again just wondering how other people flashed it and got it to work.
long version:
TWRP released version 3.4 which supports android 10! yay im all happy and crap because pixel 3a is supported so i flash a kernel that supports LZMA compression. (i installed elemental x for android 10) and now i meet all the requirements. go to boot the .img file like they say using fastboot. i typed into ubuntu terminal "fastboot boot twrp3.4sargo.img" i get "error verifying the received boot.img: invalid parameter" this is the same exact error when booting older twrp recoveries because they arent compatible with android 10. not a problem though i thought! i have ex kernel manager so i can flash the twrp zip file through there! (thats what twrp website tells you to do if twrp had booted anyways so i thought well maybe i can skip that step since it isnt booting anyway and just flash the damn file) so i open ex kernel manager and flash the zip file! twrp boots im all happy and then i go to reboot and S#!+. nothing boots except twrp. anyone have any ideas on getting this to work since supposedly pixel3a android 10 is supported now?
Whenever Ive seen that error it means its not recognizing the partition youre trying to flash. Try adding the "a" or "b" after boot. So fastboot boot boot_a or boot_b depending on which is the active partition.
All this said, what are you trying to flash? A patched boot image or TWRP? If TWRP then you dont want to flash it to the boot partition, that goes to recovery.
Have you ever had to flash a full factory image of Android 10 (not just an OTA update)? TWRP will only work on Android 10 if the device was updated from Android 9 and still retains it's Android 9 file structure. I'm wondering if the file structure gets changed to the regular Android 10 file structure when you flash a full factory image vs an OTA update from Android 9 to Android 10 - I'm betting that it does. This would mean that TWRP would not work.
I honestly didn't even know this was released and I will try to install it on my 3A XL later today. I have flashed an Android 10 factory image since I moved from 9 to 10 via an OTA update, so I guess I will be able to test my hypothesis.
ctfrommn said:
Whenever Ive seen that error it means its not recognizing the partition youre trying to flash. Try adding the "a" or "b" after boot. So fastboot boot boot_a or boot_b depending on which is the active partition.
All this said, what are you trying to flash? A patched boot image or TWRP? If TWRP then you dont want to flash it to the boot partition, that goes to recovery.
Click to expand...
Click to collapse
Sorry been busy didn't have time to check this. I did try to flash to recovery. Flashing to boot was a typo. Same error result though. I'll try the a b partition thing later.
sic0048 said:
Have you ever had to flash a full factory image of Android 10 (not just an OTA update)? TWRP will only work on Android 10 if the device was updated from Android 9 and still retains it's Android 9 file structure. I'm wondering if the file structure gets changed to the regular Android 10 file structure when you flash a full factory image vs an OTA update from Android 9 to Android 10 - I'm betting that it does. This would mean that TWRP would not work.
I honestly didn't even know this was released and I will try to install it on my 3A XL later today. I have flashed an Android 10 factory image since I moved from 9 to 10 via an OTA update, so I guess I will be able to test my hypothesis.
Click to expand...
Click to collapse
Did you ever get it to work?
AudibleDruid said:
Did you ever get it to work?
Click to expand...
Click to collapse
I haven't tried yet. Honestly I'm not very motivated either. I'm 99.9% sure it won't work (because I have flashed a full factory image of Android 10 since taking the OTA update) and I don't feel like getting myself into a situation where I might have to reset my phone. I realize it shouldn't go that far, but the "reward" simply isn't worth the risk for me right now.
The Pixel-3a partition scheme was updated when upgraded to Android 10, i.e. the Pixel-3a is an exception to the rule that a device launched with Android 9 is compatible with TWRP 3.4. The Pixel-3a having Android 10 has the same structure like a device directly launched with Android 10 and so TWRP 3.4 will not work.