Related
your device is corrupt. it can't be trusted and will not boot
g.com/abh
Hello, I tried root my phone NX616J ( nubia x ui.nubia.cn / rom / detail / 58 )
maybe someone gives me good instructions for flash img
I tried this:
fastboot -w update C:\nubiax\zip\update.zip
error:
NotSpecified: (archive does no...droid-info.txt':String)
and this:
fastboot erase modem
fastboot erase cache
fastboot format userdata
fastboot flash boot C:\nubiax\img\NX616J-V2-11Firmware\boot.img
fastboot flash system C:\nubiax\system.img #### it took from "red nubia" nowhere found system.img for x nubia !!! ####
fastboot flash recovery C:\nubiax\img\NX616J-V2-11Firmware\recovery.img
fastboot flash boot C:\nubiax\img\NX616J-V2-11Firmware\dspso.bin
fastboot flash boot C:\nubiax\img\NX616J-V2-11Firmware\parameter.img
fastboot flash splash C:\nubiax\img\NX616J-V2-11Firmware\splash.img
fastboot flash modem C:\nubiax\img\NX616J-V2-11Firmware\NON-HLOS.bin
fastboot flash boot C:\nubiax\img\NX616J-V2-11Firmware\vbmeta.img
fastboot flash recovery C:\nubiax\img\NX616J-V2-11Firmware\recovery.img
fastboot reboot
if someone has the same problem:
at link everything what you need
https://drive.google.com/drive/folde...vH?usp=sharing
#C:\nubiax\adb\..
adb devices
adb reboot bootloader
adb kill-server && adb start-server
fastboot oem nubia_unlock NUBIA_NX616J
fastboot flash system C:\nubiax\img\nubiaximg\system.img
fastboot flash vendor C:\nubiax\img\nubiaximg\vendor.img
fastboot flash modem C:\nubiax\img\nubiaximg\modem.img
fastboot flash splash C:\nubiax\img\nubiaximg\splash.img
fastboot flash parameter C:\nubiax\img\nubiaximg\parameter.img
fastboot flash dtbo C:\nubiax\img\nubiaximg\dtbo.img
fastboot flash boot C:\nubiax\img\nubiaximg\boot.img
fastboot flash recovery C:\nubiax\img\nubiaximg\recovery.img
fastboot flash vbmeta C:\nubiax\img\nubiaximg\vbmeta.img
fastboot reboot bootloader
reciovey should now work * thanks for the file and help Member - Nubia2452
now just
upload it to USB the file NX616J-updateRomV305.zip
from recover start USB update (zip)
nubia X should come back to life
Now If you want Root Nubia X - RomV305!
enable USB debugging (setting - Developer options)
and
come back bootloader ( adb reboot bootloader )
Start - nubia-X_Root-V305.exe at PC - USB cable connected to phone
ROOT should now work
and
Now If you want TWRP in Nubia X RomV305!
start - nubia X-for Android P-TWRP-3.3.0.exe at PC - USB cable connected to phone
reciovey TWRT should now work
Zed Malta said:
if someone has the same problem:
at link everything what you need
https://drive.google.com/drive/folde...vH?usp=sharing
#C:\nubiax\adb\..
adb devices
adb reboot bootloader
adb kill-server && adb start-server
fastboot oem nubia_unlock NUBIA_NX616J
fastboot flash system C:\nubiax\img\nubiaximg\system.img
fastboot flash vendor C:\nubiax\img\nubiaximg\vendor.img
fastboot flash modem C:\nubiax\img\nubiaximg\modem.img
fastboot flash splash C:\nubiax\img\nubiaximg\splash.img
fastboot flash parameter C:\nubiax\img\nubiaximg\parameter.img
fastboot flash dtbo C:\nubiax\img\nubiaximg\dtbo.img
fastboot flash boot C:\nubiax\img\nubiaximg\boot.img
fastboot flash recovery C:\nubiax\img\nubiaximg\recovery.img
fastboot flash vbmeta C:\nubiax\img\nubiaximg\vbmeta.img
fastboot reboot bootloader
reciovey should now work * thanks for the file and help Member - Nubia2452
now just
upload it to USB the file NX616J-updateRomV305.zip
from recover start USB update (zip)
nubia X should come back to life
Now If you want Root Nubia X - RomV305!
enable USB debugging (setting - Developer options)
and
come back bootloader ( adb reboot bootloader )
Start - nubia-X_Root-V305.exe at PC - USB cable connected to phone
ROOT should now work
and
Now If you want TWRP in Nubia X RomV305!
start - nubia X-for Android P-TWRP-3.3.0.exe at PC - USB cable connected to phone
reciovey TWRT should now work
Click to expand...
Click to collapse
https://drive.google.com/drive/folde...vH?usp=sharing[/url]
the link is dead and i'm in a really bad situation...please
my nubia x is locked and i can't acces the restor mode even with power vol+ is not working i can only boot on fastboot mode and when i select reboot to recovery nothing happens it goes directly on " your device is corrupted"
It was rooted and i tried to restore it with twrp. Can you help me ?
elnas1369 said:
https://drive.google.com/drive/folde...vH?usp=sharing[/URL]
the link is dead and i'm in a really bad situation...please
my nubia x is locked and i can't acces the restor mode even with power vol+ is not working i can only boot on fastboot mode and when i select reboot to recovery nothing happens it goes directly on " your device is corrupted"
It was rooted and i tried to restore it with twrp. Can you help me ?
Click to expand...
Click to collapse
hi dear
have you got the solution as i am at the same setuation as you mention above. i am also stuck on Recovery mode please let me know if you got the link
This is an attempt at rooting the UMIDIGI F2. Caution be advised, we are not responsible for your mistakes; but rest assured, most of them can be corrected.
Rooting the F2
Disclaimers
This is important, please read thoughtfully.
whatever you do, never ever use SP Flash Tool in "Format All+Download" mode. This will wipe your IMEIs and some other bad stuff will happen like loss of fingerprint sensor. This cannot be reversed by us.
Once bootloader is unlocked, warranty is considered void. By following this guide, you consent to that happening. Safety net CTS will not pass anymore unless you flash Magisk which hides the unlocked bootloader.
Never relock your bootloader while running anything unofficial as the phone will not boot until you unlock again.
And, once again, a lot of bad things can happen like bootloops, if that happens to you don't freak out and reflash stock, redoing the rooting process from the start. It might be time consuming, but that's your safest bet!
More important even, have fun rooting, it's before all a hobby!
Various Resources
>>> Latest official stock ROM <<<
Minimal ADB and Fastboot by shimp208
> Magisk (and Manager) by topjohnwu <
Mediatek SP Flash Tool
Latest unofficial TWRP
Unlocking Bootloader
ATTENTION!! After unlocking the bootloader, all user data in the phone's memory will be lost, so do not forget to throw all the most important things on your computer or flash drive!
1) Activate "Developer options" through Settings > About Phone > Tap Build Number multiple times.
2) Open "Developer options" in Settings > System > Tap Advanced.
Enable "OEM Unlocking" and enter your password to confirm. Enable "USB Debugging" as well.
3) On Windows, download and install Minimal ADB and Fastboot by shimp208
On Linux, use your packet manager to install android-tools-adb and android-tools-fastboot
4) Open command prompt (Win + R > type cmd) or a terminal on linux.
5) Plug your phone, accept the prompt about adb and the PC signature.
6) Type adb reboot bootloader to reboot in fastboot mode.
THESE NEXT TWO STEPS WILL COMPLETELY WIPE YOUR DATA
7) Unlock the bootloader using fastboot flashing unlock and pressing Vol+
8) Unlock the secure partitions using fastboot flashing unlock_critical and pressing Vol+
9) Restart using fastboot reboot
You will now always see "Orange State" at boot; this is completely fine and will only delay your boot by 5 seconds.
Rooting using Magisk patched boot.img
This is "experimental" and is probably overkill, but everyone managed to install Magisk with it.
1) Clean install UMIDIGI_F2_V1.0_20200106.V3.08 with SPFT by selecting the scatter file, pressing download an rebooting the phone (Make sure it is in "Download Mode" and not "Format + Download")
2) Patch boot.img by copying it to your device, using Magisk Manager to patch it, and get back the magisk_patched.img in the Download folder back to your PC.
3) Start ADB while booted; run adb reboot bootloader. Alternative is to reboot to recovery and selecting "reboot to bootloader"
4) unlock if not already done with fastboot flashing unlock followed by fastboot flashing unlock_critical
You can try without --disable-verity --disable-verification if those commands are not recognized. I have not tested without them.
6) fastboot --disable-verity --disable-verification flash boot magisk_patched.img
7) fastboot --disable-verity --disable-verification flash recovery recovery.img (recovery.img from stock)
8) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (vbmeta.img from stock)
9) fastboot reboot
When rebooting, install Magisk Manager. It will prompt to finalize the installation, you can do so.
Congratulations ! You are now a proud Magisk user ! All credits goes to @topjohnwu he's the real MVP here.
Returning to stock / Resolving issues
The best way to resolve any issue is to return to stock. Here is the method.
1) Download latest stock ROM ("SPFT .zip") on UMIDIGI's forums
2) Download SP Flash Tool if you don't have it yet (Windows only)
3) Extract stock ROM in SP Flash Tool directory
4) Open SP Flash Tool, Download Tab, "Choose" in Scatter-loading file, select the scatter file in the stock ROM directory.
5) If you want to keep your data, untick "userdata" partition
6) Press Download and connect your device via USB. Reboot the phone or turn it off and everything will be flashed.
7) If you want a full stock experience, I recommend relocking the bootloader so that SafetyNet will pass. Get into fastboot mode by using adb reboot bootloader and use fastboot flashing lock_critical followed by fastboot flashing lock. This will wipe your data once more.
You should be good to go.
TWRP
Device Tree
>> Download my latest build here <<
Flash in Bootloader mode with fastboot flash recovery twrp_f2.img
Android 10 and TWRP aren't compatible yet. /system and /vendor cannot be mounted. /data partition is encrypted. You can still flash .img and some zips that alter different partitions. Nothing I can do about it.
Misc
Different boot modes
Recovery / TWRP :
Turn off the phone (or reboot)
Press Vol+ and Power until some choice comes up to you
Navigate using Vol+, select Recovery Mode using Vol-
Bootloader mode :
Boot into TWRP, select Reboot, Bootloader
Or use adb reboot bootloader either in recovery or system
Or use fastboot reboot-bootloader in fastboot mode
Magisk and EdXposed
Fixing Magisk bootloop
Two techniques that could work after installing a module that broke everything :
Hook your device up to a computer (or other device you can run adb from) and execute the following command:
adb wait-for-device shell magisk --remove-modules
After that you can start your device and as soon as adb is available the command will activate, the modules will be removed and the device will reboot.
Click to expand...
Click to collapse
-----
You could also try :
If you can't boot your device, this can be done by placing a file in /cache (/data/cache on A/B devices) named ".disable_magisk" (without quotation marks and with the leading dot). This will enable Core Only Mode and you can boot up your device, uninstall the troublesome module and then go into the Manager settings, disable Core Only Mode and reboot. In TWRP you can create the file through the TWRP terminal with the touch command, see below for an example.
Click to expand...
Click to collapse
Installing EdXposed
Please use the latest YAHFA or Sandhook canary build. I have a report of Xposed-SandHook-v0.4.6.1 (4504)-tdgptedc-release working.
_cab13_ said:
This is an attempt at rooting the UMIDIGI F2. For now, unsuccessful. Any help would be appreciated!
Click to expand...
Click to collapse
ATTENTION!! After unlocking the bootloader, all user data in the phone's memory will be lost, so do not forget to throw all the most important things on your computer or flash drive!
1) Activate the "for developers" item in the settings (7 times click on the "build number" in the "about phone" settings at the bottom)
2) Go to "Settings"(the main screen of the application) go to "for developers" and move the switches to the enabled position near the items "USB Debugging" and " Unlocking the bootloader"
3) Then download platform tools from here https://developer.andr...eleases/platform-tools
4) Unpack the archive from platform tools to the root of the C: drive(so that the platform-tools folder is in the root of the C drive: )
5) if the process does not go install VCOM driver
6) Switch your smartphone to fastboot mode:
6.1) connect the included phone to the computer
6.2) Open the command prompt
6.2.1) Click Win+R
6.2.2) in the window that appears, write "cmd" and click " OK"
6.3) in the command line when the phone is turned on, write(without quotes)
6.3.1) " cd " (note that there is a space after "cd") and drag the "platform-tools" folder with the cursor to the command line window, press Enter
6.3.2) the Following command "adb reboot bootloader"
6.3.3) Your phone should reboot into Fastboot mode or a window should appear on the phone asking for debugging permission for this computer - put a check mark "Always allow debugging from this computer" and click "OK", repeat point 6.3.2
7) After that, on the computer in the same command line, enter " fastboot flashing unlock"
8) when the smartphone screen will prompt confirm by pressing vol+
9) after you see Finished, restart your device
Now the logo will be labeled Orange state when loading
I've rooted my F2. I used magisk to patch the boot.img then flashed the boot.img through fastboot on Linux. It didn't work with magisk 20.1. Had to used the newest magisk manager. I am interested in your twrp if you have one to try. Would you upload it so I may try to flash it.
Please upload your patched boot.img file. Thanks
I would love to have that boot image as well! What magisk version did you use then ? I can start crafting a guide.
EDIT: what boxes did you tick in Magisk Manager ?
EDIT 2: did you pad the boot image with DD ? Or maybe you wiped the boot partition beforehand to make it all zeroes ? It seems to be the missing thing and a known bug in Magisk.
Magisk 20.2 was what I used. Then flashed the boot through fastboot using Debian Linux.
Rooted f2 boot IMG
I've tried everything to get it rooted but any magisk patched boot image I flash just sends it into a bootloop including the one posted in this thread. It doesn't matter whether I flash it in Linux or Windows, in fastboot or in SP Flash Tool. What stock build are you guys on, the European or the Global? It seems that the boot.img is the same in both.
Apparently the issue is that the bootloader really doesn't like the fact that the image is not the full size of the partition. I'll try to dd it to the "max" size so it completely replaces the boot image and not only parts of it.
Seems to be an issue with the bootloader which doesn't like being flashed with a smaller boot image than it's partition size. Could you try padding it ? https://github.com/topjohnwu/Magisk/issues/2005
With this command
Code:
dd if=/dev/zero of=magisk_patched.img bs=1 count=1 seek=33554431
EDIT: Double post, my internet is pretty bad, I thought the first one didn't go. Can't delete apparently.
When I unlocked the bootloader I also unlocked critical areas
fastboot flashing unlock_critical
Warning---- this will wipe your phone again just like the bootloader unlock.
Haha seems to be the key to it ! Thanks for the update !
I've tried everything as well. Still bootloop. Your patched image doesn't work for me. I've unlocked critical as well as regular unlock.
1. Did you tick any box in Magisk Manager ?
2. Did you relock afterwards ?
3. What firmware version ?
I downloaded the new update today and I haven't been able to root the boot.IMG so far. I will keep trying and note anything that is successful.
GOOD NEWS ! I managed to make it work, I don't really know how, but I now have Magisk 20.2 installed. Here is what I did.
1) Clean install UMIDIGI_F2_V1.0_20200106.V3.08 with SPFT
2) Download the f2rootedboot file from zironia
3) Start ADB while booted; run adb reboot bootloader
4) unlock if not already done with fastboot flashing unlock followed by fastboot flashing unlock_critical
5) I flashed a bunch of partitions with dm-verity disabled.
6) fastboot --disable-verity --disable-verification flash boot f2rootedboot.img
7) fastboot --disable-verity --disable-verification flash recovery recovery.img
8) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
9) fastboot --disable-verity --disable-verification flash super super.img
10) fastboot --disable-verity --disable-verification flash tee1 tee.img
11) fastboot --disable-verity --disable-verification flash tee2 tee.img
12) fastboot --disable-verity --disable-verification flash cache cache.img
13)/!\ WILL RESET DATA : fastboot --disable-verity --disable-verification flash userdata userdata.img
13) fastboot reboot
I'm really not sure if you really need all that hassle, but that made it work for me. PLEASE USE FASTBOOT FROM BOOTLOADER (adb reboot bootloader, or choose "Reboot in Bootloader" in recovery / fastbootd)
_cab13_ said:
GOOD NEWS ! I managed to make it work, I don't really know how, but I now have Magisk 20.2 installed. Here is what I did.
1) Clean install UMIDIGI_F2_V1.0_20200106.V3.08 with SPFT
2) Download the f2rootedboot file from zironia
3) Start ADB while booted; run adb reboot bootloader
4) unlock if not already done with fastboot flashing unlock followed by fastboot flashing unlock_critical
5) I flashed a bunch of partitions with dm-verity disabled.
6) fastboot --disable-verity --disable-verification flash boot f2rootedboot.img
7) fastboot --disable-verity --disable-verification flash recovery recovery.img
8) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
9) fastboot --disable-verity --disable-verification flash super super.img
10) fastboot --disable-verity --disable-verification flash tee1 tee.img
11) fastboot --disable-verity --disable-verification flash tee2 tee.img
12) fastboot --disable-verity --disable-verification flash cache cache.img
13)/!\ WILL RESET DATA : fastboot --disable-verity --disable-verification flash userdata userdata.img
13) fastboot reboot
I'm really not sure if you really need all that hassle, but that made it work for me. PLEASE USE FASTBOOT FROM BOOTLOADER (adb reboot bootloader, or choose "Reboot in Bootloader" in recovery / fastbootd)
Click to expand...
Click to collapse
This worked for me to reroot after the update today. Not sure what part of it is necessary for the boot image to work right though. I left off the userdata.img so I could keep my files in place.
_cab13_ said:
GOOD NEWS ! I managed to make it work, I don't really know how, but I now have Magisk 20.2 installed. Here is what I did.
1) Clean install UMIDIGI_F2_V1.0_20200106.V3.08 with SPFT
2) Download the f2rootedboot file from zironia
3) Start ADB while booted; run adb reboot bootloader
4) unlock if not already done with fastboot flashing unlock followed by fastboot flashing unlock_critical
5) I flashed a bunch of partitions with dm-verity disabled.
6) fastboot --disable-verity --disable-verification flash boot f2rootedboot.img
7) fastboot --disable-verity --disable-verification flash recovery recovery.img
8) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
9) fastboot --disable-verity --disable-verification flash super super.img
10) fastboot --disable-verity --disable-verification flash tee1 tee.img
11) fastboot --disable-verity --disable-verification flash tee2 tee.img
12) fastboot --disable-verity --disable-verification flash cache cache.img
13)/!\ WILL RESET DATA : fastboot --disable-verity --disable-verification flash userdata userdata.img
13) fastboot reboot
I'm really not sure if you really need all that hassle, but that made it work for me. PLEASE USE FASTBOOT FROM BOOTLOADER (adb reboot bootloader, or choose "Reboot in Bootloader" in recovery / fastbootd)
Click to expand...
Click to collapse
Confirmed working, thanks. I ended up patching the new boot.img myself and that also worked. I own a Note 10 + and OnePlus 7 Pro and honestly I think the Umidigi is an awesome deal, everything is pretty good on the device. It's something I wanted to try out and I'm actually impressed.
Did one of you already tried some treble roms on the f2? lineagOS, Havoc 3.0 or aosp?
ubuntuh said:
Did one of you already tried some treble roms on the f2? lineagOS, Havoc 3.0 or aosp?
Click to expand...
Click to collapse
Currently there is no twrp recovery for the f2. I've tried a couple ports of twrp but can't get past the splash screen.
We don't need TWRP to flash ROMs. Fastboot / SPFT should suffice.
_cab13_ said:
We don't need TWRP to flash ROMs. Fastboot / SPFT should suffice.
Click to expand...
Click to collapse
True. Twrp just makes it quicker and has easier backup option
AIO GUIDE TECNO KD7
1. Bootloader Unlocking
1. Download & install the ADB driver
2.Enable devloper mode by taping on Build verson(setting->my phone) then enable Oem Unlock & usb debugging from (settings->System->Devloper option)
3.Now connect device & open ADB path & run cmd
command: ADB devices
then reboot to bootloader
command: ADB reboot bootloader
4. unlock bootloader
command: fastboot flashing unlock the phone will ask to confirm
5. now reboot to system
command:fastboot reboot
If you are stuck waiting for the device screen
2. TWRP [unoficial]
https://forum.xda-developers.com/t/twrp-recovery-for-tecno-kd7.4378493/
3. Orange state disabler:
Flashing guide & zip file
Click Wipe →Format Data → Yes → Press Enter.
Then Click Reboot → Recovery (Reboot to Recovery ).
After this, TWRP Recovery Mode will be installed on your phone
Link: Orange disabler.zip
4. Root
1.boot into recovery
2. Flash magisk .zip
llink:https://github.com/topjohnwu/Magisk/releases/download/v21.0/Magisk-v21.0.zip
3.1. Unroot
1.boot into recovery
2. Flash magisk unistaller .zip
link:https://github.com/topjohnwu/Magisk/releases/download/v21.0/Magisk-uninstaller-20201003.zip
5.Stock Firmware Files
Stock boot ,stock recovery & Full Firmware are added
To Flash full firmware
Extract zip & run flash.bat
Link: TECNO-SPARK-5-PRO-KD7-H6211FQRSTU-Q-GL-211101V404-fastboot flash full rom.zip
6. Gsi rom / Custom rom Installation guide:
https://forum.xda-developers.com/t/custom-rom-for-tecno-phone-dynamic-partition.4379341/
vendor : ( 3 sim problem guide )
TECNO-SPARK-5-PRO-KD7-H6211FQRSTU-Q-GL-211101V404
7. Phone Hard Brick fix
https://forum.xda-developers.com/t/phone-soft-brick-phone-on-off-poblem-tecno-device.4378501/
7.1. Flash file:
Link :
TECNO-SPARK-5-PRO-KD7-H6211FQRSTU-Q-GL-211101V404
HIT THE THANKS BUTTON IF ABOVE INFORMATION IS HELPFUL TO YOU
Tecno kd7 full guide
https://forum.xda-developers.com/t/...r-unlocking-root-twrp-stock-firmware.4345557/
What do you mean by boot into recovery? Going fastboot mode? And then writing fastboot flash recovery magisk.zip( for step 3(root)) ?
Also should have the updatest kd7 before rooting?
Thanks in advance for your hard work.
Tanjin01: Thanks
Fast time twrp recovery install: (any bulid version)
[command]
adb devices
adb reboot bootloader
fastboot flashing unlock
fastboot flash recovery twrp.img
fastboot flash vbmeta vbmeta.img
fastboot reboot recovery
[command]
Now boot into twrp recovery and from there "wipe option->Format Data -> yes Format.
Next, Reboot option -> recovery click Wait reboot recovery and flash magisk.zip
Any time root and unroot:
2.going to recovery
Open recovery and install magisk zip. /Magisk uninstall flash
Parvej789 said:
Tanjin01: Thanks
Fast time twrp recovery install: (any bulid version)
1.Fastboot flash recovery .
Fastboot reboot recovery -
Open recovery -wipe format data-yes.
reboot to recovery
and install magisk zip.
Any time root and unroot:
2.going to recovery
Open recovery and install magisk zip. /Magisk uninstall
Click to expand...
Click to collapse
Thank a bunch for consist help with my nobby question(s)!
Correct me if i am wrong before i procced,
Fire up pc, open terminal/cmd and writing the following one after another
[Command]
adb devices
adb reboot bootloader
fastboot flashing unlock
fastboot flash recovery twrp.img
fastboot flash vbmeta vbmeta.img
[command]
Now i boot into twrp recovery and from there "wipe data". Then "advanced wipe" with delvic cache.
Next, again, twrp recovery and flash magisk.zip
Right?
Tanzin01
[Command]
adb devices
adb reboot bootloader
fastboot flashing unlock
fastboot flash recovery twrp.img
fastboot flash vbmeta vbmeta.img
fastboot reboot recovery
[command]
Now i boot into twrp recovery and from there "wipe ". Then "Format Data" with yes Format.
Next, Reboot to recovery .again, twrp recovery and flash magisk.zip
Right?
Thanks man. Have a nice day&life
hey man, all went well till format. in format i saw some error, eg failed to mount /data(something like this). Any idaea why i got this?
[i got a success msg though]]
also can i access twrp recovery mode via volume and power button?(i tried volume up+power button but got adnroid image with "No command".)
Command]
adb devices
adb reboot bootloader
fastboot flashing unlock
fastboot flash recovery twrp.img
fastboot flash vbmeta vbmeta.img
fastboot reboot recovery
[command]
Now boot into twrp recovery and from there "wipe option ->Format Data -> yes Format .
Next,
Reboot options -> recovery click Wait reboot to recovery and magisk.zip flash
Parvej789 said:
Command]
adb devices
adb reboot bootloader
fastboot flashing unlock
fastboot flash recovery twrp.img
fastboot flash vbmeta vbmeta.img
fastboot reboot recovery
[command]
Now i boot into twrp recovery and from there "wipe ". Then "Format Data" with yes Format.
Next,
Reboot options to recovery .again, twrp recovery and flash magisk.zip
Right?
Click to expand...
Click to collapse
All the commands worked smoothly but when again tried to go twrp recovery for rooting, I can't seem to find twrp. I got no command with Android pic and after few seconds default device recovery option. From where I can navigate to fastboot, recovery, wipe and etc.
"
Next,
Reboot options to recovery .again, tw
Parvej789 said:
Next,
Reboot options to recovery .again, twrp recovery and flash magisk.zip
Right?
Click to expand...
Click to collapse
Not sure what you mean by this. But tried
[Command]
adb reboot bootloader
fastboot reboot recovery
[Command]
Which took me to deafult recovery, no Twrp this time.
However I spent some time on xda and found this Command "fastboot boot twrp.img". Will try tomorrow again, will let you know if it worked! Man I'm probably bothering you!
Tanzin01 said:
"
Next,
Reboot options to recovery .again, tw
Not sure what you mean by this. But tried
[Command]
adb reboot bootloader
fastboot reboot recovery
[Command]
Which took me to deafult recovery, no Twrp this time.
However I spent some time on xda and found this Command "fastboot boot twrp.img". Will try tomorrow again, will let you know if it worked! Man I'm probably bothering you!
Click to expand...
Click to collapse
[command]
adb devices
adb reboot bootloader
fastboot flashing unlock
fastboot flash recovery twrp.img
fastboot flash vbmeta vbmeta.img
fastboot reboot recovery
[command]
Now boot into twrp recovery and from there "wipe option->Format Data -> yes Format and back home menu
Next, Reboot option -> recovery click Wait reboot recovery and flash magisk.zip
Unorganized posts! Its xda's fault. Your edited post wasn't shown to me until my last post was posted!
Thanks man. This time I got it. I wrongly rebooted after "format data". I will reflash the twrp file again tomorrow.
Hey, i got myself in trouble again! Everything was working fine till i clicked on "Erase data" from settings. Now i cant boot into sytem, always booting into twrp.Any help?
Should i try flashing android 11, the one you provided here?
Tanzin01 said:
Hey, i got myself in trouble again! Everything was working fine till i clicked on "Erase data" from settings. Now i cant boot into sytem, always booting into twrp.Any help?
Should i try flashing android 11, the one you provided here?
Click to expand...
Click to collapse
Stock recovery.img flash and reboot
To make sure, i am donig as you described,
download stock firmware and get recovery.img.
now flash it: fastboot flash recovery recovery.img
Now reboot, right?
Btw cant i just flash andoid 11 altogether? (and thanks for your constant help
Tanzin01 said:
To make sure, i am donig as you described,
download stock firmware and get recovery.img.
now flash it: fastboot flash recovery recovery.img
Now reboot, right?
Btw cant i just flash andoid 11 altogether? (and thanks for your constant help :fashfashfashfash)
Click to expand...
Click to collapse
Yes
Or
Full flash
KD7-H6211FQRSTU-Q-GL-210520V392.zip
drive.google.com
how to do full flash?
[command]
fastboot flash system FullFlashfirmware.zip
[command]
or
sideload the zip file and then swipe install via twrp?
No .
PC to mobile(fastboot flash)
Now connect device to PC
Unzip flash file PC
Folder open
Click flash.bat
CMD open:
1.Do you want to Reboot device into fastboot [Y/N]=y type enter
2.wipe user data [Y/N]=y type enter
Then flash started
FLASHING success
Reboot to phone on
sadly im not on windows. Anyway thnx. i will try and see flashing recovery. Will let you know the result.
Stock recovery.img flash and reboot options->system click.
Reboot to phone on
Parvej789 said:
Stock recovery.img flash and reboot options->system click.
Reboot to phone on
Click to expand...
Click to collapse
got error
```
fastboot flash recovery recovery.img
Sending 'recovery' (39936 KB)
FAILED (Write to device failed (No such device))
fastboot: error: Command failed
``
tried changing cable but no change.
Oky so i had a hunch, and it was correct. i mounted system and didnt get that error.
Thanks buddy. Took me few tries and combination. but now im back with my device. And as guessed, twrp was/is the culprit. It was locking the system or something like this, perhaps a glich? anyway had to mount system and already wrote the command on terminal, so as soon as phone screen turns on, i get to send the data from pc to phone before phone starts doing many of its stuff.
Wipe option->format data -yes
Reboot option-> recovery and Twrp open
1.boot.img flash
2.super.img flash
3.recovery.img flash
Than reboot
Tanzin01 said:
Thanks buddy. Took me few tries and combination. but now im back with my device. And as guessed, twrp was/is the culprit. It was locking the system or something like this, perhaps a glich? anyway had to mount system and already wrote the command on terminal, so as soon as phone screen turns on, i get to send the data from pc to phone before phone starts doing many of its stuff.
Click to expand...
Click to collapse
Build version correct
Your build version
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
You Want Video turorial ?
Cheack This Out;- https://forum.xda-developers.com/t/...stom-rom-installation-video-tutorial.4583503/
Tutorial Install Custom rom Selene
Requirements :
- Unlocked Bootloader
- PC / Laptop with working adb fastboot, SP Flash Tools
- recovery and fastboot MIUI Stock ROM ( ID, EEA, Global, CN, Taiwan / pick one that work, or your currently ROM Version )
- put your recovery miui ROM & custom rom to Microsd / OTG
How To : (If you never update OTA then go STEP 1, else go STEP 2)
- BACKUP YOUR IMEI FIRST (on twrp and backup it to another storage or cloud)
STEP 1
- boot to fastboot mode
- flash twrp / ofox command type on minimal adb fastboot "fastboot flash boot nametwrpfile.img" (make sure the twrp file on same folder at the minimal adb fastboot folder)
- press vol + & power
- Format Data
- Yes
- install / flash MIUI Recovery rom, check reflash TWRP / OFOX
- reboot to "BOOTLOADER"
After reboot to bootloader,Device will be in fastboot.
- flash vbmeta " fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img " (make sure the twrp file on same folder at the minimal adb fastboot folder)
- reboot "fastboot reboot " ( if success booting up to system go to STEP 2, if not success, read again from start )
STEP 2
- no need to setup anything, you can skip all that MIUI Setup
- reboot to twrp recovery, press vol + & power
- Format Data
-Yes
- install / flash Custom rom with check automatically reflash TWRP after flashing a ROM checked
- reboot ( If you skipped STEP 1 and not booting, back to fastboot or TWRP, then Go to STEP 1 first, if can't boot to either TWRP / Fastboot, Then you need MTK Bypass + SP Flash Tool)
- ( If you DONE STEP 1 but still no luck check SPECIAL CASE )
- DONE
SPECIAL CASE
if your phone bootloop on mi logo, then do:
- reboot to twrp/recovery, press vol + & power (wait it, be patient)
-If not boot on TWRP, Go to Fastboot
-Reflash TWRP [fastboot flash boot twrp.img]
-Now Boot in to TWRP
- install image boot.img on boot partition from miui rom you have used on first step (see above)
- reflash twrp, install image twrp.img on recovery ramdisk
- [Even if you go to TWRP Without Reflashing again,you still need to flash boot.img on boot and twrp on ramdisk]
- reboot system
- setup phone with ur mobile internet data (if the custom rom have gapps), cause ur wifi bluetooth hotspot are died
- go to twrp again, install custom kernel to fix bug wifi hotspot bluetooth (but u can't instal yukina starlight, it will make bootloop, use another I Will Recomend Yukina Stamine)
- done u can reboot system
N.B. - If You are in MIUI 13,Then it will won't Work,First Downgrade to MIUI 12.5.xx
N.B. - Just Do Normal Format,Dont Wipe like Delvik,cache,System,Vendor etc.
N.B. - Try To Take All Files(Twrp.img,boot.img,miui recovery.zip,Custom rom zip, custom kernel.zip) In your Memory card and Avoid Use OTG
{
"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"
}
not working in my device
fastboot flash boot twrp.img
my device went in bootloop
i have also tried
Fastboot boot twrp.img
this is throwing " status read failed (too many links)
(also tried with downgrading to MIUI-12 but no success)
Then i tried to boot into fastbootD mode.
with command "Fastboot reboot fastboot"
Now my device is in the infinite boot loop.
Please help
Is that Redmi 10 Selene ?
And Which twrp you used ?
Neelthegamer007 said:
Is that Redmi 10 Selene ?
And Which twrp you used ?
Click to expand...
Click to collapse
is its redmi 10 selene
and i have used twrp you placed here
NOOBOHOLIC said:
is its redmi 10 selene
and i have used twrp you placed here
Click to expand...
Click to collapse
Install miui 12.5.** with fastboot rom,and then unlock bootloader or if its unlocked then disable security by flashing vbmeta.img , comand on post.
Then flash TWRP
fastboot flash boot [space] drag and drop twrp.img file,after flashing reboot your device by holding power button.
Neelthegamer007 said:
Install miui 12.5.** with fastboot rom,and then unlock bootloader or if its unlocked then disable security by flashing vbmeta.img , comand on post.
Then flash TWRP
fastboot flash boot [space] drag and drop twrp.img file,after flashing reboot your device by holding power button.
Click to expand...
Click to collapse
But nothing is working now its just stucked in the bootloop
not booting into recovery
not booting into fastboot
how i do it further
You need SP flash tool, and mtk auth bypass just download it, bypass mtk auth and go to sp flash tool, on auth file section select mtk scatter file from miui fastboot rom/images folder, and on sp flash tool un select every file except boot or boot.img
And click the download button [ must be sure that you need to only download the boot.img file,no other file.]
After download,you can go fastboot
If you can't understand
Get help from YouTube.
I only want root. Is it better to install magisk from this twrp(After downgrading). Or staying in miui 13 & flashing patched boot image?
Tawsif999 said:
I only want root. Is it better to install magisk from this twrp(After downgrading). Or staying in miui 13 & flashing patched boot image?
Click to expand...
Click to collapse
If you only root,then take miui 13 rom's fastboot file and extract boot.img, patch with magisk anf flash vbmeta 1st and then patched boot.img eith adb, enough
Tawsif999 said:
I only want root. Is it better to install magisk from this twrp(After downgrading). Or staying in miui 13 & flashing patched boot image?
Click to expand...
Click to collapse
Downgrade is not nessesery with only root
Neelthegamer007 said:
If you only root,then take miui 13 rom's fastboot file and extract boot.img, patch with magisk anf flash vbmeta 1st and then patched boot.img eith adb, enough
Click to expand...
Click to collapse
Are you sure I need the fastboot rom only. Because I'm already downloading a recovery rom.
And after downloading I have to flash the vbmeta.img before flashing patched boot image? But why? vbmeta is already included in the rom. Can you please explain this.
Tawsif999 said:
Are you sure I need the fastboot rom only. Because I'm already downloading a recovery rom.
And after downloading I have to flash the vbmeta.img before flashing patched boot image? But why? vbmeta is already included in the rom. Can you please explain this.
Click to expand...
Click to collapse
You need to flash vbmeta for disabled verified boot, otherwise patched boot.img is not verified,so flashing patched boot.img will be fail or will be cause of a bootloop
And as i know on recovery rom you won't get the boot.img file,but i,m not sure if you got on recovery rom then it's also file,i will work,and i,m 100 % sure, and vbmeta is inside the rom for enable verified boot,but you need to disable it to flash patched boot img file,its necessary for most of the devices,but in some device, its not necessary,but why would you take risk of a unwanted bootloop?
Disable vbmeta command
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
Any other query's ?, just reply....
Neelthegamer007 said:
You need to flash vbmeta for disabled verified boot, otherwise patched boot.img is not verified,so flashing patched boot.img will be fail or will be cause of a bootloop
And as i know on recovery rom you won't get the boot.img file,but i,m not sure if you got on recovery rom then it's also file,i will work,and i,m 100 % sure, and vbmeta is inside the rom for enable verified boot,but you need to disable it to flash patched boot img file,its necessary for most of the devices,but in some device, its not necessary,but why would you take risk of a unwanted bootloop?
Disable vbmeta command
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
Any other query's ?, just reply....
Click to expand...
Click to collapse
Thank you very much. I thought I have to flash using fastboot flash vbmeta vbmeta.img. But now I can understand, the command is not for flashing. It's for disabling verification.
Tawsif999 said:
You are most welcome
Click to expand...
Click to collapse
can you tell me more for install custom rom i try 5days and 50time bootloop please help
Teaykhuad said:
can you tell me more for install custom rom i try 5days and 50time bootloop please help
Click to expand...
Click to collapse
Sure,are you active right now ? Reply again,i eill give you my telegram..
yes i trying to booting now i dm you
Teaykhuad said:
yes i trying to booting now i dm you
Click to expand...
Click to collapse
How's your experience?
Neelthegamer007 said:
How's your experience?
Click to expand...
Click to collapse
Good bro You teach me to flash custom rom and pixel expirence is not bad but im go to miui and install https://forum.xda-developers.com/t/ultra-rooted-miui-package.4487967/ this for speed and fast animation
Neelthegamer007 said:
Tutorial Install Custom rom Selene
Requirements :
- Unlocked Bootloader
- PC / Laptop with working adb fastboot, SP Flash Tools
- recovery and fastboot MIUI Stock ROM ( ID, EEA, Global, CN, Taiwan / pick one that work, or your currently ROM Version )
- put your recovery miui ROM & custom rom to Microsd / OTG
How To : (If you never update OTA then go STEP 1, else go STEP 2)
- BACKUP YOUR IMEI FIRST (on twrp and backup it to another storage or cloud)
STEP 1
- boot to fastboot mode
- flash twrp / ofox command type on minimal adb fastboot "fastboot flash boot nametwrpfile.img" (make sure the twrp file on same folder at the minimal adb fastboot folder)
- press vol + & power
- Format Data
- Yes
- install / flash MIUI Recovery rom, check reflash TWRP / OFOX
- reboot to "BOOTLOADER"
After reboot to bootloader,Device will be in fastboot.
- flash vbmeta " fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img " (make sure the twrp file on same folder at the minimal adb fastboot folder)
- reboot "fastboot reboot " ( if success booting up to system go to STEP 2, if not success, read again from start )
STEP 2
- no need to setup anything, you can skip all that MIUI Setup
- reboot to twrp recovery, press vol + & power
- Format Data
-Yes
- install / flash Custom rom with check automatically reflash TWRP after flashing a ROM checked
- reboot ( If you skipped STEP 1 and not booting, back to fastboot or TWRP, then Go to STEP 1 first, if can't boot to either TWRP / Fastboot, Then you need MTK Bypass + SP Flash Tool)
- ( If you DONE STEP 1 but still no luck check SPECIAL CASE )
- DONE
SPECIAL CASE
if your phone bootloop on mi logo, then do:
- reboot to twrp/recovery, press vol + & power (wait it, be patient)
-If not boot on TWRP, Go to Fastboot
-Reflash TWRP [fastboot flash boot twrp.img]
-Now Boot in to TWRP
- install image boot.img on boot partition from miui rom you have used on first step (see above)
- reflash twrp, install image twrp.img on recovery ramdisk
- [Even if you go to TWRP Without Reflashing again,you still need to flash boot.img on boot and twrp on ramdisk]
- reboot system
- setup phone with ur mobile internet data (if the custom rom have gapps), cause ur wifi bluetooth hotspot are died
- go to twrp again, install custom kernel to fix bug wifi hotspot bluetooth (but u can't instal yukina starlight, it will make bootloop, use another I Will Recomend Yukina Stamine)
- done u can reboot system
N.B. - If You are in MIUI 13,Then it will won't Work,First Downgrade to MIUI 12.5.xx
N.B. - Just Do Normal Format,Dont Wipe like Delvik,cache,System,Vendor etc.
N.B. - Try To Take All Files(Twrp.img,boot.img,miui recovery.zip,Custom rom zip, custom kernel.zip) In your Memory card and Avoid Use OTG
View attachment 5793645
Click to expand...
Click to collapse
How do I restore WiFi and Bluetooth after flashing