Database Info

[GUIDE] New Root Method for LG Devices

Code:
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
A lot.
Original Guide
Prerequisites
1.) Download LG Root
2.) Download LG Drivers
3.) A micro USB cable connected to your PC
4.) Your device must be unencrypted
5.) Before you ask a question, make sure you looked at the pictures in the guide.
1.) Download and unzip the LG_Root.zip in your preferred location
I chose the Desktop for my location
{
"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"
}
2.) Enable ADB debugging on your device
Go to Settings > About Phone > Software Information and tap build number until you are presented with "You are now a developer"
Exit back to Settings main screen
In Developer Options enable USB Debugging (Some devices require enabling PTP for debugging to work)
3.) In the root of LG_Root folder start a command prompt
Instructions may vary based on Window's version
Inside of LG_Root folder hold shift and right click a blank space you should see "Open command window here"
4.) Now that we have a command prompt running in the root of the folder let's get started. (Commands are copy+paste unless specified)
Let's make sure our device is connected
Code:
adb.exe devices
5.) Great! My device is connected let's continue, we need to get the files onto the device used for this root method.
In the same command prompt let's execute another command
Code:
adb.exe push busybox /data/local/tmp/ && adb.exe push lg_root.sh /data/local/tmp && adb.exe push UPDATE-SuperSU-v2.46.zip /data/local/tmp
6.) Well that was easy , let's continue (Now that we have the files on our device we want to put our device is download mode)
(Note this method may vary from device to device)
Power off your device
When the device is powered off, hold volume up and insert a USB cable connected to the PC
Wait for the drivers to install
7.) We're almost done (you've managed to get in download mode)
8.) Let's find which COM port our device is connected to
Double click ports.bat (This will give us the COM port in which our device is connected we are looking for the Diag port)
You may exit this command prompt when you have your COM port number, keep the other command prompt open
9.) Let's Begin! (Keep the device in Download mode)
Let's run Send_Command.exe (It couldn't connect? Make sure you COM port number is correct it varies)
Code:
Send_Command.exe \\.\COM4
10.) Final Step!!!!!! (We must run the root script)
Code:
sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
11.) We're done
You may pull the battery to get the device out of Download mode
Credit
All credit goes to @jgkim find a post and thank this guy for posting the method.
Thank @high247 for ports.bat

One Click Root
You can follow the one click root guide here thanks to @avicohh

Devices confirmed working with root method (If your device isn't listed it's most likely still supported)
LG F60 (all variants)
LG Tribute (all variants)
LG G2 (all variants)
LG MS395/D393
LG G3 (all variants)
LG L90 (all variants)
LG Transpyre
LG Volt (LS740)
LG G Flex 2
NOTE: Do not attempt this on devices with 5.1.1 , at the time this method was posted it worked on many firmware 5.0.2 and below. With the current releases from LG, this method has and will brick many users. This can be said for the one click method as well. Failure to read the complete thread may render your device non repairable as the KDZ firmware isn't released for all LG devices.

Are u saying it unlocks vzw boot loader

EDIT: Fixed, Bootloader Unlocked.

dabug123 said:
Are u saying it unlocks vzw boot loader
Click to expand...
Click to collapse
It works for some devices. It has yet to be confirmed. The confirmed devices are for root only.

Unjustified Dev said:
It works for some devices. It has yet to be confirmed. The confirmed devices are for root only.
Click to expand...
Click to collapse
Right root,unlock vzw g3 my question there is fastboot was removed..So is fastboot being replaced with that.

dabug123 said:
Right root,unlock vzw g3 my question there is fastboot was removed..So is fastboot being replaced with that.
Click to expand...
Click to collapse
After zeroing out the LAF partition the boot loader falls back to fastboot the LAF partition is simply LG's Download mode. Once it falls back to fastboot you can run fastboot commands , but nothing is being replaced it existed it was just a priority LAF over fastboot. If fastboot was removed by LG in your device it wouldn't be replaced.

