[HELP] Root Acer Liquid Zest plus z628 t08 !!! - Android Q&A, Help & Troubleshooting

Hi everyone,
I have an Acer Liquid Zest Plus t08 - z628
Here is other info of a device:
Android version: Marshmallow 6.0
Kernel version: 3.18.19+
Build number: Acer_AV0M0_t08_RV01RC03_EMEA_BHT (last three digits "BHT" is probably BH Telecom my carrier in Bosnia)
Chipset: mt6735
==========================================
I want to root this device. I've tried all possible methods i could find on the web. (Kingroot, Kingoroot, Framaroot, MobileGo!, TunesGo!, Root Genius, Baidu root), pretty much all possible "one-click-root" tools available, all methods failed to root my device.
One of the possible solutions is tu flash custom recovery, and flash SuperSu, but the problem is, i couldn't find a twrp or cwm for this device. I searched all the web but I couldn't find it.
Also i tried to make my own cwm using MTK Android tools, but I don't have boot.img file. I can't find boot.img anywhere on the web.
Im desperetly need help because i tried almost everything i know.
If anyone have Stock rom of this device, or boot.img of this device or anything that can help me root this device, please help!
Thanks in forward, and sorry for bad english.

Update:
I've tried apsolutely every possible thing available and failed.
Does anyone have scatter file of this device model?
That file would help me to create a boot image and then to port cwm for my device.
I tried MTK Droid tools to create scatter file but failed. When I click on "blocks map" button it gives me an empty table.
So what I need is:
- scatter file for acer z628 t08
or
- boot.img
or
- recovery.img (cwm or twrp)
or link to original stock rom for this device model.
Any help would be appreciated!

Same problem
I would like to tell you that I found a way, but i didn't. I actually have the same problem, on the exact same phone. My knowledge in phone rooting isn't great so I won't be able to help, but i would be very happy if you could inform me if you find a way.

Hello,
Ask this man. Hi did it for (t7) version. May be he will help you to port twrp.
https://forum.xda-developers.com/an...st-4g-z628-t3534746/post70540747#post70540747
You are not alone!

no your not alone, bluetooth won't work properly on min, alway's disconnect

Upvote
mirzakv said:
Im desperetly need help because i tried almost everything i know.
Click to expand...
Click to collapse
Same problem here

Hi All,
Like Mirzakv i also tried everything, but in addition "One Click Root " tool lead me to the answer this software tool is suitable and claimed it has the power for rooting the Acer Liquid Zest Plus T08 . But unfortunately the "One Click Root " tool stucked the rooting process unless you pay or transfer 35 USD for going on.

Here is the scatter taken from OS_Acer_Acer.AV0M0.T08.1.015.00.WW.GEN1S_A60M_A.zip which can be downloaded from acer's site.
I don't know what is the difference between GEN1 (my case) and GEN1S versions, but I hope that memory maps are the same.
preloader 0x0
pgpt 0x0
proinfo 0x80000
nvram 0x380000
protect1 0x880000
protect2 0x1280000
lk 0x1c80000
para 0x1d00000
boot 0x1d80000
recovery 0x2d80000
logo 0x3d80000
expdb 0x4580000
seccfg 0x4f80000
oemkeystore 0x5000000
secro 0x5200000
keystore 0x5800000
tee1 0x6000000
tee2 0x6500000
frp 0x6a00000
nvdata 0x6b00000
metadata 0x8b00000
system 0xb000000
cache 0xbe800000
userdata 0xd7800000
flashinfo 0xFFFF0084
sgpt 0xFFFF0004

MTK droid version
mirzakv said:
Hi everyone,
I have an Acer Liquid Zest Plus t08 - z628
Here is other info of a device:
Android version: Marshmallow 6.0
Kernel version: 3.18.19+
Build number: Acer_AV0M0_t08_RV01RC03_EMEA_BHT (last three digits "BHT" is probably BH Telecom my carrier in Bosnia)
Chipset: mt6735
==========================================
I want to root this device. I've tried all possible methods i could find on the web. (Kingroot, Kingoroot, Framaroot, MobileGo!, TunesGo!, Root Genius, Baidu root), pretty much all possible "one-click-root" tools available, all methods failed to root my device.
One of the possible solutions is tu flash custom recovery, and flash SuperSu, but the problem is, i couldn't find a twrp or cwm for this device. I searched all the web but I couldn't find it.
Also i tried to make my own cwm using MTK Android tools, but I don't have boot.img file. I can't find boot.img anywhere on the web.
Im desperetly need help because i tried almost everything i know.
If anyone have Stock rom of this device, or boot.img of this device or anything that can help me root this device, please help!
Thanks in forward, and sorry for bad english.
Click to expand...
Click to collapse
Hi Mirzakv,
Which version of MTK Droid root and tools did you used ? Version 2.5.3 ?
we have MT 6735 chip, maybe we are not in this sequence, (MT6572-MT6592), and have to wait for an MTK Droid tool update for rooting the device.
On the Acer website, Netherlands, i see O.S i think this is the stockrom or firmware and this is maybe not the scatter file, but i am not sure.
Maybe Romavnts can help us out, i am not a programmer or electronic engineer, but user only of this smartphone who like to tweak and tink.
Still waiting and hoping for more advice,
regards

Is there still no way to root this device?
The acer website now shows 2 os images:
1. WW_GEN1S
2. TWN_GEN1
Does that help us?
Lol idk much about rooting but it'll be cool to able root my phone XD
(kinda weird cause the image i have is Acer_AV0M0_T08_RV01RC12_PA_GEN1)

Working TWRP recoverimage for ACER T08
Hi Guys
I was also looking for a way to Root the Acer Liquid Zest Plus (T08). My Acer is the Acer_AV0M0_T08_1.018.00_WW_GEN1. I searched the whole Internet and found nothing. So i took the TWRP 3.0.2.1 and ported it for the ACER T08.
Now a little manual to install. First Backup all your Contacts and all the Stuff you wanna keep. Then put the SuperSU-v2.82 on the Phone / SD card in Phone.
First install ADB/Fastboot on your Computer.
Then start a CMD (press Start-button and search for cmd and start cmd.exe) then change to the directory where you have installed ADB/Fastboot.
Next step, put the TWRP_ACER_T08.img into the ADB/Fastboot folder.
Then you have to turn on USB-debugging @ Developer options on your phone. Also unlock Booloader.
Now back to the CMD-window and enter:
adb reboot bootloader - (it will restart your phone and after a few second u see on Display a down left corner Fastboot mode)
Then write at the CMD-window
fastboot getvar all - (look if Bootloader is unlocked. If not write: "fastboot oem unlock" but remember that this will do also a Factory reset on your Phone. )
If your Bootloader ist unlocked write at CMD-window
fastboot boot TWRP_ACER_T08.img -(This will only Boot into TWRP-recovery not Flash it to your Phone. So you can keep the original Acer recovery)
After a few seconds the TWRP recovery starts and u can install the SuperSU-v2.82. After installing wipe cache/dalvik and reboot your phone.
Now your Acer T08 will be rooted.
Everything u need to Root your Phone you can find here:
"https://drive.google.com/open?id=0Bz_0lBBekCI_b3BfM2lDcERCbE0"
Remember: I am not responsible for any damages on your Phone!!!

