Hi, I tried root on my phone, I was on android nougat and I installed twrp, then perform a data factory reset and restart does not go from the boot screen and shows the legend "bad key", custom recovery works but not I get nothing, please help me!
Check this out
rolas96 said:
Hi, I tried root on my phone, I was on android nougat and I installed twrp, then perform a data factory reset and restart does not go from the boot screen and shows the legend "bad key", custom recovery works but not I get nothing, please help me!
Click to expand...
Click to collapse
I had the same problem and this post helped me.
samvictorino said:
I had the same problem and this post helped me.
Click to expand...
Click to collapse
Cmd does not recognize fastboot mode, usb debugging is disabled and I can not find a way to activate it, adb sideload from twrp works but will work from there?
rolas96 said:
Cmd does not recognize fastboot mode, usb debugging is disabled and I can not find a way to activate it, adb sideload from twrp works but will work from there?
Click to expand...
Click to collapse
Sorry, actually when I did it I accidentally wiped the system partition and this post helped me, not the previous one.
I didn't need to enable unknown sources or usb debug because there was no system to begin with. I hope it helps you.
rolas96 said:
Cmd does not recognize fastboot mode, usb debugging is disabled and I can not find a way to activate it, adb sideload from twrp works but will work from there?
Click to expand...
Click to collapse
Fastboot doesn't need USB debugging to be enabled. You have some other issue.
Sent from my XT1650 using Tapatalk
In twrp just ignore encrypt pass and not modify system allowed (slider)
Related
My phone is from chinavasion it is galaxy i8550 WIN clone with lower specs it is mocor droid 2.0.5 with a fake jellybean speadtrum sc6820 it is rooted i connected the phone via adb and reboot into recovery i have stock recovery not cwm and i tried fixing it btw i meessed up my build.prop file but anyways i tried to fix it via adb and i got a permission error and i have a backup of my build.prop tho ...i just gave up and rebooted to recovery and wiped data/factory reset and ofcourse it didnt work but i lost my adb drivers i cant turn on usb debugging so i cant use adb and i dont know how to accesss recovery i keep ending up in the speadtrum factory test where u test phone hardware nothing else please help if u can altho i highly doubt it and also when i used adb to reboot in recovery and used a zip file it would say signature verification failed :crying::fingers-crossed: But i trust in xda please help even to give me the phone combination keys to recovery and that give me a zip that will be accepted PLEASE i only had the phone for a month
What exactly were you trying to fix in your stock recovery? Assuming I understand you correctly?
Sent from my K2_CL using Tapatalk
Fixing
Modding.MyMind said:
What exactly were you trying to fix in your stock recovery? Assuming I understand you correctly?
Sent from my K2_CL using Tapatalk[/QUOT
I just fugured out something the problem occured when i took a backup of my build.prop (original one) from my sd card and replaced it with the one in my system folder and forgot to add permissions to it and i restarted my phone and now its bootlooped. When it happened i tried to fix it before i factory reset my phone and lost access to recovery cuz i use to access it from adb i tried to flash a new one (build file) but i got signature verification failed so i just factory reset and lost my adb drivers so now i cant connect it to my computer to use adb commands to reboot into recovery and idk my combination for recovery it is speadtrum sc6820 .....ps. my phone is rooted and has mocor droid 2.3.5 with 4.2.2 jellybean so u know its a fake jellybean cuz its a cloned phone and i have no cwm :crying:
Click to expand...
Click to collapse
@BenDroid1
You can write the custom recovery to your recovery partition using dd in an android terminal emulator from the play store. You would need to know which partition holds your recovery.
For MY device (your partition is different) it would be as followed in the terminal emulator:
Code:
su
Code:
dd if=/sdcard/customrecovery.img of=/dev/block/mmcblk0p21
/dev/block/mmcblk0p20 is the partition that holds my recovery on my device - yours will be different!
You can also use this method for the boot.img towards the boot partition as well as data to data partition, and so forth.
If you have CWM and you were smart enough to create a backup of your device, then I would write the custom recovery to your recovery partition, boot in to CWM, and restore your device with your backup. Then, reboot, plug device in to your computer, allow the computer to reinstall the drivers and hopefully at this point you should be able to establish connection with adb/fastboot again.
Sent from my K2_CL using Tapatalk
Example 1
Sent from my K2_CL using Tapatalk
Example 2
Sent from my K2_CL using Tapatalk
Cant do that
How do uexpect me to do all of that when everytime i boot my phone the its stuck on the logo and i Dont have cwm ...my phone is bootlooped
BenDroid1 said:
Modding.MyMind said:
What exactly were you trying to fix in your stock recovery? Assuming I understand you correctly?
Sent from my K2_CL using Tapatalk
Click to expand...
Click to collapse
When it happened i tried to fix it before i factory reset my phone and lost access to recovery cuz i use to access it from adb i tried to flash a new one (build file) but i got signature verification failed so i just factory reset and lost my adb drivers so now i cant connect it to my computer to use adb commands to reboot into recovery and idk my combination for recovery it is speadtrum sc6820 .....
Click to expand...
Click to collapse
Because right here according to your quote you mentioned that you resetted your device, lost connection to your adb. Only time you can use ADB is when your phone is running. Only way you can confirm if you lost connection with ADB is if your phone is up and running, you open up command window on pc, then run 'adb devices' and if nothing returns then you have no connection. Otherwise, there is no way to confirm if you lost connection to it. So by your quote above, you made it sound like you got around your bootloop problem but could not connect with using ADB and no longer had CWM on your device.
Try to be more clear next time lol.
Have you tried using fastboot instead of ADB?
Sent from my K2_CL using Tapatalk
Modding.MyMind said:
Because right here according to your quote you mentioned that you resetted your device, lost connection to your adb. Only time you can use ADB is when your phone is running. Only way you can confirm if you lost connection with ADB is if your phone is up and running, you open up command window on pc, then run 'adb devices' and if nothing returns then you have no connection. Otherwise, there is no way to confirm if you lost connection to it. So by your quote above, you made it sound like you got around your bootloop problem but could not connect with using ADB and no longer had CWM on your device.
Try to be more clear next time lol.
Have you tried using fastboot instead of ADB?
Sent from my K2_CL using Tapatalk
Click to expand...
Click to collapse
no i havent and sorrry i ...i will be clearer when i press power plus volme up i get speadtrum factory test where u test phone hardware but no android recovery
Your phone has a bootloader. You need to access your bootloader, select fastboot, plug your device in your pc, open up command window, then type 'fastboot devices'.
If you get your device serial number returned back to you then you have connection. If it returns blank, then you do not have connection which at this point I will not be able to help you.
Sent from my K2_CL using Tapatalk
Modding.MyMind said:
Your phone has a bootloader. You need to access your bootloader, select fastboot, plug your device in your pc, open up command window, then type 'fastboot devices'.
If you get your device serial number returned back to you then you have connection. If it returns blank, then you do not have connection which at this point I will not be able to help you.
Sent from my K2_CL using Tapatalk
Click to expand...
Click to collapse
unfortunately looks like u cant help me cuz neither that wont showup
BenDroid1 said:
unfortunately looks like u cant help me cuz neither that wont showup
Click to expand...
Click to collapse
I'm sorry bro. Maybe someone else on here will pickup where I left off. Good luck friend.
Sent from my K2_CL using Tapatalk
Hi,
I upgraded a patch of custom rom and phone restarted and stopped at boot image.
Now, I want to reboot it into recovery and replace other custom rom but due to unusable volume key I'm not able to reboot it to recovery mode.
Tried this by using adb but its not recognizing the phone (might be USB debugging is in disable mode). Pls Help me on this.
Thanks,
Dharmender
dharmuls said:
Hi,
I upgraded a patch of custom rom and phone restarted and stopped at boot image.
Now, I want to reboot it into recovery and replace other custom rom but due to unusable volume key I'm not able to reboot it to recovery mode.
Tried this by using adb but its not recognizing the phone (might be USB debugging is in disable mode). Pls Help me on this.
Thanks,
Dharmender
Click to expand...
Click to collapse
Try this method to install recovery.... http://forum.xda-developers.com/showthread.php?t=2167621
Tried this but getting error msg at sp flash tool and not moving further, might be due to usb debugging not enabled
got the below error msg
zeu55 said:
Try this method to install recovery.... http://forum.xda-developers.com/showthread.php?t=2167621
Click to expand...
Click to collapse
Pls help me, my phone is unusable state now :crying:
dharmuls said:
Pls help me, my phone is unusable state now :crying:
Click to expand...
Click to collapse
Installing recovery does not require adb. Check you have correct drivers installed.
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
osikiri said:
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
Click to expand...
Click to collapse
My watch is now bricked because I have no way to get out of "adb sideload" mode...how did you get out of that mode? please tell me.
TjPhysicist said:
My watch is now bricked because I have no way to get out of "adb sideload" mode...how did you get out of that mode? please tell me.
Click to expand...
Click to collapse
I pushed the reset button on the back(the silver one right above the charging connectors) with a pen for about 10 seconds, and it rebooted.
osikiri said:
I pushed the reset button on the back(the silver one right above the charging connectors) with a pen for about 10 seconds, and it rebooted.
Click to expand...
Click to collapse
Wow ok, that's a LOT longer than I'm used to with other devices...THANK GOD I thought I had bricked it completely.
Anyway, now i have to figure out a way to get adb to work in sideload,...i mean CLEARLY it's possible lots of others doing it..
---------- Post added at 08:26 AM ---------- Previous post was at 07:41 AM ----------
TjPhysicist said:
Wow ok, that's a LOT longer than I'm used to with other devices...THANK GOD I thought I had bricked it completely.
Anyway, now i have to figure out a way to get adb to work in sideload,...i mean CLEARLY it's possible lots of others doing it..
Click to expand...
Click to collapse
Ok, does anyone know how to get my computer to recognise my watch in recovery mode? It's not about 'driver' the computer plain doesn't recognise that anything is plugged in at all.
I know the post is quite old already, but I experience exactly the same phenomenon...
I tried multiple PCs Linux and Windows,but non of them recognized the watch (neither on 4.4W1 nor on 4.2W2).
Anyone any idea?
Wikiwix said:
I know the post is quite old already, but I experience exactly the same phenomenon...
I tried multiple PCs Linux and Windows,but non of them recognized the watch (neither on 4.4W1 nor on 4.2W2).
Anyone any idea?
Click to expand...
Click to collapse
I believe u need to update the drivers.....I always go-to device manager...update driver..hit select from list..and choose android adb....
Sent from my LGLS990 using XDA Free mobile app
mrkrabs said:
I believe u need to update the drivers.....I always go-to device manager...update driver..hit select from list..and choose android adb....
Sent from my LGLS990 using XDA Free mobile app
Click to expand...
Click to collapse
The problem, as @osikiri stated, is that the device does not get recognized at all (no unknown devices in devicemanager and the sound that comes on plugging in a device does not come as well). Furthermore, afaik Linux does not even need any drivers
Had the same issue today... and the only way out way battery death and recharge
JaceAlvejetti said:
Had the same issue today... and the only way out way battery death and recharge
Click to expand...
Click to collapse
If this really helps (seems weird): I guess the exact setting could be necassary:
You simply ran out of battery while the watch was running(not recovery or fastboot) and then plugged it in and went directly (or not?) to the recovery?
Thanks in advance, would be really great to fix this!
Anyone ever find a fix to this? I'm trying to manually install the 5.0 update and I'm having the same issue. Every post I find with search tells me to update drivers but I'm on a Mac that doesn't even use ADB drivers. I've updated the SDK.
MSigler said:
Anyone ever find a fix to this? I'm trying to manually install the 5.0 update and I'm having the same issue. Every post I find with search tells me to update drivers but I'm on a Mac that doesn't even use ADB drivers. I've updated the SDK.
Click to expand...
Click to collapse
I'm doing the same thing and having the same issues!
Yeah, same issue for me as described.
Windows (Win7 x64 for me) doesn't even realise that the device is connected when it is in recovery mode. Although it will connected properly when booted normally.
+1 Any ideas?
Same issue for me. I've tried removing and replacing it on the cradle, killing and restarting the adb server, entering recovery by the touchscreen or by the adb/fastboot commands, clearing debugging keys, etc... Anybody have any other ideas?
---------- Post added at 07:25 PM ---------- Previous post was at 06:46 PM ----------
Ok, so it appears that the recovery img on 4.4w2 broke adb support or something. There are a few threads that suggest you can root and flash it or just wait for the OTA. We'll see whether I get the OTA before I have time to try this out.
Lollipop OTA Update: Download and How-To (Root Required)
I made a script that roots and updates your watch to 5.0.1 in a click.
[UTILITY][RESTORE][UNLOCK][ROOT] LG G Watch Tool
My way of doing it
osikiri said:
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
Click to expand...
Click to collapse
I've similar problem, and I've spent almost 3 hours to find the solution. I found that following solution work for me:
http://forum.xda-developers.com/g-watch-r/development/manual-ota-update-root-t2969845
I've changed the step slightly according to the comments inside the thread:
- Enter Bootloader (swipe top left-bottom right as soon as the LG logo pops up on boot)
- Unlock bootloader (fastboot oem unlock) and boot the watch normally once
- Turn off and re-enter bootloader
- Flash 5.0.1 Stock Recovery (fastboot boot recovery.img)
// Do Not Flash 5.0.2 stock recovery
- Enter recovery and ADB sideload the update (tap the android, select install update from ADB and enter adb sideload filename.zip)
//you might have to reinstall the ADB drivers, just follow the simple step to install ADB driver
Done.
fi thought it was finally the solution, but fastboot oem unlock bricked my sony smartwatch3. I see tomorrow if with my windows pc i can fix with sony companion, otherwise i'll have to use the warranty
willisc said:
I've similar problem, and I've spent almost 3 hours to find the solution. I found that following solution work for me:
http://forum.xda-developers.com/g-watch-r/development/manual-ota-update-root-t2969845
I've changed the step slightly according to the comments inside the thread:
- Enter Bootloader (swipe top left-bottom right as soon as the LG logo pops up on boot)
- Unlock bootloader (fastboot oem unlock) and boot the watch normally once
- Turn off and re-enter bootloader
- Flash 5.0.1 Stock Recovery (fastboot boot recovery.img)
// Do Not Flash 5.0.2 stock recovery
- Enter recovery and ADB sideload the update (tap the android, select install update from ADB and enter adb sideload filename.zip)
//you might have to reinstall the ADB drivers, just follow the simple step to install ADB driver
Done.
Click to expand...
Click to collapse
My phone is stuck on bootloop. I have cyanogenmod 13 installed on my moto g 3rd gen(2015). I can't seem to get into my system recovery either, which is now twrp and it just shows the logo for twrp recovery. I also for some dumb reason disabled my usb debugging mode, so i can't flash my phone either. Help plzz
Maybe go to bootloader and reflash TWRP
minimale_ldz said:
Maybe go to bootloader and reflash TWRP
Click to expand...
Click to collapse
Doesn't work, can't connect to bootloader
znyght said:
Doesn't work, can't connect to bootloader
Click to expand...
Click to collapse
So, if you turn the phone off and then hold "power" and "volume down" untill it boots, nothing happens?
minimale_ldz said:
So, if you turn the phone off and then hold "power" and "volume down" untill it boots, nothing happens?
Click to expand...
Click to collapse
of course, it goes into bootloader but my PC can't recognize anything. So I can't flash anything. USB Debugging is disabled. If there was a way to force connect that would be great
znyght said:
of course, it goes into bootloader but my PC can't recognize anything. So I can't flash anything. USB Debugging is disabled. If there was a way to force connect that would be great
Click to expand...
Click to collapse
You don't need USB debugging to use fastboot when your phone is booted into bootloader. What you need there is a fastboot tool and drivers. I'm using this one:
http://forum.xda-developers.com/showthread.php?p=48915118
and if it doesn't install correct drivers for you, you can get them here:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
first thing to do is check what fastboot returns after this command:
Code:
fastboot devices
if it shows your device ID you're good to go
I'd suggest downloading stock firmware first and flashing it before messing with custom recovery. Just remember Motorola often updates bootloader with new firmware so don't flash anything older than you had on your phone before.
Good luck
EDIT: you can also use RSD Lite to flash a new software, it basically automates fastbooting proccess, so theres no risk of misspelling or doing other stuff wrong
EDIT2: firmware is here:
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
also, the OP (lost101) is a great, helpful guy who may give you some advice if you need
Thanks I'll give them a try
Originally Posted by minimale_ldz
You don't need USB debugging to use fastboot when your phone is booted into bootloader. What you need there is a fastboot tool and drivers. I'm using this one:
Click to expand...
Click to collapse
I've tried these but they didn't seem to work
Hi,
I'm stuck on eRecovery because I forgot to re-flash the stock recovery (B360) before doing a Factory Reset. So now I'm stuck on eRecovery and I have no recovery or TWRP installed. When I flash the stock recovery or TWRP via fastboot it says "Command not allowed " so I think that USB Debugging is not enabled.
My question: How can I enable USB Debugging ?
(Mayen via fastboot ? How ?
Thanks
jacquesallet said:
Hi,
I'm stuck on eRecovery because I forgot to re-flash the stock recovery (B360) before doing a Factory Reset. So now I'm stuck on eRecovery and I have no recovery or TWRP installed. When I flash the stock recovery or TWRP via fastboot it says "Command not allowed " so I think that USB Debugging is not enabled.
My question: How can I enable USB Debugging ?
(Mayen via fastboot ? How ?
Thanks
Click to expand...
Click to collapse
have you solved this problem buddy? i ahve the same problem. what should we do?
I followed this tutorial: https://forum.xda-developers.com/mate-9/how-to/funky-huawei-erecovery-solution-100-t3620165/page5
Post #45
but it didn't worked for me because the tutorial asks to change the DNS of the wifi router and FirmwareFinderRewrite crashes on my PC (Asus Windows 7) But you can try. Now I have no other solution so I'm going to use DC-Phœnix to unbrick my phone.
jacquesallet said:
Hi,
I'm stuck on eRecovery because I forgot to re-flash the stock recovery (B360) before doing a Factory Reset. So now I'm stuck on eRecovery and I have no recovery or TWRP installed. When I flash the stock recovery or TWRP via fastboot it says "Command not allowed " so I think that USB Debugging is not enabled.
My question: How can I enable USB Debugging ?
(Mayen via fastboot ? How ?
Thanks
Click to expand...
Click to collapse
jacquesallet said:
I followed this tutorial: https://forum.xda-developers.com/mate-9/how-to/funky-huawei-erecovery-solution-100-t3620165/page5
Post #45
but it didn't worked for me because the tutorial asks to change the DNS of the wifi router and FirmwareFinderRewrite crashes on my PC (Asus Windows 7) But you can try. Now I have no other solution so I'm going to use DC-Phœnix to unbrick my phone.
Click to expand...
Click to collapse
thanks for replying,
i'll try it later this tutorial. so if i got failed like you, how to use dc unlocker? im so newbie here man.
ImHonor said:
thanks for replying,
i'll try it later this tutorial. so if i got failed like you, how to use dc unlocker? im so newbie here man.
Click to expand...
Click to collapse
https://www.******.com/recover-huaw..._Full_bricked_devices_no_fastboot_no_recovery