Im reverting back to android 6.0 for my k1
But when i go to flash userdata its says userdata isnt found
And i look in the zip and it wasnt there so i downloaded again and it still wasnt there any suggestions
1 more thing nvidias instrucrions say to
Fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
And rhats it do i reboot after blob?
Cause someone elses tutorial says to
fastboot flash recovery {dir}/recovery.img
fastboot flash boot {dir}/boot.img
fastboot flash system {dir}/system.img
fastboot flash userdata {dir}/userdata.img
fastboot flash staging {dir}/blob
fastboot flash dtb {dir}/tegra124-tn8-p1761-1270-a04-e-battery.dtb
Tjeres an extra command?
Which do i use?
Thx
Iceek1 said:
Im reverting back to android 6.0 for my k1
But when i go to flash userdata its says userdata isnt found
And i look in the zip and it wasnt there so i downloaded again and it still wasnt there any suggestions
1 more thing nvidias instrucrions say to
Fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
And rhats it do i reboot after blob?
Cause someone elses tutorial says to
fastboot flash recovery {dir}/recovery.img
fastboot flash boot {dir}/boot.img
fastboot flash system {dir}/system.img
fastboot flash userdata {dir}/userdata.img
fastboot flash staging {dir}/blob
fastboot flash dtb {dir}/tegra124-tn8-p1761-1270-a04-e-battery.dtb
Tjeres an extra command?
Which do i use?
Thx
Click to expand...
Click to collapse
Don't worry, that one isn't included in the latest Nougat builds as well and they still flash normally.
Just proceed without that
XT1924-7 (METROPCS VARIANT)
Download: https://drive.google.com/file/d/1qJfpA3SML_SgJGjhyTmURuv7Sr1rMrYh/view?usp=sharing
Remember where you got it from first ! Not available on lolinet either.
Dont forget to hit that THANKS! button if you download it,
Happy flashing!!
Enjoy
t.me/motoe5dev
I'm currently using the [AOSP 9.0] Phh-Treble ROM on my E5 Plus, but I'd prefer to go back to stock...Is it safe to go back an Android version?
Are there any special steps I need to take?
Appreciate any help!
JamesAlanTyler said:
I'm currently using the [AOSP 9.0] Phh-Treble ROM on my E5 Plus, but I'd prefer to go back to stock...Is it safe to go back an Android version?
Are there any special steps I need to take?
Appreciate any help!
Click to expand...
Click to collapse
yes it is safe
Power off device , power on with volume down + power to access fastboot mode
then use these commands to return to stock with latest firmware
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
JamesAlanTyler said:
I'm currently using the [AOSP 9.0] Phh-Treble ROM on my E5 Plus, but I'd prefer to go back to stock...Is it safe to go back an Android version?
Are there any special steps I need to take?
Appreciate any help!
Click to expand...
Click to collapse
I'm a newbie with android and thought I had bricked my phone. I tried everything and nothing worked until I came across this thread! Thank you so very much:good::laugh:
i unlocked my bootloader but after doing so my recovery disappeared. i cant boot to recovery all i get is bad key even when i factory reset the robot doesnt appear it just says bad key then it takes me to the screen to set my phone up. what should i do? i tried flashing twrp but its the same thing
Anytime you flash stock firmware you must reboot to bootloader and flash twrp again then boot recovery mode by holding vol down during power cycle and to go to bootloader then press vol down twice and power once to boot recovery
whodat711 said:
Anytime you flash stock firmware you must reboot to bootloader and flash twrp again then boot recovery mode by holding vol down during power cycle and to go to bootloader then press vol down twice and power once to boot recovery
Click to expand...
Click to collapse
Is there no way to make a flashable .zip file instead of doing fastboot command without compromising root? Since TWRP can actually be flashed to the recovery partition and the phone can be decrypted?
Is there an updated image available? I can no longer flash this after getting the latest security update. EDIT: I used Lenovo Moto Smart Assistant to recover it.
Is anyone experience bootloops on random occasions with android 10 ROMs?
Things work great, played with tons of stuff and when android 10 ROMs appeared I jump to them. With android 9 firmware and android 10 custom ROMs I had no issues except the HEVC issues which were common before they fix this.
So after a while Xiaomi release android 10(miui) and I've put the firmware only and clean flash custom ROMs but after a few weeks I've experience some hard reboots. Random without any reason, bam hard reboot and when it occured it was bootlooping without a stop.
So Xiaomi image(unlocked), rom load and bam again restart, sometimes it booted properly but most of the times the boot loop never stopped UNLESS I force restart faster than the rom logo and enter twrp and shut it off and leave it a few seconds then boot it up ...after that it was working fine until the next boot loop that might occur same day or a few days later
One time it bootloop I enter to twrp fast and it boot looped even in TWRP!!!
This is weird, so let's fastboot the phone and clean everything up. Using Mi flashtool I tried to flash MIUI, after 30+ minutes nothing..it was trying to flash. Oh well. I force restart and enter fastboot and tried again..it finished with error but seemed to flash MIUI properly, clean flash custom ROMs but the issue remains
Anyone have similar experience? After some search some other Xiaomi users have similar issues and use an app called "wakelock" ..I'll see how this goes
P.S. If issue remains I'll fastboot the phone manually(without the mi flashtool), that would be my last resort - Sorry for the long post
P.S.2 usually the bootloop starts when I'm stop using my phone and press the power button to turn off display, it never happened when the phone is on idle
EDIT: Wakelock didn't save anything, got bootloop once again ..tonight I'm gonna try fastboot manual ..hoping for a fix(if it still keeps messing around I'd go back to android 9 where I had no issues at all)
So Xiaomi flash tool failed me if you read my original post, didn't want to risk it again, so I backup up everything and went the old way, it seems the bootloop is fixed, my proximity issues are also fixed(proximity sensor worked on short calls but on long calls the screen remained black - cleaned it as some suggested but the issue was there, now it seems that it's also fixed!!)
So if you have weird behavior just use CMD with fastboot style and write the following(one at a time, or you can create a batch file(bat file) but I strongly recommend that you do it one after another and seek for "success" after each command):
fastboot erase boot
fastboot flash crclist crclist.txt
fastboot flash sparsecrclist sparsecrclist.txt
fastboot flash xbl_ab xbl.img
fastboot flash xbl_config_ab xbl_config.img
fastboot flash abl_ab abl.img
fastboot flash tz_ab tz.img
fastboot flash hyp_ab hyp.img
fastboot flash devcfg_ab devcfg.img
fastboot flash storsec_ab storsec.img
fastboot flash bluetooth bluetooth.img
fastboot flash cmnlib_ab cmnlib.img
fastboot flash cmnlib64_ab cmnlib64.img
fastboot flash modem modem.img
fastboot flash dsp dsp.img
fastboot flash keymaster_ab keymaster.img
fastboot flash logo logo.img
fastboot flash misc misc.img
fastboot flash aop_ab aop.img
fastboot flash qupfw_ab qupfw.img
fastboot flash ImageFv imagefv.elf
fastboot flash vendor vendor.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot erase sec
fastboot flash cust cust.img
fastboot flash boot boot.img
fastboot reboot
P.S. This WILL ERASE your internal data but won't lock bootloader, so back up your photos and files before
Requirements:
1) ADB Installer v1.4.3 (or any adb installer you prefer)
2) Fastboot MIUI rom, I've use "polaris_global_images_V11.0.4.0.QDGMIXM_20200325.0000.00_10.0_global_82f39e53fd"
T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional)
This thread is for the T-Mobile OnePlus 7 Pro GM1915 Model ONLY
WARNING
Proceed at your own risk. I am not responsible for any damage to your device.
Performing the instructed steps below will completely replace the existing firmware on your device, including bluetooth, WiFi and radio firmware.
Do not proceed unless you are absolutely certain your device is the T-Mobile GM1915 Model
Flashing Android 11 will remove TWRP if installed, and custom recovery will no longer be available.I have temporarily removed instructions for flashing this firmware until I can test it further.
FIRMWARE DETAILS
Version Name: OnePlus7ProTMOOxygen_11_2104261207
Version: OnePlus7ProTMOOxygen_11.O.20_GLO_020_2104261207
Security Patch Level: 2021-04-01
OOS Version: 11.0.1.2.GM31CB
DOWNLOADS
GM1915_11.0.1.2.GM31CB.zip (2.6GB) - md5: 2bb808a07052d5b240e3c8d3dfaf95ac
If you have any problems with the downloads or process, please reply to the thread and tag me. Thanks!
weakNPCdotCom said:
T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional)
This thread is for the T-Mobile OnePlus 7 Pro GM1915 Model ONLY
WARNING
Proceed at your own risk. I am not responsible for any damage to your device.
Performing the instructed steps below will completely replace the existing firmware on your device, including bluetooth, WiFi and radio firmware.
Do not proceed unless you are absolutely certain your device is the T-Mobile GM1915 Model
Flashing Android 11 will remove TWRP if installed, and custom recovery will no longer be available.Now that Oxygen OS 11 has been pushed OTA to devices, some of us trying to revert back to stock TMO firmware may not want to revert to Android 10.
This guide will flash TMO 11.0.1.2 firmware to your device, reverting it to stock and updating it to Android 11
FIRMWARE DETAILS
Version Name: OnePlus7ProTMOOxygen_11_2104261207
Version: OnePlus7ProTMOOxygen_11.O.20_GLO_020_2104261207
Security Patch Level: 2021-04-01
OOS Version: 11.0.1.2.GM31CB
INSTRUCTIONS
If you are going to root: Have a copy of Magisk Manager v23 downloaded to your PC.
Option A: Manual Flash (Recommended)
Download GM1915_11.0.1.2.GM31CB.zip
Extract contents to your fastboot directory or a directory of your choice
For root, replace the extracted boot.img with the boot.img file in the "magisk_patched-OOS-11.0-boot" directory
Execute the following fastboot commands in order. Make sure you specify the path to the extracted images if they were not extracted to your fastboot directory
Code:
fastboot flash abl_a abl.img
fastboot flash abl_b abl.img
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash hyp_a hyp.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash LOGO_a LOGO.img
fastboot flash LOGO_b LOGO.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash odm_a odm.img
fastboot flash odm_b odm.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash xbl_config_a xbl_config.img
fastboot flash xbl_config_b xbl_config.img
fastboot erase ddr
If you are converting from a non TMO ROM, this step is required. Otherwise it is optional.
Code:
fastboot erase userdata
Reboot your device. Developer Options and USB Debugging may need to be re-enabled on first boot.
If you flashed the patched boot image for root, copy the Magisk Manager v23 apk to your device and install it. Run the app to make sure magisk is being detected properly.
Option B: Fastboot Update
*I have not tested this method*
Download GM1915_11.0.1.2.GM31CB_UPDATE.zip
Extract contents to your fastboot directory or a directory of your choice
Execute one of the following fastboot commands
Wipe Data (Required if coming from a non TMO ROM):
Code:
fastboot -w update images.zip
Keep Data:
Code:
fastboot update images.zip
OPTIONAL for root, execute the following
Code:
fastboot flash boot_a /magisk-patched-OOS-11.0-boot/boot.img
fastboot flash boot_b /magisk-patched-OOS-11.0-boot/boot.img
Reboot your device. Developer Options and USB Debugging may need to be re-enabled on first boot.
If you flashed the patched boot image for root, copy the Magisk Manager v23 apk to your device and install it. Run the app to make sure magisk is being detected properly.
DOWNLOADS
GM1915_11.0.1.2.GM31CB.zip (2.6GB) - md5: 2bb808a07052d5b240e3c8d3dfaf95ac
GM1915_11.0.1.2.GM31CB_UPDATE.zip (2.6GB) - md5: 12d8a57c1d56e0079bf4375513c1ece6
If you have any problems with the downloads or process, please reply to the thread and tag me. Thanks!
Click to expand...
Click to collapse
Question I owned the T-Mobile variant OnePlus 7 pro which is converted to the international variant running android 11 will this procedure work for me ?
Wouldn't work on my TMobile oneplus 7 pro with bootloader unlocked I get the error sending abl_a okay writing abl_a failed (remote: flashing is not allowed for critical partitions I'm currently on converted international international latest Android 11 update
mjb337 said:
Wouldn't work on my TMobile oneplus 7 pro with bootloader unlocked I get the error sending abl_a okay writing abl_a failed (remote: flashing is not allowed for critical partitions I'm currently on converted international international latest Android 11 update
Click to expand...
Click to collapse
that's strange, I am able to flash abl fine.
I'm also having this issue.
mjb337 said:
Wouldn't work on my TMobile oneplus 7 pro with bootloader unlocked I get the error sending abl_a okay writing abl_a failed (remote: flashing is not allowed for critical partitions I'm currently on converted international international latest Android 11 update
Click to expand...
Click to collapse
And unfortunately there's no way to get TWRP on Android 11 at the moment. Not sure about how else to go about flashing
weakNPCdotCom said:
that's strange, I am able to flash abl fine.
Click to expand...
Click to collapse
Strange it wouldn't work for me my bootloader plus my device have been carrier unlocked for almost two years and I'm converted to the international variant as well I've never had a problem with flashing I guess it's not for me I'll probably convert back to TMobile just to test there update
mjb337 said:
Question I owned the T-Mobile variant OnePlus 7 pro which is converted to the international variant running android 11 will this procedure work for me ?
Click to expand...
Click to collapse
If you have converted to international for all intents and purposes you now have a GSM1917 international. You can install Derpfest and all the other "regular roms". If you do the "manual method" where you flash each partition you should be good to go.
greytheVIIth said:
I'm also having this issue.
And unfortunately there's no way to get TWRP on Android 11 at the moment. Not sure about how else to go about flashing
Click to expand...
Click to collapse
Not true anymore. If this rom uses "fbev2" which apparently most true android 11 rom's do then nebrassy released a version a couple of days back that works just fine with android 11....I linked to it in the derpfest thread and posted install instructions which should work here as well. Even if you get twrp installed you probably still don't want to install the rom's via twrp...just do manual method and then use twrp for backup's etc.
weakNPCdotCom said:
T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional)
This thread is for the T-Mobile OnePlus 7 Pro GM1915 Model ONLY
WARNING
Proceed at your own risk. I am not responsible for any damage to your device.
Performing the instructed steps below will completely replace the existing firmware on your device, including bluetooth, WiFi and radio firmware.
Do not proceed unless you are absolutely certain your device is the T-Mobile GM1915 Model
Flashing Android 11 will remove TWRP if installed, and custom recovery will no longer be available.Now that Oxygen OS 11 has been pushed OTA to devices, some of us trying to revert back to stock TMO firmware may not want to revert to Android 10.
This guide will flash TMO 11.0.1.2 firmware to your device, reverting it to stock and updating it to Android 11
FIRMWARE DETAILS
Version Name: OnePlus7ProTMOOxygen_11_2104261207
Version: OnePlus7ProTMOOxygen_11.O.20_GLO_020_2104261207
Security Patch Level: 2021-04-01
OOS Version: 11.0.1.2.GM31CB
INSTRUCTIONS
If you are going to root: Have a copy of Magisk Manager v23 downloaded to your PC.
Option A: Manual Flash (Recommended)
Download GM1915_11.0.1.2.GM31CB.zip
Extract contents to your fastboot directory or a directory of your choice
For root, replace the extracted boot.img with the boot.img file in the "magisk_patched-OOS-11.0-boot" directory
Execute the following fastboot commands in order. Make sure you specify the path to the extracted images if they were not extracted to your fastboot directory
Code:
fastboot flash abl_a abl.img
fastboot flash abl_b abl.img
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash hyp_a hyp.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash LOGO_a LOGO.img
fastboot flash LOGO_b LOGO.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash odm_a odm.img
fastboot flash odm_b odm.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash xbl_config_a xbl_config.img
fastboot flash xbl_config_b xbl_config.img
fastboot erase ddr
If you are converting from a non TMO ROM, this step is required. Otherwise it is optional.
Code:
fastboot erase userdata
Reboot your device. Developer Options and USB Debugging may need to be re-enabled on first boot.
If you flashed the patched boot image for root, copy the Magisk Manager v23 apk to your device and install it. Run the app to make sure magisk is being detected properly.
Option B: Fastboot Update
*I have not tested this method*
Download GM1915_11.0.1.2.GM31CB_UPDATE.zip
Extract contents to your fastboot directory or a directory of your choice
Execute one of the following fastboot commands
Wipe Data (Required if coming from a non TMO ROM):
Code:
fastboot -w update images.zip
Keep Data:
Code:
fastboot update images.zip
OPTIONAL for root, execute the following
Code:
fastboot flash boot_a /magisk-patched-OOS-11.0-boot/boot.img
fastboot flash boot_b /magisk-patched-OOS-11.0-boot/boot.img
Reboot your device. Developer Options and USB Debugging may need to be re-enabled on first boot.
If you flashed the patched boot image for root, copy the Magisk Manager v23 apk to your device and install it. Run the app to make sure magisk is being detected properly.
DOWNLOADS
GM1915_11.0.1.2.GM31CB.zip (2.6GB) - md5: 2bb808a07052d5b240e3c8d3dfaf95ac
GM1915_11.0.1.2.GM31CB_UPDATE.zip (2.6GB) - md5: 12d8a57c1d56e0079bf4375513c1ece6
If you have any problems with the downloads or process, please reply to the thread and tag me. Thanks!
Click to expand...
Click to collapse
Thank you very much!!!
saved my phone <3
Hi. This rom supports dual sim?
kobebryant said:
Hi. This rom supports dual sim?
Click to expand...
Click to collapse
This is a stock firmware package. Also, it is NOT a TRWP flashable zip. I can make one of those if twrp actually works now.
famewolf said:
Not true anymore. If this rom uses "fbev2" which apparently most true android 11 rom's do then nebrassy released a version a couple of days back that works just fine with android 11....I linked to it in the derpfest thread and posted install instructions which should work here as well. Even if you get twrp installed you probably still don't want to install the rom's via twrp...just do manual method and then use twrp for backup's etc.
Click to expand...
Click to collapse
Would it be possible for you to link me to the source of that TWRP build? I would like to get it on my phone.
Also, that would allow me to build a flashable zip of this firmware.
famewolf said:
Not true anymore. If this rom uses "fbev2" which apparently most true android 11 rom's do then nebrassy released a version a couple of days back that works just fine with android 11....I linked to it in the derpfest thread and posted install instructions which should work here as well. Even if you get twrp installed you probably still don't want to install the rom's via twrp...just do manual method and then use twrp for backup's etc.
Click to expand...
Click to collapse
I found nebrassy's twrp image, but it still does not support decryption.
Also, when I booted to it, it messed up my entire system. The phone was no longer able to boot to android and when I reflashed my boot image it started crashing on boot.
I am looking into how to get this working properly.
weakNPCdotCom said:
I found nebrassy's twrp image, but it still does not support decryption.
Also, when I booted to it, it messed up my entire system. The phone was no longer able to boot to android and when I reflashed my boot image it started crashing on boot.
I am looking into how to get this working properly.
Click to expand...
Click to collapse
If you didn't find the post where he specifically says "here is the fbev2 version" then you didn't install the right one. He has SEVERAL versions of twrp.
TWRP-3.5.1-guacamole-FBEv2-Nebrassy-3.img | by Nebrassy for OnePlus 7 Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
famewolf said:
If you didn't find the post where he specifically says "here is the fbev2 version" then you didn't install the right one. He has SEVERAL versions of twrp.
Click to expand...
Click to collapse
i assumed that the filename "TWRP-3.5.1-guacamole-FBEv2-Nebrassy" indicated it was FBEv2 xD
weakNPCdotCom said:
i assumed that the filename "TWRP-3.5.1-guacamole-FBEv2-Nebrassy" indicated it was FBEv2 xD
Click to expand...
Click to collapse
See previous file link since the -3 in it means you might have an older version.
*update* Found actual post: https://forum.xda-developers.com/t/...eamwin-recovery-project.4289455/post-85197387
famewolf said:
See previous file link since the -3 in it means you might have an older version.
*update* Found actual post: https://forum.xda-developers.com/t/...eamwin-recovery-project.4289455/post-85197387
Click to expand...
Click to collapse
yeah, that says "only use if you are on a custom rom and other builds dont work for you"
it ended up soft-bricking my phone
weakNPCdotCom said:
yeah, that says "only use if you are on a custom rom and other builds dont work for you"
it ended up soft-bricking my phone
Click to expand...
Click to collapse
Both Derpfest and Yaap work well with fbev2 and are Android 11 based on AOSP. I'm sorry that happened to you. In future you should use "Fastboot BOOT twrp.img" to boot recovery without replacing the existing recovery...then if it didn't work all you'd need to do if force the phone to power off via holding down vol up and power for several seconds. Still not sure how you soft bricked because I tried installing it in recovery on a non compatible rom and all it did was startup and show available storage as 0. It showed no files...once i upgraded the rom then it worked fine.
If you pay attention to with slot you are booting to and flashing to ,it will help out slot. This will always leave you a option to repair. By just switching to the opposite slot to boot to recovery. If you don't know the command then you should really learn fastboot --help. It's all the same as Python.
Hi, do you have the 11.0.1.3 update as well ? I can't install it through OTA, installation keeps failing for whatever reason...
Pluginbaby00 said:
Hi, do you have the 11.0.1.3 update as well ? I can't install it through OTA, installation keeps failing for whatever reason...
Click to expand...
Click to collapse
I have the extracted payload, but im not sure if it's actually usable on the GM1915. I can upload it if you need it, but there are several partitions you cant flash and the system image is not in the proper sparse format.
I got Motorola Edge S from China, and plan to:
1. Unlock (Succeeded !)
2a. fastboot flash boot twrp-3.5.2_11.0-2-nio.img
fastboot flash boot_b twrp-3.5.2_11.0-2-nio.img
SD card cannot work properly, as well as Adb sideload, so Official LOS.zip cannot be flashed,
OR
2b. fastboot flash boot lineage-19.1-20220604-recovery-nio.img
fastboot flash boot_b lineage-19.1-20220604-recovery-nio.img
Stucked on the Boot-up screen with Logo before Recovery mode.
3. flash Stock EU rom
(to achieve more international firmware, since I don't find independent firmware.zip)
4. flash LOS rom
N.B. [data] partition had been cleared, and I should haven't cleared [system] partition, but I cannot boot back to stock rom after Step 2, and I believe the stock rom has been removed for any accident.
Please help
Might be a long shot here, but I bricked G100 when trying to flash to both slots. Use the Motorola device recovery tool to bring it back to stock and flash only ONE slot (the active one) with your rom. There's installation scripts on this forum that do exactly this for you.
twelfth said:
Might be a long shot here, but I bricked G100 when trying to flash to both slots. Use the Motorola device recovery tool to bring it back to stock and flash only ONE slot (the active one) with your rom. There's installation scripts on this forum that do exactly this for you.
Click to expand...
Click to collapse
Initially I just flash one slot. Then I read that inconsistency between 2 slots can cause problem, so I have flash 2nd slot also, by copy-partitions-20210323_1922.zip or by "fastboot flash boot_b ...".
Now, I can also recovery and boot back to stock rom, by flash boot.img extracted from stock rom.zip with the same version as mine.
So the KEY problem is:
Under TWRP recovery loader, with ADB sideload turned on, the PC seems cannot connect & send below crucial command to Android:
$ fastboot flash boot lineage-19.1-20220604-recovery-nio.img
N.B. I have already used USB driver from Motorola, so ADB commands can run without problem, except ADB Sideload mode. Also, I have tried using USB 2.0 hub port with 2.0 cable (4-pins) as well.
TWRP for nio is not stable (yet). Use the instructions for lineageos official.
patwwh said:
I got Motorola Edge S from China, and plan to:
1. Unlock (Succeeded !)
2a. fastboot flash boot twrp-3.5.2_11.0-2-nio.img
fastboot flash boot_b twrp-3.5.2_11.0-2-nio.img
SD card cannot work properly, as well as Adb sideload, so Official LOS.zip cannot be flashed,
OR
2b. fastboot flash boot lineage-19.1-20220604-recovery-nio.img
fastboot flash boot_b lineage-19.1-20220604-recovery-nio.img
Stucked on the Boot-up screen with Logo before Recovery mode.
3. flash Stock EU rom
(to achieve more international firmware, since I don't find independent firmware.zip)
4. flash LOS rom
N.B. [data] partition had been cleared, and I should haven't cleared [system] partition, but I cannot boot back to stock rom after Step 2, and I believe the stock rom has been removed for any accident.
Please help
Click to expand...
Click to collapse
Late here but on 2a step, you can actually copy the ROM zip to internal storage since windows can detect your phone as storage device when it is in TWRP recovery.
https://wiki.lineageos.org/devices/nio/install is telling everything you need to know.
Though:
NEW:
Code:
fastboot devices
fastboot --set-active=a
// Update firmware
// Files taken from https://mirrors.lolinet.com/firmware/motorola/nio/official/RETEU/
fastboot flash modem_a NON-HLOS.bin
fastboot flash modem_b NON-HLOS.bin
fastboot erase mdmddr
fastboot flash fsg_a fsg.mbn
fastboot flash fsg_b fsg.mbn
fastboot erase mdm1m9kefs1
fastboot erase mdm1m9kefs2
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot erase carrier
fastboot erase ddr
fastboot reboot bootloader
fastboot devices
fastboot --set-active=a
// First setup
// Files taken from https://mirror.math.princeton.edu/pub/lineageos/full/nio/
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash vendor_boot_a vendor_boot.img
fastboot flash vendor_boot_b vendor_boot.img
fastboot reboot bootloader
fastboot devices
fastboot --set-active=a
// Install recovery
// Files taken from https://download.lineageos.org/nio
fastboot flash boot <recovery_filename>.img
for example:
fastboot flash boot_a <recovery.img>
fastboot flash boot_b <recovery.img>
fastboot reboot recovery
// Be sure all firmware is consistant
// Files taken from https://mirrorbits.lineageos.org/tools/copy-partitions-20220613-signed.zip
adb sideload copy-partitions-20220613-signed.zip
fastboot reboot recovery
FRESH INSTALL OF LINEAGE
Code:
Reboot into recovery
CHECK WHICH IS THE ACTIVE PARTITION, FIRST TIME A
Goto “Factory reset”
Goto “Format data/factory reset”
Goto “Format data”
Goto “Apply Update”
Goto “Apply from adb”
adb sideload <lineageos.zip>
Goto “Advanced”
Goto “Reboot to recovery” (now active partition is changed to the updated one)
CHECK WHICH IS THE ACTIVE PARTITION, FIRST TIME SHOULD BE B!!
Reboot to system and setup...
(This is how I do it...)
(On updates, active partition is switching on reboot after you have done a flash of lineageos.zip file)
(Forget TWRP for this device as it is not finished and several bugs are there. Just use Lineage OS)
TWRP only works on Android 11, above that nothing will work and it will be very buggy