lucky666666 said:
Hi Guys
I was also looking for a way to Root the Acer Liquid Zest Plus (T08). My Acer is the Acer_AV0M0_T08_1.018.00_WW_GEN1. I searched the whole Internet and found nothing. So i took the TWRP 3.0.2.1 and ported it for the ACER T08.
Now a little manual to install. First Backup all your Contacts and all the Stuff you wanna keep. Then put the SuperSU-v2.82 on the Phone / SD card in Phone.
First install ADB/Fastboot on your Computer.
Then start a CMD (press Start-button and search for cmd and start cmd.exe) then change to the directory where you have installed ADB/Fastboot.
Next step, put the TWRP_ACER_T08.img into the ADB/Fastboot folder.
Then you have to turn on USB-debugging @ Developer options on your phone. Also unlock Booloader.
Now back to the CMD-window and enter:
adb reboot bootloader - (it will restart your phone and after a few second u see on Display a down left corner Fastboot mode)
Then write at the CMD-window
fastboot getvar all - (look if Bootloader is unlocked. If not write: "fastboot oem unlock" but remember that this will do also a Factory reset on your Phone. )
If your Bootloader ist unlocked write at CMD-window
fastboot boot TWRP_ACER_T08.img -(This will only Boot into TWRP-recovery not Flash it to your Phone. So you can keep the original Acer recovery)
After a few seconds the TWRP recovery starts and u can install the SuperSU-v2.82. After installing wipe cache/dalvik and reboot your phone.
Now your Acer T08 will be rooted.
If you want to flash the TWRP recovery to your Phone write at CMD-window
fastboot flash TWRP_ACER_T08.img
Everything u need to Root your Phone you can find here:
"https://drive.google.com/open?id=0Bz_0lBBekCI_b3BfM2lDcERCbE0"
Remember: I am not responsible for any damages on your Phone!!!
Click to expand...
Click to collapse
After such a long time my t08 is FINALLY rooted!
I did all the steps, and everything worked 100% as you said. I still can't beleive!
Thanky you million times!
P.S. i can't flash ported twrp there is somekind of error when i type "fastboot flash TWRP_ACER_T08.img"
but I can boot into the ported twrp and boot works fine!
Thanks one more time!
P.S. 2:
I didn't do wipe data and cache after flashing SuperSu, I just rebooted the phone and everything went just perfectly fine. My phone is intact, and rooted =

mirzakv said:
After such a long time my t08 is FINALLY rooted!
I did all the steps, and everything worked 100% as you said. I still can't beleive!
Thanky you million times!
P.S. i can't flash ported twrp there is somekind of error when i type "fastboot flash TWRP_ACER_T08.img"
but I can boot into the ported twrp and boot works fine!
Thanks one more time!
P.S. 2:
I didn't do wipe data and cache after flashing SuperSu, I just rebooted the phone and everything went just perfectly fine. My phone is intact, and rooted =
Click to expand...
Click to collapse
Sorry that a error happen while trying to flash the recovery, but i haven´t tried to flash it on my phone cause i wanted to keep the original recovery. But i´m happy to hear that it finally worked for you with the Bootway.

Just followed your instructions, worked perfectly. Thanks a lot!

Thanks a lot! You are great!
But I had a problem with Windows10. After adb reboot bootloader command phone restarted to Fastboot mode. And there was no connection.
On Ubuntu16 everything was fine.

I need help...
Guys please, I need some help... my phone is stuck in the select boot mode thing, it isn't responding. I don't want to lose my phone, please help me...
Edit: It's ok, but for now, my problem is that i don't know how and where to put the twrp image...
Edit 2: Finally worked it out... You need to write fastboot boot WhereYouPutYourTwrpImage Ex: fastboot boot C:\adb\TWRP_ACER_T08.img
That was for the not that much tech people like me...

i cant find the of twrp
how to port twrp on acer plss send tutorial

luciapao211 said:
how to port twrp on acer plss send tutorial
Click to expand...
Click to collapse
I ported the TWRP with this instruction.
"***.chinaphonearena.com/forum/Thread-Tutorial-HOW-TO-PORT-TWRP-MT6735-MT6752-MT6753-MT6795-MT6797-TWRP-MT67xx-tutorial"

Thank you for your hard work

not recognized
Hi there. My liquid zest plus doesnt show up in adb devices or fastboot devices. Also I apparently have no os and no system files. I have twrp installed but cant install any of the roms for the t08 because apparently my internal storage and system cant be mounted. Any suggestions please? Im desperate.
Thanks

Related

[Q] [Brick] ZTE Open, need low level flash (TPT?) instructions

