Database Info

Cannot Factory Reset Phone

I have an HTC One XL(Evita, At&t)? I purchased it from a third party. The device is rooted and unlocked.
My phone's battery died. Once I went home to recharge it, the device was unable to get past the white HTC quietly brilliant screen. I would reboot it by pressing the volume down button + power button to reboot it and factory reset it. However, it continued to do this action. Then, I chose to reboot it under some setting. After I rebooted it, the device went to a "teamwins" screen. I erased everything, including the rom. Once I did this, it re-booted the device and continued to be on the same screen. Since this action happened, I connected it to my Windows 7 PC. I noticed that my HTC could not be identified as an external hard drive, it was identified as a CD rom drive.
I tried to fix this problem by looking at other forums containing this topic. Here is what I tried:
- I tried to go to HTC support. I downloaded the current system, and tried to use it. When I tried to use it, it kept saying error.
- I uninstalled the driver and tried to re-install it, it came back as a CD rom drive.
- I restarted my computer, pressed f8, and put disable driver signature.
- The driver re-installed as a CD rom drive.
Can anybody help me identify my problem, and a solution for it?!? Thank you so much

You need to relock the boot loader before running an ruu.
Fastboot oem lock
Did you do a reset in the boot loader or recovery? If you did it in the boot loader you just corrupted the sdcard and need to reformat that
Sent from my HTC One X-

absolutelygrim said:
You need to relock the boot loader before running an ruu.
Fastboot oem lock
Did you do a reset in the boot loader or recovery? If you did it in the boot loader you just corrupted the sdcard and need to reformat that
Sent from my HTC One X-
Click to expand...
Click to collapse
How do you relock the bootleader, do fastboom oem lock, adnd reformat the sd card?
I resetted in both, I believe. I haven't touched my phone in over a week

samoyedpuppy said:
How do you relock the bootleader, do fastboom oem lock, adnd reformat the sd card?
I resetted in both, I believe. I haven't touched my phone in over a week
Click to expand...
Click to collapse
Do a quick Google search for 'fastboot files'
Extract somewhere like C:\
Open command prompt
cd C:\fastboot
fastboot oem lock
Don't format the SDcard
Sent from my HTC One X-

And when you wiped system in recovery your phone had no Rom to boot up into so that's why you couldn't...search fastboot and learn a bit on it like grim said and than in fastboot do the command he said to lock your bl than run the ruu

absolutelygrim said:
Do a quick Google search for 'fastboot files'
Extract somewhere like C:\
Open command prompt
cd C:\fastboot
fastboot oem lock
Don't format the SDcard
Sent from my HTC One X-
Click to expand...
Click to collapse
Should I connect the phone turned off or on?

Also, when I type in the command without the phone, I get: 'not reecognized as an internal or external command, operable program or batch file'

bump

bump

samoyedpuppy said:
Also, when I type in the command without the phone, I get: 'not reecognized as an internal or external command, operable program or batch file'
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://www.dropbox.com/sh/vdmnx14u1pkn4s8/vDVJJI44XW/fastboot2.jpg

[Q] I need help unlocking bootloader

I am trying to unlock the bootloader on my US Moto G 16 G. I have followed the instructions provided in Unlock Youe Device and Android Pit. I have followed the instructions in the FAQ as well.
After I input "$ fastboot oem get_unlock_code" i get the following reply " '$' is not recognized as an internal or external command, operable program, or batch file."
I have searched for the reply in Google, but I cannot come across another user who has documented this issue and how to resolve it. Any help would be greatly appreciated.

You are not supposed to write the $ symbol, start with "fastboot..."
Sent from my XT1032 using xda app-developers app