Unjustified Dev said:
After zeroing out the LAF partition the boot loader falls back to fastboot the LAF partition is simply LG's Download mode. Once it falls back to fastboot you can run fastboot commands , but nothing is being replaced it existed it was just a priority LAF over fastboot. If fastboot was removed by LG in your device it wouldn't be replaced.
Click to expand...
Click to collapse
yes I understand laf and the ends and outs,what I'm saying is fastboot was removed on the Verizon g3 so if I remove laf there will be no fastboot.just confirming this can't replace fastboot that was removed

dabug123 said:
yes I understand laf and the ends and outs,what I'm saying is fastboot was removed on the Verizon g3 so if I remove laf there will be no fastboot.just confirming this can't replace fastboot that was removed
Click to expand...
Click to collapse
I guess I should warn people about that thanks, hopefully someone can find a workaround for the secure boot.

Unjustified Dev said:
I guess I should warn people about that thanks.
Click to expand...
Click to collapse
Ya definitely ,I know better but guy above may have already gone down that road.Would be nice to replace it somehow..The users may not realize Verizon is the only g3 with no fastboot and removing laf can be very dangerous..

EDIT: Fixed problem.

high247 said:
I've re installed the LG Driver three times with no luck getting my phone to be recognized when I'm in fastboot mode.
I attached a picture showing with what is happening when in fastboot. I did try poniting to the LG Driver Folder, but it said it could not find anything. When I'm just in MTP or PTP Debug Mode the phone is recognized, so I'm confused.
Click to expand...
Click to collapse
It may be due to XP but could you try this guide here here

Unjustified Dev said:
It may be due to XP but could you try this guide here here
Click to expand...
Click to collapse
Hey I'm still on xp for a few more weeks till my new beast gets built.
Going to try that now. Thanks for helping!

dabug123 said:
Ya definitely ,I know better but guy above may have already gone down that road.Would be nice to replace it somehow..The users may not realize Verizon is the only g3 with no fastboot and removing laf can be very dangerous..
Click to expand...
Click to collapse
You can actually add it back manually just start a shell and reverse the command
dd if=/sdcard/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
added it to guide. Thanks again.

Got it my driver issue fixed with the help of this post http://forum.xda-developers.com/showpost.php?p=59310899&postcount=471 the driver in the file he attached is just what I needed to get it to work correctly.
It might also be very useful for anyone else who might run into the same problem I did. Cheers!
---------- Post added at 02:15 AM ---------- Previous post was at 02:10 AM ----------
Rooted, Bootloader UNLOCKED, and installed AdFree.apk... Today was a good day!

Unjustified Dev said:
You can actually add it back manually just start a shell and reverse the command
dd if=/sdcard/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
added it to guide. Thanks again.
Click to expand...
Click to collapse
No u misunderstood me again I mean I wish this was a way to put fastboot back.Good u added those instructions though for adding laf back,good to have posted.

Thank you so much Unjustified Dev! I was almost quite literally banging my head against a wall trying to figure this out. This guide was just I needed. My mistake was just opening the command prompt by itself instead of opening the command prompt in the folder itself. No I'm fully rooted. Thanks again!:good:

Root method works for LG Volt LS740 - ZV4 and ZV5 firmware

Unjustified Dev said:
You can actually add it back manually just start a shell and reverse the command
dd if=/sdcard/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
added it to guide. Thanks again.
Click to expand...
Click to collapse
I can't do this because I'm on vzw, but I must be missing something.
Normally you would have to run a fastboot command similar to, fastboot oem unlock, but I don't see where you instructed to run any commands.
Maybe I overlooked it, went to bed at 12 and woke up for work at 4:30 lol

[Guide] Root on Linux Mint

