Device restart problem after 8.1.1 feb update - Nexus 6P Q&A, Help & Troubleshooting

i have flashed the FireHound-v4.1.1 [Angler] rom and gapps and i was on 8.1.0 (OPM5.171019.015, Feb 2018) so i didn't flash vandor image in first time and got error in firstboot lockscreen that i have to flash the opm 3.17 . By using twrp image flash option i flash opm 3.17 vandor then again after advance wipe FireHound rom flashed. Now device not booting up after lock screen of firehound it goes back to twrp after 2 hrs of waiting to device to bootup i flash stock 8.1.0 (OPM5.171019.015, Feb 2018) again.Now my device is keep on restarting it not even going to recovery i can go to bootloader only. I have unlocked bootloader and fastboot flash method enabled. Please help me as its my beloved device. i have already made my backup of all data.

Got any solution ?? I have the same problem.

I had a similar issue but it was on nougat 7.1.2 . Anyway i flashed the factory image and the first time it bootlooped but on reflashing the same factory image around 3rd time the phone booted up. So try that and see if you can fix it.

Related

Flashing stock images problem.

I was systemless-rooted, with xposed installed on 6.0.1 with the December security patch.
I went ahead and tried to flash the February Security patch through Fastboot (Followed the steps in order to not get my data wiped)
Tried to boot, and was told encryption failed, so I basically had to wipe my phone completely.
Now I have a problem. Since I am on the latest build number (mmb29q) I don't know which custom boot image it is that I have to use in order to flash a custom recovery and root my phone again.
If you jst flash recovery via fastboot then flash latest supersu and you'll be good. 2.67. When twrp asks to root select no and reboot and you will be good or you could use a custom kernel and su or I came across this
http://forum.xda-developers.com/showthread.php?t=3306684 I think it's what your looking for.
Edit
DoUknoGREG said:
I was systemless-rooted, with xposed installed on 6.0.1 with the December security patch.
I went ahead and tried to flash the February Security patch through Fastboot (Followed the steps in order to not get my data wiped)
Tried to boot, and was told encryption failed, so I basically had to wipe my phone completely.
Now I have a problem. Since I am on the latest build number (mmb29q) I don't know which custom boot image it is that I have to use in order to flash a custom recovery and root my phone again.
Click to expand...
Click to collapse
I'm not sure what the problem is here, you don't need a custom boot.img to install TWRP, just flash it. You don't need a custom boot.img for root either, systemless SuperSU patches the boot.img for you. It's all in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

Safetynet fails on clean Nougat install

