Develop Bugs

[Q] need help rooting dinc2 please

so i got up to the part where i need to flash clockworkmod recovery into the command prompt however after i type in fastboot oem rebootRUU and it finds my device i move onto the next step "flash recovery recovery-clockwork-4.0.0.4-vivow.img and it cannot load that
i have left my phone plugged in on the htc screen hoping someone can help me successfully complete the root
many thanks in advance
EDIT: can only start in bootloader now, cant use it as actual phone =[

simple29 said:
so i got up to the part where i need to flash clockworkmod recovery into the command prompt however after i type in fastboot oem rebootRUU and it finds my device i move onto the next step "flash recovery recovery-clockwork-4.0.0.4-vivow.img and it cannot load that
i have left my phone plugged in on the htc screen hoping someone can help me successfully complete the root
many thanks in advance
EDIT: can only start in bootloader now, cant use it as actual phone =[
Click to expand...
Click to collapse
what guide are you using? the recovery img has to be in the same folder as fastboot unless you point it towards a different folder

In the same boat as the OP, I've done everything right and I get this error message in cmd with the black screen and white HTC text.
BTW OP - You can go back to using your phone. Take out the battery (with the usb plug out of the phone or computer) and put it back in and turn the phone on normally. You'll just have to go through the process again of fastboot oem rebootRUU to get back to the black screen with white HTC text.
I'm using the CyanogenMod Wiki HTC Incredible 2 Full Update Guide (since I cannot link it in my post), I dunno what the OP is using. Also, the recovery file is in the appropriate location(s) in the android-sdk-windows folder.

im using the cyanogenmod wiki and i tried putting the recovery image for clockwork into the same folder as fastboot and adb and it still gives me that error and i dont have the technical savvy to figure this out
edit: that would be the platform-tools folder in the android sdk folder, thats what i found people did by googling this
and to finalassault, i took out my battery and tried turning it back on normally i just get stuck at the white screen with the green htc lettering so i clearly messed something up unless i just have to wait a few minutes

Try this guide. Use the clockwork image attached instead of the one from the CM7 guide.
http://forum.xda-developers.com/showthread.php?p=14947083
Sent from my Incredible 2 using Tapatalk

nothing is working and im completely lost, thanks for the help though
also i still cant turn my phone on normally

drcrawfo said:
Try this guide. Use the clockwork image attached instead of the one from the CM7 guide.
http://forum.xda-developers.com/showthread.php?p=14947083
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
Same error, except it's just coming up as not able to load this file instead of the other one. Maybe I possibly screwed up whilst doing AlphaRev?
Edit - I just did it a different way and I didn't get an error message:
sending 'recovery' (5022 KB)...
OKAY [ 25.776s]
writing 'recovery'...
OKAY [ 2.254s]
finished. total time: 28.030s
I guess that worked.
Edit 2 - It "worked" but didn't really do anything else. Might have done something wrong on the AlphaRev step. Actually I'll shut up now, something else showed up.
Edit 3 and final edit - Done and done. That was fun.

how did you get it too work???

simple29 said:
how did you get it too work???
Click to expand...
Click to collapse
It sounds like you may have borked your stock rom....if you can boot to hboot and select fastboot then you should be able to flash the CWM from this link http://forum.xda-developers.com/show...php?p=14947083
Follow the instructions on the link not the one from CM Wiki. Make sure you have fastboot.exe and CWM image from the link in the same folder as your adb. If you're using windows 7 64bit then you'll need to run adb in compatability mode (at least that's what I had to do to get it working in 64bit).
You should then be able to flash a rooted, deodexed stock froyo sense rom from this link by Jcase http://forum.xda-developers.com/showthread.php?t=1138274 or use XGunthers Incredibly Debloated Rom here http://forum.xda-developers.com/showthread.php?t=1138202
That should get you up and runnning. Or you could just jump straight into the GB ASOP roms CM7, MIUI, etc.
Let me know if this works for you....

the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
edit: got it in compatibility mode, i suppose i didnt install it right because it looks like it does something for a few seconds then seems to stop

simple29 said:
the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
Click to expand...
Click to collapse
Use the link in my post above.
Sent from my Incredible 2 using Tapatalk

simple29 said:
the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
Click to expand...
Click to collapse
It's okay don't worry...I'm pretty new to this stuff too since I just got into rooting about 2 weeks ago.
Compatability mode is an option in windows 7. Right click on the adb.exe file and select Properties. Once that comes up, you'll need to select the compatability tab on top and choose run in 'Windows XP Service Pack 2' mode (sorry I'm at work and don't have access to my win7 machine). Then click ok and it should run in compatability mode.
Then just follow the flash instructions from the link drcrawfo posted up and you should be good to go!

yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod

ok so idk why but i decided to try taking out the sd card and then when i did the flash recovery cwm thing a whole list of commands came up in the command prompt and i have no clue if thats good or bad or what command i should pick
ill list a few just to see if that helps you guys in helping me out
update <filename>
flashhall
flash <partition> [ <filename> ]
and a few more then there were options that followed
edit: and now for somereason it doesnt flash again but if i do fastboot recovery i still get all those options so is there a way to get the cwm to flash through that way

simple29 said:
yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod
Click to expand...
Click to collapse
Hmmm..so you have all your files setup in the same folder and when running the commands from cmd they don't do anything? Does it saying anything is being sent?
This may be beyond my expertise. Have you tried posting in the clockwork mod thread in the development section?
Sent from my Incredible 2

I just want to mention that I didn't end up using the exact commands that are given from the wiki, that didn't seem to work for me. I had to mess around with it (including manually pointing cmd to where it was) to get it to work for me. Had all of the drivers, SDK stuff, the path and everything where they should have been. I hope you get this resolved.

nothing is working out for me this is not fun

same boat as you simple but I can still use my phone. I just gave up as none of the methods seemed to work.

simple29 said:
yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod
Click to expand...
Click to collapse
You need to open a command window, change the working directory to where adb/fastboot are located and then type adb.exe at the command prompt.
It sounds like you are trying to double-click the adb.exe from Windows Explorer.

yea i was double clicking, im not too savvy with this stuff, how do you change the directory and all that

[Q] Lg g3 D855 adb issues <no found solution>

Hi guys im unsure if you would call me a noob since ive been playing with androids and custom ops for a while, however my girlfriend purchased an lg d855 (stock as a rock)and "all of a sudden" it failed to reboot, now from what i have found it appears to be quite unusual for this to happen but common for the os to crash into a boot freeze or boot loop, i have no complete load of download mode, it comes up with the little blue dots and the picture of the phone or whatever the symbol is. i can get it into fastboot for use with the adb or fastboot apps, i have obtained the stock LAF.img for the 32gb variant, the issue is that after the phone is connected and ready to send operations
i send the command
c:\adb\fastboot erase recovery >
erasing recovery>
FAILED <remote: failed to erase partition>
and on the phone it says
<start>
fastboot: processing commands
fastboot: getvarartition-type: recovery
fastboot erase: recovery
partition getsize 16777216 bytes
erasing card: 0x48000:0x8000
error: command never completed
error: command timeout error
error: command completed with errors
failed to send erase grp start address
mmc erase failed
<end>
so the question, what the hell does that mean, also if i try other commands it also failes to complete them such as erasing the laf file and or replacing it, i feel like i am mostlikely not the only one with this issue, i do have all the correct drivers installed, using the adb that i have which is 1.3 and one that comes with a kit of the sdk tools and all that, i feel like it is a phone issue more than computer as its failing to erase the mmc, i am wondering if there is other commands i could put in the phone to figure this out or if anyone knows what it all means i would greatly appreciate any help Thanks guys an gals.

iv tried also to load a custom recovery but cant do that because it comes up with incomplete bootloader on the phone, is anyone even able to help? i have no idea what the hell i am doing and nobody seems interested to try and help me.

Same problem here
I'm in the same situation as you did you manage to erase the recovery or something else in order to put your smartphone to work? thkx

ferreirix said:
I'm in the same situation as you did you manage to erase the recovery or something else in order to put your smartphone to work? thkx
Click to expand...
Click to collapse
Can I give you a bit of friendly advice firstly if you look at this thread you resurrected it is dated about a year ago and also if you look at the person who posted his last post anywhere on Xda was over a year ago ( you can find this out by clicking on is name/profile and view forum posts).
Now my point is resurrecting this very old post and and asking a question to the person who posted it along time ago is not likely going to get you a answer from him.You probably need to find newer up to date posts or answers by doing a more in depth search.
Saying all that here is a little info that may help you it is a slightly different solution but may help you >> http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 << this is a more up to date thread and if you post your question there with as much detail as possible about your problem and anything you have done to fix it then you may solve your problem.
If you choose to try the advice given in that thread don't forget to use a tot file for your particulate model and not the one posted in the thread.
Good luck with your problem.

tallman43 said:
Can I give you a bit of friendly advice firstly if you look at this thread you resurrected it is dated about a year ago and also if you look at the person who posted his last post anywhere on Xda was over a year ago ( you can find this out by clicking on is name/profile and view forum posts).
Now my point is resurrecting this very old post and and asking a question to the person who posted it along time ago is not likely going to get you a answer from him.You probably need to find newer up to date posts or answers by doing a more in depth search.
Saying all that here is a little info that may help you it is a slightly different solution but may help you >> http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 << this is a more up to date thread and if you post your question there with as much detail as possible about your problem and anything you have done to fix it then you may solve your problem.
If you choose to try the advice given in that thread don't forget to use a tot file for your particulate model and not the one posted in the thread.
Good luck with your problem.
Click to expand...
Click to collapse
I can start to see the light with the tuto you recommended thank you so much !

2 XL flashing stock images, target didn't report max-download-size

Hello,
I managed to screw something up, and now my phone is in a bootloop.
I have already posted a question somewhere else on this forum, but I got a suggestion to post it here.
Here is the link to the thread.
https://forum.xda-developers.com/ge...ges-target-t3803741/post76807253#post76807253
Please, I really need to get this phone up and running again.
I'm going to try everything that is suggested.
Thank you very much,
Jan

jan_ruc said:
Hello,
I managed to screw something up, and now my phone is in a bootloop.
I have already posted a question somewhere else on this forum, but I got a suggestion to post it here.
Here is the link to the thread.
https://forum.xda-developers.com/ge...ges-target-t3803741/post76807253#post76807253
Please, I really need to get this phone up and running again.
I'm going to try everything that is suggested.
Thank you very much,
Jan
Click to expand...
Click to collapse
Where are you at right now, and what have you all tried besides the skipsoft?

Badger50 said:
Where are you at right now, and what have you all tried besides the skipsoft?
Click to expand...
Click to collapse
I tried downloading the official(8.1.0) and the latest version of P beta from Google, and ran the flash-all.bat. Running that said that the max reported download size was not reported and failed. As far as I know Android should still be installed, TWRP still works and thats pretty much it.

jan_ruc said:
I tried downloading the official(8.1.0) and the latest version of P beta from Google, and ran the flash-all.bat. Running that said that the max reported download size was not reported and failed. As far as I know Android should still be installed, TWRP still works and thats pretty much it.
Click to expand...
Click to collapse
Try a different USB cable.

ilal2ielli said:
Try a different USB cable.
Click to expand...
Click to collapse
I don't have any other cables. I will ask my friend to lend me his and try that. But what if that doesn't work?

I had this issue on my old tower. Plugging my phone into USB 3.X ports didn't allow it to flash images via fastboot with the same error. I plugged it directly into the case's 2.0 ports and it worked perfectly. My new tower doesn't do that, though. Oh and I had two brand new cables.
So basically try a different port/cable.

Ariac Konrel said:
I had this issue on my old tower. Plugging my phone into USB 3.X ports didn't allow it to flash images via fastboot with the same error. I plugged it directly into the case's 2.0 ports and it worked perfectly. My new tower doesn't do that, though. Oh and I had two brand new cables.
So basically try a different port/cable.
Click to expand...
Click to collapse
Thank you very much.
I will try every port I find on every device I find.
What shoul I do if I find that it works somewhere?
Should I simply run flash-all.bat?
I want to go back to full stock.
It's weird because that cable and that port work very well for data transfer and adb actually works. Fastboot works as well...
Is the problem in that command only?

I had a similar issue. I had to use a different PC to get my phone back to work. Try restarting the pc or a create a different user in Windows and see if that helps. Also there is a very useful script called Deus script on the forums here for bootloops try it.

dabaang_khan said:
I had a similar issue. I had to use a different PC to get my phone back to work. Try restarting the pc or a create a different user in Windows and see if that helps. Also there is a very useful script called Deus script on the forums here for bootloops try it.
Click to expand...
Click to collapse
Do you mean Deuces? I tried it. Should I try it again on a different computer?

jan_ruc said:
Thank you very much.
I will try every port I find on every device I find.
What shoul I do if I find that it works somewhere?
Should I simply run flash-all.bat?
I want to go back to full stock.
It's weird because that cable and that port work very well for data transfer and adb actually works. Fastboot works as well...
Is the problem in that command only?
Click to expand...
Click to collapse
Yeah, the case was the same for me.
Super weird issue.
OH, there's one more thing I can think of. What OS are you running? If it's Windows 10, it could also be that. MS and their automatic updates override Google's driver so I always disabled that. It's weird, but that was another issue I had at some point.
You might see a LeLand driver or something similar for it, I don't remember the exact name. So that's also something to look into if you can.
For full stock run flash-all.bat, this will erase all the phone's data though.

Ran into the same issue few days ago, changing cables and ports didn't help but restarting the computer several times did.

Ariac Konrel said:
Yeah, the case was the same for me.
Super weird issue.
OH, there's one more thing I can think of. What OS are you running? If it's Windows 10, it could also be that. MS and their automatic updates override Google's driver so I always disabled that. It's weird, but that was another issue I had at some point.
You might see a LeLand driver or something similar for it, I don't remember the exact name. So that's also something to look into if you can.
For full stock run flash-all.bat, this will erase all the phone's data though.
Click to expand...
Click to collapse
I do have a laptop that is running Win 7 and my father's laptop that has Vista on it for some reason.
Also I relaized my friend has a Type-C port on his desktop so will probably give that a try, and use the original cable.
I forced a Google backup before I messed it up so I don't really care about the data.
By the way what's the matter with the
"fastboot: error: Device does not support slots"?
Is that anything critical? Or just another weird error because of the cable/port?
Also: I did some digging throu the system files with TWRP and most of the root directories are empty...

jan_ruc said:
I do have a laptop that is running Win 7 and my father's laptop that has Vista on it for some reason.
Also I relaized my friend has a Type-C port on his desktop so will probably give that a try, and use the original cable.
I forced a Google backup before I messed it up so I don't really care about the data.
By the way what's the matter with the
"fastboot: error: Device does not support slots"?
Is that anything critical? Or just another weird error because of the cable/port?
Also: I did some digging throu the system files with TWRP and most of the root directories are empty...
Click to expand...
Click to collapse
See, look at all the advice you got. From what I've read, your USB cables appears to be your #1 issue. Like others have said, get a good USB A to USB C cable, and you'll likely be ok ?

Badger50 said:
See, look at all the advice you got. From what I've read, your USB cables appears to be your #1 issue. Like others have said, get a good USB A to USB C cable, and you'll likely be ok
Click to expand...
Click to collapse
Indeed, thank you! I'm actually kinda stuck installing the newest ADB and drivers right now... Can someone share a link to the latest 8.1 image avadible for this phone and the adb that I need, please? This laptop is currently quite clean and I really don't want to mess around anymore.
Thank you all!

jan_ruc said:
Indeed, thank you! I'm actually kinda stuck installing the newest ADB and drivers right now... Can someone share a link to the latest 8.1 image avadible for this phone and the adb that I need, please? This laptop is currently quite clean and I really don't want to mess around anymore.
Thank you all!
Click to expand...
Click to collapse
Here's the factor image page. Just look for Taimen, June image at the bottom of the section. Use the OPM2 unless your on T-Mobile.
https://developers.google.com/android/images
And this is the SDK/platform-tools that I use that also has the adb interface ?
https://developer.android.com/studio/releases/platform-tools

Badger50 said:
Here's the factor image page. Just look for Taimen, June image at the bottom of the section. Use the OPM2 unless your on T-Mobile.
https://developers.google.com/android/images
And this is the SDK/platform-tools that I use that also has the adb interface
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Thanks! Now I simply extracted the platform-tools in a folder C:\adb.
Downloaded the image, but the phone won't show up when I run adb devices...
On Windows 7... On my desktop it shows up the sec I run it.
Installed Google drivers as well.
Say could I simply "adb push" the image on the phone and flash it from TWRP?
"adb push" works. I just tried and pushed the image on the phone. But it says "invalid zip file format".
Could I extract the zip and push all the images one by one?

jan_ruc said:
Thanks! Now I simply extracted the platform-tools in a folder C:\adb.
Downloaded the image, but the phone won't show up when I run adb devices...
On Windows 7... On my desktop it shows up the sec I run it.
Installed Google drivers as well.
Say could I simply "adb push" the image on the phone and flash it from TWRP?
"adb push" works. I just tried and pushed the image on the phone. But it says "invalid zip file format".
Could I extract the zip and push all the images one by one?
Click to expand...
Click to collapse
You've got to get in the mindset that though adb and SDK/platform-tools are part of each other, they are also different. Adb is mostly used when your device is on, whereas sdk/platform-tools is used as your bootloader interface, where you do your fastboot commands.
After you installed the SDK, there should be a folder within SDK named platform-tools. That's where your extracted files from the factory image go. You don't put the full factory image in there. The pics should give you an idea what I'm taking about. You'll actually open your command prompt on the platform-tools folder so you can execute your fastboot commands.

Badger50 said:
You've got to get in the mindset that though adb and SDK/platform-tools are part of each other, they are also different. Adb is mostly used when your device is on, whereas sdk/platform-tools is used as your bootloader interface, where you do your fastboot commands.
After you installed the SDK, there should be a folder within SDK named platform-tools. That's where your extracted files from the factory image go. You don't put the full factory image in there. The pics should give you an idea what I'm taking about. You'll actually open your command prompt on the platform-tools folder so you can execute your fastboot commands.
Click to expand...
Click to collapse
Now I have installed Android Studio and selected the SDK tools that weren't selected before and installed them.
Still my question remains... Since the USB cable is the problem, could I flash it from TWRP? I don't mind keeping TWRP installed so if I could just reinstall the OS. That would be lovely.
On the other hand. Tell me what to do, and I'll do it.

Another route to go of your struggling with paths is my convoluted method that works for me. Every month I download the latest factory image and the latest platform tools and extract both to the same folder. I also put the TWRP.img file and also dueces script there too. So each month I have a stand alone installation. I have used the dueces script the last two months with good results. (I just like having both slots up to date in case I install a custom Rom). If you choose to go the route with the script there is an additional zip file to extract. At the end, all the loose files are in one directory beside some folders for platform tools. Let us know if you need additional info. Note for June they changed something in the syntax so dueces made a new version of the script. Here are the files in my latest dir.
deuce-flash-all-v4.5.bat
platform-tools-latest-windows.zip
taimen-opm2.171026.006.c1-factory-21236059.zip
Twrp-3.2.1-2-taimen.img

CyberpodS2 said:
Another route to go of your struggling with paths is my convoluted method that works for me. Every month I download the latest factory image and the latest platform tools and extract both to the same folder. I also put the TWRP.img file and also dueces script there too. So each month I have a stand alone installation. I have used the dueces script the last two months with good results. (I just like having both slots up to date in case I install a custom Rom). If you choose to go the route with the script there is an additional zip file to extract. At the end, all the loose files are in one directory beside some folders for platform tools. Let us know if you need additional info. Note for June they changed something in the syntax so dueces made a new version of the script. Here are the files in my latest dir.
deuce-flash-all-v4.5.bat
platform-tools-latest-windows.zip
taimen-opm2.171026.006.c1-factory-21236059.zip
Twrp-3.2.1-2-taimen.img
Click to expand...
Click to collapse
At the moment all I really want is to get this phone working...
I just re-ran the flash-all.bat with the same set of folders as you have and got this:
< waiting for any device >
Sending 'bootloader_a' (36380 KB) OKAY [ 0.937s]
Writing 'bootloader_a' FAILED (remote: Flashing is not allowed for Critical Partitions
)
Finished. Total time: 0.947s
rebooting into bootloader OKAY [ 0.002s]
Finished. Total time: 0.002s
fastboot: error: Failed to identify current slot
rebooting into bootloader OKAY [ 0.002s]
Finished. Total time: 0.003s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: TMZ12g
getvar:version-baseband FAILED (remote: unknown command)
fastboot: error: requirements not met!
Press any key to exit...
So I guess that means criticlal is locked?
I ran fastboot flashing unlock_critical:
fastboot flashing unlock_critical
FAILED (remote: Device already : unlocked!)
Finished. Total time: 0.002s
EDIT*: I rebooted the phone in hopes of you know... Any progress. It seems to be stuck on the "G" loading screen.
From this point could I just flash a custum ROM via TWRP?
I just want it to work.

adb restore 'ended' without restoring

OK so first of all, if this is the wrong place for this I'm sorry, it's quite late for me and I've been researching how to fix this for about two days and running up with nothing.
I recently upgraded to a Pixel 2XL, loving the device but unfortunately a couple of my apps save data into the data/data part of phone. The only way to then move that over and preserve the data is to use something like adb backup and restore. The backup seems to work fine, but so far every time I try to use restore on my pixel 2xl it 'ends' without actually adding the missing app data across.
I've tried using usb 2 and 3, no difference. I've made sure the usb debugging is on and that my phone is unlocked. I also made sure to try using the commands through both cmd and powershell and that both were in admin mode. I've also tried looking into other options like a friend suggested using es file explorer manager to change the download location, but I wasn't able to puzzle out a way to make something that was in data/data save elsewhere.
My phone isn't rooted, and I'd rather not go that far if I can help it. Any advice or ideas?

Aahhh,"...your phone isn't rooted..."that's probably it/key. I'm unsure whether any kind of "restore" works without root access -- backup of course works because that simply involves "copying" and "storing" files (essentially the basic process of backing up) and, as the system needs to be able to read and access the data, you pretty much have the "read access" to it. Restore on the otherhand, for those who are unaware, are essentially "copying" those stored files and "overwriting" the existing files -- which require "write access". The process of "rooting" is to acquire "root access" which allows both "read/write access" (therefore: "r/w access"). *again, for those who are unaware.
Sorry for just blabbering on about that, I guess I got carried away. In any case, basically (all in all, the reason why I blabbered on) I don't think you're going to go far without root access -- or "rooting" as you say -- but there is one thing I can suggest. When using adb, try running this command first before running any other adb command (i.e. restore):
Code:
adb root
It might just give you enough of that "root access" I was blathering about...
Also, among the all the things you made sure to do and include you made sure of, one thing you didn't mention is making sure you have the most up to date platform-tools (r28.0.1 *at least last I personally saw a few weeks ago).
Good luck to you, hope I made these things somewhat understandable, and hope this helped as well....

Thank you for the suggestions, tried it but no dice sadly. I kinda am hairy on rooting it too as I just got the phone and it's been a long time since I've done android dev work. If you have any other ideas I'd be welcome to hearing them but again thanks for trying.
simplepinoi177 said:
Aahhh,"...your phone isn't rooted..."that's probably it/key. I'm unsure whether any kind of "restore" works without root access -- backup of course works because that simply involves "copying" and "storing" files (essentially the basic process of backing up) and, as the system needs to be able to read and access the data, you pretty much have the "read access" to it. Restore on the otherhand, for those who are unaware, are essentially "copying" those stored files and "overwriting" the existing files -- which require "write access". The process of "rooting" is to acquire "root access" which allows both "read/write access" (therefore: "r/w access"). *again, for those who are unaware.
Sorry for just blabbering on about that, I guess I got carried away. In any case, basically (all in all, the reason why I blabbered on) I don't think you're going to go far without root access -- or "rooting" as you say -- but there is one thing I can suggest. When using adb, try running this command first before running any other adb command (i.e. restore):
Code:
adb root
It might just give you enough of that "root access" I was blathering about...
Also, among the all the things you made sure to do and include you made sure of, one thing you didn't mention is making sure you have the most up to date platform-tools (r28.0.1 *at least last I personally saw a few weeks ago).
Good luck to you, hope I made these things somewhat understandable, and hope this helped as well....
Click to expand...
Click to collapse

Where your bootloader is apparently unlocked, download a TWRP recovery image to the directory fastboot is in and boot it using the fastboot command "fastboot boot twrp.img". From there, take a nandroid backup of your device. Restoring is done in the same fashion. AND, since TWRP is memory resident when booting it this way, the stock recovery remains untouched.

Strephon Alkhalikoi said:
Where your bootloader is apparently unlocked, download a TWRP recovery image to the directory fastboot is in and boot it using the fastboot command "fastboot boot twrp.img". From there, take a nandroid backup of your device. Restoring is done in the same fashion. AND, since TWRP is memory resident when booting it this way, the stock recovery remains untouched.
Click to expand...
Click to collapse
Great idea! And that's why veterans and those with experience are the best to go to...!

OK so first, thank you so much for all the advice. I've taken awhile to get back to you because this took some time to parse. I'm admittedly kind of a novice at this. So I've used the instructions here https://www.xda-developers.com/how-to-install-twrp/ to try and install twrp. I think I did it right, had the zip contents and img file in the same directory that adb is in, then ran the command...and this is what I got back.
N:\platform-tools>fastboot flash recovery twrp-3.2.3-1-taimen.img
Sending 'recovery' (40960 KB) OKAY [ 1.203s]
Writing 'recovery' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 1.219s
as the 'fastboot reboot' command appeared to bring me right back to normal operating for the phone I'm guessing the failed stopped me with that 'flashing not allowed in lock state' there. Am I missing a step?

close, but not exactly right...
you got the downloading platform tools right, and putting the necessary files in that same folder that fastboot.exe resides in also right (you wouldn't believe how many novices actually make the mistake of not doing this)...
but you don't ever (underlined and emphasized not really for you AshtonHunter, but for any who are under the wrong impression; it's caused endless headaches and has even been complained by developers on Twitter...) "fastboot flash" TWRP with Pixels (any; and AFAIK any a/b slotted devices). You boot the twrp .img file. Also, for those who do not know and for future reference, there is no "recovery" for fastboot to "flash" to on Pixels (any), as there no longer is a separate partition for recovery; recovery resides in the boot partition. All in all, the command should be exactly this:
Code:
fastboot boot twrp-3.2.3-1-taimen.img
Immediately afterwards, you'll see your Pixel 2 XL restart and load up TWRP...
Good luck to you and hope this helps...

Hey everyone. So I tried this but it also didn't work. Same error 'cannot in locked state' when trying to run the command. I do notice there's a green 'locked' on my phone when it's in the screen after the 'adb reboot bootloader' command. Any ideas?
simplepinoi177 said:
close, but not exactly right...
you got the downloading platform tools right, and putting the necessary files in that same folder that fastboot.exe resides in also right (you wouldn't believe how many novices actually make the mistake of not doing this)...
but you don't ever (underlined and emphasized not really for you AshtonHunter, but for any who are under the wrong impression; it's caused endless headaches and has even been complained by developers on Twitter...) "fastboot flash" TWRP with Pixels (any; and AFAIK any a/b slotted devices). You boot the twrp .img file. Also, for those who do not know and for future reference, there is no "recovery" for fastboot to "flash" to on Pixels (any), as there no longer is a separate partition for recovery; recovery resides in the boot partition. All in all, the command should be exactly this:
Code:
fastboot boot twrp-3.2.3-1-taimen.img
Immediately afterwards, you'll see your Pixel 2 XL restart and load up TWRP...
Good luck to you and hope this helps...
Click to expand...
Click to collapse

AshtonHunter said:
OK so first of all,
if this is the wrong place for this I'm sorry, it's quite late for me and I've been researching how to fix this for about two days and running up with nothing.
I recently upgraded to a Pixel 2XL, loving the device but unfortunately a couple of my apps save data into the data/data part of phone. The only way to then move that over and preserve the data is to use something like adb backup and restore. The backup seems to work fine, but so far every time I try to use restore on my pixel 2xl it 'ends' without actually adding the missing app data across.
I've tried using usb 2 and 3, no difference.
I've made sure the usb debugging is on and that my phone is unlocked. I also made sure to try using the commands through both cmd and powershell and that both were in admin mode. I've also tried
looking into other options like a friend suggested using es file explorer manager to change the download location, but I wasn't able to puzzle out a way to make something that was in data/data save elsewhere.
My phone isn't rooted, and I'd rather not go that far if I can help it. Any advice or ideas?
Click to expand...
Click to collapse
AshtonHunter said:
Hey everyone. So I tried this but it also didn't work. Same error 'cannot in locked state' when trying to run the command. I do notice there's a green 'locked' on my phone when it's in the screen after the 'adb reboot bootloader' command. Any ideas?
Click to expand...
Click to collapse
You would only get this error if your device isn't "unlocked"... I/we were all under the impression that (which is why I quoted) your device is "unlocked"... So maybe some clarification is in order...
There are two types of "unlocking" that can be attributed to the device; 1) your device can be "locked" to a carrier or global region, and it can be "unlocked" so the device can be used on any network anywhere, and 2) all Pixel's (and all smartphones AFAIK) have their bootloader in a locked state, and in order to do any kind of "rooting" or data restore/recovery or modification down to the system level you have to "unlock" the bootloader or have it in an "unlocked" state.
*BEWARE! Before running these commands, please note that running critical will erase/wipe EVERYTHING -- I am pretty sure running both will actually cause this to happen.
Considering all of this, when you said your "...phone is unlocked", you are speaking in terms of #2 I listed above, correct? Basically, you have run the command -- while in Bootloader Mode -- "fastboot flashing unlock" & (just as important, imho) "fastboot flashing unlock_critical", right? Because, if you haven't done these, then your device was never "unlocked" (in the sense that most relates to us and what you are intending) as well as without having one these commands, you had no chance at restoring your /data folder or partition "data" (pun not intended).
After clearing any misunderstanding and/or issues of these type, we might be able to better help after that point...but it is looking like you may need to root or at least do the same steps towards that end to accomplish what you are seeking...
So, get back to me/us on this, and hope this all helps...

Ok! So after confirming I could do it without any issue and having a day of time to work on it, my phone's bootloader is now unlocked and I've managed a backup using TWRP. Only thing now is I'm not entirely sure what I should be looking at and how in here. Advice is welcome but I'm going to be digging into it myself to see if I can puzzle it out with some friends of mine online. Also just again thank you all for all the assistance. I would have never gotten this far with it without you all!

AshtonHunter said:
Ok! So after confirming I could do it without any issue and having a day of time to work on it, my phone's bootloader is now unlocked and I've managed a backup using TWRP. Only thing now is I'm not entirely sure what I should be looking at and how in here. Advice is welcome but I'm going to be digging into it myself to see if I can puzzle it out with some friends of mine online. Also just again thank you all for all the assistance. I would have never gotten this far with it without you all!
Click to expand...
Click to collapse
What exactly are you wanting to do now that your bootloader is unlocked, and you have twrp? Can I assume you want to root it?

AshtonHunter said:
Ok! So after confirming I could do it without any issue and having a day of time to work on it, my phone's bootloader is now unlocked and I've managed a backup using TWRP. Only thing now is I'm not entirely sure what I should be looking at and how in here. Advice is welcome but I'm going to be digging into it myself to see if I can puzzle it out with some friends of mine online. Also just again thank you all for all the assistance. I would have never gotten this far with it without you all!
Click to expand...
Click to collapse
I'm glad you were successfully able to get it done! (clicking a "Thanks!" would be all I would welcome in return)
So, now, you might be able to successfully do what you originally did and restore through adb if you wish...I mean, if you simply have a /data folder that's been backed up, there might not be too many options available for you. Another thing you might try is running a custom recovery (TWRP I believe is the best or only) and restoring -- and/or backing up from your old device/phone, wiping everything, setting phone up, then use that TWRP backup to restore -- but you can only really run a restore if it was a TWRP backup to begin with... One other good way is running a Titanium Backup backup and restoring that way...
Good luck and hope this helps...

please help
simplepinoi177 said:
Aahhh,"...your phone isn't rooted..."that's probably it/key. I'm unsure whether any kind of "restore" works without root access -- backup of course works because that simply involves "copying" and "storing" files (essentially the basic process of backing up) and, as the system needs to be able to read and access the data, you pretty much have the "read access" to it. Restore on the otherhand, for those who are unaware, are essentially "copying" those stored files and "overwriting" the existing files -- which require "write access". The process of "rooting" is to acquire "root access" which allows both "read/write access" (therefore: "r/w access"). *again, for those who are unaware.
Sorry for just blabbering on about that, I guess I got carried away. In any case, basically (all in all, the reason why I blabbered on) I don't think you're going to go far without root access -- or "rooting" as you say -- but there is one thing I can suggest. When using adb, try running this command first before running any other adb command (i.e. restore):
Code:
adb root
It might just give you enough of that "root access" I was blathering about...
Also, among the all the things you made sure to do and include you made sure of, one thing you didn't mention is making sure you have the most up to date platform-tools (r28.0.1 *at least last I personally saw a few weeks ago).
Good luck to you, hope I made these things somewhat understandable, and hope this helped as well....
Click to expand...
Click to collapse
sorry in advance, I'm not very familiar with this webiste.
Im in a similar situation where it wont let me restore my adb backup, I am rooted and the bootloader is unlocked (though twrp is not installed). could you please help, i beg you.

Unable to root the M8s, can't flash a recovery

Greetings, this is my first post on the forum.
Sadly, I tried to backup my M8s to do a factory reset it and I forgot to save some audio recordings.
I tried to root to install some kind of file recovery but it didn't work out.
I am on android 6.0.1
HBOOT 3.19.0.0000
OS-2.21.401.1
First, I unlocked the bootloader , using HTC Dev, then I tried to flash a custom recovery from voidzero(can't post the link due to being a new user)
It didn't work out saying :
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 7751680 is not a multiple of the block size 4096
Sending sparse 'recovery' 1/2 (15368 KB) error: write_sparse_skip_chunk: don't care size 7751680 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 7751680 is not a multiple of the block size 4096
OKAY [ 1.610s]
Writing sparse 'recovery' 1/2 FAILED (remote: 'image error! (BootMagic check fail)')
Finished. Total time: 1.844s
Then I tried to flash an older recovery from TWRP witch told me it was a success but when I try to enter recovery mode it says entering recovery for a split second and took me to fastboot once again. I am officially out of ideas and I didn't want to post anything before I don't "do my homework".
Thank you all in advance . I have learned a lot in the past week about my phone but not enough.

BigTree22 said:
Greetings, this is my first post on the forum.
Sadly, I tried to backup my M8s to do a factory reset it and I forgot to save some audio recordings.
I tried to root to install some kind of file recovery but it didn't work out.
I am on android 6.0.1
HBOOT 3.19.0.0000
OS-2.21.401.1
First, I unlocked the bootloader , using HTC Dev, then I tried to flash a custom recovery from voidzero(can't post the link due to being a new user)
It didn't work out saying :
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 7751680 is not a multiple of the block size 4096
Sending sparse 'recovery' 1/2 (15368 KB) error: write_sparse_skip_chunk: don't care size 7751680 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 7751680 is not a multiple of the block size 4096
OKAY [ 1.610s]
Writing sparse 'recovery' 1/2 FAILED (remote: 'image error! (BootMagic check fail)')
Finished. Total time: 1.844s
Then I tried to flash an older recovery from TWRP witch told me it was a success but when I try to enter recovery mode it says entering recovery for a split second and took me to fastboot once again. I am officially out of ideas and I didn't want to post anything before I don't "do my homework".
Thank you all in advance . I have learned a lot in the past week about my phone but not enough.
Click to expand...
Click to collapse
It is not a very good phone to root. I am popping in on this forum which I haven't used in almost a year...
I have had mine rooted for a long time. The phone is the only phunction that I use this phone for. That and the occasional porno search.
The phone resets its friggin permissions all the friggin time and displays a notification that its permissions for gallery require to be set to allow storage permission.
This can also be accompanied by a total settings wipe on occasion. That means that ALL settings get destroyed, such as network mode and location on/off.
This is usually also accompanied by disappearance of widgets, I have found.
All in all the phone has been decent as a phone-only, but really a PITA for any other use. I use my more modern larger phone for internet and other functions now.
It requires the obligatory visit to htcdev to be rooted. But I'm sure you know that.
Biggest thing is though, this phone is like pumping iron you will be a much stronger android user than the brainless masses who never heard of the apps tab in settings. Perhaps you'll even learn to clear your caches like dirty dishes after every use on social networking sites.

kruc Ire said:
It is not a very good phone to root. I am popping in on this forum which I haven't used in almost a year...
I have had mine rooted for a long time. The phone is the only phunction that I use this phone for. That and the occasional porno search.
The phone resets its friggin permissions all the friggin time and displays a notification that its permissions for gallery require to be set to allow storage permission.
This can also be accompanied by a total settings wipe on occasion. That means that ALL settings get destroyed, such as network mode and location on/off.
This is usually also accompanied by disappearance of widgets, I have found.
All in all the phone has been decent as a phone-only, but really a PITA for any other use. I use my more modern larger phone for internet and other functions now.
It requires the obligatory visit to htcdev to be rooted. But I'm sure you know that.
Biggest thing is though, this phone is like pumping iron you will be a much stronger android user than the brainless masses who never heard of the apps tab in settings. Perhaps you'll even learn to clear your caches like dirty dishes after every use on social networking sites.
Click to expand...
Click to collapse
Sorry I didn't answer earlier. I was away for a few days. The thing is, it's not that important, just wanted to have a little fun trying to root the phone, as I have never done this before.
This phone is not my primary phone so no big deal.
I unlocked the bootloader from HTC Dev but installing a TWRP said it worked and now, when I enter recovery....it just takes me back to fastboot menu, which is a bit weird and I'm stuck at this stage.
Has this happened to you before? because I searched for a bit and didn't find something like this.

BigTree22 said:
Sorry I didn't answer earlier. I was away for a few days. The thing is, it's not that important, just wanted to have a little fun trying to root the phone, as I have never done this before.
This phone is not my primary phone so no big deal.
I unlocked the bootloader from HTC Dev but installing a TWRP said it worked and now, when I enter recovery....it just takes me back to fastboot menu, which is a bit weird and I'm stuck at this stage.
Has this happened to you before? because I searched for a bit and didn't find something like this.
Click to expand...
Click to collapse
I use one of the TWRPs from this board
if you flashed one and it doesn't work, I suggest to flash the other
of course by now maybe there's a third or more recovery here. My TWRP works. My M8s is red and pretty reliable. I keep the stock system but use a few apps that use root. However like I said I only ever use the phone as a phone anymore. Or to look at Twitter.

kruc Ire said:
I use one of the TWRPs from this board
if you flashed one and it doesn't work, I suggest to flash the other
of course by now maybe there's a third or more recovery here. My TWRP works. My M8s is red and pretty reliable. I keep the stock system but use a few apps that use root. However like I said I only ever use the phone as a phone anymore. Or to look at Twitter.
Click to expand...
Click to collapse
Could you link me the exact recovery or tell me the version ? I have tried many of them,of course, from the other threads. and they didn't work.
The ones I tried are 2.8.6.0 | 2.8.7.1 | 3.2.1.0 | 3.2.3.0

You have not tried the recovery I use
it is 3.0.2.0
---------- Post added at 08:18 PM ---------- Previous post was at 08:06 PM ----------
Here is (a copy of a quote of) a/the xda post which contains a/the 3.0.2-0 twrp maybe it comes from:. You can additionally search the internet for "htc m8s" twrp 3.0.2-0
Note*
I remember now that I did have troubles with other twrps on the phone because they were a bad size. But this one (or the one I have) seems to work well:
burleanu said:
RUU for your phone is not present on ruu.lalleman.net.
Your need to find right RUU for your phone or wait for right OTA update for your phone made by H3G.
It is possible to change CID and flash whatever RUU. However, you need to be S-OFF and you loose customization of H3G ROM and warranty of course.
---------- Post added at 10:31 PM ---------- Previous post was at 09:48 PM ----------
@WildfireDEV, @El-Conkistador: Any idea why booting TWRP (twrp-2.8.7.0-m8s-qlul.img) restarts my phone and it doesn't boot it after upgrading to Android 6.0?
You can try to see if the last recovery from @Captain_Throwback works on android 6.0.
https://basketbuild.com/filedl/devs...back/One (M8S)/Recovery/twrp-3.0.2-0-m8ql.img (3.0.2.1 is not working)
This one works on 5.0, don't know if on 6 works.
Also maybe you need to use htc_fastboot instead of the fastboot.
To flash the img file for sure, don't know if just to boot tho.
Also locked or unlocked bootloader? I imagine locked if you could upgrade. Take care if you unlock it you will have to factory reset, is doing that when you unlock. Make at least a back-up on HTC servers if not other back-up
If you can boot it up please make a back-up of system and boot image and put it somewhere available.
Respect!
Click to expand...
Click to collapse

BigTree22 said:
Could you link me the exact recovery or tell me the version ? I have tried many of them,of course, from the other threads. and they didn't work.
The ones I tried are 2.8.6.0 | 2.8.7.1 | 3.2.1.0 | 3.2.3.0
Click to expand...
Click to collapse
How did it go? I am writing this cause you probably didnt get notified when I didn't quote you in that last comment.

kruc Ire said:
How did it go? I am writing this cause you probably didnt get notified when I didn't quote you in that last comment.
Click to expand...
Click to collapse
Oooh...you are right, I didn't get notified. I will try it in a couple of hours and post my answer, right now I have a bit of work to do. Thank you so much !

I have the same problem, TWRP 2..5.0.0 and the newest will not stick on my HTC OneM8s.
Curious if you get the problem solved

Oooh, boy, been a mad week for me.
Aside from a ton of work to do (I'm in senior high school and have a lot to do) , 5 days ago I dropped my primary phone (the primary one, a HTC M8) on the floor and it won't boot .
And now I'm left with the M8s as my daily driver and to be honest, I am a bit afraid to try to root it anymore because if this fails, I won't have another phone to go back to.
I opened the m8 up to see if maybe a cable was disconnected, but didn't find anything, I might send it to a repair shop in the near future(or tear it down completely to further inspect it).
As for the recovery, I won't try installing it anymore until I get another phone in the near future.
Sorry for taking so long to provide an update. If I decide to try to root it again I will post here about it, on this thread.

I can understand your ideaś.
I had contact with HTC and they gave me a link for a chat-session with one of their develloppers. But I first have to find out what time they are availablen nextr week and if I hear something useful I will post it here.
Thanx and have a nice weekend.