Rooting a Xiaomi Mi 4i on Linux Mint 17.1 Rebecca
- This guide might also be relevant for users of Debian and Ubuntu
Disclaimer: I accept no responsibility for any damage you do to your phone, body, life or anything else in the past present or future.
This has been written as I had so much difficulty in getting my Mi 4i rooted. I kept trying to do it in Windows through Virtual Box but kept failing.
1. Enable Developer Options
- On your phone, go to Settings
- About phone
- Keep tapping on the Android version until the message at the bottom says that you are a developer
2. Enable USB debugging
- On your phone, go to Settings
- Additional settings
- Developer options
- USB debugging
3. Install the tools
Code:
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
4. Try and see the devices
- Connect the phone to your computer
- Run the following command at the terminal
Code:
adb devices
- It will now say List of devices attached.
- If you see another line with an 8 character identifier such as bf1b6529 then you can skip step 5
5. Add phone to known devices
- Run the following command on the terminal
Code:
echo 0x2717 >> ~/.android/adb_usb.ini
6. Add your computer to trusted devices on your phone
- Enter the following command on the terminal:
Code:
adb devices
- Look on your phone, it should now be asking you if it can add the machine to the trusted devices, or something like that. I'm writing this from memory.
7. Check that adb devices is working
- Enter the following command on the terminal:
Code:
adb devices
- Check that the device ID is there (8 characters such as bf1b6529)
- Check that it says device after it
8. Kill adb
- Enter the following command on the terminal
Code:
adb kill-server
9. Now for the fun. You will need sudo access for this stage.
- Download boot.img to your computer.
- At the terminal, navigate to the directory where you downloaded boot.img, this will probably be ~/Downloads
- At the terminal:
Code:
adb reboot bootloader
- You will now see a screen like the following:
{
"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"
}
- At the terminal:
Code:
sudo su
fastboot devices
- You will now see your device ID followed by fastboot
Code:
fastboot boot boot.img
- You will now see something like the following:
Code:
downloading 'boot.img'...
OKAY [ 1.022s]
booting...
OKAY [ 0.259s]
finished. total time: 1.281s
10. Restart
- At the terminal enter:
Code:
fastboot reboot
- You should now see a textual boot screen wher you can see it actually carrying out the rooting with boot.img
- Then it should boot as normal into Android
- Check your apps. You should now have SuperSU

Thanks for step no 5. After trying all kind of 51-android.rules guide from stackoverflow and your solution work. Now I can detect my device in Linux Mint.
5. Add phone to known devices
- Run the following command on the terminal
Code:
echo 0x2717 >> ~/.android/adb_usb.ini
Click to expand...
Click to collapse

thanks....
finally i can connect my mi4i to my linux desktop

Thank you for your guide. I assume this will work on Ubuntu 14.04 as well.
Question to step no.9: "Download boot.img to your current dir" => Which directory do you mean? The root of the phone or on my laptop? Sorry for being newbie. Many thanks.

rmsinaga said:
Which directory do you mean? The root of the phone or on my laptop?
Click to expand...
Click to collapse
You need to download boot.img to your laptop. I've updated Step 9 with the following:
- Download boot.img to your computer.
- At the command line, navigate to the directory where you downloaded boot.img, this will probably be ~/Downloads
Click to expand...
Click to collapse

Step one on the path to rooting my m4i was getting adb to work.
kblade29m said:
Thanks for step no 5. After trying all kind of 51-android.rules guide from stackoverflow and your solution work. Now I can detect my device in Linux Mint.
Click to expand...
Click to collapse
After much googling, much time, and trial and error, I had reached this point. Then I come here and here it is! All made simple.
The next hurdle is that adb devices shows the phone with the word "offline," and that is where...
aembleton said:
- Look on your phone, it should now be asking you if it can add the machine to the trusted devices, or something like that. I'm writing this from memory.
Click to expand...
Click to collapse
...I find I wasn't even seeing the message because the flip cover was closed. Doh.
This is my second Android phone, and I rooted and installed CM on the previous one, a Defy+. Still feel very much a novice, and approaching the rooting is quite scary. Among my worries...
Does this method change the recovery?
Does this method, with boot.img, install a new rom, or does it root the exisiting one?
Will everything else be reset/wiped? (well, backups anyway. Of course).
Will Xiaomi updates still work and be installable?
I am considering using method 1 from "Root/Unroot V6.5.x W/out Losing Stock Recovery [Simplified]" (new member: cannot make that a link) . Any comments?
It is so nice to see the Linux, and especially mint-specific, advice here. Thank you!
(My first post here: usual forum-novice disclaimers apply )

