Database Info

[C2304] Installing TWRP or CWM recovery in the Xperia C

Well, I just purchased this device and came here after that to look at what we had and I'm disgusted.
And there are several reasons for that, being:
1 - Locked Bootloader...
2 - This forum seems somewhat abandoned, which leads it to be somewhat disorganized.
EdiT:
Thanks to our friend repey6 > http://forum.xda-developers.com/member.php?u=5704037
TWRP 2.8.7.0 is now included, and it works just ok, with all functionality.
I strongly recommend you to use it instead of any other recovery. Just make sure to backup your ROM again after installing it, as CWM or Carliv backups won't work in TWRP.
I replaced the old TWRP included in the attachments with the new one provided by repey6, but the installation process remains the same.
Plus, this was not created by me and it's mad old (2014). But still it works better than the Carliv Recovery we have available here...
So Let's go. The proccess is the same for both, just choose the recovery image you want in the end of the topic.
(almost forgot to say that if your phone bricks it's you responsibility, I tested it in mine and it is working fine)
STEPS:
STEP1- Root your phone (if it's not rooted yet).
To root your phone you'll need to:
a-Download the framaroot APK provided in the attachments
b-Install it then click in the Boromir option and the su binary will be installed.
c-Download SuperSU from google play store.
That's all, simple like that.
STEP2- Check your bootloader's S1 Version
a-Open your dialer and input *#*#7378423#*#* , then go to Service Info>Software Info> S1 Boot Version.
b- Check if yours is 2.14.J.2.6 or 2.14.J.2.13 or 2.14.J.2.16 . If yours is one of these go ahead, it should work just fine and you can proceed.
If yours is 2.14.J.0.68 do not proceed, as it will 100% brick your phone.
c- My phone has S1 Boot Version 2.14.J.1.15 and in spite of the developer having not mentioned anything about it, I risked it all and my phone flashed the recovery normally, so if your version is also 2.14.J.1.15, it should work just fine and you can proceed.
STEP3 - Install the recovery
NOW, BE EXTREMELY CAREFUL HERE, OTHERWISE YOU WILL HARD BRICK YOUR PHONE:
a-Download the mobileuncle.apk file provided in the attachments and install it.
b-Download the twrp_xperia_C.img file provided below and put it in your internal memory (not on the external). Rename it to recovery.img, otherwise mobile uncle won't see it.
Now, here's the part you have to mind, so you won't brick your phone.
Mobile uncle can install a recovery using one of two methods. One is by installing the image from your internal memory (which we'll be doing). Other is installing it from the internet.
Now, YOU DON'T WANT to install a recovery from the internet, as mobile uncle doesn't provide any image for your device. So if you flash any of these recoveries, you'll never be able to make your phone boot again.
See in the image below and you'll get what I mean:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
c - So, before proceeding TURN OFF YOUR WIFI AND DATA CONNECTIONS so that mobile uncle won't show any recovery from internet
d-Open mobile uncle.
e-Grant Super User
f-Press "Recovery Update"
g- With wifi turned off, you'll see only your recovery in the screen
h- Click it, the file size of the file I'm posting must be around 6MB ( 6210KB for CWM), if it's different cancel and download file again.
i- press ok and restart.
DONE
:good:
EDIT:
I just noticed that after flashing the recovery you might get your phone stuck in the SONY logo after it.
In fact it happened to me, but just once.
If that happens don't panick. Recove the cover of your phone and besides the SIM-2 slot you'll see a tiny role with the word "reset". Insert a needle in there and your phone will restart normally.
CREDITS FOR CWM
Prashanth Jraj
Credits for posting it on the net and for the original tutorial:
informationlord.com
credits for TWRP 2.8.7.0
Miha_xXx
Original Post (for TWRP - in Russian): Click Here
credits for this tutorial:
me
ATTACHMENTS BELOW

Thanks for the guide! Does this also work on the C2305 model, or is it strictly for C2304?

Syd_M said:
Thanks for the guide! Does this also work on the C2305 model, or is it strictly for C2304?
Click to expand...
Click to collapse
It should work in both, I'm using a recovery for C2305 in my C2304.
Just don't try flashing a C2305 ROM on your C2304. It will not hardbrick your phonw, but the SIM cards will not work and you will get a mad functioning phones.
Some custom ROM's based on stock firmware work in both though.

Hey anyone tried for xc 2305???

So my S1 bootloader version is: 2.14.J.0.68. Is it for sure there is nothing that can be done?

SMIT120 said:
Hey anyone tried for xc 2305???
Click to expand...
Click to collapse
sid4913 said:
So my S1 bootloader version is: 2.14.J.0.68. Is it for sure there is nothing that can be done?
Click to expand...
Click to collapse
Sorry for the late reply! Haven't been able to test this until recently due to an issue getting my PC to work properly with my phone. Anyway, I would like to confirm that I was able to flash this on my Xperia C2305 that had S1 Boot Version 2.14.J.0.68. The photo below is proof of CWM running on my Xperia C2305:
Things you will need:
WMShua SuperFlash: http://soft.flushrom.com/WMShuaSetup.exe (after installing, you can change the language to English by renaming Program Files/wmshua/language to Program Files/wmshua/language_x)
Xperia C 16.0.B.2.16 FTF: C2305_16.0.B.2.16_TacoNikky.ftf or C2305_16.0.B.2.16_Congngheviet.ftf (pick one; I used TacoNikky's version)
Procedure:
1. Open WMShua, then click on Flash (not Super Flash). Browse to the FTF file you downloaded. You can choose to backup system before flash (I unchecked it on mine). Follow the screenshot below for guidance:
2. Turn off your phone. Next, hold down the Vol- (volume down) button on your phone. While holding down, plug in the micro USB cable. The LED will flash red. When it changes to green, release the Vol- button. WMShua should automatically try to install the needed drivers. After installing drivers, it will begin the flashing process. If your phone turns on instead, simply unplug it from the USB, turn it off, then try again.
The flash process may take a long time (it took 30+ minutes for me), and sometimes it may look like it hanged, but it's actually working. Just be patient. Once it reaches 100%, your phone will automatically boot up. Check your S1 Boot Version—it should now be 2.14.J.2.16. You may find that you've lost root, so you will need to root it again (I use KingoRoot). After rooting, follow the instructions on the first post to install CWM or TWRP. Good luck!

[Completed] [OP3] After couple ROM change test my phone is unusable, HELP PLEASE !

Hello everyone,
I currently have a Oneplus 3 which is completly unusable and I'm asking for your help to make it working again.
Until yesterday I used OxygenOs 4.0.2 ROM and it was about a moment I was thinking about changing my OS for the LineageOS ROM on Android 7.1.1 .I already did in the past this kind of changement on my nexus 5 for CM 13.0 .
So, I prepared all the files I needed (TWRP, ROM, Gapps etc...) and compared a lot of similar tutorial for being able to do it perfectly and being sure everything will work fine.
Firstly, I unlocked my bootloader though my PC and installed TWRP whithout any problems.
After that, I started the flash of the ROM and the Gapps zip packs. Everything worked and I launched the OS for checking if everything work.
I also wanted to ROOT my phone so I rebooted it and went to recovery again for flashing the ROOT zip from the LineageOS website and I picked the ARM64 one because I saw on internet it was the one needed.
After that, when I reboot the phone onto the system I have to make a "reconfiguration process" on this kind of way : Choose language --> Restore from zero --> Choose network --> Google account.
But, after filed my google account information I was normally able to receive a text for the double checked of my account but never it never came and the configuration is finally unsuccessfull because IMPOSSIBLE to skip the "network" or "google account" step.
I also tried to connect my phone on an other google account without the double checked option and it doesn't work too with this king of alert : " The process doesn't work due to an unknow error. Try again in 24 hours " .
I concluded that the problem come from the ROOT ZIP file, so I put my phone again in recovery and I do a " wipe / factory reset " for doing the exact same process from the begining (installing ROM) until root with this time the ARM ROOT ZIP.
Finally, I got the exact same result with the Google Account problem.
I choosed to do the complete process a third time with this time the SuperSu v2.79 ZIP file .... Result still the same.
Finally, I stoped trying to root my phone and I did again a "Wipe / factory reset" for just installing LineageOS and the Gapps pack. And I was suprised to see that the same problem continue to happen ! I wipe the phone and did again and again and again.
But, after all of that I choosed to do it on an other way. I saw on internet that " format data" through TWRP could be a solution for cleaning everything and start from zero. I did it and the process failed ....
From this point, I am with a phone which can't do anything and which saying that's impossible for it to "mount data" and other but I prefer to show that part on pictures. I think it'll be better for understanding (Excuse me for the pink because my HTC One M7 spare phone) :
Above there are the information that TWRP give me when I start it :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
On an other hand, the phone is recognize by the computer just as a multimedia device and it's impossible to write on its memory or just having access on it :
I hope I was the most clear as I could and hoping as well for an existing solution for my issue (in better case with LineageOS on it with root working ! But I don't want to ask to much !).
Also, I am french and I apologize for my english if it can be weak sometimes.
Thank you in advance. I'll allways available if you need further information.
PS: Since my bootloader is unlocked I have these both pages when the phone boot (Picture 1 and 2) which normally permit me to boot onto the system, recovery, fastboot etc .... (Picture 3) but in reality there is NOTHING happening and I always have to do it on the classic way if I want to boot on recovery or fastboot (hold power button + ..... etc...) :

Up

Daftnap said:
Up
Click to expand...
Click to collapse
Hi !
Please don`t bump up the threads , we will answer according to our availability , thank you
Here the thread you need to follow
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Good luck !

[Share][Translated] [LR.Team] 3.3.0 TWRP Redmi 6 Custom Recovery

This is a custom recovery made by LR.Team and I translate the flash tool.
This recovery can automatically decrypt /data partition.
Use the flash tool in the file to flash it.
!!WARN!! Be sure to flash "sign boot" in the advanced menu or you might not be able to boot
(Mount /system,/vendors before flashing magisk or sign boot)
!!WARN!! Flash this recovery on Oreo only.
Link:https://drive.google.com/file/d/1W4bU1m-s8JSkbvCKwt-vauwqqSQjjnzl/view?usp=sharing
Source:https://www.miui.com/thread-19005924-1-1.html
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
**ChangeLogs**
2019.4.30
Magisk updated to v19.0
Twrp updated to 3.3.0
Fix system partition mounting problem
mtp not working.(alternative adb pull/push)

*Reserved*

Thank you. It is necessary to do Mount /system/vendors before flashing magisk or sign boot.
Made without problem

Respected sir
Any custom rom available for redmi 6 device ?
Any working GSI android oreo/pie based
If available rom/gsi Providing link for this
I am waiting for 2 month
Sorry for my bad English

Hey is there any custom ROM for redmi 6?

for anyone has problem flashing magisk but not be able to boot
try this
*install magisk manager first
*boot to recovery and install magisk 18.1
*mount system and vendor
*go sign boot in advaced menu
*reboot and
*enjoy

Hello...
I'm sorry, but it is necessary unlock the bootloader?
I must to wait 360 hours from Xiaomi?

To everyone who have problems with overwriting some system files.. From what i read i think it's something like system-write protection but even if i tried disabling it i still can't modify system at all
---------- Post added at 18:16 ---------- Previous post was at 18:14 ----------
Is that a 19.0 beta magisk in this recovery? I always got bootlooped no matter what with this version. (Only with this one)

working GSI custom rom for redmi 6
---------- Post added at 11:52 PM ---------- Previous post was at 11:48 PM ----------
[/COLOR]
Nitin_ahir said:
Respected sir
Any custom rom available for redmi 6 device ?
Any working GSI android oreo/pie based
If available rom/gsi Providing link for this
I am waiting for 2 month
Sorry for my bad English
Click to expand...
Click to collapse
many gsi, take a look here: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
ps: but if you want also a phone that calls and receives i would go on theese: Aosp9, OctopusOs, Descendant, and Omni.
I think this last one is the best (but not all omnirom worked on my phone, so the best i've used is this:
https://forum.xda-developers.com/pr...abled-device-development/9-0-omnirom-t3901305
With this one you don't even have to edit the /system/build.prop to make calls work as others, this one works as is, and bluetooth worked perfectly in car during calls, the others c roms didn't).
Changed the boot logo... liveboot doesn't work on this rom and sure that boot logo is a detail, but i found a bit embarassing in case of booting with that omni boot logo whithin other people but i think that at the moment is the best alternative if you can't live anymore with that bloatware of miui (because if you still think that privacy is still a right at the moment, place a non rooted firewall the first time you connect and see what tries to pass) so for me at the moment omni is the best choice for this phone.
since i've spent a lot of time seeking not a good rom, but any working custom rom for this damned phone, if it can be helpful to someone and you want to install, this is what i did: - hey, i'm not surely an expert as many guru devs of this site, so proceed at your own risk, and probably some things are not necessary but this is what i did to make it work for me:
1 download omnirom, magisk 17.0 (because magisk 19.0 didn't work or gave me problems with most part of the custom rom i've tryed), MagiskManager-v5.9.1.apk and place all in sd phone card or otg
2 boot in twrp recovery (press power until it vibrates and press (keeping presseded) up vol key for 8 secs or since twrp logo appears)
3 with all the custom roms i've installed since now i couldn't find a way to solve data encryption problem without loosing phone calls, so if the twrp can't decrypt data partition, format data and reboot again in recovery:
wipe/format data/yes (you will loose all your data so if you need to backup somthing do it before) /back and reboot in recovery
3a wipe/ advanced wipe / wipe davilk, cache, data (suppose it's not necesary if you have alrady formatted it), system
4 flash magisk 17.0 (don't install magisk 19 (twrp built-in magisk) because in our case (redmi 6) it doesn't root) and reboot to system
5 now when you boot in to system it will start crypting data, be patient and let it go, there will be an horizontal line going on, when you see it hangs don't worry simply reboot (obviously keeping pressed only power button untill it reboots)
6 maybe it will boot alone several times, don't worry be patient and let it reboot the needed times (i think once i've counted 4 or 5 consequent reboots)
7 when you are finaly in omni, install MagiskManager and open it (it will say that magisk is not installed, don't worry, it is), only reboot system again
8 open Magiskmanager again (now you will find magisk installed)
9 grant permission to the apks you need and if you want to change bootlogo i do it here before backupping. there are a lot of nice ones only search here in xda and replace the new one in /system/media/bootanimation.zip (system must be obviously writable to place it or changing permission, and if it doesn't show correclty new logo at boot check permissions/chmod it to 644 and it must go)
10 before than now i was used to use quite only twrp to make full backups, but now since data is encrypted again it's a problem, so since i don't know how to keep pemanently data not encrypted (i mean keeping a phone that still calls and receives ), i make a system backup with twrp, and a data backup (apks+setting) in the custom rom with titanium.
So after having installed and setted all the apks, i make a titanium backup and copy the titanium_backup_folder in the SD storage.
Then i boot recovery, format data (loosing all setting again), reboot recovery again and make the backup of the modified system.
once i reboot system i restore the setted backupped apks with titanium.
Surely there shall be more simple ways, but this is the only i use at the moment.
i don't have the redmi6 anymore and i think i'll never buy xiaomi again in my life! (think it's better to be the owner of the phone i buy) so i've dropped these memos before forgetting and maybe for someone that was desperate as me - ok, it's late so sorry for my english and if something has been helpful for you give me a thank (if there's a way) , tchau

anyone with root tried this?
https://www.xda-developers.com/xiaomi-redmi-6-redmi-6a-alpha-builds-android-pie/#disqus_thread

Miuipro is available for Redmi 6 only register user
Many people is already downloaded and use it
I request to all those people download this miuipro rom sher with other user
Please sher rom with all users
You can join teligram group for Redmi 6. @redmi6official
Sorry for my bad English

lastly, dont work on Android Pie, need a new kernel after all

I flashed mi redmi 6 with this recovery (from last post) and now it's bricked
the phone wont boot it just vibrate
help

You have BRICKED your phone. You have no way of recovering it without an authorised account or sending it to a Mi service centre. This recovery was for Miui Oreo only, not for pie.
OP should make it CLEAR that TWRP 3.3.0 is ONLY for OREO. DO NOT INSTALL ON PIE. @seanho12345
TWRP 3.3.1 is for PIE ONLY. DO NOT INSTALL ON OREO.
---------- Post added at 08:32 AM ---------- Previous post was at 08:32 AM ----------
You have BRICKED your phone. You have no way of recovering it without an authorised account or sending it to a Mi service centre. This recovery was for Miui Oreo only, not for pie.
OP should make it CLEAR that TWRP 3.3.0 is ONLY for OREO. DO NOT INSTALL ON PIE. @seanho12345
TWRP 3.3.1 is for PIE ONLY. DO NOT INSTALL ON OREO.

What do you mean by this? :
!!WARN!! Be sure to flash "sign boot" in the advanced menu or you might not be able to boot​

It asks for a password please help

Jayoo124 said:
It asks for a password please help
Click to expand...
Click to collapse
just click cancel

ThanX ! ! !
Working great.
Wysłane z mojego Redmi 6 przy użyciu Tapatalka

Hi.
Anyone managed to install on the miui v11.0.2.0 version or miui v11.0.3.0?
Wysłane z mojego Redmi 6 przy użyciu Tapatalka

i just want to report, by following step in thred 1 , i sucessful install twrp. folow th step.
the sign boot is insde twrp.
and
if anyone have error pop up after boot, flash the treble_error_off.zip. i got this from other thread. but cant find which thread anymore.
so i just keep here for future reference
i am on oreo 8.1 when flashing twrp and magisk 18.1

Alpha ROM (AOSP Android 11)

New Android 11 GSI ROM based on Phhusson's AOSP . Really good, stable enough to be used as your daily driver. No major bugs. Preinstalled SuperUser, Android Auto, smart "Keep Notes" etc...
Bored during quarantine? Try this great ROM!
Note: Tested on 9.1.0.132.
Credits: @berkay-gsi
Requirements: basically full stock EMUI 9.1, with stock recovery.
IMPORTANT! Before booting up the ROM, you will need to perform a factory reset in stock recovery!
1. Download system-alpha ROM
ROM
2. Extract the .img file from the compressed file.
3. Flash extracted system.img from fastboot , use command
fastboot flash system (file_name).img
4. Run command 'fastboot reboot', unplug your phone, when on the screen appears yellow warning, press and hold for 3 sec Volume Up . In eRecovery select 'Wipe data/factory reset'. Reboot .
NFC:
- Download NFC Patch
- Install
TWRP
over eRecovery (it makes things easier) - follow this
guide
- In TWRP unmount all except SD Card , Vendor and System (unmount and mount again)
- Flash nfc_universal_patch.zip
- From TWRP menu reboot into recovery and perform factory reset .
Note: you can flash NFC patch before booting up the ROM
How?
Tip: use "Simple Gallery"
download
Enjoy !
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Some banking apps refuse to work on rooted devices, is it possible to use those on that rom?

CrystalCase said:
Some banking apps refuse to work on rooted devices, is it possible to use those on that rom?
Click to expand...
Click to collapse
-Alf- said:
Preinstalled SuperUser,
Click to expand...
Click to collapse

Thanks for the information! I do not want to break anything so I would like to follow a more detailed 'tutorial'. I did search for some, but I am not sure which I can use to install this particular rom. Is there one you can recommend? Like somthing for beginners?

CrystalCase said:
Thanks for the information! I do not want to break anything so I would like to follow a more detailed 'tutorial'. I did search for some, but I am not sure which I can use to install this particular rom. Is there one you can recommend? Like somthing for beginners?
Click to expand...
Click to collapse
No flashing instructions for beginners are offered, sorry. If you're here in this section, you should know what you're doing. More detailed guide can be found here and here .
Read the instructions carefully and completely, check unfamiliar terminology by google or xda.
The instructions do not perform, if you do not know what you're doing.
P.S.: keep in mind, that this ROM is rooted with build-in SuperUser , and you cannot turn off SuperUser!

-Alf- said:
No flashing instructions for beginners are offered, sorry. If you're here in this section, you should know what you're doing. More detailed guide can be found here and here .
Read the instructions carefully and completely, check unfamiliar terminology by google or xda.
The instructions do not perform, if you do not know what you're doing.
P.S.: keep in mind, that this ROM is rooted with build-in SuperUser , and you cannot turn off SuperUser!
Click to expand...
Click to collapse
Okay thanks. I kinda know what I am doing, at least I know what I want. My last time is some years ago on samsung devices so I am not into the new phoes but I will read some and go for it.

Hi Alf! Is always me ahaha.
Anyway I wanted to ask you if it makes sense to switch from LineageOS 18.1 to this one here, or they are the same (especially in terms of stability). I also would like to know if there is a way to avoid loosing the unlocked bootloader when I have to switch to stock firmware. Thank you

Anonymousxx said:
Hi Alf! Is always me ahaha.
Anyway I wanted to ask you if it makes sense to switch from LineageOS 18.1 to this one here, or they are the same (especially in terms of stability). I also would like to know if there is a way to avoid loosing the unlocked bootloader when I have to switch to stock firmware. Thank you
Click to expand...
Click to collapse
Hello, what about your exams stage? O.K.?

-Alf- said:
Hello, what about your exams stage? O.K.?
Click to expand...
Click to collapse
What do you mean? ahahah

Anonymousxx said:
Hi Alf! Is always me ahaha.
Anyway I wanted to ask you if it makes sense to switch from LineageOS 18.1 to this one here, or they are the same (especially in terms of stability). I also would like to know if there is a way to avoid loosing the unlocked bootloader when I have to switch to stock firmware. Thank you
Click to expand...
Click to collapse
Can anyone more polite answer me please? Thank you

-Alf- said:
New Android 11 GSI ROM based on Phhusson's AOSP . Really good, stable enough to be used as your daily driver. No major bugs. Preinstalled SuperUser, Android Auto, smart "Keep Notes" etc...
Bored during quarantine? Try this great ROM!
Note: Tested on 9.1.0.132.
Credits: @berkay-gsi
Requirements: basically full stock EMUI 9.1, with stock recovery.
IMPORTANT! Before booting up the ROM, you will need to perform a factory reset in stock recovery!
1. Download system-alpha ROM
ROM
2. Extract the .img file from the compressed file.
3. Flash extracted system.img from fastboot , use command
fastboot flash system (file_name).img
4. Run command 'fastboot reboot', unplug your phone, when on the screen appears yellow warning, press and hold for 3 sec Volume Up . In eRecovery select 'Wipe data/factory reset'. Reboot .
NFC:
- Download NFC Patch
- Install
TWRP
over eRecovery (it makes things easier) - follow this
guide
- In TWRP unmount all except SD Card , Vendor and System (unmount and mount again)
- Flash nfc_universal_patch.zip
- From TWRP menu reboot into recovery and perform factory reset .
Note: you can flash NFC patch before booting up the ROM
How?
Tip: use "Simple Gallery"
download
Enjoy !
View attachment 5214123View attachment 5214125View attachment 5214127View attachment 5214129View attachment 5214131View attachment 5214133View attachment 5214137View attachment 5214139
Click to expand...
Click to collapse
any new updates and changes for this rom out yet?

lucsol said:
any new updates and changes for this rom out yet?
Click to expand...
Click to collapse
I don't know bro, but try looking here:
berkai-gsi

Boot Loop / Checksum Error when trying to root (Umidigi A7 Pro).

Spoiler: Phone Data:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi Guys,
I'm super new to the whole topic and am only doing this because I have a spare smartphone and wanted to learn something.
The bootloader is unlocked.
The USB drivers are installed on the PC.
USB Debugging is turned on.
Smartphone states "Orange State [...]" while booting.
Then I tried to extract the boot.img via the "MTK Droid Root & Tools v2.5.3" to flash this later with Magisk. But here I got the following error message:
Spoiler: MTK Error
The same messages have been there before I did anything on the smartphone for the first time.
From DE to ENG:
--->>> Connect to device <<<---
--- ERROR: --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!--- unknown ROM structure, backup NOT possible!ATTENTION! a file (/system/recovery-from-boot.p) which restores the stock recovery in case of normal phone startup was found!
So I flashed a stock rom here from
Spoiler: link
Umidigi A7 Pro Stock Firmware ROM (Flash File)
Download Official Umidigi A7 Pro Firmware (original flash file) without any password for Free. We also provide the Stock Rom for other Umidigi devices.
xdafirmware.com
to the phone via the SP Flash Tool (because I did something that enabled the first Boot Loop), the phone restarts in factory state succesfully, I set it up once and then installed Magisk, and using Magisk patched the boot.img of the from I downloaded.
However, when I now want to flash it via the flash tool, this error message appears:
Spoiler: Flash Tool Error
And suddenly I am in boot loop. As soon as I flash the original boot.img, the phone starts as usual.
I have also tried the whole thing via TWRP, and as soon as I install Magisk.zip via the TWRP the boot loop angers me again. Also MTK still shows the same error.
Spoiler: I have followed the following instructions:
Main Guide: https://www.getdroidtips.com/root-umidigi-a7-pro/
Helping Video:
Spoiler: Magisk log
I'm happy about anything that helps me out getting this phone rooted

Sorry my friend that noone has yet to have replied to your inquiry here. Ill do my best to give you some of the knowledge I have when it comes to setting you in the right direction without failure next time. Today and for the last month or so I have been working hard with the Umidigi a7 pro 64gb. To be clear are you making sure to flash the magisk zip file of the boot.img file that you saved from the stock firmware. You shouldn't have to fiddle around with to many of the settings just when you do flash the patched file you have to make sure to uncheck everything other then boot.img patched file. I am very new to this as well and honestly it's a tricky process to get it ever done right on your first attempt. You seem to have and know enough knowledge on this topic. MTK is a finnacky processor. I myself have yet to get this device fully rooted yet. The issue I myself have is my PC is not properly updating the MTK and other drivers to make the magic happen which I think I am just going to have to get my other dell going again to try on a fresh PC that I just set up again for this exact thing. To my most recent knowledge though when it comes to the Umidigi a7 pro you have to follow each and every step closely and to a exact precise t or the whole operation will fail every time you try. Are you using your micro SD card to it's full potential and making sure that you saved the patched file properly. You also have to watch for corrupt files when it comes to this kind of thing. But you know enough to just trust the pages you are downloading your files from and make sure everything is signed and legit. Another thing is what seemed to help me is removing SP flash tool completely from my PC. Then re downloading it and starting from scratch by flashing your stock scatter file and I find when flashing hold the power button when it starts for just a few seconds only some people think to keep holding the power button through the entire flash process but to my knowledge what has worked from a noobs perspective is hold power for just a few seconds until the full load of the red bar comes and then when it goes away you can let go of power button and it will continue on with the rest of the manual installment process. There are a lot of high technical highs and lowes when it comes to what you can do here and from the info I've gotten MTK devices weren't really meant to be able to withstand even being remotely compatible devices for root. Honestly let me know how things are going lately for you as I know this post is a bit old. I myself have came close to periodically throwing this phone as far out of the window as it can reach, I'm not a quitter by any means and still today and even right now m working on that to try to help others in any way i possibly can and today I will get this device into full root accesss.