Hi,
I have a legend and everything was fine but after I tried to install the legend CM6RC2 BUILD 66 Rom from cynogenmod it would not reboot any more and I only saw the android robot. After that I tried to get into recovery but that's not possible anymore.
I al ready tried modaco's guide but I didn't understand.
Does anyone know how I can unbrick my usb to be able to get into recovery to install another Rom?
Thanks in advance!
you must unbrick your USB by following this step ( nobody can do it for you... ) :
http://android.modaco.com/content/h...com/309961/usb-brick-rickrolled-b0rked-fixed/
usb drivers
I tried to understand this guide but I don't understand this part:
"Move this to /data/ , and flash the modified image using:
"/data/flash_image misc /data/mtd0.img"
You can move both mtd0.img and flash_image by putting it on your sdcard, and issueing the following command in a terminal emulator:
'cat /sdcard/flash_image > /data/flash_image'
'cat /sdcard/mtd0.img > /data/mtd0.img'
You might have to do 'chmod u+x /data/flash_image' before you run the commands (or chmod 755 /data/flash_image)"
and also i cant do step one because device is not found
you must do this after starting your device.
Before starting your device you must mount you sdcard with 'fastboot oem enableqxdm 0' under fastboot mode ( device off : hold power button + volume down )
after your device started, go to market and install Connecbot.
Start connectbot, select ( at the bottom ) Local in place of ssh , and type 'su' 2 times.
If you get permission denied, do what he's done in his PS http://android.modaco.com/index.php?s=&showtopic=309961&view=findpost&p=1335813
i can type su as many times as i want and nothing happens.
YES i typed it in local.I re-installed htc sync and still my pc cant recognize my phone.
what should i do?
you type SU on your device ? ( in connectbot )
if you see a # at the begining of the line , you are logged as root , just follow the unbrink step
ilos said:
you must do this after starting your device.
Before starting your device you must mount you sdcard with 'fastboot oem enableqxdm 0' under fastboot mode ( device off : hold power button + volume down )
after your device started, go to market and install Connecbot.
Start connectbot, select ( at the bottom ) Local in place of ssh , and type 'su' 2 times.
If you get permission denied, do what he's done in his PS http://android.modaco.com/index.php?s=&showtopic=309961&view=findpost&p=1335813
Click to expand...
Click to collapse
could you explain it for me ? how to do fastboot oem enableqxdm 0 in fastboot.....
you must have android sdk installed to use adb
When you have installed android sdk, go to tools directory, open a command prompt ( MSDOS ) , type 'adb shell' and 'fastboot oem enableqxdm 0'
after that, just reboot your device.
Look that for adb : http://forum.xda-developers.com/showthread.php?t=517874
ilos said:
you must have android sdk installed to use adb
When you have installed android sdk, go to tools directory, open a command prompt ( MSDOS ) , type 'adb shell' and 'fastboot oem enableqxdm 0'
after that, just reboot your device.
Look that for adb : http://forum.xda-developers.com/showthread.php?t=517874
Click to expand...
Click to collapse
what should i do after i reboot my device?
Win7 said he cant recognize the usb device.
is this good? dont you have the drivers or something?
zorro12010 said:
what should i do after i reboot my device?
Win7 said he cant recognize the usb device.
is this good? dont you have the drivers or something?
Click to expand...
Click to collapse
see post #6
to be simple :
only the device will see your sdcard.. not your computer... all steps for unbrick must be done on the phone except the fastboot command
i also tried typing SU and sl
and instead of # it says sh-3.2#
so you are logged as root
just to be sure type : ls not sl
you will see same thing like my screenshoot posted early
now follow unbrick command
ilos said:
you must have android sdk installed to use adb
when you have installed android sdk, go to tools directory, open a command prompt ( msdos ) , type 'adb shell' and 'fastboot oem enableqxdm 0'
after that, just reboot your device.
Look that for adb : http://forum.xda-developers.com/showthread.php?t=517874
Click to expand...
Click to collapse
thousand thanks......for you man.....i made it...........
congratulations !!!
Hi ..
I do not speak English well ،But I'm trying to understand
Please have the same problem, and tried to solve, but to no avail
at the above link in comment # 14
Thanks to Google Translate
Hello, recently I've ran into a stupid problem after unlocking bootloader on my M7. Here is what happened, after unlocking I was not able to use my phone in debugging mode, the authorization pop-up didn't show up wherever I connected my phone to PC in ADB mode. This was not Drivers fault I just lost RSA Key, I managed to get it back, I hope it will help you also.
To get RSA keys you need to do next thing.The trick is to create the .android directory elsewhere, for example on the SD Card:
You need Android Terminal Emulator and Root for this operation. ( Link to Android Terminal Emulator: https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en )
Open Android Terminal Emulator and write:
adb kill-server
HOME=/sdcard adb start-server
At this point you should have /sdcard/.android and the 2 keys in it.
Then just copy adbkey from your phone to your computer into C:/Users/YOURNAME/.android then write in terminal.
stop adbd
start adbd
Then connect you phone in ADB mode Wifi or USB and check again:
adb kill-server
adb start-server
adb devices
Now authorization prompt should pop up!
This issue is also known as Unauthorized device in ADB mode.
Good luck!
When I use adb and type in adb devices, it returns the device name so I know it's recognized but then it says" device offline". Then when I type in "adb shell" it returns "error: device offline" so can't use adb. Any help?
Hello everyone, first thanks for all the help, i'm new in here but the people is awesome:good:
My problem with my J5 Sm-j500m (root with CF-Auto-Root, android 6.0.1, firmware from sammobile ) is this: i have tried to setup my sd card as adoptable storage with two methods and i have failed.
1) Adb shell
i installed android sdk windows and run the comand window with the comands "adb devices"
and i get this:
List of devices attached
5806d690 device
So next, i do: "adb shell sm list-disks adoptable"
and i always get this: CANNOT LINK EXECUTABLE: cannot locate symbol "_ZN7android14AndroidRuntime5startEPKcRKNS_6VectorINS_7String8EEE" referenced by "app_process"...
i've tried "adb shell sm set-force-adoptable true" and other with the same luck, so no solution here.
2) i download root essencials and i tried without luck, it says "insert sd card" and the sd is already in the phone i tried with other sd and the same happened.
Does Anyone know how to do it? on a J500M? i see this http://forum.xda-developers.com/galaxy-j5/how-to/finally-adoptable-storage-j500fmm-t3470225 and this http://forum.xda-developers.com/galaxy-j5/themes/galaxy-j5-adaptable-storage-6-0-1-t3470020 both options says i have to Flash a zip with TWRP and its done but i don't know how can i do that, because i don't have TWRP. also its not specific to SM-J500M.
Thanks for the help:good::good:
tryser said:
Hello everyone, first thanks for all the help, i'm new in here but the people is awesome:good:
My problem with my J5 Sm-j500m (root with CF-Auto-Root, android 6.0.1, firmware from sammobile ) is this: i have tried to setup my sd card as adoptable storage with two methods and i have failed.
1) Adb shell
i installed android sdk windows and run the comand window with the comands "adb devices"
and i get this:
List of devices attached
5806d690 device
So next, i do: "adb shell sm list-disks adoptable"
and i always get this: CANNOT LINK EXECUTABLE: cannot locate symbol "_ZN7android14AndroidRuntime5startEPKcRKNS_6VectorINS_7String8EEE" referenced by "app_process"...
i've tried "adb shell sm set-force-adoptable true" and other with the same luck, so no solution here.
2) i download root essencials and i tried without luck, it says "insert sd card" and the sd is already in the phone i tried with other sd and the same happened.
Does Anyone know how to do it? on a J500M? i see this http://forum.xda-developers.com/galaxy-j5/how-to/finally-adoptable-storage-j500fmm-t3470225 and this http://forum.xda-developers.com/galaxy-j5/themes/galaxy-j5-adaptable-storage-6-0-1-t3470020 both options says i have to Flash a zip with TWRP and its done but i don't know how can i do that, because i don't have TWRP. also its not specific to SM-J500M.
Thanks for the help:good::good:
Click to expand...
Click to collapse
Look in the other bit of the forums. Guides - news
There are a couple of new threads on adaptable storage. Not sure if it's your device but worth a look.
Good luck
Sent from my Galaxy J5 using XDA Labs
I am trying to sideload the new 7.1.1 OTA image from Google. When I run the command adb sideload [PATH TO UPDATE]\updatefile.zip it comes back with:
loading: 'update.zip'
* cannot read 'update.zip' *
File Permissions are all OK
The platform-tools have been updated using sdk-manager
ADB devices shows the device.
The phone is encrypted (I am guessing this is the issue)
Any help would be appreciated.
hideous said:
I am trying to sideload the new 7.1.1 OTA image from Google. When I run the command adb sideload [PATH TO UPDATE]\updatefile.zip it comes back with:
loading: 'update.zip'
* cannot read 'update.zip' *
File Permissions are all OK
The platform-tools have been updated using sdk-manager
ADB devices shows the device.
The phone is encrypted (I am guessing this is the issue)
Any help would be appreciated.
Click to expand...
Click to collapse
Just checking the obvious....but updatefile.zip is in your computer that's executing the ADB command, not on you phone, correct?
edit: Also, is your ota file actually named updatefile.zip?
Phone's encryption doesn't matter here.
Yes, I am running this from my computer. I have tried the original name for the OTA (also tried downloading it multiple times)
Also the phone is completely stock with a locked bootloader.
EDIT:
I turned on Tracing and this is the full error:
c:\Users\user\Nexus6P\ROMS\OTA>adb sideload angler-ota-nmf26f-61b4a915.zip
adb I 15200 3428 adb_trace.cpp:169] Android Debug Bridge version 1.0.36
adb I 15200 3428 adb_trace.cpp:169] Revision 302830efc153-android
adb I 15200 3428 adb_trace.cpp:169]
loading: 'angler-ota-nmf26f-61b4a915.zip'adb I 15200 3428 sysdeps_win32.cpp:145] load_file: could not allocate 1331770063 bytes
* cannot read 'angler-ota-nmf26f-61b4a915.zip' *
Are you on Windows 10? Experienced this issue yesterday and I also searched a long time.
In the device manager, my device showed up as "LeMobile Android Device", because this seems to be the newest Android driver. ADB is not working correctly with the LeMobile drivers. Had to switch back via "Use previous drivers" to the Nexus 6P drivers, then it worked like a charm.
The OTA image needs to be in the platform-tools folder along with the adb executable. Then Shift/right- click in the folder and select "Open command prompt here". Next type the command "adb sideload angler-ota-nmf26f-61b4a915.zip" without the quotes, this after selecting "Apply update from ADB" from the recovery menu. You may need to unplug your phone, and then plug it back in if the command fails.