Its a shame.
7 years unlocking bootloaders, installing CWM or TWRP or Philz recovery, flashing rom after rom, not even one device bricked, and today, i messed up, i hope its not bad.
So the short version of what i did is that i flashed twrp.img trough and older version of twrp and now it wont boot into twrp, it says that it failed to verify the recovery image or something like that, and my laptop wont recognize the cellphone, the cellphone boots into the latest Havoc rom but without Gapps and without root because i did not install it beforehand, when in bootloader mode it just says that it could not recognize the device.
The long version is that i had Resurrection Remix, obviously an unlock bootloader, magisk etc... everything was fine until today that i tried to install Havoc, the installation went well but i found out that ambient display was not working, someone told me that the previous version of Havoc did not had that problem so i tried to flash it but it bootlooped for like 1hr, so i read that the version of TWRP provided by the OP was the way to get it to work, i downloaded the .img file and flashed it trough TWRP and tried to install Havoc again but i was stuck in a bootloop, so i flashed the latest Havoc build so i could download the latest version of twrp, i did not flash Gapps or Magisk because i was going to re flash the rom and then flash Gapps and magisk, so i downloaded TWRP and flashed trough TWRP and thats when the sh$& hit the fan, now it wont boot into TRWP and my laptop wont recognize the device, neither on android nor in bootloader mode.
So, thank you guys in advance for your help, tomorrow im going to try on a computer at my work and see if its my computer and if not, well, ill have to se what you geniuses come up with. thank you so much again.
Info:
Rom build number: opm6.171017.030.h1 or 20180811 android 8.1.0
TWRP: i started with 3.2.2-0 then i downgraded to 3.2.1-0 and the one that messed up everything was 3.2.3-0
By the way, I have a full twrp backup of when my phone was stock, (but no way to use it) T_T
Related
Hi guys, I was able to root my G900V, unlock the boot loader into Developer mode, re-write the recovery with TWRP and install AICP custom rom. It was working great, I put Titanium Backup on my phone and it warned of an old version of SU. It recommended I upgrade SuperSU, so I installed the SuperSU app. When it came up of course it detected the same thing (old version of su) and recommended update. I have never used the TWRP/CWM method so again I tried Normal mode. It asked for access and I granted it, spent some time acting like something was happening then failed. I rebooted the phone and tried again -- same thing still failed.
Since I had TWRP installed, I thought I'd give the alternative flash a try. When I chose it, it booted into recovery and flashed a zip file. When it rebooted, it tried to bring up the OS and it hangs at the AICP logo. I can still get into recovery but the OS won't fire up. I'm not sure where to go from here, I think I can start over with ODIN but I'd rather know how to repair this situation (if it's possible) since I started to get the phone set up...
EDIT: By the way, the rom was the AICP Nightly from 12/30 and TWRP of 3.0.2-2.
Solved
I downloaded chainfire's latest SuperSU zip file: https://plus.google.com/+Chainfire/posts/WrCvex7KAZR and flashed it in TWRP. Got me rollin' again.
OK, as of yet, I can not get ANY version of TWRP based on 3.0.3-x to flash a ROM zip and have ANY of the extra zips (supersu and busybox) to install during the main ROM install, like it did on 3.0.2-3 and prior.
Ive tried flashing recovery several times, from 3 different developers, flashing through TWRP img selection as well as through fastboot, including the official TWRP build. Am I missing something?
The ROM flashes fine, but the included SuperSU and Busybox installer zips never even get recognized. But on previous versions of TWRP it works perfectly, and those two extra zips are installed as they should be.
Also, just saw @The Flash updated his TWRP build, still on 3.0.3-0. Not sure what changed, but even that version still has the same problem.
So basically, I'm stuck on 3.0.2-3 by vt0r.
UPDATE:
OK, so I FINALLY got the official 3.0.3-0 to recognize and flash the included extra zips. Had to flash THREE TIMES in fastboot (one flash right after the next), reboot directly back into bootloader, than reboot into recovery. So freaking weird. BUT, I still cant get ANY N4F26J ROM to boot. Not one. Not mine, not anyone elses. My radio, bootloader, and vendor are all the right ones. I dont get it......What happened!?
Don´t know if anybody had this kind of Problem before. Couldnt find anything.
Was on Stock V image with cutom kernel flashed via fastboot and SU flashed via fastboo boot to root.
Problem:
bootet TWRP via fastboot with newest drivers. Flashed RC via booted TWRP.
Wanted to reboot system, but was stuck in a TWRP bootloop. No chance to boot into bootloader also. Even tried changing slots in twrp but still only bootloop to twrp.
Than I thought about sideload because that's what I did with latest ota image from Google.
Here is what I did:
sideloaded the ota.zip via TWRP from PC "adb sideload ota_file.zip" ota_file should be the name of your ota file
It gave me an error, but after rebooting system all fine again. Back to stock V and bootloader is there again.
Easier thing to do is flash boot.img from the factory image to boot_a and boot_b if you are having issues.
This problem occurs when you flash TWRP if you have root installed. To avoid, remove root before installing TWRP.
Oh, I should mention to get into bootloader from TWRP, simply use the adb command "adb reboot bootloader". Should work, worked for me.
I just have avoided flashing TWRP altogether. I rarely need to flash anything, so it can wait until I am at work or home to use a PC to BOOT TWRP each time I need it, instead of flashing it.
Nitemare3219 said:
I just have avoided flashing TWRP altogether. I rarely need to flash anything, so it can wait until I am at work or home to use a PC to BOOT TWRP each time I need it, instead of flashing it.
Click to expand...
Click to collapse
Until it gets a little more stable on the Pixel, this is probably a good idea.
Good idea. But I M sometimes flashing when I am at or on the way to work.
Flash junkie needs his daily dosis
mikaole said:
Don´t know if anybody had this kind of Problem before. Couldnt find anything.
Was on Stock V image with cutom kernel flashed via fastboot and SU flashed via fastboo boot to root.
Problem:
bootet TWRP via fastboot with newest drivers. Flashed RC via booted TWRP.
Wanted to reboot system, but was stuck in a TWRP bootloop. No chance to boot into bootloader also. Even tried changing slots in twrp but still only bootloop to twrp.
Than I thought about sideload because that's what I did with latest ota image from Google.
Here is what I did:
sideloaded the ota.zip via TWRP from PC "adb sideload ota_file.zip" ota_file should be the name of your ota file
It gave me an error, but after rebooting system all fine again. Back to stock V and bootloader is there again.
Click to expand...
Click to collapse
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.
Shadow of Destiny said:
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.
Click to expand...
Click to collapse
I have this issue and flashing supersu didn't fix my problem. Will go to factory image flashing.
Shadow of Destiny said:
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.
Click to expand...
Click to collapse
Thanks! This worked for me.
EDIT: Never mind, I missed the comment guiding ppl to flash SuperSU. I suppose that when this thread was posted, that SuperSU was still being used instead of Magisk, so solution is essentially the same thing I'm recommending.
I think this thread is missing the much easier solution here:
I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.
cognitivedissonance said:
EDIT: Never mind, I missed the comment guiding ppl to flash SuperSU. I suppose that when this thread was posted, that SuperSU was still being used instead of Magisk, so solution is essentially the same thing I'm recommending.
I think this thread is missing the much easier solution here:
I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.
Click to expand...
Click to collapse
This is a Pixel XL forum.
Homeboy76 said:
This is a Pixel XL forum.
Click to expand...
Click to collapse
Aren't the two systems (Pixel OG and Pixel 2) extremely similar? If they're not, then my advice should be ignored for anyone using the Pixel OG.
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??
So I've got a little problem with my Redmi Note 7 - I unlocked the bootloader, flashed the TWRP recovery via fastboot and flashed Magisk v19.3 to root it.
Everything works fine but when I try to download and install the official rom updates the phone just boots to recovery and after restart it says that the update wasn't successful.
Any way to fix it?
beybus said:
So I've got a little problem with my Redmi Note 7 - I unlocked the bootloader, flashed the TWRP recovery via fastboot and flashed Magisk v19.3 to root it.
Everything works fine but when I try to download and install the official rom updates the phone just boots to recovery and after restart it says that the update wasn't successful.
Any way to fix it?
Click to expand...
Click to collapse
Download latest Miui version ,Magisk and lazyflasher-no-verity-opt-encrypt
Wipe cache/Art
Install the rom using TWRP
Install magisk
Install lazy flasher
Reboot.
Every thing you need can be found in this link i have already downloaded it and put all the things in one folder.
https://1drv.ms/u/s!AuqQvn5aQs0xg_IU3fLQqFxu9pp-dg?e=JaoDdC