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] TWRP Stuck in Recovery Bootloop

Hey guys, got myself in bit of a bind. I just recently rooted using the 1 click tool and also installed CWM with it. Later, I tried to install TWRP through goomanager on top of that. It rebooted to recovery, and the recovery seems to not have installed properly. It just stays stuck at the TEAMWIN screen and flashes. Even after powering it off and back on, it goes straight to the teamwin screen. The only way for it to boot properly is to voldown+power and then let it cold boot.
So, I tried installing TWRP 2.5.0.0 over that, but instead of rebooting properly (after I follow the instructions from the twrp website) it reboots straight into the recovery still.
I tried using the 1 click tool to try to reinstall CWM, but now it no longer works. The command prompt just disappears after the driver installation part. After that, I tried easy flasher. Wasn't able to install Rogue or TWRP. They state that they have been installed correctly, but when I boot up the tablet it goes straight to the teamwin screen and stays stuck there.
Anyone else have any ideas? I honestly feel like I've tried everything. I haven't tried wiping it yet, but only because I don't feel safe wiping it without a recovery installed.

Using EasyFlasher, did you see any text on the screen? If not, it did not install.
Also, do you know how to use ADB?
If so, run try this:
Plug tablet to PC via USB
After the device was detected, Settings - Developer Options - Debugging (tick the box).
It should install new hardware and show 2 devices, an MTP and an ADB device.
Update the driver in the Device Manager on the windows machine to the Naked Drivers
Once that is updated, I downloaded ADB from the Android SDK. You really only need three files, available here: https://www.dropbox.com/s/h61zwmzaynouc1k/adb.zip
Unzip these files to a folder called c:\adb
Open a command prompt and type the following:
Code:
c:
cd c:\adb
adb devices
It should show a device connected. It may error out when restarting the daemon, but keep trying and see if it can find your tablet.
If you cannot get the ADB driver installed or updated, my guess is that you have a bad USB cable. Yes, it IS possible to have a bad cable for data transfer that STILL charges your tablet. I have even had that happen to me.
If you got this far, then here is what to do next:
Download your favorite recovery. I strongly recommend TWRP. The latest official release is here: http://techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob
Save this at c:\adb\TWRP.blob. You can use a different recovery method if you have the blob file (such as CWM) but TWRP is far superior unless you are looking to install Android Revolution HD.
Code:
adb push TWRP.blob /sdcard/
adb shell
dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4
Wait until you see it succesfully transfer data.
Then:
Code:
adb reboot
exit
Once it reboots, you should see a progress bar at the ASUS screen. Once this completes you will have TWRP (or some other custom recovery installed)

