Database Develop

[ Help ] Device offline in ADB

Please,Someone help me fix this issue
Code:
C:\Users\MANH>adb devices
List of devices attached
FA364W914159 offline
THANKS ALL !
Stock 4.4.2 ,Fastboot uncheck,Usb debugging is enable.

Have you checked that USB debugging is switched on in the settings? Try restarting the adb server using "adb kill-server" and then "adb start-server".

JasSingh93 said:
Have you checked that USB debugging is switched on in the settings? Try restarting the adb server using "adb kill-server" and then "adb start-server".
Click to expand...
Click to collapse
the same issue in offline. already tried restart adb server, and reinstall HTC driver, and replug USB cable, and switch all USB port on my computer, even change my computer from windows to Mac, also remind me device offline.
BTW, already delete adb key file in the folder ".android", but there is no new key file generate. so I guess the problem is in my phone.
trying to download android sdk now, to make sure i use the latest version adb tool, I hope this can fix the problem.

I download latest sdk, and replace the adb tools I used with the version in platforms folder. then adb give me a different answer below:
C:\Users\fudaming\Downloads\unlock>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HC34YW904321 unauthorized
And a dialog box jump out, let me choose to agree the authorize the computer connect to the phone or not, I choose yes, then everything is ok.
C:\Users\fudaming\Downloads\unlock>adb devices
List of devices attached
HC34YW904321 device

adb devices offline
can anyone help me???
{
"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"
}

Philips9 said:
can anyone help me???View attachment 3120300
Click to expand...
Click to collapse
turn off usb debugging on the phone
turn it back on and grant the key that pops up

clsA said:
turn off usb debugging on the phone
turn it back on and grant the key that pops up
Click to expand...
Click to collapse
That is the problem.... I've already turned off debugging usb, turned it back on, but no pops appeared
where i'm wrong?

Philips9 said:
That is the problem.... I've already turned off debugging usb, turned it back on, but no pops appeared
where i'm wrong?
Click to expand...
Click to collapse
you reboot the phone and the PC ?

clsA said:
you reboot the phone and the PC ?
Click to expand...
Click to collapse
Yes, I solved with another rom....but
Now I see my device with "adb devices" or reboot("adb reboot"), but I can't push or flash rom with adb in recovery....
This problem is the same when I tried to make S-off with Firewater

Philips9 said:
but I can't push or flash rom with adb in recovery....
Click to expand...
Click to collapse
What do you mean exactly? ADB outputs an error when trying to push the file?
This problem is the same when I tried to make S-off with Firewater
Click to expand...
Click to collapse
FIrewater is discontinued

alray said:
What do you mean exactly? ADB outputs an error when trying to push the file?
FIrewater is discontinued
Click to expand...
Click to collapse

Bootloader Blocked!

Hi guys, i have a problem with my device. Htc Desire 500.
I apologize for my english .. I try to make the bootloader to my device , but when I have to write in cmd : fastboot flash unlocktoken Unlock_code.bin .
In my device not I get anything to finally unlock the device .
You know what I can do ?
Attached I send you pictures of my device
{
"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"
}

MrR4nma said:
Hi guys, i have a problem with my device. Htc Desire 500.
I apologize for my english .. I try to make the bootloader to my device , but when I have to write in cmd : fastboot flash unlocktoken Unlock_code.bin .
In my device not I get anything to finally unlock the device .
You know what I can do ?
Attached I send you pictures of my device
Click to expand...
Click to collapse
Type fastboot devices and see if a device name tag gets listed. If not, it means you haven't installed the usb drivers correctly.
Are you on Windows 8 or 10?
To install ADB and Fastboot drivers on Windows 8 and 10, a forum member posted the following solution:
1. Uninstall all drivers for HTC phone
2. Install latest HTC Sync Manager
3. Connect phone in normal mode
4. Connect phone in fastboot mode (system reports unrecognized device)
5. Run regedit as administrator
6. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\usbflags
7. Right-click on usbflags, click new > key, name it 0BB40FF00100
8. Select 0BB40FF00100 and in the right window right click > new > binary value
9. Rename created binary value to SkipBOSDescriptorQuery
10. Right click SkipBOSDescriptorQuery > modify binary data, type 01 00 00 00 , click ok
11. Unplug usb cable and plug again.
12. In fastboot cmd window type fastboot devices, press enter and see if your device is listed
You can also try WinDroid, it works with Desire 500
http://forum.xda-developers.com/showthread.php?t=2499926