kafepuya said:
I am trying to unlock the bootloader on my US Moto G 16 G. I have followed the instructions provided in Unlock Youe Device and Android Pit. I have followed the instructions in the FAQ as well.
After I input "$ fastboot oem get_unlock_code" i get the following reply " '$' is not recognized as an internal or external command, operable program, or batch file."
I have searched for the reply in Google, but I cannot come across another user who has documented this issue and how to resolve it. Any help would be greatly appreciated.
Click to expand...
Click to collapse
The $`s are not to be typed bro and the correct cmd command afaik is : fastboot oem get_unlock_data

Thanks for pointing out the mistake on the command. I tried the correct way of doing it, and I still get essentially the same reply. Here is a screenshot to illustrate my situation.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I got the same, when you paste the code into the box click and delete all spaces and make sure there are no spaces at the beggining of the code also.

kieranc88 said:
I got the same, when you paste the code into the box click and delete all spaces and make sure there are no spaces at the beggining of the code also.
Click to expand...
Click to collapse
No dice bro. No matter what I type, I get back "[whatever the first word in the command I type] is not recognized as an internal or external command, operable program or batch file.
I don't even know what to try next.

Oh I get you now, have you got fastboot and adb installed? If so point it to the folder that contains fastboot and adb iI usually place it on c drive in a folder called android so in command prompt to point it adb I would type cd c:/android then execute your commands

kieranc88 said:
Oh I get you now, have you got fastboot and adb installed? If so point it to the folder that contains fastboot and adb iI usually place it on c drive in a folder called android so in command prompt to point it adb I would type cd c:/android then execute your commands
Click to expand...
Click to collapse
Well, I don't know if I have adb installed. I only downloaded and installed the 2 files mentioned in the Motorola page. Android SDK and the latest Motorola drivers. I can navigate to any folder in terminal (all I do is Shift+Right click on a folder and select open command window here...)

If you haven't got adb and fastboot installed look here http://forum.xda-developers.com/showthread.php?p=42407269

kieranc88 said:
If you haven't got adb and fastboot installed look here http://forum.xda-developers.com/showthread.php?p=42407269
Click to expand...
Click to collapse
Well, that sure is quite more than was in the Motorola website. Ill read up on that and figure out how to do it. Thanks a lot. I'll keep you posted.

You don't actually need the android SDK ,install adb and fastboot from the previous link I posted above
Install drivers point cmd to folder containing adb and fast boot type in cmd "adb devices" if your phone is recognised it will show a serial number,if so continue with the unlock process,
If its not recognised the drivers aren't installed properly if so download pdanet for windows and set it up ( its a tethering app but it installs drivers) get it here http://pdanet.co/bin/PdaNetA4126.exe
Check again if device is recognised and if so continue with rest of process
---------- Post added at 12:59 AM ---------- Previous post was at 12:51 AM ----------
For an easier way to install adb check this out http://forum.xda-developers.com/showthread.php?t=2588979

kieranc88 said:
You don't actually need the android SDK ,install adb and fastboot from the previous link I posted above
Install drivers point cmd to folder containing adb and fast boot type in cmd "adb devices" if your phone is recognised it will show a serial number,if so continue with the unlock process,
If its not recognised the drivers aren't installed properly if so download pdanet for windows and set it up ( its a tethering app but it installs drivers) get it here http://pdanet.co/bin/PdaNetA4126.exe
Check again if device is recognised and if so continue with rest of process
---------- Post added at 12:59 AM ---------- Previous post was at 12:51 AM ----------
For an easier way to install adb check this out http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
I did it! Thanks for all the great help, specially kieranc88. Xposed here I come!!!

help root

Hi everyone,
I tried the method given by @DallasCZ but I have an issue.
All the files are in the same folder but I have this message: "cannot load: 'boot.img': No such file or directory"
Please help me !
Thanks in advance.
Kisses

Bencaill said:
Hi everyone,
I tried the method given by @DallasCZ but I have an issue.
All the files are in the same folder but I have this message: "cannot load: 'boot.img': No such file or directory"
Please help me !
Thanks in advance.
Kisses
Click to expand...
Click to collapse
Hello, are you sure you have the boot.img also in the direcotry?

DallasCZ said:
Hello, are you sure you have the boot.img also in the direcotry?
Click to expand...
Click to collapse
yes, I am sure I have it

Bencaill said:
yes, I am sure I have it
Click to expand...
Click to collapse
i tried it again and it works well for me.
can you post a creen of the folder where you extracted the files?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

you have to run the root.bat file, you cannot dir the boot.img

I know I have to run the bat file but you asked me a screen of the folder

I have this message:

strange... idunno for me its working well (windows 7 pro) and the boot.img is in the same directory... do you have some antivirus, anti spam apps running?

A other member of Frandroid forum has exactly the same issue. But he is running W8.1
That is really strange.

I am running win 8.1 as well

POThe only thing I can suggest is to change the line
fastboot -i 0x1bbb boot boot.img
to (in your specific case)
c:\users\user\desktop\idol3_6045_root\fastboot -i 0x1bbb boot c:\users\user\desktop\idol3_6045_root\boot.img
and see what occurs.
I'm thinking you may have fastboot somewhere else on your computer as well and that somehow, it's looking in the local directory of that fastboot. While that goes against everything logical (local directory should always be checked first), I'd give that a shot.
If that still doesn't work, open the cmd.exe with elevated permissions (right click "command prompt" in start menu, and run as administrator)

The problem seems to be resolved by using Windows 7 instead.
http://forum.frandroid.com/topic/223905-tuto-root-de-l-idol-3-55/?p=3417628

using win 7 is not a solution... there have to be a way how to do it, because there are thousands of users with win 8.1 who using fastboot and adb commands...

Is it a drivers issue? Does "adb devices" return anything? Or "fastboot devices" if you're in the bootloader? If you don't get a device listed after executing that command, the OS isn't fully recognizing the Icon 3.
I've all but abandoned using Windows for interaction with my Android devices. The driver issues are too big a pain in the butt. With Mac, and no need for installing drivers, the only issue is the occasional usb cable that doesn't work well. I don't mean that as a Mac is better than Windows thing. I use both and am not into these kinds of battles. But it is easier on Mac in this case.
OP, have you tried this with a different USB cable?

is your bootloader unlocked?

And I take it you've enabled Developer Options and USB Debugging?

After all my talk about the ease of communicating with Android devices from a Mac, I'm now unable to successfully issue fastboot commands when in the bootloader. I've tried using sudo, making sure to include arguments that address the device, etc. I can execute adb commands when the phone's system is booted, though. But fastboot commands either get me a "waiting for device" or nothing at all. I thought I was able to do this successfully yesterday, when I was just testing it out. Today, I was going to root by booting into TWRP and flashing SuperSU.

maigre said:
Is it a drivers issue? Does "adb devices" return anything? Or "fastboot devices" if you're in the bootloader? If you don't get a device listed after executing that command, the OS isn't fully recognizing the Icon 3.
I've all but abandoned using Windows for interaction with my Android devices. The driver issues are too big a pain in the butt. With Mac, and no need for installing drivers, the only issue is the occasional usb cable that doesn't work well. I don't mean that as a Mac is better than Windows thing. I use both and am not into these kinds of battles. But it is easier on Mac in this case.
OP, have you tried this with a different USB cable?
Click to expand...
Click to collapse
If it was a driver issue, my phone would not restart with the command, every drivers are OK

ractar28 said:
POThe only thing I can suggest is to change the line
fastboot -i 0x1bbb boot boot.img
to (in your specific case)
c:\users\user\desktop\idol3_6045_root\fastboot -i 0x1bbb boot c:\users\user\desktop\idol3_6045_root\boot.img
and see what occurs.
I'm thinking you may have fastboot somewhere else on your computer as well and that somehow, it's looking in the local directory of that fastboot. While that goes against everything logical (local directory should always be checked first), I'd give that a shot.
If that still doesn't work, open the cmd.exe with elevated permissions (right click "command prompt" in start menu, and run as administrator)
Click to expand...
Click to collapse
Your method worked !!!!!!!!!!!!!!! THX !!!!!

Windows cannot detect that the phone is in fastboot mode

Hey bros. This might sound like a noob question but I just cannot get the phone to show up in command prompt. I booted the thing into fastboot, I have all of them adb goodies installed (alright not all of them, only the minimal installation) and I also have the Nokia driver installed but the thing simply refuses to show up. I type "fastboot devices" and I just get another line of text. Interestingly enough though I did manage to unlock the bootloader, even though when I typed "fastboot devices" I got nothing, just like the first time. When I try to flash TWRP I get the legendary "<waiting for device>" message. Although like I was saying, unlocking the bootloader worked just fine, which is strange

Brilliant99 said:
Hey bros. This might sound like a noob question but I just cannot get the phone to show up in command prompt. I booted the thing into fastboot, I have all of them adb goodies installed (alright not all of them, only the minimal installation) and I also have the Nokia driver installed but the thing simply refuses to show up. I type "fastboot devices" and I just get another line of text. Interestingly enough though I did manage to unlock the bootloader, even though when I typed "fastboot devices" I got nothing, just like the first time.
Click to expand...
Click to collapse
i think it's ok, it doesn't matter if other adb and fastboot commands work properly.

SkaboXD said:
i think it's ok, it doesn't matter if other adb and fastboot commands work properly.
Click to expand...
Click to collapse
Problem is, when I try to flash TWRP I get the legendary "<waiting for device>"

Brilliant99 said:
Problem is, when I try to flash TWRP I get the legendary "<waiting for device>"
Click to expand...
Click to collapse
I am sorry I forgot to mention that in the main post. Let me edit it

Brilliant99 said:
Problem is, when I try to flash TWRP I get the legendary "<waiting for device>"
Click to expand...
Click to collapse
try to install other adb. I recommend to install platform-tools as it have only 5mb. If that doesn't work, try to reinatall Nokia 3 driver.

SkaboXD said:
try to install other adb. I recommend to install platform-tools as it have only 5mb. If that doesn't work, try to reinatall Nokia 3 driver.
Click to expand...
Click to collapse
I did all of that too and it still doesn't work. I have Windows 10 if that helps. I also have another computer on Windows 8.1

Brilliant99 said:
I did all of that too and it still doesn't work. I have Windows 10 if that helps. I also have another computer on Windows 8.1
Click to expand...
Click to collapse
I also have access to macOS, but I doubt it's any useful

Brilliant99 said:
I did all of that too and it still doesn't work. I have Windows 10 if that helps. I also have another computer on Windows 8.1
Click to expand...
Click to collapse
maybe a stupid question, but did you enable usb debugging and usb file transfer (mtp)?

SkaboXD said:
maybe a stupid question, but did you enable usb debugging and usb file transfer (mtp)?
Click to expand...
Click to collapse
I enabled those too
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

idk then, try on other system, I'm using Windows 7 and i never had problem with it.

Try this
fastboot.exe -i 0x2e04 [Your_Command]
i had same issued but it fixed after use that command

lordschleger said:
Try this
fastboot.exe -i 0x2e04 [Your_Command]
i had same issued but it fixed after use that command
Click to expand...
Click to collapse
Thank you , you saved me hours of problem solving

Is the Alcatel 9029W rootable?

I just got this tablet a few days ago so I was wondering if it was possible to root it as I already have a primary phone that I use.

Search the WEB for "root any MTK device"

jwoegerbauer said:
Search the WEB for "root any MTK device"
Click to expand...
Click to collapse
Will the method still work even though it's not a MTK device? On CPU-Z it says it's a ARM Cortex device.

ARM Cortex is a processor technology,, what in your case is used by MediaTek when they developed and produced the chipset for your phone.

That seems to make sense. I'll try the method when my laptop charges back up. Thanks for the help

jwoegerbauer said:
Search the WEB for "root any MTK device"
Click to expand...
Click to collapse
The method doesn't seem to work because after doing
adb reboot bootloader
The device just reboots and when I do
fastboot oem unlock, it gets stuck on waiting

What's the method you always are referring to?

jwoegerbauer said:
What's the method you always are referring to?
Click to expand...
Click to collapse
The mtk one you told me about

I was following this to be more specific

The steps to prepare programmatically unlocking a phone's bootloader by means of fastboot what most people do - me included - are
Code:
adb devices <- your phone must be listed here
adb shell "getprop ro.oem_unlock_supported" <- The return value must be 1, if not then don't proceed
adb reboot fastboot <- or: fastboot reboot bootloader
fastboot devices <- your phone must be listed here
to verify the phone is succesfully connected and acting in fastboot ( aka bootloader ) mode.
If phone isn't shown then a fastboot connection doesn't got established.

adb devices - works
adb shell "getprop ro.oem_unlock_supported" - I get a 1
adb reboot fastboot - device just reboots normally
fastboot reboot bootloader - says <waiting for any device>
fastboot devices - just shows a empty line of text

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You simply confirmed that fastboot isn't working.
Hints:
1. Install its latest version ( -> see my signature )
2. Additionally install the "Android USB Driver" suitable to your phone: with regards to some phones this driver is also needed to make fastboot working - may be your phone is one of these.

jwoegerbauer said:
You simply confirmed that fastboot isn't working.
Hints:
1. Install its latest version ( -> see my signature )
2. Additionally install the "Android USB Driver" suitable to your phone: with regards to some phones this driver is also needed to make fastboot working - may be your phone is one of these.
Click to expand...
Click to collapse
I've finished doing 1 and 2. Do I retry going into fastboot again?

Oskii said:
I've finished doing 1 and 2. Do I retry going into fastboot again?
Click to expand...
Click to collapse
Do what you think is right ...

It seems that the device is still unable to go into fastboot mode.

I will double check to make sure

In @Oskii 's defense, I've had some Alcatel devices that somehow seemed to have fastboot disabled (namely the Alcatel 1 / Orange Rise 54, IIRC), I don't know how though. It's just impossible to boot into any bootloader/fastboot mode (or at least I never found out how).
I *did* manage to (sort of) root them using a method I don't remember (sorry ; it was an obscure app), but it was unreliable : root wouldn't always "get applied/stick" after boot and I had to reboot and cross my fingers to make it work again.
I know it's not of much help, but still…

It's still not working :v

It cannot without booting to fastboot mode.