With easyflasher I just hit flash and it says it worked correctly. Nothing appears on the tablet or anything.
I'm a newbie at adb, but I spent mostly all of yesterday learning it. After looking at your guide, I can say I was doing everything correct yesterday. I followed these same steps and still was sent back to the teamwin flashing screen after the reboot. There was no loading bar asus screen. I'm not sure what the problem is. Adb is working fine, it recognizes the device, it pushes the TWRP.blob, it goes through all the commands without error. Should I not be in a cold boot when entering this? Should I be in APX mode?
{
"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 wasn't able to get it working with your adb download however, I'm using the adb provided with the SDK manager. Not sure if that makes a difference. And could it be my drivers? I believe I installed the asus sync for my drivers, so when trying to update to naked drivers it just says it's already up to date. Also, I really appreciate the guide you wrote up, it really helped me cement that I'm doing everything right.

Very very weird.... I just fixed it, I think. I guess my drivers were bad, because I was able to update them to the naked drivers when in APX mode. Then I was able to use easy flash to reflash rogueCWM. After rebooting however, TWRP 2.5.0.0 was installed! Very very weird.

Can recover data/restore factory rom via adb/fastboot/PC only (w bootloader locked)?

in brief:
the data should be there on the phone, so there's hope it should be easier to recover than deleted data but i run out of ideas how to get adb to find and pull it... maybe a more advanced user has better knowledge (better commands or tools)
adb devices and fastboot devices communicate with phone, so i have all drivers installed, i can only tackle with it via usb from windows 7 based computer
the detailed story:
i have a huawei g620s-L01, stuck in bootloop (just loading huawei logo forever or until battery empty but does not restart) and also "volume down" button does nothing... the bootloader is locked and huawei seems to have stopped providing unlock codes...the touch works but is shattered so i was told repair the button is not an option...
i can boot it into recovery mode using "volume up + power" but i can't use the recovery menu due to the dead "volume down"
from recovery menu i can only "reboot system now" but that re-enters the bootloop,
also i get bootloop if i try to boot into download mode via adb command
i can use some adb commands (i say some because some return errors, others say i don't have permissions)
i can boot into fastboot via adb command too...i can not find my dcim folder or any data folder to use the pull commnad, i tried the generic commands to pull sdcrd or dcim or all files with *.jpg
the user data is not accesible, i could browse some system directories but they did not contain my files via cd commands
i found some threads saying maybe i need mount or root commands
but trying to mount partitions or access su via adb also gives errors
su is not found, i do remember there was a su when android was working on the devices but is useless if i can't find/access it
i found the factory rom and some tools to try to restore rom to the phone due to claims that same rom might find my data, but the tools failed to start due to locked bootloader
i also tried several versions of full android sdk (old and new) trying to find "monitor or file browser" tools but the menu is not there...perhaps it will not activate those tools when device is in fastboot/recovery modes
{
"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 also found a 3rd party full android browser but can't connect with it either
also recovery softs are useless, they need a working android to try to recover anything...some recovery softs claimed they can fix bootloop but don't support my device
free tools that try to unlock bootloader also failed
so at this point i am running out of things to try

this is what i figured so far: i can see my data but can't touch it
i seem to have 4 partitions on the device:
1 is called sdcard but has nothing accesible on it, could be the feature for external card
2 is called ext , total size is 711,49mb , used 124,98 and available 586,5
3 is called system , total size 1,64 gb, used 1,23gb, available 418,1mb
4 is called data, total size 3,96gb, used 3,75gb, available 218,16mb
clearly the data partition is still keeping my data
i can not see my installed apps, so i guess they are also on that partition
i can see some system apps, namely 49 out of 146
so i'm guessing the issue is with one application, likely system app since i can't see them all
the phone may be partly rooted, the android may have some rooted features but the adb on it is not rooted
so i can not use the adb root command to get to my data
and i can not try to flash recovery or rom or custom boot img from adb due to bootloader locked and asking for unknown code

"Alcatel A30 Fierce" ROOTED/On-Going

Hello, I'm new to this- all of it, I've only just recently got into rooting and such things, but I'm progressing and that's what matters, no?
Anyway, I've successfully managed to root this phone via Magisk, that no one probably cares for anymore through trial and error and I'll do my very best to explain my method, and give updates as this is very on-going, there are certain issues and things I need to work out, but I appreciate any help, pointers, and such as before mentioned, I am new.
{
"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"
}
ALCATEL A30 FIERCE - Specs, and Specifications.
This phone was released in August, 2017.
Display - 5.5inches, 1280 x 720
Camera - 13 MP (Single Camera)
Hardware - MediaTek, 2GB RAM
Storage - 32GB, microSDXC
Battery - 3000mAh
OS - Android 7.0 Nougat
My own notes about this device.
Lots of MetroPCS Bloatware, can be a bit janky, but it's manageable.
It does not have a traditionally accessed Bootloader, no "adb reboot bootloader", this command just restarts the device to system.
Fastboot is odd, I managed to access Fastboot by some way I don't entirely understand, I'll go about what I did to get there later on in this post and try to recreate it later on as this post updates.
This device has colour states (if that's commonology), meaning, once the Bootloader is "unlocked", you will get an "Orange State" message before starting your phone that gets in the way of some things, I have yet to fix this, but I imagine we will if this gains traction, there will be a quicker fix!
No TWRP yet, as of posting, flashing a ported twrp.img through MTK_TWRP, or the TWRP_Port has not worked, and after flashing, neither will flashing the stock recovery but I've a quickfire way of getting around to fix this, if I can.
MTKCLIENT - https://github.com/bkerler/mtkclient
My Process, in the system, press the build number seven times to enable developer options - enable OEM Unlocking.
Then enable USB Debugging, and make sure you've installed adb and fastboot, as well as the correct drivers.
Through that link, follow the instructions specific to your operating system (I use POP OS and WINDOWS 11, YOU DON'T HAVE TO USE THE SAME AS ME), you may use the mtkclient_gui for an easier experience.
To unlock the bootloader, which will trigger "Orange State", open your terminal in the directory of the mtkclient and run python "mtk e metadata,userdata,md_udc", then, with your powered off device, and it will say something along the lines of "Preloader - Waiting for Device", with your USB Cable, and your wits about you, hold the volume down button (if this doesn't work for you, hold both volume buttons in" and plug your device into your PC with that command running. If the command completes, then run "python mtk da seccfg unlock", and this will unlock your bootloader.
WARNING: Unlocking the bootloader wipes the data of your device!
After this, dump your boot vbmeta with the commands in the mtkclient instructions, if this does not work for you with python or python3, I will provide the required files below.
Then, power your device back up, and install the patched magisk-app and push it to your sd card through adb, or traditional file transfer.
If you have your boot.img, push it to your sd card and patch it with magisk, then retrieve it from your phone - this is where my tutorial and mtk's tutorial take a bit of a turn!
I had a problem with the "reconnecting to preloader" phase, as it would not go through, or an error labeled [Unpack Requires A Buffer Of 12 Bytes] would crop up which prevented me from flashing the required files through "python mtk w boot,vbmeta boot.patched,vbmeta.img.empty". Let's go through some cautionary steps, what I did to achieve perma-root.
Create a funny-named file in the mtkclient directory labeled "DUMPY", do "python/python3 mtk_gui" and connect your powered off phone through the previously mentioned volume holding until it connects you in BROM mode. Under "read partitions", select all partitions, then "read partitions" and make sure the output is that "DUMPY" folder. This process will take awhile!
Once it finishes, rename your patched magisk-boot from [magisk.img name] to "boot.patched.bin" and under "write partitions", select the boot partition and write the boot.patched.bin to the boot partition! Once finished, start your device and install a root checker! It should be working!
If there are any errors, I will do my best to try and help you but keep in mind, I am very new to this, I hope it works for you too!

Question Graphene OS - switch back to Google OS

I tried Graphene OS for the past week and decided to go back to original.
- bootloader is unlocked
- am using Android Flash TOOL from here https://flash.android.com/
- Removed non-stock key prior to proceeding with Flashing
- i got to FastBoot screen during the Flash and the browser provided the following warning : '' Your device is being used by another program'' and then the Flasing process stopped.
- Am now back at the main Google screen.
- I believe Graphene OS already removed from device.
- Trying to initialize Android Flash TOOL once again, i accept ADB / Grant access to ADB keys - device does not show up in the tool anymore to flash stock OS. (see attached screenshot)
When I'm stuck at the main Google screen, I decided to factory reset.
Turned device off > Pressed Volume down > highlight “Recovery mode.” > “Wipe data/factory reset” > After reset completed, pressed the Power button to select “Reboot system now.”
{
"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"
}

Add new device ???? nothing ?.
What I always did with Google phones (family and friends who brought them to me to flash):
With the original ROM and before any manipulation
-go to developer mode + USB debugging + unlock bootloader.
-in fastboot, fastboot flashing unlock, reboot then reconfig of the phone.
-switch back to developer mode + USB debugging + USB connection to PC.
-adb reboot bootloader then adb kill-server (on the PC).
-connect to Android Flash Tool then do as if I was going to flash the original Rom (to make the phone recognized by Google) and stop the process before flashing.
I don't know if it's really useful to do all this but recently with 2 phones (Google 4A5G and Google 5 under GrapheneOS) putted back the ROM from Google before re-flashing on the 2 CalyxOS (support planned until January 2025) without any problem.
Last possibility for you, download the ROM factory, unzip it and launch the flash-all.bat in fastboot.

Tintin62 said:
Add new device ???? nothing ?.
What I always did with Google phones (family and friends who brought them to me to flash):
With the original ROM and before any manipulation
-go to developer mode + USB debugging + unlock bootloader.....
Click to expand...
Click to collapse
@yycDAAN This is the best solution: doing this stuff manually and not using a tool/site to automate things =).
But anyway, ensure that you have USB Debugging enabled. If you don't, then no image flashing will work manually or through sites that tackle it all for you - as they won't be able to detect the device (which appears to be your current problem).

Thank you guys for taking the time to help - much appreciate it
got into Fastboot mode. Android Flash TOOL recognized device and was able to install the original OS . When i restart phone, get the warning page :
''Your device is corrupt. It can't be trusted and may not work properly'' . I click CONTINUE and everything loads normally.
Is there anything I can do to ensure that ''Your device is corrupt.'' page stop showing up on Boot ?
EDIT : appears once bootloader is Locked, screen disappears
Leaving Thread up for reference.