Database Info

Back to Stockrom (Recovery/System) Mediapad X2 703L

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

[GUIDE][FIX] Bricklooping Lettuce (YU Yuphoria) , No IMEI , Corrupt EFS

Hello Good People !!!
So yesterday,I encountered a brickloop on my lettuce and after around 10 hours of trying almost all methods,I was finally able to solve it.Though,mainly I was able to try all these as I had already got my replacement request from Amazon approved...
For those who don't know,brickloop is a situation when the device bootloops just after the YU logo and this bootloop isn't resolved even after factory image flash or any other ROM flash .
I cannot guarantee that this will work for everyone. However It has proven to be a solution for almost everyone that have used it. So if it does not work I ask that you be respectful in posting as such.
I am making a package for you to download which contains all files needed to make this happen (You need three more files,modemst1.img and modemst2.img and latest CM nightly but I am not going to give you those as I don't want everyone to have my IMEI on their lettuce . Though I will definitely tell you how to get those two files.) Download the package here :- https://www.androidfilehost.com/?fid=24052804347796818
So inside it you will have these files:
persist.img
adb 1.0.32
INSTRUCTIONS :-
Please note that any commands run in fastboot mode require you to have an unlocked boot loader. If you are not sure if you are unlocked then that means you aren't! So to unlock the bootloader,follow this guide :- http://forums.yuplaygod.com/threads/official-how-to-unlock-bootloader-on-the-yu-yuphoria.13785/
Step 1 :- You need to have proper adb/fastboot drivers installed.If you have unlocked bootloader ever or did so by the above guide,you already have these drivers with you.Else,use this guide to get drivers working :- http://forums.yuplaygod.com/threads...-drivers-pack-drivers-for-adb-fastboot.15025/ After you have made the drivers to work,continue to the next step.If you have issues in making drivers work,tag me in the thread and I will try my best to help you out.
Step 2 :- Extract the downloaded Zip on the Desktop .
Step 3 :- Open the adb1032 folder extracted on the desktop and put the latest CM nightly,modemst1.img and modemsr2.img inside it.Open Command Window by pressing Shift Key + Right click anywhere inside the folder and then selecting Open Command Window here.Boot your phone to fastboot mode.
Step 4 :- Now type the following command inside the Command Window or just copy-paste it :-
Code:
fastboot -i 0x2A96 erase persist
Wait for the process to complete (Should take less than 5 seconds).
Step 5 :- Type the following command inside the Command Window or just copy-paste it :-
Code:
fastboot -i 0x2A96 flash persist persist.img
Wait for the process to complete (Should take less than 5 seconds).
Step 6 :- (In most cases,the issue is solved in the Step 5 only.But still I recommend following all these steps.If you,by any chance,don't have modemst1.img and modemst2.img with you,DIRECTLY SKIP TO STEP 7) Type the following commands one by one :-
Code:
fastboot -i 0x2A96 erase modemst1
Code:
fastboot -i 0x2A96 erase modemst2
Code:
fastboot -i 0x2A96 flash modemst1 modemst1.img
Code:
fastboot -i 0x2A96 flash modemst2 modemst2.img
Step 7 :- If you don't have TWRP flashed,flash it from this thread :- http://forums.yuplaygod.com/threads/recovery-twrp-2-8-7-0-for-yu-yuphoria-01-08-15.13974/
Step 8 :- DON'T DO fastboot -i 0x2A96 reboot BUT instead remove the battery and then put it again and boot to recovery by pressing Power+Vol. Down button.
Step 9 :- Inside recovery,in the advanced folder,select ADB Sideload and select "Wipe Dalvik Cache" and "Cache" and swipe to start ADB Sideload.
Step 10 :- In the command window on your pc,type (Replace xxx with the correct Nightly name ) :-
Code:
adb sideload cm-xx-xxxxxxxx-NIGHTLY-lettuce.zip
Wait for the nightly to flash.
Step 11 :- From inside the recovery,reboot to system.
Your phone will be back now ....... Yayyyyy !!!!
And yeah,how to get modemst1.img and modemst2.img :-
Step 1 :- Download this app on your phone :- https://play.google.com/store/apps/details?id=ma.wanam.partitions
Step 2 :- Grant root access and in the settings,select storage to external sdcard and backup format to .img .
Step 3 :- Backup all partitions by selecting them and pressing a download like button at the bottom right . (Though we need to backup only modemst1 and modemst2 but I recommend you to backup all ... But yeah,first backup modemst1 and modemst2 and then backup others.The main reason I was able to restore my phone was because I had backup of all partitions,)
Step 4 :- In your external sdcard,find the modemst1.img and modemst2.img and save them inside the specified folder and also at as many secure places as you can so that these files never get lost.)
Please Note :- Most of the times,even a corrupt EFS is solved just by erasing and flashing persist.So don't worry much if you forgot to take its backup.Also,sometimes,a brickloop might be caused due to any other partition getting corrupted and that too can be solved but that is very rare.If this guide doesn't help in solving brickloop,tag me here,and I will help you out.

Reserved to improve the look of the post ... And also my story of how I arrived to this solution ..
And teaser : Another great guide coming soon ...

im having a weird situation here....i flashed aicp rom it bootlooped...then i restored my twrp backup of stock...its also stuck at boot animation......can you help me out..

sdnavale said:
im having a weird situation here....i flashed aicp rom it bootlooped...then i restored my twrp backup of stock...its also stuck at boot animation......can you help me out..
Click to expand...
Click to collapse
here you go bro.

Hi.. I'm new to Snapdragon chipsets..
Can I know what are these images for: persist.img, modemst1.img and modemst2.img
I mean, what are these partitions used for?

GokulNC said:
Hi.. I'm new to Snapdragon chipsets..
Can I know what are these images for: persist.img, modemst1.img and modemst2.img
I mean, what are these partitions used for?
Click to expand...
Click to collapse
These store the IMEI of your phone and some more important stuff... But IMEI is the most important of those...
Sent from my YU5010 using Tapatalk

@Naman Bhalla can u make a guide for hardbrick also? If you can?
Sent from my YU5010 using Tapatalk

Code:
target reported max download size of 268435456 bytes
sending 'persist' (32768 KB)...
OKAY [ 1.034s]
writing 'persist'...
FAILED (remote: flash write failure)
finished. total time: 1.430s
i get this error
Bootloader UNLOCKED Successfully though

Zeehan said:
i get this error
Bootloader UNLOCKED Successfully though
Click to expand...
Click to collapse
Restart into bootloader and then see , if it works

Same Error
TheDemon12 said:
Restart into bootloader and then see , if it works
Click to expand...
Click to collapse
Hi Pal,
I tried restarting into the bootloader as well and am still getting the same error!! Please help!

Step 4 :- Now type the following command inside the Command Window or just copy-paste it :-
Code:
fastboot -i 0x2A96 erase persist
Wait for the process to complete (Should take less than 5 seconds).
Step 5 :- Type the following command inside the Command Window or just copy-paste it :-
Code:
fastboot -i 0x2A96 flash persist persist.img
Wait for the process to complete (Should take less than 5 seconds).
Click to expand...
Click to collapse
I encountered
FAILED (remote:flash write failure)

xmertrans said:
I encountered
FAILED (remote:flash write failure)
Click to expand...
Click to collapse
Looks like partitions are corrupt.

Naman Bhalla said:
Looks like partitions are corrupt.
Click to expand...
Click to collapse
Yes I tried formatting with help of twrp it showed format successful but still twrp showed memory as 0mb

Code:
C:\adb>fastboot -i 0x2a96 erase modemst1
erasing 'modemst1'...
FAILED (remote: failed to erase partition
)
finished. total time: 0.034s
I am getting this error while erasing the modemst partitions. Can I continue with the flashing the modemst partitions directly?

Naman Bhalla said:
Looks like partitions are corrupt.
Click to expand...
Click to collapse
Is there a way to correct the partitions?

"FAILED (remote: flash write failure)"
When I try to flash persist, using the following command -
fastboot -i 0x2A96 flash persist persist.img
I get the error -
"FAILED (remote: flash write failure)"
Please help !

@Naman Bhalla,
I knew you from the OnePlus forums unbrick tool for 1+3.
I loved your work and it really saved my ass a lots of time.
I hope you're the same person and I Thank you very much
For that tool.
Coming to Lettuce,
I have installed this ROM: https://forum.xda-developers.com/yu-yuphoria/general/rom-lineage-os-14-1-lettuce20170108-t3538332
And suddenly my phone got blank. I can't access anything..
And all I can see is a ? icon what ever I restart the phone to, every reboot to bootloader/ recovery or even when connected to PC.. it's just the battery icon. The device is not even detected as any type of device in PC.
I tried the emmc dump method using first 200MB dumb, no luck there.
Can you provide me any other method to make my phone work again?
Please help me..

@Naman Bhalla
Hi my YU Yuphoria 5010 started acting up since last week ,when i noticed that the phone was restarting randomly and the settings was missing and even if i clicked on the settings logo in the notification panel, nothing would happen .So i decided to flash a Cusstom ROM instead and boot into recovery.While trying to wipe cache,dalvik and data I got an error message "uable to mount data,cache ,system(invalid argument) and internal memory* was showing up as 0.So i thought my phone was bricked and tried reviving it with the sd card method.But everything else except for system flashed , and got an error FAILED (remote: flash write failure ) just for system .Anyway now I could boot into recovery using fastboot boot command and the internal memory started showing up correcty. The fastboot command is the only way i could get into recovery, if i try power+volume down it would just come up with the empty battery logo. After this i installed qualcomm drivers and manually changed the driver to Qualcomm HS-USB QD Loader 9008 and tried flashing through QFil with a flashable stock ROM and ended up with the error message:"Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol** at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)** at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail".
*
But after going through some of your posts I found that my phone might not be bricked in the first place.My device just shows up as 'Android' under Other devices in Device Manager.
The following are the details from device manager.
Device type: Other devices
Manufacturer: Unknown
Location Port_#002.Hub_#003
Problem code : 0000001C
Physical Device Object name: \Device\USBPDO-6
Hardware IDS: USB\VID_2A96&PID_300A&REV_0100
************************ USB\VID_2A96&PID_300A
{259abffc-50a7-47ce-af08-68c9a7d73366}[13]: 6.0
{6a3433f4-5626-40e8-a9b9-dbd9ecd2884b}[4]: <true>
{6a3433f4-5626-40e8-a9b9-dbd9ecd2884b}[6]: <true>
*
I also tried to restore through TWRP recovery using the back up my brother created on his YU 5010A to no success.Changing the file system type and back to ext4 also didnt help. I use a Windows 10 64bit Laptop.
What could I possibly do to revive my phone?Kindly help.
*

