[Q] How to enable DIAG mode on Defy? (For QPST)

[Q] How to enable DIAG mode on Defy? (For QPST) - Defy Android Development

I moved this from the general forum as I think it might be more related to android development (sort of)
Does anyone know how to enable "DIAG" or diagnostic mode on the defy?
(This is required to identify itself correctly to Qualcomm Phone Support Tools as well as other things)
It seems you just need to hold "T" during boot to do this on a Droid, and only enable USB debugging on a Droid X
On some phones like the Samsung Fascinate apparently only this is required:
Code:
Settings - Wireless Networks - Enable Dialup Networking
Also, either:
Code:
echo 1 > /dev/qct_diag_enable
or
Code:
echo 1 > /sys/devices/virtual/usb_composite/diag/enable
are said to work for "many" CM7 phones
But I can't find anything about doing it on a defy. Anyone know how you can do this?

Well, I contacted Motorola, and they told me:
Motorola said:
diagnostic modes are only for the information of the technicians, not the end users. We will not be able to provide you any information about this.
Click to expand...
Click to collapse
I paid for this phone, I don't see why they can't tell me how to use the diagnostic mode. They could have just said that it will void your warranty if you use it...
Anyway the important part seems to be setting the modem to diagnostic passthrough, but I'm not sure how you actually do that. Setting it to data passthrough seems to be what USB tethering does, so I'm going to look into that now.
If anyone has any ideas on this or knows the command to enable the diagnostic mode, let me know!
EDIT: The phone portal usb setting aready opens a data port on 192.168.16.2:8080 and I need to open a diagnostics port on 192.168.16.2:11008 as well. Is this likely to be something simple like a command to open the port and the modem will already be listening on that port? I don't know much about networking in linux/android

Try.... it for usbd
usb_mode_ngp
usb_mode_modem_adb
usb_mode_msc_adb
usb_mode_charge_adb
usb_mode_rndis
usb_mode_mtp

Sorry Quarx, I don't understand what those are! Are they commands that I have to type somewhere?
The closest I can find is things like this:
Code:
/sys/devices/virtual/usb_composite/rndis/enable
but nothing seems to happen if I "echo 1 > enable" - it still stays as a 0

try to hold vol+ vol- and power button while boot.

For example.
# Enable ADB mode
write /dev/usb_device_mode msc_adb

@drakeM: That boots in safe mode, which stops non-essential services from starting, but I can't get diagnostic mode through it (or I don't know how to)
@Quarx: I couldn't get those commands to work - I don't have "write" on any of the ROMs I've tried, so I tried echo, which didn't work. I got an error of "could not create /dev/usb_device_mode: error 16"
I tried doing it like this:
Code:
echo mtp > /dev/tempfile
mv /dev/tempfile /dev/usb_device_mode
This ran without errors for all the commands, but I don't think it did anything. I don't know if that was because of the way I did it?
Apparently you can enable diagnostic mode from fastboot:
Code:
fastboot oem rtask c
Is it possible to reboot into fastboot, maybe with 2nd init?

mmec2 said:
I don't have "write" on any of the ROMs I've tried
Click to expand...
Click to collapse
write is for *.rc in rootfs, or other *.rc files that might be imported.

racca said:
write is for *.rc in rootfs, or other *.rc files that might be imported.
Click to expand...
Click to collapse
oh..... ok, so I need to put one of the commands in the "on boot" section of init.rc, restart then try again etc. etc.

Ok, am I doing something stupid? init.rc and init.mapphone_umts.rc get recreated every boot. How can I change them? They just keep changing back to the original version every time I reboot.

Related

ATTN: Backup your boot0 block today

ATTENTION: PUBLIC SERVICE ANNOUNCEMENT
It has come to my attention that under certain circumstances when the Kindle HD's get stuck in a bootloader bootloop the information on the "boot0" block of the internal storage can be ERASED and RESET.
This partition is special and contains ALL of your device's hardware specific information:
- Wifi MAC address + Encoded Secret for registering w/ Amazon services
- BT MAC address
- Serial #
etc
FOR BACKING UP THIS PARTITION:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb pull /sdcard/boot0block.img
Place the "boot0block.img" file with the other files that you backed up in the original instructions for safe keeping.
FOR RESTORING THIS PARTITION:
(do not do this unless you are absolutely SURE that your boot0 block got wiped out -- hopefully you never need to)
This is done via adb from your PC while the device is in TWRP recovery or in the Android OS (not fastboot):
Code:
cd <your safekeeping files>
adb push boot0block /sdcard/boot0block.img
adb shell "echo 0 > /sys/block/mmcblk0boot0/force_ro; dd if=/sdcard/boot0block.img of=/dev/block/mmcblk0boot0;"
THIS FILE IS UNIQUE TO YOUR DEVICE AND CANNOT BE REPLACED OR REBUILT FROM ANOTHER DEVICE. DO NOT SHARE IT WITH ANYONE AS IT CONTAINS INFORMATION ABOUT YOUR DEVICE USED BY AMAZON DURING REGISTRATION.

very interesting Hashcode,thanks for the information :good:

Odd, I can't seem to find the file after I pulled it with ADB.
EDIT: I didn't even assign the command an output location to begin with. LOL.

Thanks for the info.
How can I access KFHD via ADB if CM10.1 installed.
I can't see my device in device manager only as a media storage or sth like that.
Should I remove KFHD adb driver and install the google driver?
Or just using the hidden trick in cm10.1?
"Enable Developer options in your phone (Settings > About phone and tap Build Number until you are a developer (about 7 times)
Set root access for APPS and ADB in: Settings > Developer Options > Root Access
Enable Android debugging at the same page (Developer Options). Enable ADB over network if you need.
Check if your Settings > Security > Unknown Sources is checked. you will need it to install over ADB."
Yeah...it helped

esox_hu said:
Thanks for the info.
How can I access KFHD via ADB if CM10.1 installed.
I can't see my device in device manager only as a media storage or sth like that.
Should I remove KFHD adb driver and install the google driver?
Or just using the hidden trick in cm10.1?
"Enable Developer options in your phone (Settings > About phone and tap Build Number until you are a developer (about 7 times)
Set root access for APPS and ADB in: Settings > Developer Options > Root Access
Enable Android debugging at the same page (Developer Options). Enable ADB over network if you need.
Check if your Settings > Security > Unknown Sources is checked. you will need it to install over ADB."
Yeah...it helped
Click to expand...
Click to collapse
Just turn on ADB debugging on the tablet, and plug it into the computer. On the computer, open command prompt, use the command "adb devices" to see if your ADB is working.
Other than that, I don't know what happened in your post.