I have used this method to root my mi4i.
Quick answer:
1. No
2. It only roots the existing ROM
3. No
4. You need to full unroot 1st from SuperSU before updating, otherwise it will be bootloop
5. Never tried before

rmsinaga said:
I have used this method to root my mi4i.
Quick answer:
... ... ...
Click to expand...
Click to collapse
Great answer! :good:
Thank you very much for attention to every detail. The only thing putting me off going for this straight away is that I am travelling in just over a week, which doesn't give me any margin for making mistakes (if they can be made, I will make them!).
You mentioned having failed to make stuff work in a virtual machine. Did you try Wine? I failed to make the Mi PC manager software run in Wine.

Simple, painless and absolutely effective
aembleton said:
10. Restart[/B]
- At the terminal enter:
Code:
fastboot reboot
Click to expand...
Click to collapse
(response typed from memory)
Code:
# fastboot reboot
<Waiting for Device>
...amd it goes on waiting. Does anybody get any other response on the terminal screen after this?
Anyway, Be Patient! Probably better to make tea or something away from the screen. After several minutes of Fastboot screen on the phone, the process continues as premised...
aembleton said:
- You should now see a textual boot screen wher you can see it actually carrying out the rooting with boot.img
- Then it should boot as normal into Android
- Check your apps. You should now have SuperSU
Click to expand...
Click to collapse
...and all is well.
After the phone had rebooted, I just ctrl-c-ed the fastboot process and exited from the terminal.

Works wonders, thanks!
Could only find ****ty .exe rooting tools that seemed sketchy and don't have windows installed anymore, so this saved me hours.
My computer could find the phone through adb and got authorized, the phone couldn't find my computer through adb though which was strange but it still worked fine. Thanks alot!

Thad E Ginathom said:
4. Will Xiaomi updates still work and be installable?)
Click to expand...
Click to collapse
rmsinaga said:
4. You need to full unroot 1st from SuperSU before updating, otherwise it will be bootloop
Click to expand...
Click to collapse
Just tried this, it does not work.
Disabled root from SuperSU and updated to the newest weekly developer rom, and my device is now in a boot loop.
I'm currently trying to download the stable fastboot rom from the MIUI forums, but their servers are both incredibly slow and unstable. Doesn't go past 100kb/s and the download loses connection after a while and fails to continue the download. If someone could provide a alternative download link that would be great.
EDIT: Found a hidden link on the rom page for the fastboot rom from the miui page. Go to this page and Ctrl-F Mi4i

zenolijo said:
Found a hidden link on the rom page for the fastboot rom from the miui page. Go to this page and Ctrl-F Mi4i
Click to expand...
Click to collapse
Did this work for you?
I also got into a boot loop after installing the latest update. I installed the latest stable version. This worked, but the Play Store won't start.

aembleton said:
Did this work for you?
I also got into a boot loop after installing the latest update. I installed the latest stable version. This worked, but the Play Store won't start.
Click to expand...
Click to collapse
Well, the stable fastboot rom isn't the global version, so i only used it to get my phone running again and then flashed the stable global version. Everything works as expected now.

How to update ROM using fastboot in Linux?
Do you know how to update ROM using fastboot in Linux?
Sorry to bother you as I'm new in this Linux world.
Thank you.

