Database Info

[Q] Problem rooting/not a noob....ideas???

I tried using revolutionary to root the phone and its worked for my phone and about 4 others ive done. but this peticular phone i came across it will read it, give me a code but tell me that i inputted the.wrong code and close. i did this a few times same.result. so i went to htc.com and unlocked the bootloader and i when i try to install the custom recovery the rough the bootllader it tells me.the phone is not recognized after it picks up the file and opens it. what the #$%$# is going on? lol

Chances are you've made a typo somewhere with Revo, and with unlocking via HTC you have to manually flash CWM to be able to flash a ROM

i tried like ten times and it keeps telling me key is incorrect.
i feel doing it manuelly is the only way to go. since the bootloader is unlocked i downloaded the recovery and saved it to the root. i turned on the phone to the bootllader, it reads it, and it says device not recognized. is their a .img file i can use instead? and what are the adb commands so i can flash it that way?

There are threads covering adb on here, and just Googling it will give you what you want to know as well.
What version of Revolution are you using? Could be an older one which has a different beta key than the current v0.4

adb way is manually
make sure you have sdk and adb/fastboot set up in your environment, its lot faster that way
once you have that, put the phone in fastboot
and type
fastboot flash recovery (drag the recovery.img in command window) and press enter and it will flash new recovery

HHHHHHHHEEEEEECCCCCKKK YYYYEEEESSSS!!!!
Thanks bro!!!!
I put the reocevery into c:/android
Ran cmd
fastboot flash recovery recovery.img
perfect
thx again!!!

Welcome and happy Rom flashing

[email protected] said:
i tried like ten times and it keeps telling me key is incorrect.
i feel doing it manuelly is the only way to go. since the bootloader is unlocked i downloaded the recovery and saved it to the root. i turned on the phone to the bootllader, it reads it, and it says device not recognized. is their a .img file i can use instead? and what are the adb commands so i can flash it that way?
Click to expand...
Click to collapse
Copy/paste the key to notepad then copy/paste from notepad to revolutionary then it will work.

[Q] Help Please no bootloader or recovery

Before anyone calls me an idiot and tells me to check other similar posts, trust me I have. I have been pulling out my hair for 5 hours now and I'm seriously out of ideas and methods. I currently have 14 tabs open on similar posts and how to fix it my problem as you can see from my pictures is I have no bootloader or recovery img. I have tried downloading the soju recovery files as well as a bunch of others I cant get into cwm at all and all I want to do is flash codename jellybean. I rooted the phone myself about a year ago and only remember that I had a really hard time finding a rom that I could even use. I have tried so many different fastboot combinations it disgusting I have watched videos on forcing the phone into cwm and nothing will work at all. When I try to fastboot recovery img and all I get is waiting on device forever! Can someone please dumb down the procedure for me so I can flash something new, please and thank you to anyone and everyone who can help me out.

1. Make sure you installed the correct drivers for your specific device. Go to fastboot mode then connect your phone to pc via usb. Below the android logo you should see something like this:
USB Control Init
USB Control Init End
STANDARD_SET_CONFIGURATION
2. Download this: http://techerrata.com/file/twrp2/crespo/openrecovery-twrp-2.3.3.0-crespo.img
3. Go to command prompt, then type this:
fastboot flash recovery <type the EXACT location of your downloaded img file, for example c:\downloads\openrecovery-twrp-2.3.3.0-crespo.img>
4. Reboot
5. Download whatever rom you like, go to custom recovery then flash it.
Oh btw, consider rotating your images first before attaching them.

ej8989 said:
1. Make sure you installed the correct drivers for your specific device. Go to fastboot mode then connect your phone to pc via usb. Below the android logo you should see something like this:
USB Control Init
USB Control Init End
STANDARD_SET_CONFIGURATION
2. Download this: http://techerrata.com/file/twrp2/crespo/openrecovery-twrp-2.3.3.0-crespo.img
3. Go to command prompt, then type this:
fastboot flash recovery <type the EXACT location of your downloaded img file, for example c:\downloads\openrecovery-twrp-2.3.3.0-crespo.img>
4. Reboot
5. Download whatever rom you like, go to custom recovery then flash it.
Oh btw, consider rotating your images first before attaching them.
Click to expand...
Click to collapse
I get waiting fro device when I type the command in I also do not see the STANDARD_SET_CONFIGURATION[/I]