Ok i really can't figure this one out, I used adb many times while testing KFFAide tool so I am 100% sure my adb drivers are installed correctly, But since i switched to cm10.1 (Thanks hashcode) ADB cannot recognize my device anymore, I have enabled ADB on my KFHD and when i connect it to my pc a small notification appears "Android debugging enabled" but when i use "adb devices" command nothing shows up!
Can anyone help me with this i'm completely lost here!

AmrBanawan said:
Ok i really can't figure this one out, I used adb many times while testing KFFAide tool so I am 100% sure my adb drivers are installed correctly, But since i switched to cm10.1 (Thanks hashcode) ADB cannot recognize my device anymore, I have enabled ADB on my KFHD and when i connect it to my pc a small notification appears "Android debugging enabled" but when i use "adb devices" command nothing shows up!
Can anyone help me with this i'm completely lost here!
Click to expand...
Click to collapse
Leave the device plugged in, go to Developer Setting and uncheck ADB debugging, then check it again. You should see a prompt, select OK for both.

seokhun said:
Leave the device plugged in, go to Developer Setting and uncheck ADB debugging, then check it again. You should see a prompt, select OK for both.
Click to expand...
Click to collapse
Ok thanks i tried but to no avail

AmrBanawan said:
Ok thanks i tried but to no avail
Click to expand...
Click to collapse
Yeah I actually have the same problem too now

Thanks for the heads up hash, got it on a usb stick now
---------- Post added at 11:41 PM ---------- Previous post was at 11:39 PM ----------
Protomartyr said:
Yeah I actually have the same problem too now
Click to expand...
Click to collapse
I had to manually check android debugging and usb debugging notify and it worked just fine.... make sure adb over network is not checked

Protomartyr said:
Yeah I actually have the same problem too now
Click to expand...
Click to collapse
AmrBanawan said:
Ok thanks i tried but to no avail
Click to expand...
Click to collapse
Why don't you guys try this, go into CMD while connected with the device (ADB debugging on), and type "adb devices" to start the daemon, then try the commands. Other than that, I don't know what else to do.

seokhun said:
Why don't you guys try this, go into CMD while connected with the device (ADB debugging on), and type "adb devices" to start the daemon, then try the commands. Other than that, I don't know what else to do.
Click to expand...
Click to collapse
Nope. Just get "List of Devices Attached" but no serial number. Checked device manager and it's showing up as a portable device. Probably will reinstall them and see if that solves it.
On a side note:
if we ran these commands in terminal emulator on the device, would that be sufficient?

Protomartyr said:
Nope. Just get "List of Devices Attached" but no serial number. Checked device manager and it's showing up as a portable device. Probably will reinstall them and see if that solves it.
On a side note:
if we ran these commands in terminal emulator on the device, would that be sufficient?
Click to expand...
Click to collapse
Yes
run the first command then pull it manually
But we need to know what's going on, i will need adb sometime soon when prokennexusa releases the next version of KFFAide

AmrBanawan said:
Yes
run the first command then pull it manually
But we need to know what's going on, i will need adb sometime soon when prokennexusa releases the next version of KFFAide
Click to expand...
Click to collapse
you can always open up your device manager and manually apply the adb drivers to your kindle

How do we know the boot0 partition is erased?
Sent from a Kindle Fire HD running CM10.1 using Tapatalk 2

had same probs on cm10 getting the files no matter what i tried.in windows 7 and xp it wouldnt install normal driver so i could see kindle as a drive so flashed an amazon zip and pc recognizes it without any problems and now have the files needed

dugoy13 said:
How do we know the boot0 partition is erased?
Sent from a Kindle Fire HD running CM10.1 using Tapatalk 2
Click to expand...
Click to collapse
Normally you would notice WiFi doesn't work under any circumstances same for BT. And when on Amazon's software it won't let you register.
Sent from my Amazon Kindle Fire HD using Tapatalk 2

I can't get ADB to find it either, think i'll revert back to stock to get the file then go back to CM - I notice though on CM turning USB Debugging on doesn't change anything in device manager, it still stays connected as a media device or camera, depending on which you have ticked in storage setting *shrugs*
Thank you Hashcode

PaulJCW said:
I can't get ADB to find it either, think i'll revert back to stock to get the file then go back to CM - I notice though on CM turning USB Debugging on doesn't change anything in device manager, it still stays connected as a media device or camera, depending on which you have ticked in storage setting *shrugs*
Thank you Hashcode
Click to expand...
Click to collapse
No don't, just type the command hashcode provided in terminal emulator and you'll find the backup in your sdcard, just copy it to your pc like normal!

You can do it from the terminal without typing ADB. that may be why people are confused. Start with hashcodes command but start with "su -c" in the terminal.
Sent from my Nexus S 4G using xda app-developers app

[question] how to enable htc diagnostics interface via adb or terminal emulator

Hello... I have being at this for a long time. I have been googling and searching Xda but no better results. I want to enable the HTC's DIAG MODE via adb-shell or terminal emulator. In most HTC devices running stock HTC ROMS, this can be enabled by entering certain codes in the dailer but it doesnt work on the DESIRE HD's stock rom.
I managed to find some commands.
This one
Code:
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
And this
Code:
echo 1 > /sys/devices/virtual/usb_composite/diag/enable
First one works on non sense roms and the second one works on sense roms. They actually trigger the diag mode when they are issued but when i open QPST, it says no phone although it detects the port been opened,same thing applies to DFS. In device manager i can see the HTC DIAGNOSTICS INTERFACE there. I installed the driver but its still wouldnt work.
This leaves me to think that maybe i havent enabled all the functions needed for diagmode to work.
Reason why i have come to this conclusion is that, with the samsung devices, you would have to enter 3 to 4 commands to have the mode activated.
If anyone has been able to activate diagmode on thier HTC device via adb or terminal, pls share. As many people might be depending on this to fix thier devices(changed imeis after jtag).

mickeyasamoah said:
Hello... I have being at this for a long time. I have been googling and searching Xda but no better results. I want to enable the HTC's DIAG MODE via adb-shell or terminal emulator. In most HTC devices running stock HTC ROMS, this can be enabled by entering certain codes in the dailer but it doesnt work on the DESIRE HD's stock rom.
I managed to find some commands.
This one
Code:
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
And this
Code:
echo 1 > /sys/devices/virtual/usb_composite/diag/enable
First one works on non sense roms and the second one works on sense roms. They actually trigger the diag mode when they are issued but when i open QPST, it says no phone although it detects the port been opened,same thing applies to DFS. In device manager i can see the HTC DIAGNOSTICS INTERFACE there. I installed the driver but its still wouldnt work.
This leaves me to think that maybe i havent enabled all the functions needed for diagmode to work.
Reason why i have come to this conclusion is that, with the samsung devices, you would have to enter 3 to 4 commands to have the mode activated.
If anyone has been able to activate diagmode on thier HTC device via adb or terminal, pls share. As many people might be depending on this to fix thier devices(changed imeis after jtag).
Click to expand...
Click to collapse
AnyOne?