razvangrig said:
Type fastboot devices and see if a device name tag gets listed. If not, it means you haven't installed the usb drivers correctly.
Are you on Windows 8 or 10?
A forum member posted the following solution (not tested) to install Adb and Fastboot drivers on Windows 8 or 10:
1. Uninstall all drivers for HTC phone
2. Install latest HTC Sync Manager
3. Connect phone in normal mode
4. Connect phone in fastboot mode (system reports unrecognized device)
5. Run regedit as administrator
6. Add this key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\usbflags\0BB40FF00100]
"SkipBOSDescriptorQuery"=hex:01,00,00,00
7. Unplug usb cable and plug again.
8. In fastboot cmd window type fastboot devices, press enter and see if your device is listed
You can also try WinDroid, it works with Desire 500
http://forum.xda-developers.com/showthread.php?t=2499926
Click to expand...
Click to collapse
Can i use disable driver signature enforcement in windows 8.1 to use adb for this device?Without modifying registry only allow unsigned driver.

Bootloader locked. Flashing lock flag is locked!

Hello....
I want to unlock bootloader of itel p33
(Couldn't found any custom recovery for this device)
I tried adb fastboot option...
fastboot oem unlock
fastboot flashing unlock
fastboot flash boot pathed_boot.img
fastboot flash recovery recovery.img
etc..
in adb command line it shows
...
Failed.(flashing lock flag is locked. Plz unlock it first!)
.
(I have enabled oem unlocking in dev option)
How to unlock the locked bootloader? I just want to root.
Currently using Itel p33
Android 8.1.0(go edition)
1gb ram/16gb rom
Spreadtrum sc7731e
(I just want to know is it possible if i unpack stock firmware img file and edit something and repack it. Then flash it to phone. Will it help?? I don't have much knowledge.)
Thanks....

Hey, I have the same kind of device with this issue. I am guessing the bootloader is not unlockable, I think this is true for probably any device with this processor. I got my hands on a reference sprd u-boot source code, which is not exactly labeled for this chipset but it seems to have a lot of things related to it. I'll post an update here if I get to root the device or be able to install a modified version of the firmware.
A quick note for myself : after looking for the fastboot commands in the src, there are some fkup I am seeing, the "fastboot boot" cmd seems to point the function for "fastboot continue" ???? wth
oem and flashing commands should be available if secboot is enabled but fastboot gives out unknown command but the strings are there in the compiled uboot ?????
Code:
fastboot_register("getvar:", fb_cmd_getvar);
/*when you input cmd"flash" in host, we will rcv cmd"download" first,then the "flash",
so even if we can't see cmd"download" in host fastboot cmd list,it is also used */
fastboot_register("download:", fb_cmd_download);
fastboot_publish("version", "1.0");
fastboot_register("flash:", fb_cmd_flash);
fastboot_register("erase:", fb_cmd_erase);
fastboot_register("[COLOR="SeaGreen"]boot[/COLOR]", [COLOR="Red"]fb_cmd_continue[/COLOR]);
fastboot_register("reboot", fb_cmd_reboot);
fastboot_register("powerdown", fb_cmd_powerdown);
fastboot_register("continue", [COLOR="Red"]fb_cmd_continue[/COLOR]);
fastboot_register("reboot-bootloader", fb_cmd_reboot_bootloader);
#ifdef CONFIG_SECBOOT
fastboot_register("flashing", fb_cmd_setlockflag);
fastboot_register("getflag", fb_cmd_getlockflag);
fastboot_register("oem", fb_cmd_oemcmd);
/*add fastboot cmd for sharkl2*/
fastboot_register("getlcs", fb_cmd_getlcs);
fastboot_register("setrma", fb_cmd_setrma);
fastboot_register("getsocid", fb_cmd_getsocid);
#endif

Same problem (Itel Vision 1 Plus P36 Pro LTE L6501)
{
"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"
}
Hey, I have the same kind of device with this issue. I am guessing the bootloader is not unlockable, I think this is true for probably any device with this processor. I got my hands on a reference sprd u-boot source code, which is not exactly labeled for this chipset but it seems to have a lot of things related to it. I'll post an update here if I get to root the device or be able to install a modified version of the firmware.[/B][/SIZE][/FONT]
A quick note for myself : after looking for the fastboot commands in the src, there are some fkup I am seeing, the "fastboot boot" cmd seems to point the function for "fastboot continue" ???? wth
oem and flashing commands should be available if secboot is enabled but fastboot gives out unknown command but the strings are there in the compiled uboot ?????
Code:
fastboot_register("getvar:", fb_cmd_getvar);
/*when you input cmd"flash" in host, we will rcv cmd"download" first,then the "flash",
so even if we can't see cmd"download" in host fastboot cmd list,it is also used */
fastboot_register("download:", fb_cmd_download);
fastboot_publish("version", "1.0");
fastboot_register("flash:", fb_cmd_flash);
fastboot_register("erase:", fb_cmd_erase);
fastboot_register("[COLOR="SeaGreen"]boot[/COLOR]", [COLOR="Red"]fb_cmd_continue[/COLOR]);
fastboot_register("reboot", fb_cmd_reboot);
fastboot_register("powerdown", fb_cmd_powerdown);
fastboot_register("continue", [COLOR="Red"]fb_cmd_continue[/COLOR]);
fastboot_register("reboot-bootloader", fb_cmd_reboot_bootloader);
#ifdef CONFIG_SECBOOT
fastboot_register("flashing", fb_cmd_setlockflag);
fastboot_register("getflag", fb_cmd_getlockflag);
fastboot_register("oem", fb_cmd_oemcmd);
/*add fastboot cmd for sharkl2*/
fastboot_register("getlcs", fb_cmd_getlcs);
fastboot_register("setrma", fb_cmd_setrma);
fastboot_register("getsocid", fb_cmd_getsocid);
#endif
[/QUOTE]
My device is Itel Vision 1 Plus (P36 Pro LTE) L6501.
And I'm facing same kind of problem. Can't do literally anything in fastboot.
Is there any way to contact the makers/developers for a response?
I'm already regretting my decision to buy an itel phone.

shamimurrahman19 said:
Hey, I have the same kind of device with this issue. I am guessing the bootloader is not unlockable, I think this is true for probably any device with this processor. I got my hands on a reference sprd u-boot source code, which is not exactly labeled for this chipset but it seems to have a lot of things related to it. I'll post an update here if I get to root the device or be able to install a modified version of the firmware.[/B][/SIZE][/FONT]
Click to expand...
Click to collapse
I am getting those same errors typing in the same commands. I guess it's a phone that just can be rooted? Or just not by this method?
P.S. Currently trying this on a BLU G5.

fastboot_register("getvar:", fb_cmd_getvar);
/*when you input cmd"flash" in host, we will rcv cmd"download" first,then the "flash",
so even if we can't see cmd"download" in host fastboot cmd list,it is also used */
fastboot_register("download:", fb_cmd_download);
fastboot_publish("version", "1.0");
fastboot_register("flash:", fb_cmd_flash);
fastboot_register("erase:", fb_cmd_erase);
fastboot_register("boot", fb_cmd_continue);
fastboot_register("reboot", fb_cmd_reboot);
fastboot_register("powerdown", fb_cmd_powerdown);
fastboot_register("continue", fb_cmd_continue);
fastboot_register("reboot-bootloader", fb_cmd_reboot_bootloader);
#ifdef CONFIG_SECBOOT
fastboot_register("flashing", fb_cmd_setlockflag);
fastboot_register("getflag", fb_cmd_getlockflag);
fastboot_register("oem", fb_cmd_oemcmd);
/*add fastboot cmd for sharkl2*/
fastboot_register("getlcs", fb_cmd_getlcs);
fastboot_register("setrma", fb_cmd_setrma);
fastboot_register("getsocid", fb_cmd_getsocid);
#endif

you may need rooted phone to flash via adb nd get #su permission

hello this is of interest to me. I have the decompiled binaries, editable on my linux device, for this img. i can edit the part you need. Please show me exactly how you would fix this

flaccidattempts said:
hello this is of interest to me. I have the decompiled binaries, editable on my linux device, for this img. i can edit the part you need. Please show me exactly how you would fix this
Click to expand...
Click to collapse
can you decompile the kernel and get full source code?

well i believe im pretty close
take a look. I lost the original file

How to unlock bootloader on Spreadtrum Phone - unofficial twrp
unlock bootloader on Spreadtrum Phone easy method by using the signature.bin, you can unlock any spreadtrum or UniSoc Phone
unofficialtwrp.com
this will erase all of your data. what is your phone model? and please show me how to decompile kernel binaries. I really need this.

There is no certified way to reverse source code from binary. The process in which it has been compiled has to be reversed.
Now if you want to analyze binary and cross-examine it with android from source files, then you can derive using basic lamba functions to infer missing pieces.
But..... binaries can be engineered in a way that the code becomes obvious ESPECIALLY if you have Android from Source.
Essentially, you can download android from source using google repo tool, repo the release edition, compare side by side, file for file, what is different.
I Use these linux command s
$ strings <binary file> >> myText.txt
Click to expand...
Click to collapse
$ hexdump <binary file>
Click to expand...
Click to collapse
From there i use a custom python file that 'line for line' searches for the strings, if they match, it logs the match.
once done with that, it sends it over to sublime text, which for some reason, on rare occasions resolves the binaries immediately, especially when paired with the matching strings file.
For files that are obviously encrypted, i wait till the end and brute force popular hashes, map out links, use lambda functions and use general deduction to solve to source.
If you want to learn how to analyze binaries with linux watch "malware analysis" videos on youtube

TWRP recovery for this device, tested and working. Plus magisk patched boot image for instant root and custom vbmeta for verifying the boot and recovery image, for now there seems to be no way of disabling verity check permanently on this device.

Question HELP needed for unlocking the Mi ultra

HI
I tried to unlock my MI ultra ... but the unlock tool doesnt see my phone
I did .. developper option ... the OEM unlocking , USB debugging and the Mi unlock add account
I signed into same account on the latest unlock tool
fastboot mode
but nothing appear on the unlock tool screen
what did I miss ?

You have to install the Fastboot drivers on your Windows.

Afg Playa said:
You have to install the Fastboot drivers on your Windows.
Click to expand...
Click to collapse
I DID
But same issue .. I will try to use different PC

Anesthetist said:
HI
I tried to unlock my MI ultra ... but the unlock tool doesnt see my phone
I did .. developper option ... the OEM unlocking , USB debugging and the Mi unlock add account
I signed into same account on the latest unlock tool
fastboot mode
but nothing appear on the unlock tool screen
what did I miss ?
Click to expand...
Click to collapse
On Windows 10 with your phone plugged in just go to windows update and you'll find a driver install request

Anesthetist said:
HI
I tried to unlock my MI ultra ... but the unlock tool doesnt see my phone
I did .. developper option ... the OEM unlocking , USB debugging and the Mi unlock add account
I signed into same account on the latest unlock tool
fastboot mode
but nothing appear on the unlock tool screen
what did I miss ?
Click to expand...
Click to collapse
Did you do the unlocking in fastboot mode? Try another usb cable, some people are having issues with some.

Run the unlock tool as an administrator - the only thing which solved it for me under Windows 10.

Send me a private message with teamviewer details. I can help

Make sure the following is done prior to booting into fastboot:
Make sure that developer options is enable.
Make sure Unlock OEM is enabled
Make sure you have linked your MI account to your phone
Make sure USB debugging is enabled
Step 1: Place the phone in fastboot and plug it into your PC.
Step 2: Navigate to your windows search bar, enter "device manager" and open the top result. It should now show you several different drivers. You should see one named Android under "Other Devices."
{
"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"
}
If you see a little triangle, then you just need to download the driver for it.
I downloaded these driver
Step 3: Uncompress the files and open the folder up. You should see a file called Mi USB Driver. Run that file.
Step 4: A window will pop up asking you to unplug your Phone. Unplug it from the USB and replug it back in. It should then change the message to "Installing Drivers"
Step 5: Open the MI Unlock Tool and refresh. You should now have the ability to unlock the phone.
Let me know if that helped, or if you need additional assistance.

panda24z said:
Make sure the following is done prior to booting into fastboot:
Make sure that developer options is enable.
Make sure Unlock OEM is enabled
Make sure you have linked your MI account to your phone
Make sure USB debugging is enabled
Step 1: Place the phone in fastboot and plug it into your PC.
Step 2: Navigate to your windows search bar, enter "device manager" and open the top result. It should now show you several different drivers. You should see one named Android under "Other Devices."
View attachment 5329617
If you see a little triangle, then you just need to download the driver for it.
I downloaded these driver
Step 3: Uncompress the files and open the folder up. You should see a file called Mi USB Driver. Run that file.
View attachment 5329623
Step 4: A window will pop up asking you to unplug your Phone. Unplug it from the USB and replug it back in. It should then change the message to "Installing Drivers"
View attachment 5329625
View attachment 5329627
Step 5: Open the MI Unlock Tool and refresh. You should now have the ability to unlock the phone.
View attachment 5329629
Let me know if that helped, or if you need additional assistance.
Click to expand...
Click to collapse
Thank you so much
I have been very busy lately with covid 19 pts and Urgent operations ... I will follow your instructions as soon as I can
Thank you so so much

Anesthetist said:
Thank you so much
I have been very busy lately with covid 19 pts and Urgent operations ... I will follow your instructions as soon as I can
Thank you so so much
Click to expand...
Click to collapse
Please let me know if it worked for you.
I'll have to do the same procedure soon.

Question [FIXED] fastboot.exe/Mi Unlock Tool won't recognize my device

Hello!
I wanted to unlock my bootloader on my Redmi Note 11, but I have ran into a problem. It won't detect it in fastboot.exe or the Mi Unlock tool. I already:
Installed the Google USB driver
Updated the Mi Unlock tool, My phone, Windows
Enabled USB debugging & OEM unlocking
Booted the device in fastboot mode (Orange text saying FASTBOOT)
Can anyone help? Thanks.
{
"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"
}

Is the cable good and is there a normal connection for data exchange with the phone?
Are you using the USB port from the motherboard?
Does the adb devices command work and can you see the device?

ze7zez said:
Is the cable good and is there a normal connection for data exchange with the phone?
Are you using the USB port from the motherboard?
Does the adb devices command work and can you see the device?
Click to expand...
Click to collapse
Thanks for your reply
The cable is in perfect condition, it was shipped with my phone and it works.
No I am using the one on the case, I am not sure on how it will affect this in any way but I am gonna try it.
Nope, ADB doesn't report anything

yo!
this happened to me also, i did fixed it by installing the fastboot driver
1. download the attachment below.
2. then extract it, a folder called 'Fastboot driver' should appear.
3. now, press Win+R, and a Run window should appear.
4. copy paste this 'devmgmt.msc' (without the quotation) into it, press OK.
5. Device Manager should appear. On top left, go to Action -> Add Drivers.
6. Browse to the 'Fastboot driver' folder, select it, click OK and then click Next.
7. after 'Drivers successfully installed', click Close.
now if things goes right, fastboot should be detected by now.
if not, idk tbh

Thunderoar said:
yo!
this happened to me also, i did fixed it by installing the fastboot driver
1. download the attachment below.
2. then extract it, a folder called 'Fastboot driver' should appear.
3. now, press Win+R, and a Run window should appear.
4. copy paste this 'devmgmt.msc' (without the quotation) into it, press OK.
5. Device Manager should appear. On top left, go to Action -> Add Drivers.
6. Browse to the 'Fastboot driver' folder, select it, click OK and then click Next.
7. after 'Drivers successfully installed', click Close.
now if things goes right, fastboot should be detected by now.
if not, idk tbh
Click to expand...
Click to collapse
Thank you, I forgot to mention I already fixed this.

_matteodev said:
Thank you, I forgot to mention I already fixed this.
Click to expand...
Click to collapse
can you mention how you fixed it? i'm having the same problem