I woke up today to a bootloop. After pulling out the battery, I cant turn it on, it was stuck at the google logo. I thought it was some rom issue or something. When I had the time, in the afternoon, I just boot to recovery, and wiped data+sd card. Turns out sd card was not wiped.
Just now, I found a way to boot it. (AFTER WIPING DATA) I used the gnex toolkit and boot with insecure image, and guess wat? My old rom boots. Everything was the way it was, and then it crashed and stuck on the google logo again.(I made sure i wiped things two to three times, data and sd) I did a few experiments:
1) Flash using ODIN
2) Flash CWM using toolkit--it changed back to twrp after reboot
3) Changing the icon on my homescreen after boot--- everything was the same again after booting
4) Flash stock image using toolkit
5) Wipe data using manual adb
6) Try to lock my bootloader
So, what happened, I was almost finishing the flashing of the rom, I was in twrp, and selected reboot to boot loader mode, but I selected slot 2; then my screen never more get on. @majmoz Can you help me?
there should be a error screen after boot with slot2, coz i was tried before, i fixed with full flash with gpt / bootloader with full rom
Hi,
I had this happen about two weeks ago and I wiped my phone and flashed a fresh Android 10 (latest as of two weeks ago). I only restarted my phone because I was having issues with Snapchat so I restarted and it's popped back up again...
I don't want to have to wipe my phone again, I'd just finished logging everything in! I have Magisk and a fingerprint/pin added to my OS so the data in TWRP will be encrypted.
What do I do to fix this? I'd appreciate some help!
Thanks
Hyflex said:
Hi,
I had this happen about two weeks ago and I wiped my phone and flashed a fresh Android 10 (latest as of two weeks ago). I only restarted my phone because I was having issues with Snapchat so I restarted and it's popped back up again...
I don't want to have to wipe my phone again, I'd just finished logging everything in! I have Magisk and a fingerprint/pin added to my OS so the data in TWRP will be encrypted.
What do I do to fix this? I'd appreciate some help!
Thanks
Click to expand...
Click to collapse
If your fastbooting the factory image, try switching to your inactive slot, and fastboot the factory image again with the -w removed.
Badger50 said:
If your fastbooting the factory image, try switching to your inactive slot, and fastboot the factory image again with the -w removed.
Click to expand...
Click to collapse
Uhm... Could you provide a bit more detail? I have this tool https://forum.xda-developers.com/pi...ol-tool-one-driversunlocktwrpfactory-t3730226 installed to make stuff easier but I still don't know what you mean :/
Hyflex said:
Uhm... Could you provide a bit more detail? I have this tool https://forum.xda-developers.com/pi...ol-tool-one-driversunlocktwrpfactory-t3730226 installed to make stuff easier but I still don't know what you mean :/
Click to expand...
Click to collapse
The P2XL is a A/B dual partition device. If you fastboot the factory image with the -w intact within the flash-all.bat file, it will flash to both partition slots. When you remove the -w from the flash-all.bat file, it will only flash to one slot/partition and does not wipe your data. I personally don't use tool kits since I like a more hands on approach. Also, are your platform-tools up to date? If not, that can cause headaches as well.
Badger50 said:
The P2XL is a A/B dual partition device. If you fastboot the factory image with the -w intact within the flash-all.bat file, it will flash to both partition slots. When you remove the -w from the flash-all.bat file, it will only flash to one slot/partition and does not wipe your data. I personally don't use tool kits since I like a more hands on approach. Also, are your platform-tools up to date? If not, that can cause headaches as well.
Click to expand...
Click to collapse
So...
Extract the factory image, edit flash-all.bat and remove the -w, run flash-all.bat?
Yep my platform-tools are up to date!
Hyflex said:
So...
Extract the factory image, edit flash-all.bat and remove the -w, run flash-all.bat?
Yep my platform-tools are up to date!
Click to expand...
Click to collapse
Exactly. Just make sure you have all the extracted factory image files in your platform-tools folder. If you have to change slots, the command is......fastboot --set-active=a or b. Depending of course on which slot your currently on.
If you don't know which slot your on, run...fastboot getvar all. :good:
Badger50 said:
Exactly. Just make sure you have all the extracted factory image files in your platform-tools folder. If you have to change slots, the command is......fastboot --set-active=a or b. Depending of course on which slot your currently on.
If you don't know which slot your on, run...fastboot getvar all. :good:
Click to expand...
Click to collapse
So current slot is b? https://i.imgur.com/85l7Y6v.png
Why do I need to have the image files in platform-tools? I have adb setup where I can use it anywhere.
I should do
Code:
fastboot --set-active=a
and then just run the flash-all.bat which I've modified to look like https://i.imgur.com/yGPkqqY.png (removed -w)
I must admit, I don't understand why we have to change from a to b or vice versa... I didn't do that last week when I tried to fix this... I just removed the -w and ran the file which didn't work.
Hyflex said:
So current slot is b? https://i.imgur.com/85l7Y6v.png
Why do I need to have the image files in platform-tools? I have adb setup where I can use it anywhere.
I should do and then just run the flash-all.bat which I've modified to look like https://i.imgur.com/yGPkqqY.png (removed -w)
I must admit, I don't understand why we have to change from a to b or vice versa... I didn't do that last week when I tried to fix this... I just removed the -w and ran the file which didn't work.
Click to expand...
Click to collapse
I don't understand everything all the time either. I just know what I have done in the past to fix this issue. It may not work either if you have corrupted internal files or maybe a hardware issue.
Badger50 said:
I don't understand everything all the time either. I just know what I have done in the past to fix this issue. It may not work either if you have corrupted internal files or maybe a hardware issue.
Click to expand...
Click to collapse
I tried to switch slots and it threw up:
Code:
> fastboot: error: Device does not support slots
My platform tools are from last month
Hyflex said:
I tried to switch slots and it threw up:
My platform tools are from last month
Click to expand...
Click to collapse
Then I would start from scratch. Delete your current platform-tools, and download it again. Also, sometimes your USB cables and ports can cause glitches on the P2XL.....even if they've worked in the past, I've had it happen to me.
Badger50 said:
Then I would start from scratch. Delete your current platform-tools, and download it again. Also, sometimes your USB cables and ports can cause glitches on the P2XL.....even if they've worked in the past, I've had it happen to me.
Click to expand...
Click to collapse
Interesting, I switched cable and it allowed me to flash it... I tried and it still shows the same message so I guess I have to do the full wipe one again.
Does anyone know of any other solutions before i wipe the phone.
Hyflex said:
Interesting, I switched cable and it allowed me to flash it... I tried and it still shows the same message so I guess I have to do the full wipe one again.
Does anyone know of any other solutions before i wipe the phone.
Click to expand...
Click to collapse
So... I got it working, I also broke it again and then got it working.
1. I switched from slot b to a
2. Re-flashed a factory firmware without -w
3. Tried to boot... still broken
4. I switched from slot a back to slot b
5. Re-flashed a factory firmware without -w
6. Tried to boot... still broken
7. Booted into TWRP and then into system
8. Tried to boot... still broken
9. Flashed TWRP via Toolkit (installs to both slots with a recovery script)
10. Tried to boot... it worked
11. Flashed Magisk
12. Tried to boot... it's back to being broken again
13. Flashed TWRP via Toolkit (installs to both slots with a recovery script)
14. Tried to boot... still broken
15. I switched from slot b to slot a
16. Re-flashed a factory firmware without -w
17. Tried to boot... still broken
18. Flashed MagiskUninstaller.zip
19. Tried to boot... it worked
20. Flashed Magisk
20. Tried to boot... it worked
So I guess it was something from Magisk that broke it... one of the modules.
Hyflex said:
So... I got it working, I also broke it again and then got it working.
1. I switched from slot b to a
2. Re-flashed a factory firmware without -w
3. Tried to boot... still broken
4. I switched from slot a back to slot b
5. Re-flashed a factory firmware without -w
6. Tried to boot... still broken
7. Booted into TWRP and then into system
8. Tried to boot... still broken
9. Flashed TWRP via Toolkit (installs to both slots with a recovery script)
10. Tried to boot... it worked
11. Flashed Magisk
12. Tried to boot... it's back to being broken again
13. Flashed TWRP via Toolkit (installs to both slots with a recovery script)
14. Tried to boot... still broken
15. I switched from slot b to slot a
16. Re-flashed a factory firmware without -w
17. Tried to boot... still broken
18. Flashed MagiskUninstaller.zip
19. Tried to boot... it worked
20. Flashed Magisk
20. Tried to boot... it worked
So I guess it was something from Magisk that broke it... one of the modules.
Click to expand...
Click to collapse
Well done my friend. Goes to show that persistence pays off! :good::good:
Another method I do when I run across issue in the past.
I would lock and unlock my bootloader a few times (of course start the devices after each lock and unlock), which erase everything, then my phone will let me flash Google factory imagine..
hi, I tried to install twrp-3.3.0-0 and 3.2.3-1 but neither of two can mount SYSTEM and VENDOR partitionjs, im back to stock Android 10... some help would be appreciated guys how did you installed twrp on Android 10 ...?
estemanito said:
hi, I tried to install twrp-3.3.0-0 and 3.2.3-1 but neither of two can mount SYSTEM and VENDOR partitionjs, im back to stock Android 10... some help would be appreciated guys how did you installed twrp on Android 10 ...?
Click to expand...
Click to collapse
You won't be able to mount system/vendor until twrp updates the recovery to accommodate A10 and the new logical partitions that google implemented. If they choose to do so at all. However, the 330-0 version will still flash zips despite throwing vendor/system errors. The way installed twrp is....have a copy of the twrp 330-0 image, not zip, on your phones internal storage. Then fastboot into twrp. Once there, select install, then select image. Go to where your twrp.img file is located, and select it. You will then get a prompt to which partition you want to flash it to...select recovery ramdisk, and flash it. And that's it :good:
Badger50 said:
You won't be able to mount system/vendor until twrp updates the recovery to accommodate A10 and the new logical partitions that google implemented. If they choose to do so at all. However, the 330-0 version will still flash zips despite throwing vendor/system errors. The way installed twrp is....have a copy of the twrp 330-0 image, not zip, on your phones internal storage. Then fastboot into twrp. Once there, select install, then select image. Go to where your twrp.img file is located, and select it. You will then get a prompt to which partition you want to flash it to...select recovery ramdisk, and flash it. And that's it :good:
Click to expand...
Click to collapse
I cant install from the recovery cause when i try to boot in recovery mode i get a black screen with a little dead droid then a "no command" message. The way i installed before is from fastboot with the .img file
estemanito said:
I cant install from the recovery cause when i try to boot in recovery mode i get a black screen with a little dead ath droid then a "no command" message. The way i installed before is from fastboot with the .img file
Click to expand...
Click to collapse
You have to fastboot the twrp.img file first using your pc.
Badger50 said:
You have to fastboot the twrp.img file first using your pc.
Click to expand...
Click to collapse
ok so i flash first from the pc then i boot in trwp then i re-flash trwp.img from the trwp menu (not the trwp.zip) thats it...?
estemanito said:
ok so i flash first from the pc then i boot in trwp then i re-flash trwp.img from the trwp menu (not the trwp.zip) thats it...,
Click to expand...
Click to collapse
Bingo! You got it :good::laugh:
Hey guys, got myself into a sticky situation by doing a lot of stuff without really thinking about it. I'm in a state where my slot a is pretty much borked I think. Anytime in slot a I try to reboot into recovery I just get put back into fastboot mode. in slot b I still have the LOS recovery. I've tried running the copy-partitions script on slot b to try to fix a but it didn't make a difference. Any help to get my slot a back up?
what I've done that doesn't seem to work:
Code:
fastboot --set-active=a
fastboot fastboot flash boot lineage-18.1-20210706-recovery-lemonadep.img
and my terminal response:
Code:
Sending 'boot_a' (196608 KB) OKAY [ 4.306s]
Writing 'boot_a' OKAY [ 0.604s]
Finished. Total time: 5.012s
It looks like it goes through successfully but when I try to fastboot reboot recovery I just get brought back to the bootloader/fastboot screen.
I accidentally did this to my slot B after I ran the copy-partitions script and I didn't lose my recovery, so it's not something with the recovery image. It's something wrong with my slot a. Any easy way for me to go back to stock or something?
Ok I'm back booted directly into OOS. I'll keep story time brief. Downloaded the OOS zip from the pinned OOS thread here. Downloaded payload-dumper-go from: here
Used payload-dumper-go to dump all the images out of the zip. Then, went into Sconny's thread, downloaded his zip, copied all of the fastboot commands he had in his flasher.bat and made my own shell script with just those commands. Ran the script and Viola. Thanks a ton Sconny! You saved my butt
shmallow said:
Ok I'm back booted directly into OOS. I'll keep story time brief. Downloaded the OOS zip from the pinned OOS thread here. Downloaded payload-dumper-go from: here
Used payload-dumper-go to dump all the images out of the zip. Then, went into Sconny's thread, downloaded his zip, copied all of the fastboot commands he had in his flasher.bat and made my own shell script with just those commands. Ran the script and Viola. Thanks a ton Sconny! You saved my butt
Click to expand...
Click to collapse
hm I'm in something of a similar situation, where slot b is f'd up but slot a is fine, but my problem is I can't update oos either in twrp or local update, so I'm going to try what you did to reflash oos (I used payload dumper already). so in short, did you essentially reflash oos on your phone? and I'm glad you didn't wipe first bc I do not want to lose data.
thirtythr33 said:
hm I'm in something of a similar situation, where slot b is f'd up but slot a is fine, but my problem is I can't update oos either in twrp or local update, so I'm going to try what you did to reflash oos (I used payload dumper already). so in short, did you essentially reflash oos on your phone? and I'm glad you didn't wipe first bc I do not want to lose data.
Click to expand...
Click to collapse
Yeah it gave me stock OOS, I used the newest version for global. I think you will lose your data; my rom was really messed up. I had dirty flashed stock OOS through TWRP (sideloaded) on top of Lineage OS... So my OS was probably completely messed up on that slot. I thought I would have needed a fastboot -w (which I think is wipe? not sure about that)
So mine booted OOS when it booted even though I forgot to do that, so I think it did some sort of wipe.
Well maybe you're right and you don't lose data. I just accidentally did it again after flashing magisk and I still have magisk. Though now I have to flash it again lol
shmallow said:
Hey guys, got myself into a sticky situation by doing a lot of stuff without really thinking about it. I'm in a state where my slot a is pretty much borked I think. Anytime in slot a I try to reboot into recovery I just get put back into fastboot mode. in slot b I still have the LOS recovery. I've tried running the copy-partitions script on slot b to try to fix a but it didn't make a difference. Any help to get my slot a back up?
Click to expand...
Click to collapse
May i ask what is this Slot A and Slot B? i never heard about smth like this in previous phones i used...
Ninxha said:
May i ask what is this Slot A and Slot B? i never heard about smth like this in previous phones i used...
Click to expand...
Click to collapse
Me too, honestly the only reason I looked into it was because I was forced to. From what I've gathered, it seems like slot b is a staging area for updates when downloaded. It's an entirely separate partition but I'm not sure it's fully functional. I really don't know much and would appreciate anyone that has some insight into that.
@Ninxha and @shmallow
while slots can be confusing, and even though this is in the op6 forum it greatly helps explain the new(er) slot a/b system
[GUIDE] The Noob's Guide to A/B Partitions and Other OP6 Idiosyncrasies
If you've just arrived on the phone modding scene, or are coming from another phone that uses traditional approaches to flashing, you've likely come across people talking about the "A/B partitions." If you don't have any experience with this...
forum.xda-developers.com