[NOUGAT][RECOVERY] TWRP mod (COMPLETE BACKUP) - Honor 7X ROMs, Kernels, Recoveries, & Other Devel
{
"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"
}
Requirements:
Unlocked Honor 7x : See this [But don't flash twrp from anywhere else before backing up your device. Use twrpimgmount for backing it up first.]
Download:
TWRP Complete Backup
TWRP Img mount
Instructions:
Flash twrpimgmount.img through fastboot
Code:
fastboot flash recovery twrpimgmount.img
fastboot flash recovery2 twrpimgmount.img
Backup/restore and flash image functions are tested for system/vendor/product/version/cust/oeminfo/recovery/recovery2/boot rest of them are not tested by me but should work.
Note: It is suggested to make a complete backup in memory card before rooting your Honor 7x.
After backing up, flash TWRP Complete Backup
Join Telegram group if you are willing to test latest stuff
Credits:
Ported form Honor 6x : OP
Follow next:
1. Make Complete Backup using TWRP Img mount
2. Make Complete Backup using PC
XDA:DevDB Information
[NOUGAT]TWRP COMPLETE BACKUP, Tool/Utility for the Honor 7X
Contributors
Sudeep Duhoon, OldDroid, surdu_petru, xepeleato
Source Code: https://github.com/OpenKirin/android_device_honor_berlin
Version Information
Status: Testing
Created 2017-12-31
Last Updated 2018-03-17
For oreo : Go here
This work for BND-L24 US version?
crayonicle said:
This work for BND-L24 US version?
Click to expand...
Click to collapse
It should
Sent from my BND-AL10 using Tapatalk
Sudeep Duhoon said:
It should
Sent from my BND-AL10 using Tapatalk
Click to expand...
Click to collapse
Confirmed working for BND-L24
It works!!
How can i restore the original Recovery? (so I can update the phone)
Thanks!
lowspeed said:
How can i restore the original Recovery? (so I can update the phone)
Thanks!
Click to expand...
Click to collapse
Here is the OPs reply to me in another thread.
Sudeep Duhoon said:
No it won't, it'll backup twrp recovery instead
But you can get stock recoveries from here
https://forum.xda-developers.com/devdb/project/?id=23956#downloads
Click to expand...
Click to collapse
update fails after restoring stock recovery. Weird.
Also the directories still seems to be encrypted after flashing this TWRP. Any trick i'm missing?
lowspeed said:
update fails after restoring stock recovery. Weird.
Also the directories still seems to be encrypted after flashing this TWRP. Any trick i'm missing?
Click to expand...
Click to collapse
Flash system and boot through fastboot to update.
This recovery don't auto decrypt data.
Sent from my BND-AL10 using Tapatalk
Sudeep Duhoon said:
Flash system and boot through fastboot to update.
This recovery don't auto decrypt data.
Sent from my BND-AL10 using Tapatalk
Click to expand...
Click to collapse
Got directions? The update.zip I know where to get but what do I do with it? (I only know how to use recovery to flash it)
Sudeep Duhoon said:
Flash system and boot through fastboot to update.
This recovery don't auto decrypt data.
Sent from my BND-AL10 using Tapatalk
Click to expand...
Click to collapse
only available files in the update.zip is this: No system.img
-a---- 12/5/2017 6:32 PM 15519744 BOOT.img
-a---- 1/3/2018 10:53 AM 98 BOOT.img.header
-a---- 12/5/2017 6:32 PM 13666 CRC.img
-a---- 1/3/2018 10:53 AM 98 CRC.img.header
-a---- 12/5/2017 6:32 PM 15 CURVER.img
-a---- 1/3/2018 10:53 AM 98 CURVER.img.header
-a---- 12/5/2017 6:32 PM 16035840 DTS.img
-a---- 1/3/2018 10:53 AM 98 DTS.img.header
-a---- 12/5/2017 6:32 PM 17408 EFI.img
-a---- 1/3/2018 10:53 AM 98 EFI.img.header
-a---- 12/5/2017 6:32 PM 2702912 FASTBOOT.img
-a---- 1/3/2018 10:53 AM 98 FASTBOOT.img.header
-a---- 12/5/2017 6:32 PM 3346688 FW_HIFI.img
-a---- 1/3/2018 10:53 AM 98 FW_HIFI.img.header
-a---- 12/5/2017 6:32 PM 168064 FW_LPM3.img
-a---- 1/3/2018 10:53 AM 98 FW_LPM3.img.header
-a---- 12/5/2017 6:32 PM 6688492 MODEMNVM_UPDATE.img
-a---- 1/3/2018 10:53 AM 98 MODEMNVM_UPDATE.img.header
-a---- 12/5/2017 6:32 PM 100663296 MODEM_FW.img
-a---- 1/3/2018 10:53 AM 98 MODEM_FW.img.header
-a---- 12/5/2017 6:32 PM 14 PACKAGE_TYPE.img
-a---- 1/3/2018 10:53 AM 98 PACKAGE_TYPE.img.header
-a---- 12/5/2017 6:32 PM 37165056 RECOVERY.img
-a---- 1/3/2018 10:53 AM 98 RECOVERY.img.header
-a---- 12/5/2017 6:32 PM 37165056 RECOVERY2.img
-a---- 1/3/2018 10:53 AM 98 RECOVERY2.img.header
-a---- 12/5/2017 6:32 PM 778304 SENSORHUB.img
-a---- 1/3/2018 10:53 AM 98 SENSORHUB.img.header
-a---- 12/5/2017 6:32 PM 256 SHA256RSA.img
-a---- 1/3/2018 10:53 AM 98 SHA256RSA.img.header
-a---- 12/5/2017 6:32 PM 3085696 TEEOS.img
-a---- 1/3/2018 10:53 AM 98 TEEOS.img.header
-a---- 12/5/2017 6:32 PM 109568 TRUSTFIRMWARE.img
-a---- 1/3/2018 10:53 AM 98 TRUSTFIRMWARE.img.header
-a---- 12/5/2017 6:32 PM 1136 VERLIST.img
-a---- 1/3/2018 10:53 AM 98 VERLIST.img.header
-a---- 12/5/2017 6:32 PM 69184 XLOADER.img
-a---- 1/3/2018 10:53 AM 98 XLOADER.img.header
lowspeed said:
only available files in the update.zip is this: No system.img
-a---- 12/5/2017 6:32 PM 15519744 BOOT.img
-a---- 1/3/2018 10:53 AM 98 BOOT.img.header
-a---- 12/5/2017 6:32 PM 13666 CRC.img
-a---- 1/3/2018 10:53 AM 98 CRC.img.header
-a---- 12/5/2017 6:32 PM 15 CURVER.img
-a---- 1/3/2018 10:53 AM 98 CURVER.img.header
-a---- 12/5/2017 6:32 PM 16035840 DTS.img
-a---- 1/3/2018 10:53 AM 98 DTS.img.header
-a---- 12/5/2017 6:32 PM 17408 EFI.img
-a---- 1/3/2018 10:53 AM 98 EFI.img.header
-a---- 12/5/2017 6:32 PM 2702912 FASTBOOT.img
-a---- 1/3/2018 10:53 AM 98 FASTBOOT.img.header
-a---- 12/5/2017 6:32 PM 3346688 FW_HIFI.img
-a---- 1/3/2018 10:53 AM 98 FW_HIFI.img.header
-a---- 12/5/2017 6:32 PM 168064 FW_LPM3.img
-a---- 1/3/2018 10:53 AM 98 FW_LPM3.img.header
-a---- 12/5/2017 6:32 PM 6688492 MODEMNVM_UPDATE.img
-a---- 1/3/2018 10:53 AM 98 MODEMNVM_UPDATE.img.header
-a---- 12/5/2017 6:32 PM 100663296 MODEM_FW.img
-a---- 1/3/2018 10:53 AM 98 MODEM_FW.img.header
-a---- 12/5/2017 6:32 PM 14 PACKAGE_TYPE.img
-a---- 1/3/2018 10:53 AM 98 PACKAGE_TYPE.img.header
-a---- 12/5/2017 6:32 PM 37165056 RECOVERY.img
-a---- 1/3/2018 10:53 AM 98 RECOVERY.img.header
-a---- 12/5/2017 6:32 PM 37165056 RECOVERY2.img
-a---- 1/3/2018 10:53 AM 98 RECOVERY2.img.header
-a---- 12/5/2017 6:32 PM 778304 SENSORHUB.img
-a---- 1/3/2018 10:53 AM 98 SENSORHUB.img.header
-a---- 12/5/2017 6:32 PM 256 SHA256RSA.img
-a---- 1/3/2018 10:53 AM 98 SHA256RSA.img.header
-a---- 12/5/2017 6:32 PM 3085696 TEEOS.img
-a---- 1/3/2018 10:53 AM 98 TEEOS.img.header
-a---- 12/5/2017 6:32 PM 109568 TRUSTFIRMWARE.img
-a---- 1/3/2018 10:53 AM 98 TRUSTFIRMWARE.img.header
-a---- 12/5/2017 6:32 PM 1136 VERLIST.img
-a---- 1/3/2018 10:53 AM 98 VERLIST.img.header
-a---- 12/5/2017 6:32 PM 69184 XLOADER.img
-a---- 1/3/2018 10:53 AM 98 XLOADER.img.header
Click to expand...
Click to collapse
You need a Full Firmware Package.
But there is no for L21 and L24,must wait until there is one
skippotter said:
Confirmed working for BND-L24
Click to expand...
Click to collapse
I updated to the latest version "BND-L24C567B130" do you think I can still continue with this method?
Sudeep Duhoon said:
Flash system and boot through fastboot to update.
This recovery don't auto decrypt data.
Click to expand...
Click to collapse
Can you please explain on video or YouTube
I am a new users of Android
tootysa said:
Can you please explain on video or YouTube
I am a new users of Android
Click to expand...
Click to collapse
You shouldn't be doing this if you're a new user then
Cringing said:
I updated to the latest version "BND-L24C567B130" do you think I can still continue with this method?
Click to expand...
Click to collapse
Yes. You can.
Sent from my iPhone using Tapatalk
ahmad.o said:
You shouldn't be doing this if you're a new user then
Click to expand...
Click to collapse
Really ?
Would someone with a working BND-L21 be kind enough to upload a twrp backup?
With no full ota being out, it'd help alot with the unbricking, gapps, etc. situation.... thanks
Is anyone can help me
How to mount back internal storage in honor 7x I lost it something I do wrong ??
I m not able to install zip files from internal and external storage
Or tell me about full stock flash
Please please help me devs
Related
I Need a BIG help to root my device
So I tried EVERYTHING to root my Sony Tablet and nothing! When I type "adb devices" in ADB Command Prompt it just says List of Devices Attached and nothing more! It doesn't show my tablet. The Windows is not recognizing the Sony_Tablet (debug mode) but just the MTP I tried to install de .inf file (Android Composite ADB Interface) to make it work but the Windows simply didn't let me! It says "The hash for the file is not present in the specified catalog file" Please help me I'm going nuts here!!!
same here -- hash file not present/tampered What version of Android and what version of Windows are you running? I am running Win8 RP. I just loaded the Android ADK (4.1). Trying to connect to a kindle fire: For "Android Composite ADB Interface" I get and error: "the hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering." I am running X64 cat file signature: from 6/23 C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver Thumbprint from androidwinusb86.cat 06 c9 2b ec 3b bf 32 06 8c b9 20 85 63 d0 04 16 94 48 ee 21 androidwinusba64.cat 8f d9 9d 63 fb 3a fb d5 34 a4 f6 e3 1d ac d2 7f 59 50 40 21 Files: Directory of C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver 06/30/2012 11:11 AM <DIR> . 06/30/2012 11:11 AM <DIR> .. 06/30/2012 10:42 AM <DIR> amd64 06/30/2012 10:42 AM 9,239 androidwinusb86.cat 06/30/2012 10:42 AM 9,275 androidwinusba64.cat 06/30/2012 11:11 AM 4,540 android_winusb.inf 06/30/2012 10:42 AM <DIR> i386 06/30/2012 10:42 AM 16,514 source.properties 4 File(s) 39,568 bytes Directory of C:\Program Files (x86)\Android\android-sdk\extras\google\usb_drive r\amd64 06/30/2012 10:42 AM <DIR> . 06/30/2012 10:42 AM <DIR> .. 06/30/2012 10:42 AM 236 NOTICE.txt 06/30/2012 10:42 AM 1,721,576 WdfCoInstaller01009.dll 06/30/2012 10:42 AM 1,002,728 winusbcoinstaller2.dll 06/30/2012 10:42 AM 2,152,176 WUDFUpdate_01009.dll 4 File(s) 4,876,716 bytes Directory of C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver\i386 06/30/2012 10:42 AM <DIR> . 06/30/2012 10:42 AM <DIR> .. 06/30/2012 10:42 AM 236 NOTICE.txt 06/30/2012 10:42 AM 1,461,992 WdfCoInstaller01009.dll 06/30/2012 10:42 AM 851,176 winusbcoinstaller2.dll 06/30/2012 10:42 AM 1,837,296 WUDFUpdate_01009.dll 4 File(s) 4,150,700 bytes Total Files Listed: 12 File(s) 9,066,984 bytes 8 Dir(s) 9,815,154,688 bytes free
Dont use windows 8. Use Win XP only! Use the driver found here: http://forum.xda-developers.com/showthread.php?t=1488822. (credits to BlueChipJ). Open the file android_winusb.inf. Look for the two sections called ";SONY Sony Tablet S" and remove " " from "%CompositeAdbInterface%". It should now look like this: ;SONY Sony Tablet S %CompositeAdbInterface% = USB_Install, USB\VID_054C&PID_05B4&MI_01 Save the file. Use the driver installer provided. Connect the device and try the adb which is provided with the driver. It's best to try this on a fresh computer which doesnt have the adb drivers. If i have helped you, click the thanks button!
[Q] 1.0.1-4ubuntu5.3 for lib was not found error
Guys am getting this error.. i was trying to set up build environment on Ubuntu 12.04 LTS using this guide http://forum.xda-developers.com/showpost.php?p=30958867&postcount=1 screenshot: https://www.dropbox.com/s/wiz9al02oyxx4xm/ubuntu_tes.png
When i install OpenSSL I just type Code: sudo apt-get install openssl ---------- Post added at 10:22 AM ---------- Previous post was at 10:20 AM ---------- By the way, if you want something much more in depth, check this link
matt95 said: When i install OpenSSL I just type Code: sudo apt-get install openssl ---------- Post added at 10:22 AM ---------- Previous post was at 10:20 AM ---------- By the way, if you want something much more in depth, check this link Click to expand... Click to collapse Sorry mate. Getting the same error. I did what u said..it has been installed. Even I installed openssl from source. But when I type that command stated in the guide I get the same error @matt95 Am going to try your method tomorrow. . Sent from my GT-I9100 using Tapatalk 2
How to unpack and repack Oreo ROM?
I am trying to add a few things into system.img for a Chuwi H9Air. It is an MTK MT6797 chip. I download the firmware and it has the following files: 04/08/2018 04:45 PM 146,026 APDB_MT6797_S01_alps-trunk-o0.tk_W17.45 06/04/2018 11:43 AM 10,298,256 boot.img 06/02/2018 08:23 PM 9,044,272 cache.img 04/02/2018 10:37 AM 2,333,509 DbgInfo_DSP_MT6797_MOLY_LR11_W1630_MD_MP_V67_2_2018_03_06_16_40_1_ulwctg_n 04/08/2018 04:09 PM 3,078,862 DbgInfo_LR11.W1630.MD.MP_TK_MD_BASIC_MOLY_LR11_W1630_MD_MP_V67_2_2018_04_02_17_52_1_ulwctg_n 06/02/2018 01:49 PM 418,240 lk.img 06/02/2018 01:49 PM 2,762,896 logo.bin 06/02/2018 01:53 PM 528 md1arm7.img 06/02/2018 01:53 PM 1,015,120 md1dsp.img 06/02/2018 01:53 PM 18,196,000 md1img.img 06/02/2018 01:53 PM 4,255,344 md3img.img 04/02/2018 10:37 AM 1,271,188 MDDB.C2K.META_MT6797_S00_SIXTH_CBP_MD_MP5_V72_2_3_3g_n.EDB 04/08/2018 04:09 PM 788,954 MDDB.META_MT6797_S00_MOLY_LR11_W1630_MD_MP_V67_2_1_ulwctg_n.EDB 04/08/2018 04:09 PM 61,806,498 MDDB_InfoCustomAppSrcP_MT6797_S00_MOLY_LR11_W1630_MD_MP_V67_2_1_ulwctg_n.EDB 06/02/2018 01:50 PM 14,119 MT6797_Android_scatter.txt 06/02/2018 03:20 PM 71,440 odmdtbo.img 06/02/2018 01:50 PM 189,528 preloader_x970_t10.bin 06/04/2018 11:43 AM 12,082,064 recovery.img 06/04/2018 11:40 AM 42,688 scp.img 06/27/2018 08:24 AM 1,846,269,976 system.img 06/04/2018 11:40 AM 90,112 tee.img 06/04/2018 11:44 AM 53,470,064 userdata.img 06/04/2018 11:44 AM 381,834,204 vendor.img I tried to use MTK_Extractor_V2.6.3 to unpack and repack system.img. Then I use SP_Flash_Tool_v5.1804_Win to flash it back. However, I got stuck at fast boot. It appears that Oreo and earlier has dm-verify. So I tried: Remove verified tag in the vendor.img at etc\fstab.mt6797 and remove the verity_key file in initrd of boot.img. This go into fastboot. Just remove verified tag in the vendor.img at etc\fstab.mt6797. This go into a boot loop. But I still see the same problem. Is there any suggestion on how to proceed? Thanks.
Do you have Oreo on your MTK6797 ? I just purchased a generic tablet said to have v8 on it, when it arrived it was 4.4 spoofed to show 8.0 now I need to upgrade at least to 5 to get my apps to run on it. I'm not familiar with the limitations can the MTK6797 run v8? is this rom specific to the MTK6797 or to the tablet hardware?
HD1925 OnePlus 7t Pro McLaren 5g - Crowdsourced Data Request.
ntzrmtthihu777 said: So, I've been doing some work on getting LineageOS to work on this device. No idea as of right now if it will work on any other carrier variants (I think they don't allow for bootloader unlocking?). Currently everything 'works' (some is buggy but that may be more to do with the fact that 17.1 is not currently finished) with the exception of two things I've tested/noticed (other stuff may be broken but I've not seen them yet): audio in calls (I can make/take calls but I can't hear or be heard. Audio works as I can play music in the LineageOS music app and record/playback the recording in the app) and the fingerprint sensor (pretty sure I'm just missing some part from the stock ROM). What I'm asking is that all owners of stock (unlocked/rooted is probably fine, custom kernels prob not) collect some logs for me during specific activities so I can determine what is missing and maybe produce a rom for you guys to test out without losing some features. I'd like three things: 1. Follow the instructions here and upload the oem_log folder to somewhere and share it. 2. A logcat of boot up through making a phone call and hang up. To take this, you'll need developer mode and adb debugging enabled on the phone and the platform tools (adb primarily) set up for your operating system. From either cmd.exe (windows) or Terminal.app (OSX) or your preferred terminal emulator (Linux, too many options to list them all), enter this command: Code: adb logcat > logcat.call.log Then, power your phone off, hook it up via USB to the machine, power it on, place the call, say a few words, hang up. Then press ctrl+c in the cmd/terminal/whatever window to end the logging session. 3. A logcat of boot up through enrolling a fingerprint in the phone and unlocking via the fingerprint. Same procedure, but the command is: Code: adb logcat > logcat.finger.log Optionally, for those with rooted phones, I'd like these logs as well: 4. A dmesg during boot up through making a call and hangup. Same procedure as #2, but the command is Code: adb shell su -c dmesg > dmesg.call.log 5. A dmesg during boot up through enrolling a fingerprint in the phone and unlocking via the fingerprint. Same procedure as #3 but the command is Code: adb shell su -c dmesg > dmesg.finger.log The files gathered from #2-5 will be in the current directory you executed the logcat command from. On windows it will say this right before where you type the command, and on OSX/Linux this will probably be in your home directory, unless you changed the directory first. I expect OSX or Linux users to be a bit more savvy about this already. The files may contain unique data to your phone (serial number, IMEI, other things) but android filters out all but the last two numbers of the phone you are calling, so its generally ok. However, I do not suggest posting links to these files here, but you can message me them directly here. If/when you do this, please make note of the exact model number of your phone (not sure if all 5g phones are HD1925 or not), current firmware version, and baseband version. These can all be found in settings->about phone or so. Click to expand... Click to collapse Hopefully we can get all this sorted out before too long and have working lineage builds quickly. Thanks in advance and happy hacking!
ntzrmtthihu777 said: So, I've been doing some work on getting LineageOS to work on this device. No idea as of right now if it will work on any other carrier variants (I think they don't allow for bootloader unlocking?). Currently everything 'works' (some is buggy but that may be more to do with the fact that 17.1 is not currently finished) with the exception of two things I've tested/noticed (other stuff may be broken but I've not seen them yet): audio in calls (I can make/take calls but I can't hear or be heard. Audio works as I can play music in the LineageOS music app and record/playback the recording in the app) and the fingerprint sensor (pretty sure I'm just missing some part from the stock ROM). What I'm asking is that all owners of stock (unlocked/rooted is probably fine, custom kernels prob not) collect some logs for me during specific activities so I can determine what is missing and maybe produce a rom for you guys to test out without losing some features. I'd like three things: 1. Follow the instructions here and upload the oem_log folder to somewhere and share it. 2. A logcat of boot up through making a phone call and hang up. To take this, you'll need developer mode and adb debugging enabled on the phone and the platform tools (adb primarily) set up for your operating system. From either cmd.exe (windows) or Terminal.app (OSX) or your preferred terminal emulator (Linux, too many options to list them all), enter this command: Then, power your phone off, hook it up via USB to the machine, power it on, place the call, say a few words, hang up. Then press ctrl+c in the cmd/terminal/whatever window to end the logging session. 3. A logcat of boot up through enrolling a fingerprint in the phone and unlocking via the fingerprint. Same procedure, but the command is: Optionally, for those with rooted phones, I'd like these logs as well: 4. A dmesg during boot up through making a call and hangup. Same procedure as #2, but the command is 5. A dmesg during boot up through enrolling a fingerprint in the phone and unlocking via the fingerprint. Same procedure as #3 but the command is The files gathered from #2-5 will be in the current directory you executed the logcat command from. On windows it will say this right before where you type the command, and on OSX/Linux this will probably be in your home directory, unless you changed the directory first. I expect OSX or Linux users to be a bit more savvy about this already. The files may contain unique data to your phone (serial number, IMEI, other things) but android filters out all but the last two numbers of the phone you are calling, so its generally ok. However, I do not suggest posting links to these files here, but you can message me them directly here. If/when you do this, please make note of the exact model number of your phone (not sure if all 5g phones are HD1925 or not), current firmware version, and baseband version. These can all be found in settings->about phone or so. Hopefully we can get all this sorted out before too long and have official lineage builds quickly. Thanks in advance and happy hacking! Click to expand... Click to collapse If I can get my hands on my laptop, I'll see if I can help out with this. Will PM you if I can manage it!
champ784 said: If I can get my hands on my laptop, I'll see if I can help out with this. Will PM you if I can manage it! Click to expand... Click to collapse Thanks much, would be quite helpful I think. its soo frikken close to being done and usable as a phone.
ntzrmtthihu777 said: Thanks much, would be quite helpful I think. its soo frikken close to being done and usable as a phone. Click to expand... Click to collapse Super excited but also worried as there is no proven way to restore to stock??
kirschdog1 said: Super excited but also worried as there is no proven way to restore to stock?? Click to expand... Click to collapse I don't know, as far as I can tell using the flash.zip in one of these threads did the trick for me, but as there is no ota to be taken I can't tell if that works or not.
kirschdog1 said: Super excited but also worried as there is no proven way to restore to stock?? Click to expand... Click to collapse You can use the msm tool to read back all partitions U will get the boot system vendor dtbo vbmeta,etc plus all bin files . just in case you screw up your 5g modem or lose your IMEI
twinnfamous said: You can use the msm tool to read back all partitions U will get the boot system vendor dtbo vbmeta,etc plus all bin files . just in case you screw up your 5g modem or lose your IMEI Click to expand... Click to collapse Explain.
ntzrmtthihu777 said: Explain. Click to expand... Click to collapse Open up msm tool and press f8 when the screen pops up use crtl+a to select all partitions the PW is oneplus then ok . Then press readback button .Power off phone and connect phone while holding both volume buttons to USB keep holding the buttons till it shows it's connected and readback will start and you should have all img files and bin files in C/
twinnfamous said: Open up msm tool and press f8 when the screen pops up use crtl+a to select all partitions the PW is oneplus then ok . Then press readback button .Power off phone and connect phone while holding both volume buttons to USB keep holding the buttons till it shows it's connected and readback will start and you should have all img files and bin files in C/ Click to expand... Click to collapse This would require the MSM tool specific to this device, would it not? If it doesn't, man, I need to get some folks to do this.
ntzrmtthihu777 said: This would require the MSM tool specific to this device, would it not? If it doesn't, man, I need to get some folks to do this. Click to expand... Click to collapse I've done it. But my bootloader is not unlocked and the OnePlus website says my IMEI is invalid. Use msm tool found in this forum. I used the one from my op7pro. This is something alot should have tried just from owning previous oneplus devices
ntzrmtthihu777 said: This would require the MSM tool specific to this device, would it not? If it doesn't, man, I need to get some folks to do this. Click to expand... Click to collapse I did mine already but my bootloader is still locked too invalid imei
twinnfamous said: Open up msm tool and press f8 when the screen pops up use crtl+a to select all partitions the PW is oneplus then ok . Then press readback button .Power off phone and connect phone while holding both volume buttons to USB keep holding the buttons till it shows it's connected and readback will start and you should have all img files and bin files in C/ Click to expand... Click to collapse There is no msm tool for the 5g McLaren... ?
kirschdog1 said: There is no msm tool for the 5g McLaren... ? Click to expand... Click to collapse Read a couple Posts before. There is msm tool in this forum that will work to read back from phone. https://forum-xda--developers-com.c...3A%2F%2Fwww.google.com&_tf=From%20%251%24s
@ntzrmtthihu777 Thank you very much for continuing to work on developing for this phone! Just sent you a PM with the logcats for the calls and fingerprint, oem_log, and screenshots of phone information. Please let me know if there is more I can help with
a63548 said: @ntzrmtthihu777 Thank you very much for continuing to work on developing for this phone! Just sent you a PM with the logcats for the calls and fingerprint, oem_log, and screenshots of phone information. Please let me know if there is more I can help with Click to expand... Click to collapse Is it within your wheelhouse to try the readback the previous poster in this thread mentioned? Shouldn't require the bootloader unlock, and you'd have the most virgin dump to provide to the rest of us for the moment.
twinnfamous said: Open up msm tool and press f8 when the screen pops up use crtl+a to select all partitions the PW is oneplus then ok . Then press readback button .Power off phone and connect phone while holding both volume buttons to USB keep holding the buttons till it shows it's connected and readback will start and you should have all img files and bin files in C/ Click to expand... Click to collapse The MSM tool is asking for a password? Edit: Nevermind the password is oneplus
ntzrmtthihu777 said:
Is it within your wheelhouse to try the readback the previous poster in this thread mentioned?
Shouldn't require the bootloader unlock, and you'd have the most virgin dump to provide to the
rest of us for the moment.
Click to expand...
Click to collapse
Reading back the files as I type Are there any files/partitions I should keep out of the archive I will be uploading for here? I selected all of them, but for safety would prefer to leave out any that might not be good to put online.
Edit: Completed!
Total uncompressed size 19GB (mainly due to super.img) Compressed size is 3.9GB. Sending you a link through PM.
{
"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"
}
Code:
01/16/2020 03:43 AM <DIR> .
01/16/2020 03:43 AM <DIR> ..
01/16/2020 03:38 AM 8,388,608 abl.elf
01/16/2020 03:38 AM 67,108,864 aging.bin
01/16/2020 03:38 AM 33,554,432 aging_mod.bin
01/16/2020 03:38 AM 106,496 ALIGN_TO_128K_1.bin
01/16/2020 03:39 AM 106,496 ALIGN_TO_128K_2.bin
01/16/2020 03:38 AM 524,288 aop.mbn
01/16/2020 03:39 AM 262,144 apdp.mbn
01/16/2020 03:38 AM 100,663,296 boot.img
01/16/2020 03:38 AM 1,048,576 BTFM.bin
01/16/2020 03:39 AM 1,048,576 catecontentfv.bin
01/16/2020 03:39 AM 524,288 catefv.bin
01/16/2020 03:39 AM 2,097,152 cateloader.bin
01/16/2020 03:38 AM 131,072 cdt.bin
01/16/2020 03:38 AM 524,288 cmnlib.mbn
01/16/2020 03:38 AM 524,288 cmnlib64.mbn
01/16/2020 03:30 AM 524,288 config.bin
01/16/2020 03:38 AM 178,257,920 core_nhlos.bin
01/16/2020 03:38 AM 1,048,576 ddr.bin
01/16/2020 03:38 AM 131,072 devcfg.mbn
01/16/2020 03:39 AM 4,096 devinfo.bin
01/16/2020 03:39 AM 1,048,576 dip.bin
01/16/2020 03:38 AM 67,108,864 dspso.bin
01/16/2020 03:38 AM 25,165,824 dtbo.img
01/16/2020 03:30 AM 10,485,760 dynamic_nvbk.bin
01/16/2020 03:29 AM 524,288 frp.bin
01/16/2020 03:39 AM 131,072 fsc.bin
01/16/2020 03:39 AM 2,097,152 fsg.bin
01/16/2020 03:38 AM 2,097,152 fw_ufs1.bin
01/16/2020 03:38 AM 2,097,152 fw_ufs2.bin
01/16/2020 03:38 AM 2,097,152 fw_ufs3_a.bin
01/16/2020 03:38 AM 2,097,152 fw_ufs3_b.bin
01/16/2020 03:38 AM 2,097,152 fw_ufs4_a.bin
01/16/2020 03:38 AM 2,097,152 fw_ufs4_b.bin
01/16/2020 03:38 AM 2,097,152 fw_ufs5_a.bin
01/16/2020 03:38 AM 2,097,152 fw_ufs5_b.bin
01/16/2020 03:38 AM 20,480 gpt_backup0.bin
01/16/2020 03:38 AM 20,480 gpt_backup1.bin
01/16/2020 03:38 AM 20,480 gpt_backup2.bin
01/16/2020 03:38 AM 20,480 gpt_backup3.bin
01/16/2020 03:39 AM 20,480 gpt_backup4.bin
01/16/2020 03:39 AM 20,480 gpt_backup5.bin
01/16/2020 03:38 AM 24,576 gpt_main0.bin
01/16/2020 03:38 AM 24,576 gpt_main1.bin
01/16/2020 03:38 AM 24,576 gpt_main2.bin
01/16/2020 03:38 AM 24,576 gpt_main3.bin
01/16/2020 03:39 AM 24,576 gpt_main4.bin
01/16/2020 03:39 AM 24,576 gpt_main5.bin
01/16/2020 03:38 AM 8,388,608 hyp.mbn
01/16/2020 03:38 AM 2,097,152 imagefv.elf
01/16/2020 03:29 AM 524,288 keystore.bin
01/16/2020 03:38 AM 524,288 km4.mbn
01/16/2020 03:39 AM 4,096 limits.bin
01/16/2020 03:39 AM 67,108,864 logdump.bin
01/16/2020 03:39 AM 8,388,608 logfs_ufs_8mb.bin
01/16/2020 03:38 AM 16,777,216 logo.bin
01/16/2020 03:39 AM 1,048,576 mdm1m9kefs1.bin
01/16/2020 03:39 AM 1,048,576 mdm1m9kefs2.bin
01/16/2020 03:39 AM 1,048,576 mdm1m9kefs3.bin
01/16/2020 03:39 AM 4,096 mdm1m9kefsc.bin
01/16/2020 03:39 AM 1,048,576 mdm1oemnvbktmp.bin
01/16/2020 03:38 AM 1,048,576 mdmddr.bin
01/16/2020 03:30 AM 1,048,576 mdm_oem_dycnvbk.bin
01/16/2020 03:30 AM 1,048,576 mdm_oem_stanvbk.bin
01/16/2020 03:38 AM 4,194,304 mdtpsecapp_a.bin
01/16/2020 03:38 AM 4,194,304 mdtpsecapp_b.bin
01/16/2020 03:38 AM 33,554,432 mdtp_a.bin
01/16/2020 03:38 AM 33,554,432 mdtp_b.bin
01/16/2020 03:38 AM 16,777,216 metadata.img
01/16/2020 03:29 AM 1,048,576 misc.bin
01/16/2020 03:39 AM 2,097,152 modemst1.bin
01/16/2020 03:39 AM 2,097,152 modemst2.bin
01/16/2020 03:39 AM 262,144 msadp.mbn
01/16/2020 03:38 AM 32,768 multi_image.mbn
01/16/2020 03:38 AM 314,572,800 NON-HLOS.bin
01/16/2020 03:39 AM 314,572,800 op1.img
01/16/2020 03:30 AM 268,435,456 op2.img
01/16/2020 03:30 AM 1,717,989,376 opproduct_a.bin
01/16/2020 03:31 AM 1,717,989,376 opproduct_b.bin
01/16/2020 03:29 AM 1,048,576 param.bin
01/16/2020 03:29 AM 33,554,432 persist.img
01/16/2020 03:38 AM 81,920 qupv3fw.elf
01/16/2020 03:38 AM 134,217,728 rawdump.bin
01/16/2020 03:38 AM 100,663,296 recovery.img
01/16/2020 03:39 AM 8,290,304 reserve1.bin
01/16/2020 03:39 AM 16,580,608 reserve2.bin
01/16/2020 03:39 AM 16,580,608 reserve3.bin
01/16/2020 03:39 AM 16,580,608 reserve4.bin
01/16/2020 03:39 AM 28,672 sec.elf
01/16/2020 03:39 AM 34,226,176 splash.bin
01/16/2020 03:39 AM 8,388,608 spunvm.bin
01/16/2020 03:29 AM 8,192 ssd.bin
01/16/2020 03:30 AM 10,485,760 static_nvbk.bin
01/16/2020 03:39 AM 131,072 storsec.mbn
01/16/2020 03:37 AM 15,032,385,536 super.img
01/16/2020 03:39 AM 2,759 ToolLog.txt
01/16/2020 03:39 AM 1,048,576 toolsfv.bin
01/16/2020 03:38 AM 4,194,304 tz.mbn
01/16/2020 03:39 AM 524,288 uefivarstore.bin
01/16/2020 03:38 AM 2,097,152 uefi_sec.mbn
01/16/2020 03:38 AM 65,536 vbmeta.img
01/16/2020 03:38 AM 65,536 vbmeta_system.img
01/16/2020 03:38 AM 3,670,016 xbl.elf
01/16/2020 03:38 AM 131,072 xbl_config.elf
twinnfamous said: Read a couple Posts before. There is msm tool in this forum that will work to read back from phone. https://forum-xda--developers-com.c...3A%2F%2Fwww.google.com&_tf=From%20%251%24s Click to expand... Click to collapse I'm pretty sure that this will not work on the McLaren 5g edition but maybe Im wrong?? Has anyone with the McLaren edition 5g used this to restore?? Dan?
twinnfamous said: Read a couple Posts before. There is msm tool in this forum that will work to read back from phone. https://forum-xda--developers-com.c...3A%2F%2Fwww.google.com&_tf=From%20%251%24s Click to expand... Click to collapse Not for McLaren 5g!!
kirschdog1 said: Not for McLaren 5g!! Click to expand... Click to collapse Pretty sure in this case we are just using the MSM tool to make a backup/dump all of the partitions using the readback mode. I just did this successfully, and the phone is fine. Not sure, but I think using the MSM tool to restore/write anything would be where issues such as bricking would arise.
CPH1979 ROM Nuker
Just a simple batch script to go through and remove a list of useless or bloatware packages, and make sure to read "INSTRUCTIONS.txt" NOTE: THIS WILL ALSO REMOVE THE STOCK PHONE AND MESSAGING APPLICATIONS, THIS MEANS YOU WILL HAVE TO DOWNLOAD GOOGLES, OR A THIRD PARTIES MESSAGING AND PHONE APP! List of useless crap: com.coloros.backuprestore com.google.android.youtube com.coloros.phonenoareainquire com.coloros.gamespace com.oppo.operationManual com.oppo.partnerbrowsercustomizations com.android.htmlviewer com.coloros.weather.service com.google.ar.core com.coloros.oshare com.android.contacts com.android.mms com.dropboxchmod com.coloros.assistantscreen com.google.android.apps.tachyon com.mediatek.mdmlsample com.facebook.services com.google.android.music com.coloros.smartdriving com.google.android.apps.docs com.google.android.apps.maps com.coloros.wallpapers com.opera.browser com.coloros.weather2 com.android.chrome com.coloros.compass2 com.coloros.colorfilestand com.google.android.videos com.coloros.pictorial com.coloros.widget.smallweather com.coloros.calculator com.google.android.feedback com.google.android.apps.photos com.google.android.calendar com.facebook.katana com.coloros.alarmclock com.oppo.logkit com.facebook.system com.oppo.atlas com.oppo.music com.oppo.criticallog com.coloros.video com.google.android.keep com.coloros.soundrecorder com.oppo.quicksearchbox com.opera.preinstall com.facebook.appmanager com.coloros.floatassistant com.coloros.childrenspace com.mediatek.mtklogger com.google.android.apps.magazines com.coloros.musiclink com.nearme.atlas com.nearme.themestore com.google.android.gm com.coloros.phonemanager RELEASES: Version 2.7: https://drive.google.com/open?id=1DEPuKn85V-dCjHKdWMHRCuCn9wjBI8kV Version 2.8: https://drive.google.com/open?id=1Ork7Dvf6JaVP-JxvdqgzOaTrk-SNBvrv Version 2.9 https://drive.google.com/file/d/1PtbzD0ppUEqQ9_PEPjAZYxtlJ-yKDsSJ/view?usp=sharing
********
Why is gamespace useless? Also possible to delete some of them and not the list? ---------- Post added at 09:10 AM ---------- Previous post was at 08:23 AM ---------- Castorite said: <Mod edit: Quoted OP deleted> Click to expand... Click to collapse maybe you do know how downgrade firmware?
Predatorhaze said: Why is gamespace useless? Also possible to delete some of them and not the list? ---------- Post added at 09:10 AM ---------- Previous post was at 08:23 AM ---------- maybe you do know how downgrade firmware? Click to expand... Click to collapse I classified OPPO's Gamespace as "useless" because it was apart of the ColorOS Operating System, you can change what packages are removed by editing "CPH1979 ROM Nuker.bat" and changing the package list below line 32, to keep the Gamespace application simply remove line 36, you can add and remove packages to process there, as for downgrading the firmware I'm afraid there isn't a way as of yet, OPPO is very restrictive when it comes to firmware.
How to remove the OPPO launcher ? I get an error when trying to remove it with ADB
works a treat