Thank you man, you have guided us to the land of light, you are our moses, krishna, muhammad and so on and so forth. We can flash left and right without second thoughts. Please keep up your efforts. Thank you one more time.

My phone is, as per previous posts, rooted, using this method.
Can I now flash TWRP recovery from Linux?

Hey, this is a method only for Xiaomi Mi4i? I have an Estar Crystal-clearview and wondering if I can root it by this method? I run the terminal with the adb install and then for the list of devices attached, and I started thinking about!
P.s. Just searched ''root with mint'' and your post was first!

Thad E Ginathom said:
Can I now flash TWRP recovery from Linux?
Click to expand...
Click to collapse
Eventually I got around to doing this using Flashify. I followed the instructions here on the MIUI forum. It was simple and straightforward and I now have TWRP recovery.
However, when I tried to use it to do a backup, it said there was not enough space. But it was long past bedtime, and that is another story that I have yet to investigate. There is probably a simple answer, err... make more space! The absence of SD card slot and the limited internal memory is the big frustration about this phone.
But I want to upgrade MIUI --- and I don't want to do it without an easy backtrack to the previous ROM.

[Solved] Step 9 not working
Goto developer options
Check if 'fastboot mode' is enabled

Thanks
Hi aembleton,
Thanks a lot. it worked just fine.
does this replace recovery too ?

Oneplus 7 pro keep going into fastboot mode

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

Systemless Root on Ulefone Armor 10 5G: How I did it...

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

[GUIDE][ROOT] QLink Serrano 3 (HPP-L55B) Bootloader Unlocking And Rooting Guide