I just updated to Nougat and safetynet fails. I have not even rooted or put TWRP back on.
I'm using the EU ROM.
Previously I updated from 6.0 Sept to 6.0 Dec patch by flashing the boot and recovery image (from the Sept. firmware) on the device, then taking the update. And then flashing TWRP and magisk again.
6.0 Dec. to Nougat didn't go as well. I flashed the boot and recovery but the phone didn't boot... I used the Sept firmware as I do not have the Dec. firmware (I'm very adamant about getting the latest stock ROM for flashing purposes..). Anyways, so I had to flash the entire 6.0 Sept ROM again (I did not wipe my data) and then update to the December patch and then to Nougat. Would have been so much easier if I had the December patch ROM to flash...
I actually uninstalled magisk before all of this. But actually, magisk/root would be gone after flashing the boot image anyway.
After updating to Nougat I have not done any modding, but safetynet fails... Why is this? And I can only start from scratch from the 6.0 September patch...so starting over is not sounding good.
Possibly due to the unlocked bootloader from reading other threads...
d.casper.b said:
I just updated to Nougat and safetynet fails. I have not even rooted or put TWRP back on.
I'm using the EU ROM.
Previously I updated from 6.0 Sept to 6.0 Dec patch by flashing the boot and recovery image (from the Sept. firmware) on the device, then taking the update. And then flashing TWRP and magisk again.
6.0 Dec. to Nougat didn't go as well. I flashed the boot and recovery but the phone didn't boot... I used the Sept firmware as I do not have the Dec. firmware (I'm very adamant about getting the latest stock ROM for flashing purposes..). Anyways, so I had to flash the entire 6.0 Sept ROM again (I did not wipe my data) and then update to the December patch and then to Nougat. Would have been so much easier if I had the December patch ROM to flash...
I actually uninstalled magisk before all of this. But actually, magisk/root would be gone after flashing the boot image anyway.
After updating to Nougat I have not done any modding, but safetynet fails... Why is this? And I can only start from scratch from the 6.0 September patch...so starting over is not sounding good.
Possibly due to the unlocked bootloader from reading other threads...
Click to expand...
Click to collapse
I have the same issue with safetynet, I could only fix it while flashing this: Universal SafetyNet Fix v2 beta 4 !
https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
An unlocked bootloader will cause SafetyNet to fail in Nougat, at least in some devices (Pixel/Nexus, HTC 10/U11, OP3/3T too), could well be the reason it is failing.

OnePlus 5 stuck on stock rom after trying brick cant flash anything now

So im trying to root my oneplus 5 and i started off by using Lineage OS but i wasnt too happy with it and i liked Oxygen OS much better so i decided to go back to it and while doing so like an idiot i wiped everything in twrp including the storage with all my ROM files and the phone was bricked and after a long struggle i used the unbrick tool which is called MSM tool which installed oxygen 4.5.8 using some some Qualcomm mode or something and it booted and worked fine but ever since i wasnt able to download the oxygen 5.1.1 update through the phones update section, it reaches 100% and says signature verification failed and goes back to 5%. So i tried downloading the latest Open Beta from the OP site and tried local upgrade which said installation failed so i try installing it locally through the Oxygen Recovery but again Installation failed so i try unlocking the bootloader again and installing it through twrp and it just keeps showing the boot animation forever( i know people say be patient but i waited for 20 mins+). So i decided to use the unbrick tool again and now im stuck on the OOS 4.5.8 unable to update the phone.
I tried to flash the latest oreo through twrp several times and just tried flashing it through so many ways where none worked , even adb sideloading it worked till 47% and said installation failed and everytime this happens i have nothing left to do but use the tool and unbrick it again and this takes so much time as i have to unbrick and then do the first setup and then go to fastboot and unlock the bootloader and do the setup again and transfer the files and then install twrp and flash.
Nothing has worked so far
And now even when i go back to the 4.5.8 stock after unbricking for some reason it just doesnt connect to any wifi , it just says Connecting and then saved and then disabled and repeat, only my mobile data works.
I tried to flash lineage again but got an error 7 with it or something and im back to the stock unbricked state without wifi and all i can do is unlock bootloader and install twrp.
If anybody has any suggestions and can help me please do so immediately. I require my phone urgently and need to fix this fast.
Thank You !
(btw im in India and do local service centres fix such issues?)
Make sure you use newest twrp. And also flash firmware for 5.1.1
Vika__ said:
Make sure you use newest twrp. And also flash firmware for 5.1.1
Click to expand...
Click to collapse
i am using the latest codeworkx twrp 3.2.1 and when should i flash firmware? can you just give the process i should do? stuck at 4.5.8 without wifi with twrp and unlocked bootloader
Wipe everything except internal storage, after that click format data and type "yes" to accept. Then download oos 5.1.0 firmware from here https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/cheeseburger/firmware/ and lineageos 15 (or any rom you want now), gapps and move all 3 packages to your phone. Flash firmware first and then reboot to recovery. Then flash rom or gapps and reboot
You have to flash the latest TWRP from twrp.me, then download the latest OxygenOS build. Reboot into TWRP, wipe data, cache, system and flash the latest build, then just go to wipe > format data, type "yes" and reboot
Lol man your OP5 is not bricked, if you can boot on TWRP, you can install all that you want
I advise to Format Data/Storage, Wipe everything and install xXx 10.7 (OOS Custom with a great Aroma installer), choose decrypted, it's better if you want swtich rom in the future AOSP > OOS > AOSP
bro i have same probleme after install any rom custom or official , always stuck on boot logo , any solution ?
no solution??

[los15.1] Signal loss after wrong firmware flashing

Hi everyone, i messed up today, i was running LOS 15.1 +twrp +unlocked. Everything was fine till i updated lineage Os to last version and i decided to flash the last firmware dec 2018 for 9.0 android. Since i lost audio while calling and fingerprint. I decided to flash nov-18 Firmware, it didn't solved the issue, then
I decided to flash stock rom using Mi flash the following versions with the clean_all script.
- tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794
- tissot_images_8.1.10_20180110.0000.00_8.0_8ea503201b
Since still bootlooping, no network, the screen is always locking itself....
The IMEI are still here, i just want to downgrade to earlier firmware
I unfortunately have no twrp backup of the EFS partition.....
my mistake...thanks for your help.

Few questions before rooting/twrp

I just purchased the ph1 and plan on rooting the device and also flashing twrp. I've found the guides and everything seems pretty straight forward. The phone should be arriving tomorrow so at this point I'm unsure of the build it will have when I receive the device. I noticed a thread regarding the February update not working with twrp. Has this issue been resolved or will I need to flash to the January version to complete the task? Is the February and January builds mentioned the most recent updates for the device? I've found the links to the essential website but it gives me a error that its server IP cannot be found so I've been unable to check it. Is the site going to be down indefinitely due to no longer supporting the device? Does anyone have a link to the updates hosted elsewhere? The device was listed as GSM unlocked and did not mention any carrier tied to it so I'm assuming it's a factory unlocked device but will have to verify upon receiving it. Is the updates carrier dependant or do they all utilize the same files? Whats the consensus on roms/kernals on this device as opposed to rooting and using twrp on the most recent stock builds? Which Rom would you recommend if I do decide to go that route? Thanks for any advice you can offer, it's greatly appreciated.
Count me in as needing to know this information. I am planning on installing the Android 11 release when it comes out this month and I am currently running 10 Build number QQ1A.200105.032 with February 5 2020 security patch level. Will I need to install the January build to install Android 11?
SirDigitalKnight said:
Count me in as needing to know this information. I am planning on installing the Android 11 release when it comes out this month and I am currently running 10 Build number QQ1A.200105.032 with February 5 2020 security patch level. Will I need to install the January build to install Android 11?
Click to expand...
Click to collapse
I ended up receiving the device and it had Android 8 out of the box. I received a update that took me to Android 9 which was roughly 1100mb and another to Android 10 which was a little over 1000mb. The second update automatically included the February security patch. Rather than downgrade to January, I simply patched a February boot image with magisk and flashed with fastboot. I also flashed ElementalX kernel via fastboot. As far as I can tell they are not carrier specific. I am considering going to January now so I can use twrp to test some custom roms. For downgrading to January do I simply flash the January boot image which shows to be about 65mb or do I need to find the firmware in it's entirety? Also rather than down grade and use twrp can I just flash custom roms via fastboot? I would say you might have to downgrade to January to use twrp to flash Android 11 unless it's possible to flash the roms on fastboot, hopefully someone chimes in bc I'm unsure at this point.
Noob question, but what's the advantage to changing just the kernel?
Coming back to XDA after over a year. Realized Google Play Store update ruined my Magisk status, and evetually root (SafetyNet stuff). Here are some notes I took while I flashed in 2019, hope it helps.
1. DISABLE Security (PIN/Pattern/Fingerprint)
2. Backup Internal Storage
3. Boot to recovery TWRP, and backup nandroid.
(must go to bootloader and change slot to boot twrp.img flashed on that boot partition slot)
4. Normal boot and drag drop nandroid backup to PC.
5. Syncthing/Resilio for extra measure.
Have latest OTA.zip, boot.img (same version as OTA.zip), and latest Magisk.zip in root internal phone storage.
Have twrp.img in platform-tools adb root for flashing in fastboot.
twrp.zip is optional stored in root internal phone storage.
Flash OTA.zip update in TWRP. (assuming system is under slot_b)
This will flash to opposite slot, _a.
(I flashed under slot_b and new OTA went to slot_a, I booted back to _b and
old system version remained with broken Wifi becasue I accidentally flashed new boot.img in TWRP image over older system image
in slot_b, without the image flash, I suspect the old slot_b would have been perfectly untouched and rooted, as OTA applied to slot_a)
(Went back to A and new OTA was perfectly fine, although unrooted).
Boot to slot_a (system_a), make sure it runs good and verify version within settings, should be unrooted.
Boot to bootloader (under same OTA slot_a), default recovery should be stock recovery (droid logo) after OTA flash.
fastboot flash boot twrp.img (this will replace stock recovery to twrp recovery, deleting stock boot img as well, breaking OTA slot)
Reboot to recovery twrp (remain on same slot and will run off of RAM, leaving boot partition open to flash back stock boot.img)
Install boot.img (make sure version is correct) boot partition should be back to working condition although unrooted OTA system.
Try booting back to recovery on same slot, and stock droid recovery is back. (you cannot edit partitions from fastboot, hence twrp flip flop)
Try booting to system, it will boot but broken, no wifi. How? Not sure, maybe used old boot partition .img in slot_b to boot to system_a
Then flash latest magisk zip to patch stock boot.img for root.
(if you flashed twrp.img and magisk, then you're patching twrp, which is incorrect.
You want to boot to twrp, then flash boot.img back to boot_a partition, then run magisk.zip to patch stock boot.img in that boot_a partition)
Magisk.zip flash log:
Current boot slot: _a
Mounting system
Mounting vendor
Device is system-as-root
System-as-root, keep dm/avb-verity
Encrypted data, keep forceencrypt
Target image: /dev/block/sde11
Device platform: arm64
Constructing environment
Boot image is signed with AVB 1.0
Unpacking boot image
Checking ramdisk status
Stock boot image detected
Backing up stock boot image
Patching ramdisk
Repacking boot image
Flashing new boot image
Sign image with test keys
Unmounting partitions
Done
Updating partition details...
...done
Wipe cache/dalvik
In TWRP, tap reboot button and switch slot_a to other slot_b (older system version).
Reboot to bootloader_b in TWRP.
Flash twrp.img in that other old slot_b (For backup purposes and to have twrp at hand because boot_a has patched rooted boot.img and not twrp anymore)
Done!
Click to expand...
Click to collapse

Categories

Resources