Official TWRP is now available: https://twrp.me/asus/zenfone9.html
IMPORTANT NOTES:
CleanSlate custom kernel is not currently compatible with TWRP for this device (Kirisakura is compatible as of v2.0.6).
This device has a recovery partition (2, in fact), and fastboot boot is disabled in the bootloader. Flashing TWRP to the recovery partition is the only way to use it.
If you attempt to fastboot boot the TWRP image, your device may end up unbootable. YOU'VE BEEN WARNED.
Any questions, comments, feedback, or concerns should always be accompanied by logs (recovery log, logcat, dmesg)
TWRP Trees
Common: https://github.com/TeamWin/android_device_asus_sm84xx-common
Device: https://github.com/TeamWin/android_device_asus_AI2202
Thanks for your work!
Installed as on twrp.me described wont boot (https://twrp.me/asus/zenfone9.html)
Had to flash stock recovery again.
Rooted device on 32.2050.2050.29 with kirisakura-kernel.
Any idea what im doing wrong?
Hermann2306 said:
Thanks for your work!
Installed as on twrp.me described wont boot (https://twrp.me/asus/zenfone9.html)
Had to flash stock recovery again.
Rooted device on 32.2050.2050.29 with kirisakura-kernel.
Any idea what im doing wrong?
Click to expand...
Click to collapse
If you're not on stock kernel, then that's probably the problem. I know the custom kernel situation is different on this device than previous ones. This may be something that @Freak07 & I have to look into together. In the meantime, can you restore back to stock kernel and confirm that TWRP works, and then install Kirisakura and see if everything still works?
Restored stock kernel with kernelflasher but now it wont boot. Tried to change the slot to a but isnt allowed in fastboot.
Have to find out now how to change the slot or install stock kernel via fastboot...
Hermann2306 said:
Restored stock kernel with kernelflasher but now it wont boot. Tried to change the slot to a but isnt allowed in fastboot.
Have to find out now how to change the slot or install stock kernel via fastboot...
Click to expand...
Click to collapse
It doesn't sound like you followed the procedure in the Kirisakura thread FAQ to fully return to stock. Can you confirm exactly what you did?
just restored the backup i made with kernelflasher befor i installed the custom kernel and rebooted.
Hermann2306 said:
just restored the backup i made with kernelflasher befor i installed the custom kernel and rebooted.
Click to expand...
Click to collapse
I'm not familiar with that app, sorry. I just know that's not the process mentioned in his thread, so until you do that, I can't really confirm what the problem could be.
ok, im back on stock. flashing following files helped. i will test twrp again later and report. thanks for your replies.
fastboot flash boot boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot reboot fastboot
fastboot flash vendor_dlkm vendor_dlkm.img
fastboot reboot
With stock kernel twrp works. Just installed as described on twrp.me. The official twrp app from playstore crashes after root allowing.
For everyone who comes from custom kernel flash the files from your actual firmware (payload-dumper) as described in the post above.
Are you working on custom kernel support?
Hermann2306 said:
With stock kernel twrp works. Just installed as described on twrp.me. The official twrp app from playstore crashes after root allowing.
For everyone who comes from custom kernel flash the files from your actual firmware (payload-dumper) as described in the post above.
Are you working on custom kernel support?
Click to expand...
Click to collapse
From stock, I just flashed the Kirisakura zip in TWRP and my device booted up fine.
EDIT: While the above is true, TWRP no longer functions after installing the kernel, and the device won't reboot again after installing it. So something is definitely wrong somewhere.
For now, I can only suggest not using it with a custom kernel until we figure this out.
Ok, flashing with EXKernelManager works also.
update
I can do reboots but twrp doesnt work anymore
Hermann2306 said:
Ok, flashing with EXKernelManager works also.
update
I can do reboots but twrp doesnt work anymore
Click to expand...
Click to collapse
Yes, there seems to be an issue in the kernel that's preventing TWRP from working. I'm not sure what the issue is, unfortunately.
So every time I restore a back up, do I have to delete all lock screen requirements ?
If that's the case, I would have to redo my fingerprints every time
c19932 said:
So every time I restore a back up, do I have to delete all lock screen requirements ?
If that's the case, I would have to redo my fingerprints every time
Click to expand...
Click to collapse
Yes.
Quick PSA for anyone using this TWRP that also wants to use a custom kernel:
As of Kirisakura 2.0.6, the custom kernel and TWRP can now co-exist. This is due to the changes that allowed a monolithic kernel build. Presently, CleanSlate has not adopted those changes, but if/when it does, I will remove that disclaimer from the OP.
Thanks to @arter97, @Freak07, & @tbalden for supporting this device!
Is the twrp compatible with android 13?
NisseGurra said:
Is the twrp compatible with android 13?
Click to expand...
Click to collapse
There's a really easy way to find out...
Captain_Throwback said:
There's a really easy way to find out...
Click to expand...
Click to collapse
I getting decrypt errors that why the q
NisseGurra said:
I getting decrypt errors that why the q
Click to expand...
Click to collapse
Then you should post some logs
Will do
Related
TL;DR: Nexus 9 bootloops with every ROM other than stock.
My Nexus 9 will bootloop whenever any custom ROM is installed on it. I follow the usual steps in TWRP (downloading ROM and Gapps, wiping factory reset, flashing the zips and wipe dalvik/cache) will not get any error during installation and regardless of the ROM, I will get my nexus stuck on Google logo. Then I will have to unroot and install stock again and it'll work.
Ive also tried Wugfresh Nexus Root Toolkit and it won't work either. As long as Im on stock, I can root as well and everything is fine.
Any idea what could be happening? I wanna get rid of the damn lag. Have tried Cyanogenmod, Slimrom6 and Pure Nexus Project. All with their recommended gapps and will always end up with my tablet stuck in the Google logo.
Any help is very appreciated.
Sounds like you are doing everything right..
How long are you waiting for the device to start up ? Is it possible you aren't simply waiting long enough ? I'd give it a good 10 - 20 minutes on 1st boot before deciding it's hung in a boot loop.
I am having the exact same problem. I have tried so many roms that install correctly and then when flashing gapps and rebooting it is stuck on the Google logo. And I left my tablet on for a few hours so its definitely bootlooping.
The only thing that comes to mind is bootloader... If you coming to androind 7.x from android 6.x, you need to flash new bootloader (for example via ADB), otherwise you'll end up in a bootloop.
yup, happening to me too. so, how can i flash the factory image now? thanks.
It's in the stickies. http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Sent from my Nexus 5X using XDA-Developers mobile app
links to 7.x compatible bootloader where?
maelfilk said:
If you coming to androind 7.x from android 6.x, you need to flash new bootloader (for example via ADB), otherwise you'll end up in a bootloop.
Click to expand...
Click to collapse
I understand that i'll have to use adb (actually fastboot) to flash the bootloader. But where do i get the right one for android 7.x and flpunder device?
Could you please post the links for that?
Thanks in advance!
nexacan said:
I understand that i'll have to use adb (actually fastboot) to flash the bootloader. But where do i get the right one for android 7.x and flpunder device?
Could you please post the links for that?
Thanks in advance!
Click to expand...
Click to collapse
You can download the necessary image here: https://developers.google.com/android/images
Inside the archive you'll find bootloader and vendor
bootloader flashing process: enough to "fastboot flash bootloader boot*.img"?
maelfilk said:
You can download the necessary image here: https://developers.google.com/android/images
Inside the archive you'll find bootloader and vendor
Click to expand...
Click to collapse
I assume i need the latest 7.0.0 (NRD91N, Nov 2016) bootloader which is inside the latest build?
Then i will need to go through the process like:
Code:
fastboot flash bootloader bootloader-flounder-3.48.0.0141.img
Or do i have to do more like described here (Steps 8-9)?
Your help is appreciated, thanks again!
ps: for others who got stuck in the bootloop and don't know how to stop it or turn off the device:
1. reboot into recoverymode in case you have twrp
2. open a terminal
3. type in
Code:
poweroff
an hit enter
Yes, NRD91N
Well , all i did was simple
fastboot flash bootloader bootloader-flounder-3.48.0.0141.img
once complete
fastboot reboot-bootloader
That's it
Still not booting...
maelfilk said:
Yes, NRD91N
fastboot flash bootloader bootloader-flounder-3.48.0.0141.img
fastboot reboot-bootloader
...
That's it
Click to expand...
Click to collapse
Thanks for clarifying that. Unfortunately i still can't boot into AOSP_flounder_11-18-2016.zip
which i flashed afterwards. The bootloader is shown correctly though. But when i start the
Nexus 9 the message https://g.co/ABH is shown in red.
Which rom are you running? A CM build or AOSP?
ps: trying with cm-14.1-20161027-UNOFFICIAL-flounder.zip now, but boot seems to hang too and the upper part
of the Nexus 9 is getting really warm. I will leave it for 15 more minutes to wait and see what happens.
nexacan said:
Thanks for clarifying that. Unfortunately i still can't boot into AOSP_flounder_11-18-2016.zip
which i flashed afterwards. The bootloader is shown correctly though. But when i start the
Nexus 9 the message https://g.co/ABH is shown in red.
Which rom are you running? A CM build or AOSP?
Click to expand...
Click to collapse
Hmm sorry i don't knwo why this is happening.
Currently i reverted back to marshmallow roms, i find them more stable.
Do you have twrp? After flashing bootloader i go to twrp and do complete wipe and format data, then flash new rom. I had no problems booting.
maelfilk said:
Do you have twrp?
Click to expand...
Click to collapse
Sure, the latest from TWRP
twrp-3.0.2-1-flounder.img 13M 2016-08-24 16:30:03 EDT
maelfilk said:
After flashing bootloader i go to twrp and do complete wipe and format data, then flash new rom. I had no problems booting.
Click to expand...
Click to collapse
I will try it again - exactly as you describe it. Maybe i missed a step.
How long did you wait after reboot for the system to start up?
nexacan said:
Sure, the latest from TWRP
twrp-3.0.2-1-flounder.img 13M 2016-08-24 16:30:03 EDT
I will try it again - exactly as you describe it. Maybe i missed a step.
How long did you wait after reboot for the system to start up?
Click to expand...
Click to collapse
About 10-15 minutes
It works now!
Thank you maelfilk, i got i running now.
CM boots properly now - though i cannot configure it. During the Setup process
in the first step of selecting the language it crashes. I am sure this will be fixed
with a later version of CM-14.1.
Does someone know any other source for CM-14.1 for flounder?
Meanwhile i will try AOSP again.
Edit: AOSP boots properly but unfortunately WLAN does not work in the AOSP_flounder_11-18-2016.zip build.
I guess this is why you stick to the 6.x builds maelfilk.
большое спасибо
nexacan said:
большое спасибо
Click to expand...
Click to collapse
Glad it works
As for wlan problem, did you flash the vendor as well? If not it might be the problem
link to the "vendor"
maelfilk said:
Glad it works
As for wlan problem, did you flash the vendor as well? If not it might be the problem
Click to expand...
Click to collapse
Man, you are so helpfull! Where do i find the "vendor" (drivers?) please?
I guess i will find it as it is described here
nexacan said:
Man, you are so helpfull! Where do i find the "vendor" (drivers?) please?
I guess i will find it as it is described here
Click to expand...
Click to collapse
In the archive with bootloader is another archive with vendor and other images. Just flash it in twrp as in the instructions in the link you gave. If you have trouble with wlan or camera it usually means that vendor is outdated.
Black bootscreen and hanging after flashing vendor.img (only vendor.img)
maelfilk said:
In the archive with bootloader is another archive with vendor and other images. Just flash it in twrp as in the instructions...
Click to expand...
Click to collapse
I did that and now there is no bootscreen, and the Nexus 9 does not boot up
Maybe i am missing something again? I did a wipe and fresh install, but that did not help.
Also TWRP disappears after flashing vendor.img
nexacan said:
I did that and now there is no bootscreen, and the Nexus 9 does not boot up
Maybe i am missing something again? I did a wipe and fresh install, but that did not help.
Also TWRP disappears after flashing vendor.img
Click to expand...
Click to collapse
Are you sure you chose to flash vendor.img in vendor partition in twrp?
SGP-321 / LTE / pollux
Bootloader unlocked
CM13 installation:
- extracted boot.img and installed by: fastboot flash boot boot.img
- installed CM13 bei "update" from inside CM_recovery
- everything works OK until now.
TWRP 3.0.2.0 instal:
- installed by ADB "fastboot flash boot TWRP.img": sending/writing 'boot': OKAY
- fastboot reboot: rebooting into TWRP
In TWRP/Reboot SYSTEM: this reboots back into TWRP, does NOT boot CM13. Why?
CM13 installed again by "install" in TWRP: this installs CM13 but overwrites TWRP with the CM13_boot.img. So after the installation TWRP is gone and i have only the CM recovery.
Installing TWRP again has the same result as above: no booting of CM13, only booting into TWRP.
How can i solve this?
(PS: on my another xperia, "pollux_windy"/WiFi everything works ok, no issues with TWRP/CM13. )
nicky-xda said:
SGP-321 / LTE / pollux
Bootloader unlocked
CM13 installation:
- extracted boot.img and installed by: fastboot flash boot boot.img
- installed CM13 bei "update" from inside CM_recovery
- everything works OK until now.
TWRP 3.0.2.0 instal:
- installed by ADB "fastboot flash boot TWRP.img": sending/writing 'boot': OKAY
- fastboot reboot: rebooting into TWRP
In TWRP/Reboot SYSTEM: this reboots back into TWRP, does NOT boot CM13. Why?
CM13 installed again by "install" in TWRP: this installs CM13 but overwrites TWRP with the CM13_boot.img. So after the installation TWRP is gone and i have only the CM recovery.
Installing TWRP again has the same result as above: no booting of CM13, only booting into TWRP.
How can i solve this?
(PS: on my another xperia, "pollux_windy"/WiFi everything works ok, no issues with TWRP/CM13. )
Click to expand...
Click to collapse
Use CM13 kernel (boot.img) with TWRP integrated or if you don't have it, flash TWRP to FOTA:
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Click to expand...
Click to collapse
Thanks a lot for the hint!
CM13 kernel (boot.img) with TWRP integrated: unfortunately i have not seen that anywhere mentionded until now. Where could i get that?
I have TWRP 3.0.2.0 for my "pollux_windy" that works fine, from the following download:
https://dl.twrp.me/pollux_windy/
I have been trying TWRP 3.0.2.0 for my "pollux" from the same site:
https://dl.twrp.me/pollux/
Is the TWRP for pollux_windy with integrated boot.img and the one for "pollux" without boot.img?
nicky-xda said:
unfortunately i have not seen that anywhere mentioned until now. Where could i get that?
Click to expand...
Click to collapse
here.
I actually don't know why it worked for you with windy, as when you flash fastboot flash boot TWRP.img it replaces stock CM boot.img and it won't boot, cause inside twrp.img is only recovery, but not kernel to boot system.
Thanks a lot for this excellent hint! It was a big help and it seems to work now perfectly.
pollux_windy / WiFi & TWRP:
After second thought i have to admit that i do not quite remember how exactly i installed TWRP on this one, it was some 2 months ago and i cannot remember any more:
- after unlocking the bootloader i extracted the "boot.img" from CM13 and installed it by "fastboot flash boot boot.img"
- then i installed CM13 by the option "update" in CM_recovery
- after that i maybe tried to install TWRP (from the link above) by the ADB command: fastboot flash recovery twrp.img. Would that have worked?
- or i did it by the app "TWRP manager" which i have also installed
In any case until your answer in this topic i have not heard about the "boot" part having to be integrated into TWRP for it to work on the xperia.
Anyway: it works on my pollux_windy ok.
BTW: if it should some time in the future be necessary to install TWRP again on my "windy" would you have a link for a TWRP+boot.img for the "windy" as well?
nicky-xda said:
Would that have worked?
- or i did it by the app "TWRP manager" which i have also installed
Click to expand...
Click to collapse
"fastboot flash recovery" command will not work, because sony devices (at least besides the very latest ones) don't have separate recovery partition, as nexus and other manufacturers have. That's why recovery should be integrated with kernel in boot.img
TWRP manager could have possibly installed it for you properly, but to FOTA partition which is used to install OTA updates on stock Sony firmware.
On unlocked bootloader it is not in use and could store TWRP recovery permanently (as normal recovery partition).
nicky-xda said:
BTW: if it should some time in the future be necessary to install TWRP again on my "windy" would you have a link for a TWRP+boot.img for the "windy" as well?
Click to expand...
Click to collapse
Sure. PM me, when you need it.
Did you follow my tutorial stricly ?
http://forum.xda-developers.com/xpe...de-tutorial-sony-xperia-tablet-z-lte-t3392831
djibe89 said:
Did you follow my tutorial stricly ?
http://forum.xda-developers.com/xpe...de-tutorial-sony-xperia-tablet-z-lte-t3392831
Click to expand...
Click to collapse
Yes, i did. But in your tutorial i do not mention anything about the sort of recovery it needs to wor properly: recovery inkluding the kernel. Did you read the hints by Rootk1t above in this topic?
Sony doesn't have a Recovery partition.
Hence you need a FOTAkernel compatible recovery (latest TWRP 3.x are) (hack that takes the Sony partition reserved for over the air updates, and turns it into a persistent recovery partition).
This guide : http://forum.xda-developers.com/xperia-s/general/twrp-recovery-to-fota-partition-guide-t3258821 looks good but read carefully.
Why don't you try to step back to my guide. Back to the recovery flash.
Fastboot flash temporary TWRP, enter TWRP, format partitions to F2FS, wipe data and then flash RESURECTION REMIX 5.7.4 + Black kernel for pollux + Gapps ?
I will update my tutorial this weekend to explain better.
Keep in touch
@Djibe: just take a look in this topic above, posting #4. This is a file including TWRP + kernel. Only this one i was able to successfully instal by the command:
fastboot flash boot twrp.img
The TWRP that you link in your guide does not work because it does not include the kernel.
You should have pointed it out better to be understandable better by beginners like me
Otherwise: thanks a lot for your help and support anyway
nicky-xda said:
@Djibe: just take a look in this topic above, posting #4. This is a file including TWRP + kernel. Only this one i was able to successfully instal by the command:
fastboot flash boot twrp.img
The TWRP that you link in your guide does not work because it does not include the kernel.
You should have pointed it out better to be understandable better by beginners like me
Otherwise: thanks a lot for your help and support anyway
Click to expand...
Click to collapse
Sorry sorry, i replied in a rush.
Enjoy TabZ
@Rootk1t: What about updating to the newest ver. TWRP 3.1.x?
Hi I had Xpower5 Rom. I wanted to try new Nougat. I had many issues with flash (error of processing system.sin and loader.sin). I dont know how now it work. After that I flashed AndroPlus 43 kernel and TWRP 3.0.2. Kernel works but No white led on startup and no recovery there (also adb reboot recovery not work) . I tried another img of twrp and nothing changed. Any idea how install recovery? Anybody has the same problem with flashing? Thanks
As this phone doesn't support universal recovery and only sports a ota partition that can be used for recovery but then requires a kernel that supports booting recovery from ota partition, it's a hustle to use non standard recovery systems.
Is there even a nougat compatible kernel with included TWRP ota boot support for this phone?
This should work
https://forum.xda-developers.com/showpost.php?p=70807294&postcount=132
Also patching the stock kernel with the rootkernel tool integrates working twrp.
Gewiz said:
This should work
https://forum.xda-developers.com/showpost.php?p=70807294&postcount=132
Also patching the stock kernel with the rootkernel tool integrates working twrp.
Click to expand...
Click to collapse
It works! Thanks. Problem was: no white LED flash there. I have to press vol down and power on.
But I have still have a problem with flashing. Error of processing file loader.sin or system.sin. I cant flash again anything
Make sure you use latest ver of flashtool 0.9.23.2
Gewiz said:
Make sure you use latest ver of flashtool 0.9.23.2
Click to expand...
Click to collapse
Yes I have latest version. I tried older version as well but nothing changed
hromanse said:
Yes I have latest version. I tried older version as well but nothing changed
Click to expand...
Click to collapse
Flash firmware 5.11 first and flash nougat firmware afterwards.
This should work
Not work as well
the 3.1 3.0.2 TWRP bundled in rootkernel 5.23 messess up the internal permissions, so it will appear to work until you try and recover, or - TWRP runs a wipe with mkext4fs
i was talking a bit about it in https://forum.xda-developers.com/showthread.php?t=3560135
---------- Post added at 18:16 ---------- Previous post was at 18:13 ----------
Gewiz said:
Flash firmware 5.11 first and flash nougat firmware afterwards.
This should work
Click to expand...
Click to collapse
Yeah, going back to Lollipop and going all the way up to Nougat works, this is what happened to me. I thought I had a psuedo-recovery-dual system boot .... where i could switch between Marshmallow and Nougat
But then I decided to factory reset, and that started all the problems.
NeoBeum said:
Yeah, going back to Lollipop and going all the way up to Nougat works, this is what happened to me...
Click to expand...
Click to collapse
Thanks! It works
hromanse said:
Thanks! It works
Click to expand...
Click to collapse
Just make sure Restore works, so you don't get burned thinking everything is ok and end up with 12GB of partition mismatched data backup after a month, like I did
Here is the last version at the moment of the Maze alpha ROM (tested only in 4GB version)
It's a complete ROM, not an OTA update, it can be flashed using the provided TWRP 3.2.1 version, I ported from a Jemmini (many thanks) version for Bluboo S1.
Unfortunately, the TWRP cannot be flashed (issue with the touch panel), only launched by fastboot.
The ROM is the same as the v8 official one except that it is rooted using Magisk 15.2 and busybox 1.27.2 (thanks to osm0sis) is installed in /system/xbin
There is also a SPFlashTool clean version of this ROM, useful in case of troubles (as official: no root, no busybox)
1- Reboot you phone in fastboot mode : adb reboot bootloader
2- Flash the provided TWRP : fastboot flash recovery recovery_maze_alpha_4G_twrp-321.img
3- Reboot to TWRP recovery
4- copy in your SDCARD and install, in the running TWRP, the downloaded ROM V09 : Maze_Alpha_4GB_v09_TWRP.zip
The first boot take some minutes so be patient.
Here the SPFlashTool versions :
MAZE_Alpha_4GB_V09_SPFT.zip
Here, if needed, my V09 TWRP backup (new one from 21/04/2018) :
TWRP_BACKUP_MAZE_Alpha_A_V09.zip
Credits to Jemmini and Magisk team.
Can you make this for the 6 gb version?
many thanks gonna ty it soon
Nautilus99 said:
Can you make this for the 6 gb version?
Click to expand...
Click to collapse
I do not have the 6GB version
If I can download a stock ROM and a recent OTA update, I will do that.
Maze do not help us unfortunately
No complete stock ROM, No kernel source nothing !!!!!!!!!!
dreambo said:
I do note have the 6GB version
If I can download a stock ROM and a recent OTA update, I will do that.
Maze do not help us unfortunately
No complete stock ROM, No kernel source nothing !!!!!!!!!!
Click to expand...
Click to collapse
Yes i know its sad, i did a backup of mine and root it but it didnt work the backup i had to do clean flash, if we can manage to have a twrp and a source of the stock roms we could make a deabloat and put update apps ( menssages, calendar etc) and put mods for awsome features i dont see RR or lineage putting thier hands on this phone
Thanks for this Rom.
Is there any root for the maze alpha x?
here
WiddleyScudds said:
Is there any root for the maze alpha x?
Click to expand...
Click to collapse
read
The ROM is the same as the v8 official one except that it is rooted using Magisk 15.2 and busybox 1.27.2 (thanks to osm0sis) is installed in /system/xbin
Click to expand...
Click to collapse
thorfr said:
read
Click to expand...
Click to collapse
I have an alpha x, not alpha.
Thanks for ROM
When I install this ROM, from TWRP, i need install anything for root (Supersu)? Or when I install this ROM, I have root?
rzoli71 said:
Thanks for ROM
When I install this ROM, from TWRP, i need install anything for root (Supersu)? Or when I install this ROM, I have root?
Click to expand...
Click to collapse
No it is already rooted.
Reboot your phone to android, and then install MagsikManager.apk
I am editing my post to give you a 100% working TWRP 3.2.1 for our beloved Maze Alpha 4G :victory:
thank you
After I installed this rom, and freezed the hot knot, baidu_location FM Radio, etc, the BT connection did not break.
dreambo said:
No it is already rooted.
Reboot your phone to android, and then install MagsikManager.apk
I am editing my post to give you a 100% working TWRP 3.2.1 for our beloved Maze Alpha 4G :victory:
Click to expand...
Click to collapse
Hi dreambo,
do You know if there's a stock rom for download from maze alpha x? I think it's important for normal users and developers to get one. For normal users it's important to have an option to reinstall stock version and for developers I think it's the source for custom roms (e.g. Lineage Os).
If You know a source, can You please give us a link?
ahorntaler said:
Hi dreambo,
do You know if there's a stock rom for download from maze alpha x? I think it's important for normal users and developers to get one. For normal users it's important to have an option to reinstall stock version and for developers I think it's the source for custom roms (e.g. Lineage Os).
If You know a source, can You please give us a link?
Click to expand...
Click to collapse
No I not have any source, I am just a simple user like any other.
If I have any source or if I can make a ROM for MAZE Alpha X, I will do it and I will share it with every body, as I do until now for the MAZE Alpha 4/64
Hi
Sorry for stupid question, but is flashing with SP Flashtool an option to get root without wiping all data (unlike all other methods involving bootloader unlocking)?
iBolitN said:
Hi
Sorry for stupid question, but is flashing with SP Flashtool an option to get root without wiping all data (unlike all other methods involving bootloader unlocking)?
Click to expand...
Click to collapse
Unfortunatly no. As you will see repeated times in the forum, people have issue with phone not booting after changing from stock recovery to twrp. This is do (most likely from) to verified boot setting. And by unlocking bootloader we can bypass verified boot. So without unlock you might get a successfull load into twrp, but android will not boot.
Hello to all and please help if you can.
After unlocking the bootloader and flash the rom I'v got orange state with bootloop. Then after trying to fix it (wrong way) and relock bootloader and got red state with bootloop. I read that flahing back to stock fix the problem but I have no success with the rom provided in this post, the v5 from maze, the latest flash tool and the maze alpha flash tool... in all cases I get DA error(maze flash tool) or DA MISHMATCH (sp flash tool). I also tried different pc and cable with no result and finaly can't get fastboot. If that helps I've got the same flash tool error before the procedure. Every help will be appreciated.
stargazer78 said:
Hello to all and please help if you can.
After unlocking the bootloader and flash the rom I'v got orange state with bootloop. Then after trying to fix it (wrong way) and relock bootloader and got red state with bootloop. I read that flahing back to stock fix the problem but I have no success with the rom provided in this post, the v5 from maze, the latest flash tool and the maze alpha flash tool... in all cases I get DA error(maze flash tool) or DA MISHMATCH (sp flash tool). I also tried different pc and cable with no result and finaly can't get fastboot. If that helps I've got the same flash tool error before the procedure. Every help will be appreciated.
Click to expand...
Click to collapse
First unlock again your bootloader and use fastboot to flash boot, recovery and system partitions:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img.
Those partition images can be found in the ROM for SPFlashTool I have provide.
After that you can boot android normally.
If you any TWRP backup, you can restore it after flashing the TWRP.
Thanks a lot for your reply....
the problem is that i cant boot into fastboot to unlock bootloader....
the phone bootloops all the time, shows the red state alert and even with vol+ pressed the menu to choose recovery or fastboot doesn't apear... thanks again.
dreambo said:
First unlock again your bootloader and use fastboot to flash boot, recovery and system partitions:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img.
Those partition images can be found in the ROM for SPFlashTool I have provide.
After that you can boot android normally.
If you any TWRP backup, you can restore it after flashing the TWRP.
Click to expand...
Click to collapse
Is there any way to unlock the bootloader in my situation or/and enter the fastboot mode in order to follow your steps... thanks.
Hello XDA developers, I'm in urgent and I have a really big problem. It sounds funny but, I deleted my realme ui recovery ,_,
I was trying to install PPUI 4.1 on my Realme 7 but I saw a tutorial that you have to erase the recovery to install TWRP. Please, I need a solution of how can I get it back. I also tried flashing a lot of recoveries and their vbmeta but nothing works. Sadly.
Edit: I'm on RMX2151_11_C.17 | Realme UI 2.0 Latest version
Here is the stock recovery
Chenes said:
Here is the stock recovery
Click to expand...
Click to collapse
You sure? I'm on RMUI2.0 and how do I flash it? Can I type 'fastboot boot recovery.img'? Are my data will be wiped?
Sorry for a lot of questions, haha
iOussamato_ said:
You sure? I'm on RMUI2.0 and how do I flash it? Can I type 'fastboot boot recovery.img'? Are my data will be wiped?
Click to expand...
Click to collapse
From what I read before, fastboot boot will only boot to that recovery file temporarily but I haven't tried it myself. It should be
Code:
fastboot flash recovery recovery.img
I'm not 100% sure it will work without problems, but if it did, your data will not be wiped.
I suggest you wait for someone else to answer coz I'm not expert. I only learned from guides in the telegram group.
Chenes said:
From what I read before, fastboot boot will only boot to that recovery file temporarily but I haven't tried it myself. It should be
Code:
fastboot flash recovery recovery.img
I'm not 100% sure it will work without problems, but if it did, you're data will not be wiped.
I suggest you wait for someone else to answer coz I'm not expert. I only learned from guides in the telegram group.
Click to expand...
Click to collapse
Can I have that Telegram group invite?
iOussamato_ said:
Can I have that Telegram group invite?
Click to expand...
Click to collapse
Realme 7 • Narzo 20 Pro • Global
Welcome To Realme 7 | Narzo 20 Pro Group • RM6785_updates(official-A12/A13)- @RM6785 / https://t.me/realme7updater • RM6785_Gaming- @RM6785Gaming • Realme 7 Cloud: @realme_7_cloud
t.me
iOussamato_ said:
You sure? I'm on RMUI2.0 and how do I flash it? Can I type 'fastboot boot recovery.img'? Are my data will be wiped?
Sorry for a lot of questions, haha
Click to expand...
Click to collapse
You can try, first, if fastboot works in your device, type adb reboot fastboot, once the script ends, quickly disconnect device from your PC and again reconnect it, you will be redirected to fastboot, if the bootloader is unlocked, you could flash it using fastboot commands.
If you can´t get it to work then you can flash it using SPFT https://spflashtool.com/, put the recovery, in the same folder, with the attached files. All the sources to can use the tool, here https://www.getdroidtips.com/bypass-mediateks-sp-flash-tool-authentication-protection/
SubwayChamp said:
You can try, first, if fastboot works in your device, type adb reboot fastboot, once the script ends, quickly disconnect device from your PC and again reconnect it, you will be redirected to fastboot, if the bootloader is unlocked, you could flash it using fastboot commands.
If you can´t get it to work then you can flash it using SPFT https://spflashtool.com/, put the recovery, in the same folder, with the attached files. All the sources to can use the tool, here https://www.getdroidtips.com/bypass-mediateks-sp-flash-tool-authentication-protection/
Click to expand...
Click to collapse
I have never used SPFlashTool before honestly, I'm just scared to break my phone or lost my data in it. I just wish to install a custom ROM
iOussamato_ said:
I have never used SPFlashTool before honestly, I'm just scared to break my phone or lost my data in it. I just wish to install a custom ROM
Click to expand...
Click to collapse
Most of the custom roms I've seen requires formatting data. Just to be sure have you unlocked bootloader already? That requires wiping data iirc.
If not then nothing will really work with what you're doing.
iOussamato_ said:
I have never used SPFlashTool before honestly, I'm just scared to break my phone or lost my data in it. I just wish to install a custom ROM
Click to expand...
Click to collapse
What you are saying now is totally different from what you firstly posted.
Installing a custom ROM doesn't require a stock recovery (just in case you are confusing), and obviously, to can switch from a stock ROM to a custom ROM, that has a total different basement, it's mandatory to format data, anyway, you should back up your data previously to do so.
SubwayChamp said:
What you are saying now is totally different from what you firstly posted.
Installing a custom ROM doesn't require a stock recovery (just in case you are confusing), and obviously, to can switch from a stock ROM to a custom ROM, that has a total different basement, it's mandatory to format data, anyway, you should back up your data previously to do so.
Click to expand...
Click to collapse
I meant, I wish to install a custom ROM but I cannot install a working recovery and wanted the stock one. Sorry
Chenes said:
Most of the custom roms I've seen requires formatting data. Just to be sure have you unlocked bootloader already? That requires wiping data iirc.
If not then nothing will really work with what you're doing.
Click to expand...
Click to collapse
Yes my bootloader is already unlocked
iOussamato_ said:
Yes my bootloader is already unlocked
Click to expand...
Click to collapse
Then you can root your phone 1st then backup your files to a computer and use migrate backup to backup app data. Note that migrate backup is limited to 4gb. Then do the fastboot flash i mentioned before
iOussamato_ said:
I meant, I wish to install a custom ROM but I cannot install a working recovery and wanted the stock one. Sorry
Click to expand...
Click to collapse
Why you are saying that you cannot install a working recovery, I don't know of any attempt you did to achieve it.
A stock recovery is not needed to install a custom ROM, and even you can't install a custom ROM using a stock recovery.
If you want to join, flashing your device and stuff like this, better learn how to use SPFT, also you have this tool https://github.com/bkerler/mtkclient, this can save your device, if something in the process goes wrong.
SubwayChamp said:
Why you are saying that you cannot install a working recovery, I don't know of any attempt you did to achieve it.
A stock recovery is not needed to install a custom ROM, and even you can't install a custom ROM using a stock recovery.
If you want to join, flashing your device and stuff like this, better learn how to use SPFT, also you have this tool https://github.com/bkerler/mtkclient, this can save your device, if something in the process goes wrong.
Click to expand...
Click to collapse
I wanted to flash stock rom to downgrade into Realme UI 1.0 then flash the custom recovery so I can flash a custom rom
iOussamato_ said:
I wanted to flash stock rom to downgrade into Realme UI 1.0 then flash the custom recovery so I can flash a custom rom
Click to expand...
Click to collapse
OK, then what you are trying to install is an "old" Android 10 based ROM, if this is the case, then just download a stock Android 10 ROM, flash it through SPFT, then use SPFT to flash the custom recovery, transfer the custom ROM to your external SD Card (preferably) or sideload it, through recovery, and flash it. In the process you need to unlock bootloader, and immediately to flash the custom recovery, boot to it, using hardware buttons.
SubwayChamp said:
OK, then what you are trying to install is an "old" Android 10 based ROM, if this is the case, then just download a stock Android 10 ROM, flash it through SPFT, then use SPFT to flash the custom recovery, transfer the custom ROM to your external SD Card (preferably) or sideload it, through recovery, and flash it. In the process you need to unlock bootloader, and immediately to flash the custom recovery, boot to it, using hardware buttons.
Click to expand...
Click to collapse
Do you know a tutorial of how to use SPFlashTool?
iOussamato_ said:
Do you know a tutorial of how to use SPFlashTool?
Click to expand...
Click to collapse
How to use SP Flash Tool
This is a step-by-step tutorial on how to flash stock rom to a Mediatek device using Smart Phone Flash tool. SP Flash tool is one application you could find very useful in fixing extreme cases of a br
www.hovatek.com
Alright so, it might sound funny but I think I fixed it. I was playing with my downloaded recoveries until I downloaded the stock recovery, it is compatible but when I do fastboot reboot recovery I get stuck at Orange State for like 30min and it boots me into the recovery so does anyone know a solution for this? And thank you for everything and sorry for wasting y'all's time. Sincereley.
iOussamato_ said:
Alright so, it might sound funny but I think I fixed it. I was playing with my downloaded recoveries until I downloaded the stock recovery, it is compatible but when I do fastboot reboot recovery I get stuck at Orange State for like 30min and it boots me into the recovery so does anyone know a solution for this? And thank you for everything and sorry for wasting y'all's time. Sincereley.
Click to expand...
Click to collapse
You have to boot to recovery using hardware buttons (PWR + vol. down), in regard to orange state, this is absolutely normal when bootloader was unlocked, it's not an issue but a cosmetic thing.