Database Info

ADB Access Win x64 (CM10)

Since I can't respond to threads in Developer and I think that this might belong here to answer some folks questions. I have read that a lot of people are having issues with ADB access under Windows x64 using the latest CM10 by h8rift. I found a solution that worked for me and I wish to share it with everyone in case it will work for them. A few critiria:
- Your device is connected via USB cable to your computer
- Your device is listed as "HTC MTP Device" in Windows Device Manager
- When you open a CMD prompt under your Android Directory and type "adb devices", nothing is listed
This is because you have the wrong device drivers installed on your system and it needs to be corrected. This is how I accomplished it.
1. Uninstall the driver completely from your system. This has to be done under the device properties. Under "Action", select "Scan for New Hardware Changes". Your system will see the new device and identify it under "Other Devices" as "One". If Windows tries to install the wrong drivers, you will have to restart all over until the HTC MTP Device driver is completely removed from your system.
2. Install HTC Sync from their website. Once installed, it has to update to the latest version. This is needed to install all additional drivers for SD Card access.
3. HTC One X Drivers will be listed under C:\Program Files (x86)\HTC\HTC Driver\Driver Files (default install location).
4. For ADB access, you will need the drivers located here; download appropriate drivers for your Windows flavor. These are the ADB drivers.
5. Download the zip, and extract. Remember the location of the files. Go into Device Manger, find "One" under "Other Devices" and Update Driver Software. Point to the new directory you made and install. The One X will now be listed in Device Manager as "My HTC" under "Android USB Devices"
6. To verify ADB, open a CMD prompt, point to Android directory and type in "adb devices". Your beautiful HTC One X should be listed.
I am not the maintainer of any of these webpages nor can I guarantee that these pages will exist to the end of time. Those of you wishing to have ADB access under Windows for CM10, this worked well for me. I gathered up this information just by doing a quick search in Google and through the forums.
Thank you to h8rift for CM10 and all the hard work he puts into it.

Will try this when I get home! Thanks.

This worked perfectly for me. Thanks man!
------------------------------------------------------------
HTC One X, CM10-Evita JellyBean, Win7-x64

Not working for me, evertime I scan for hardware changes it tried to install HTC MTP DEVICE, and when I try to update that driver with the new ADB driver, it says it's already installed. Then when I uninstall that driver, I don't see the One devices anywhere, until I scan for hardware changes again, which then repeats the above. What am I doing wrong?

Chrysis said:
Not working for me, evertime I scan for hardware changes it tried to install HTC MTP DEVICE, and when I try to update that driver with the new ADB driver, it says it's already installed. Then when I uninstall that driver, I don't see the One devices anywhere, until I scan for hardware changes again, which then repeats the above. What am I doing wrong?
Click to expand...
Click to collapse
I think I found a fix for that. Let me restart my computer and verify
edit: nope.. nothing so far. mine doesn't even show HTC MTP DEVICE anymore >.>

same i see one when i look for new hardware but it always just auto sets to mtp.

Delete old drivers
The reason for this is that you cannot completely delete existing drivers using device manager. They still exist in the driver store, and are loaded as soon as you scan for hardware changes.
There might be a better way to do this, but here's how I did it:
- uninstall driver in device manager. Don't scan for hardware changes.
- Run a CMD prompt as administrator (right click "Run as Administrator")
- navigate to C:/Windows/system32 which is the location of the driver store
- type pnputil.exe /e
- this will list the drivers that exist in the driver store. They are denoted as oem##.inf
- find the driver that has "HTC Corporation" in the description. Write down the oem##.inf number (ex. oem81.inf)
- type pnputil.exe /d oem##.inf (where ## corresponds to the number of the HTC driver).
This will remove the old driver from the driver store. Now when you scan for hardware changes, it should fail to find a driver and prompt you for a location.
NOTE: I actually had several HTC drivers in the driver store. Its because I've had a few HTC devices over the years. I deleted them all. This may break HTC Sync, I dunno. I don't use it.

Fixed. See post below