I can assume that you got wrong drivers installed.
Follow instructions here: http://www.droidiser.com/2012/11/how-to-install-drivers-for-any-android.html

*disregard, sorry

Half bricked Xoom, deleted everything - help appreciated

Hello,
again i need help I have unlocked the bootloader on my Xoom, the i have flashed TWRP and downloaded a Rom and the Gapps. I copied the gapps onto the device and followed instructions which came with the rom. I was instructed to wipe "system" too which i did.
Of course that deleted the downloaded rom and gapps too. Now i have TWRP and was excited to mount USB storage and just copy over again the rom and gapps but unfortunately there is no mount as USB option.
What and how is the smartest way to go about it? I wanted to sideload over ADB but the device is not found. I have really tried everythin in my knowledge, hope someone can help
cheers

Come on guys, really need help here. My kids are killing me for the damn thing

I have same problem.......it's an issue of twrp !

Have you tried a micro sd card? (copy the rom and gapps there from a pc then put it in the Xoom, etc...)
Worst case, you should be able to grab the stock images http://forum.xda-developers.com/wiki/Motorola_Xoom and fastboot flash the device back to stock.

Have the same problem
dosada, could you solve the problem?
airesch, I tried to mount sd card but it is impossible. How can I return to stock without ADB because computer is not recognized?

hbtwender said:
dosada, could you solve the problem?
airesch, I tried to mount sd card but it is impossible. How can I return to stock without ADB because computer is not recognized?
Click to expand...
Click to collapse
Stock flash doesnt require adb, just fastboot mode. You may need to still install a driver, but if you can boot into recovery then the xoom should also be able to boot into fastboot mode and be recognized by a pc. If the instructions on the link I gave arent enough, I will see if I cant find something tomorrow when I am on a pc.
Sent from my GT-N8013 using XDA Premium 4 mobile app

hbtwender said:
dosada, could you solve the problem?
airesch, I tried to mount sd card but it is impossible. How can I return to stock without ADB because computer is not recognized?
Click to expand...
Click to collapse
NOTE: This WILL erase everything remaining on the device. In the case of the above, I don't know that you have much choice, just be forewarned.
Lord AIO toolkit has all the tools you need (look at the second post if you need the Windows driver.) Extract both the stock image zip and the toolkit (unless you have the sdk, in which case as long as you can find fastboot.exe you should be fine,) to somewhere convenient. Install the windows driver if you never have before and reboot your pc.
1. Boot your Xoom in fastboot mode: Power+Vol+ until it says: Starting Fastboot protocol support (you may need to tap the Vol+ instead of holding it the whole time, my Xoom has always been a bit picky about the buttons.)
2. Connect the usb to the pc
3. In a Command prompt window, go into the extracted version of the toolkit above (or if you have the sdk, just go to where you have fastboot.exe from it)
4. Run the following commands (replacing the files at the end with the full extract path from your stock image zip extract)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
"fastboot reboot" if you want to stay unlocked or "fastboot oem lock" if you want to re-lock and follow the prompts. The Xoom will get OTA updates even if it's unlocked, so there should be no reason to re-lock unless you need to send it in for service.
The driver isn't what I used to use, but it *should* work, and the instructions should be correct as far as I can remember. As long as you don't flash the wrong image to the wrong place/run out of power during flashing/disconnect during a flash then none of this should permanently damage the hardware and should get you a working device again. It's just that it's been so long since I have personally done any of this that I have forgotten more than I ever knew .

