Related
Hi guys,
I have a problem with install recovery on my Nexus S. When I'm in the command promt and I typed cmd. Then when I must type ""fastboot flash recovery ...img" it don't work anymore. I've downloaded the newest recovery from here: http://forum.xda-developers.com/showthread.php?t=988686
The file is in my download folder and called "5023-green.img". When I'm in the command promt and go into the download folder and then type "fastboot flash recovery 5023-green.img" it gives an error. It don't recocnize the file
I hope it is clear to understand because it's hard to explain My phone is unlocked and is in fastboot.
giganielsie said:
Hi guys,
I have a problem with install recovery on my Nexus S. When I'm in the command promt and I typed cmd. Then when I must type ""fastboot flash recovery ...img" it don't work anymore. I've downloaded the newest recovery from here: http://forum.xda-developers.com/showthread.php?t=988686
The file is in my download folder and called "5023-green.img". When I'm in the command promt and go into the download folder and then type "fastboot flash recovery 5023-green.img" it gives an error. It don't recocnize the file
I hope it is clear to understand because it's hard to explain My phone is unlocked and is in fastboot.
Click to expand...
Click to collapse
put both fastboot.exe and the recovery.img file in the same folder (for example c:/flash) then open cmd and navigate to that folder, you should see in the command line something like c:/fash/. Now you can do fastboot flash recovery recoveryname.img
Probably you don't have fastboot added to the path or you're not pointing to the correct folder where the recovery image is.
DeuXGod said:
put both fastboot.exe and the recovery.img file in the same folder (for example c:/flash) then open cmd and navigate to that folder, you should see in the command line something like c:/fash/. Now you can do fastboot flash recovery recoveryname.img
Probably you don't have fastboot added to the path or you're not pointing to the correct folder where the recovery image is.
Click to expand...
Click to collapse
Thanks for youre reply but still get the error. I've downloaded a tool package from here: http://www.mediafire.com/?wj0kbm0dooa5wsd
In this package is a fastboot.exe file. I put this file with the 5023-green.img in the same folder but still get error
giganielsie said:
Thanks for youre reply but still get the error. I've downloaded a tool package from here: http://www.mediafire.com/?wj0kbm0dooa5wsd
In this package is a fastboot.exe file. I put this file with the 5023-green.img in the same folder but still get error
Click to expand...
Click to collapse
I use the Android SDK, it has the updated fastboot tool. Anyway are you rooted already? If you're just get the Rom Manager from the market and install CWM from there. If not, try to get the android SDK from here:
http://developer.android.com/sdk/index.html
Install it (make sure that you also have java SE installed) to, let's say, C:/androidsdk
It will prompt you to open the Android SDK manager, say yes, select platform tools and hit download
Now in c:/androidsdk/platform-tools you will have fastboot.exe
Download the recovery from http://www.clockworkmod.com/rommanager to the platform-tools folder
Put your phone in fastboot (volume up+power on)
then open the cmd, navigate to c:/androidsdk/platform-tools and do fastboot devices, it should show you the SN from your nexus. If it doesn't show, then you need to update your ADB driver. You can get it from the Android SDK Manager in the extras.
Now do fastboot flash recovery recoveryname.img
Should work now
DeuXGod said:
I use the Android SDK, it has the updated fastboot tool. Anyway are you rooted already? If you're just get the Rom Manager from the market and install CWM from there. If not, try to get the android SDK from here:
http://developer.android.com/sdk/index.html
Install it (make sure that you also have java SE installed) to, let's say, C:/androidsdk
It will prompt you to open the Android SDK manager, say yes, select platform tools and hit download
Now in c:/androidsdk/platform-tools you will have fastboot.exe
Download the recovery from http://www.clockworkmod.com/rommanager to the platform-tools folder
Put your phone in fastboot (volume up+power on)
then open the cmd, navigate to c:/androidsdk/platform-tools and do fastboot devices, it should show you the SN from your nexus. If it doesn't show, then you need to update your ADB driver. You can get it from the Android SDK Manager in the extras.
Now do fastboot flash recovery recoveryname.img
Should work now
Click to expand...
Click to collapse
Thanks for youre explanation!
I think my ADB driver must have an update because when I type in the command promt c"/androidsdk/platform-tools>fastboot devices he says: "can not find the specified path".
In the Android SDK manager in extras is not shows any ADB driver? I have installed the Google USB Driver and the Google Web Driver in extras but which other file must I download?
giganielsie said:
Thanks for youre explanation!
I think my ADB driver must have an update because when I type in the command promt c"/androidsdk/platform-tools>fastboot devices he says: "can not find the specified path".
In the Android SDK manager in extras is not shows any ADB driver? I have installed the Google USB Driver and the Google Web Driver in extras but which other file must I download?
Click to expand...
Click to collapse
The google USB driver is the ADB driver. If you go into your Device manager in windows, with your Nexus in fastboot and connected to the PC, can you see a ADB device? Or do you see a yellow exclamation mark? You sure you're in the androidsdk folder in the command prompt?
Let's try a different thing. Copy adb.exe, fastboot.exe and AdbWinApi.dll to C:/windows/system32
Reboot just in case and try to do again fastboot devices from the cmd
Should work now
DeuXGod said:
The google USB driver is the ADB driver. If you go into your Device manager in windows, with your Nexus in fastboot and connected to the PC, can you see a ADB device? Or do you see a yellow exclamation mark? You sure you're in the androidsdk folder in the command prompt?
Let's try a different thing. Copy adb.exe, fastboot.exe and AdbWinApi.dll to C:/windows/system32
Reboot just in case and try to do again fastboot devices from the cmd
Should work now
Click to expand...
Click to collapse
Also don't work
This is the error:
{
"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"
}
In that folder are all of the files I needed so it should work though he don't work
And my phone also recognize as Android ADB Interface.
Edit: It's working!!! My brother fixed it! Thanks for the replies!!!:good::victory:
Now I have recovery but now I have another problem. When I reboot my phone, I can't go anymore to recovery. I see then a green android with a open stomach. Anybody a solution? It looks like there is something went wrong with the install of the recovery but what?
And I have root permission now but with rom manager I can install recovery but when I reboot into recovery, the green android with open stomach come back...
Stock ROM? Delete /system/etc/install-recovery.sh, flash CWM again and that's it.
Sent from my Nexus S using xda app-developers app
DeuXGod said:
Stock ROM? Delete /system/etc/install-recovery.sh, flash CWM again and that's it.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Thanks!!! It looks like it works! Thanks for youre fast replies:good::good:
I didn't want to create another thread because I am somewhat having the same problem and I really don't know what to do. I have an M200 version on T-Mobile USA and I got the JB OTA yesterday and everything was running fine until, about 30 mins ago. The phone slowed down and the started to reboot and it keeps rebooting sometimes into safe mode. I took out the battery and tried the recovery mode, but this is what I get.
GripR said:
I didn't want to create another thread because I am somewhat having the same problem and I really don't know what to do. I have an M200 version on T-Mobile USA and I got the JB OTA yesterday and everything was running fine until, about 30 mins ago. The phone slowed down and the started to reboot and it keeps rebooting sometimes into safe mode. I took out the battery and tried the recovery mode, but this is what I get.
Click to expand...
Click to collapse
Do you have unlocked bootloader? If you have just flash CWM from the fastboot, enter in recovery and do a full wipe and install another ROM or even the stock image. Don't forget to remove the system/etc/install-recovery.sh file if you flash the stock ROM so CWM won't be overwritten every time you do a reboot.
DeuXGod said:
Stock ROM? Delete /system/etc/install-recovery.sh, flash CWM again and that's it.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
from the dead droid reboot with power+ vol up
enter jb and with a file manager (like es file..or something else) delete both:
-/system/recovery-from-boot.p
-/system/etc/install-recovery.sh
reboot and reinstall cwm via fastboot
Only problem with that is he will require root access to do that.
Which I am assuming he currently doesn't have.
Anyways as someone already stated. Unlock bootloader if it isn't already. That will wipe your data off the phone.
Boot or flash a custom recovery.
Flash su.zip or supersu etc to get root
Boot up and make sure you actually have root.
Do as above poster said and remove those files.
Either flash recovery from a app like goo manager or rom manager. Hell now that that I think about it. I think rom manger has the option to remove those files for you when it flashes cwm. Or reboot into the bootloader and flash the recovery with fastboot. It will stick. Keep in mind that you need to download the fastboot version of the recovery if you go that route. It will be a .img. the others will be a .zip .
If you don't know how to use fastboot. Read the quides/stickies etc.
Hi guys,
On this post I will share with you a method to root Wiko Jerry.
You will get a TWRP recovery installed too.
Sorry if my english is a bit bad
Sorry if the print screens if you find are in Portuguese, as it would be boring to change my Windows language.
DISCLAIMER:
I AM NOT responsible for bricked devices and lost warranties.
If you don't feel safe modifying your device DO NOT do anything.
Backup the data you have on your phone. Accidents can happen.
That said, let's go to the fun!
What you need:
Your Wiko Jerry
This TWRP 3.1.1 recovery: https://mega.nz/#!rZM2XIhY!tuneB9pGNQzhbGWz1kRY-mzeCGtRjUAP2QqX791r4Go
ADB / Fastboot on your computer. I will explain how to set it up on your PC later.
Magisk flashable ZIP. Magisk thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Connect your phone to your PC with your USB cable.
1- Preparing your PC:
If you already have ADB on your PC, you can skip this part.
After downloaded the files you need, let's get your computer ready.
You will need fastboot and ADB for this method, so download from here:
Installing ADB on Windows:
Open this link and click on SDK Platform-tools for Windows.
After downloaded, extract the ZIP anywhere you want.
You should now have a folder like this:
{
"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"
}
Keep the folder open (or just minimize it) and go ahead to the next step.
Installing ADB on Linux:
Run one of this commands on your terminal.
-Ubuntu/Debian based Linuxes (APT):
Code:
sudo apt install android-tools-adb android-tools-fastboot
-Fedora (YUM):
Code:
sudo yum install android-tools
Test with:
Code:
sudo adb version
You should get something like this:
Code:
Android Debug Bridge version 1.0.40
Version 4986621
2- Getting your phone ready:
To get your phone ready you need to enable ADB on Settings.
Open Settings>About phone and tap "Buid number" 7 times.
Go back one time and you sholud get a "Developer options" menu on Settings.
Open the "Developer options" and enable "USB debugging" option.
Now you have ADB enabled on your device.
3- Installing TWRP on your phone
Do you remember the TWRP file you downloaded before? Now you will need it.
-Copy the TWRP_3.1_JERRY.img file to your platform-tools folder.
-Rename the file to recovery.img.
-Open a command prompt.
-On command prompt do this to open your platform-tools folder on it:
Code:
cd INSERT PATH TO YOUR platform-tools FOLDER
Now, unlock your phone and run this command:
Code:
adb devices
It should appear something like this on your PC:
Code:
List of devices attached
<your-device-id> offline
And this on your phone:
On that window, check the box and tap OK. This will allow your phone to communicate with ADB running on your PC.
Check if everything is ok doing the "adb devices" command again. If it is ok, this will show up:
Code:
List of devices attached
<your-device-id> device
Now, on your command line run the command:
Code:
adb reboot-bootloader
Your phone will reboot in fastboot mode. It should look like this:
Run this on your command line:
Code:
fastboot flash recovery recovery.img
If you get <waiting-for-device> on command prompt, check this:
-Open Device Manager (Win key+X, click on Device Manager)
-Find a device called "fastboot Gadget" or similar name with a exclamation mark.
-Right click it and click on "Update drivers..."
-Click on second option on the setup (search manually)
-Click on the second option again.
-On the list, look for Universal Serial Bus Devices and double click it
-Inside the Manufacturer list select WinUsb Device
-On the right list select ADB Device and double click it
-Click on yes
-After installed, close and its fixed!
When the command finishes, you should get this:
Code:
Sending 'recovery' (12866 KB) OKAY [ 0.550s]
Writing 'recovery' OKAY [ 0.762s]
Finished. Total time: 1.317s
Congratulations! Now you have TWRP on your phone!
4- Booting into TWRP and root the phone with Magisk
Now you need to turn off your phone. You can just take the battery out and put it again.
This phone has a weird way to boot into the recovery. You need to press the power button and a second later, the VOL+ button.
The Wiko logo will appear and the phone MUST NOT VIBRATE. If it vibrates, the normal Android will start.
Do this procedure anytime you want to go into TWRP.
Connect your USB cable.
Tap "Keep Read Only"
In your PC, go to This PC and open the JERRY device.
Copy the previously downloaded Magisk ZIP file into the Internal Storage.
In TWRP, tap Install
Search for the Magisk ZIP in the file explorer.
Swipe to confirm the flash
Tap Home button
Tap Reboot
Tap System
Android should boot normally
Warning: It could take a few seconds to Magisk Manager to appear on apps list.
Congratulations! You have done it! You have TWRP and Magisk!
help
i always get error remote replacing recovery not allowed something like that
what should i do
edit : its this error
remote: 'download for partition 'recovery' is not allowed
GnarlyBuzzard50 said:
i always get error remote replacing recovery not allowed something like that
what should i do
edit : its this error
remote: 'download for partition 'recovery' is not allowed
Click to expand...
Click to collapse
hey you'll need to unlock your bootloader first
FIRST BACKUP EVERYTHING USEFUL FROM YOUR PHONE, THI WILL FACTORY RESET YOUR DEVICE
after getting adb working (debug on and all that stuff)
enter in your cmd prompt
Code:
adb reboot bootloader
then wait till your phone is in fastboot mode
now you'll type in cmd
Code:
fastboot flashing unlock
read carefully what appears in your phone screen and accapt it (at your own risk, it will probably void your warranty)
now type in cmd
Code:
fastboot reboot
done
TWRP file is not working
Code:
fastboot flashing unlock
Click to expand...
Click to collapse
I get "Unlock Failed"
When I try to enter recovery mode, it says: no command
is this recovery image meant for the SPD or the MTK variant?
Tried this on an SPD Jerry & it didn't work
Any other help?
KitK4t said:
Hi guys,
On this post I will share with you a method to root Wiko Jerry.
You will get a TWRP recovery installed too.
Sorry if my english is a bit bad
Sorry if the print screens if you find are in Portuguese, as it would be boring to change my Windows language.
DISCLAIMER:
I AM NOT responsible for bricked devices and lost warranties.
If you don't feel safe modifying your device DO NOT do anything.
Backup the data you have on your phone. Accidents can happen.
That said, let's go to the fun!
What you need:
Your Wiko Jerry
This TWRP 3.1.1 recovery: https://mega.nz/#!rZM2XIhY!tuneB9pGNQzhbGWz1kRY-mzeCGtRjUAP2QqX791r4Go
ADB / Fastboot on your computer. I will explain how to set it up on your PC later.
Magisk flashable ZIP. Magisk thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Connect your phone to your PC with your USB cable.
1- Preparing your PC:
If you already have ADB on your PC, you can skip this part.
After downloaded the files you need, let's get your computer ready.
You will need fastboot and ADB for this method, so download from here:
Installing ADB on Windows:
Open this link and click on SDK Platform-tools for Windows.After downloaded, extract the ZIP anywhere you want.You should now have a folder like this:
Keep the folder open (or just minimize it) and go ahead to the next step.
Installing ADB on Linux:
Run one of this commands on your terminal.-Ubuntu/Debian based Linuxes (APT):
Code:
sudo apt install android-tools-adb android-tools-fastboot
-Fedora (YUM):
Code:
sudo yum install android-tools
Test with:
Code:
sudo adb version
You should get something like this:
Code:
Android Debug Bridge version 1.0.40[/INDENT]
[INDENT]Version 4986621
2- Getting your phone ready:
To get your phone ready you need to enable ADB on Settings.
Open Settings>About phone and tap "Buid number" 7 times.
Go back one time and you sholud get a "Developer options" menu on Settings.
Open the "Developer options" and enable "USB debugging" option.
Now you have ADB enabled on your device.
3- Installing TWRP on your phone
Do you remember the TWRP file you downloaded before? Now you will need it.
-Copy the TWRP_3.1_JERRY.img file to your platform-tools folder.
-Rename the file to recovery.img.
-Open a command prompt.
-On command prompt do this to open your platform-tools folder on it:
Code:
cd INSERT PATH TO YOUR platform-tools FOLDER
Now, unlock your phone and run this command:
Code:
adb devices
It should appear something like this on your PC:
Code:
List of devices attached
<your-device-id> offline
And this on your phone:
On that window, check the box and tap OK. This will allow your phone to communicate with ADB running on your PC.
Check if everything is ok doing the "adb devices" command again. If it is ok, this will show up:
Code:
List of devices attached
<your-device-id> device
Now, on your command line run the command:
Code:
adb reboot-bootloader
Your phone will reboot in fastboot mode. It should look like this:
Run this on your command line:
Code:
fastboot flash recovery recovery.img
If you get <waiting-for-device> on command prompt, check this:
-Open Device Manager (Win key+X, click on Device Manager)-Find a device called "fastboot Gadget" or similar name with a exclamation mark.-Right click it and click on "Update drivers..."-Click on second option on the setup (search manually)-Click on the second option again.-On the list, look for Universal Serial Bus Devices and double click it-Inside the Manufacturer list select WinUsb Device-On the right list select ADB Device and double click it-Click on yes-After installed, close and its fixed!
When the command finishes, you should get this:
Code:
Sending 'recovery' (12866 KB) OKAY [ 0.550s]
Writing 'recovery' OKAY [ 0.762s]
Finished. Total time: 1.317s
Congratulations! Now you have TWRP on your phone!
4- Booting into TWRP and root the phone with Magisk
Now you need to turn off your phone. You can just take the battery out and put it again.
This phone has a weird way to boot into the recovery. You need to press the power button and a second later, the VOL+ button.
The Wiko logo will appear and the phone MUST NOT VIBRATE. If it vibrates, the normal Android will start.
Do this procedure anytime you want to go into TWRP.
Connect your USB cable.
Tap "Keep Read Only"
In your PC, go to This PC and open the JERRY device.
Copy the previously downloaded Magisk ZIP file into the Internal Storage.
In TWRP, tap Install
Search for the Magisk ZIP in the file explorer.
Swipe to confirm the flash
Tap Home button
Tap Reboot
Tap System
Android should boot normally
Warning: It could take a few seconds to Magisk Manager to appear on apps list.
Congratulations! You have done it! You have TWRP and Magisk!
Click to expand...
Click to collapse
<thanks man, worked fine for me.
just like he says...
adb reboot-bootloader
fastboot flash recovery <pathoftherenamedTWRP.img>
Take the battery out, back in
press and hold start button, sec later vol down button too
Now TWRP should start
read only
transfer the magisk.zip file to internal storage(PC)
install button(TWRP, Smartphone)
tap on the magisk.zip file and swipe to accept
wait till its done
press on reboot
done
Zaki4t said:
is this recovery image meant for the SPD or the MTK variant?
Tried this on an SPD Jerry & it didn't work
Any other help?
Click to expand...
Click to collapse
Worked for me. Where can i see which i have. maybe i can help
z0mb13m4ch1n3 said:
Worked for me. Where can i see which i have. maybe i can help
Click to expand...
Click to collapse
and if you messed up(like I do in my first try) here...
Wiko Mobile: Kundenbereich / Verbindung.
customer-de.wikomobile.com
take out the battery, theres the imei number
youll download a .exe file. stressed me in linux and lend a win 7 laptop. 5min or so and i had a factory fresh jerry to try again
The problem is there is no WinUsb there i dont have it.
Hi, I have a big trouble i followed all the instructions and everything was just fine, until the step 4- Booting into TWRP and root the phone with Magisk, after a take out and put the battery again in the cell, it doesn't boot from logo, just reset an reset, I already try o hard reset, try to enter TWRP, I try all kind of button combination, nothing works can someone helpme. Thks...
Hi,
I am in huge trouble. I bought this phone 2 weeks ago and 2 days ago installed android Q. This was mistake because after a some time phone was going to something called "Qualcomm dump mode" and that was it. Only thing to do was wait to battery goes down and restart.
So, I tried to go back, nothing from official ways works so I decided to go with TWRP and unblocking bootloader. And now I think I totally bricked my phone...
After command: "fastboot boot flash twrp.img" my phone only is restarting to this:
{
"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"
}
( I don't know how to insert picture here)
Is it can be saved?? Or I screwed up all the way? Anyway thank you in advance for any kind of help.
My phone details:
Oneplus 7 pro ver. GM1910
you need the drivers id believe and in device manager on pc what you show is mtp with ! orob delete that restart device get drivers
I had the same. You can install the rom again via fastboot with Guac recovery (search on this forum)
Solex49 said:
I had the same. You can install the rom again via fastboot with Guac recovery (search on this forum)
Click to expand...
Click to collapse
I am getting:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.946s
Click to expand...
Click to collapse
ecompton59 said:
you need the drivers id believe and in device manager on pc what you show is mtp with ! orob delete that restart device get drivers
Click to expand...
Click to collapse
I kinda don't understand. And I no longer can find my device in Device manager
@edit
Also I have this info:
Connect your phone to your computer in Fastboot mode
Ensure you have installed the drivers for the phone : https://www.androidfilehost.com/?fid=3556969557455274390 (I've uploaded the drivers from Android 10 Open Beta 1 here too : https://www.androidfilehost.com/?fid=1899786940962579686)
Open a command window in the folder that the fastboot/adb tools have been installed to (By default the OnePlus drivers install those here : C:\Program Files (x86)\OnePlus USB Drivers\Android )
Enter the command fastboot devices
If you see a result from that command then the computer can see the phone correctly, if it's a blank line then it can't. In that case, try another usb port or cable.
Go here : https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Download the relevant package for the version you want to use
Extract the package and then run the flash-all.bat file
The script will then apply all default partitions for the version you have specified, this will wipe your data partition on the phone but, if you couldn't get into the phone in the first place, that's no big deal.
For good measure, once you have completed the install go into recovery and wipe the cache partition, I would actually use the factory default wipe option to start completely from scratch
Bear in mind though, you will still have an unlocked bootloader, to lock the bootloader again you would need to go into the developer settings and lock it and use the oem lock command
If you really want TWRP/Magisk back in then you'll likely need to use my workaround from here : https://forum.xda-developers.com/showpost.php?p=79961624&postcount=1210
Just use the fastboot getvar current-slot and fastboot set_active a or fastboot set_active b to track the active boot partition, that's very important for situations where the phone isn't booting correctly, a lot of the time it will be because you have the incorrect active slot enabled, in that case use the set_active command and the fastboot reboot command.
I would definitely recommend getting a usb drive you can use with the phone, there was an issue where TWRP couldn't see storage sometimes due to the difference between Android 9/10, using a usb drive to host the files you wanted to flash would help bystep encryption issues as the usb drive isn't encrypted.
I personally use these :
USB C to USB 3.0 Male Adapter : https://www.amazon.co.uk/gp/product/B07KXHNY5F
SanDisk Ultra USB Type-C 16 GB up to 130 MB/s USB 3.1 Flash Drive : https://www.amazon.co.uk/gp/product/B01BUSMYHC
When you use the drive it will make an "Android" folder, just throw your stuff in there, when you go to Install in TWRP you'll have a "SELECT STORAGE" button on the bottom left, that will let you use the usb drive, If you're using the File Manager in TWRP then it's listed under "usbstorage" in the main list.
djsubterrain said:
Connect your phone to your computer in Fastboot mode
Ensure you have installed the drivers for the phone : https://www.androidfilehost.com/?fid=3556969557455274390 (I've uploaded the drivers from Android 10 Open Beta 1 here too : https://www.androidfilehost.com/?fid=1899786940962579686)
Open a command window in the folder that the fastboot/adb tools have been installed to (By default the OnePlus drivers install those here : C:\Program Files (x86)\OnePlus USB Drivers\Android )
Enter the command fastboot devices
If you see a result from that command then the computer can see the phone correctly, if it's a blank line then it can't. In that case, try another usb port or cable.
Go here : https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Download the relevant package for the version you want to use
Extract the package and then run the flash-all.bat file
The script will then apply all default partitions for the version you have specified, this will wipe your data partition on the phone but, if you couldn't get into the phone in the first place, that's no big deal.
For good measure, once you have completed the install go into recovery and wipe the cache partition, I would actually use the factory default wipe option to start completely from scratch
Bear in mind though, you will still have an unlocked bootloader, to lock the bootloader again you would need to go into the developer settings and lock it and use the oem lock command
If you really want TWRP/Magisk back in then you'll likely need to use my workaround from here : https://forum.xda-developers.com/showpost.php?p=79961624&postcount=1210
Just use the fastboot getvar current-slot and fastboot set_active a or fastboot set_active b to track the active boot partition, that's very important for situations where the phone isn't booting correctly, a lot of the time it will be because you have the incorrect active slot enabled, in that case use the set_active command and the fastboot reboot command.
I would definitely recommend getting a usb drive you can use with the phone, there was an issue where TWRP couldn't see storage sometimes due to the difference between Android 9/10, using a usb drive to host the files you wanted to flash would help bystep encryption issues as the usb drive isn't encrypted.
I personally use these :
USB C to USB 3.0 Male Adapter : https://www.amazon.co.uk/gp/product/B07KXHNY5F
SanDisk Ultra USB Type-C 16 GB up to 130 MB/s USB 3.1 Flash Drive : https://www.amazon.co.uk/gp/product/B01BUSMYHC
When you use the drive it will make an "Android" folder, just throw your stuff in there, when you go to Install in TWRP you'll have a "SELECT STORAGE" button on the bottom left, that will let you use the usb drive, If you're using the File Manager in TWRP then it's listed under "usbstorage" in the main list.
Click to expand...
Click to collapse
Unfortunately, it is not working and I read that: These ROMs can't be used to update or downgrade your phone but just to restore your phone[...].
I am, I think, I am, at andorid Q and want to back to android 9
Yep, I am getting this:
@edit
Ok, had 100MB free space on my hdd... Sorry about that.
@edit2
Ok, thank You men, I managed to go throgu, but now after booting I have black screen. Should I now try to install some roms?
KramarSenior said:
Unfortunately, it is not working and I read that: These ROMs can't be used to update or downgrade your phone but just to restore your phone[...].
I am, I think, I am, at andorid Q and want to back to android 9
Yep, I am getting this:
@edit
Ok, had 100MB free space on my hdd... Sorry about that.
@edit2
Ok, thank You men, I managed to go throgu, but now after booting I have black screen. Should I now try to install some roms?
Click to expand...
Click to collapse
Due to the change in version you should really go to recovery and do a factory reset. See what happens after reboot then.
djsubterrain said:
Due to the change in version you should really go to recovery and do a factory reset. See what happens after reboot then.
Click to expand...
Click to collapse
Still black screen. At least I have no problems with booting an .img files. Already installed TWRP from offical but when I copied zip file with rom it is not see it.
@edit
Ok, I installed a rom but now phone is still loading (this red dot with 2 white dots running around) and nothing is happaning
djsubterrain said:
Due to the change in version you should really go to recovery and do a factory reset. See what happens after reboot then.
Click to expand...
Click to collapse
Ok, dude, love You, phone is working fine now. Andoid 9, and all I need to to is install updates. Thank You very much for help. I will press "thank you" buttons as soon as I get home.
Thread can be closed.
djsubterrain said:
Connect your phone to your computer in Fastboot mode
Ensure you have installed the drivers for the phone : https://www.androidfilehost.com/?fid=3556969557455274390 (I've uploaded the drivers from Android 10 Open Beta 1 here too : https://www.androidfilehost.com/?fid=1899786940962579686)
Open a command window in the folder that the fastboot/adb tools have been installed to (By default the OnePlus drivers install those here : C:\Program Files (x86)\OnePlus USB Drivers\Android )
Enter the command fastboot devices
If you see a result from that command then the computer can see the phone correctly, if it's a blank line then it can't. In that case, try another usb port or cable.
Go here : https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Download the relevant package for the version you want to use
Extract the package and then run the flash-all.bat file
The script will then apply all default partitions for the version you have specified, this will wipe your data partition on the phone but, if you couldn't get into the phone in the first place, that's no big deal.
For good measure, once you have completed the install go into recovery and wipe the cache partition, I would actually use the factory default wipe option to start completely from scratch
Bear in mind though, you will still have an unlocked bootloader, to lock the bootloader again you would need to go into the developer settings and lock it and use the oem lock command
If you really want TWRP/Magisk back in then you'll likely need to use my workaround from here : https://forum.xda-developers.com/showpost.php?p=79961624&postcount=1210
Just use the fastboot getvar current-slot and fastboot set_active a or fastboot set_active b to track the active boot partition, that's very important for situations where the phone isn't booting correctly, a lot of the time it will be because you have the incorrect active slot enabled, in that case use the set_active command and the fastboot reboot command.
I would definitely recommend getting a usb drive you can use with the phone, there was an issue where TWRP couldn't see storage sometimes due to the difference between Android 9/10, using a usb drive to host the files you wanted to flash would help bystep encryption issues as the usb drive isn't encrypted.
I personally use these :
USB C to USB 3.0 Male Adapter : https://www.amazon.co.uk/gp/product/B07KXHNY5F
SanDisk Ultra USB Type-C 16 GB up to 130 MB/s USB 3.1 Flash Drive : https://www.amazon.co.uk/gp/product/B01BUSMYHC
When you use the drive it will make an "Android" folder, just throw your stuff in there, when you go to Install in TWRP you'll have a "SELECT STORAGE" button on the bottom left, that will let you use the usb drive, If you're using the File Manager in TWRP then it's listed under "usbstorage" in the main list.
Click to expand...
Click to collapse
My current slot is "a" but if I try to use fastboot set_active b or fastboot --set-active=b it shows: usage: fastboot [ <option> ] <command> and shows me all the fastboot commands
also if I try : fastboot boot "recovery_name".img it shows : downloading 'boot.img'...
OKAY [ 2.119s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 2.162s
of course I tried fastboot flash boot "recovery_name".img and it flashes ok but when I try to reboot to recovery the bootloader pops up again
any ideas ?
Maybe try this: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
I'm pleased to report I've successfully done systemless root with MAGISK on the Ulefone Armor 10 5G. Turns out the process is nearly identical to the Armor 8.
My thanks to all contributors to this thread and this one. Here's what worked for me, developed with pieces culled from both.
WHAT YOU'LL NEED:
--The current version of ADB Platform Tools.
--The APK file for MAGISK (Current version, as of this post's date, is 22.0).
--ADB and Fastboot USB drivers. I found my copy here.
--A copy of the Armor 10's current ROM image. This can be had from Ulefone's site (non-EU version). If you need the EU version, use this link.
--A copy of vbmeta_null.img as found here.
HOW TO DO IT:
The usual disclaimers apply; Do this at your own risk, I'm not responsible if you brick or damage your device, or void your warranty, etc. I'm also going to condense the instructions a bit, on the assumption anyone who's serious about rooting already knows the basics.
Unlock your phone's bootloader.
Once you get through the factory initialization again, enable developer options.
Install the ADB platform tools and USB drivers on your PC.
Extract boot.img from the stock ROM download and place it in the same directory as your ADB tools install. Transfer vbmeta_null.bin to the same spot.
Do a sideload install of the Magisk APK file to your phone.
Copy the boot.img file to your phone's local storage using the file transfer method of your choice.
Assuming you survived the above, your phone is now unlocked and ready to root. Proceed as follows:
Open the Magisk app. Click 'Install' for the Magisk Manager app, agree to any prompts, etc.
Next, tick 'Install' for 'Install Magisk' (NOT the manager portion). When prompted for the method, choose 'Select and patch a file.'
Select the 'boot.img' file you transferred to the phone's local storage in step 6 above. Once you do this, the patching process begins on its own.
Magisk will write a root-patched copy, named 'magisk_patched_xxxxx.img,' to the same directory (the X's indicate an alphanumeric string).
Transfer the patched image file back to the ADB tools directory on your PC, with whatever transfer means is comfortable for you.
Now we get to the interesting part. Reboot the phone to fastboot mode, and make sure it's connected to your PC via USB.
Open a command prompt window, on your PC, in the directory your ADB tools are installed.
Type 'fastboot devices' to make sure the system sees your phone.
Assuming all is well, type: 'fastboot flash vbmeta vbmeta_null.img' and hit enter. You should get appropriate responses saying the file was transferred.
Next, type 'fastboot flash boot magisk_patched_xxxxx.img' (naturally, replace the X's with whatever string of characters Magisk supplied).
Assuming no errors, type 'fastboot reboot' and hit enter. Your Armor 10 should now be rooted.
Enjoy!
Happy tweaking.
Hey, thank you for this guide but I'm facing an issue with step 9.
When I try to flash vbmeta_null.img, I'm getting this error "no such file or directory". I tried flashing just magisk but that gives me a bootloop
foumfo said:
Hey, thank you for this guide but I'm facing an issue with step 9.
When I try to flash vbmeta_null.img, I'm getting this error "no such file or directory". I tried flashing just magisk but that gives me a bootloop
Click to expand...
Click to collapse
You're welcome. Did you make sure to put the vbmeta_null.img file in the same directory with your adb and fastboot executables?
kc7gr said:
You're welcome. Did you make sure to put the vbmeta_null.img file in the same directory with your adb and fastboot executables?
Click to expand...
Click to collapse
Yep, I think the error message refers to the phone not having the vbmeta file. But after flashing magisk and rebooting to fastboot, flashing vbmeta works. But I'm still getting a bootloop
The sequence is also important: Install Magisk, flash modified boot.img, flash vbmeta_null. As I understand it, it's the act of installing Magisk which makes it possible to flash vbmeta.
Worst case: Do as I did, look at all available posts and experiment. You can find a sequence which works for you as well.
Stay well...
Did someone try to flash a GSI Rom in the Ulefone Armor 10? I plan to flash Havoc GSI...Has anyone tried if everything is working? Is there also a TWRP Version for this Ulefone?
Hello,
thank you for this Guide. I have Problems unlocking bootloader. "Enable OEM unlock" is set in debeloper settings. I tried "flashing unlock" and "oem unlock". Both give me a "Command failed".
Update: the problem was the USB-driver. The latest version from the web didnt work. Then i use the search-driver-function of windows device-manager. After that it worked.
bd080392 said:
Did someone try to flash a GSI Rom in the Ulefone Armor 10? I plan to flash Havoc GSI...Has anyone tried if everything is working? Is there also a TWRP Version for this Ulefone?
Click to expand...
Click to collapse
Yes. It has and not relesead yet! Need more tests. But you can look here: Some extra informations
Update: TWRP is now ready to use since July 1st. Two users have the file in the 4pda forum. I will not put the file here.
Acetonperoxid said:
Hello,
thank you for this Guide. I have Problems unlocking bootloader. "Enable OEM unlock" is set in debeloper settings. I tried "flashing unlock" and "oem unlock". Both give me a "Command failed".
Update: the problem was the USB-driver. The latest version from the web didnt work. Then i use the search-driver-function of windows device-manager. After that it worked.
Click to expand...
Click to collapse
You need write:
Code:
fastboot flashing unlock
The message appears in the screen. Press Vol+ and wait. Reboot device and you see message about Orange State.. Your device's unlocked!
Acetonperoxid said:
Hello,
thank you for this Guide. I have Problems unlocking bootloader. "Enable OEM unlock" is set in debeloper settings. I tried "flashing unlock" and "oem unlock". Both give me a "Command failed".
Update: the problem was the USB-driver. The latest version from the web didnt work. Then i use the search-driver-function of windows device-manager. After that it worked.
Click to expand...
Click to collapse
I use command for Ulefeno Armor 7
fastboot oem unlock-go
Or
fastboot oem unlock
getting this when I try to push the vbmeta_null.img It is in the directory I'm running the command from
{
"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"
}
@kc7gr thanks for the guide
im getting stuck at step 9
is this guide for EU or Non EU version?
i got fastboot running in Windows 7 rather than 10
is this same did u run it in win 10?
finnd1 said:
getting this when I try to push the vbmeta_null.img It is in the directory I'm running the command from
View attachment 5344503
Click to expand...
Click to collapse
You may have the file in the folder your running the command from, but would that be your adb/fastboot root dir?
Hello. There's little information on XDA for Uleafone phones. I've bought an Uleafone Armor X10 Pro. Could I do the same process as described here to install TWRP on it / flash magisk?
kc7gr said:
I'm pleased to report I've successfully done systemless root with MAGISK on the Ulefone Armor 10 5G. Turns out the process is nearly identical to the Armor 8.
My thanks to all contributors to this thread and this one. Here's what worked for me, developed with pieces culled from both.
WHAT YOU'LL NEED:
--The current version of ADB Platform Tools.
--The APK file for MAGISK (Current version, as of this post's date, is 22.0).
--ADB and Fastboot USB drivers. I found my copy here.
--A copy of the Armor 10's current ROM image. This can be had from Ulefone's site (non-EU version). If you need the EU version, use this link.
--A copy of vbmeta_null.img as found here.
HOW TO DO IT:
The usual disclaimers apply; Do this at your own risk, I'm not responsible if you brick or damage your device, or void your warranty, etc. I'm also going to condense the instructions a bit, on the assumption anyone who's serious about rooting already knows the basics.
Unlock your phone's bootloader.
Once you get through the factory initialization again, enable developer options.
Install the ADB platform tools and USB drivers on your PC.
Extract boot.img from the stock ROM download and place it in the same directory as your ADB tools install. Transfer vbmeta_null.bin to the same spot.
Do a sideload install of the Magisk APK file to your phone.
Copy the boot.img file to your phone's local storage using the file transfer method of your choice.
Assuming you survived the above, your phone is now unlocked and ready to root. Proceed as follows:
Open the Magisk app. Click 'Install' for the Magisk Manager app, agree to any prompts, etc.
Next, tick 'Install' for 'Install Magisk' (NOT the manager portion). When prompted for the method, choose 'Select and patch a file.'
Select the 'boot.img' file you transferred to the phone's local storage in step 6 above. Once you do this, the patching process begins on its own.
Magisk will write a root-patched copy, named 'magisk_patched_xxxxx.img,' to the same directory (the X's indicate an alphanumeric string).
Transfer the patched image file back to the ADB tools directory on your PC, with whatever transfer means is comfortable for you.
Now we get to the interesting part. Reboot the phone to fastboot mode, and make sure it's connected to your PC via USB.
Open a command prompt window, on your PC, in the directory your ADB tools are installed.
Type 'fastboot devices' to make sure the system sees your phone.
Assuming all is well, type: 'fastboot flash vbmeta vbmeta_null.img' and hit enter. You should get appropriate responses saying the file was transferred.
Next, type 'fastboot flash boot magisk_patched_xxxxx.img' (naturally, replace the X's with whatever string of characters Magisk supplied).
Assuming no errors, type 'fastboot reboot' and hit enter. Your Armor 10 should now be rooted.
Enjoy!
Happy tweaking.
Click to expand...
Click to collapse
Hello, gonna do this on an Armor X10 Pro. Already got it's original ROM. About vbmeta_null.img file, is that file universal, is it specific for Ulefone phones, or do I need one of those specific for Armor X10 Pro?
GauchoTche said:
Hello, gonna do this on an Armor X10 Pro. Already got it's original ROM. About vbmeta_null.img file, is that file universal, is it specific for Ulefone phones, or do I need one of those specific for Armor X10 Pro?
Click to expand...
Click to collapse
Here a secure file: vbmeta.img from G
I have a rooted Moto G8 Plus with stock ROM. And today I was trying to remove Cerberus, which I had installed as an hidden system app with root.
When hidden, Cerberus is shown as an application "System Framework". But I had troubles getting it removed the normall way, so I've tried my chances with "System app remover" from the app store.
I had removed this "System Framework" app. but then after checking I noticed that it was still there in the app menu, and that it had another install size of the one I had removed. My phone was still working so no problems so far. Unless I've decided to reboot. Now it's stuck on start up. So it seems I accidentally had removed the wrong app called "System Framework", not being aware of it that there was another one of it.
Seems I'm stuck on a "Fastboot Flash Mode (Secure)" acreen now, asking to connect a USB data cable.
{
"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"
}
Does annyone knows how to repair this and acces still acces my phone and data?
Thanks in advance!
- connect phone in fastboot mode usb to PC
- install Android Bootloader Interface drivers
- download platform-tools
- download TWRP recovery
- type in cmd.exe
Code:
fastboot devices
fastboot boot twrp-3.4.0-0-doha-mauronofrio.img
- decrypt /data (unlock pin/pattern)
- create backup of /data from menu
- install Android ADB Interface drivers
- pull all files /sdcard to PC
Code:
adb devices
adb pull -a /sdcard
- flash /system_image
Thanks!
This is for copying content from the internal memory to a PC?
Could I also repair it by reloading "System Framework" and acces the phone and my data in a normall way too?
Still have the same image somewhere on my PC that I've used to flash with while booting. Could I still do something with that?
you can try anything you want - after you saved that backup to PC
Yes, you're right with that. Maybe it's the safest step to do first.
I'm no pro with ADB etc. Just used it once in a while to root evices and needed somekind of guides then first.
But this: "adb pull -a /sdcard" is copying the internal storage to the PC? Where is it getting coppied to? I suspose somekind of default dir in C:\ or so?
right. you can specify target path as last argument. with no path given, current dir is used.
type 'adb help' for usage
Code:
device commands:
adb push <local>... <remote>
- copy files/dirs to device
adb pull [-a] <remote>... <local>
- copy files/dirs from device
(-a preserves file timestamp and mode)
I'm somehow a bit stuck.
I've managed to do the first part. Everything was still installed and the TWRP image was the same as used the first time. Still had the file of it in the Fastboot folder.
After doing the first part:
Code:
fastboot devices
fastboot boot twrp-3.4.0-0-doha-mauronofrio.img
My cmd screen shows that the file is uploaded and that that the phone is restarting. The phone actually restarts.
And it returns to the fastboot screen of the image above.
But after that I'm stuck.
I think the seccond part is about the TWRP configuration?
But it seems I'm not able to enter TWRP.
Powering on while holding volume-up and power is not doing annything. And when selecting "recovery mode" from fastboot it's resulting in a black screen with an Android with the text "no command"
Rockel said:
And it returns to the fastboot screen of the image above.
Click to expand...
Click to collapse
Do you mean fastbootd from within TWRP? Or did you mean it simply returned to normal fastboot mode (fastboot boot didn't work)?
aIecxs said:
Do you mean fastbootd from within TWRP? Or did you mean it simply returned to normal fastboot mode (fastboot boot didn't work)?
Click to expand...
Click to collapse
It returns to this screen when selecting "recovery mode":
I got confused with the word 'image' for 'picture' please use latest platform-tools from link above. the no command screen is part of stock recovery. booting with Volume key won't work, it requires TWRP to be installed in boot.img recovery_ramdisk (you don't have)
in case fastboot boot cmd is not working, this leaves no option other than flashing TWRP into boot partition. however, this will soft-brick device until boot.img is restored. do you still have magisk patched boot.img matching current buildno?
Code:
fastboot getvar ro.build.fingerprint
Well yes, but "volume-down & power" was used to enter fastboot mode if I remember correctly. And I thought I was accesing TWRP with "volume-up & power. So when I suppose I should be able to enter TWRP this way now when everything should have been ok?
I'm still having a stock ROM on my PC, it's from this specific phone and I believe I've used it for rooting back then.
Fastboot is displaying XT2019-1, which is a common name of my backed up ROM file on the PC. So I asume it's the same. I believe I even had to use this file for the unlock proces.
wait.. you already installed TWRP before the bootloop?
Yes, I had completely rooted my phone. Unlocked bootloader, installed exactly the same TWRP version as you linked above and used it to load Magisk.
The only thing I've done so far now is accidentally removing the real "System Framework" which had started to cause this after reboot, and tried to re-load the exact same version of TWRP as you discribed above.
Still having all the files used in the booting proces. So all the files I use should be exactly te same now.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY227HDV34 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp-3.4.0-0-doha-mauronofrio.img
downloading 'boot.img'...
OKAY [ 0.738s]
booting...
OKAY [ 10.280s]
finished. total time: 11.030s
C:\Program Files (x86)\Minimal ADB and Fastboot>
you are sure you previously installed TWRP already, then you can boot into TWRP recovery with "volume-up & power" (or press + keep holding Vol Up while rebooting from fastboot reboot) then provide lock screen pin/pattern to TWRP so it can decrypt files (TWRP will ask for in case device is encrypted).
in case TWRP is not installed, kindly answer post #10 + following cmds
Code:
fastboot getvar securestate
fastboot getvar verity-state
fastboot getvar current-slot
(please note that Minimal ADB and Fastboot is not recommended anymore, it won't work nice with new fastbootd, for example 'fastboot reboot recovery')
Volume-up & power isn't working. Holding down volume-up while booting with fastboot is also not.
It's 2 years ago already since I rooted this device. But always backup the orriginal files used in the rooting process, just in case I will need them on a later moment.
I'm not working with this fastboot, ADB or TWRP etc on regular base. Therefore I forgot about TWRP and I didn't tried it to enter before post #2. So I can't tell if it was working before reloading TWRP through fastboot. However I do not know if loading the exact same version of TWRP using fastboot is causing something to brick?
When using the code in post #10 it shows me:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar ro.build.fingerprint[0]
(bootloader) ro.build.fingerprint[0]: not found
getvar:ro.build.fingerprint[0] FAILED (remote failure)
finished. total time: 0.116s
When using codes in post #14:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar securestate
securestate: flashing_unlocked
finished. total time: 0.003s
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar verity-state
verity-state: enforcing (0)
finished. total time: 0.007s
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar current-slot
current-slot: a
finished. total time: 0.001s
Note that fastboot boot cmd only boot file from PC, it does not install anything.
kindly check what files you have on PC
✓ boot.img
✓ magisk_patched.img
✓ twrp-3.4.0-0-doha-mauronofrio.img
if not, try to get buildno without [0] maybe?
Code:
fastboot getvar ro.build.fingerprint
Oh this code did not install or overwrite annything?
Code:
fastboot boot twrp-3.4.0-0-doha-mauronofrio.img
I notice the "boot" command now in it. I thought it was installing/ overwriting TWRP.
I still have the following files on my PC:
Magisk:
- boot.img
- magisk_patched.img
Others:
- twrp-3.4.0-0-doha-mauronofrio.img
- XT2019-1_DOHA_RETEU_10_QPI30.28-Q3-28-26-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Without [0] worked
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar ro.build.fingerprint
(bootloader) ro.build.fingerprint[0]: motorola/doha_reteu_n/doha_n:10/QP
(bootloader) ro.build.fingerprint[1]: I30.28-Q3-28-26-3/a320d:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
ro.build.fingerprint: Done
finished. total time: 0.022s
good, buildno matches the already downloaded stock ROM. then most likely the files are matching, too. let's start with flashing...
first flash TWRP into boot partition. then reboot phone, it now has no way to boot into android anymore, but will boot into TWRP instead.
use current-slot: a
Code:
fastboot devices
fastboot flash boot_a twrp-3.4.0-0-doha-mauronofrio.img
fastboot reboot
TWRP will now ask for pin/pattern (if required)
first thing to do in TWRP, restore boot partition from adb to restore its bootable state.
(may require adb drivers re-installed)
Code:
adb devices
adb push magisk_patched.img /tmp
adb shell
# dd if=/tmp/magisk_patched.img of=/dev/block/bootdevice/by-name/boot_a
# exit
now you've been temporary booted into TWRP. you can now proceed with backup (post #2).
for installing TWRP, download Magisk, add suffix zip to file name, then install this order (I recommend older previously installed Magisk version, latest is not always best):
Code:
adb devices
adb push boot.img /tmp
adb push twrp-3.4.0-0-doha-mauronofrio.img /tmp
adb push Magisk-v25.2.apk.zip /tmp
adb shell
# dd if=/tmp/boot.img of=/dev/block/bootdevice/by-name/boot_a
# echo 'KEEPVERITY=false' >/cache/.magisk
# echo 'KEEPFORCEENCRYPT=true' >>/cache/.magisk
# exit
(last line depends wether phone is currently encrypted or not)
1) install TWRP into stock boot ramdisk via TWRP menu (refer to TWRP Other Install guide)
- TWRP > Advanced > Install Recovery Ramdisk
- navigate to /tmp, choose twrp-3.4.0-0-doha-mauronofrio.img
- swipe to install TWRP
2) Now re-install Magisk into boot partition
- TWRP > Install
- choose /tmp/Magisk-v25.2.apk.zip
- swipe to install
assuming everything went well, you have successfully installed TWRP and should now be able to boot into TWRP recovery with Volume Up + Power Buttons any time*
*use TWRP A/B Retention Module on each OTA/Magisk update to preserve TWRP ramdisk in both slots
Ah thanks!
Yes, it should actually be the same ROM as was installed on the phone at the moment. Can't remember exactly, but I needed it in the root proces. I believe for unlocking. That's why I still have the file on my PC. Should be exactly the same.
I see I was using the wrong term "loading" before. But (re) flashing (the same version) TWRP or anything else does still keep the data intact or accessable (if still the case)?
Retrieving the data has my priority now. Since I already have a new phone. So "unbricking" is less important now. Although it will be necessary to retrieve the data I suppose.
the goal is to backup data. it depends on
- TWRP is booting
- device is encrypted or not
- TWRP is able to decrypt or not
in case something does not work, we still have other options without TWRP