How can i find modem files as i dont have their backup?
Is their any way of getting volte on yuphoria 5010?

not working bro plz help

My Phone just rebooted and now loops at the android loading logo CM13

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

Unofficial twrp for Elephone u pro v3.2.1.0

{
"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:

[OOS13] IN2023_11_F.62 Patched boot.img

Hello guys !
F.62 update is rolling out on the OnePlus 8 Pro, and I managed to download the full OTA zip package through the OxygenOS Updater app.
I extracted the boot.img file thanks to the payload_dumper_go tool on this thread.
This post is inspired from this one from @bebop80 (thank you !) since it is very simple, and we love what is simple here
Steps :​> Make sure your device is a OnePlus 8 Pro running on IN2023_11_F.62 Official version, with an unlocked bootloader.
> Download _IN2023_11_F62-Patched.img from https://pilou.org/OxygenOS/IN2023_11_F.62/ and vbmeta.img below.
> Connect your device to your computer, and make sure it is recognized when typing adb devices
> Enter into fastboot mode using the command adb reboot fastboot
> flash the patched boot image using fastboot flash boot _IN2023_11_F62-Patched.img
> (Optionnal, recommended by Magisk) flash the vbmeta image using fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
> fastboot reboot
> Open magisk app (If not installed, install the apk located in your internal storage root) and hit Install then use the recommended method.
> Reboot, your device is rooted

thanks gor the share.
have you been able to install the update with inbuild updater "Local install"
for me it will fail at 27%, no matter what i updater i use( inbuild or updater apks from oneplus). downloaded update already 3 times... pretty strange

SchWeinSAuG said:
thanks gor the share.
have you been able to install the update with inbuild updater "Local install"
for me it will fail at 27%, no matter what i updater i use( inbuild or updater apks from oneplus). downloaded update already 3 times... pretty strange
Click to expand...
Click to collapse
I received the update through the phone settings, before Oxygen Updater app released it. I installed it without any issue. I was on IN2023_11_F.15 software version. That's strange it doesn't work for you ..
The only thing I can recommend is a factory reset, but I understand it's annoying

Great post (even though I don't own the Pro). I like the idea of having pre-patched images available instead of going through the whole process for every new phone (which can be time-consuming on some models).
Funnily enough, my Oneplus 8, with great zeal, tried to install this update but of course it failed since its for the wrong model

i get
fastboot: error: Failed to identify current slot
i tryed
fastboot getvar all
getvar:all FAILED (remote: 'unknown command')
Finished. Total time: 0.000s
later tryed again and i have slot a as active
fastboot --set-active=a
< waiting for any device >
Setting current slot to 'a' OKAY [ 0.009s]
Finished. Total time: 0.012s
fastboot flash boot patchedF62.img
fastboot: error: Failed to identify current slot
---
after some more trials i could flash it

how to get rid of the info at start - yellow status - phone is unlocked

Google pay is recognize the root.