Solved
airesch said:
NOTE: This WILL erase everything remaining on the device. In the case of the above, I don't know that you have much choice, just be forewarned.
Lord AIO toolkit has all the tools you need (look at the second post if you need the Windows driver.) Extract both the stock image zip and the toolkit (unless you have the sdk, in which case as long as you can find fastboot.exe you should be fine,) to somewhere convenient. Install the windows driver if you never have before and reboot your pc.
1. Boot your Xoom in fastboot mode: Power+Vol+ until it says: Starting Fastboot protocol support (you may need to tap the Vol+ instead of holding it the whole time, my Xoom has always been a bit picky about the buttons.)
2. Connect the usb to the pc
3. In a Command prompt window, go into the extracted version of the toolkit above (or if you have the sdk, just go to where you have fastboot.exe from it)
4. Run the following commands (replacing the files at the end with the full extract path from your stock image zip extract)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
"fastboot reboot" if you want to stay unlocked or "fastboot oem lock" if you want to re-lock and follow the prompts. The Xoom will get OTA updates even if it's unlocked, so there should be no reason to re-lock unless you need to send it in for service.
The driver isn't what I used to use, but it *should* work, and the instructions should be correct as far as I can remember. As long as you don't flash the wrong image to the wrong place/run out of power during flashing/disconnect during a flash then none of this should permanently damage the hardware and should get you a working device again. It's just that it's been so long since I have personally done any of this that I have forgotten more than I ever knew .
Click to expand...
Click to collapse
Hey airesch, thank you for your support. I couldn´t follow yours suggestion because my xoom was not recognizing the PC or MAC. However I discovered that my sdcard was broken. When I´ve tried a new one with ZIP files inside it works perfectcly and I could return to my old room doing flah in the recovery mode of TWRP2.2.
It is important to note that my Xoom did not find .IMG files inside the card but only ZIP ones. Any way it worked perfectly and I hope this solution will serve to other in solving his/her problems.
Many thanks