For anyone having problems. I finally got it working.
THIS SHOULD BE NO LONGER NEEDED. ROHAN'S NEW AOKP VERSION 2 SHOULD WORK WITH STOCK DRIVERS. IM ASSUMING THIS WILL BE MERGED WITH ANY OTHER AOSP ROMS. IF YOU STILL NEED THIS INFORMATION HOWEVER, I WILL LEAVE IT UP.
1. Uninstall HTC Sync and any HTC sync drivers listed in your "Add/Remove Programs"
2. Delete EVERY driver pertaining to HTC when you run CMD as admin and type "pnputil -e" and then type "pnputil -d oem##.inf" (such as oem13.inf ONLY IF it says HTC or HTC Corporation)
3. Download Deview - 32 bit OR 64 bit, and run as administrator and uninstall ALL disconnected drivers (it won't matter if you uninstall the wrong thing, because it will just reinstall again when you plug in the hardware. make sure your phone IS NOT plugged in)
4. Download ADB drivers 32 bit OR 64 bit. (windows)
**Restart Computer**? (I did just to be safe)
5. Plug in your phone. Go into device manager, and find your device. It should be listed as "One" with a yellow question mark.
6. Right click and update driver software
7. find your USB drivers you downloaded and choose to install those.
your device should now be listed under "Android USB Devices" as "My HTC"
When I did this, my phone skipped being labelled as "HTC MTP Device" all together
If it is not detected in ADB after installing drivers...
1. UNPLUG PHONE
2. Run USBDeview as administrator
3. Uninstall any unplugged devices
4. Restart computer
5. Plug in phone
{
"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"
}
and after verifying adb reboot bootloader worked. I thought, well heck. I'm sick of installing a file manager to install a file manager that's already stored on my sdcard.
and to verify it installed (no restart)
I hope this helps someone

done everything, nothing work. sees my HOX only while being ON and thus can't get the cid :/

pet3rs said:
done everything, nothing work. sees my HOX only while being ON and thus can't get the cid :/
Click to expand...
Click to collapse
What exactly are you trying to do? Did you install HTC Sync drivers? This is for using ADB on the old CM10/AOKP, not for rooting your phone

device is already rooted, I need to get adb working because I can't get my cid from fastboot command.

pet3rs said:
device is already rooted, I need to get adb working because I can't get my cid from fastboot command.
Click to expand...
Click to collapse
Boot your phone into fastboot from your bootloader
Sent from my HTC One XL using xda-developers app

i'm in fastboot and type adb shell getprop ro.cid, message says error: device not found. fastboot getvar cid returns CID: none

Found a great way that fixed it for me on Windows 8:
use this tool: http://www.nirsoft.net/utils/usb_devices_view.html to remove all instances of anything that has to do with HTC. Then, follow steps above to scan for new devices, and set the driver accordingly (with USB debugging on on the phone). It should register as "My HTC" and then you will be able to see the device in "adb devices" list.

pet3rs said:
i'm in fastboot and type adb shell getprop ro.cid, message says error: device not found. fastboot getvar cid returns CID: none
Click to expand...
Click to collapse
you can't use adb from fastboot. you use fastboot.exe e.g.
fastboot oem getvar cid
no adb needed.

Guys can u pls help me? I've done the above procedure for installing the drivers on my htc explorer, it all worked, in the device manager panel i can see My htc when i'm in fastboot, and i can see Android bootloader Interface when i'm in the bootloader, but nevertheless I can't run adb shell because it doesn't find the device, and when I run adb device it gives me an embty list, i must use adb in order to attemp to recover the nand that it's probably burned.

OPO not recognized in ADB Devices

Hey guys, I've long had this issue with my OnePlus One and I for the life of me cannot figure it out after searching and reading mad threads/forums.
Computer OS: Windows 7 x64
Problem: OnePlus One NOT RECOGNIZED under command > adb devices.
So I'm following all the instructions possible step by step. I have my OPO in Recovery (TWRP 2.8.6.0) and it won't show up as an ADB Devices...
Yet, noting key parameters here:
- All my drivers are up to date
- My Android SDK is up to date
{
"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"
}
- Java SE is up to date
FastBoot - Phone is recognized (picture below).
ADB Sideload Mode in TWRP Recovery - ADB Sideload recognizes OPO, but doesn't work still.
But standard ADB is not listed when Recovery is on main page. But I get this prompt whenever the phone boots into recovery or I plug it in via USB when Recovery is active.
This is my command prompt to prove FastBoot recognizes my device, but ADB does not.
What am I doing wrong? Can someone help me? I've noticed this issue as long as I can remember, and have resorted to always having to copy my ROM files through the OS, doing a factory reset, then installing. I have never been able to use ADB Push.
Can someone provide me some pointers?
Thanks!!!

do you have debugging enabled on the phone, and if you do, have you authorized that computer on the phone? (I guess you have already, but just throwing out some ideas you might have forgotten)

CSquared4290 said:
Hey guys, I've long had this issue with my OnePlus One and I for the life of me cannot figure it out after searching and reading mad threads/forums.
Computer OS: Windows 7 x64
Problem: OnePlus One NOT RECOGNIZED under command > adb devices.
So I'm following all the instructions possible step by step. I have my OPO in Recovery (TWRP 2.8.6.0) and it won't show up as an ADB Devices...
Yet, noting key parameters here:
- All my drivers are up to date
- My Android SDK is up to date
- Java SE is up to date
FastBoot - Phone is recognized (picture below).
ADB Sideload Mode in TWRP Recovery - ADB Sideload recognizes OPO, but doesn't work still.
But standard ADB is not listed when Recovery is on main page. But I get this prompt whenever the phone boots into recovery or I plug it in via USB when Recovery is active.
This is my command prompt to prove FastBoot recognizes my device, but ADB does not.
What am I doing wrong? Can someone help me? I've noticed this issue as long as I can remember, and have resorted to always having to copy my ROM files through the OS, doing a factory reset, then installing. I have never been able to use ADB Push.
Can someone provide me some pointers?
Thanks!!!
Click to expand...
Click to collapse
Firstly, uninstall all the drivers for your OPO from device manager and restart the system
Now, follow this link to install drivers >> http://www.technobuzz.net/install-oneplus-one-usb-drivers-windows/
After this, install adb and fastboot files >> http://forum.xda-developers.com/showthread.php?t=2317790
Even I have Android SDK installed on my system for developing apps, however, I used above steps to ensure that my system recognises my OPO

Mr hOaX said:
Firstly, uninstall all the drivers for your OPO from device manager and restart the system
Now, follow this link to install drivers >> http://www.technobuzz.net/install-oneplus-one-usb-drivers-windows/
After this, install adb and fastboot files >> http://forum.xda-developers.com/showthread.php?t=2317790
Even I have Android SDK installed on my system for developing apps, however, I used above steps to ensure that my system recognises my OPO
Click to expand...
Click to collapse
Thanks Mr. Hoax! I will give that a try and report back.
Interestingly in an attempt to use ADB Sideload to install the latest ROM update from scratch, I took a gamble and did a full format/wipe and was able to install the OS using ADB SideLoad. But afterwards, it still didn't come up under ADB Devices...But will try your recommendations and see what happens.
Elkhantar said:
do you have debugging enabled on the phone, and if you do, have you authorized that computer on the phone? (I guess you have already, but just throwing out some ideas you might have forgotten)
Click to expand...
Click to collapse
Yessir, Debugging was enabled through the OS (I don't know of any other way to enable debugging?)

Mr hOaX said:
Firstly, uninstall all the drivers for your OPO from device manager and restart the system
Now, follow this link to install drivers >> http://www.technobuzz.net/install-oneplus-one-usb-drivers-windows/
After this, install adb and fastboot files >> http://forum.xda-developers.com/showthread.php?t=2317790
Even I have Android SDK installed on my system for developing apps, however, I used above steps to ensure that my system recognises my OPO
Click to expand...
Click to collapse
Hey Mr. Hoax. I tried those steps, uninstalled every driver I could associate with any of my Android devices (have an HTC One as a backup) and sadly, ADB is still not recognizing my OPO when I enter "ADB Devices".
However, I still get the Windows prompt. Any clue?

Wug's tookit for bacon hv step by step procedure to install adb n fastboot drivers...gv it a try...i did it myself n it works nice
1+1

CSquared4290 said:
Hey Mr. Hoax. I tried those steps, uninstalled every driver I could associate with any of my Android devices (have an HTC One as a backup) and sadly, ADB is still not recognizing my OPO when I enter "ADB Devices".
However, I still get the Windows prompt. Any clue?
Click to expand...
Click to collapse
After drivers installation is done, you need to reboot your OPO in bootloader(fastboot) mode and type
fastboot devices
And check out if the prompt shows your device serial number.

I see you're using the nexus driver. Perhaps try a Samsung ADB driver. It works with my phone without problems.

I get the same problem with my work PC, while everything works fine at home.
What CSquared4290 says, applies here:
Computer OS: Windows 7 x64
Problem: OnePlus One NOT RECOGNIZED under command > adb devices.
- All my drivers are up to date
- My Android SDK is up to date
The phone is recognised normally under command > fastboot devices.
Symantec Endpoint Protection is running at my work PC. Could this be a reason?

CSquared4290 said:
Hey Mr. Hoax. I tried those steps, uninstalled every driver I could associate with any of my Android devices (have an HTC One as a backup) and sadly, ADB is still not recognizing my OPO when I enter "ADB Devices".
However, I still get the Windows prompt. Any clue?
Click to expand...
Click to collapse
100% agree with the other posters, really delete all of your old USB ADB drivers, including the Google USB driver. Here's a tool I use for that: http://www.nirsoft.net/utils/usb_devices_view.html
Install Samsung ADB drivers, then when you plug your OPO in you should be able to see it in Device Manager as "Android Device" don't let Windows pick the driver. Right click and pick the browse my computer for drivers, then find the Samsung Android ADB Interface, install that. Unplug your phone, then plug it back in...profit? Good luck!

From my OnePlus X rooting guide. It looks like you need to install the universal adb driver linked in #2 and follow the steps in #3.
If you cannot get the connection to work:
1. Check your USB connection, then verify that Android debugging is enabled in settings and that your computer’s RSA fingerprint has been authorized.
2. Still not working? Open Device Manager in Windows and make sure that you don’t have a yellow exclamation point next to something like “Android Device” or “One.” This would indicate a driver problem that must be resolved. Try re-installing the Universal Android ADB Driver for Windows, and make sure to restart your computer. Once you’ve rebooted, if you still have a yellow triangle, right-click on the device and select “Update Driver Software,” then “Search automatically for updated driver software.”
3. If you still have a yellow exclamation point, then try forcing the driver to install:
In Device Manager, right-click on the device and select “Update Driver Software.”
Select “Browse my computer for driver software”
Select “Let me pick from a list of device drivers on my computer”
Select “ADB Interface” from the list
Select manufacturer “Google”
Select “Android Testing Interface Version xxx”
Click “Next.” If you get a warning, select “Yes” to continue and wait for the driver to install properly.
Click to expand...
Click to collapse

[Resolved] How to successfully root PTCL Charji Wingle R660 and enable security and NAT features

Goal has been successfully achieved by a little bit of research and careful experimentation. Got to the middle of this post to find the complete solution.
I have a 4g Router Model: R660 also called 4g Wingle. The manufacturer is unknown as there is no branding on the device. But some say it is a GadgetIT product. I have scoured the internet and I cannot find the vendor named GadgetIT. But that is a separate discussion.
Main Goal: My main goal is to enable Virtual Server/Port forwarding in the device. The UI available when the device is connected is available at 192.168.1.1 with credentials admin/admin and Looks 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"
}
This device is marketed by ISP PTCL as CHARJI EVO . The users of PTCL charji on this forum might say that port forwarding is not possible in this device but I disagree. and I have evidence to support otherwise but again that is a separate discussion.
What I have found so far?
I am able to telnet to this device at 192.168.1.1 via admin/admin credentials. Here is what I get.:
Version
LNX.LE.4.1-41009-9x35
But admin is not root. There is a separate user called root which obviously has a different password. I have tried all common router password (not sure what all will constitute...but i have tried many).
The goal here is to root this device so that I can perform the necessary changes such as the following:
As you might have guessed by now, that i cannot unless I am root which I am not.
So I need your help guys. Here are other interesting things to look at:
I could edit mobileap_cfg.xml but I cannot because the file is readonly and I was unable to chmod it to 777 with an error message "Operation not permitted" indicating that I am not root and I can not make that happen.
The second thing i would like to do is to enable SNMP monitoring which I cannot do from the main interface because the vendor hid the option.
Lastly, enable firewall.
Interestingly, all these options are available in a tab called "Security" which the vendor has hidden from the configuration interface available at 192.168.1.1
So I am inviting the expert comments of all hackers that can help me make get it sorted out. Ideally, it would be awesome to have these options enabled from the UI (I am willing to hack, root this device and modify firmware if needed) to get this done.
This can potentially help millions of PTCL Charji Users who cannot run any kind of server using this device (including game servers) and any kind of listening services (sockets or WEB or FTP) r those who would like use torrents but suffer from terrible low download speeds on torrents because of not being able to open ports for incoming connections that significantly raise download speeds for torrent.
More details:
mobileap_cfg.xml ownership and permissions:
Appreciate your help. Waiting to hear helpful responses soon. Successfully rooted without any busy box.
Solution Achieved successfully- See Steps & detail as follows:
I was able to switch device to bootloader mode and was able to change root password and now I am able to switch to root mode when logged in via admin using telnet. I have successfully change the DMZ but i have yet to observe its effects. If it works, I will work on changing other values as well.
Detail:
The device closely resembles D-Link DWR 901 But mind you, it is NOT DWR 901. Even thought the radio matches, if you flash the firmware from DWR 901 (which will be successful), the device will NOT work. Since there is no available source of the original firmware of the device, the device will be of no use anymore. So do not do it.
Similary D-Link's DWM 222 is also similar to this device (only that DWM 222) is a 3G modem. I downloaded both firmwares and found out upon extraction of these firmwares, that it contains the following files.
Files that you actually need are present in this archive -
WARNING
Use at your own RISK!!. Flashing this directly to your Charji will brick you Charji device. So just follow the procedure I described and do not try to flash it directly otherwise it will render your device unable to connect even though everything will look all right in the software. The device will never connect again...ever!
https://www.dropbox.com/s/hqa2m4499pyrj3z/R660A-Donot-Flash-it-On-Charji-It-Will-Brick-Your-device.7z?dl=0
There is a file called dl.exe which can turn the device into download mode assumung you have the PTCL Charji Wingle R660 plugged into the USB port.
After that running adb devices command will list all the devices.
After that you need to run the following commands
Code:
adb shell
passwd
The adb shell command will take you to the shell.
The passwd command executed from shell will tell you to enter a new password for root user
You will have to provide a secure password for it to be accepted.
After that, it will update the root password.
exit the shell using the exit or quit command or simply close the command prompt.
Now, you can telnet to the device using the command
Code:
telnet 192.168.1.1
Login with username admin and password admin (if these are your credentials to access the router page, Use your credentials. Mine were admin/admin)
The issue the following command to switch to root mode
Code:
su
It will ask for root password. Enter the password you set using the adb shell you had used before. and viola. You will turn to root mode.
You you have two ways to fix the NAT/DMZ problem.
Either you can directly use the vi editor (my OpenEmbedded Linux OS installed on the device has only vi support) to edit the file mobileap_cfg.xml and update DMZ value and port forwarding values.
or you can enable the security tab by editing the menu.js file which is located in /WEBSERVER/www/ directory. Now I had a PTCL Charji R660. If you have a different device, your files will be located elsewhere with different sets of issues.
You can do whatever you want!
Older Updates
Update# 02:
DMZ is now working !!
Update# 03
Successfuly unlocked the hidden security tab but still untested. Will test it shortly.
Update # 04
Successfully unlocked Wizard
Update# 05
NAT Rules persisting and working, tested by download torrents and using CanYouSeeMe.ORG
Torrents Downloads working on max available speeds

Reserved 1

Reserved for additional instructions etc
Reserved 2

Good find but instructions are really ambiguous and unclear. What are you supposed to do with dl.exe? run it, stare at it, run it and press enter????
You are just trapping people into bricking their devices with this instruction.

Yes I am bad at providing instructions.
dl.exe once run, turns the charji into bootloader mode and then it is possible to run adb shell and adb commands.
Hope this helps. I will update the article to be more descriptive in future sometime. Don't have time right now.
Regards.

timematcher said:
dl.exe once run, turns the charji into bootloader mode and then it is possible to run adb shell and adb commands.
Click to expand...
Click to collapse
Ok you are still not being clear. What do you mean by run once? currently dl.exe shows
Code:
Welcome to use OnekeyUpdate Tool.
The Software to be updated:Desktop
Press 'Enter' to update or 'Q' to quit.
on opening. Should I press Enter?
Sorry about being rude in first comment. I am really angry right now over this device right now, what kind of stupidity is not allowing user to port forward.

raza1080p said:
Ok you are still not being clear. What do you mean by run once? currently dl.exe shows
Code:
Welcome to use OnekeyUpdate Tool.
The Software to be updated:Desktop
Press 'Enter' to update or 'Q' to quit.
on opening. Should I press Enter?
Sorry about being rude in first comment. I am really angry right now over this device right now, what kind of stupidity is not allowing user to port forward.
Click to expand...
Click to collapse
When you click Enter, it will say "Waiting for device...." and then "found"
That is the point the device will appear in device manager (on windows) as well. and Now is the time to run adb shell and corresponding commands in my first article.
Important thing to note is that if you have never rooted any android (or linux) based device/phone/tablet, I suggest you read more about running adb.
The goal of my article was the following:
1. reset root password on the OpenEmbedded Linux variant on teh charji wingle device
2. Login via Telnet to 192.168.1.1 (Charji web console) using admin/admin (default credentials of Charji)
3. change to root mode using su command
4. Be able to change the xml files ( i mentioned in the first post) that allow the user to create the firewall rules and virtual server entries.
Now at this point I did not know that the person who whitelabelled Charji wingle for PTCL simply had disabled the relevant code in menu.js that enabled the Virtual server entries and firewall entries and DMZ fields (that allow pot forwarding, open firewall or simply set an ip address for DMZ that opens everything to a single IP on charji local network).
Once I found out, I was really happy and now I created the virtual server entries for torrent which was my main problem.
Thanks to Dr.hack who created a proper tutorial on his blog based on information in this article in a more streamlined manner.
Dr. Hack's Blog, Root-hack-ptcl-charji-evo-nat/

thank you for the tutorial.I am trying it on a charji cloud R500A. when dl.exe finds the device it goes to "6% Downloading hex image" .Am i suppose to wait at this point?
And will i be able to use other sim on the the device after the root?

Tarar said:
thank you for the tutorial.I am trying it on a charji cloud R500A. when dl.exe finds the device it goes to "6% Downloading hex image" .Am i suppose to wait at this point?
And will i be able to use other sim on the the device after the root?
Click to expand...
Click to collapse
First things first!, Are you trying to flash the image from the firmware link I gave? You should really not do that!
The link i gave is only provided for firmware modding experts. It is not the firmware of Charji. So if you flash it, it will brick your device and it will become useless.
What you really need to use is th dl.exe file , copy it into a separate folder with no other stuff in it.
If you run it from the same folder, it will brick your device by flashing a firmware which will not work for your Charji. CHarji will never connect after that!
dl.exe must be run to turn the device into booloader mode, After that you have to run adb shell commands and make the necessary changes to reset the root user password.
I don't know if it will allow you to use another SIM or not. PTCL devices are usually NOT network locked. But again, this is not a tutorial for allowing the users to use another sim. It merely allows the user unlock Virtual Server, Firewall, DMZ settings and similar features which are hidden by PTCL.
And there is no such thing as "Telenet". Telnet is a client application in windows which is not installed by default. You will have to install Telnet Client from "Add Remove programs" in Windows. It is needed to access the device using the telnet protocol. Do some research on Telnet.

timematcher said:
First things first!, Are you trying to flash the image from the firmware link I gave? You should really not do that!
The link i gave is only provided for firmware modding experts. It is not the firmware of Charji. So if you flash it, it will brick your device and it will become useless.
What you really need to use is th dl.exe file , copy it into a separate folder with no other stuff in it.
If you run it from the same folder, it will brick your device by flashing a firmware which will not work for your Charji. CHarji will never connect after that!
dl.exe must be run to turn the device into booloader mode, After that you have to run adb shell commands and make the necessary changes to reset the root user password.
I don't know if it will allow you to use another SIM or not. PTCL devices are usually NOT network locked. But again, this is not a tutorial for allowing the users to use another sim. It merely allows the user unlock Virtual Server, Firewall, DMZ settings and similar features which are hidden by PTCL.
And there is no such thing as "Telenet". Telnet is a client application in windows which is not installed by default. You will have to install Telnet Client from "Add Remove programs" in Windows. It is needed to access the device using the telnet protocol. Do some research on Telnet.
Click to expand...
Click to collapse
Thank you so very much for the details.
Yeah i found out about telnet commands.but i was using the dl.exe in the same folder.i guess that's why adb devices wasn't able to find my device.
Luckily it didn't install that firmware.

I have bricked my device by accidentally runing the gui.exe and i was dont know that it will flash new firmware. is there any way to get back ?:crying:

If you are able to switch to fastboot mode and you have the original software in the right format, then you should be able to flash the new firmaware using the utilities provided in the original post. The only way I think. I will try to see if I can create an image for my Charji R660 but I can not promise anything.
Note that I bricked first of mine and I took it to the people who upgrade firmware of the device and they were unable to fix it. and I got a new one by being sneaky (and playing dubm) about it.
Or if you want to learn, maybe start experimenting a little bit but I think you will need the original firmware.

timematcher said:
When you click Enter, it will say "Waiting for device...." and then "found"
That is the point the device will appear in device manager (on windows) as well. and Now is the time to run adb shell and corresponding commands in my first article.
Important thing to note is that if you have never rooted any android (or linux) based device/phone/tablet, I suggest you read more about running adb.
The goal of my article was the following:
1. reset root password on the OpenEmbedded Linux variant on teh charji wingle device
2. Login via Telnet to 192.168.1.1 (Charji web console) using admin/admin (default credentials of Charji)
3. change to root mode using su command
4. Be able to change the xml files ( i mentioned in the first post) that allow the user to create the firewall rules and virtual server entries.
Now at this point I did not know that the person who whitelabelled Charji wingle for PTCL simply had disabled the relevant code in menu.js that enabled the Virtual server entries and firewall entries and DMZ fields (that allow pot forwarding, open firewall or simply set an ip address for DMZ that opens everything to a single IP on charji local network).
Once I found out, I was really happy and now I created the virtual server entries for torrent which was my main problem.
Thanks to Dr.hack who created a proper tutorial on his blog based on information in this article in a more streamlined manner.
Dr. Hack's Blog, Root-hack-ptcl-charji-evo-nat/
Click to expand...
Click to collapse
Hi dear friend how are you? I need original webui of PTCL Charji device For Huawei Ec8372u-876 device please can you share the link or any guidance for this

saqi755 said:
Hi dear friend how are you? I need original webui of PTCL Charji device For Huawei Ec8372u-876 device please can you share the link or any guidance for this
Click to expand...
Click to collapse
Or any other links of non modified original Loced Huawei firmware and Webui

Huawei Ec8372u-876 is a very good device compared to sh!t devices offered by PTCL before.
Here is what I have found on the web.
Its probably an unlocking solution and not a locked file.
I am in no way responsible for the quality of the file or the steps as I dont have this device and I can not test it before posting.
Please use these are your own risk. I at least downloaded the file and executed on local PC.
but that is pretty much it. Please use at your own risk.
PTCL Evo Charji Cloud
E5377u-872
How to Unlock Evo Charji E5377u-872
1: Battery Should be 100% Charged
2: Data Cable
3: A Pin
4. Unlocked file
Click to expand...
Click to collapse
Code:
www.mediafire.com/file/6td2bh12b4l6g9o/PTCL_charji_E5377u-872-www.hispeedsolution.com.exe/file
Process>>
1. Remove the battery from the device
2. Press & Hold Power Button + Reset Button on the same time after 5 seconds device will boot into download mode.
3. Connect to PC
4. Wait for drivers
5. After the drivers installed go to device manager & note down the port # namely appplication UI interface.
6. Run the *.exe file & enter the port # (E.g 19 or 20 or etc etc)
7. Let it flash the device, it will take about 5 minutes, after the flashing let the device reboot. Your device will stuck on the Huawei screen, Don't worry wait for 3 minutes then remove the battery insert any Sim card & turn on the device.
8. Your device is successfully unlocked on all network Sim.
9. Connect the device to PC & set up accordingly.
Click to expand...
Click to collapse

timematcher said:
Huawei Ec8372u-876 is a very good device compared to sh!t devices offered by PTCL before.
Here is what I have found on the web.
Its probably an unlocking solution and not a locked file.
I am in no way responsible for the quality of the file or the steps as I dont have this device and I can not test it before posting.
Please use these are your own risk. I at least downloaded the file and executed on local PC.
View attachment 5369881
but that is pretty much it. Please use at your own risk.
Code:
www.mediafire.com/file/6td2bh12b4l6g9o/PTCL_charji_E5377u-872-www.hispeedsolution.com.exe/file
Click to expand...
Click to collapse

Thanks for your cooperation but I need file for Ec8372u-876 this file is not working on this please check this again this is not a device with battery

Let me look into it.

timematcher said:
timematcher said:
Can we use other networks 4G in this device?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Please reply if possible

sparking111 said:
Please reply if possible
Click to expand...
Click to collapse
Huawei 4G wingle should support other networks/SIMs once rooted.
I had a E8372h-608 4G wingle which was network locked to Telenor. After flashing it with network-neutral, universal firmware from huawei, it works for Ufone, Telenor, Warid/Jazz after appropriate AP configuration within the device UI.
Does that answer your query?

How To Root Any Android Device~! Part 1

=================================================
================================
HOW TO ROOT ANYTHING ANDROID
=============================
===========================​
Hello Friends~!
I am working out a Series of Threads that I want to string together to sort of go over the many nuances and intricacies of unlocking a device's bootloader and flashing Roms.
This is part 1, unlocking the bootloader, part 2 will be rom flashing oriented, and will be added to a separate thread whenever the heck I work it out~!
Part 3? Will be taking the adb tools and building our first piece of Open Source "Software" on Windows, with a GUI, to make using ADB easier and more fun~!
Please Note That There Is No "One Best Way" To Do Anything In Rooting and Computing in General. There are Many Ways~! As evidenced here:
Spoiler: THE MOST EPIC ROOT
[CLOSED]HaHaHack Dis: No Magisk REQUIRED!!!!
Magisk is no more... I present a new fool proof method of flashing su to Android 10_Q and above!! I ranted and ranted about variant=user/user-debug/eng builds that I got no-where... people thinkin am dissin john wu, nah, I respect what I've...
forum.xda-developers.com
This Guide Is Catered To Take Someone Down "The Path", Who Has Never Done A "Root" before, For An Android Device, On Windows~!
Spoiler: DISCLAIMER
Note that this Guide cannot Currently help if you have purchased an Android Device from a Proprietary Manufacturer, that Locks the Bootloader with Efuse Chip Technology..
eFuse - Wikipedia
en.wikipedia.org
Spoiler: GETTING STARTED
You will need some options enabled in File Explorer, if you don't have them already...
Press the Windows Key and type "folder"
That should pull up an option for "File Explorer Options" Select it, then..
Make sure "Display the Full Path" is ticked.
Select, "Show Hidden Files and Folders"
UNTICK hide extensions for known file types.
Spoiler: 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"
}
Spoiler: GETTING ADB AND THE USB DRIVERS
Download Android Studio & App Tools - Android Developers
Android Studio provides app builders with an integrated development environment (IDE) optimized for Android apps. Download Android Studio today.
developer.android.com
Spoiler: PROGRAMMING OUR DEVICE FOR ADB
Spoiler: A QUICK NOTE ABOUT MANUALLY ACCESSING THE BOOTLOADER
For Knowledge Purposes~!
You can usually use a combination of the power and volume keys, to access the bootloader.
This can also be done with devices like Google's Chromecast
Which uses a method involving the usb cable itself, and the back button... android boxes, etc.
Sometimes the bootloader can be accessed with controllers or keyboards, but this method is Not Universal for all Manufacturers and or Devices~!
Since we setup ADB Fully, we will make the method to access the Bootloader Partition of the Android Device, Universal, on Windows, by using the Command Line...
So we will use adb Instead of an Analouge Method..
Spoiler: EXAMPLES OF MANUALLY POWERING INTO THE BOOTLOADER
Since we will use ADB From the Start, we will Avoid Having to Figure out the Manual Method for our Devices.
For instance...
Spoiler: VISUAL EXAMPLES
This video Illustrates the Common Volume and Power button Method~!
The beginning of this video shows using a controller method, which would equate to holding a+b on a USB 3.0 keyboard, to post into the NVIDIA Shield's Bootloader. USB 3.0 Mattering in this, Device Specific, Case~!
Spoiler: ENABLE DEVELOPER OPTIONS
We will need to enable developer options for our device~!
This process Is Universal, But Only Universal to Your Android Firmware Version, IE Android 10,11,12 and if it is a TV, Phone, etc~!
Every Firmware will simply Require some form of you going into Settings, finding the "About" section on the device, Finding the build number,
Then select your Build 7 times. There's tons of videos on this step, Should you get hung up on your Particular device~!
Spoiler: ENABLE USB DEBUGGING AND OEM UNLOCKING
Once you have Developer Settings Unlocked, you need to go into the actual "Developer Settings" tab and enable these options..
Your browser is not able to display this video.
Spoiler: INSTALLING THE WINDOWS USB DRIVER FOR YOUR DEVICE
Now that we have USB ADB Debugging Enabled on Our Device, and OEM Unlocking, we can plug the device into our PC, and open Device Manager.
Your device will likely show up as either "fastboot", "other", or an "unknown" device.
Right Click that device, then install the driver as shown below..
Spoiler: INSTALLING THE WIN_USB DRIVER
Your browser is not able to display this video.
Spoiler: DOWNLOAD
Here is a link for a Mirror of Google's Universal USB DRIVER, if you need:
FASTBOOT DRIVER.zip
drive.google.com
Spoiler: DRIVER TROUBLESHOOTING
SAVE YOURSELF A HEADACHE AND KNOW FROM THE START, THAT THE GOOGLE USB DRIVERS AND FASTBOOT DO NOT WORK WITH SOME USB 3.0 DEVICES...
FOR INSTANCE, LATER MODEL LAPTOPS.... IF YOU FIND YOURSELF GETTING A CODE 1O ERROR, USE A USB 2.0 HUB TO ATTACH YOUR ANDROID DEVICE TO THE PC.
Spoiler: CODE10ERROR
Spoiler: USING ADB TO BOOT INTO THE BOOTLOADER
Now we should be able to open command prompt, type: adb devices, and see our device attached.
Spoiler: LIKE THIS
Spoiler: PASTE THIS COMMAND
adb reboot bootloader
Spoiler: BOOTLOADER PICS
You should have one of two results from this command..
Spoiler: BOOTLOAD IMAGE1
If your device shows this:
Spoiler: SHOW IMAGE
Then your device uses fastbootd and will require us to run a different command.
Remove the USB cable from your device, then hold the power key down for 10-20 seconds.
Your device will Power Off. Power it back on.
When it has fully rebooted, plug the usb cable back in, make sure USB debugging is Enabled and Run this Command:
Spoiler: PASTE THIS
adb reboot fastboot
Which will put us in fastbootd
Spoiler: WHAT IS FASTBOOT D
"Android 10 and higher supports resizable partitions by relocating the fastboot implementation from bootloader to userspace.
This relocation enables moving the flashing code into a maintainable and testable common location with only the vendor-specific
parts of fastboot implemented by a hardware abstraction layer (HAL)."
"In addition, Android 12 and higher supports flashing ramdisks through an added fastboot command."
--SOURCE.ANDROID.COM
Essentially, some devices may have this new fastboot scheme, meaning we will have a few new commands to work with when using fastboot..
Requiring a change in Semantics~!
In FastbootD, a noticeable difference in Semantics is the process of "Unlocking" the bootloader.
Traditionally, one would simply boot into the bootloader, and issue a command of "fastboot oem unlock" and that would get the job done.
However, with the integration of FastbootD, we too have to learn to speak it's new Language~!
So Instead, to get the same effect, we would use this command:
Spoiler: UNLOCK FLASHING IN FASTBOOTD
This part may or may not require OEM Specific Fastboot commands.
type:
fastboot flashing unlock
If successful, you're ready to Flash, which will be covered in part 2...
If not we need to look at figuring out our device's fastboot OEM commands, which can be vendor specific and will be covered on this guide, using the G20 as an example..
Mapping Out The G20's Internals
================================== ===================================== NOKIA G20 ALL ADB SHELL COMMANDS ========================================= Hello Friends, Welcome To.... My Book~! xD ===================== This Thread's mostly being put...
forum.xda-developers.com
Spoiler: BOOTLOAD IMAGE2
Else, if your device shows something like this:
Spoiler: SHOW IMAGE
You're ready to continue...
Spoiler: UNLOCK BOOTLOADER
You should now see an option to "Unlock" The Bootloader, Do So~!
THIS WILL DELETE THE DATA ON YOUR DEVICE~! YOU HAVE BEEN WARNED~!
Unlocking the bootloader will allow you to be able run this fastboot command:
fastboot oem unlock
to "Unlock" or allow your device's partitions to be modified, flashed, erased, etc~! I.E. Giving us "Root" Access~!
Spoiler: ADB TROUBLESHOOTING
If you do not see your device attached, remove the usb cable from the device, and remove the usb hub cable if using one, reset the Android device.
When the device is fully booted, reattach the usb cable and/or hub, and verify USB Debugging is showing on the device.
Spoiler: LIKE THIS
Your browser is not able to display this video.
This is the end of part 1, part 2+ will involve the intricacies of building and flashing of A Rom for our devices~!
<333333
Spoiler: REFS
How to enter Recovery mode on Nokia G10/G20?
Hello everyone. This is my post here on XDA. I'm using Nokia G20 TA-1365 Model (INDIA). Let's get to the tutorial. Prerequisites: 1. A Windows PC. 2. ADB and Fastboot Drivers. 3. Nokia G20 or G10. Switch off your Nokia G20 device. Press and...
forum.xda-developers.com
joegib's post on the thread above taught me about fastbootd
joegib
forum.xda-developers.com
This article goes into fastbootd, which I hadn't heard of before
What is fastbootd? How to Enable and Boot?
Google introduced the Android 10 operating system back in September 2019. Android 10 brought in new support for resizable partition which relocates the
www.getdroidtips.com
FastbootD Source Code
Moving Fastboot to Userspace | Android Open Source Project
source.android.com
This video explains Super Partition Better
What are Ram Disks
RAM Disks Explained: What They Are and Why You Probably Shouldn’t Use One
Your computer’s RAM is still faster than even modern solid-state drives. RAM disks take advantage of this, using your computer’s RAM as a lightning-fast virtual drive. But you probably don’t want to use a RAM disk, anyway.
www.howtogeek.com
How to unlock bootloader on Nokia G20 - ROM-Provider
step by step guide to unlock bootloader on Nokia G20, after unlocking the bootloader you can root it by using the magisk
romprovider.com
Android Kitchens~! Or at least some tools to edit the bootimg for future reference
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
GitHub - szym/unbootimg: The complement to Android's mkbootimg
The complement to Android's mkbootimg. Contribute to szym/unbootimg development by creating an account on GitHub.
github.com
Please feel free to share any details below related to bootloader unlocking, adb, fastboot, etc~! I learn A Lot from You Guys~!
LEARN HOW TO MAP OUT YOUR DEVICE'S INTERNALS
Mapping Out The G20's Internals
================================== ===================================== NOKIA G20 ALL ADB SHELL COMMANDS ========================================= Hello Friends, Welcome To.... My Book~! xD ===================== This Thread's mostly being put...
forum.xda-developers.com
Hello from Jen in August 2022. A TLDR, I spent 5 months learning that android literally is linux i.e. all the bin files are ambidextrous and therefore a lot of the articles I link for knowledge to the systems on this device are linux specific.
The exercise and effort of mapping out the device taught me a lot. Highly recommend doing it once if you are brand new. I learned so much about Linux in a way I could personally digest.

An Addendum,
Some devices have a "preloader", a layer before the bootloader. I am working through learning how to bypass and explain that whole mess. Idk how long it will take.
With that out of the way, I have an idea how one Could Actually Root any Android device, just not conventionally.
What I mean is, and this is all in theory and being developed now https://forum.xda-developers.com/t/...r-android-devices-windows-10-nox-lab.4481613/
What if you could just use a simple app like limbo to boot up a pre-installed with root and magisk android image?
Breaking it down further, what if it was possible to run a virtual machine image of android that was pre-rooted with pre-installed apps (i.e. a custom rom)
That would in theory allow one to keep the integrity of the main system, while working or playing on the virtual machine.
This is a project being started from the grassroots by a crazy cat lady. Feel free to help develop our new Machine, "Root" if you can. I will begin running isos tomorrow
Oh, and There's This News Today~!

[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?