Hi folks,
unfortunately I somehow bricked my ZTE Open. I flashed cwm (worked fine) but after flashing both system AND userdata via flash_image, the phone won't boot and what is much worse it won't boot into cwm anymore as it hangs there with just showing the logo and the cwm version. The menus are missing, it does not react buttons and does not show up in adb. FTM mode is also non-functional, holding volup gets you also into broken recovery.
For earlier ZTE devices like the ZTE Blade it seems to be possible to low level flash them in diagnostics mode. Diagnostics mode is working fine on the ZTE Open (it shows up with the diagnostics port on USB. Luckily I also have all the 20 partitions backed up, but I don't know how to flash them in this diagnostics mode. I tried putting the files into the root of the SD card and including sha1/256/512 plus md5sum files, but it was not impressed by that. Not sure if this only works in FTM mode, though.
Any help would be highly appreciated! I highly assume that the procedure is the same as for the ZTE Blade.
This may help. http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/
At least there is more going on for Firefox Open over there.
Thanks but as you might have noticed I posted several comments there already, but I thought XDA would be the right place for unbricking devices.
Defier525 said:
Thanks but as you might have noticed I posted several comments there already, but I thought XDA would be the right place for unbricking devices.
Click to expand...
Click to collapse
Sorry! Eyes tight shut!
Are there any updates on this one?
I have bricked Open too, I'm attaching the PCB picture, if it is any help to maybe find UART or JTAG pins?
Can someone be really nice and please dump the bootloader from working ZTE Open in send it to me?
I've found some guy, who maybe can help me write bootloder with JTAG.
I think this should work, but no promises: https://sites.google.com/site/zteopenfirmware/download-mode
psywolf said:
I think this should work, but no promises: https://sites.google.com/site/zteopenfirmware/download-mode
Click to expand...
Click to collapse
Thanks for your time to help, but this does not work for me. I get an error, when I press flash button (printscreen under attachments).
I've tried to probe the pins with the multi-meter and found GND and V+ (picture under attachment)
Now it would be nice to have something like this -> http://www.grandideastudio.com/portfolio/jtagulator/
Defier525 said:
Hi folks,
unfortunately I somehow bricked my ZTE Open. I flashed cwm (worked fine) but after flashing both system AND userdata via flash_image, the phone won't boot and what is much worse it won't boot into cwm anymore as it hangs there with just showing the logo and the cwm version. The menus are missing, it does not react buttons and does not show up in adb. FTM mode is also non-functional, holding volup gets you also into broken recovery.
For earlier ZTE devices like the ZTE Blade it seems to be possible to low level flash them in diagnostics mode. Diagnostics mode is working fine on the ZTE Open (it shows up with the diagnostics port on USB. Luckily I also have all the 20 partitions backed up, but I don't know how to flash them in this diagnostics mode. I tried putting the files into the root of the SD card and including sha1/256/512 plus md5sum files, but it was not impressed by that. Not sure if this only works in FTM mode, though.
Any help would be highly appreciated! I highly assume that the procedure is the same as for the ZTE Blade.
Click to expand...
Click to collapse
tpt files for the zte open
https://www.dropbox.com/sh/rnj3rja7gd54s98/_twgXEkMFH/P752D04_DEV_EU_20131212_v1.2.7z
Thank you for the link. But what tool is supposed to be used to flash the files? And is there a way I can use my backup as well? In this case: how can I transform it to TPT files?
Update: I tried flashing it by following the instructions of the link posted by psywolf, but unfortunately I am getting the same error as aversario. I tried also flashing just recovery, but it seems like no single partition is flashed successfully.
So, I've ordered jtagulator and it showed the pins. Now I need jtag programmer, which one do you guys recommend?
And I am still looking for some great guy to share with me his bootloader of a functional zte open.
aversario said:
So, I've ordered jtagulator and it showed the pins. Now I need jtag programmer, which one do you guys recommend?
And I am still looking for some great guy to share with me his bootloader of a functional zte open.
Click to expand...
Click to collapse
on what partition is the bootloader? i have a UK revision 02 one, i would help you out if you tell me how to get the bootloader?
linr76 said:
on what partition is the bootloader? i have a UK revision 02 one, i would help you out if you tell me how to get the bootloader?
Click to expand...
Click to collapse
Well, I don't know the partition names by heart, but as I remember the bootloader is one of the small partitions (so definitely not system or boot or userdata or recovery).
The way to get that small partitions would be installing CWM recovery first -> http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/
then enter adb shell on computer
su # to get root privileges
then it should be something like explained here -> https://www.youtube.com/watch?v=j3GOzUURSgM&feature=player_detailpage#t=153
And thank you very much for your time
If i figure out how to do that without CWM i'll upload it for you. Cannot install CWM because i need to be on stock recovery for development of update packages, sorry
Sent from my V3 using Tapatalk
linr76 said:
If i figure out how to do that without CWM i'll upload it for you. Cannot install CWM because i need to be on stock recovery for development of update packages, sorry
Click to expand...
Click to collapse
OK, I get that. I'm sure there exists a way to do it without changing recovery also. I just can't figure it out because that's the only Firefox OS phone I've had.
try to reinstall
Hi, I bricked my ZTE Open (EU version) too. Had bought it from a German Ebay seller and tried to flash FirefoxOS 2.0 on my device. I don't have the CWM recovery installed, only the "Firefox OS System Recovery" Big mistake, I know . When I switch on the device, the Firefox OS logo appears, then disappeas after a few seconds, and so on, the perfect bootloop
I can't access the device via ADB or fastboot.
When I ty to install any downloaded zip (even from ZTE's homepage) from the SD card, I get following messages:
Code:
--Install /sdcard ...
Finding update package ...
Opening update package ...
Verifying update package ...
E: signature verification failed
Installation aborted.
So there is no valid signature.
Can you help me please? Thank you!
Heinz
Found a solution by myself!:victory:
I downloaded the update.zip file from firefox.ztems.com (Update package of Android GB for OPEN device) and installed it.
After that I could flash the CWM recovery. It seems to work...

[Q] Alps S5 octacore, ROM readback and root

Hi, I just bought this phone from TECA Mobility, it turns out to be an Alps S5. See attachement for a detailed description.
I tried to ge the root. I tried some different tools, without success.
MTK Droid Tools ROOT button doesn't work but gives a link to xda's MKT forum, so I started with the recommended procedure. I tried to read back the ROM with SP-FlashTools but no way, it doesn't start. I also made some attempts with the Android SDK but adb backup of course doesn't work for the System partition without root.
When I send the adb reboot recovery command the phone goes in download mode, with the adb reboot bootloader command it goes in fastboot mode, while to have it in the factory recovery mode I have to manually hold down the start and vol down buttons. However, it doesn't matter, the readback does not start.
Should I try to install the CWD recovery without having a backup of the ROM? I think it's too risky. I looked at NEEDROM to see if I can find my ROM, but didn't find. I found these, "S5 SM-G900 MT6592", but I cannot be sure it's the right one.
Somebody can help me? I want to root the device.
gt56 said:
Hi, I just bought this phone from TECA Mobility, it turns out to be an Alps S5. See attachement for a detailed description.
I tried to ge the root. I tried some different tools, without success.
MTK Droid Tools ROOT button doesn't work but gives a link to xda's MKT forum, so I started with the recommended procedure. I tried to read back the ROM with SP-FlashTools but no way, it doesn't start. I also made some attempts with the Android SDK but adb backup of course doesn't work for the System partition without root.
When I send the adb reboot recovery command the phone goes in download mode, with the adb reboot bootloader command it goes in fastboot mode, while to have it in the factory recovery mode I have to manually hold down the start and vol down buttons. However, it doesn't matter, the readback does not start.
Should I try to install the CWD recovery without having a backup of the ROM? I think it's too risky. I looked at NEEDROM to see if I can find my ROM, but didn't find. I found these, "S5 SM-G900 MT6592", but I cannot be sure it's the right one.
Somebody can help me? I want to root the device.
Click to expand...
Click to collapse
Hi
1) First root your device using MTK Chopper (from PC) or framaroot (from android app) . Both work fine for MTK phones
2) Then using MTK droid tools backup your ROM. Here is the guide for that
http://forum.xda-developers.com/showthread.php?t=2730031
3)Then using MTK droid tools , make CWM recovery for your phone and install it . Here is guide for that
http://forum.xda-developers.com/showpost.php?p=44660171&postcount=417
Hit THANKS if it works
4shreyas said:
Hi
1) First root your device using MTK Chopper (from PC) or framaroot (from android app) . Both work fine for MTK phones
2) Then using MTK droid tools backup your ROM. Here is the guide for that
http://forum.xda-developers.com/showthread.php?t=2730031
3)Then using MTK droid tools , make CWM recovery for your phone and install it . Here is guide for that
http://forum.xda-developers.com/showpost.php?p=44660171&postcount=417
Hit THANKS if it works
Click to expand...
Click to collapse
I think you mean MOTO Chopper? It doesn't work, same as framaroot. They are old tools, they don't work anymore on the ROMs released after June 2014.
ODIN could work but I have not the sure/right file to download.
Generally speaking, the first thing to do is that of getting a backup of the ROM from the un-rooted phone
The guides that have been reported to work in these cases are:
From XDA:
http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
From China Devices:
http://www.china-devices.com/Thread-ROOT-CWM-Readback-your-ROM-with-SP-Flash-Tools#
Hereunder is the link to a success case story:
http://www.china-devices.com/Thread-Rooting-new-octacore-S5
There is no way I know to get the root with one-click-tools, there is no case I could find of anybody being able to root these phones by following other procedures.
If anybody knows better, please send me a link (MTK phones with ROM s released after june 2014 only!!!)
My only problem now is that I cannot get the read back with Flash Tools. I have tried uncountable button-pressing combinations, I have put the phone in recovery, download, fastboot mode, I have tried with and without battery, phone switched off or on - no error, but the read-back doesn't start (however my phone doesn't have the USB connection working when it's off or without battery).
The only way to skip this step is, if I had already a copy of the firmware available, a sure one.
Kindly help me if you can
Hi
Odin doesn't work for MTK mate
Try this latest app . It worked for some latest MTK KK phones
http://www.kingoapp.com/index.htm
Some other KK phones got rooted using vroot and rootgenius
Try your luck
Final option is to read back from SPFT which has 90+ success rate
Link to your stock firmaware: ( Official ROM Kingelon G9000 Version: 20140710_e2706v92_jbla_fhd -> This model number matches with model no in your image)
http://www.needrom.com/download/alps-star-kingelon-g9000-style-s5-touchwiz/
As bizarre as this sounds, I managed to get root on a similar phone (another MTK6592 S5 knockoff) with MTK tools. After exhausting my options, I clicked the ADB button and tried to get root shell regardless (via 'adb root shell', which probably isn't the proper command but it works regardless), which caused some sort of hang. After a minute or so I unplugged my phone, which caused things to start responding again; plugging it back in showed me as having temporary root, and the get root button actually worked the next time I tried it. I have no idea how or why it worked, or if it was a once in a lifetime occurrence, but it can't hurt to try.
Also, if your phone is anything like mine (and is actually running some form of KitKat), good luck getting write support for external SD cards. I couldn't get the system partition to mount (to write changes to the necessary file) via anything but ADB shell.
Problem solved
Good to know, thank ypu.
However in the meantime I solved my problem.
My phone works this way: I have to remove the battery and connect it to the USB cable. Then it goes in "preloader mode" and tries to install a driver called "MT65XX preloader driver". This driver actually emulates a COM port. If data transfer doesn't start, then, after a few seconds, the device goes down and disappear from Windows list. So it is easy to miss it when we install all drivers. I had to dowload it (from Google cloud service in my case), install and ... the Read Back started !!! Now I have completed the procedure and my phone is rooted with the CWD recovery installed.
ALPS S5 phone, real FLASHROM total size, 64GB ext SDcard not working
FEGuy said:
As bizarre as this sounds, I managed to get root on a similar phone (another MTK6592 S5 knockoff) with MTK tools. After exhausting my options, I clicked the ADB button and tried to get root shell regardless (via 'adb root shell', which probably isn't the proper command but it works regardless), which caused some sort of hang. After a minute or so I unplugged my phone, which caused things to start responding again; plugging it back in showed me as having temporary root, and the get root button actually worked the next time I tried it. I have no idea how or why it worked, or if it was a once in a lifetime occurrence, but it can't hurt to try.
Also, if your phone is anything like mine (and is actually running some form of KitKat), good luck getting write support for external SD cards. I couldn't get the system partition to mount (to write changes to the necessary file) via anything but ADB shell.
Click to expand...
Click to collapse
Maybe your phone was using firmware dated before june 2014? These was a bug that was exploited by Framaroot, but now they fixed it.
Is your phone also from ALPS? They sold it to me as capable of installing an external 64GB SDHC card, but I cannot have it working. Did you face any similar issue?
Otherwise 32GB cards work fine. Have you tried Aparted app? I use it for formatting/maintenace. This app makes partitioning, I guess it should work.
Also, if your phone is from ALPS, does it really have the ROM memory that is advertised?
I am facing some interesting issues with my phone on this respect. It was sold as having 16GB internal ROM, of which about 12GB avalible for users. In fact, the settings menu shows 10GB ,( 8GB available) of internal memory, and about 4GB of phone memory. Well, if I am correct, this so called internal memory maps to the directory /data (the one highest level in the root), who corresponds to partirtion mmcblk0p7. This partition actually has a size of 2.3GB instead of 10 !!!. f I install and try to run online Nandroid backup, I cannot have it working on paths directed towards the SDcards, but it works on the path data/media. Well, a backup of about 1.2GB is shown in the setting menu of the phone as a memory consumption of about 5 GB !!!
Then I had also hard time in copying this file from the /data directory to one of the SD cards. Root Browser and Root Explorer didn't work, only ES Manager with root rights worked.
Maybe you can give me some advice in finding some tool or SDK procedure to assess what the real total size of the memory is? Or some suggestion on how to fix the ext 64GB card? I got bad feelings with the guys who sold this phone to me, so I would like to collect some more evidence if possible.
I downloaded some applications for making device inspection. They read the manufacturers' data, so they get cheated - even if, in some cases, they can show the right amount of unused memory still available (quite lower than declared by the phone) . Also I cannot see the real size of the RAM memory used by the CPU .
Need stock ROM for Teca g89 mobile.
Hi experts,
I need stock ROM of TECA G89W ANDROID 4.4 2.4GHz 4GB-RAM +32GB 18MP 5.5-inch GPS SMARTPHONE. I brought this phone 6 months back and unfortunately the software corrupted. I tried with other ROMs and currently bricked my phone. If anyone who might have this phone by fortunate can help me to post the stock rom by read back or any process whatever you wish as you know much than me.
Desperately need the ROM file as I want to have my phone back to working.... Thank you....
need that rom
hello. can you ... or someone else, upload that rom again?
the link is no longer online at needrom, and that was the best rom for my kingelon g9000.
i had made a flash to try another rom, but is wasn't better. when i wanted to download again that ALPS rom it was no longer online!
gt56 said:
Hi, I just bought this phone from TECA Mobility, it turns out to be an Alps S5. See attachement for a detailed description.
I tried to ge the root. I tried some different tools, without success.
MTK Droid Tools ROOT button doesn't work but gives a link to xda's MKT forum, so I started with the recommended procedure. I tried to read back the ROM with SP-FlashTools but no way, it doesn't start. I also made some attempts with the Android SDK but adb backup of course doesn't work for the System partition without root.
When I send the adb reboot recovery command the phone goes in download mode, with the adb reboot bootloader command it goes in fastboot mode, while to have it in the factory recovery mode I have to manually hold down the start and vol down buttons. However, it doesn't matter, the readback does not start.
Should I try to install the CWD recovery without having a backup of the ROM? I think it's too risky. I looked at NEEDROM to see if I can find my ROM, but didn't find. I found these, "S5 SM-G900 MT6592", but I cannot be sure it's the right one.
Somebody can help me? I want to root the device.
Click to expand...
Click to collapse
Hi see if the link helps you to find the mach of your phone model file:///data/data/com.android.browser/files/kingelon_g9000.mht
---------- Post added at 04:58 PM ---------- Previous post was at 04:53 PM ----------
gt56 said:
Hi, I just bought this phone from TECA Mobility, it turns out to be an Alps S5. See attachement for a detailed description.
I tried to ge the root. I tried some different tools, without success.
MTK Droid Tools ROOT button doesn't work but gives a link to xda's MKT forum, so I started with the recommended procedure. I tried to read back the ROM with SP-FlashTools but no way, it doesn't start. I also made some attempts with the Android SDK but adb backup of course doesn't work for the System partition without root.
When I send the adb reboot recovery command the phone goes in download mode, with the adb reboot bootloader command it goes in fastboot mode, while to have it in the factory recovery mode I have to manually hold down the start and vol down buttons. However, it doesn't matter, the readback does not start.
Should I try to install the CWD recovery without having a backup of the ROM? I think it's too risky. I looked at NEEDROM to see if I can find my ROM, but didn't find. I found these, "S5 SM-G900 MT6592", but I cannot be sure it's the right one.
Somebody can help me? I want to root the device.
Click to expand...
Click to collapse
Hi see if the link helps you to find the mach of your phone model file:///data/data/com.android.browser/files/kingelon_g9000.mht , you can root it using v root you will need a pc to root your phone.

HELP TO UNBRICK CAT S30 (Snapdragon 210 MSM8909) AFTER OTA

Hi guys, i really hope you can help me, i m so deseperate...
After OTA Update my CATERPILLAR S30 bricked into bootloop, i can access to the stock recovery (wipe data/factory not fix it) and bootloader show me ; "DC CHECK"
I read that it could be my bootloader (emmc) wich it's corrupted...
The chipset is a Qualcomm Snapdragon MSM8909, of course USB debugging is disabled and i can't find any stock rom, backup for this phone....
Please HELP ME...i work hight in the mountain and if i cant communicate it will become....quite dangerous for me...
If someone has a backup (EU AREA), a stock rom or any solution for me ill be gratefull
Bye
Nobody can upload me OTA file (wich i ll .zip), boot.img, backup or any kind of solution please...?
AnY-One said:
Nobody can upload me OTA file (wich i ll .zip), boot.img, backup or any kind of solution please...?
Click to expand...
Click to collapse
What software version are you on?
Chuggers said:
What software version are you on?
Click to expand...
Click to collapse
Hello there and thanks helping me...
I'm AnY-One but i can't log in with; i dont know why...
I dont know what is my software version i only can say to you that the last update i tried to install came about 10-12/01 (EU France) and i bought this phone the 24/12 and i already did a first update.
So my phone stuck in bootloop (Qualcomm HS-USB QDLoader 9008 recognized) when i tried to install the 2nd update 10-12/01 so...
I have all qualcomm developpers tools with qualcomm flash utility and i can access to stock recovery...perhaps just a boot.img should work...
Pleassse help guys...
"and...as you can read; SORRY FOR MY ENGLISH"
---------- Post added at 05:32 PM ---------- Previous post was at 04:52 PM ----------
an update.zip that i can flash from recovery should be welcome
---------- Post added at 06:19 PM ---------- Previous post was at 05:32 PM ----------
Got it, i think software version (viewing in recovery mode) is LTE_D0201121.0_S30_0.017.01
Zi0nlive said:
-snip-
Click to expand...
Click to collapse
Is warranty not an option?
nagalun said:
Is warranty not an option?
Click to expand...
Click to collapse
it is but it takes time...and i like to fix my mistakes by my self...
Have you a solution for me? can you upload the OTA files or a backup rom .zip?
Zi0nlive said:
it is but it takes time...and i like to fix my mistakes by my self...
Have you a solution for me? can you upload the OTA files or a backup rom .zip?
Click to expand...
Click to collapse
You can access recovery?
Usually when you see "Qualcomm HS-USB QDLoader 9008" it is because the phone can't load the bootloader (bios), so I am a bit confused about the state of your phone.
You likely need more files than the OTA has.
nagalun said:
You can access recovery?
Usually when you see "Qualcomm HS-USB QDLoader 9008" it is because the phone can't load the bootloader (bios), so I am a bit confused about the state of your phone.
You likely need more files than the OTA has.
Click to expand...
Click to collapse
That's a good question ; yes i can access to QDloader HS-USB 9008 with qualcomm drivers ; I CAN ONLY acces to
recovery holding VOL+ then plugin in USB. Phone off then : POWER + VOL+ doesnt boot recovery.
Wipe Data/factory seems to work, adb sideload; device is regognized in adb shell but most of commands answer are: "FAILED (remote: unknown command)" when i choose reboot in bootloader it's the boot screen with 'DC CHECK MODE' left corner..
Is there someone reading me who has the same phone?
Is there someone able to upload me .img (system, boot ...) that i can flash with QPST Tools? Stock Firmware? Nandroid Backup?
Is there someone who can guide me to repair that phone stuck in bootscreen? I think the problem come from my stupidity fogetting to unroot (Kingoroot apk replaced by SuperSU) before OTA update.
How extract my proper firmware
Hello
How extract the om from the device
Help Me
Same problem...
I have the same problem too... Please help
sharing my experience in a similar quest
Hello ! You probably must have resolved the issue by now. Like you, I too had a similar issue ( Reliance Jio Lyf Wind4 - Haier L51)
In my nooby quest for a solution have made some progress. The learning is:
One needs : Mprg8909.hex, 8909_msimage.mbn, rawprogram0.xml, patch0,xml to recover.
If you can get hold of a phone similar to yours, you can dump all the partitions. That can then be used to get the required information to make your unique rawprogram0.xml. The process of dumping becomes very easy if the phone is root and you are running an insecure boot. Using basing Linux commands like fdisk,gparted,proc you can get and idea of your partition details. The dd command will help you dump the partitions.
Yes the tools to use is from the QPST suite or look for the stand alone emmcdl.exe
As your phone is showing the QUSB 9008 mode you need to be able to switch the phone to Emergency Download Mode after which you can use MIflash or similar tool to flash the ROm from the dumped images. Thats where the rawprogram0.xml comes in. It details partition information required to revive the phone.
Havent succeeded yet, but am feeling encouraged. Probably need to resolve syntax errors creating the rawprogram0.xml and figure out if just this much is enough to switch the phone to EDL.
After lurking here for months, this is my first post, therefore I request indulgence in case I have inadvertently erred
TooSour
AnY-One said:
Hi guys, i really hope you can help me, i m so deseperate...
After OTA Update my CATERPILLAR S30 bricked into bootloop, i can access to the stock recovery (wipe data/factory not fix it)
and bootloader show me ; "DC CHECK"
I read that it could be my bootloader (emmc) wich it's corrupted...
The chipset is a Qualcomm Snapdragon MSM8909, of course USB debugging is disabled and i can't find any stock rom, backup for this phone....
Please HELP ME...i work hight in the mountain and if i cant communicate it will become....quite dangerous for me...
If someone has a backup (EU AREA), a stock rom or any solution for me ill be gratefull
Bye
Click to expand...
Click to collapse
You will need:
Hi
I have a similar issue with a different phone (Reliance LYF LS 5014 - a.k.a. Haier HL-L51) Service centres will claim that the motherboard needs to be changed (and charge you an arm and a leg ;p) Even if you get the firmware image it wont help. Thats becuase if you are bricked and in the QLoader 9008 , you first have to get the phone in EDL (emergency download mode) only then can you use MI Flash et al to flash your ROM.
The route I am taking is as follows: got hold of a similar phone and dumped all the partitions using the dd command. Then getting hold of all partition information using gdisk/parted/df et al This is so that I can create a partition.xml. From this I could run a Python script ( PartitionTool.py) to get rawprogram0.xml, patch0.xml. Using emmcldl and partiton.xml I can create the 8909_msimage.mbn . Hopefully, armed with these and QPST /Miflash I should be able to revive my phone. I have read that one needs the mprg8909.hex to kick the phone into EDL but am not convinced that without it I will remain stuck. That file seems to be guarded like a state secret by phone manufacturers.
ALl this I have learnt the hard way over almost a fortnight. I confess that I do fall into the "noob" category and cant program/develop to save my life. Therefore it should be easy for anyone with the right amount of enthu
Cheers
Zi0nlive said:
Is there someone reading me who has the same phone?
Is there someone able to upload me .img (system, boot ...) that i can flash with QPST Tools? Stock Firmware? Nandroid Backup?
Is there someone who can guide me to repair that phone stuck in bootscreen? I think the problem come from my stupidity fogetting to unroot (Kingoroot apk replaced by SuperSU) before OTA update.
Click to expand...
Click to collapse
on continuing my quest for a solution
Havent given up yet.
Discovered two really useful utilities: emmcdl and fh_loader both work from the DOS command prompt and are useful to download images and partitions to the phone.
Managed to create a rawpartition0.xml which I think is for my phone ( LYF Wind 4 a.k.a Haier HL L51 and LS5014) For this I used a similar phone and after rooting it managed to extract start sector and size in kilobytes info for each of the partitions.
Also used EFS Professional to get a backup of emcc firmware.
Have successfully downloaded all the partitions but am failing at the bootloader (emmc firmware) part. Continuing my quest for a solution and will share whatever I figure.
Cheers
Vonageext4ts said:
Havent given up yet.
Discovered two really useful utilities: emmcdl and fh_loader both work from the DOS command prompt and are useful to download images and partitions to the phone.
Managed to create a rawpartition0.xml which I think is for my phone ( LYF Wind 4 a.k.a Haier HL L51 and LS5014) For this I used a similar phone and after rooting it managed to extract start sector and size in kilobytes info for each of the partitions.
Also used EFS Professional to get a backup of emcc firmware.
Have successfully downloaded all the partitions but am failing at the bootloader (emmc firmware) part. Continuing my quest for a solution and will share whatever I figure.
Cheers
Click to expand...
Click to collapse
1. Why can't you go to the Rjio service center and get it flashed? Just tell them it got screwed after an update.
2. How did you manage to root the phone? Mine is Flame1 which has same MSM8909 chipset.
I am very not happy with the stock ROM but I don't think anyone has come up with a custom ROM for this cheap chipset.
I have bricked my CAT S30 too. Is there someone who have a solution? Or can somehow make a ROM copy so I can somehow flash it to the phone? I made a lot of searching and can not figure out how to make the phone work again.
hello I need firmware for S30 because I lightened too much after the root and I deleted something I should not, is now locked in the home screen CAT, but I can get into fastboot and bootloader.
thank you guys
file for CAT S30
Hello
I purchased another CAT S30 which has just lit downloaded a system update and I extracted from the cache, now the load so you can work on it.
if you need other things tell me how can I copy them from working phone.
my I crashed after I canceled the DownloadProviderUi.apk files and perhaps I put not compatible. now I can only access the fastboot or DC CHECK mode.
I tried to flash the .zip program but by mistake, I tried to flash the update and installs it by error although it says it has been installed, and still does not start, remains in the white screen CAT
https://www.dropbox.com/s/trqfxvnp90qt8vn/__FUMO.zip?dl=0
Vonageext4ts said:
Havent given up yet.
Discovered two really useful utilities: emmcdl and fh_loader both work from the DOS command prompt and are useful to download images and partitions to the phone.
Managed to create a rawpartition0.xml which I think is for my phone ( LYF Wind 4 a.k.a Haier HL L51 and LS5014) For this I used a similar phone and after rooting it managed to extract start sector and size in kilobytes info for each of the partitions.
Also used EFS Professional to get a backup of emcc firmware.
Have successfully downloaded all the partitions but am failing at the bootloader (emmc firmware) part. Continuing my quest for a solution and will share whatever I figure.
Cheers
Click to expand...
Click to collapse
Hi.. i have a CAT S30 stuck in logo, how i can use your file? thanks
Hi got this same phone only two weeks ago, and broke it trying to root it, got stuck on Bootscreen, however I found an unofficial rom for the device, loaded into an SD card and applied via recovery and boom, its a working phone again.
If you still need help, let me know so I send you a link to the ROM.

Can anyone help me root properly BLU Vivo 5 MINI? I'm freezed.

Hello all,
I'm a long date not registered user but after tryIng root my Blu Vivo 5 MINI a whole week I've come to the conclusion to ask for your help!
I'll try put all the things and methods I tried to achieve this, but not succeeded.
Device info:
BLU Vivo 5 Mini
Android version 6.0;
Build number: MRA58k
Baseband version MOLY.WR8.W1499.MD.WG.MP.V57.P14
Chipset: MT6580
What I've tried so far:
After enable USB debugging and unlock oem. I uninstalled my antivirus too.
- Tried root with one click programs like Kingroot, genius root, etc. The programs can verify the model vivo 5 mini but can't complete the process.
- Tried root with SP Flash Tool taking the stock rom and replacing the recovery.img by a twrp-recovery.img for chipset MT6580. After sucessfuly flashed and turn device on with power button + volume up button the system displays that's entering Recovery Mode but reset automatically doing a reboot. When I gave up of repeating this and let the device reboot I comes as a reseted stockrom or it soft bricks looping the boot screen until battery end.
- Tried flash recovery.img for mt6580 chipset by fastboot. Made device listed from adb devices, then entered fastbook mode by adb reboot bootloader and flash it with fastboot flash recovery recovery.img. At the phone screen displays data transfer status Ok and then when rebooted I get the same flooping error, cant enter twrp because I don't know why and when I let it go I get a reseted stockrom again or soft bricked.
I tried made this last step too doing the adb erase recovery.img and trying again. Tried made before it all some adb kill-server and adb start-serve and also kill the adb.exe process from task manager processes.
Can anyone please, help me? What should I do? Anyone already rooted sucessfuly a Vivo 5 MINI?
Hope you can help me and made me able to use the full potential of my phone.
goodfox said:
Can anyone please, help me? What should I do? Anyone already rooted sucessfuly a Vivo 5 MINI?
Hope you can help me and made me able to use the full potential of my phone.
Click to expand...
Click to collapse
Don't have a MINI. I found a twrp that was close to my XL2, used Carliv Image Kitchen to unpack it and the stock recovery. Had to redo some files, TWRP building thread shows correct formats and info needed, so read that and adjust for your MINI. Repacked using Carliv then flashed using SPF Tools. Once it worked, I backed up all my partitions then flashed SuperSU.
Once I realized I had all the info I needed to build TWRP, that is what I did.
smith901 said:
Don't have a MINI. I found a twrp that was close to my XL2, used Carliv Image Kitchen to unpack it and the stock recovery. Had to redo some files, TWRP building thread shows correct formats and info needed, so read that and adjust for your MINI. Repacked using Carliv then flashed using SPF Tools. Once it worked, I backed up all my partitions then flashed SuperSU.
Once I realized I had all the info I needed to build TWRP, that is what I did.
Click to expand...
Click to collapse
Thank you for your light!
I'll sit and study this a little deeper, hope have some time soon. When I get informations and try new things I back here let you guys know.
If anyone still knowing something more, please, share here in the thread
Blu Vivo 5 Mini
For full disclosure I am not a developer so my anticipated apologies for any comments that sound weird.
I got a Blu Vivo 5 Mini for using as a data collection on a field project, expecting it would be OTG compatible. It happens that it is not from out-of-the-box.
I've been trying all sorts of suggestions to root it available on this and other threads but nothing works.
I spoke to Blu this morning and they told me that the hardware in this phone is not compatible with OTG. I am trying to understand what that means. Using OTG checker it only says I am missing the USB Host file.
Appreciate any light on this.
here is how to root the blu vivo 5 mini
I know i am a little late to answer this question
follow this thread
https://forum.xda-developers.com/android/general/rooting-blu-vivo-5-mini-using-twrp-guide-t3924895

[Solved] Hard brick after flashing Magisk's patched boot.img. Unbrick with SP Flashtool possible?

Update 2021.01.24: I consider the problem mentioned here as solved, since it can be resolved with MTK Bypass explained in the Guides Section. BE CAREFUL however to ONLY choose "Download Only" from the dropdown box in SP Flashtool! DO NOT select anything with "Format" in it, else you will lose S/N, MACs and IMEIs!
--- Original post ---
Hi, I have hard-bricked my new Realme 6 while trying to root it with Magisk. At the moment I am stuck in a bootloop at the power-on logo (realme in white letters). The boot animation (yellow realme letters) does not appear, instead the phone reboots after ~35 seconds. The bootloader says "Orange State".
I can NOT enter fastboot nor recovery mode by any key combination. Holding Power and Vol- makes the string RECOVERY MODE appear for a split second in the lower left part of the screen, however nothing happens afterwards.
I can power down by holding Power and Vol+ an releasing them immediately after the screen goes blank.
Holding Vol- and Vol+ while the phone is off and connecting USB makes a USB serial device appear on a windows machine for about 1-2 seconds before it disappears again.
I am very thankful for any hints on how to unbrick the device.
Here's what I have done in detail to mess up the phone:
1. OTA-Update to the latest OS in my region (EU11.A.48)
2. Unlocked the bootloader with the realme In-depth Test app (everything fine so far)
3. Download stock firmware RMX2001EU_11.A.48 ozip from realmeupdater.com
4. Unzipped with gnu unzip (content was readable, no extra decrytion tool for the ozip needed?) and extracted boot.img
5. Installed Magisk Manager and uploaded boot.img to the phone
6. Patched boot.img with Magisk Manager (and if I remeber correctly DIDN'T UNCHECK Preserve AVB 2.0/dm-verity)
7. Certainly FORGOT to do anything with vbmeta.img
8. Did NOT erase cache and userdata
9. Flashed patched boot.img directly and WITHOUT --disable-verity or --disable-verification
10. Rebooted the phone.
Am I correct that my problem is the AVB/dm-verity part?
Why does the modified boot.img affect the recovery (I thought they were seperate)
Can I try something with SP Flashtool?
I do have a second intact device that I didn't dare to touch yet, if that helps resolving the issue (e.g. for SP Flashtool readbacks).
As said any advice is highly welcome. Please ask I you need any more information to help.
I did that too... Magisk patched boot .img process of rooting is the risky process , I bricked my device, got it into red state.. tried thick and thin to revive using various flash tools, unable to do it, finally went to a shop , got it fixed, go-to a good repair shop, if you go to the service center, they will say replace motherboard for 5 k , I hope it helps, do traditional unlock bootloader TWRP recovery then flashing Magisk zip method for rooting process.
Thank you for sharing! But doesn't red state mean locked BL plus non-stock firmware? I wish I could find any repair shop during this Corona lockdown... May I ask how much they charged you for having the phone reflashed?
cmfan said:
Thank you for sharing! But doesn't red state mean locked BL plus non-stock firmware? I wish I could find any repair shop during this Corona lockdown... May I ask how much they charged you for having the phone reflashed?
Click to expand...
Click to collapse
Yes, you are right , red state means that, I guess bcoz, I may have formatted it and ran again unlocked bootloader but it showed unlocking failed, but I thought that I had previously unlocked it so it should be unlocked but I forgot to do that app thing process of deep test again, and I was on Android 10 latest and patched boot img of previous version using magisk, now I understand what mistake I made, I should have used boot IMG of current version of a 10 , but still I am afraid of doing this magisk method of rooting by patching boot IMG bcoz repair cost me 800/- , and I found out on YT that the latest version of a 10 of my device doesn't readily allows twrp and flashing zip of magisk.... Plus there are half baked info on important things, this is new device for me, I have had rooted Samsung and Lenovo, but rooting this is kind of tricky, bcoz it's still new, I think.... Want to try .... But I m afraid.... Tried fastboot method of TWRP flashing but can't replace stock room, so I guess I can't root .....
Well, there is a tutorial on how to root here on XDA, and seems to be confirmed working. I just didn't know about the vbmeta part from earlier Android versions. Haven't you tried that?
cmfan said:
Well, there is a tutorial on how to root here on XDA, and seems to be confirmed working. I just didn't know about the vbmeta part from earlier Android versions. Haven't you tried that?
Click to expand...
Click to collapse
Thnx man, I have rmx 1825 , but the process would be same for my device, I would have to search for it...
cmfan said:
Thank you for sharing! But doesn't red state mean locked BL plus non-stock firmware? I wish I could find any repair shop during this Corona lockdown... May I ask how much they charged you for having the phone reflashed?
Click to expand...
Click to collapse
Hello, please check my reply to your reply on my thread. BROM mode is as known as "Emergency Mode" and should not be inaccessible. I will once again request you to try different key combinations and also if it's detecting as fastboot, ADB or Fastboot commands should be available. Please try typing adb reboot or fastboot reboot with minimal ADB and fastboot tools and let me know. If you want to personally message me, message my telegram. I will try helping you there.
Why is this thread showing solved !!! It's nothing solved here... Pls check and confirm
daeSundae said:
Hello, please check my reply to your reply on my thread. BROM mode is as known as "Emergency Mode" and should not be inaccessible. I will once again request you to try different key combinations and also if it's detecting as fastboot, ADB or Fastboot commands should be available. Please try typing adb reboot or fastboot reboot with minimal ADB and fastboot tools and let me know. If you want to personally message me, message my telegram. I will try helping you there.
Click to expand...
Click to collapse
I think there is no Emergency Download Mode in Realme devices.. pls guide ...
Ank Sak said:
Why is this thread showing solved !!! It's nothing solved here... Pls check and confirm
Click to expand...
Click to collapse
Hello. Please follow this guide.
Repair DEAD(HARD BRICKED) Realme 3 | 3i Tutorial
In this tutorial we are going to Repair Realme 3 (RMX1821) MT6771 Chipset. from being hard bricked (no charge, no recovery, no fastboot) using SP Flashtool. with the help of Bypass Utility "MTK-bypass" to disable bootrom protection(sla and daa)...
forum.xda-developers.com
daeSundae said:
Hello. Please follow this guide.
Repair DEAD(HARD BRICKED) Realme 3 | 3i Tutorial
In this tutorial we are going to Repair Realme 3 (RMX1821) MT6771 Chipset. from being hard bricked (no charge, no recovery, no fastboot) using SP Flashtool. with the help of Bypass Utility "MTK-bypass" to disable bootrom protection(sla and daa)...
forum.xda-developers.com
Click to expand...
Click to collapse
Thnx that's a life saver, I am afraid to go forward with the device, this is promising, I will try, I found out that the new version c17 os Android 10 I am unable to root by twrp magisk zip flashing method, twrp isn't installing, there's an .ofp extracter, but it gives virus with software, unable to do, even talked on WhatsApp and gave him Gmail id, will try this method , I wanted the SP flash tool method, it's simple and can readily restore the stock rom... Thnx Sundae.. daesundae ... What kind of name is that...?? .. chuckles...
Ank Sak said:
Why is this thread showing solved !!! It's nothing solved here... Pls check and confirm
Click to expand...
Click to collapse
This thread is about a Realme 6 (RMX2001 in my case). I've edited the very first post to immediately show the solution. Please check there or follow daeSundae's guide if you have a different device.
cmfan said:
This thread is about a Realme 6 (RMX2001 in my case). I've edited the very first post to immediately show the solution. Please check there or follow daeSundae's guide if you have a different device.
Click to expand...
Click to collapse
I saw everything that You posted, incidentally the YouTube video on this is on rmx1825 , thnx, whatever you posted it helped..

Categories

Resources