Well, that works too, and that was closer to what I originally suggested (tho I didn't expect you had a bad sd card.)
And yes, recoveries generally don't support IMG files directly, you need to have a specially crafted zip to flash those in. IMG files directly are for fastboot/pc tool flashing.
Congrats on fixing it.

[SOLVED] No OS and can't switch off to reboot into recovery

Hi there,
I had my HTC One S rooted, S-OFF, unlocked, with SuperCID running MaximusHD and I wanted to reinstall a fresh version of it to give it to my father. However, I went too fast and wiped absolutely everything. So now, I'm stuck on the startup screen (with the warning message in red) with no OS and I can't reboot into recovery (wether using hard keys or fastboot) as I can't switch off my phone. What do I need to do in this case? It's plugged to my computer but, of course, as it's stuck on the startup screen, it doesn't recognize it.
Thanks in advance.

Small update: I managed to turn it off but I still can't get it recognized by my computer. I will try to uninstall all drivers for now, I'll get back here as soon as I have time to do that. Hopefully someone will have an idea by then

Flash the recovery from my signature. It will enable USB mounting in recovery mode for hboot 2.16. Just be sure to flash the dm version.

The thing is I can't flash anything since I can't transfer anything to my phone.
Right now, what I've done is reinstalling drivers properly (I get the mention "FASTBOOT USB" in bootloader) but I can't do anything with One S toolkit v4 for example. I managed to get adb commands working and tried to push Maximus ROM through ADB but I got a protocol failure message
Edit: oh wait, it's been transferred anyway.

Do you still have the folder from the install package archive? If yes, open the cmd console and go to the package folder. If it's like in my case "D:\Root" you got to type
Code:
d:
and press enter. Then you got to type
Code:
cd
hit space, repeat pressing tab until it says
Code:
cd Root
and hit enter, again. Then plug in your phone, put it into fastboot usb mode and type
Code:
fastboot devices
into the cmd console and hit enter, once more. If everything is working you should get a list with attached devices which shows your phone.
If your phone isn't listed try another usb port or another cable or if nothing else works another computer.
Next download the TWRP version from my signature, rename it to recovery.img an put it into the install package folder. Then enter
Code:
fastboot flash recovery recovery.img
into the cmd console and press enter for one last time.
TWRP 2.8.0.1-dm should be installed now and you should be able to mount your phone as mtp in recovery mode.

It's all good now! I could get ADB/Fastboot working and could reinstall a fresh Maximus on my One S. I can now safely give it to my father and enjoy my new Z3 Compact. I'll probably install your TWRP anyway though.
Thanks for your help!

Your welcome. Actually it's not my work so it's not "my" TWRP. I've found some mistakes in my last answer cause I'm in a little hurry right now. Going to correct it later for the case that someone else has a similiar problem...
Edit: My previous answer is corrected now.

Flashed stock recovery and thought I soft bricked my shield tablet.

First I'll give credit where it is due. From two threads on this site is where I got help with this issue:
I followed THIS guys steps for manually erasing and got the recovery images and lots of other useful information from HERE. Thank you guys very much!
OK, so, hopefully I can help someone with my little story as well. I was having issues with apps and programs crashing on me with lollipop and the new marshmallow update. The tablet just wasn't working properly and moving slow. I even had the SD card holding all my apps and larger files so I didn't overload the internal storage. So, I decided I wanted to flash back to factory/stock recovery and go from there. I did this using THIS method. I flashed via the "flash-all.bat" file (the command in fastboot is the same as the file name). I should note that there was one instance that failed during the install (I did try it again and got the same failure). Said something about “did you mean you wanted to flash this partition” or something, then showed it failed. After flashing I hit continue on the bootloader screen of the tablet and it said it was "cold booting." After about 5 minutes or so it started to boot but never made it past the NVidia screen. I tried wiping the phone with factory reset, wiping the cache, etc. and then re-flashing the recovery (again with the .bat file). I tried flashing TWRP but it didn't install apparently, because it still went to factory recovery. I even re-locked and then unlocked my bootloader to see if that would set everything straight. Nothing seemed to work. I knew I would eventually find a solution though so I kept looking. Stumbled on some other people that had the same issues but no solution (hope those people got it figured out). So here's what I did after some more research:
First, if you're in this situation and you did factory reset to try and resolve the problem, you may feel like you can no longer communicate with the device via fastboot/adb, but as long as you have the usb drive and your SDK tools installed (I used CodeWorks for Android all-in-one program) that shouldn't be a problem. You'll just have to be in the bootloader on the tablet.
-If for some reason you deleted or uninstalled your drivers and tools you'll have to download them again and then, the computer should still be able to communicate with the tablet. In the device manager under portable devices it will still show up as Module something or other. So the computer still sees the device but doesn't fully recognize it yet. Don't worry, this should still work! Just make sure you that fastboot is seeing the device by inputting "fastboot devices" in the command window and a 14 digit serial number should pop up. If it just says "list of devices" or there's nothing then you wont be communicating with the tablet.
Your device should be connected to your computer and started in bootloader mode. On your computer you should have the command prompt for adb/fastboot open. I just go to the folder where the .exe files are located and hold shift and right click in the white space of the folder, then select "open command window here."
From here follow the erase steps: stolen from manigault! :highfive:
fastboot erase system
fastboot erase userdata
fastboot erase boot
fastboot erase recovery
fastboot erase cache
Then flash your recovery MANUALLY:
fastboot flash recovery {dir}/recovery.img
fastboot flash boot {dir}/boot.img
fastboot flash system {dir}/system.img
fastboot flash userdata {dir}/userdata.img
fastboot flash staging {dir}/blob
fastboot flash dtb {dir}/tegra124-tn8-p1761-1270-a04-e-battery.dtb
You can download whatever recovery version you wish. I downloaded 2.2.2 because that's what my device came with out of the box on Christmas 2014. It will more then likely be a .zip file. To make this whole process a little easier simply extract the files in the .zip file where the adb.exe and fastboot.exe files are located (folder should be named platform-tools) and you can completely eliminate typing the whole directory before the file name. ***After your done flashing everything you can go back and delete those files if you want. Just double check that you're deleting the right files by looking at the original zip file. Not sure if it makes a difference but I deleted them anyway.
For example the commands in fastboot will look like this exactly :
(after extracting recovery files into platform-tools folder)
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
Note: Do NOT use the flash-all.bat command as this doesn't seem to work for this situation. Do it manually like shown above. And let each individual process complete before attempting to input another command.
After this step I didn't select continue on the bootloader. You can either select reboot or simply input "fastboot reboot" into the command window. It may take about 5 minutes to start installing everything but just be patient, it should start. Sometimes with these things you have to do things twice before it works. If for some reason it doesn't work the first time then start from the beginning and try it again. It took two times for me, but that's because I installed system.img twice and was getting double screen. Newb error... and I was a bit inebriated last night when I did this.
Hope this helps someone!
Thanks again to manigault and MidgetMob!
NVIDIA download files HERE!

i think i done the same thing
but the problem i now have is i cnt get tablet into fastboot on pc. i can load fastboot on tablet with power and volume down , but the tablet only shows as MTP device in device manager. i have downloaded drivers from nvidia and no matter what i try i cant install them i have been through all instructions but scince it went to mtp device i cant get device showing in adb. The only way i can get device showing in adb on pc ist to select apply update from adb ! but none of these commands listed in your post will work because its in sideload. is there anyway i cn reset , flash custom rom ect bu using commands while device is in adb sideload.
all i get is now send the package you want to apply to the device with "adb sideload <filename>".....
if you could shed any light on this it would be much appreciated , thanks , lester

did you update official android 6.0 before? then, not working stock recovery, stock boot...
If you can enter bootloader mode, download unofficial twrp 3.0.0.0 (here http://forum.xda-developers.com/shield-tablet/development/wip-twrp-2-8-0-1-unofficial-t2877117) and flash it.
i have a working boot.img file on marshmallow if you want.. please reply.

Sorry for the late response! I have no clue how you got into sideload??? Are you talking about through the recovery on your device? You're not able to get adb/ fastboot to recognize the device, right? It doesn't matter how you get the tablet into the bootloader. Whenever you have the phone in the bootloader then you'll use the fastboot command to "talk to" the device; i.e. "fastboot devices" without the quotes. That command should show your device if it shows as an MTP device whenever you open your "device manager" in windows. That's the same exact situation I was in. Download the codeworks from nvidia like I linked above. Hopefully then you should be able to recognize your device through the bootloader. If not DM me and I'll try to help you.

I'm having the exact problem as Lester. Tablet boots into bootloader but won't connect to computer. So I go into recovery mode and nothing works except apply update from adb. Which brings up the side load message that Lester quoted. And bootloader is showing "device=locked". I am attempting to fix this tablet for a friend that messed it up trying to flash a custom rom. Problem is he had no idea what he was doing and I'm not exactly sure what he did. I do however have a lot of experience with rooted android devices and flashing so any help would be GREATLY APPRECIATED!
---------- Post added at 05:59 PM ---------- Previous post was at 05:55 PM ----------
Also, I've already tried flashing stock rom back onto the tablet by applying update from sd card function in the recovery but when I try to do that the tablet for some reason can't mount the sd card.

rom fiend said:
Tablet boots into bootloader but won't connect to computer.
Click to expand...
Click to collapse
If you've got the device in bootloader then you need to use fastboot, not adb. Try the command 'fastboot devices' and see if the device id is listed. If so then grab a factory image, unzip it and use fastboot to flash the .img files using the commands 'fastboot flash system system.img'. Just make sure to match the partition names to the files.

Hello i have similar issue except when i try flash something i get this error ''remote: file write failed''
and i have to reboot into fastboot to get it flashing fully
but even though i managed to flash everything by rebooting when i boot system nothing shows up, i can just see the back light coming on and turning off after a while
Please help