Related
FOR SOLUTION READ POST:
[SIZE="5"]https://forum.xda-developers.com/showpost.php?p=71007646&postcount=6[/SIZE]
Long time silent reader here. I always find solutions for my problems in xda-devs, until now.
Hope you guys can help me once again..
So, yesterday I messed up my OP3 and wiped all partitions on my phone.
I've tried many steps, trying to flash a flashable stock rom (the one with boot.img and system img) in fastboot, result= installation succeed, but getting blackscreen on boot.
Installing full OOS rom from adb sideload using stock recovery, result= failed (* cannot read 'OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip' *)
Installing full OOS rom from adb sideload using TWRP recovery, result= failed (* cannot read 'OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip' *)
Copy the rom to my phone, and installing the zip with TWRP, result failed (error=7)
So far these are my references:
https://forums.*neplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip
OnePlus3Oxygen_16_OTA_008_all_1606122244_e0cfc5ffc8bf411a.zip
oxygen-os-3.2.5-fastboot-flashable.zip
twrp 3.0.3
https://forum.xda-developers.com/showthread.[/CODE]php?t=2588979
Click to expand...
Click to collapse
applsaus said:
Long time silent reader here. I always find solutions for my problems in xda-devs, until now.
Hope you guys can help me once again..
So, yesterday I messed up my OP3 and wiped all partitions on my phone.
I've tried many steps, trying to flash a flashable stock rom (the one with boot.img and system img) in fastboot, result= installation succeed, but getting blackscreen on boot.
Installing full OOS rom from adb sideload using stock recovery, result= failed (* cannot read 'OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip' *)
Installing full OOS rom from adb sideload using TWRP recovery, result= failed (* cannot read 'OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip' *)
Copy the rom to my phone, and installing the zip with TWRP, result failed (error=7)
So far these are my references:
Click to expand...
Click to collapse
So twrp is working right?
Flash any rom say lineage os
Flash multirom by BitOBSessiOn
Flash multirom twrp
Flash oos as secondary rom
And then swap oos to primary rom
try with some other TWRP . May be v16 blu_spark
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Ye sideboard gives me issues aswell, push the zip and manually flash it In twrp: "adb push romzipname /sdcard/", the file is now ib the folder /sdcard/.
Puddi_Puddin said:
Ye sideboard gives me issues aswell, push the zip and manually flash it In twrp: "adb push romzipname /sdcard/", the file is now ib the folder /sdcard/.
Click to expand...
Click to collapse
tried it with OOS 3.2.8 and OOS 4.0.2, both give me ERROR=7
abhi0502 said:
So twrp is working right?
Flash any rom say lineage os
Flash multirom by BitOBSessiOn
Flash multirom twrp
Flash oos as secondary rom
And then swap oos to primary rom
Click to expand...
Click to collapse
Working on it. Flashed lineage os, looks like working.
Still waiting on boot screen tho (15 mins & counting, hope it won't be bootloop)
hyperorb said:
try with some other TWRP . May be v16 blu_spark
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Click to expand...
Click to collapse
Good idea, I'll put ur idea for the next try
applsaus said:
tried it with OOS 3.2.8 and OOS 4.0.2, both give me ERROR=7
Working on it. Flashed lineage os, looks like working.
Still waiting on boot screen tho (15 mins & counting, hope it won't be bootloop)
Good idea, I'll put ur idea for the next try
Click to expand...
Click to collapse
Then it's a twrp issue. I'm currently in Bluspark v16 so
Error 7 in TWRP AFAIK is an issue with using an incompatible recovery, try the latest one 3.0.4-1 I think it is from this forum.
Puddi_Puddin said:
Then it's a twrp issue. I'm currently in Bluspark v16 so
Click to expand...
Click to collapse
ghostofcain said:
Error 7 in TWRP AFAIK is an issue with using an incompatible recovery, try the latest one 3.0.4-1 I think it is from this forum.
Click to expand...
Click to collapse
I flash twrp bluspark as @Puddi_Puddin suggested and flashing Freedom OS. After that, I restore my data using my last Nandroid backup, then the bootloop comes again. Tried it several times using TWRP Bluspark with different ROMs, still no luck. So I suggest, there's nothing I can do to restoring my phone's data.
I read across the XDA forums and Oneplus forums that some people had similar issues for me, and they suspected something's wrong about corrupted partition, not because twrp version. And I also had tried flashing a few ROM in the past using the same TWRP 3.03 version without any problems. Strange.
Anyway, problems solved, my phone's up and running.
CASE CLOSED.
Thanks XDA
P.S: MODS Please Lock/Close this thread
applsaus said:
Anyway, problems solved, my phone's up and running.
CASE CLOSED.
Thanks XDA
P.S: MODS Please Lock/Close this thread
Click to expand...
Click to collapse
And, what was the solution ?
Restarting from Zero I guess.
Donglip said:
And, what was the solution ?
Click to expand...
Click to collapse
This:
hyperorb said:
try with some other TWRP . May be v16 blu_spark
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Click to expand...
Click to collapse
emuandco said:
Restarting from Zero I guess.
Click to expand...
Click to collapse
Better than not starting at all, at least.
First off I am a seasoned novice in the android flashing/ rooting scene, not know but asking for help by swallowing my pride. I've had the device for two days now and I enjoy the device but would love to try these custom ROMs out. I have installed TWRP multiple times and the TWRP A/B partition flasher, installed Magisk and had a working stock rooted with Elemental X running. No matter how many times I flash a ROM it never seems to boot past the custom ROM's boot sequence, I even tried the manual reboot fix and no dice.
I ask for help for myself and future noobs to this A/B partitioned device.
Thanks in advance
this will help you mate
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
kismetmookz said:
this will help you mate
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
Thanks, I have been using this and used it as I was wring the article, I'm just trying to see how we flash the ROMs on this puppy.
i use to do these steps
wipe caches
install rom
install twrp.zip for taimen
reboot
setup phone
if you want root then reboot on recovery again then install magisk.
I do these steps and have no failure when flashing; after I wipe the Caches, I flash the ROM and then the TWRP partition flasher and reboot the system. I've waited 15 minutes to have the device boot with no luck and I don't want to risk any longer due to the Pixel 2/ XL having burn-in issues.
thowersome said:
First off I am a seasoned novice in the android flashing/ rooting scene, not know but asking for help by swallowing my pride. I've had the device for two days now and I enjoy the device but would love to try these custom ROMs out. I have installed TWRP multiple times and the TWRP A/B partition flasher, installed Magisk and had a working stock rooted with Elemental X running. No matter how many times I flash a ROM it never seems to boot past the custom ROM's boot sequence, I even tried the manual reboot fix and no dice.
I ask for help for myself and future noobs to this A/B partitioned device.
Thanks in advance
Click to expand...
Click to collapse
Probably because there's not a full OS on the slot your flashing to. If you know your fastboot, it's relatively easy going forward. The Dueces scrip it's great tool for sure to help out. If you want to do it manually, fastboot the factory image to both slots with the -w removed from the flash-all.bat file.
Once that's done, go back to fastboot, and boot into twrp. Then do a twrp factory reset with the swipe bar. Flash the rom, then the twrp.zip and let it boot up. Once in the OS, keep lock screen set to swipe, and do a minimal setup. Then go back to twrp and flash your custom kernel(optional) then flash magisk. And that should do it :good:
Will try this out right now, just restored stock, unlocked, rooted and TWRPed it. Will reply with results.
thowersome said:
Will try this out right now, just restored stock, unlocked, rooted and TWRPed it. Will reply with results.
Click to expand...
Click to collapse
If your on the stock April release, you might want to wait until the Devs have updated their roms to be compatible with the current stock release :good:
Btw...what is a twrp partition flasher????
Badger50 said:
If your on the stock April release, you might want to wait until the Devs have updated their roms to be compatible with the current stock release :good:
Btw...what is a twrp partition flasher????
Click to expand...
Click to collapse
The zip that flashes TWRP on both the A and B partition, available at the TWRP website
thowersome said:
The zip that flashes TWRP on both the A and B partition, available at the TWRP website
Click to expand...
Click to collapse
Hahahahahaha...that's pretty good bruh! I've just never heard it called that before. Carry on my friend! ??
Badger50 said:
Hahahahahaha...that's pretty good bruh! I've just never heard it called that before. Carry on my friend!
Click to expand...
Click to collapse
Hey thanks a lot, I got it to boot into AquariOS with no issues, saw that I kept downloading the latest OFW (ie April) on accident.
thowersome said:
Hey thanks a lot, I got it to boot into AquariOS with no issues, saw that I kept downloading the latest OFW (ie April) on accident.
Click to expand...
Click to collapse
Outstanding! Well done :good::good:
So i sideload the Oreo on Nougat. Everything was fine. Then i rooted with magisk and it is no stuck in bootloop. The only way to boot up the device is to go to bootloader screen and hit start. I flashed an image found on this forum and nothing changed. I believe i need a new image ?
Thank you
There is an Oreo .xml.zip, but I don't know for which versions it is:
https://firmware.center/firmware/Motorola/Moto Z Play/Stock/
Gigahyperprime1 said:
So i sideload the Oreo on Nougat. Everything was fine. Then i rooted with magisk and it is no stuck in bootloop. The only way to boot up the device is to go to bootloader screen and hit start. I flashed an image found on this forum and nothing changed. I believe i need a new image ?
Thank you
Click to expand...
Click to collapse
The solution is in this post -- https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
The user Rafikowi give the solution in that post. - "Good Luck" :good:
UPDATE 20.04.2018
If you flashed everything as described in OP and noticed that you got stuck in boot, go to TWRP again and:
1. Uninstall Magisk using latest Magisk uninstaller.
2. Flash Magisk 16.0 or 16.2 (does not matter) AGAIN (yes.).
3. Flash f2fs-loopback-bug-workaround-2018.1.31.zip
4. Enjoy rooted phone.
PS. I do not know why device does not start after first flashing to be honest, but these four steps above are confirmed by several users (and by me last night).
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
cicish said:
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
Click to expand...
Click to collapse
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
niceman2007 said:
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
Click to expand...
Click to collapse
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
cicish said:
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
Click to expand...
Click to collapse
If you still want to root it again,after flasing new rom go to twero and then go to wipe then format,you should format your phone after rom flashing,try this and inform me
Yes yes! I want to root phone once again. So the steps are these:
1) booting into twrp with adb from pc.
2) from the twrp menu wiping and formating the data
3) instaling new rom
Is this true?
Thanks!
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
You mean that its possible to have root access on stock rom?
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
cicish said:
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
Click to expand...
Click to collapse
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Leeban Joseph said:
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Click to expand...
Click to collapse
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
cicish said:
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
Click to expand...
Click to collapse
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Leeban Joseph said:
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Click to expand...
Click to collapse
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
cicish said:
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
Click to expand...
Click to collapse
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Leeban Joseph said:
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Click to expand...
Click to collapse
I've already flashed the stock rom but this will help me next time! Thanks!
I'll stop trying for some days cause I'm really tired with tweaking so thanks and will get back!
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
the_weird_aquarian said:
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
Click to expand...
Click to collapse
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
cicish said:
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
Click to expand...
Click to collapse
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
the_weird_aquarian said:
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
Click to expand...
Click to collapse
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
cicish said:
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
Click to expand...
Click to collapse
that thread is for redmi note 5 pro..and flashing different kernel probably won't solve it because I know few guys flashed genom kernel but still ended up with reboot in huaxing display. Maybe waiting for fix is better.
I successfully rooted the phone using Magisk, and looking at how to install LineageOS, I saw I needed TWRP first. I followed all the instructions, but when I use fastboot to boot twrp.img, I get the following error message, "Error verifying the received boot.img: Invalid Parameter". Searching for an answer, I saw there was an old issue with TWRP with the Pixel 3a XL and Android 10, but I found nothing more recent about Android 11.
I thought maybe I shouldn't have rooted the phone first, so I reflashed with the stock boot.img and tried TWRP again, but that doesn't solve it. Any idea how I can boot TWRP? Or is there a way to install LineageOS with TWRP? Thanks!
Build # RQ2A.2100505.002
TWRP image twrp-3.5.2_9-0-bonito.img
Twrp doesn't work currently for android 10+
You don't need it to install lineage, just flash the lineage recovery and follow the wiki install guide.
Install LineageOS on bonito | LineageOS Wiki
wiki.lineageos.org
If TWRP does not work on Android 10+ what are we doing about flashing custom roms? Booting the TWRP and then sideloading the ROM?
I need help. When I try to boot TWRP(assuming its possible) I get an error :invalid parameter, error verifying the boot image. I am on Android 11. Yes, Ive used the search function or else I would not have found this thread.
I do not want to flash lineage, but the instructions are vague in other ROM threads.
I just built a TWRP that works on Android 11. I wasn't sure how much interest there was in it, though, so I didn't bother posting it anywhere. I'll consider it once I clean up the source a bit.
Captain_Throwback said:
I just built a TWRP that works on Android 11. I wasn't sure how much interest there was in it, though, so I didn't bother posting it anywhere. I'll consider it once I clean up the source a bit.
Click to expand...
Click to collapse
Please post it! It would be greatly appreciated!
ncrawler said:
Please post it! It would be greatly appreciated!
Click to expand...
Click to collapse
I posted it on Telegram here: https://t.me/pixel3a/161825
Captain_Throwback said:
I posted it on Telegram here: https://t.me/pixel3a/161825
Click to expand...
Click to collapse
Thank You! I've been waiting for this!
I cant get your twrp and magisk to work together? I can only get one or the other working.
ncrawler said:
I cant get your twrp and magisk to work together? I can only get one or the other working.
Click to expand...
Click to collapse
Boot TWRP, copy image to device, use Install Image -> Install Recovery Ramdisk to install TWRP, then flash Magisk.apk.
I've done it a bunch of times and it works fine. Is that what you're doing?
Captain_Throwback said:
Boot TWRP, copy image to device, use Install Image -> Install Recovery Ramdisk to install TWRP, then flash Magisk.apk.
I've done it a bunch of times and it works fine. Is that what you're doing?
Click to expand...
Click to collapse
Done it about 10 times and never boots again
ncrawler said:
Done it about 10 times and never boots again
Click to expand...
Click to collapse
with or without lmza kernel
ncrawler said:
with or without lmza kernel
Click to expand...
Click to collapse
No idea what to tell you. It works for users in the TG group and it works for me. That's the exact process I'm using. You can alternatively try the Advanced -> Flash Current TWRP option and then flash Magisk and see what happens.
Thanks! I think I got it! Think I was using the wrong Magisk! I Guess I still have to use lmza kernel to pass integrity in magisk?
ncrawler said:
Thanks! I think I got it! Think I was using the wrong Magisk! I Guess I still have to use lmza kernel to pass integrity in magisk?
Click to expand...
Click to collapse
I have no idea about any specific kernel or integrity checks in Magisk. I only build TWRP.