{
"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"
}
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Notice1:
U Pro has A/B partitions. to prevent issues its good to flash it in both slot, because i/we can not know on which partition you are
Notice 2:
This version only working on Eragon roms
Maybe soon I'll manage it to work on stock rom
Notice 3: Sdcard now working
DOWNLOAD
TWRP for 20180227 Base via Qfil Flashtools:
Go here : https://drive.google.com/file/d/1JZ59mO07Zc1a9kdA6j7LJvrgc9g2kf5d/view?usp=sharing
TWRP for 20180511 Base and newer:
Go here: https://drive.google.com/file/d/1RrWuncXsH8GtCTbaEgGpDffRUDK9fMVv/view?usp=sharing
INSTALLATION
if you use the old 20180227 Base you have to use Qfil Flashtools , because fastboot commands dont work in that Build.
we have a good guide of how to use FLashtools already
look here: https://forum.xda-developers.com/android/development/guide-elephone-pro-user-manual-t3775895
if you are on 20180511 Base and newer you can use fastboot commands
required : ADB and fastboot
enable usb debugging in developer settings.
do this:
Code:
adb shell
Code:
reboot bootloader
now we flash it in slot a
Code:
fastboot flash boot_a twrp.img
after that we flash it also in slot b
Code:
fastboot flash boot_b twrp.img
Special thanks to
teamwin for this awesome custom recovery
And @skeleton1911 for his help
Reserved 1
I loaded up all my usual apps and settings and was going to do twrp backup and strange thing happened: the recovery doesn't see my external SD. I can see sd card's files from the phone but it's invisible in twrp. Funny, because someone couldn't flash ROM from sd yesterday and I did, I still have the ROM files there on SD. I tried to pick the sd storage for the backup and that's how I found out it's missing. The trwp was flashed per instruction: fastboot, 'a' & 'b' then I did a total wipe in twrp and flashed the ROM twice - that was it. Probably some conflict between a an b again? It can wait, am not in the hurry, this Rom otherwise looks really good, it boots faster then the stock, nice.
mzsquared said:
I loaded up all my usual apps and settings and was going to do twrp backup and strange thing happened: the recovery doesn't see my external SD. I can see sd card's files from the phone but it's invisible in twrp. Funny, because someone couldn't flash ROM from sd yesterday and I did, I still have the ROM files there on SD. I tried to pick the sd storage for the backup and that's how I found out it's missing. The trwp was flashed per instruction: fastboot, 'a' & 'b' then I did a total wipe in twrp and flashed the ROM twice - that was it. Probably some conflict between a an b again? It can wait, am not in the hurry, this Rom otherwise looks really good, it boots faster then the stock, nice.
Click to expand...
Click to collapse
It's fixed now i uploaded the new twrp now everything working very well
Maherabed1986 said:
It's fixed now i uploaded the new twrp now everything working very well
Click to expand...
Click to collapse
sorry for bringing bad news, I flashed that new ver. it shows SDcard(it wasn't there before) and that's it, it won't go 'up level', also in File Manager or Backup storage choices it shows externalSD with 0MB space.
Hey Guys, we have two parallel Upro Universes here, two seperate threads on "Unofficial twrp for Elephone u pro v3.2.1.0", would that be _a and _b?
mzsquared said:
sorry for bringing bad news, I flashed that new ver. it shows SDcard(it wasn't there before) and that's it, it won't go 'up level', also in File Manager or Backup storage choices it shows externalSD with 0MB space.
Hey Guys, we have two parallel Upro Universes here, two seperate threads on "Unofficial twrp for Elephone u pro v3.2.1.0", would that be _a and _b?
Click to expand...
Click to collapse
Can you join us on Telegram group plz
https://t.me/joinchat/GxIBOhKXi5I6bsNWOm6LFg
Maherabed1986 said:
Can you join us on Telegram group plz
https://t.me/joinchat/GxIBOhKXi5I6bsNWOm6LFg
Click to expand...
Click to collapse
opened my acct in telegram, so, what next?
mzsquared said:
opened my acct in telegram, so, what next?
Click to expand...
Click to collapse
Tab the link again then join the group
mzsquared said:
sorry for bringing bad news, I flashed that new ver. it shows SDcard(it wasn't there before) and that's it, it won't go 'up level', also in File Manager or Backup storage choices it shows externalSD with 0MB space
Click to expand...
Click to collapse
same problem here
jimibxl said:
same problem here
Click to expand...
Click to collapse
reinstalled, reflashed, flashed and reinstalled and still no show for extSD in TWRP. But am all set for now, placed Eragon v.5 and Magisk Mgr on microSD/USB C OTG dongle and installed the ROM(zip) + Magisk(zip) from there via TWRP. Everything's good 'xept that 0 extSD. I was also able to do TWRP nandroid sys backup which went on that OTG dongle, some 3.8GB, that'll save me some time in the future I'd think :laugh: So, with the Springtime weather outside am gonna leave my computer stuff now and go out to ejnoy some of that Spring! See you later!
Hi Skeleton my problem is:
target reported max download size of 536870912 bytes
sending 'boot_b' (55180 KB)...
OKAY [ 1.564s]
writing 'boot_b'...
FAILED (remote: unknown command)
finished. total time: 1.567s
and
PS C:\adb> fastboot flash boot_b twrp.img
target reported max download size of 536870912 bytes
sending 'boot_b' (55180 KB)...
OKAY [ 1.564s]
writing 'boot_b'...
FAILED (remote: unknown command)
finished. total time: 1.567s
Can you help me??
Thanks
Enrique602012 said:
Hi Skeleton my problem is:
target reported max download size of 536870912 bytes
sending 'boot_b' (55180 KB)...
OKAY [ 1.564s]
writing 'boot_b'...
FAILED (remote: unknown command)
finished. total time: 1.567s
and
PS C:\adb> fastboot flash boot_b twrp.img
target reported max download size of 536870912 bytes
sending 'boot_b' (55180 KB)...
OKAY [ 1.564s]
writing 'boot_b'...
FAILED (remote: unknown command)
finished. total time: 1.567s
Can you help me??
Thanks
Click to expand...
Click to collapse
You are on build 20180227 so the flash commands not available you must use Qfil flashing tools to flash twrp
mzsquared said:
reinstalled, reflashed, flashed and reinstalled and still no show for extSD in TWRP. But am all set for now, placed Eragon v.5 and Magisk Mgr on microSD/USB C OTG dongle and installed the ROM(zip) + Magisk(zip) from there via TWRP. Everything's good 'xept that 0 extSD. I was also able to do TWRP nandroid sys backup which went on that OTG dongle, some 3.8GB, that'll save me some time in the future I'd think :laugh: So, with the Springtime weather outside am gonna leave my computer stuff now and go out to ejnoy some of that Spring! See you later!
Click to expand...
Click to collapse
On last build of twrp everything is working perfectly
Thanks but I run now Eragon V6. Each time start the Rom appear yellow !.
Enrique602012 said:
Thanks but I run now Eragon V6. Each time start the Rom appear yellow !.
Click to expand...
Click to collapse
It's because the unlocked bootloader it's normal
The problem is when I try to install TWRP now run V6:
target reported max download size of 536870912 bytes
sending 'boot_b' (55180 KB)...
OKAY [ 1.564s]
writing 'boot_b'...
FAILED (remote: unknown command)
finished. total time: 1.567s
and
PS C:\adb> fastboot flash boot_b twrp.img
target reported max download size of 536870912 bytes
sending 'boot_b' (55180 KB)...
OKAY [ 1.564s]
writing 'boot_b'...
FAILED (remote: unknown command)
finished. total time: 1.567
Thanks again
Hi Skeleton now I try to install TWRP and first no problem with boot_a and boot_b.
I run V6.
When restart the phone initial appear ! yellow........next appear TWRP and nothing hapen. Each time restart phone appear the same thing. Many times.
I try to install TWRP with QPST and nothing happend
I reinstall V5 by zip file and reinstall V6 by QPST and all ok.
What can I do to install TWRP without problem.
Thanks so much
Maherabed1986 said:
fix this command from
Code:
fastboot falsh boot_b twrp.img
to
Code:
fastboot flash boot_b twrp.img
Click to expand...
Click to collapse
And thanks dude. :good:
powergo said:
And thanks dude. :good:
Click to expand...
Click to collapse
Thanks dude but there's no difference between the two codes ?
Maherabed1986 said:
Thanks dude but there's no difference between the two codes
Click to expand...
Click to collapse
i mean falsh to flash
:good:
Related
Hi!
I've been going mad searching the web for a solution.
As you understand I was stupid enough to wipe the whole internal storage when I was about to flash OxygenOS.
So now I have no OS to boot up to.
I've have tried basically everything I've found of the web.
- Sideloading a stock flash worked partially, it transferred but then nothing more.
- Fastboot using this cmd: fastboot -w update [insert zip here].zip worked partially but stuck on writing system.img
- Fastboot using all the individual commands is the same thing, gets stuck on writing system.img or erasing userdata.
It feels as whatever I do something small is messing it up.
Can you please help me troubleshoot this super annoying mess I've done.
I have gotten a basic knowledge of sideloading and fastboot commands from this though, but not enough I feel.
Thanks in advance!
mayby this help... google for "OPO_Toolbox" and click first link
choose 16 or 64 gb !
reinstall cm 11
hgeert said:
mayby this help... google for "OPO_Toolbox" and click first link
choose 16 or 64 gb !
reinstall cm 11
Click to expand...
Click to collapse
I have used the toolkit (the one by inthiaano) and when installing the cm11 it gets stuck on erasing userdata..
target reported max download size of 536870912 bytes
sending 'boot' (5580 KB)...
OKAY [ 0.177s]
writing 'boot'...
OKAY [ 0.109s]
finished. total time: 0.286s
target reported max download size of 536870912 bytes
erasing 'userdata'...
Ok,i found a Way back to Stock for Mediapad X2 703L
i test this and works fine.
If your Mediapad X2 Rooted and have install Custom Recovery and will go back to Stock.(Also your Pad is Rooted,Unlocked Bootloader and Twrp installed)
Backup your Data Before Flash this Firmeware!!!
Download the Huawei Extractor App unpack and install it (Download from Attachment).
Download the Huawei Firmware from here and unpack it.
Installing Mediapad X2 Driver (Hi Suite) and must have fastboot ADB installed.
Copy the Update.app in dload Folder in Internal or external Storage.(For later)
Open the Huawei Extractor and extract Recovery and or System and copy Recovery and or System in your ABB Folder.
Reboot your Mediapad in Fastboot/Bootloader Power Off - Connect to Pc and Press and hold Power and Volume Down to boot in Fastboot Mode or CMD Command adb reboot bootloader.(USB Debugging must be enabled)
Open CMD and Navigate to your ADB Folder (cd C:\ADB)
For Recovery to Update for Local Update
fastboot flash recovery RECOVERY.img
For System (If you have delete Apps from System and not wipe your Data))
fastboot flash System SYSTEM.img
wait to finish this Procedur.
The X2 Reboot and go in Setting to Update Program-Menu-Local Update and Flash your Original Firmware for GEM 703L
Wait to Reboot and you have Original Stockrom/Firmware without Root and Twrp.This wipe your Data,please Backup your Data before you make this Procedur!
I am not responsible for damage to the unit or other!!!
Sorry for my bad English.
thank you. now my phone gets bootloop.I will try this method !
I can't flash system.img.Error messaging : can't load system.img
Bootloader unlocked
I have 702L, will the 703L firmware work for my Mediapad? I couldn't find the specific firmware for it on Huawei's web-site.
It worked! Oh my god, thank you! I was close to tears, being up all night trying to fix my failed root attempt. Time to start again from scratch hahahaha!
what if in fastboot when flashing it says : " write : command not allowed " ...
How do I get USB debugging if I have no ROM installed and TWRP won't flash D: (only thing I can get is erecovery)
EDIT: Well TWRP wouldn't flash because I had to reunlock my bootloader, yes....reunlock.
letschky said:
For System (If you have delete Apps from System and not wipe your Data))
fastboot flash System SYSTEM.img
Click to expand...
Click to collapse
Code:
platform-tools>fastboot flash recovery RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (32354 KB)...
OKAY [ 1.010s]
writing 'recovery'...
OKAY [ 1.050s]
finished. total time: 2.060s
platform-tools>fastboot flash System SYSTEM.img
[COLOR="Red"]error: cannot load 'SYSTEM.img'[/COLOR]
xdxdxd33 said:
Code:
platform-tools>fastboot flash recovery RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (32354 KB)...
OKAY [ 1.010s]
writing 'recovery'...
OKAY [ 1.050s]
finished. total time: 2.060s
platform-tools>fastboot flash System SYSTEM.img
[COLOR="Red"]error: cannot load 'SYSTEM.img'[/COLOR]
Click to expand...
Click to collapse
Extract the SYSTEM.img again,i had the same Problem,then it worked
letschky said:
Extract the SYSTEM.img again,i had the same Problem,then it worked
Click to expand...
Click to collapse
Nope still does not work, I tried with GEM-703L_EMUI3.0.5_Android5.0_V100R001C233B015 and GEM-703L_EMUI3.1_Android5.1_V100R001C233B112
What is the sha1 or md5 hash for your SYSTEM.img?
My fastboot / platform-tools were outdated, so I downloaded newer ones that fixed the issue.
I'm pulling out my hair trying to get this to work.
When I try to run the local update using the UPDATE.APP file, I get an incompatible error.... I definitely downloaded the 703L stock ROM FOR MY 703L...... so wtf is the problem?
I've followed your instructions and the local update always fails with this error message i.imgur.com/Gb7P9Ks.jpg
So what could I be doing wrong...?
I've tried all these ROMs
Code:
GEM-703L_EMUI3.0.5_Android5.0_V100R001C233B015
GEM-703L_EMUI3.1_Android5.1_V100R001C233B112
GEM-703L_EMUI3.1_Android5.1_V100
GEM-703LT_EMUI3.1_Android5.1_V10
Hello I have the latest version of this rom http://forum.xda-developers.com/oneplus-one/development/rom-cm-12-builds-t3045053
and it was working great! I had no problems and then one day while playing an audio file (smart voice recorder), my phone froze for lke 30 seconds and then just rebooted by itself and started looping the android logo. Worried I booted into TWRP (3.0.2-0) and found out that in the logs I get these messages:
Could not mount /data and unable to find crypto footer.
Failed to mount /data (invalid argument)
Failed to mount /cache (invalid argument)
Unable to mount storage
What the hell, does this happen to anyone? Using their phone all ok and then bam reboot and now my internal storage is gone! Was it because I was using a 25 watt apple charger because I was recording video at the time and needed the juice. Oh man I really need those videos they mean everything to me!
system shows a size but very small like 1.3 gigs or something
data shows 0 mb for all stats
cache shows 0 mb for all stats
Internal Storage shows "invalid partition selection"
I have no idea what happened, I have such important data on this phone! How can I recover this? Please!!! I tried using the repairing data option and i got this error message
/sbin/efsck -fp /dev/block/mmcblk0p28 process ended with ERROR: 4
Unable to repair data
Will offer a bounty if someone can help me recover my data! I am knocking my own ass for not having a backup ugh
I will offer a bounty if someone with experience can help me through this. The memories of my mother's passing means a lot to me and I would hate to lose it because some stupid app crashed on me and the phone rebooted.
vap3 said:
Hello I have the latest version of this rom http://forum.xda-developers.com/oneplus-one/development/rom-cm-12-builds-t3045053
and it was working great! I had no problems and then one day while playing an audio file (smart voice recorder), my phone froze for lke 30 seconds and then just rebooted by itself and started looping the android logo. Worried I booted into TWRP (3.0.2-0) and found out that in the logs I get these messages:
Could not mount /data and unable to find crypto footer.
Failed to mount /data (invalid argument)
Failed to mount /cache (invalid argument)
Unable to mount storage
What the hell, does this happen to anyone? Using their phone all ok and then bam reboot and now my internal storage is gone! Was it because I was using a 25 watt apple charger because I was recording video at the time and needed the juice. Oh man I really need those videos they mean everything to me!
system shows a size but very small like 1.3 gigs or something
data shows 0 mb for all stats
cache shows 0 mb for all stats
Internal Storage shows "invalid partition selection"
I have no idea what happened, I have such important data on this phone! How can I recover this? Please!!! I tried using the repairing data option and i got this error message
/sbin/efsck -fp /dev/block/mmcblk0p28 process ended with ERROR: 4
Unable to repair data
Will offer a bounty if someone can help me recover my data! I am knocking my own ass for not having a backup ugh
Click to expand...
Click to collapse
In twrp if you go to advance then file manager click on sdcard can you see your files?
If not did you try to mount in twrp?
If so then you can pull the whole sdcard or select files via adb.
Durso81 said:
In twrp if you go to advance then file manager click on sdcard can you see your files?
If not did you try to mount in twrp?
If so then you can pull the whole sdcard or select files via adb.
Click to expand...
Click to collapse
for question #1 yes I do see my files. But certain folders like DCIM (pictures) or other apps such as whatapp is not showing.
when i try to mount in TWRP only firmware and system is checkable.... data/cache/usb-otg is not selectable (meaning check marks won't show up if I try to click it)
when I hit "select storage" i see the select storage options and both options (internal storage and usb-otg) says 0 MB
for your last suggestion im going to try it and see if I can access my files
Thank you for your help! Let me know how else I can continue the diagnostic and I will keep my word
vap3 said:
for question #1 yes I do see my files. But certain folders like DCIM (pictures) or other apps such as whatapp is not showing.
when i try to mount in TWRP only firmware and system is checkable.... data/cache/usb-otg is not selectable (meaning check marks won't show up if I try to click it)
when I hit "select storage" i see the select storage options and both options (internal storage and usb-otg) says 0 MB
for your last suggestion im going to try it and see if I can access my files
Thank you for your help! Let me know how else I can continue the diagnostic and I will keep my word
Click to expand...
Click to collapse
Yeah I would try pulling the whole sdcard to your computer via adb and see if it pulls the files you want.
If that doesn't work all I got is you can dirty flash that same ROM you had installed before. When you dirty flash you don't wipe data or anything since its the same ROM you had before. Its the same thing you do when you update to a new version of that developers ROM and you don't loose your data.
Just curious did you change over to f2fs the developer recommended it for installing his ROM, not sure if that's what caused the initial problem if you did not change to f2fs.
Durso81 said:
Yeah I would try pulling the whole sdcard to your computer via adb and see if it pulls the files you want.
If that doesn't work all I got is you can dirty flash that same ROM you had installed before. When you dirty flash you don't wipe data or anything since its the same ROM you had before. Its the same thing you do when you update to a new version of that developers ROM and you don't loose your data.
Just curious did you change over to f2fs the developer recommended it for installing his ROM, not sure if that's what caused the initial problem if you did not change to f2fs.
Click to expand...
Click to collapse
interesting i will try the adb method and see if that i can pull the files despite not seeing everything in the file manager
unfortunately i have never changed to the f2fs file system due to me being a noob at the time. But i never had a problem with his early builds and dirty flashing all the way to September. Ironically every time I dirty flashed i did a nandroid backup on the phone. lol... i can't even access that file right now because i don't see it in the file manager as the data cannot be accessed at the moment.
vap3 said:
interesting i will try the adb method and see if that i can pull the files despite not seeing everything in the file manager
unfortunately i have never changed to the f2fs file system due to me being a noob at the time. But i never had a problem with his early builds and dirty flashing all the way to September. Ironically every time I dirty flashed i did a nandroid backup on the phone. lol... i can't even access that file right now because i don't see it in the file manager as the data cannot be accessed at the moment.
Click to expand...
Click to collapse
Just to interject, not being on f2fs is wise, I don't believe it to be as stable, and is not very useful..
I'd like to also recommend using TWRP 2.8.6 (there's a link in my signature).. I've read more recovery related issues since it was updated..
Good luck
I know you said you are new if your having issues figuring out how to pull files via adb there is a all in one toolkit that has a pull/push file fearure. http://www.wugfresh.com/brt/
It will be under advance utilities.
should i downgrade to twrp 2.8.6 before proceeding to try the adb dirty flash upgrade?
Durso81 you are so awesome! Gonna try this tonight (PRAYING) and Setting.Out thank you!
damn I got this error message triying to flash twrp 2.8.6.0
C:\android-sdk-windows>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (10882 KB)...
OKAY [ 0.351s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.399s
uh oh... is the thing totally bricked? i also tried to flash the oct 15th build of jpgapps and it didn't work got this screenshot for you! That Bacon tool is cool though!
vap3 said:
damn I got this error message triying to flash twrp 2.8.6.0
C:\android-sdk-windows>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (10882 KB)...
OKAY [ 0.351s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.399s
uh oh... is the thing totally bricked? i also tried to flash the oct 15th build of jpgapps and it didn't work got this screenshot for you! That Bacon tool is cool though!
Click to expand...
Click to collapse
Looks like your firmware isn't correct, finish switching to 2.8.6 before fixing this.. As per recovery, flash the image in TWRP.. Select 'instal' and there's an option for 'IMG' select it and find the recovery image and then select the option for recovery, swipe to flash and upon success reboot the recovery.. Now update the firmware as per the ROM's OP and the ROM will flash..
Setting.Out said:
Looks like your firmware isn't correct, finish switching to 2.8.6 before fixing this.. As per recovery, flash the image in TWRP.. Select 'instal' and there's an option for 'IMG' select it and find the recovery image and then select the option for recovery, swipe to flash and upon success reboot the recovery.. Now update the firmware as per the ROM's OP and the ROM will flash..
Click to expand...
Click to collapse
I tried that and when i rebooted the TWRP is still 3.02.0 what's the next step?
vap3 said:
I tried that and when i rebooted the TWRP is still 3.02.0 what's the next step?
Click to expand...
Click to collapse
You still had 3.02 after flashing the 2.8.6 recovery.img and rebooting twrp? And fastboot flashing recovery failed?..
Try flashing this normally..
https://www.androidfilehost.com/?fid=95916177934548751
Setting.Out said:
You still had 3.02 after flashing the 2.8.6 recovery.img and rebooting twrp? And fastboot flashing recovery failed?..
Try flashing this normally..
https://www.androidfilehost.com/?fid=95916177934548751
Click to expand...
Click to collapse
exactly! Its like nothing wants to work I got the same error message trying to flash that url you gave me too
C:\android-sdk-windows>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (10882 KB)...
OKAY [ 0.347s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.406s
man now I know its one of those things I can't recover no matter how much money I throw at it T_T not even about the value of the phone but the data I appreicate your help though so if you have any other ideas please let me know i'm all ears
vap3 said:
exactly! Its like nothing wants to work I got the same error message trying to flash that url you gave me too
C:\android-sdk-windows>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (10882 KB)...
OKAY [ 0.347s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.406s
man now I know its one of those things I can't recover no matter how much money I throw at it T_T not even about the value of the phone but the data I appreicate your help though so if you have any other ideas please let me know i'm all ears
Click to expand...
Click to collapse
Don't fastboot flash a .zip... Flash it through recovery using twrp..
Fastboot is for recovery.IMG
Let's see if that helps..
Setting.Out said:
Don't fastboot flash a .zip... Flash it through recovery using twrp..
Fastboot is for recovery.IMG
Let's see if that helps..
Click to expand...
Click to collapse
what i would do is unzip the twrp and the default file name is recovery.img so I would unzip it to my SDK android folder that contains the adb.exe
so I tried flashing in TWRP again but this time selecting the zip file instead of the img file and I got the same error and it after rebooting it still boots into TWRP 3.0.2.0
vap3 said:
what i would do is unzip the twrp and the default file name is recovery.img so I would unzip it to my SDK android folder that contains the adb.exe
so I tried flashing in TWRP again but this time selecting the zip file instead of the img file and I got the same error and it after rebooting it still boots into TWRP 3.0.2.0
Click to expand...
Click to collapse
Are you encrypted?
Setting.Out said:
Are you encrypted?
Click to expand...
Click to collapse
like through TWRP or through android? I don't remember... if I am how do I unencrypt? But I'm wondering how I got here in the first place.
vap3 said:
like through TWRP or through android? I don't remember... if I am how do I unencrypt? But I'm wondering how I got here in the first place.
Click to expand...
Click to collapse
You'd know, it requires many steps to encrypt, so I'll guess no.. Have you ever been able to flash anything through that recovery?
I'd copy your SD to your computer and return to stock, then try again with customs from there...
Setting.Out said:
You'd know, it requires many steps to encrypt, so I'll guess no.. Have you ever been able to flash anything through that recovery?
I'd copy your SD to your computer and return to stock, then try again with customs from there...
Click to expand...
Click to collapse
nope when I try to flash the oct 15th of the rom I get simliar error messages like trying to flash the twrp 2.8.6
im wondering how am I suppose to recover certain files like my bitcoin app, google authenticator passcodes, smart audio recorder files, photos and videos as when i peek into the file structure nowhere is to be found!
can the bacon tool do all the backup for me? what's the easiest way to do this? damn im super sleepy so i'll try again tomorrow thanks for the help
Here is twrp for HUAWEI MATE 10 LITE.
Who want?
Comment Here.
i need Android 8 for mate 10 lite !
yes i need thanks
100% tested every thing work just mtp does not work..
Still working on it.
Link is Here
Extract to Pc in Adb Fastboot Folder and
Install through fastboot Command
fastbbot flash recovery_ramdisk twrp8.img
https://drive.google.com/file/d/1_dfpSOCD23Oz_LexYMn1JNRVfrlvKU-x/view?usp=drivesdk
Azan Mughal said:
Link is Here
Extract to Pc in Adb Fastboot Folder and
Install through fastboot Command
fastbbot flash recovery_ramdisk twrp8.img
https://drive.google.com/file/d/1_dfpSOCD23Oz_LexYMn1JNRVfrlvKU-x/view?usp=drivesdk
Click to expand...
Click to collapse
Officall oreo emui8 This is working twrp?
Taha0194 said:
Officall oreo emui8 This is working twrp?
Click to expand...
Click to collapse
Yep
I am using but not officiall.
Not compatible with Official Oreo
Taha0194 said:
Officall oreo emui8 This is working twrp?
Click to expand...
Click to collapse
I tried it on official Oreo.
It does not work.
Error received -
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (18199 KB)...
OKAY [ 0.479s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.493s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.028s
prasanthkb said:
I tried it on official Oreo.
It does not work.
Error received -
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (18199 KB)...
OKAY [ 0.479s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.493s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.028s
Click to expand...
Click to collapse
Bro. Offical oreo emui 8 working
adb command
fastboot flash recovery_ramdisk RECOVERY-V2.img
https://mega.nz/#!GxsAUQaS!2-9yPFh3reghkGcfSl3nRIJhHGkP8fqDsgUG66ewjkk
Taha0194 said:
Bro. Offical oreo emui 8 working
adb command
fastboot flash recovery_ramdisk RECOVERY-V2.img
https://mega.nz/#!GxsAUQaS!2-9yPFh3reghkGcfSl3nRIJhHGkP8fqDsgUG66ewjkk
Click to expand...
Click to collapse
Hi,
Many thanks. Flashed it finally
I want to take the TWRP backup of my Oreo.
Is it fine if i take the backup of all partitions and restore when needed ?
Some forums said not to restore OEMInfo and Product partitions with TWRP since its not 100% functional !!
I tried to backup to external SD and received error message saying "Cannot create folder, permission denied".
The same error when i used internal SD.
Can you please provide some information on this ?
prasanthkb said:
Hi,
Many thanks. Flashed it finally
I want to take the TWRP backup of my Oreo.
Is it fine if i take the backup of all partitions and restore when needed ?
Some forums said not to restore OEMInfo and Product partitions with TWRP since its not 100% functional !!
I tried to backup to external SD and received error message saying "Cannot create folder, permission denied".
The same error when i used internal SD.
Can you please provide some information on this ?
Click to expand...
Click to collapse
He's not backing up the data partition
It gives an error because of it
Remove sign from data when backing up
Also memory card format must be NTFS
*4GB does not support fat32
achievements
Azan Mughal said:
Link is Here
Extract to Pc in Adb Fastboot Folder and
Install through fastboot Command
fastbbot flash recovery_ramdisk twrp8.img
https://drive.google.com/file/d/1_dfpSOCD23Oz_LexYMn1JNRVfrlvKU-x/view?usp=drivesdk
Click to expand...
Click to collapse
so, this twrp can all save except data.
But we can restore data from emui 5.1 in emui 8.0?
merci
New Version is coming of twrp.
Azan Mughal said:
New Version is coming of twrp.
Click to expand...
Click to collapse
Great, and cant wait, when it is coming ?
Coming Soon
Coming Soon Every thing work and Now tell about it after view whats we need more.
You can unlock frp with this recovery and backup of frp
And backup every partition.
Chisetdel31260 said:
so, this twrp can all save except data.
But we can restore data from emui 5.1 in emui 8.0?
merci
Click to expand...
Click to collapse
I have not tried yet to retrieve data from emui 5 to emui 8 but you know about Android versions emui 5 is 6.0, 7.0 and emui 8 is 8.0 so its possible to retrieve but i think apps were creating problem so its your choice what to do.
Azan Mughal said:
I have not tried yet to retrieve data from emui 5 to emui 8 but you know about Android versions emui 5 is 6.0, 7.0 and emui 8 is 8.0 so its possible to retrieve but i think apps were creating problem so its your choice what to do.
Click to expand...
Click to collapse
OK, thanks
I will test it and tell you if all is well.
thank you for your work.
Azan Mughal said:
Coming Soon Every thing work and Now tell about it after view whats we need more.
You can unlock frp with this recovery and backup of frp
And backup every partition.
Click to expand...
Click to collapse
When you are releasing the new version? I am waiting to install because I tried the V2 but it is not working phone and FAILS to install.
LINK is Here.
Download the file extract the Folder and Go to fastboot mode and double click on TWRP.bat file and you have successfully installed TWRP.
https://drive.google.com/file/d/1DkU-2c4qCm_cGzr-aaDFoFEn0YlLl6fh/view?usp=drivesdk
If anyone like my work can donate. :good:
Azan Mughal said:
Download the file extract the Folder and Go to fastboot mode and double click on TWRP.bat file and you have successfully installed TWRP.
https://drive.google.com/file/d/1DkU-2c4qCm_cGzr-aaDFoFEn0YlLl6fh/view?usp=drivesdk
If anyone like my work can donate. :good:
Click to expand...
Click to collapse
The link is only accessible by your own account. Kindly share a proper link or provide access individually bcoz I already sent you a permission request.
Download Message:
Sorry, this file is infected with a virus
Only the owner is allowed to download infected files.
Somehow managed to download it...
Thank you
Just wanted to write a report on the successful flashing Oukitel WP5 (version 4/32 Gb) with Mediatek MT6761 + PowerVR Rogue GE8300
I have used instructions in this thread with some modification.
disclaimer (short version): Do not do any of the following unless you are prepared to lose your warranty or brick your phone. Everything that you do with your phone is at your own risk, and no one but you is responsible for it.
For flashing i used adb and fastboot. In Debian 10 it's easy to install:
sudo apt install adb fastboot
How to do that in other systems you my read on this forum or do some googling.
System image from phh's you can download here. I have used system-quack-arm64-ab-floss.img.xz image.
The steps of the procedure are almost the same as for WP6, except for one important point:
1. Battery must be charged. Unlock the bootloader as usual (developer options - enable USB debugging and OEM unlock). Connect phone to computer with USB cable
2. Type:
adb devices
ADB should now detect your device, and a request for access will pop up on your phone asking to allow permission. Allow it.
Next type:
adb reboot bootloader
The phone will reboot into fastboot mode, wait a few seconds until "fastboot mode" is shown on the bottom left of your phone's screen.
Next type:
fastboot devices
Fastboot should detect your device
Next type:
fastboot flashing unlock
Fastboot and your phone will ask you to confirm that you want to unlock your bootloader, confirm it using the volume buttons on your phone according to the instructions on your phones screen.
After the bootloader has unlocked successfully you need to format your device, type:
fastboot erase userdata
You'll receive a confirmation that data has been formatted.
Type:
fastboot erase system
You'll receive a confirmation that system has been formatted.
3. Next, you need to disable protection from booting non-factory firmware or whatever it is called - let the experts correct me. For that i flashed vbmeta partition with blank one (see attached file):
fastboot flash vbmeta vbmeta-blank.img
This is important step! If you do not do that - you will get phone infinity cycle trying to boot and rebooting
4. Final step, flashing the system image, that you have previously download and unpack:
fastboot flash system system-quack-arm64-ab-floss.img
and reboot after process is finished:
fastboot reboot
P.S. After booting everything works like a Swiss watch
I note that there is an AOSP 11 available since a few days. Any reason to avoid trying that on my WP5?
https://github.com/phhusson/treble_experimentations/releases/download/v302/system-roar-arm64-ab-floss.img.xz
I have tried AOSP 11 on Oukitel WP6 - it was slow (compared to AOSP 10) and, as i remember, on AOSP 11 does not worked some applications, that i need.
But you can try it yourself. Since there was several new releases - may be something was improved.
I went ahead and installed phh's AOSP 11 ndklite vanilla on my WP5 and it all seems to work ok. I'm confused at having superuser preinstalled and unsure how that affects trying to install magisk. but anyhow, for anyone wondering, it worked.
I'm kind of confused by the AOSP install. I wanted to change /system/etc/hosts but it is RO and can't be mounted RW despite superuser root. Online searches suggest I need magisk with systemless enabled. however unlike playing with the stock rom, i can't figure out how to get my boot.img to patch. i thought i'd find it in the AOSP image file but I can't locate it. I thought I could perhaps us SP flashtool to readback, but I don't have the scatter file, unless it's the same as stock. Perhaps the boot.img is the same as stock. I'm out of my depth.
gringobenuk said:
I'm kind of confused by the AOSP install. I wanted to change /system/etc/hosts but it is RO and can't be mounted RW despite superuser root. Online searches suggest I need magisk with systemless enabled. however unlike playing with the stock rom, i can't figure out how to get my boot.img to patch. i thought i'd find it in the AOSP image file but I can't locate it. I thought I could perhaps us SP flashtool to readback, but I don't have the scatter file, unless it's the same as stock. Perhaps the boot.img is the same as stock. I'm out of my depth.
Click to expand...
Click to collapse
.
The thumb rule of applies to all operating systems. DON'T use them, if you can't control them. Meaning, if you have no root control and firewall for what goes in and out. How do you know what's going on in the background?. My point is... Using a system you are rooted in and can control, rather than using the latest Bling Bling systems, for the sake of trend ore popularity. You should use an older proven and rooted system....
I guess your curiosity and search for knowledge is the reason why you hang out here with us at XDA.
XDA is the epicenter of public knolitsh for smartphones and technology...
Millions of brains combined into a singularity for problem solving and solutions...
.
Took me the better part of a day to figure all this out, but I've finally got phh's A11 GSI running on my 3GB model. I've added a brief guide at https://github.com/adil192/OukitelWP5TrebleTips/ if anyone with this phone stumbles across this in the future.
Risbele94 said:
I've added a brief guide at https://github.com/adil192/OukitelWP5TrebleTips/ if anyone with this phone stumbles across this in the future.
Click to expand...
Click to collapse
I have WP5 3 GiB RAM model and flashing ARM32 images ( like mentioned on this site: system-roar-arm32_binder64-ab-vndklite-gapps.img ) results in a boot stuck.
ARM64 images (AOSP9, AOSP10, ...) works.
I can confirm - with Android 10 stock firmware from https://oukitel.com/pages/download-center phone constantly restarts itself. (I wrote about this to Oukitel but appears that they don't give a sh*t...)
Why sometimes *.img uploading speed is ~20 MB/s :
>fastboot flash system system-roar-arm32_binder64-ab-vndklite-gapps.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/15 (131060 KB) OKAY [ 6.349s]
Writing 'system' OKAY [ 1.811s]
Sending sparse 'system' 2/15 (131048 KB) OKAY [ 6.309s]
Writing 'system' OKAY [ 1.794s]
Sending sparse 'system' 3/15 (131068 KB) OKAY [ 6.299s]
Writing 'system' OKAY [ 1.788s]
[...]
and another time only ~3 MB/s ?
>fastboot flash system system-roar-arm64-ab-gapps.img
Sending sparse 'system' 1/18 (131068 KB) OKAY [ 42.548s]
Writing 'system' OKAY [ 1.799s]
Sending sparse 'system' 2/18 (131068 KB) OKAY [ 42.618s]
Writing 'system' OKAY [ 1.821s]
Sending sparse 'system' 3/18 (131068 KB) OKAY [ 42.647s]
Writing 'system' OKAY [ 1.824s]
[...]