QLink Serrano 3
Model No. HPP-L55B
By Hot Pepper Mobile
{
"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"
}
Bootloader Unlocking
And Rooting Guide ​
OVERVIEW:
This guide provides step-by-step instructions for unlocking the bootloader and achieving root access on the QLink Serrano 3. Please note that this guide is specifically for the QLink variant of the Serrano 3 (HPP-H55L), as I have not verified the applicability of this guide on other carrier variants of this smartphone. To simplify the rooting procedure, and to cater this guide to new and inexperienced members, I have provided a boot image pre-patched for Magisk systemless root support below, in the downloads section.
IMPORTANT NOTE: The pre-patched boot image in the downloads section below corresponds with firmware build HPP-L55B-J-9.0.0. If your Serrano is running a different build, flashing the pre-patched boot image provided may or may not result in compatibility issues. In short, the best rule of thumb when achieving systemless root is to always patch an image that matches the firmware build installed on your device, otherwise you may encounter issues such as broken WiFi, broken Bluetooth, or your device may not boot at all. Should any members encounter issues of this sort, you may flash your device with the HPP-L55B-J-9.0.0 firmware by following my firmware restoration guide for the Serrano here: QLink Serrano 3 Firmware Restoration Guide
PREREQUISITES:
You will need a Windows PC or laptop with the ADB & fastboot tools installed. I have provided a link below for the latest Minimal ADB & Fastboot tools. You will need the factory supplied, or a quality equivalent micro USB to USB-A data syncing/charging cable. And, you will need your QLink Serrano 3 smartphone. I again emphasize that this guide has only been tested on the QLink variant of the Serrano (HPP-L55B).
DISCLAIMER:
The tasks outlined in this guide encompass inherent risks to the integrity and operability of your smartphone. Moreover, unlocking the bootloader/rooting the device will void any active manufacturer's warranty you may have on your Serrano. By proceeding further, you are assuming full responsibility for the state and health of your smartphone. As such, you are hereby absolving me of any responsibility or civil liability in the unfortunate event things go badly. This guide has been fully and thoroughly tested. Follow the instructions carefully, employ some patience, and pay attention to detail and I'm confident things will go smoothly. It should also be noted that the tasks outlined herein can be carried out using a Mac or Linux computer as well. This particular guide, however, will focus solely on a Windows -based setup.
I.. INSTALLING ADB & FASTBOOT
Because both tasks outlined in this guide require ADB/Fastboot communication between your phone and PC/laptop, this first section will focus on proper installation of the ADB & Fastboot utilities on your Windows computer. If you already have a working ADB/Fastboot environment, skip down to the next section on unlocking the bootloader. Otherwise, follow these steps:​
Download the Minimal ADB & Fastboot tools installer from the link below. Right click the .exe file and opt to run it as an administrator. Follow the on-screen prompts and complete the installation;​
Open the Windows File Explorer, go to This PC and open your C: drive directory. Open Program Files x86 and locate the Minimal ADB & Fastboot folder. Copy the folder and then paste it on your desktop (this step merely configures the ADB & Fastboot directory to a more convenient location from which to work);​
Open the Minimal ADB & Fastboot folder and double click the file named cmd-here. A command prompt will open. Next, connect your Serrano to your Windows computer using a suitable micro USB to USB-A data syncing cable. Ensure that USB Debugging is enabled in your Developer Options menu.​
In the command window you opened in the previous step, execute this command:
Code:
adb devices
Watch your device display for a USB Debugging authorization prompt. Grant the request. If properly connected, the command window will output an alphanumeric string consistent with your device serial number;​
If the command window does not display your serial number, or if you get a WAITING notification, your smartphone isn't communicating properly with your PC or laptop. Try another data syncing cable,; change USB ports; and/or reinstall the Minimal ADB & Fastboot tools on your computer;​
Once you have established proper device communication, we will now test fastboot mode communication. Execute this command:
Code:
adb reboot bootloader
Your device should now boot into fastboot mode, which will be illustrated by a darkly backlit display with the words => FASTBOOT mode.... displayed in a white font at the bottom-left of the screen;​
Next, execute this command:
Code:
fastboot devices
Similar to before, if properly connected, the command window will display your device S/N. If you don't see your S/N, or if the command window says WAITING, you are not properly connected. Again, try changing USB ports, try another data syncing cable, and/or reinstall the Minimal ADb & Fastboot tools on your computer.​
II. UNLOCKING THE BOOTLOADER
WARNING: Unlocking the bootloader triggers a native Android security mechanism that forces the device into a factory data reset. This will erase all saved userdata on your phone. Before proceeding further, make a backup of all saved userdata you wish to keep.​
Open device Settings>System>Developer Options, and enable the OEM Unlock option;​
Boot into fastboot mode by executing:
Code:
adb reboot bootloader
Once in fastboot mode, it's time to initiate bootloader unlocking. Execute this command:
Code:
fastboot flashing unlock
Your smartphone display will now prompt you to tap Volume + to proceed with unlocking, or Volume - to cancel;​
After pressing Volume +, the unlock sequence will finish in just a few seconds. Now reboot to complete the process: Execute:
Code:
fastboot reboot
As mentioned previously, your phone will now initiate a mandatory factory data reset, after which your device will boot into the initial setup phase of the Android OS. Your bootloader is now officially unlocked.​
III. ROOTING THE SMARTPHONE
Now that the bootloader is unlocked, attaining root access is very straightforward.​
Download the patched boot image and vbmeta image files from the links below and save the files in your Minimal ADB & Fastboot folder;​
Double click the cmd-here.exe file to open a command window. Execute this command to flash the patched boot image:
Code:
fastboot flash boot patched_boot.img
Now we will disable dm-verity by executing this command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Now, execute this command to reboot your phone:
Code:
fastboot reboot
Upon reboot into the Android OS, locate the Magisk app or its stub placeholder in your app drawer. Open Magisk, grant any requested permissions, and follow any prompts to finish setting up the root environment. Magisk may initiate a reboot to complete root setup. If the Magisk app or its stub placeholder is not in your app drawer, download the Magisk v25.2 APK from the link below and install it on your phone. That's it. You are rooted with the Magisk v25.2 systemless root solution.​
DOWNLOADS:
• Minimal ADB & Fastboot v1.4.3
• Patched boot.img
• vbmeta.img
• Official Magisk Releases (GitHub)​

