So I tried to flash CyanogenMod 12 to my phone, however, because this was my first time doing this sort of thing, I missed turning off the security on my phone before I wiped the phone. Obviously, at this point it was bricked, and after searching around, I discovered ADB Sideload. So I went through the process to get ADB, downloaded Android SDK and installed the platform tools, and I thought I was going to be able to save my phone. However, when I ran the TWRP ADB sideload, this happens when trying to input my file View attachment 3306335
I tried to check the drivers and found the HTC One X+ drivers, however when I try to install the drivers, this happens
{
"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"
}
When it does sometimes work, it gets to around 40% then just stops, or does "Total transfer 0.01" or something like that
There's also the problem that I couldn't actually flash a recovery without using the tool built for it by somebody on here, and that wouldn't let me get ClockworkMod Recovery for some reason
Please help me here, I'm incredibly stuck and even trying a RUU doesn't do anything
By the way it seems to connect just fine outside of ADB Sideload, it even gets detected by ADB when the server actually works and doesn't fail to start "ACK"
(EDIT) I do hear the phone disconnect and reconnect when I enter Sideload
TezzaBP said:
So I tried to flash CyanogenMod 12 to my phone, however, because this was my first time doing this sort of thing, I missed turning off the security on my phone before I wiped the phone. Obviously, at this point it was bricked, and after searching around, I discovered ADB Sideload. So I went through the process to get ADB, downloaded Android SDK and installed the platform tools, and I thought I was going to be able to save my phone. However, when I ran the TWRP ADB sideload, this happens when trying to input my file View attachment 3306335
I tried to check the drivers and found the HTC One X+ drivers, however when I try to install the drivers, this happens View attachment 3306350
When it does sometimes work, it gets to around 40% then just stops, or does "Total transfer 0.01" or something like that
There's also the problem that I couldn't actually flash a recovery without using the tool built for it by somebody on here, and that wouldn't let me get ClockworkMod Recovery for some reason
Please help me here, I'm incredibly stuck and even trying a RUU doesn't do anything
By the way it seems to connect just fine outside of ADB Sideload, it even gets detected by ADB when the server actually works and doesn't fail to start "ACK"
(EDIT) I do hear the phone disconnect and reconnect when I enter Sideload
Click to expand...
Click to collapse
Uninstall HTC sync and leave drivers. If that is indeed installed.
Lloir said:
Uninstall HTC sync and leave drivers. If that is indeed installed.
Click to expand...
Click to collapse
I'll try that
Unfortunately that didn't do anything
Related
Well... I have a OG Droid 2.2.3. Whenever I connect it to my windows 7, it shows up as "device has malfunctioned, device.. unknown" everytime. I have tried reinstalling drivers, etc but the Computer never recognizes it as a Motorola device.
Also, my phone doesn't charge when the phone is on and connected to the pc, but when the phone is connected to the PC and I turn the phone off, it charges (but then it wont turn on unless I disconnect it).
Also, whenever it is connected, it never shows the USB icon/ or anything in the notification bar. So, I havent been able to root it yet. I have tried on 3 other computers (XP, 7, 7) and 3 other USB cables. Same results.
I want to root my Droid 2.2.3, I have tried z4root app, but it doesn't support 2.2+
How can I root my Droid without a PC, can I use terminal, etc and do it on the phone itself?
edit: just re-read what you typed sorry mate cant help
Tapped from a modded GS2
Tried it. This is all I get in device manager: I don't get any usb mass storage devices, or anything. I get 1 Unknown device, which if I try to manually update with Motorola drivers, Windows tells me they are incompatible and it doesnt install
{
"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"
}
your best bet is superoneclick 2.3.3. (just look it up or go to shortfuse.org) i got it to work beautifully on my moms phone. plus it works on 2.3.3 (no duh! lol). terminal emulator may work.... but what is the model under your "about phone." im not familiar with the "og droid" and im getting conflicting results searching for it... is it the droid one by motorola?
and uninstall the "unknown device" drivers, reboot your machine, and run the driver installers as administrator
update: what sucks is, if you were already rooted, adbwireless and ftpdroid could solve all of your problems, assuming you have wifi at home.............
i have an idea, post a link to the motorola drivers you have, and ill see if they install over here. if so, its a computer problem for sure. if not, then you probably need to get them somewhere else. (dont know why the source would have sucky drivers when other places wouldnt, but there's no harm in trying.
Tried your suggestion. Nothing. Still getting device is unrecog/has malfunctioned.
Its the Motorola Droid 1 on 2.2.3
Come on. There HAS to be a way to root it or install a custom rom without a computer! Ahh
Sorry. The only two ways I know how to root 2.3.3 and up use comp. Best Bet is fixing your connection with computer right now. Sorry. Try asking customer service? Maybe get the phone replaced. Then you have Shiney NEW phone to root!
ROOTED Xperia Play 4G 2.3.3
Anyone else have any other suggestions?
So I flashed a unofficial lollipop rom for my m8, but then I found it slow and buggy, so I went back to TWRP and restore it back to my GPE 4.4.4. However, when I boot it back, it turns out like this, I think it is bricked. When I plug it into the computer, the computer detects the phone, but it adb does not, probably because I did not turn on debugging in the lollipop rom.
{
"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"
}
Then I try to go back to bootloader. When I enter bootloader, it automatically jumps to HBOOT, checking something, and pops up this page. If I hit "yes", then it fix it and reboot, but when I come back to bootloader, it still jumps to this page. If I hit no, same thing. When I plug it into the computer, the computer doesn't detect the phone at all.
So I am stuck, any solution please?
thousight said:
So I flashed a unofficial lollipop rom for my m8, but then I found it slow and buggy, so I went back to TWRP and restore it back to my GPE 4.4.4. However, when I boot it back, it turns out like this, I think it is bricked. When I plug it into the computer, the computer detects the phone, but it adb does not, probably because I did not turn on debugging in the lollipop rom.
Then I try to go back to bootloader. When I enter bootloader, it automatically jumps to HBOOT, checking something, and pops up this page. If I hit "yes", then it fix it and reboot, but when I come back to bootloader, it still jumps to this page. If I hit no, same thing. When I plug it into the computer, the computer doesn't detect the phone at all.
So I am stuck, any solution please?
Click to expand...
Click to collapse
When you are on the second screen, does your computer pick it up?
No unfortuanately
Take the external sdcard out and put it in another device,you need to move/remove the "0P6BIMG.zip" file .once file is removed put the sdcard back in your phone or you can boot hboot without it even and the rest of the options should be there like normal
thousight said:
I think it is bricked.
Click to expand...
Click to collapse
If the screen comes on its not bricked.
thousight said:
When I plug it into the computer, the computer detects the phone, but it adb does not, probably because I did not turn on debugging in the lollipop rom.
Click to expand...
Click to collapse
You need to be in recovery for adb to work. USB Debugging only makes a difference if you are trying to connect adb when the OS is booted (which is obviously not the case for you).
As mentioned above, you just need to stop it from trying to update. After that, you probably just need to get a known good ROM on the phone or SD and flash in TWRP. Or at worst, you may need to re-install TWRP and/or update to a newer TWRP version if its outdated.
I had the same problem yesterday and removed the 0P6BIMG.zip file like jball said rebooted 2 or 3 times more and reloaded TWRP and venom one. Now I'm replying with that phone.
Hello there,
my issue is that when i go in bootloader mode, i have a blackscreen, then my phone switch off. The system ui (custom rom Crdroid) and the recovery (orange fox) are working well.
I recognize also that when i reboot, i don't have anymore the MI logo where you have the status of your bootloader when it's unlocked.
More of it, when i plug it on windows , i cannot access to its usb storage (i tried also in mounting it through twrp, but same issue), nothing appears. For example, with an "adb devices" cmd command, no device can be found.
When i check the Windows devices manager, i can see an "unknown usb device" (i tried to force to reinstall drivers on it like the latest google usb driver, but windows refuse it, saying that it has the best and latest one for it).
{
"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"
}
Debugging mode is well enabled
Drivers have been reinstalled (the latest miflashtool install all what is needed)
Nothing appears on my smartphone when i plug it to windows (before i had a notification ot choose in charge mode, usb mode, etc...)
Plug to different usb port has been done without succeess
The phone doesn't appear in miflashtool obv
Restoring a previous backup didn't change the issue (i'm using the custom rom crdroid).
I guess all the things are linked but how i can fix it if i don't have access anymore to my bootloader mode to be able to flash some *.img via fastboot or if i cannot transfer files to my phone to operate in recovery, and more WHAT to do?
I hope you guys, will be able to help. The issue can be really annoying, and stuck me in "no rom update and no transfers of anything possible" situation.
Thank you beforehand
@bonbonboy
Try flashing the firmware through recovery from here https://androidfilehost.com/?fid=11410963190603850663 then reboot device and send it to bootloader via command adb reboot bootloader
It works like a charm!
Mi logo back, adb commands run, usb transfers work and no more error in the device manager.
You saved my day :good::good::good: Thanks a lot !
Hello,
I am new to this forum but maybe I have an interesting thing.
I found a Samsung A3 (SM-310F 16GB) wich was going to trash. It seems it acts as a medical device for monitoring heart diseases. It has a custom launcher loaded on wich you can only load the monitoring program. It has the Android top bar with time bluetooth-status battery and so on, but you can´t swipe down to access preferences or else. You also can´t take screenshot due to security guidelines and you can´t connect to it with a PC.
So my question, is it possible to do a root on this device. Or to flash it with a stock firmware to use it as anormal phone?
I´m wondering if anyone has an idea about this.
Thanks
Dirk
The door to any Android device is ADB ( read: Android Debug Bridge ). If device isn't accessable by means of ADB then you can NOTHING do with it, IMHO.
jwoegerbauer said:
The door to any Android device is ADB ( read: Android Debug Bridge ). If device isn't accessable by means of ADB then you can NOTHING do with it, IMHO.
Click to expand...
Click to collapse
Ok, so how do I know if it is accessable with ADB?
And just for understanding, how do you customize a normal android device (smartphone), that it won´t act like a phone anymore? Just custom firmware, or custom chips?
igel81 said:
Ok, so how do I know if it is accessable with ADB?
Click to expand...
Click to collapse
You on Windows computer
install the Android USB driver suitable to this phone
install ADB
Then you connect Windows computer and phone via USB-cable, power on phone, and run this ADB command
Code:
adb devices
Look also inside here.
jwoegerbauer said:
You on Windows computer
install the Android USB driver suitable to this phone
install ADB
Then you connect Windows computer and phone via USB-cable, power on phone, and run this ADB command
Code:
adb devices
Look also inside here.
Click to expand...
Click to collapse
Thanks. I tried this, but unfortunately it shows no device. By holding up and home at start, it boots into a firmware update mode. From here I can connect with adb in sideload mode. Don´t know if this is helpfull...
@igel81
If you can boot phone into ADB Sideload mode
{
"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"
}
then you can flash a ROM as a whole.
jwoegerbauer said:
@igel81
If you can boot phone into ADB Sideload mode
then you can flash a ROM as a whole.
Click to expand...
Click to collapse
Too bad, it doesn´t work. It says "footer is wrong" and "signature verification failed". It seems you can only install roms signed by that medical company.
Hey I'm new to this forum and Android Tablets in general. I have received a Vodafone Smart Tab 4G, which doesn't boot up. It's an old Tablet and it hasn't been used in a couple years. I want to see if I can make it boot up and test whether it's still usable for minor tasks. I thought I'd try to install an update using an SD card, but it's surprisingly impossible to find anything from an official source. The service menu does say "KTU84P release-keys" which seems to suggest that it has Android 4.4.4 installed.
What I've tried so far:
1: Go into the service menu and do a factory reset.
2. Try to find an update file to install through SD card method (to no avail)
3. Put some alleged stock roms onto an SD card and try to use the update function (fails on the verification step)
4. Installed ADB & Unsigned Mediatek Vcom Drivers on Windows 10. ADB has no connection to the Tablet.
5. Downloaded and tried SmartTab4G_Recovery_KK_benjaminwan to no avail. It gets stuck at "waiting for device".
6. Downloaded SP Flash tool, but failed to find a ROM for the Smart Tab 4G with a scatter file.
7. Out of desperation I tried to flash it with a Smart Tab 3G Rom which had a scatter file, but when I press download nothing happens.
My current understanding is that the standard service menu isn't meant to be used to flash the firmware. If I had an official update file I might have had some success, but I couldn't find one. All the other attempts involving a connection to my Windows 10 PC failed, which seems to indicate that I might be using bad drivers. I'm honestly at my wits' end and I don't understand why this is any more complicated than going to the manufacturers website, finding my device, downloading the most recent system software and flashing it through the service menu. Hope someone can help me out with this one.
Update: Tried a different computer. Partial success. Device manager actually recognized an Android device this time. I installed the usb driver and the recovery batch actually didn't get stuck on "waiting for device" this time. That's great news, although I didn't get much further. Here's what I got:
{
"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"
}
Thread can be closed. I got it after all with the help of the available information. Turns out the recovery.bat was a dead end. Not sure why it didn't work for me with the batch. I tried the approach explained here with cmd and it worked fine.
fastboot -i 0x1bbb oem unlock
fastboot -i 0x1bbb boot cwm.img
Once I was in the cwm everything went smoothly since verification was disabled and I could install a custom rom. This probably took me way longer than it should've, but at least it's working now.