Galaxy S5 with broken screen, need help controlling it from PC

Hi, I've got an old S5 with a broken screen. There's no image going on and there's no indication that the touchscreen is working.
I'm not looking to recover data, I'm looking to play around with it by controlling it from my PC. Last I remember, the phone is running a Cyanogenmod OS (I don't think LineageOS was around at that time) with either TWRP or CWM recovery, but I'd bet on TWRP.
Now: the device reaches the OS properly, I can tell because if I try to turn the ringing sound up it gives me an audio feedback.
If I connect it to a PC from the OS:
- the phone shows up in Windows Explorer as "SM-G900F"
- Device Manager shows me a "SAMSUNG Mobile USB Composite Device" under Universal Serial Bus controllers
However I cannot access any files (Windows Explorer shows the device as empty), and if I attempt to 'adb devices' in the console it shows me an empty devices list.
Now, I suspect that USB debugging might be off. So I also tried connecting it to a PC from recovery and the exact same thing as above can be observed, PLUS:
- Device manager also shows me a "SAMSUNG Android Phone" list which can be expanded to show me one entry called "SAMSUNG Android ADB Interface"
However it's the same as before, no files available and 'adb devices' shows an empty list.
Now I heard that I can theoretically enable USB debugging through ADB, by writing to a config file. That would allow me to enable USB debugging and try something like Vysor in order to control the phone from my PC.
However that's a moot point until I can figure out why the ADB service on my PC isn't seeing the device. Any help would be greatly appreciated, and if you need more info I can provide it.
Extra info:
- I installed Samsung USB drivers at some point while trying to make it work
- Windows Explorer shows a phone icon for this device, and if I recall correctly that's what happens when it's connected through MTP (Mass Storage should show it like a memory card)

_sepiroth said:
Hi, I've got an old S5 with a broken screen..........
Click to expand...
Click to collapse
I've never experienced this situation myself but, I've seen that the following thread has worked for many individuals.
https://forum.xda-developers.com/showthread.php?t=2786395
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.

Ibuprophen said:
I've never experienced this situation myself but, I've seen that the following thread has worked for many individuals.
https://forum.xda-developers.com/showthread.php?t=2786395
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
Click to expand...
Click to collapse
Thanks a bunch, that pointed me in the right direction with my research! I solved my issue, I can now control my phone from my PC.
By doing this I ran into a couple of problems, I'm going to describe them and their solutions:
Problem 1: couldn't ADB into the device when in Recovery Mode. That is because after a long head scratching session I came to the conclusion that I didn't have TWRP Recovery installed (I had Philz Touch CWM Recovery and LineageOS 14.1 instead).
Solution 1: ADB mode is enabled in TWRP by default. So I flashed the latest TWRP through Odin, ADB instantly started working afterwards in Recovery Mode.
Problem 2: USB Debugging was disabled inside the OS.
Solution 2: from the thread that Ibuprophen posted, you can enable USB debugging in your OS by opening an ADB shell into your device and modify the build.prop like so
Code:
Adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop
reboot
Problem 3: /system was empty so there was no build.prop. If I attempted to create a build.prop file it wouldn't be saved after a device reboot, so USB debugging still didn't work.
Solution 3: it seems like TWRP doesn't mount /system by default, only /data. You can mount it manually through ADB like this:
Code:
mount -o rw /dev/block/bootdevice/by-name/system /system
I found this out from this stackexchange question: https://android.stackexchange.com/q...data-partitions-in-recovery-mode-in-adb-shell
Problem 4: When an app tries to use USB Debugging you need to allow it to do so from the phone. Since the screen was broken, I couldn't do this.
Solution 4: You'll need to push a public key to your device with ADB. Boot into Recovery Mode and make sure your device is recognized by your PC and type
Code:
adb push <path to adbkey.pub on your PC> /data/misc/adb/adb_keys
This solution is from: https://stackoverflow.com/questions...b-rsa-key-with-broken-touch-screen-on-android
This will make sure that you won't need to confirm debugging permissions for apps coming from your machine.
So for anyone who has a broken phone screen (my screen is dead and touchscreen/touch buttons are kaput too) and wishes to control their phone from their PC but USB debugging is disabled:
1. Boot device in TWRP Recovery (flash it if you don't have it)
2. ADB into the device
3. Make sure /system is mounted (if it's empty it means it's not mounted), else mount it manually like in Solution 3
4. Configure build.prop to have USB Debugging enabled like in Solution 2
5. Push your public key to the device like in Solution 4
6. Restart the phone (into its OS)
7. Download the Chrome extension called Vysor and launch it
8. Connect your phone through a USB cable
9. The device should appear in Vysor, connect to it and have fun controlling it
Note that if you just want to backup your files, steps 1 + 2 are sufficient. After making sure ADB works you can just 'adb pull' all your files which should be located in /sdcard. Google it, it's easy to find.
The same goes for backups, you can do them directly through ADB.
Again, thanks Ibuprophen!

Vysor does not work on all graphic cards. a good free alternative is scrcpy
btw instead of flashing twrp, you can flash a modified system partition with proper entries in build.prop (for those with no custom recovery available)

aIecxs said:
Vysor does not work on all graphic cards. a good free alternative is scrcpy
btw instead of flashing twrp, you can flash a modified system partition with proper entries in build.prop (for those with no custom recovery available)
Click to expand...
Click to collapse
Very well pointed out, thanks for this.

Resetting Verizon Orbic Speed RC400L firmware flash Kajeet

I purchased a used Kajeet branded Orbic Speed RC400L hotspot off eBay which came with a charger, carrying case and Verizon SIM. I went though the Verizon prepaid activate website and it says the device is compatible and the Verizon sim card in it will work, however I noticed when I powered on the hotspot many menu settings were locked out.
I then connected to the hotspot and navigated to 192.168.1.1 and following Verizon's manual for this device I entered in admin as the username and the wifi password as the password and nope, wasn't able to log in. To make matters worse I decided to swap a Verizon prepaid SIM from another device and everything appeared to work, it showed signal however it had no internet, and when I looked into this further I realized this device is programmed with a different APN than the Verizon default for Kajeet's services, and I can't log in to change this.
I then attempted to hold down the reset button on the device for 5 seconds following Verizon's manual for this device while it was powered on and it did not reset, nothing I did would let me factory reset the device.
I then started to look into other options.
If I connect the device powered off to a laptop via USB, press and hold both the power and reset buttons I hear the device connect sound on Windows. I checked Device Manager and see the device as a Qualcomm device on COM10. I opened up QPST which confirms this device is on COM10 and in download mode.
This is good news as this appears to be how I can flash new firmware onto this device, but sadly there is no instructions on how to do this nor the stock Verizon firmware to download for this device.
When connecting the device powered up normally QPST detects it on COM10 but isn't able to read any info about the device at all.
I am stuck now on what to do, part of me wants to activate it on Verizon prepaid and then call Verizon when it has no internet and see if they can remotely reset it or program the right APN settings into the device to see if it'll work, however I don't know if they'll be able to do this.

I’m looking into acquiring a second Orbic Speed hotspot new from Verizon and making a backup of that firmware and then flashing it to this other hotspot using the Qualcomm download mode to recover it as well as uploading it and making instructions here for anyone else who runs into this issue.
That seems to be the only way to do a complete hard reset since the firmware on the one I have is locked and the reset button doesn’t do anything in its regular powered up state.
There are various tutorials for Qualcomm based devices on how to make an entire firmware backup or dump of the device so I’m hoping those will work with this device as well.
I’d like to see if anyone can root this hotspot given it reportedly runs Linux and install a modified OS on it as well as do band unlocking and allow it to work on any carrier too, I’ll see if I can get more info about the hardware and which Qualcomm chipset it uses.
You can obtain one of these hotspots new for a significant discount by purchasing a used Ellipsis MHS900L and exchanging it under the recall that exists for these devices.

TheTechDude48 said:
I’m looking into acquiring a second Orbic Speed hotspot new from Verizon and making a backup of that firmware and then flashing it to this other hotspot using the Qualcomm download mode to recover it as well as uploading it and making instructions here for anyone else who runs into this issue. Omegle app
That seems to be the only way to do a complete hard reset since the firmware on the one I have is locked and the reset button doesn’t do anything in its regular powered up state.
There are various tutorials for Qualcomm based devices on how to make an entire firmware backup or dump of the device so I’m hoping those will work with this device as well.
I’d like to see if anyone can root this hotspot given it reportedly runs Linux and install a modified OS on it as well as do band unlocking and allow it to work on any carrier too, I’ll see if I can get more info about the hardware and which Qualcomm chipset it uses.
You can obtain one of these hotspots new for a significant discount by purchasing a used Ellipsis MHS900L and exchanging it under the recall that exists for these devices.
Click to expand...
Click to collapse
Xposed is incompatible with the ART runtime. That means it won't work on Lollipop.

How can i
Make an backup of a normal orbic hotspot

I have an Orbic Speed that I got in exchange for an Ellipse with the battery problem.
I had already wasted more money on the 8800L so I really didn't need the Orbic.
I was playing around trying to get it into EDL mode.
The normal connect is RNDIS.
I tried to find EDL test points, but nothing seemed to work.
I tried beating on it and actually got it into 11f6/900e QHSUSB__BULK, which is certainly strange. (Should be 05c6/9008).
I haven't been able to get there again, it may have just been really corrupted. Also, it didn't respond correctly to Sahara and got wedged.
But... I did find a test point to reliably put it into Fastboot mode! I was surprised. I can getvar and reboot but no reboot-edl or oem edl.
The test point is under the top left corner of the LCD, the first point in the corner. Just ground it during reset.
You have to ease the LCD display up a bit.
Does anyone know any good Orbic OEM commands?
Edit: Lol! That was quick. I just discovered that if you connect the "Fastboot" test point to the test point immediately to the right it goes into EDL.
I haven't got a loader for it, but Sahara gives me HWID: 000480e100000000, MSM: 000480e1, OEM: 0000, Model: 0000, Hash: cc3153a80293939b.
I haven't found a loader yet because my internet is so crappy. Yeah, Verizon.
For Fastboot: Connect Sense to Gnd
For EDL: Connect Sense to 1.8V
If you're timid, use a resistor (I used a 1k).
The loader that you want is:
https://github.com/bkerler/Loaders/qualcomm/patched/mdm9x07/prog_nand_firehose_9x07.mbn
This uses NAND storage.
The partioning is not GPT, it's something else.
Partitions are: sbl, mibib, efs2, dynamic_nv, efs2_bak, tz, rpm, aboot, boot, scrub, modem, misc, recovery, usrdata, recoveryfs, sec, system
The boot image is Red Hat UBI.
Edit: I got tired of this thing sitting around disassembled, so I soldered in a tiny magnetic reed switch and buttoned it up.
Now if I want to get to EDL I just park a magnet in the top of the case and hit reset.
I did this before to my ereader (Onyx Poke3) too.

@Renate
Are you still fooling with this device?
I told you I got one a couple weeks ago, I have my workup done for it. I also go the factory for it and patched it so it actually works now lol, it would only work before if you were on I think it was v1.5.1 now I have it set to force load everytime and patched the version check, I have full reloadable firmware made up for it now and can erase the device to 0 and then recover it to fully working.
I never could get that loader to work, i have to find a diff one for this model
here is a few screenshots
imei repair was different for this one than on other similar devices
We were talking about its comports in that 8800 thread, I baked enabled ports into the first firmware build I made for this one but then later found a way to enable them without needing to load firmware, if you need your ports enabled on yours hit me up.
Someone sent me a moxee device a few days ago and while they are basically the same looking device it is a deceiving similarity, cannot use the same firmware or loader and the board layouts are much different, the Verizon orbic model is much better than the moxee device at first glance the only notable diff is the micro USB port but looks can be deceiving lol.
the dumbed-down kernel with almost none of the needed modules makes it live up to its entry-level status.

Mmm, I don't need dumber Verizon hot spots, I need a smarter one!
It's too bad that the NetGear NightHawk M1 and M6 don't have the Verizon bands.

I have put hundreds of M1's on vzw, it only lacks b13 but most markets have 2, 4 & 66, they work fine on vzw and M6 I have put many on vzw also

Figured out a few things about my RC400L. First, to enable ADB, send a USB control message of type LIBUSB_REQUEST_TYPE_VENDOR, request 0xa0, a value of 0, and no data. The device will now reboot. adb is now enabled, but rndis has been disabled (regardless of what you set USB tethering to). However, it's also exposed the DIAG and AT endpoints, so if you have drivers installed for that you can just connect to the AT port and send AT+SER=9,1 which will switch to a mode that exposes adb, diag, at, and rndis. adb is running as an unprivileged user, but if you connect over the AT interface you can also run AT+SYSCMD= with a Linux command after the equals sign, and it'll run that as root. I was hoping to find a way to reboot into fastboot via software but haven't had any luck on that so far, so I guess I'll have to crack the case open.

Unfortunately it's not possible to configure the Orbic to just boot when plugged into USB - it's actually booting Linux, but simply displaying a charging screen instead of enabling USB or starting the modem stack. This is controlled by the "androidboot.poweronreason=" parameter that's passed on the kernel command line, and several different components parse this. The easiest solution I've found is to dump the bootloader (it's /dev/mtdblock7) and search for the byte sequence "03 02 00 0a 20" and replace the 20 with ff. 20 is the value read from the power management controller that indicates the device powered up because it was plugged into USB - replacing that with ff means the bootloader no longer understands that, and falls back to describing it as a hard reset. This value is interpreted as a legitimate bootup and everything works.

mjg59 said:
Unfortunately it's not possible to configure the Orbic to just boot when plugged into USB - it's actually booting Linux, but simply displaying a charging screen instead of enabling USB or starting the modem stack. This is controlled by the "androidboot.poweronreason=" parameter that's passed on the kernel command line, and several different components parse this. The easiest solution I've found is to dump the bootloader (it's /dev/mtdblock7) and search for the byte sequence "03 02 00 0a 20" and replace the 20 with ff. 20 is the value read from the power management controller that indicates the device powered up because it was plugged into USB - replacing that with ff means the bootloader no longer understands that, and falls back to describing it as a hard reset. This value is interpreted as a legitimate bootup and everything works.
Click to expand...
Click to collapse
Any chance at getting some 5000 foot guide/direction on how to do this? I haven't messed with ADB in the last 10 or so years . I would love to get my RC400L setup to auto start from a powered off state when the USB power is connected. My use case is a rpi running a remote weather station and camera that posts to twitter every 5 minutes. I have access to the setup, but it's a 15 minute drive each way!

Renate said:
I have an Orbic Speed that I got in exchange for an Ellipse with the battery problem.
I had already wasted more money on the 8800L so I really didn't need the Orbic.
I was playing around trying to get it into EDL mode.
The normal connect is RNDIS.
I tried to find EDL test points, but nothing seemed to work.
I tried beating on it and actually got it into 11f6/900e QHSUSB__BULK, which is certainly strange. (Should be 05c6/9008).
I haven't been able to get there again, it may have just been really corrupted. Also, it didn't respond correctly to Sahara and got wedged.
But... I did find a test point to reliably put it into Fastboot mode! I was surprised. I can getvar and reboot but no reboot-edl or oem edl.
The test point is under the top left corner of the LCD, the first point in the corner. Just ground it during reset.
You have to ease the LCD display up a bit.
Does anyone know any good Orbic OEM commands?
Edit: Lol! That was quick. I just discovered that if you connect the "Fastboot" test point to the test point immediately to the right it goes into EDL.
I haven't got a loader for it, but Sahara gives me HWID: 000480e100000000, MSM: 000480e1, OEM: 0000, Model: 0000, Hash: cc3153a80293939b.
I haven't found a loader yet because my internet is so crappy. Yeah, Verizon.
For Fastboot: Connect Sense to Gnd
For EDL: Connect Sense to 1.8V
If you're timid, use a resistor (I used a 1k).
The loader that you want is:
https://github.com/bkerler/Loaders/qualcomm/patched/mdm9x07/prog_nand_firehose_9x07.mbn
This uses NAND storage.
The partioning is not GPT, it's something else.
Partitions are: sbl, mibib, efs2, dynamic_nv, efs2_bak, tz, rpm, aboot, boot, scrub, modem, misc, recovery, usrdata, recoveryfs, sec, system
The boot image is Red Hat UBI.
Edit: I got tired of this thing sitting around disassembled, so I soldered in a tiny magnetic reed switch and buttoned it up.
Now if I want to get to EDL I just park a magnet in the top of the case and hit reset.
I did this before to my ereader (Onyx Poke3) too.
Click to expand...
Click to collapse
magnetic reed switch is so ****ing clever so it doesnt have to be disassembled to use testpoints for edl

chimchim54321 said:
Any chance at getting some 5000 foot guide/direction on how to do this? I haven't messed with ADB in the last 10 or so years . I would love to get my RC400L setup to auto start from a powered off state when the USB power is connected. My use case is a rpi running a remote weather station and camera that posts to twitter every 5 minutes. I have access to the setup, but it's a 15 minute drive each way!
Click to expand...
Click to collapse
Ok, this is extremely at your own risk - I've attached a zip file with a couple of files.
Download https://www.verizon.com/support/verizon-orbic-speed-mobile-hotspot-update-instructions/ and install it.
Unzip this zip file into the update app directory
Download https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html .
Plug in your hotspot
Run the update app. Hit start. Wait until you hear the Windows device disconnected sound and unplug your hotspot. Quit the update app.
Plug your hotspot back in. Device Manager should now show a bunch of com ports that weren't there before.
Open a command prompt and go to the update app directory. Run adb push orbic/* /tmp
Run Putty and tell it to make a serial connection. Choose the COM port that Device Manager has listed with AT in the name.
Type AT. You should get back an "OK" response. Type AT+SYSCMD=cp /tmp/sshell /sbin
Type AT+SYSCMD=chown root /sbin/sshell
Type AT+SYSCMD=chmod 4755 /sbin/sshell
Go back to the command prompt and run adb shell
Type sshell
This is the dangerous part. If you want to modify your existing bootloader, run dd if=/dev/mtdblock7 of=/tmp/aboot and then use adb pull to copy it back to your computer. Modify it as described above, and then use adb push to copy it back into /tmp on the hotspot. If you're willing to risk bricking your device if the bootloader is somehow incompatible, you can just use the copy that was in the zip file.
adb shell back into the device and run sshell again. Run dd if=/tmp/aboot of=/dev/mtdblock7 oflags=sync . The patched bootloader is now installed. Run reboot.
It's probably fine to just use the bootloader I've included, but it does seem to vary between firmware releases, so if you feel up to patching it yourself then I'd recommend that (make sure that your bootloader only contains one copy of the byte sequence I mention - if there's more then let me know and I'll figure out where the patch needs to go.

mjg59 said:
Ok, this is extremely at your own risk - I've attached a zip file with a couple of files.
Download https://www.verizon.com/support/verizon-orbic-speed-mobile-hotspot-update-instructions/ and install it.
Unzip this zip file into the update app directory
Download https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html .
Plug in your hotspot
Run the update app. Hit start. Wait until you hear the Windows device disconnected sound and unplug your hotspot. Quit the update app.
Plug your hotspot back in. Device Manager should now show a bunch of com ports that weren't there before.
Open a command prompt and go to the update app directory. Run adb push orbic/* /tmp
Run Putty and tell it to make a serial connection. Choose the COM port that Device Manager has listed with AT in the name.
Type AT. You should get back an "OK" response. Type AT+SYSCMD=cp /tmp/sshell /sbin
Type AT+SYSCMD=chown root /sbin/sshell
Type AT+SYSCMD=chmod 4755 /sbin/sshell
Go back to the command prompt and run adb shell
Type sshell
This is the dangerous part. If you want to modify your existing bootloader, run dd if=/dev/mtdblock7 of=/tmp/aboot and then use adb pull to copy it back to your computer. Modify it as described above, and then use adb push to copy it back into /tmp on the hotspot. If you're willing to risk bricking your device if the bootloader is somehow incompatible, you can just use the copy that was in the zip file.
adb shell back into the device and run sshell again. Run dd if=/tmp/aboot of=/dev/mtdblock7 oflags=sync . The patched bootloader is now installed. Run reboot.
It's probably fine to just use the bootloader I've included, but it does seem to vary between firmware releases, so if you feel up to patching it yourself then I'd recommend that (make sure that your bootloader only contains one copy of the byte sequence I mention - if there's more then let me know and I'll figure out where the patch needs to go.
Click to expand...
Click to collapse
Some of the steps are just a touch off on syntax, but it all worked successfully with my edit of aboot locally on my Windows machine via the HxD app.
Does the battery bypass file work to allow the RC400L to boot without the battery installed? If so, is the file specific to the RC400L?

chimchim54321 said:
Some of the steps are just a touch off on syntax, but it all worked successfully with my edit of aboot locally on my Windows machine via the HxD app.
Does the battery bypass file work to allow the RC400L to boot without the battery installed? If so, is the file specific to the RC400L?
Click to expand...
Click to collapse
Oh, please let me know what I screwed up and I'll fix it in case anyone else follows this! But no, as far as I can tell if the battery is missing the code changes behaviour at an earlier point, and I haven't looked into that (or whether it's even possible for it - some devices insist on the battery because they may instantaneously draw more power than is provided over USB and rely on the battery to make up for it). But this specific patch is very specific to the RC400L bootloader, and the entire process would probably need to be modified for other devices.

rich hathaway said:
I have put hundreds of M1's on vzw, it only lacks b13 but most markets have 2, 4 & 66, they work fine on vzw and M6 I have put many on vzw also
Click to expand...
Click to collapse
B13 at 750 MHz is very important when you're in the sticks.
In contrast, 5G is something that will never make any difference to me.
(A bit off-topic)
I'm currently running PtMP (microwave) internet off a Ubiquiti LTU Mini and a separate router/WiFi.
I'd like to be able to seasonally switch over to a 4G LTE modem with only wired ethernet.
So I don't want a modem with anything (no NAT, no WiFi), only a RJ45.
I see the NetGear LM1200. Is this any good? That 5G is useful to at least discount the 4G equipment.
Also, this is a battery-less device.
I never liked the MiFi 8800L. I found that when the LTE reception was flailing it would disrupt the regular connection between local devices on the WiFi.

mjg59 said:
Ok, this is extremely at your own risk - I've attached a zip file with a couple of files.
Download https://www.verizon.com/support/verizon-orbic-speed-mobile-hotspot-update-instructions/ and install it.
Unzip this zip file into the update app directory
Download https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html .
Plug in your hotspot
Run the update app. Hit start. Wait until you hear the Windows device disconnected sound and unplug your hotspot. Quit the update app.
Plug your hotspot back in. Device Manager should now show a bunch of com ports that weren't there before.
Open a command prompt and go to the update app directory. Run adb push orbic/* /tmp
Click to expand...
Click to collapse
step 7 - my win10 PC didn't care for the orbic/* portion. Either use just "orbic" or use orbic/sshell (unteseted but would likely work)
mjg59 said:
Run Putty and tell it to make a serial connection. Choose the COM port that Device Manager has listed with AT in the name.
Type AT. You should get back an "OK" response. Type AT+SYSCMD=cp /tmp/sshell /sbin
Click to expand...
Click to collapse
second half of step 9, the path is wrong and strangely the terminal responds back with OK. The path should be /tmp/orbic/sshell
mjg59 said:
Type AT+SYSCMD=chown root /sbin/sshell
Type AT+SYSCMD=chmod 4755 /sbin/sshell
Go back to the command prompt and run adb shell
Type sshell
This is the dangerous part. If you want to modify your existing bootloader, run dd if=/dev/mtdblock7 of=/tmp/aboot and then use adb pull to copy it back to your computer. Modify it as described above, and then use adb push to copy it back into /tmp on the hotspot. If you're willing to risk bricking your device if the bootloader is somehow incompatible, you can just use the copy that was in the zip file.
adb shell back into the device and run sshell again. Run dd if=/tmp/aboot of=/dev/mtdblock7 oflags=sync . The patched bootloader is now installed. Run reboot.
It's probably fine to just use the bootloader I've included, but it does seem to vary between firmware releases, so if you feel up to patching it yourself then I'd recommend that (make sure that your bootloader only contains one copy of the byte sequence I mention - if there's more then let me know and I'll figure out where the patch needs to go.
Click to expand...
Click to collapse
I think that was it for the issues I had. At least with the directions The adb pull put the file in a weird AppData path location, and perhaps a fully qualified path for the target of the pull would be advisable.
My old modem would often sort of flip out and require a power cycle to get back to normal. I built a relay module that could be operated by one of the gpio pins on the Rpi, and it would cut the external power as well as the internal battery. Was much easier as the internal battery had wires and a plug that I could splice into. For this modem I think I'm going to have to design and print a battery adapter that will allow me to put a set of relay contacts between the battery tabs and the modem battery buttons.

Renate said:
B13 at 750 MHz is very important when you're in the sticks.
In contrast, 5G is something that will never make any difference to me.
Click to expand...
Click to collapse
Yes the lower end of the spectrum is better for penetrating buidings and such, but if you have a tower (line-of-site) or maybe not to far and not to obstructed b13 is not needed to get good service, I have a tower at about 8miles not line of site and b66 works fine for me here on an m1
Renate said:
I'd like to be able to seasonally switch over to a 4G LTE modem with only wired ethernet.
So I don't want a modem with anything (no NAT, no WiFi), only a RJ45.
I see the NetGear LM1200. Is this any good? That 5G is useful to at least discount the 4G equipment.
Also, this is a battery-less device.
Click to expand...
Click to collapse
I have not had that device before so I am not familiar with it and not sure what it costs but the m2000 is a fine device and can run without a battery with a simple mod, no rj45 coming out but the usb-C can be cheaply adapted over to rj45, and this device can be bought for cheap (35 bucks) on ebay if you look around there are many for 50 bucks out there.
if you need help pulling in signal in your location the FW2000 is an excellent device, its expensive but I can tell you I am using one now and it is a beast with built in high power antennas it really pulls the signal in and is battery - less

Phone's screen partially working, need to activate USB Debug

Hello everyone,
my phone (Xiaomi MI 9T) has fallen in the water and now it's partially working.
I really need to recover some data from it, but any method I've found on the internet requires USB Debug active. The phone turns on but it works only as long as it stays on the lock screen or if I go to settings from the notification bar. If I unlock it, the launcher doesn't work (but I can still drag down the notification's bar) and after few seconds the phone reboots I'm also able to activate the toggle of the USB Debug but it looks like it doesn't stay active because if I go back and re-enter developer's section, USB Debug is OFF.
At this point I don't really know what to do. The phone enters fastboot and recovery mode, unfortunately everything is stock, so my possibilities are limited.
I haven't tried to change the screen, but I doubt that would solve the problem, since if I stay in those specific areas, it works fine.
Android version: 10
MIUI 12
Thank you

Dona2592 said:
Hello everyone,
my phone (Xiaomi MI 9T) has fallen in the water and now it's partially working.
I really need to recover some data from it, but any method I've found on the internet requires USB Debug active. The phone turns on but it works only as long as it stays on the lock screen or if I go to settings from the notification bar. If I unlock it, the launcher doesn't work (but I can still drag down the notification's bar) and after few seconds the phone reboots I'm also able to activate the toggle of the USB Debug but it looks like it doesn't stay active because if I go back and re-enter developer's section, USB Debug is OFF.
At this point I don't really know what to do. The phone enters fastboot and recovery mode, unfortunately everything is stock, so my possibilities are limited.
I haven't tried to change the screen, but I doubt that would solve the problem, since if I stay in those specific areas, it works fine.
Android version: 10
MIUI 12
Thank you
Click to expand...
Click to collapse
Due to the security implications of remotely enabling USB Debugging, the only way to enable it is through Developer Options. You can try rebooting to recovery and clearing cache although I am doubtful as to how much that might help you. If your device took a swim, you're going to be looking at repair, which will most likely result in wiping your data.

V0latyle said:
Due to the security implications of remotely enabling USB Debugging, the only way to enable it is through Developer Options. You can try rebooting to recovery and clearing cache although I am doubtful as to how much that might help you. If your device took a swim, you're going to be looking at repair, which will most likely result in wiping your data.
Click to expand...
Click to collapse
Do you know if changing the screen could solve the problem? Or do you think there's a way to copy data 1:1 on another device (such as a used mi 9t I could buy)?

Dona2592 said:
Hello everyone,
my phone (Xiaomi MI 9T) has fallen in the water and now it's partially working.
I really need to recover some data from it, but any method I've found on the internet requires USB Debug active. The phone turns on but it works only as long as it stays on the lock screen or if I go to settings from the notification bar. If I unlock it, the launcher doesn't work (but I can still drag down the notification's bar) and after few seconds the phone reboots I'm also able to activate the toggle of the USB Debug but it looks like it doesn't stay active because if I go back and re-enter developer's section, USB Debug is OFF.
At this point I don't really know what to do. The phone enters fastboot and recovery mode, unfortunately everything is stock, so my possibilities are limited.
I haven't tried to change the screen, but I doubt that would solve the problem, since if I stay in those specific areas, it works fine.
Android version: 10
MIUI 12
Thank you
Click to expand...
Click to collapse
How long ago was it dropped in water, have you allowed it thoroughly dry out? Can you open the body of the device to allow it to dry?

Droidriven said:
How long ago was it dropped in water, have you allowed it thoroughly dry out? Can you open the body of the device to allow it to dry?
Click to expand...
Click to collapse
It stayed in the water for few seconds, the bottom half of it. I shut it down and I let it dry for 2 days, after removing the battery. Anyway I brought it to a center that made a treatment for electronic contacts, an they said that it's needed to change the display first, then run some tests to see what else is wrong. The problem is that changing the screen costs 130€ and, in my opinion, won't solve the issue.

Dona2592 said:
It stayed in the water for few seconds, the bottom half of it. I shut it down and I let it dry for 2 days, after removing the battery. Anyway I brought it to a center that made a treatment for electronic contacts, an they said that it's needed to change the display first, then run some tests to see what else is wrong. The problem is that changing the screen costs 130€ and, in my opinion, won't solve the issue.
Click to expand...
Click to collapse
Can you find a stock update for your specific model number in the form ol stock update.zip that can be flashed in your stock recovery like a OTA update? If so, you might be able to extract the build.prop file from the update then open the build.prop file in a note editor and edit the file by adding or editing lines that enable USB debugging. Then save the file. Then remove everything from the update.zip except for the Meta-inf or "updater script" file/folder then place your modified build.prop file in the update.zip so that it is the only thing in the zip other than the Meta-inf/updater script. Then put it on external sdcard, insert it into your device and boot into stock recovery then choose the option that lets you install updates from sdcard and try flashing your modified update.zip file and reboot the device, if it works, it will enable USB debugging. The next obstacle is getting past your lock screen, which is pointless if the device reboots in seconds. If you can get it to stop rebooting, you might be able to use adb to unlock the lock screen by using adb commands that simulate the touch input required to unlock the screen. You'll have to do some searching to find out the "address" and order of each part of the screen that you need to simulate the touch input on the screen in the right order. It's a bit complicated for those that aren't familiar but it can be done if you do the research.
Or,you can try connecting a USB mouse to the device and see if it will let you open the lock screen.

Droidriven said:
Can you find a stock update for your specific model number in the form ol stock update.zip that can be flashed in your stock recovery like a OTA update? If so, you might be able to extract the build.prop file from the update then open the build.prop file in a note editor and edit the file by adding or editing lines that enable USB debugging. Then save the file. Then remove everything from the update.zip except for the Meta-inf or "updater script" file/folder then place your modified build.prop file in the update.zip so that it is the only thing in the zip other than the Meta-inf/updater script. Then put it on external sdcard, insert it into your device and boot into stock recovery then choose the option that lets you install updates from sdcard and try flashing your modified update.zip file and reboot the device, if it works, it will enable USB debugging. The next obstacle is getting past your lock screen, which is pointless if the device reboots in seconds. If you can get it to stop rebooting, you might be able to use adb to unlock the lock screen by using adb commands that simulate the touch input required to unlock the screen. You'll have to do some searching to find out the "address" and order of each part of the screen that you need to simulate the touch input on the screen in the right order. It's a bit complicated for those that aren't familiar but it can be done if you do the research.
Or,you can try connecting a USB mouse to the device and see if it will let you open the lock screen.
Click to expand...
Click to collapse
Droidriven said:
Can you find a stock update for your specific model number in the form ol stock update.zip that can be flashed in your stock recovery like a OTA update? If so, you might be able to extract the build.prop file from the update then open the build.prop file in a note editor and edit the file by adding or editing lines that enable USB debugging. Then save the file. Then remove everything from the update.zip except for the Meta-inf or "updater script" file/folder then place your modified build.prop file in the update.zip so that it is the only thing in the zip other than the Meta-inf/updater script. Then put it on external sdcard, insert it into your device and boot into stock recovery then choose the option that lets you install updates from sdcard and try flashing your modified update.zip file and reboot the device, if it works, it will enable USB debugging. The next obstacle is getting past your lock screen, which is pointless if the device reboots in seconds. If you can get it to stop rebooting, you might be able to use adb to unlock the lock screen by using adb commands that simulate the touch input required to unlock the screen. You'll have to do some searching to find out the "address" and order of each part of the screen that you need to simulate the touch input on the screen in the right order. It's a bit complicated for those that aren't familiar but it can be done if you do the research.
Or,you can try connecting a USB mouse to the device and see if it will let you open the lock screen.
Click to expand...
Click to collapse
The procedure looks good, I'd give it a try but is there any alternative to the SD card? Cause my phone has no SD slot available. Maybe an external usb card reader to plug into the phone?

Dona2592 said:
The procedure looks good, I'd give it a try but is there any alternative to the SD card? Cause my phone has no SD slot available. Maybe an external usb card reader to plug into the phone?
Click to expand...
Click to collapse
Yes USB should work in place of sdcard

Dona2592 said:
Plus, I don't really get why the system fails right after the lockscreen, I'm actually able to enter the code and the phone unlocks but the launcher seems not working, while the notifications bar works fine, and after some seconds the phone reboots. How can the system work fine in some aspects and bad in others at the same time? Can it be some flash memory issue?
Click to expand...
Click to collapse
That or kernel panic due to some other important hardware is damaged.
Maybe you can use a adb script to interrupt the running processes right after the device unlocks. Something to stop everything from loading beyond screen unlock. It might allow you to use adb to pull whatever you want from the device via adb pull commands.
Or, if there is a custom recovery for your device and if your bootloader is already unlocked(if it isn', don't unlock it, it will wipe your data), you can install the custom recovery and use it to create a backup of your data then extract your data from the backup.

Droidriven said:
That or kernel panic due to some other important hardware is damaged.
Maybe you can use a adb script to interrupt the running processes right after the device unlocks. Something to stop everything from loading beyond screen unlock. It might allow you to use adb to pull whatever you want from the device via adb pull commands.
Or, if there is a custom recovery for your device and if your bootloader is already unlocked(if it isn', don't unlock it, it will wipe your data), you can install the custom recovery and use it to create a backup of your data then extract your data from the backup.
Click to expand...
Click to collapse
Unfortunately I still have the stock recovery. Plus USB debug is deactivated. What really boggles me is the fact that I can still enter settings and get to developer options, turn ON the toggle of USB debug, but it's like the phone doesn't save the setting, cause if I go back to the main setting screen and enter again developer options, USB debug is OFF. I mean, what the hell?

Having access to device's Stock Recovery you can try as shown below to enable ADB / USB Debug ging: yes you can run Android shell commands from within Android's Stock Recovery.
Unplug device's USB-connection , boot into recovery mode. Having successfully booted into recovery mode, connect device via USB-cable with computer - what switches the USB driver to ADB mode.
Now enable USB debugging via recovery:
Code:
adb shell
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=adb,mtp" >> /system/build.prop"
reboot

Dona2592 said:
Unfortunately I still have the stock recovery. Plus USB debug is deactivated. What really boggles me is the fact that I can still enter settings and get to developer options, turn ON the toggle of USB debug, but it's like the phone doesn't save the setting, cause if I go back to the main setting screen and enter again developer options, USB debug is OFF. I mean, what the hell?
Click to expand...
Click to collapse
Hardware damaged. You're going to have to repair the hardware or forget about retrieving your data, unless you can find a reputable shop that has the equipment and experience to pull your data directly from the chip itself.

xXx yYy said:
Having access to device's Stock Recovery you can try as shown below to enable ADB / USB Debug ging: yes you can run Android shell commands from within Android's Stock Recovery.
Unplug device's USB-connection , boot into recovery mode. Having successfully booted into recovery mode, connect device via USB-cable with computer - what switches the USB driver to ADB mode.
Now enable USB debugging via recovery:
Code:
adb shell
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=adb,mtp" >> /system/build.prop"
reboot
Click to expand...
Click to collapse
Thanks mate, I'll give it a try for sure

Droidriven said:
Hardware damaged. You're going to have to repair the hardware or forget about retrieving your data, unless you can find a reputable shop that has the equipment and experience to pull your data directly from the chip itself.
Click to expand...
Click to collapse
Ok, but do you know what could be the damaged piece of hardware?

Dona2592 said:
Ok, but do you know what could be the damaged piece of hardware?
Click to expand...
Click to collapse
NO

xXx yYy said:
Having access to device's Stock Recovery you can try as shown below to enable ADB / USB Debug ging: yes you can run Android shell commands from within Android's Stock Recovery.
Unplug device's USB-connection , boot into recovery mode. Having successfully booted into recovery mode, connect device via USB-cable with computer - what switches the USB driver to ADB mode.
Now enable USB debugging via recovery:
Code:
adb shell
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=adb,mtp" >> /system/build.prop"
reboot
Click to expand...
Click to collapse
That might work but I've never had any luck with adb in stock recovery, not on the devices that I've owned, at least.

Dona2592 said:
Hello everyone,
my phone (Xiaomi MI 9T) has fallen in the water and now it's partially working.
I really need to recover some data from it, but any method I've found on the internet requires USB Debug active. The phone turns on but it works only as long as it stays on the lock screen or if I go to settings from the notification bar. If I unlock it, the launcher doesn't work (but I can still drag down the notification's bar) and after few seconds the phone reboots I'm also able to activate the toggle of the USB Debug but it looks like it doesn't stay active because if I go back and re-enter developer's section, USB Debug is OFF.
At this point I don't really know what to do. The phone enters fastboot and recovery mode, unfortunately everything is stock, so my possibilities are limited.
I haven't tried to change the screen, but I doubt that would solve the problem, since if I stay in those specific areas, it works fine.
Android version: 10
MIUI 12
Thank you
Click to expand...
Click to collapse
Is your bootloader locked?

Droidriven said:
That might work but I've never had any luck with adb in stock recovery, not on the devices that I've owned, at least.
Click to expand...
Click to collapse
Yeah in fact when I type "adb shell" it gives me error, but I can enter fastboot mode and the phone is seen. Unfortunately I can't do much from there

Arealhooman said:
Is your bootloader locked?
Click to expand...
Click to collapse
Yeah. **** me, for once I kept everything stock and this happened . I've always rooted and customized my phones and nothing like this has ever happened.

Database Info

welcome