Thank you for this I'm going to try this. Here are some of the issues I have been having. When I plug it in to charge it. It keeps trying to boot and will not stop. I have to press the power button to buy bypass an error message that says this device is corrupted. I just got this phone from qulink (Amazon) and it was doing this since I opened it. It will not update the system. I believe the boot issue may have something to do with it. I'm not sure what kind of bloat wear it has but I do know something is running rapidly in the back ground I have practically no battery life and charging it is a night near. Another important question is can I use a chrome book to do the procedure? Any input would be greatly appreciated.
Thanks
John Bridges

John Bridges said:
Thank you for this I'm going to try this. Here are some of the issues I have been having. When I plug it in to charge it. It keeps trying to boot and will not stop. I have to press the power button to buy bypass an error message that says this device is corrupted. I just got this phone from qulink (Amazon) and it was doing this since I opened it. It will not update the system. I believe the boot issue may have something to do with it. I'm not sure what kind of bloat wear it has but I do know something is running rapidly in the back ground I have practically no battery life and charging it is a night near. Another important question is can I use a chrome book to do the procedure? Any input would be greatly appreciated.
Thanks
John Bridges
Click to expand...
Click to collapse
Greetings @John Bridges. You have come to the right place. Sounds like you're stuck in a classic boot loop. Flashing the factory firmware offered in my guide should certainly restore your device to its stock factory state.
The firmware, unfortunately, does include the typical bloatware specific to QLink devices. Of course,, once you get your phone restored via firmware flashing, you can always opt to unlock your bootloader, achieve root and debloat tie stock OS. So, your best option may be to first restore your device by installing firmware, and then rooting.
Serrano Firmware Restoration Guide

Greetings Viva,
Thanks for the great response. I will try your great advice and respect you for dedicating you're time to help the Android epidemic.

John Bridges said:
Greetings Viva,
Thanks for the great response. I will try your great advice and respect you for dedicating you're time to help the Android epidemic.
Click to expand...
Click to collapse
Thank you for the kind words. The type of boot loop you are experiencing is caused from data corruption that occurs when Android decrypts the /userdata partition during the boot sequence. By default, Android encrypts all data on this partition for user security; as such, whenever your device boots up, Android decrypts the data to make it accessible. If any errors or data corruption are incurred during this process, you will be promoted to either try again or perform a factory data reset.
Sorry I just saw your reference to the Chromebook. I'm afraid it won't be much help on this. My guide focuses on a Windows setup; however, Linux or Max can also be used. Out of curiosity, have you first tried factory resetting the phone?

Yes I did still didn't help When I'd tried to start it a message would appear saying the device is court press power button to continue and it came out of the box with this problem. I tried to update it and several different errors would show up,one was something about OTA, Would it be possible to do the procedure with a chrome book?

John Bridges said:
Yes I did still didn't help When I'd tried to start it a message would appear saying the device is court press power button to continue and it came out of the box with this problem. I tried to update it and several different errors would show up,one was something about OTA, Would it be possible to do the procedure with a chrome book?
Click to expand...
Click to collapse
The device is court I mean.

Corrupt I mean

John Bridges said:
Corrupt I mean
Click to expand...
Click to collapse
I understand on the device being data corrupted. Firmware restoration is definitely your best option. I know of no way to flash firmware using a Chromebook. I'll research it and see if it can be done.
Okay I did find an XDA guide on utilizing ADB & fastboot on Chromebook. https://forum.xda-developers.com/t/...-chromeos-adb-fastboot.2157230/#post-38232908
However, even the developers who posted in that thread refer to the procedure as extremely complex.

@John Bridges have you had any luck with restoring your firmware via Chromebook?

