Device: Verizon's Motorola Droid Turbo with Android 6.0.1 and build number MCG24.251-5-5
Hey guys. Newbie here.
So recently i accidentally deleted an important video file and searched google for data recovery methods on smartphone. So most of the post that I read mentioned rooting and a recovery software called Dr.Fone etc. So I installed this software, connected my phone, turned on usb debugging and oem unlocking and started the recovery process. But it was not successful because dr.fone could not root my phone for deep data recovery.
so i googled again and tried sunshine, kingroot, kingoapp and iroot.
Then i tried adb and fastboot(to unlock bootloader).
The thing is in adb command line, the command "adb devices" shows my device. Then I wrote "adb reboot bootloader" and my phone rebooted. then i wrote "fastboot oem unlock(or something like this i copy/pasted it)" it told me that "waiting for any device".
I mean whenever i boot my phone into bootloader my "adb devices" command shows no device but i start my phone in normal mode the "adb command" is working.
Another thing, the "fastboot device/devices" is also not working. It just takes me back to a new line to enter a new command.
Any command containing fastboot is not recognizing my device and all the adb commands are recognized easily.
I have installed all the latest device drives including the universal adb drivers and motorola device manager.
Guys, i am open to all suggestions.
Please help me out.
You have to unlock your bootloader to get permanent root, and you have to do it with Sunshine.
Sunshine is a $25 paid app.
There IS an unstable, temporary root method appropriately called "temp root" that is actually the first step to using Sunshine to unlock the bootloader. Some people cheap out and ONLY use that. But it doesn't survive reboots and you have to run a special command to uninstall it, otherwise you bootloop.
https://forum.xda-developers.com/showthread.php?t=3639316
However, it's possible this temp root method will allow Dr. Done software to do what it needs. Read up on it, try it, see. (Ignore the parts about Magisk, you don't need that.) Just be sure to run the correct uninstall commands. But you would have to do that anyways, if you used Sunshine to unlock the bootloader.
ChazzMatt said:
You have to unlock your bootloader to get permanent root, and you have to do it with Sunshine.
Sunshine is a $25 paid app.
There IS an unstable, temporary root method appropriately called "temp root" that is actually the first step to using Sunshine to unlock the bootloader. Some people cheap out and ONLY use that. But it doesn't survive reboots and you have to run a special command to uninstall it, otherwise you bootloop.
https://forum.xda-developers.com/showthread.php?t=3639316
However, it's possible this temp root method will allow Dr. Done software to do what it needs. Read up on it, try it, see. (Ignore the parts about Magisk, you don't need that.) Just be sure to run the correct uninstall commands. But you would have to do that anyways, if you used Sunshine to unlock the bootloader.
Click to expand...
Click to collapse
Thanks man. Will try this method too.
ahm259 said:
Device: Verizon's Motorola Droid Turbo with Android 6.0.1 and build number MCG24.251-5-5
Hey guys. Newbie here.
So recently i accidentally deleted an important video file and searched google for data recovery methods on smartphone. So most of the post that I read mentioned rooting and a recovery software called Dr.Fone etc. So I installed this software, connected my phone, turned on usb debugging and oem unlocking and started the recovery process. But it was not successful because dr.fone could not root my phone for deep data recovery.
so i googled again and tried sunshine, kingroot, kingoapp and iroot.
Then i tried adb and fastboot(to unlock bootloader).
The thing is in adb command line, the command "adb devices" shows my device. Then I wrote "adb reboot bootloader" and my phone rebooted. then i wrote "fastboot oem unlock(or something like this i copy/pasted it)" it told me that "waiting for any device".
I mean whenever i boot my phone into bootloader my "adb devices" command shows no device but i start my phone in normal mode the "adb command" is working.
Another thing, the "fastboot device/devices" is also not working. It just takes me back to a new line to enter a new command.
Any command containing fastboot is not recognizing my device and all the adb commands are recognized easily.
I have installed all the latest device drives including the universal adb drivers and motorola device manager.
Guys, i am open to all suggestions.
Please help me out.
Click to expand...
Click to collapse
Have you tried just connecting to your pc, enable 'Transfer Files'/mtp mode, and using PhotoRec to scan it as attached storage? The video should not have been anywhere you would need root to access, so this should work. I personally haven't used PhotoRec on a phone in several years, but in the past it worked great. It's free software from CGSecurity (often bundled with TesDisk).
http://www.cgsecurity.org/wiki/Phot...data_from_my_phone.2Fdisk.2Fusb_key.2F..._.3F
Just remember, everytime you use the device you risk rendering the video totally unrecoverable. At best you'll get the whole thing back. More than likely if you're lucky, you'll only get part of it and it will be enough that video software can recognize and play what's left. (based on my own experience). It just depends on how large the video was (data-wise) and how many blocks were overwritten by other data.
Related
Hi,
I had unlocked boot loader through HTCdev on latest GB stock ROM. So, obviously I was S-ON.
Meanwhile, I tried many ROMs but manually flashing boot image in hastboot.
I had following status of last running mobile when I tried to get S-OFF
Bootloader status: unlocked
S-ON
HBOOT 2.00.0000
Recovery: CWM
ROM: CynovivoX (JB 4.1.2)
Yesterday, I tried to get S-off by downgrading as per following thread
http://forum.xda-developers.com/showthread.php?t=1705913
There were lots of error while script was running, but one I remember was related to goldcard.
While running RUU, It goes well till I find something Error 131, Customer ID related and than exit.
After trying script and RUU many times, my status is
Bootloader status: Relocked
S-ON
HBOOT 2.00.0000
Recovery: ? (can't see or access anymore)
ROM: -
when running fastboot devices, my device is appearing
but in adb devices, nothing there
So, is there still any possibility to recover from this bricked state?
Desperately looking for expert help as I am not developer but somehow....tried this thinking would not be that difficult business....so help.
Try running the latest RUU and restarting everything over. Make sure to pick the right RUU for your region. The latest build number should be 4.14.XXXXX...
Also, in fastboot, your device isn't supposed to be visible with command of adb devices.
Another thing u could try is to unlock the bootloader again and see if u can access recovery again. Adb works in recovery
Sent from the head of the Hammer
If you can get into fastboot but don't have a recovery installed, can't you just flash a new recovery? E.g. grab clockworkmod, connect your phone to your computer via usb and:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-vivo.img
(obviously replace above code with actual name of .img file)
err this might be stupid, but click on bootloader > recovery.
Looks like you are already in a sub menu when you boot the bootloader.
The error while downgrading is related to you not relocking your phone before downgrading. Always relock before downgrading with an RUU.
Sent from my Nexus 5
Thanks all guys.
But problem fixed. I have unlocked the bootloader again through htcdev and it worked.
Now let me share issue for all other nondevelopers like me who may also face such issue...
runme script is suppose to push some files through adb commands and then reboot to fastboot mode to lock bootloader.
I had adb drivers installed as I got prompt from statusbar.
However still, while running downgrade script (runme), phone was not detected in adb mode and hence no file was pushed to phone. After reboot, phone detected in fastboot and OEM successfully relocked.
I am really surprised why device not found error not appeared and script not stopped. Later I came to know this by running the script without connecting phone and it ran with asking Q&A with found device, and also reading log file.
Then I ran RUU who wiped everything.
So, my device left without any ROM and with OEM locked. I can't access or install recover, ROM etc and RUU was having goldcard error.
Somehow tried to unlock again through token provided by HTCDev earlier (around 2 years back).
And thing become normal and in my control.
My advise: always check "adb devices" before running the script as I found script is misleading of found device and finally locking device. And if such thing happen, easiest one is to get in unlocked from HTCDev and restart whole process.
RmatriX1218 said:
Thanks all guys.
But problem fixed. I have unlocked the bootloader again through htcdev and it worked.
Now let me share issue for all other nondevelopers like me who may also face such issue...
runme script is suppose to push some files through adb commands and then reboot to fastboot mode to lock bootloader.
I had adb drivers installed as I got prompt from statusbar.
However still, while running downgrade script (runme), phone was not detected in adb mode and hence no file was pushed to phone. After reboot, phone detected in fastboot and OEM successfully relocked.
I am really surprised why device not found error not appeared and script not stopped. Later I came to know this by running the script without connecting phone and it ran with asking Q&A with found device, and also reading log file.
Then I ran RUU who wiped everything.
So, my device left without any ROM and with OEM locked. I can't access or install recover, ROM etc and RUU was having goldcard error.
Somehow tried to unlock again through token provided by HTCDev earlier (around 2 years back).
And thing become normal and in my control.
My advise: always check "adb devices" before running the script as I found script is misleading of found device and finally locking device. And if such thing happen, easiest one is to get in unlocked from HTCDev and restart whole process.
Click to expand...
Click to collapse
From what I'm reading, I'm getting a much clearer image of what happened. I believe your problem to be just driver errors...
The script itself is supposed to run regardless of whether phone is properly connected with proper drivers and whatnot. After all, it's just a set of commands in cmd.
But seeing as you ONLY got Error 131, you could have solved this by simply creating a goldcard.
072665995 said:
From what I'm reading, I'm getting a much clearer image of what happened. I believe your problem to be just driver errors...
The script itself is supposed to run regardless of whether phone is properly connected with proper drivers and whatnot. After all, it's just a set of commands in cmd.
But seeing as you ONLY got Error 131, you could have solved this by simply creating a goldcard.
Click to expand...
Click to collapse
Phone was connected in adb mode. This I can say by checking notifications in android and statusbar prompt in windows 7. While running script only, something got wrong getting adb mode not detected.
Anyway, Goldcard was also in my next line of action, but not sure even after creating Goldcard, I may stuck as version-main was not downgraded to 2. However, tried and got resolved with much simpler effort of unlocking through htcdev.
May be, I am also not that competent to understand developing world and only good enough to simply flash ROMs and updates as per instructions.
Anyway, thanks.
So this morning I was lazy and tried rooting with the kingroot app, because I didn't want to factory reset. It went okay and I had root but I wanted to use SuperSU as my root manager. Well the binary wouldn't update so I figured i'd unroot from the kingroot app and remove kingroot from my phone, and root the proper way later. I pressed the unroot button and my phone rebooted, but now it's stuck in a bootloop.
I don't have an unlocked bootloader or a custom recovery, and I never checked the enable oem unlock in developer options so flashing stock isn't an option.
I tried sideloading the OTA for the build I was on, but I guess kingroot didn't actually unroot me, because it told me I needed to reflash.
I tried factory reset and wiping the cache in the stock recovery, and tried 'fastboot format userdata' and 'fastboot format cache' but that didn't work either.
The only thing I could find that might help is this post http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
but since I don't think you can run adb commands in stock recovery or bootloader this won't work.
So is there any way to fix this or am I boned?
As far as I know the only fix is the one in that link but it does require custom recovery. I'm assuming the fastboot boot command doesn't work when locked but I've never tried, if it does then you could temp boot into twrp. Worth a shot I guess.
Hindsight's 20/20 but NEVER touch anything other than your data or cache partition with a locked bootloader. Google's security jump with lollipop has caused nothing but havoc for us.
ChaosDr0id said:
So this morning I was lazy and tried rooting with the kingroot app, because I didn't want to factory reset. It went okay and I had root but I wanted to use SuperSU as my root manager. Well the binary wouldn't update so I figured i'd unroot from the kingroot app and remove kingroot from my phone, and root the proper way later. I pressed the unroot button and my phone rebooted, but now it's stuck in a bootloop.
I don't have an unlocked bootloader or a custom recovery, and I never checked the enable oem unlock in developer options so flashing stock isn't an option.
I tried sideloading the OTA for the build I was on, but I guess kingroot didn't actually unroot me, because it told me I needed to reflash.
I tried factory reset and wiping the cache in the stock recovery, and tried 'fastboot format userdata' and 'fastboot format cache' but that didn't work either.
The only thing I could find that might help is this post http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
but since I don't think you can run adb commands in stock recovery or bootloader this won't work.
So is there any way to fix this or am I boned?
Click to expand...
Click to collapse
If you already installed the drivers and know how to run fastboot commands skip to step 4. Otherwise, start at the beginning
1.) Install the Wugfresh Toolkit from here: http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 so that the drivers you need get installed along with fastboot and adb commands.
2.) Open Nexus Root Toolkit after it has finished installing. Under advanced utilities click "Launch" then choose launch command prompt for manual mode.
3.) Put your device in bootloader mode (pwr+vol down) and connect it to the computer. Type: "adb devices" into the command prompt and it should list a device serial number. If it does, go to step 4. If it doesn't, unplug the phone and plug it back in and re-run command.
4.) Then run the command "fastboot oem device-info" and tell us what the output is.
Hopefully when you rooted it, it unlocked your bootloader automatically. If you successfully rooted and rebooted it should technically be unlocked. We won't know until you run fastboot oem device-info
or, you can grab the factory image of whatever version of android that you were on, "unzip" it, grab the system.img, and flash it via fastboot. its the same thing as if was a "custom recovery", youre just reflashing the rom, and wont lose your data
first thing id do is flash a custom recovery and unlock my bootloader, and make a backup in recovery.
AlkaliV2 said:
If you already installed the drivers and know how to run fastboot commands skip to step 4. Otherwise, start at the beginning
1.) Install the Wugfresh Toolkit from here: http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 so that the drivers you need get installed along with fastboot and adb commands.
2.) Open Nexus Root Toolkit after it has finished installing. Under advanced utilities click "Launch" then choose launch command prompt for manual mode.
3.) Put your device in bootloader mode (pwr+vol down) and connect it to the computer. Type: "adb devices" into the command prompt and it should list a device serial number. If it does, go to step 4. If it doesn't, unplug the phone and plug it back in and re-run command.
4.) Then run the command "fastboot oem device-info" and tell us what the output is.
Hopefully when you rooted it, it unlocked your bootloader automatically. If you successfully rooted and rebooted it should technically be unlocked. We won't know until you run fastboot oem device-info
Click to expand...
Click to collapse
Hi, thanks for the reply.
It says
'device info' is not a supported oem command. See fastboot oem help.
FAILED <remote failure>
However I'm fairly certain the bootloader is still locked as I was unable to flash TWRP, or a stock image of android, as it tells me to unlock before doing those things.
AFAIK when you have this problem together with a stock recovery and a locked bootloader means bricked. >repair
Your bootloader is lock and you can't boot android to enable OEM unlock to unlock it. You have ruined your phone and there is no known fix.
RMA time for you.
Literally no solution unless you can invent one on your own.
Is it necessary to have your bootloader unlocked to boot into a custom recovery from your pc? Say you download twrp on your pc, would fastboot boot twrp.img be a work around for that?
CapitalParallax said:
Is it necessary to have your bootloader unlocked to boot into a custom recovery from your pc? Say you download twrp on your pc, would fastboot boot twrp.img be a work around for that?
Click to expand...
Click to collapse
yes
CapitalParallax said:
Is it necessary to have your bootloader unlocked to boot into a custom recovery from your pc?
Click to expand...
Click to collapse
Absolutely. Otherwise anybody with a notebook could swipe your phone, download everything you've got on it, then return it without you knowing, and that would mean more nekkid selfies on reddit.
CapitalParallax said:
Is it necessary to have your bootloader unlocked to boot into a custom recovery from your pc? Say you download twrp on your pc, would fastboot boot twrp.img be a work around for that?
Click to expand...
Click to collapse
The entire concept of a locked bootloader is that you can't flash images through it.
Alright, I somewhat hate Android 6.0, and that's because of my hard time rooting my Nexus 6, which is, at this point, becoming immensely irritating. If I'm allowed to do so here, since this is a Q&A board, I need to ask how the hell to root this thing, because of Android's new thing where I have to install a custom kernal to get root.
All I really know, now, ids that I need to unlock the bootloader of the phone, which I've been trying to do (installed SDK's platform tools, made sure my Nexus 6 Windows drivers are installed, but when I open a command prompt to unlock the bootloader, I'm met with a, "no devices found," response, so I have no clue what to do, and need some help, because with how many tutorials I've looked up for how to do this, and none of them working, I'm about heady to break my monitor. If anyone can explain what the **** I'm doing wrong, or link to a tutorial for how to unlock the bootloader, that actually explains what's needed to do so, it'd be appreciated.
Da-JesuZ said:
Alright, I somewhat hate Android 6.0, and that's because of my hard time rooting my Nexus 6, which is, at this point, becoming immensely irritating. If I'm allowed to do so here, since this is a Q&A board, I need to ask how the hell to root this thing, because of Android's new thing where I have to install a custom kernal to get root.
All I really know, now, ids that I need to unlock the bootloader of the phone, which I've been trying to do (installed SDK's platform tools, made sure my Nexus 6 Windows drivers are installed, but when I open a command prompt to unlock the bootloader, I'm met with a, "no devices found," response, so I have no clue what to do, and need some help, because with how many tutorials I've looked up for how to do this, and none of them working, I'm about heady to break my monitor. If anyone can explain what the **** I'm doing wrong, or link to a tutorial for how to unlock the bootloader, that actually explains what's needed to do so, it'd be appreciated.
Click to expand...
Click to collapse
This is how i always root the phone:
- Enable usb debugging and ENABLE OEM UNLOCKING in developer options
- Reboot into the bootloader and type fastboot oem unlock and let the phone boot up
- Flash TWRP in fastboot
- Go to recovery and flash a modified boot.zip (all custom kernels will do)
- Flash the latest superSU.zip, also in recovery
- Done
Here is a tut for the adb setup (Windows) http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/.
- Reboot into the bootloader and type fastboot oem unlock and let the phone boot up
That's my problem. Opening up the command prompt and typing, "fastboot OEM unlock," does absolutely nothing. No prompts come up on the phone. It just sits there, and doesn't do anything.
Da-JesuZ said:
- Reboot into the bootloader and type fastboot oem unlock and let the phone boot up
That's my problem. Opening up the command prompt and typing, "fastboot OEM unlock," does absolutely nothing. No prompts come up on the phone. It just sits there, and doesn't do anything.
Click to expand...
Click to collapse
Do you see a serial number in fastboot if you type: fastboot devices? If not your drivers aren`t installed correctly or adb isn`t setup correctly.
gee2012 said:
Do you see a serial number in fastboot if you type: fastboot devices? If not your drivers aren`t installed correctly or adb isn`t setup correctly.
Click to expand...
Click to collapse
I'm using Windows Vista, so I had to add an underscore, and type, "fastboot oem_unlock," to get the bootloader unlocked. Everything is restoring, now, however, I'm wondering if I'll have to do something similar with flashing TWRP, and the kernal I'm attempting to install. I don't know programming or cmd commands.
Da-JesuZ said:
I'm using Windows Vista, so I had to add an underscore, and type, "fastboot oem_unlock," to get the bootloader unlocked. Everything is restoring, now, however, I'm wondering if I'll have to do something similar with flashing TWRP, and the kernal I'm attempting to install. I don't know programming or cmd commands.
Click to expand...
Click to collapse
You only have to flash the TWRP.img file in fastboot, the rest (boot/superSU) are zip files to be flashed in recovery. I have no experience with Vista so can`t help you there, maybe there is some info about it on Google/YouTube.
I installed hisuite which is easily able to access all my device data. Installed adb universal which created c:/abd in my pc or don't know what created that. Installed minimal abd fast boot . Now the problem is, i go to c:/adb and open command line and keep getting "waiting for devices" then goto x86/minimal adb.... Again same thing. Even installed android sdk without even knowing what I'm doing. Now I'm feeling like dumb (probably I'm) and about about to give up. What I'm missing??
What are you trying to do and what commands are you issuing?
I'm assuming at the very least you have phone connected with debugging enabled.
Just trying to follow commands of "Unlock Bootloader, Even without code! by hackintosh5". But first I'm doing some simple commands like "fastboot reboot recovery" or "fastboot devices" but no luck. I must be doing something terribly wrong. At least show me a guide article, cause when i search i get extremely confused.
Some more info.
-usb debugging enabled, and pc authorized (maybe)
-hisuite is able to read everything so i must GUESS i have installed correct driver (tho i have no idea what it is)
Ok, to use the fastboot commands, the phone must be in fastboot mode. This is achieved by when phone is off , hold Vol - and connect phone to PC via USB.
Then try the above commands.
It finally worked, thanks a lot brother :laugh:
My phone is Rog Phone 3
WW_17.0823.2012.122
My boot loader is unlock since i used the boot loader unlocking app but i cant seem to flash twrp.
i have everything file necessary to root but when my phone goes into flashboot mode it stops detecting my phone
it detects perfectly fine during "adb devices" but when i run the "adb reboot-bootloader" command then it disconnects.
i also notice that my laptop doesnt have the "android" in "other devices" instead I have "universal serial bus usb" inside device manager.
can anyone help me?
Yes - it is absolutely possible to root!
Please check this forum properly for guides to root; plenty of info on this topic already.
Could you perhaps send me a link? As i keep getting errors when trying to flash twrp recovery when in fastboot mode
Yrmx said:
Could you perhaps send me a link? As i keep getting errors when trying to flash twrp recovery when in fastboot mode
Click to expand...
Click to collapse
I suggest that you factory reset it, try flashing another ROM (old) and retry. Everything is possible and as a proof my device is rooted, edxposed installed safetynet passing, magisk, TWRP installed. Only thing remaining is to get rid of the bootloader unlocked warning message.