I've been trying to compile twrp for the past couple days, but I've kind of got a wall. I've already posted on the twrp compile thread so I'll just going to link it here because I'm lazy and on my phone at.
https://forum.xda-developers.com/showthread.php?t=1943625&p=78396686
Any help would be greatly appreciated (especially with my device files)
Post your recovery.img
Warrior1988 said:
Post your recovery.img
Click to expand...
Click to collapse
Here you go. https://www.dropbox.com/s/75kh55ytl3k7ztd/recovery.img?dl=0
And here's the terminal output https://pastebin.com/X9yzVLWv
I removed the recovery folder from my device tree because that broke compiling.
twrp would be great cause then we can start compiling lineage
CalebQ42 said:
Here you go. https://www.dropbox.com/s/75kh55ytl3k7ztd/recovery.img?dl=0
And here's the terminal output https://pastebin.com/X9yzVLWv
I removed the recovery folder from my device tree because that broke compiling.
Click to expand...
Click to collapse
Is that the stock recovery unmodified? Also post boot.img
Warrior1988 said:
Is that the stock recovery unmodified? Also post boot.img
Click to expand...
Click to collapse
No, I just forgot to get twrp I'm rebuilding both Boot and recovery with twrp now
CalebQ42 said:
Here you go. https://www.dropbox.com/s/75kh55ytl3k7ztd/recovery.img?dl=0
And here's the terminal output https://pastebin.com/X9yzVLWv
I removed the recovery folder from my device tree because that broke compiling.
Click to expand...
Click to collapse
CalebQ42 said:
No, I just forgot to get twrp I'm rebuilding both Boot and recovery with twrp now
Click to expand...
Click to collapse
Good Luck ?
I might take a shot at it as well. I've compiled ROMs for previous devices but Android has changed so much since I last did dev. Feel like I'm back at square one lol (I mean you've probably got it by now, but I feel like I need to learn anyway...)
CurtisMJ said:
I might take a shot at it as well. I've compiled ROMs for previous devices but Android has changed so much since I last did dev. Feel like I'm back at square one lol
Click to expand...
Click to collapse
Thatd be amazing! if we can get a kernel that would boot with lineage, we could possibly use GSI's from trebel. I downloaded and made a build enviroment and was like... what do i do now.
Warrior1988 said:
... Also post boot.img
Click to expand...
Click to collapse
Now with TWRP. Still not booting.
Boot.img: https://www.dropbox.com/s/vyb7nlaji3etqon/boot.img?dl=0
Recovery.img: https://www.dropbox.com/s/75kh55ytl3k7ztd/recovery.img?dl=0
Sorry it took so long, I was kind of busy on Wednesday and have been lazy.
CalebQ42 said:
Now with TWRP. Still not booting.
Boot.img: https://www.dropbox.com/s/vyb7nlaji3etqon/boot.img?dl=0
Recovery.img: https://www.dropbox.com/s/75kh55ytl3k7ztd/recovery.img?dl=0
Sorry it took so long, I was kind of busy on Wednesday and have been lazy.
Click to expand...
Click to collapse
Here is the recovery.img with twrp
fastboot flash boot recovery.img
https://drive.google.com/file/d/14RsthZZY64xpUfrQ99W94c-5P0xZynno/view?usp=drivesdk
Warrior1988 said:
Here is the recovery.img with twrp
fastboot flash boot recovery.img
https://drive.google.com/file/d/1Ff8rioDcM_t9r8HcCqyoOIytkjDely5i/view?usp=drivesdk
Click to expand...
Click to collapse
Tested, does not boot. Tried both A and B partitions (the essential phone was weird like that).
CalebQ42 said:
Now with TWRP. Still not booting.
Boot.img: https://www.dropbox.com/s/vyb7nlaji3etqon/boot.img?dl=0
Recovery.img: https://www.dropbox.com/s/75kh55ytl3k7ztd/recovery.img?dl=0
Sorry it took so long, I was kind of busy on Wednesday and have been lazy.
Click to expand...
Click to collapse
Twiggy000b said:
Tested, does not boot. Tried both A and B partitions (the essential phone was weird like that).
Click to expand...
Click to collapse
I modified the boot.img this time.
https://drive.google.com/file/d/14RsthZZY64xpUfrQ99W94c-5P0xZynno/view?usp=drivesdk
Warrior1988 said:
I modified the boot.img this time.
https://drive.google.com/file/d/14RsthZZY64xpUfrQ99W94c-5P0xZynno/view?usp=drivesdk
Click to expand...
Click to collapse
does it actually work that means i can at least spoof pokemon go !
Twiggy000b said:
does it actually work that means i can at least spoof pokemon go !
Click to expand...
Click to collapse
Yes for MR2
Warrior1988 said:
Yes for MR2
Click to expand...
Click to collapse
let me test real quick. i'll be so gosh darn happy.
---------- Post added at 05:23 AM ---------- Previous post was at 05:22 AM ----------
same flash comman?
Twiggy000b said:
let me test real quick. i'll be so gosh darn happy.
---------- Post added at 05:23 AM ---------- Previous post was at 05:22 AM ----------
same flash comman?
Click to expand...
Click to collapse
fastboot flash boot boot.img && fastboot reboot
still doesnt work... tested multiple times. BOOTS! but goes to stock recovery.
Warrior1988 said:
I modified the boot.img this time.
https://drive.google.com/file/d/14RsthZZY64xpUfrQ99W94c-5P0xZynno/view?usp=drivesdk
Click to expand...
Click to collapse
Your boot.img seems to be 160M when I download it for some reason, which is too big to even try to flash. The recovery.img is also 160M so maybe it's something weird with google drive.
CalebQ42 said:
Your boot.img seems to be 160M when I download it for some reason, which is too big to even try to flash. The recovery.img is also 160M so maybe it's something weird with google drive.
Click to expand...
Click to collapse
oh it flashes. but boots to stock recovery. tried researching on compiling stuff and yup... scratching my head over here.
EDIT: Welp, I did some unpacking and moved some files around in the boot.img and finally got the recovery part to boot to a black screen -.-i dont quite understand, all the mounting points are correctbut any modefications to the boot.img seems to make it not want to boot.
Related
This morning I flashed through bootloader the new TWRP that was available for my ZTE Axon 7. After flashing it, I did a backup of Boot, Data and System, which is the default backup. Then I flashed SuperSU. When I tried testing my backup by restoring it through TWRP, it simply bootlooped after I restarted. I am frustrated because I have no idea what to do next. I cannot find a stock firmware for my US version Axon 7. PLEASE HELP!!!
B4oE said:
This morning I flashed through bootloader the new TWRP that was available for my ZTE Axon 7. After flashing it, I did a backup of Boot, Data and System, which is the default backup. Then I flashed SuperSU. When I tried testing my backup by restoring it through TWRP, it simply bootlooped after I restarted. I am frustrated because I have no idea what to do next. I cannot find a stock firmware for my US version Axon 7. PLEASE HELP!!!
Click to expand...
Click to collapse
Try Wipe Cache - Dalvik - Data on TWRP
I know you'll need to reinstall everything but hey may fix your bootloop problem
And so it begins...
@DrakenFX, did you have a typo in your instructions? I assume you meant Data rather than Daproblem.
TeutonJon78 said:
And so it begins...
@DrakenFX, did you have a typo in your instructions? I assume you meant Data rather than Daproblem.
Click to expand...
Click to collapse
LoL, so dislike auto-correct , Thanks for the mention
DrakenFX said:
LoL, so dislike auto-correct , Thanks for the mention
Click to expand...
Click to collapse
My early morning phone typing always look like I've had a stroke.
I wonder if we really need to wipe "Cache" anymore. I haven't seen any phone even using it lately. It just sits there basically empty since they moved everything to be stored in the Davlik one on the Data partition. I know on my Nexus 4 it basically just takes up 560 MB doing nothing but storing one recovery log file. Does TWRP use it for something during install?
TeutonJon78 said:
And so it begins...
@DrakenFX, did you have a typo in your instructions? I assume you meant Data rather than Daproblem.
Click to expand...
Click to collapse
Man people are so impatient, yes here we go, first bootloop....
---------- Post added at 07:39 PM ---------- Previous post was at 07:32 PM ----------
B4oE said:
This morning I flashed through bootloader the new TWRP that was available for my ZTE Axon 7. After flashing it, I did a backup of Boot, Data and System, which is the default backup. Then I flashed SuperSU. When I tried testing my backup by restoring it through TWRP, it simply bootlooped after I restarted. I am frustrated because I have no idea what to do next. I cannot find a stock firmware for my US version Axon 7. PLEASE HELP!!!
Click to expand...
Click to collapse
You are gonna have to wait until someone provides a working (flashable) backup of B20_boot, I'm guessing yours is corrupted or had user error, here I summon:
@DrakenFX @jkuczera @swehes @peramikic
Does anyone has a clean flashable B20_boot from your TWRP backups? This guy bootlooped after trying to restore his. I would give him mine, but will probably not get my Axon 7 Gray shipped until wednesday from B&H.
---------- Post added at 07:40 PM ---------- Previous post was at 07:39 PM ----------
B4oE said:
This morning I flashed through bootloader the new TWRP that was available for my ZTE Axon 7. After flashing it, I did a backup of Boot, Data and System, which is the default backup. Then I flashed SuperSU. When I tried testing my backup by restoring it through TWRP, it simply bootlooped after I restarted. I am frustrated because I have no idea what to do next. I cannot find a stock firmware for my US version Axon 7. PLEASE HELP!!!
Click to expand...
Click to collapse
And did you already tried clearing cache and data?
B4oE said:
When I tried testing my backup by restoring it through TWRP, it simply bootlooped after I restarted. I am frustrated because I have no idea what to do next. I cannot find a stock firmware for my US version Axon 7. PLEASE HELP!!!
Click to expand...
Click to collapse
Do you see the ZTE logo?
I have the backups already made up, I believe this might be what you need:
jcadduono said:
heres some STOCK fastboot flashables 4 funsies: https://idlekernel.com/flash-tools/firmware/ailsa_ii_A2017U/B20/
Click to expand...
Click to collapse
jkuczera said:
Do you see the ZTE logo?
I have the backups already made up, I believe this might be what you need:
Click to expand...
Click to collapse
Is "system.img" the stock, out-of-the-box OS?
daneoleary said:
Is "system.img" the stock, out-of-the-box OS?
Click to expand...
Click to collapse
No, it would be based on B20. And if B20-boot modified the system partition, those modifications would be in there as well.
I apologize for not responding sooner. I was busy at work. Someone sent me a zip to flash through TWRP, which I will upload later, and then my bootloop issue was resolved. Apparently, the problem is with TWRP. Hopefully, everything will get ironed out soon. Other than that, I'm still having a good time (although frustrating at times) tinkering with my Axon 7.
B4oE said:
I apologize for not responding sooner. I was busy at work. Someone sent me a zip to flash through TWRP, which I will upload later, and then my bootloop issue was resolved. Apparently, the problem is with TWRP. Hopefully, everything will get ironed out soon. Other than that, I'm still having a good time (although frustrating at times) tinkering with my Axon 7.
Click to expand...
Click to collapse
Looking forward for your fix to help other members down the road! THANK YOU!
Jose-MXL said:
Looking forward for your fix to help other members down the road! THANK YOU!
Click to expand...
Click to collapse
Attached is the file I flashed.
jkuczera said:
No, it would be based on B20. And if B20-boot modified the system partition, those modifications would be in there as well.
Click to expand...
Click to collapse
B20_Boot only makes changes to boot.img and recovery.img
B4oE said:
Attached is the file I flashed.
Click to expand...
Click to collapse
Who sent it to you?
rczrider said:
Who sent it to you?
Click to expand...
Click to collapse
I honestly do not remember their name. Someone I spoke to through Freenode (http://webchat.freenode.net/?channels=twrp) simply told me to flash that zip. I just renamed it before flashing because I have a huge collection of zips for various devices. Hopefully, the one that has it can respond to my post. He/She was very helpful too!
jkuczera said:
No, it would be based on B20. And if B20-boot modified the system partition, those modifications would be in there as well.
Click to expand...
Click to collapse
xtermmin said:
B20_Boot only makes changes to boot.img and recovery.img
Click to expand...
Click to collapse
No, it modifies system:
From the updater script:
Code:
ui_print("Patching system image after verification.");
show_progress(0.550000, 0);
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("Failed to update system image.");
show_progress(0.050000, 10);
ui_print("Patching fastboot.img image...");
package_extract_file("fastboot.img", "/dev/block/bootdevice/by-name/fbop");
ui_print("Patching boot image...");
apply_patch("EMMC:/dev/block/bootdevice/by-name/boot:45946154:b5154bbd9bf32de3d1e2a287df025a483bf3c50f:45942058:c31f24136f92263b578c19356df513650a12befc",
"-", c31f24136f92263b578c19356df513650a12befc, 45942058,
b5154bbd9bf32de3d1e2a287df025a483bf3c50f, package_extract_file("patch/boot.img.p"));
ui_print("Patching recovery image...");
apply_patch("EMMC:/dev/block/bootdevice/by-name/recovery:44545326:5ce0d08c1e4efdaf65879574d74611d569fa036f:44541230:a13824adb7464c22637b70ddb8b0991ff365ab4c",
"-", a13824adb7464c22637b70ddb8b0991ff365ab4c, 44541230,
5ce0d08c1e4efdaf65879574d74611d569fa036f, package_extract_file("patch/recovery.img.p"));
set_progress(1.000000);
It alters system.img, fastboot.img, boot.img, and recovery.img. By the looks of it, it modifies system.img a fair amount. Just fixing fastboot wouldn't be a 50+ MB patch.
TeutonJon78 said:
No, it modifies system:
From the updater script:
It alters system.img, fastboot.img, boot.img, and recovery.img. By the looks of it, it modifies system.img a fair amount. Just fixing fastboot wouldn't be a 50+ MB patch.
Click to expand...
Click to collapse
I'm blind. I stand corrected.
B4oE said:
I honestly do not remember their name. Someone I spoke to through Freenode (http://webchat.freenode.net/?channels=twrp) simply told me to flash that zip. I just renamed it before flashing because I have a huge collection of zips for various devices. Hopefully, the one that has it can respond to my post. He/She was very helpful too!
Click to expand...
Click to collapse
it might have been me that linked it (i'm the maker of the zip as it shows you in the console flash ) but yeah that's our go-to when someone says they flashed twrp and their system won't boot. it means they swiped to enable system modifications. we should probably go about extending the warning on the swipe to enable modifications page since devices that come with marshmallow out of factory will bootloop after swiping if you don't flash supersu or the no-verity-opt-encrypt zip. (the zip disables system integrity verification in your boot image, allowing you to boot after making modifications)
you can find the original, and updates if/when i make them at https://idlekernel.com/fun-stuff-trust-me/no-verity-opt-encrypt/
you can also follow history at https://github.com/jcadduono/lazyflasher/commits/no-verity-opt-encrypt
jcadduono said:
it might have been me that linked it (i'm the maker of the zip as it shows you in the console flash ) but yeah that's our go-to when someone says they flashed twrp and their system won't boot. it means they swiped to enable system modifications. we should probably go about extending the warning on the swipe to enable modifications page since devices that come with marshmallow out of factory will bootloop after swiping if you don't flash supersu or the no-verity-opt-encrypt zip. (the zip disables system integrity verification in your boot image, allowing you to boot after making modifications)
you can find the original, and updates if/when i make them at https://idlekernel.com/fun-stuff-trust-me/no-verity-opt-encrypt/
you can also follow history at https://github.com/jcadduono/lazyflasher/commits/no-verity-opt-encrypt
Click to expand...
Click to collapse
Awesome! Well, THANK YOU because I was bootlooped for several hours. You helped me so much!
Does anyone has TWRP backup ? I tried the stock fastboot backups and manage to flash system.img and boot.img files but I am still stuck on ZTE Logo Screen.
Android O (Oreo?) developer preview out now!
No OTA on the beta channel initially.
https://developer.android.com/preview/download.html
This is a developer's preview... probably not ready for use on a daily driver.
Weudel said:
This is a developer's preview... probably not ready for use on a daily driver.
Click to expand...
Click to collapse
Right....especially since TWRP doesn't work on it!
c7j8d9 said:
Right....especially since TWRP doesn't work on it!
Click to expand...
Click to collapse
Even fastboot boot twrp?
i cant even get it to boot into OS. Just sitting at the google boot up screen
Hogyoku said:
Even fastboot boot twrp?
Click to expand...
Click to collapse
I tried twrp alpha and rc1 with fastboot boot and got nothing.
has anyone got this to boot? it fails flashing to slot 4 on b partition?
Garner said:
has anyone got this to boot? it fails flashing to slot 4 on b partition?
Click to expand...
Click to collapse
I flashed it without wiping with no problems from 7.1.2 beta 2. Boots fine.
c7j8d9 said:
I flashed it without wiping with no problems from 7.1.2 beta 2. Boots fine.
Click to expand...
Click to collapse
booted :good:
Garner said:
booted :good:
Click to expand...
Click to collapse
woot!! Now I can't get it to boot back to 7.1.2 after flashing back. Think I screwed myself.
Garner said:
booted :good:
Click to expand...
Click to collapse
Are you able to boot up on different slot?
I installed just boot, system, and vendor via twrp and it booted fine.
This black and white will take some getting used to
c7j8d9 said:
I tried twrp alpha and rc1 with fastboot boot and got nothing.
Click to expand...
Click to collapse
I got stuck in the twrp screen flashing the logo
---------- Post added at 09:44 PM ---------- Previous post was at 09:44 PM ----------
Zavon said:
I installed just boot, system, and vendor via twrp and it booted fine.
This black and white will take some getting used to
Click to expand...
Click to collapse
Are you able to boot back to twrp?
Hogyoku said:
I got stuck in the twrp screen flashing the logo
---------- Post added at 09:44 PM ---------- Previous post was at 09:44 PM ----------
Are you able to boot back to twrp?
Click to expand...
Click to collapse
Nope, I will try formatting my data when I get off work
Boots fine without TWRP. Flashed from 7.1.2 beta2
Good news for bluetooth audio users: aptX, aptX-HD, and LDAC codecs available plus sample rate, bits per sample, channel mode, and LDAC playback quality now available.
Anyone know how to use Picture in Picture mode?
Albinoman said:
Anyone know how to use Picture in Picture mode?
Click to expand...
Click to collapse
This is a screenshot from Android Messages app with chrome PIP
Zavon said:
This is a screenshot from Android Messages app with chrome PIP
Click to expand...
Click to collapse
That's pretty sweet
flashed just the baseband thinking i could easily flash back to a different one and now it wont flash back any ideas?
edit: fixed it i had to flash a newer bootloader then it let me flash back to a radio that worked WEW!!!
So I'm currently on PureNexus / NOF27C.
I'm assuming if there is an updated baseband / radio with O, I can simply flash these and won't have any repercussions?
IIRC the baseband / bootloader has no effect over the version of the OS, right?
Edit: flashed new bootloader and radio from O on 7.1.2 PN fine.
Hi,
I've got an Asus Zenfone Pro Max M1 (6/64). And of course I would like to install custom recovery and flash magisk on it.
The thing is after I unlocked the bootloader, and installed the twrp recovery, my device won't reboot into twrp recovery. It goes blank every time and when i reboot normally, it boots up fine. And when I try getting into recovery from there, the stock recovery comes out. Also the same thing happens when I tried to install redwolf recovery.
I tried finding the solution here and everywhere else, but none helped. If anyone could help me, that would be very much appreciated.
Thank you.
There's no solution to this but i also faced same.
Only Trial and Error will work.
Here's what worked for me if i remember correct
Boot to fastboot
flash twrp again (have to do this every time after booting to stock recovery )
Keep holding vol down first
Then press and hold power
It should work now
Its tricky and no one seems have written a guide on why this happens on how to solve this but don't give up, its doable! Best of Luck
Yes, the issue is there. Try the above method or you can also flash a different version of recovery which if i remember correctly was shared in another forum (I am not sure if XDA rules allow me to say it). It was for those whose TWRP froze, search on forum.
dastan4eva said:
There's no solution to this but i also faced same.
Only Trial and Error will work.
Here's what worked for me if i remember correct
Boot to fastboot
flash twrp again (have to do this every time after booting to stock recovery )
Keep holding vol down first
Then press and hold power
It should work now
Its tricky and no one seems have written a guide on why this happens on how to solve this but don't give up, its doable! Best of Luck
Click to expand...
Click to collapse
Hi, thanks for your suggestion.
I've been trying your suggested method since morning and unfortunately, no joy.
Any other way you might have known?
Tianhe said:
Yes, the issue is there. Try the above method or you can also flash a different version of recovery which if i remember correctly was shared in another forum (I am not sure if XDA rules allow me to say it). It was for those whose TWRP froze, search on forum.
Click to expand...
Click to collapse
Hi, thanks for suggesting this. Although I tried finding it on forum, no success. If you could pinpoint the forum, that would be highly appreciated. Starting to get annoyed with this problem though lol
PS C:\Users\HP\Desktop\Asus\unlock\unlock> fastboot devices
C4ATAS000000J2E fastboot
PS C:\Users\HP\Desktop\Asus\unlock\unlock> fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (58328 KB)...
OKAY [ 1.250s]
writing 'recovery'...
OKAY [ 0.000s]
finished. total time: 1.250s
PS C:\Users\HP\Desktop\Asus\unlock\unlock> fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.259s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.259s
PS C:\Users\HP\Desktop\Asus\unlock\unlock>
Also failed to load through command.
Tried changing the twrp.img name to recovery.img, still the same.
This version of twrp posted by Jide1 helped me solved the problem.
https://cloud.mail.ru/public/75Xm/7pGy9YwFu
azfangerrard said:
This version of twrp posted by Jide1 helped me solved the problem.
https://cloud.mail.ru/public/75Xm/7pGy9YwFu
Click to expand...
Click to collapse
Nice to know it worked but Just one suggestion . From this twrp flash the latest twrp before moving on
dastan4eva said:
Nice to know it worked but Just one suggestion . From this twrp flash the latest twrp before moving on
Click to expand...
Click to collapse
Noted with thanks.
azfangerrard said:
Hi, thanks for suggesting this. Although I tried finding it on forum, no success. If you could pinpoint the forum, that would be highly appreciated. Starting to get annoyed with this problem though lol
Click to expand...
Click to collapse
Apologies for the late reply, I see that you have found the relevant file so problem solved !
azfangerrard said:
Noted with thanks.
Click to expand...
Click to collapse
reboot to bootloader
Flash twrp via adb
Long press power button to switch off
Press and hold power and vol down button until unlocked bootloader warning shows
You will be rebooted to twrp
Try Wolf RWRP
azfangerrard said:
This version of twrp posted by Jide1 helped me solved the problem.
https://cloud.mail.ru/public/75Xm/7pGy9YwFu
Click to expand...
Click to collapse
How did you flash the above one
Running ADB command and reboot or directly to twrp
Niki Exodia007 said:
How did you flash the above one
Running ADB command and reboot or directly to twrp
Click to expand...
Click to collapse
Hi, yeah run the command when the device is connected in fastboot mode and reboot into recovery.
azfangerrard said:
Hi, yeah run the command when the device is connected in fastboot mode and reboot into recovery.
Click to expand...
Click to collapse
Hey bud thanks booted into rwrp but when I flash the updated one it freezes
May I know which TWRP are u using now
Niki Exodia007 said:
Hey bud thanks booted into rwrp but when I flash the updated one it freezes
May I know which TWRP are u using now
Click to expand...
Click to collapse
This is the one mate. After booted into system, I updated the twrp using the official twrp app. But it works just fine without the latest updated version too.
https://cloud.mail.ru/public/75Xm/7pGy9YwFu
azfangerrard said:
This is the one mate. After booted into system, I updated the twrp using the official twrp app. But it works just fine without the latest updated version too.
https://cloud.mail.ru/public/75Xm/7pGy9YwFu
Click to expand...
Click to collapse
Bud I am using the twrp which is in the link
But this one cannot flash pie roms
But I am r u using other than these
Niki Exodia007 said:
Bud I am using the twrp which is in the link
But this one cannot flash pie roms
But I am r u using other than these
Click to expand...
Click to collapse
Ah I see, now I understand.
The solution to your problem is somewhere in this thread https://forum.xda-developers.com/asus-zenfone-max-pro-m1/development/recovery-twrp-3-2-1-x-t3787134
I noticed someone (user: Jide1 if I'm not mistaken) posted the twrp version that's compatible with pie rom which has problem loading into twrp. Look it up.
Niki Exodia007 said:
Bud I am using the twrp which is in the link
But this one cannot flash pie roms
But I am r u using other than these
Click to expand...
Click to collapse
Hey mate, this is it. I looked it up
https://www.dropbox.com/s/66kndzisymdq44t/twrp-3.2.3.0(pie)stockboot.img?dl=0
Again, thanks to @jide1
azfangerrard said:
Ah I see, now I understand.
The solution to your problem is somewhere in this thread https://forum.xda-developers.com/asus-zenfone-max-pro-m1/development/recovery-twrp-3-2-1-x-t3787134
I noticed someone (user: Jide1 if I'm not mistaken) posted the twrp version that's compatible with pie rom which has problem loading into twrp. Look it up.
Click to expand...
Click to collapse
Buddy searched it but the file does not exist
Can you send the file in pm if you have
---------- Post added at 05:39 PM ---------- Previous post was at 05:35 PM ----------
azfangerrard said:
Hey mate, this is it. I looked it up
https://www.dropbox.com/s/66kndzisymdq44t/twrp-3.2.3.0(pie)stockboot.img?dl=0
Again, thanks to @jide1
Click to expand...
Click to collapse
Yes I looked the same link
But the file is deleted
---------- Post added at 05:41 PM ---------- Previous post was at 05:39 PM ----------
azfangerrard said:
Hey mate, this is it. I looked it up
https://www.dropbox.com/s/66kndzisymdq44t/twrp-3.2.3.0(pie)stockboot.img?dl=0
Again, thanks to @jide1
Click to expand...
Click to collapse
Yes I looked the same link
But the file is deleted
Device - SM-A205FN.
Firmware - A205FNXXSACVB1.
Custom ROM - AospExtended-v9.0-a20-UNOFFICIAL-20220225-2212.
TWRP version - 3.6.1_9-0 [official].
I can’t install this ROM in any way, because when flashing into TWRP, error 1 pops up. I tried to clear various partitions and also deleted the first two lines of the updater-script file.
ANFOR7 said:
Device - SM-A205FN.
Firmware - A205FNXXSACVB1.
Custom ROM - AospExtended-v9.0-a20-UNOFFICIAL-20220225-2212.
TWRP version - 3.6.1_9-0 [official].
I can’t install this ROM in any way, because when flashing into TWRP, error 1 pops up. I tried to clear various partitions and also deleted the first two lines of the updater-script file.
Click to expand...
Click to collapse
Is that latest stock already?
Used "format data" as well?
Changing file system to and fro helped me once when formatting didn't help.
bmwdroid said:
Is that latest stock already?
Used "format data" as well?
Changing file system to and fro helped me once when formatting didn't help.
Click to expand...
Click to collapse
Did you change the file system of the system and did it help you avoid error 1?
I use the latest official firmware and the latest version of the official TWRP and also format the data before installing a custom ROM.
ANFOR7 said:
Did you change the file system of the system and did it help you avoid error 1?
Click to expand...
Click to collapse
Yes. To f2fs and back to ext4.
ANFOR7 said:
I use the latest official firmware and the latest version of the official TWRP and also format the data before installing a custom ROM.
Click to expand...
Click to collapse
bmwdroid said:
Yes. To f2fs and back to ext4.
Click to expand...
Click to collapse
Did you reboot?
ANFOR7 said:
Did you reboot?
Click to expand...
Click to collapse
Yes to TWRP
bmwdroid said:
Yes to TWRP
Click to expand...
Click to collapse
Did not help(
ANFOR7 said:
Did not help(
Click to expand...
Click to collapse
Sorry to hear that.
Last thing I would try is flashing latest stock ROM and start from scratch.
bmwdroid said:
Sorry to hear that.
Last thing I would try is flashing latest stock ROM and start from scratch.
Click to expand...
Click to collapse
This is what I do before every attempt to install a custom ROM.
bmwdroid said:
Sorry to hear that.
Last thing I would try is flashing latest stock ROM and start from scratch.
Click to expand...
Click to collapse
Should I try to lock and then unlock the bootloader back? I heard it clears partitions completely. By the way, in the TWRP tar-archive, not only custom recovery.img, but also custom vbmeta.img to bypass protection. Could this be causing error 1?
ANFOR7 said:
Should I try to lock and then unlock the bootloader back?
Click to expand...
Click to collapse
can't give you any advice here. I'd search other threads before to learn more what happens then.
ANFOR7 said:
I heard it clears partitions completely.
Click to expand...
Click to collapse
afaik it's only doing a factory reset.
ANFOR7 said:
By the way, in the TWRP tar-archive, not only custom recovery.img, but also custom vbmeta.img to bypass protection. Could this be causing error 1?
Click to expand...
Click to collapse
Probably but I'm not sure
Edit: just had a look inside the official twrp-3.6.1_9-0-a20.img.tar and I see only recovery.img
Where did you get the TWRP you're using from.
bmwdroid said:
just had a look inside the official twrp-3.6.1_9-0-a20.img.tar and I see only recovery.img
Where did you get the TWRP you're using from.
Click to expand...
Click to collapse
Someone on another forum gave me an archive with recovery.img, boot.img and vbmeta.img. I extracted only vbmeta.img from there and put it in the archive with the official twrp.
Link to the file: https://ru.files.fm/f/wdzcpqbjd
ANFOR7 said:
Someone on another forum gave me an archive with recovery.img, boot.img and vbmeta.img. I extracted only vbmeta.img from there and put it in the archive with the official twrp.
Link to the file: https://ru.files.fm/f/wdzcpqbjd
Click to expand...
Click to collapse
I c
bmwdroid said:
I c
Click to expand...
Click to collapse
Sorry, I can't speak English, I communicate through Google Translate. I don't understand what "I c" means.
ANFOR7 said:
Sorry, I can't speak English, I communicate through Google Translate. I don't understand what "I c" means.
Click to expand...
Click to collapse
I c = I see
Here's the patched boot.img for OnePlus 8T Android 13 KB2005_11_F.13 and F.15
Bootloader must be unlocked
(Have the img on your PC)
Instructions:
1: Reboot to bootloader "adb reboot bootloader"
2: Run CMD "fastboot flash boot" ~name of img~
Profit!
You're now rooted.
I've also attached the stock boot.img just in case anyone wants it.
Boot - Google Drive
drive.google.com
Thank's
BobbyLynn said:
Here's the patched boot.img for OnePlus 8T Android 13 KB2005_11_F.13
Bootloader must be unlocked
(Have the img on your PC)
Instructions:
1: Reboot to bootloader "adb reboot bootloader"
2: Run CMD "fastboot flash boot magisk_patched-25200_575Sf.img"
You're now rooted.
I've also attached the stock boot.img just in case anyone wants it.
Boot - Google Drive
drive.google.com
Click to expand...
Click to collapse
what if there is ota update?
MevishL said:
what if there is ota update?
Click to expand...
Click to collapse
I highly doubt there'll be another OTA until next month. Check with the developer of the unofficial orange fox recovery, he'll most likely release a new version for A13. If not, I'll pull the boot.img and patch it again and post it here.
MevishL said:
what if there is ota update?
Click to expand...
Click to collapse
Nevermind he's already released a version for A13. Here it is
Thread '[RECOVERY][UNOFFICIAL] OrangeFox Recovery Project [OnePlus 8t / 9r] [13-Nov-2022]' https://forum.xda-developers.com/t/...ry-project-oneplus-8t-9r-13-nov-2022.4391139/
BobbyLynn said:
I highly doubt there'll be another OTA until next month. Check with the developer of the unofficial orange fox recovery, he'll most likely release a new version for A13. If not, I'll pull the boot.img and patch it again and post it here.
Click to expand...
Click to collapse
okay thx , much appreciated
BobbyLynn said:
Nevermind he's already released a version for A13. Here it is
Thread '[RECOVERY][UNOFFICIAL] OrangeFox Recovery Project [OnePlus 8t / 9r] [13-Nov-2022]' https://forum.xda-developers.com/t/...ry-project-oneplus-8t-9r-13-nov-2022.4391139/
Click to expand...
Click to collapse
what if i bricked my phone , how do i flash stock file. do i need to download it in oxygen updater , and then?
MevishL said:
what if i bricked my phone , how do i flash stock file. do i need to download it in oxygen updater , and then?
Click to expand...
Click to collapse
Lol don't tell me you've bricked it!!! You can probably flash the stock boot.img and that might fix it. Otherwise you'll have to use the msm tool to reflash the firmware.
BobbyLynn said:
Lol don't tell me you've bricked it!!! You can probably flash the stock boot.img and that might fix it. Otherwise you'll have to use the msm tool to reflash the firmware.
Click to expand...
Click to collapse
no i didn't ! i'm just scared i might brick it cuz oneplus is harder to deal with than my previous phones . thnks for helping
MevishL said:
no i didn't ! i'm just scared i might brick it cuz oneplus is harder to deal with than my previous phones . thnks for helping
Click to expand...
Click to collapse
Well if you're worried about bricking it then before you start making modifications, be sure to have the latest msm for it on your PC, and also take a full backup using Orange Fox recovery, and also have the stock boot.img on your PC. And if anything goes wrong just flash the stock boot.img. And if that doesn't fix it then restore the backup, and if that still doesn't work then you'll have to do a complete restore using a msm tool
BobbyLynn said:
Well if you're worried about bricking it then before you start making modifications, be sure to have the latest msm for it on your PC, and also take a full backup using Orange Fox recovery, and also have the stock boot.img on your PC. And if anything goes wrong just flash the stock boot.img. And if that doesn't fix it then restore the backup, and if that still doesn't work then you'll have to do a complete restore using a msm tool
Click to expand...
Click to collapse
BobbyLynn said:
Well if you're worried about bricking it then before you start making modifications, be sure to have the latest msm for it on your PC, and also take a full backup using Orange Fox recovery, and also have the stock boot.img on your PC. And if anything goes wrong just flash the stock boot.img. And if that doesn't fix it then restore the backup, and if that still doesn't work then you'll have to do a complete restore using a msm tool
Click to expand...
Click to collapse
now u made it clear in my head , thx for all
MevishL said:
now u made it clear in my head , thx for all
Click to expand...
Click to collapse
No problem. If you run into any problems just let me know and I'll do what I can to figure out the simplest solution
I flash this boot.img and work like a charm easy root. Don't forget to post boot for next updates for KB2005. Thanks
Can these instructions be used for the KB2007?
kevinco1 said:
Can these instructions be used for the KB2007?
Click to expand...
Click to collapse
If it's Android 13 11_F.13 then yes. But Orange Fox has a working recovery for A13 on our phone. So you can always flash Magisk that way if you want
MrOnizuka said:
I flash this boot.img and work like a charm easy root. Don't forget to post boot for next updates for KB2005. Thanks
Click to expand...
Click to collapse
As long as I have this phone I'll continue to post the patched boot.img after each update
BobbyLynn said:
As long as I have this phone I'll continue to post the patched boot.img after each update
Click to expand...
Click to collapse
It is your time to shine again, good sir F.15 is upon us!
Thank you, kindly.
BobbyLynn said:
As long as I have this phone I'll continue to post the patched boot.img after each update
Click to expand...
Click to collapse
i have kb2005 but when i install ota update f.15 , it says installation failed at 26% . before that , i fastboot flashed stock boot.img. What should i do ?
Marduc said:
It is your time to shine again, good sir F.15 is upon us!
Thank you, kindly.
Click to expand...
Click to collapse
Thanks for reminding me. I'll upload the new boot.img shortly
MevishL said:
i have kb2005 but when i install ota update f.15 , it says installation failed at 26% . before that , i fastboot flashed stock boot.img. What should i do ?
Click to expand...
Click to collapse
You did flash unmodified boot.img before trying to update? Well, honestly idk why it won't install. Maybe you should try a different method of installing the update, like manually installing it