For those members who detest the abundance of bloatware included in the factory firmware package, I have unpacked the super.img, removed a considerable amount of the QLink apps, services and other bloatware, and then repacked the super.img. I have removed the annoying QLink lock screen, the QLink "free WiFi" service, a number of the preinstalled Google apps, and some other RAM demanding apps & services. I've noticed a remarkable improvement in performance on my own device as a result of debloating the stock OS in this manner.
I will post a new thread this weekend with this debloated stock OS, and instructions for fastboot installation. You will need an unlocked bootloader to install it.

VivaI
I just haven't had time to do it yet I am anxious to do it however and I will let you know how it went for sure.

VivaI and others,
It is a shame that people like myself that have to get these government phones to have one or hacked and it's a great thing you all are doing to give us a phone that will be actually uncorrupted. I don't know if this matters but the phone I got was from Amazon and it is supposed to be unlocked I don't know if that means the bootlegger is unlocked or anything else but I thought it may be helpful to you to know this.

John Bridges said:
VivaI and others,
It is a shame that people like myself that have to get these government phones to have one or hacked and it's a great thing you all are doing to give us a phone that will be actually uncorrupted. I don't know if this matters but the phone I got was from Amazon and it is supposed to be unlocked I don't know if that means the bootlegger is unlocked or anything else but I thought it may be helpful to you to know this.
Click to expand...
Click to collapse
And I'm talking about the phone or the replacement phone you get from q Link it is supposed to be unlocked and it comes from Amazon I checked on it online.

John Bridges said:
And I'm talking about the phone or the replacement phone you get from q Link it is supposed to be unlocked and it comes from Amazon I checked on it online.
Click to expand...
Click to collapse
To the best of my knowledge -- but not confirmed 100% -- all variants of the Serrano are GSM unlocked. Mine originally came from Amazon as well. By unlocked, I am referring to network unlocked and not the bootloader.

Very nice to know! I'm going to try and get it done tomorrow.

John Bridges said:
Very nice to know! I'm going to try and get it done tomorrow.
Click to expand...
Click to collapse
If you have any questions, or if you encounter any obstacles during the procedure, just let me know.

Viva La Android said:
For those members who detest the abundance of bloatware included in the factory firmware package, I have unpacked the super.img, removed a considerable amount of the QLink apps, services and other bloatware, and then repacked the super.img. I have removed the annoying QLink lock screen, the QLink "free WiFi" service, a number of the preinstalled Google apps, and some other RAM demanding apps & services. I've noticed a remarkable improvement in performance on my own device as a result of debloating the stock OS in this manner.
I will post a new thread this weekend with this debloated stock OS, and instructions for fastboot installation. You will need an unlocked bootloader to install it.
Click to expand...
Click to collapse
Could you share the link to this thread please? The search function on this forum is frustrating and not turning up any relevant results and with your profile set to private I coludn't search for your threads either.
Crap nevermind, I just noticed I could pull up threads you created using the search function and looks like it hasnt been posted yet. Could you update this thread when it is?

GIutton said:
Could you share the link to this thread please? The search function on this forum is frustrating and not turning up any relevant results and with your profile set to private I coludn't search for your threads either.
Crap nevermind, I just noticed I could pull up threads you created using the search function and looks like it hasnt been posted yet. Could you update this thread when it is?
Click to expand...
Click to collapse
Not finalized. There are bugs to work out.

Anyone know why we can't modify, add, or remove files from the system partition using an app like root explorer? I wanted to change my bootanimation on my hot pepper serrano 3 and remove unwanted apps and files since i now have it rooted with magisk 25.2 but system partition seems to be read only at the moment. You can delete stuff from the system partition but they come back after a reboot. Same goes with modifying or adding anything in /system. You need to mention in the OP that we only have partial root not full root. Can anyone confirm this and is there a solution to this problem? Is it just me that is having this issue?