I'm trying to figure out a way to make a few edits to my system partition without unlocking my bootloader (no TWRP available anyways) and I found a setting to enable ADB in the STOCK Recovery.
I've been able to use it to sideload an app, but was wondering how to install an app to the system partition... without having to push the entire partition PLUS the added app....
does anyone know actual SPECIFICS about the boot options on the bootloader menu? I have managed to get stuck in some strange developer mode twice now, and am actually getting a little worried I'll royally mess this up.
One developer mode I booted into never loaded SystemUI- lock screen loaded the picture, never got any text (after 20mins waiting). Held power for a minute, device booted back into the bootloader menu.
the other developer mode I toggled somehow turned all my radios off on boot, turned them on one by one, notification CQOA or similar was starting up. Then a bunch of information in a text mode style flew across the screen on top of my desktop. Again, I held power down and got the heck outta there. I had to go back into bootloader menu and select Recovery and hit VolUp and Power to get a usable menu and then recovered from there.
all this exploring just has me curious as all hell what is possible through these menus. If I had another G7Power, I would be going as far down this rabbit hole as possible... but this is my only device at this time, so I am quite concerned I'll manage to break something and not recover....
at one point, using ADB in Recovery, I was able to get my ADB shell in root mode.... but I didn't realize the # meant root worked. And I haven't been able to get that working like that again.
EDIT: I still have the CMD window open from Friday night when I started this, otherwise I wouldn't have ever realized I had root for a few minutes in ADB
END EDIT
I want to make a few edits to build.prop without having to flash the whole partition.
My bootloader is LOCKED.
I literally just had an OTA last weekend.
am I being trolled by Moto on this? like, it looks like it is doing stuff, or COULD do stuff, but is actually nerfed? It seems like there has to be a secret key combo or something to get these menus to actually work.... it also looks like it is possible to switch to USERDEBUG if only for a single boot.
Any ideas are appreciated!
Dead_Dude said:
I'm trying to figure out a way to make a few edits to my system partition without unlocking my bootloader (no TWRP available anyways) and I found a setting to enable ADB in the STOCK Recovery.
I've been able to use it to sideload an app, but was wondering how to install an app to the system partition... without having to push the entire partition PLUS the added app....
does anyone know actual SPECIFICS about the boot options on the bootloader menu? I have managed to get stuck in some strange developer mode twice now, and am actually getting a little worried I'll royally mess this up.
One developer mode I booted into never loaded SystemUI- lock screen loaded the picture, never got any text (after 20mins waiting). Held power for a minute, device booted back into the bootloader menu.
the other developer mode I toggled somehow turned all my radios off on boot, turned them on one by one, notification CQOA or similar was starting up. Then a bunch of information in a text mode style flew across the screen on top of my desktop. Again, I held power down and got the heck outta there. I had to go back into bootloader menu and select Recovery and hit VolUp and Power to get a usable menu and then recovered from there.
all this exploring just has me curious as all hell what is possible through these menus. If I had another G7Power, I would be going as far down this rabbit hole as possible... but this is my only device at this time, so I am quite concerned I'll manage to break something and not recover....
at one point, using ADB in Recovery, I was able to get my ADB shell in root mode.... but I didn't realize the # meant root worked. And I haven't been able to get that working like that again.
EDIT: I still have the CMD window open from Friday night when I started this, otherwise I wouldn't have ever realized I had root for a few minutes in ADB
END EDIT
I want to make a few edits to build.prop without having to flash the whole partition.
My bootloader is LOCKED.
I literally just had an OTA last weekend.
am I being trolled by Moto on this? like, it looks like it is doing stuff, or COULD do stuff, but is actually nerfed? It seems like there has to be a secret key combo or something to get these menus to actually work.... it also looks like it is possible to switch to USERDEBUG if only for a single boot.
Any ideas are appreciated!
Click to expand...
Click to collapse
This is NOT the Q&A thread
fubugang said:
This is NOT the Q&A thread
Click to expand...
Click to collapse
I never said it was.
These menus appear to be useful for gaining access to various things. If a good source posted a response "these menus have already been scoured for any usefulness for people like us" I would leave it alone.
If I *was* to share my own experiences with what those various items can do, would you say this isn't the place to post that information? Please clarify- I honestly don't want to post on the wrong sub. Thank you.
Dead_Dude said:
I never said it was.
These menus appear to be useful for gaining access to various things. If a good source posted a response "these menus have already been scoured for any usefulness for people like us" I would leave it alone.
If I *was* to share my own experiences with what those various items can do, would you say this isn't the place to post that information? Please clarify- I honestly don't want to post on the wrong sub. Thank you.
Click to expand...
Click to collapse
As per the thread title: This thread is for development purposes only. All questions should should be asked in the Q&A thread
I dunno but I can tell you the SUPRA from cricket does not support bootloader unlock or root right now, and probably never will, I bought one but i will probably sell it off or gift it and buy the Power or G7 Plus with the money typically with moto you just go to the motorola bootloader unlock page enter your fastboot and type oem get_unlock_code or whatever it gives you a string you put it together and paste that in the moto bootloader page and they provide an unlocked bootloader boot.img you do get the code however when you put it in it gives you message that the phone cannot be unlocked thanks alot cricket, and Att I dont mind your service here but I want to be able to flash custom roms so I will just order a moto from swappa or straight from moto so i can do what I want with the phone, considering these are prepaid and you buy them out right it should not even be legal to keep the locked really, wish some attorney that had this stuff as a hobby would help us out it is flat out wrong to tell me I cannot unlock my bootloader its not like I owe anything on the phone thru cricket in the first place its paid for in full.
Related
Hello,
I am posting in this forum for a few reasons.
First of all, I rooted my phone the day I bought it and took it home. I originally rooted it with a simple one-click method from a webpage I randomly found online.
Unfortunately, I do not remember the name of the hack, and I'm beginning to think that it has permanently affected the boot for my phone. After installing the hack, I found the CynoagenMod (or however it is spelled) custom ROM. I took some time into researching more about custom ROMs and installing with advanced settings, etc.
After I did my research, I found it best to flash with the new ROM and have had trouble with my boot since.
I did everything step by step from the website, and ran everything to the best of my abilities. The problem I am having now is that I can not access the HBoot menu.
In fact, every time I restart or shut off my phone, the screen goes black and will not respond to me holding down the recovery mode buttons. It stays pitch black and even battery resetting does nothing.
It will randomly turn on, vibrating for about a minute or two straight with the HTC splash screen, and then boot into my phone with the current ROM.
It seems strange that this is going on, and I have been searching all over the internet for weeks now trying to figure out what's wrong. I have reinstalled the stock RUU for my Inspire multiple times to no avail. It still sits at a black screen and will randomly boot into the splash whenever it deems to do so.
Is there anyone with any suggestions or advanced technical knowledge that could lead me to a solution? It is most unfortunate because I can't access for viewing s-on, s-off. I'm really debating whether to take the phone back to the rep and replace it. I'm just afraid they will discover the security off and tell me to suck a ****.
Thanks.
Run this nice little tool to factory reset, s-on your device
http://forum.xda-developers.com/showthread.php?t=1208507
Then reroot with the Hack Kit here. Read the "effen manual"
http://forum.xda-developers.com/showthread.php?t=952352
Thanks for the reply.
But here's my problem:
I can't access the HBoot menu in order to flash or install any type of file.
I've been using the terminal on my Mac to do most of my editing, and now I've ran in to a new problem: whenever I try to move files to my sd root, it says that the card is read only and therefore no files can be transferred to it.
I use the command ./adb push PD98IMG.zip /sdcard/
This is where I get the error.
Also, it takes my phone literally 5 or 6 minutes to boot into the splash screen after I use the command ./adb reboot bootloader/recovery (both of which I have tried).
I'm beginning to get quite frustrated, as I'm sure you can understand. I've also attempted to rewrite all of the necessary root programs onto the device in hope that the bootloader and recovery options will be accessible.
Do you have a solution for the write problem I am getting from my device?
Thanks.
Also, is there a way to go about doing this procedure straight from the Terminal since I can't run HBoot and recovery directly from my phone?
I have sucessfully restored s-on on my previous inspire so I can rma it for a signal issue I was having.
So I consider myself savy enough on this task. I rooted that inspire using a method available on here and not some random site. Doing that, u accept the possiblility that you may not get support on xda for using a root method that was not posted here. However, I do remember reading somewhere on here that certain inspires will go to a black screen at somewhere during the rooting process. My advice is to search the inspire threads for this topic, using keywords black screen, and see if this can provide a solution for you.
Sent from my HTC Inspire 4G using XDA App
Thanks soldier, but I've already searched through every black screen forum topic on this site for the inspire, all of which require reboot to HBoot, which I can not access from my phone without terminal access.
It seems like my phone is permanently soft bricked or something, or maybe the key commands don't do as they are supposed to. I can never get into the HBoot menu or recovery by holding down vol. - and the power button.
All it does is boots into the splash screen after about five minutes or son, and once the splash screen comes up, the phone vibrates for about 2 minutes straight.
During this time, my phone is not recognized by adp until after the phone stops vibrating.
I can't seem to find any forums ANYWHERE that propose a solution to this problem, let alone anyone that has the same issue as me.
Yeah that sux man. Well I would say, if you are within your warranty exchange, I would go that route first. Worst thing they can say is no. Although I still have yet to find a story about how someone was denied a warranty exchange for a phone that does not have physical damage. The next route is to suck it up and pay the deductible if you have insurance on it. (I always recommend insurance on any modern touchscreen smartphone) If that is not an option, then start saving up for a new phone, and lesson learned.
Ya, that seems like the only available option at the moment since my phone can't access HBoot even though I rewrote the root files to the device.
I just bought the phone this weekend, so I'm thinking of hard bricking the phone in case they decide to do an on-the-spot check. Hopefully they'll believe some bull**** story I can come up with and just give me a replacement.
Would any of you still recommend rooting again with a new phone? And what would be the best way to do so without the consequence of a soft or hard brick?
I'm just thinking of rooting and keeping the original stock OS on the device instead of running a custom ROM. That's what seems to have effed my phone.
All I really wanted to do was cut all the crappy useless programs and services out of the original Google Apps package with a fresh install to get the most out of my hardware.
FYI...if you haven't figured it by now, xda is the BEST site there is for android hacking/modding. This website IS the centralized location for all android developers/modders. Sure there are plenty of other android community sites out there, but this is the direct centralized source for all android hacking/modding.
My suggestion is to go ahead and root the next inspire you get using the hack kit in the development section. That is a long time proven and supported rooting method for the inspire. As far as roms go, from what you are saying, i would recommend you install a custom rom that is based on stock. (ex. Android Revolution) It was not the custom rom that effed up your phone, it was the questionable rooting method that did. Custom roms, by default, are superior to true stock roms, because they are modded, tweaked, and optimized far beyond the stock rom.
Awesome, I appreciate the information.
I'll keep that in mind. So which exact ROM would you suggest for my Inspire that's completely like Gingerbread?
I wasn't too fond of the CyanogenMod ROM because the GUI was a little sketchy. I like having a professional looking GUI, and I love the Gingerbread screens and menus.
Oh, one more thing. I had some success a little while ago getting into the HBoot menu from the terminal. Now I'm having a new issue:
I get into the menu at which the phone freezes and I can not use the arrow keys or power button to make a selection. Any tips?
I also believe that it is in fastboot, since it says fastboot at the top and has the Androids on the bottom skateboarding. Is this an issue? And am I screwed because I can't access the OS to turn the option off?
When you see the fastboot at the top of the screen and the androids skating at the bottom, that is perfectly normal. That is the pre screen before actually going into the bootloader. If your keys work, u press the volume down button to select which option you want, which will highlight in blue. The first option is the bootloader, so if you press the power button, it will load into the bootloader. The bootloader looks exactly the same as this screen, but with different options. This screen will show hboot at the top and have the options of fastboot, recovery, factory reset, simlock, and image crc. I have never heard of the keys not working at this point, so i couldn't help you there. Search around the forums if you haven't already.
If you want to compare this to something more familiar, think of these two screens as your motherboard bios to your PC. (What you see when your pc boots up, before it loads the OS, windows, mac, etc) On a pc, you can install any OS you want, like on the inspire, you can install any custom rom you want. But the motherboard bios is the highest level of permanent software that is directly written to the motherboard itself, like the bootloader/hboot is on the inspire. When rooting, you are essentially altering the motherboard bios on the inspire. When you install a custom rom, you are just installing an OS on the inspire.
There are plenty of custom ROMS that are based off of stock in the development section. I use and like Android Revolution. But when choosing custom roms, its always a matter of preference, and what works best for you.
digitalism said:
Thanks for the reply.
But here's my problem:
I can't access the HBoot menu in order to flash or install any type of file.
I've been using the terminal on my Mac to do most of my editing, and now I've ran in to a new problem: whenever I try to move files to my sd root, it says that the card is read only and therefore no files can be transferred to it.
I use the command ./adb push PD98IMG.zip /sdcard/
This is where I get the error.
Also, it takes my phone literally 5 or 6 minutes to boot into the splash screen after I use the command ./adb reboot bootloader/recovery (both of which I have tried).
I'm beginning to get quite frustrated, as I'm sure you can understand. I've also attempted to rewrite all of the necessary root programs onto the device in hope that the bootloader and recovery options will be accessible.
Do you have a solution for the write problem I am getting from my device?
Thanks.
Click to expand...
Click to collapse
It sounds like you may have the bad combination of a newer Inspire and the older ENG hboot. This is a problem dealt with commonly on the Aria/Inspire IRC channel. If you want to jump in, we can probably get you straightened out.
http://webchat.freenode.net/?channels=#liberatedAria
Awesome.
I am a little upset that I can't choose an action from the boot menu with the keys on the phone.
It also seems that the only way I can completely get into the boot menu is through the terminal after which I run ./fastboot-mac
After I put in this action, the menu will begin looking for the PD98IMG.zip file, and only goes on to say that there is no file, when there actually is one.
I just wish I could do all of this straight from the phone since I'm not well versed on terminal and commands for running programs to their full ability.
I wish I could figure out a way to the write permission on my sdcard so I could reinstall the .zip file for the bootloader to find.
digitalism said:
Awesome.
I am a little upset that I can't choose an action from the boot menu with the keys on the phone.
It also seems that the only way I can completely get into the boot menu is through the terminal after which I run ./fastboot-mac
After I put in this action, the menu will begin looking for the PD98IMG.zip file, and only goes on to say that there is no file, when there actually is one.
I just wish I could do all of this straight from the phone since I'm not well versed on terminal and commands for running programs to their full ability.
I wish I could figure out a way to the write permission on my sdcard so I could reinstall the .zip file for the bootloader to find.
Click to expand...
Click to collapse
You will not be able to use the volume rocker to select options if you have a PD98IMG.zip on your SD card.
Try booting into hboot with the SD card removed. That should let you move around the menu.
Sent from my Inspire 4G using the power of the dark side
Thanks for the heads up!
I can move the menus now.
Seems like all is going well now...
Just a matter of time.
digitalism said:
Thanks for the heads up!
I can move the menus now.
Seems like all is going well now...
Just a matter of time.
Click to expand...
Click to collapse
It's good to hear you're moving forward. Let us know how it comes out.
Sent from my Inspire 4G using the power of the dark side
So i unlocked the bootloader and rooted the phone, and after that im stuck on boot and nothing seems to get it back to work.
When i use the restore function on the tool i get "fastboot" is not recognized as an internal or external or external command...
Help Please? got the phone like 20 mins ago and have not even use it (((
Will anyone be kind enough to help me? its not even funny :'(
first off... it generally might take a little bit to get a response to a thread, especially with almost no information provided. Expecting a reply within 17 minutes under such circumstances is expecting quite a lot.
Now... when you say "Stuck at boot"......... what? do you see anything on the screen? If so, what? Android on its back with a red triangle? Android standing with a thing spinning by its chest and a bar below it? Does it at least turn on at all? Need details.
And fastboot is only recognized if you actually have the phone in fastboot mode... i.e. holding power and "volume down" down when powering the device on.
elementaldragon said:
first off... it generally might take a little bit to get a response to a thread, especially with almost no information provided. Expecting a reply within 17 minutes under such circumstances is expecting quite a lot.
Now... when you say "Stuck at boot"......... what? do you see anything on the screen? If so, what? Android on its back with a red triangle? Android standing with a thing spinning by its chest and a bar below it? Does it at least turn on at all? Need details.
And fastboot is only recognized if you actually have the phone in fastboot mode... i.e. holding power and "volume down" down when powering the device on.
Click to expand...
Click to collapse
The phone turns on, and it gets stuck on the boot where the circles are spinning, if I go to fastboot the android is laying down with the chest open and blue inside.
Where im stuck is at the spinning nexus logo.... :'(
I'm starting to get the feeling that you may have jumped the gun on modding your phone... ESPECIALLY unlocking the bootloader. Probably why a lot of people suggest going the manual route for things rather than relying on a tool to make it just a series of keystrokes. Less likely to potentially miss a step if you're constantly reading what has to be done next, rather than just typing number and/or hitting the Enter key.
After unlocking the bootloader, did the phone reboot, and did you see the one thing i mentioned on the screen, the android standing with his chest open and the thing spinning in front of it, with the tiny progress bar of sorts below him?
elementaldragon said:
I'm starting to get the feeling that you may have jumped the gun on modding your phone... ESPECIALLY unlocking the bootloader. Probably why a lot of people suggest going the manual route for things rather than relying on a tool to make it just a series of keystrokes. Less likely to potentially miss a step if you're constantly reading what has to be done next, rather than just typing number and/or hitting the Enter key.
After unlocking the bootloader, did the phone reboot, and did you see the one thing i mentioned on the screen, the android standing with his chest open and the thing spinning in front of it, with the tiny progress bar of sorts below him?
Click to expand...
Click to collapse
I dont believe i saw that :/
Im trying to flash factory image now.
:/
http://www.xda-developers.com/android/how-to-root-and-unlock-the-google-nexus-5-xda-developer-tv/
May want to watch the video there. The thing i speak of is at the 4:20 mark. When the bootloader is unlocked, a factory reset is automatically performed by the phone. If you're seeing the android on his back, with the blue lights inside, and text above and below him, chances are that's fastboot mode... but it could be something different that you're talking about.
It's getting quite late, and i have to get some sleep. Hopefully someone else might be able to pick this up from here...
elementaldragon said:
http://www.xda-developers.com/android/how-to-root-and-unlock-the-google-nexus-5-xda-developer-tv/
May want to watch the video there. The thing i speak of is at the 4:20 mark. When the bootloader is unlocked, a factory reset is automatically performed by the phone. If you're seeing the android on his back, with the blue lights inside, and text above and below him, chances are that's fastboot mode... but it could be something different that you're talking about.
It's getting quite late, and i have to get some sleep. Hopefully someone else might be able to pick this up from here...
Click to expand...
Click to collapse
Yes y did saw that, my problem is that when i try to do anything i get this "fastboot" is not recognized as an internal or external or external command
I had the same problem. Jumped the gun from unlocking the bootloader to immediately installing TWRP without a reboot. I was stuck in a boot loop for hours. Power down the phone by holding in the power button. Boot into the bootloader by holding down volume and the power button. From here you can use fastboot. I wiped the data and cache. "fastboot erase userdata" and "fastboot erase cache".
The error you mention above with fastboot is your computer not finding the path to fastboot. On linux, browse to the directory fastboot is in and use ./fastboot erase userdata
Once the data and cache were cleared I could boot just fine.
http://forum.xda-developers.com/showthread.php?t=2512534
Sent from my Nexus 5 using Tapatalk
orphan22 said:
Yes y did saw that, my problem is that when i try to do anything i get this "fastboot" is not recognized as an internal or external or external command
Click to expand...
Click to collapse
It seems you didn't install Fastboot on your computer... Check the requirements.
Good evening to all. I am a complete novice, but hopefully someone can instruct me on how to get my tablet operational again. I have the LTE that was re-called, but I would like to have it rooted. When I power it on, it takes me to the lock screen then shuts down. I can still hear notifications for incoming emails and had been able to get it to developer options but was unsuccessful at getting any further.
Now, I must have read something a long time ago about holding down the power button and the volume button because I am bringing up the following information:
version number
bootloader version
device-locked
serial number
continue
fastboot protocol
recovery mode
reboot
poweroff
From this menu, is there any way to get the tablet functioning again AND root it? So far, I have put nomoreota, SUPERSu, and the recovery image on my sd card, but none of this shows up due to the tablet shutting down so quickly. Even selecting Fastboot Protocol does nothing to bring me to a point where I can slightly begin to make changes.
Since it still allows me to see a glimpse of my wallpaper, I am encouraged just a little, but if it is too little too late, please someone break it down to me so I decide whether to pursue this any longer.
Props to Cedric1127 & Keithn for their support thus far.
I would grab the factory images and restore it to stock. Here is a starting point. Also if it is a recalled tablet it may have an ota waiting for it to kill the bootloader. So look in the killswitch thread and don't boot the tablet until you have an idea of what's going on or it may take the ota before you can deal with it.
http://forum.xda-developers.com/shield-tablet/general/stock-recovery-images-ota-library-guides-t2988881
Good morning, Keithn. Please pardon me for the delaying in replying, but Thanks!!!!!
I accidentally made two posts one here
http://forum.xda-developers.com/general/xda-assist/urgent-pls-motoe-1st-gen-screen-stuck-t3407572
and the other here
http://forum.xda-developers.com/moto-e/help/love-help-urgently-pls-rely-phone-t3407607
Both posts ask the same questions. but are in the wrong place so can be deleted if in wrong place, my apologies.
I need my phone for alarms to remind me when to take my various meds.
My screen is stuck in bootloader unlocked scren and i cannot switch it off. No access to settings
Somehow i managed to get it into twrp screen but I dont know how I did it, and i didnt know which option to choose after swiping, so screen went back to 'bootloader unlocked scren'
I got back in again to twrp screen but dunno how, and chose reboot, but screen just went totally black, but still on if you know what I mean.
I cannot seem to get it back into twrp screen
I an very tech naiive and routed my phone to get rid of bloatware by watching some very comprehensive indian guys videos.
I cannot understand all the jargon.
I also downloaded 'unlocked bootloader warning fix' but it got stuck at cmd screen, kept saying 'waiting for device' and I didnt even know whether to plug the phone into the laptop or not.
Plus my battery runs out quick.
Dunno how i managed to get it back to TWRP, dont even understand TWRP, what option would I choose on TWRP to get me back into my phone as I rely on it heavily.
I use the alarms and reminders as I have bad adhd, and really need them, a paper diary doesnt cut it, I also need reminding when to take my meds, but without my phone i cant.
So, if anyone can help me get back into twrp then into my phone by teling me what to press I will be greatful. I dont have access to the settings as it is stuck on bootloader unlocked screen.
thanks in advance and remember your talking to a tech dummy who came here cos her screen is locked, lol and thanks for reading and your kind help in advance.
two people also asked on here http://forum.xda-developers.com/moto...rning-t3169916 but no answers.
many thanks and sorry for the dupliate or similar posts.
Hello all, and thanks for having me:
I am here out of desperation. Other Android forums have been telling me that I need the correct RUU file, to get my HTC One X (Evita) back to factory preset(s). That's assuming it has already been wiped. I've been trying for over a month.
I am not, BY ANY STRETCH, knowledgeable in these kinds of smartphone problems. I know nothing about the various terminologies, nor what they represent, i.e. flashing, rooting, etc. I actually think that if some members here could possibly ask ME a couple questions, that that might be a faster way to try and get to the root of the problem, so to speak.
I can tell you that, as I type this, I DID manage to get the "BOOT"?? screen up. It has several commands or options, and three large bar codes at the bottom of that screen. I can also tell you that after I found out about holding down power and pressing volume down 3 times, and wait...my touch controls at the bottom of the phone, flash 15 times and stop. Much more often than not, if I continue to hold those buttons down, the HTC "Brilliant" logo pops up briefly, then disappears, but you can tell by looking closely, the screen isn't totally black, it is grey, still on, and will remain that way until the battery dies...unless I try to do something to turn it off.
Apologies for the long post. To me, this takes a more verbose explanation than it probably would those more "experienced" with the technological aspects involved in any attempt to "repair" the phone.
I need to add that, when the phone was purchased, it was bought for me, by my wife, for 1 penny, as part of an AT&T promotion. It has the AT&T logo molded into the top center of the phone, and that there are/were many AT&T apps in the phone. My wife told me long ago, that AT&T had the phone locked, and that their apps could not be removed.
We no longer use AT&T as our carrier. We use Consumer Cellular. To anyone with any expertise, advice, knowledge, etc., that could possibly aid in my restoring the phone back to what I refer to as "normal Android", I would be forever in your debt. I am disabled, and on a pittance of Social Security benefits. With prices of GOOD smartphones today, I seriously doubt I would ever be able to afford even a used one. Thanks very much. Again, my apologies for the "novel".
Its been a while since i have done an RUU as i dont own an HTC anymore but if you have access to a pc this might work.
Steps
1. Download the RUU for your device from here: http://www.htc.com/us/support/rom-downloads.html
2. Put the device into bootloader mode. (black screen with the android in the center has options for recovery, ect)
3. make sure drivers are set up on the PC and run RUU.
This "should" put you back to 100% factory settings and return the device to "out of the box" android. Again this is done at your own risk as i dont know for sure what state your device is in unless i can see it personally.
Hope this helps
Wolf
I have finally gotten to the previously mentioned "unnamed" screen. This screen has a much shorter menu. Please recall that at the top of the FIRST and only screen I was able to get said "HBOOT" at the top, above a list of various details such as the Evita name, Radio, openDSP,etc. At the top of this one, it says ***LOCKED***, above the like details mentioned.
There is then, in the center of the menu, a red highlighted "FASTBOOT AC" that cannot be selected for anything that I know of. Finally, the possible workable selections are, from top to bottom, read BOOTLOADER, REBOOT, REBOOT BOOTLOADER, and POWER DOWN.
If by "the Android" mentioned by SynisterWolf, she means the green robot icon(s), there are three of them on skateboards at the bottom of this screen. These observations are all that I know, with regard to the main issue at hand.
I have the RUU already stored in my PC, but the exact procedure to execute from this point forward is still unclear. After all, I am a self-confessed "pre-novice". ANY help would be greatly appreciated. I haven't had my phone in a normal Android state for nearly 2 months.
I had already made it known that I do not see a black screen as described by SynisterWolf above. At present, ( 12am/Thursday, 4/20 ), I was going to take the leap, go ahead and run the RUU. As soon as I plugged in the USB, my PC gave me a message that it isn't recognizing the phone. Now, I am even more perplexed than before. It is far past the point where I REALLY NEED this phone. If anyone could assist with a possible solution to my super-dilemma, I would be forever in your debt. Thanks very much to all members here.
EriktheRed565
EriktheRed565 said:
I have finally gotten to the previously mentioned "unnamed" screen. This screen has a much shorter menu. Please recall that at the top of the FIRST and only screen I was able to get said "HBOOT" at the top, above a list of various details such as the Evita name, Radio, openDSP,etc. At the top of this one, it says ***LOCKED***, above the like details mentioned.
There is then, in the center of the menu, a red highlighted "FASTBOOT AC" that cannot be selected for anything that I know of. Finally, the possible workable selections are, from top to bottom, read BOOTLOADER, REBOOT, REBOOT BOOTLOADER, and POWER DOWN.
If by "the Android" mentioned by SynisterWolf, she means the green robot icon(s), there are three of them on skateboards at the bottom of this screen. These observations are all that I know, with regard to the main issue at hand.
I have the RUU already stored in my PC, but the exact procedure to execute from this point forward is still unclear. After all, I am a self-confessed "pre-novice". ANY help would be greatly appreciated. I haven't had my phone in a normal Android state for nearly 2 months.
I had already made it known that I do not see a black screen as described by SynisterWolf above. At present, ( 12am/Thursday, 4/20 ), I was going to take the leap, go ahead and run the RUU. As soon as I plugged in the USB, my PC gave me a message that it isn't recognizing the phone. Now, I am even more perplexed than before. It is far past the point where I REALLY NEED this phone. If anyone could assist with a possible solution to my super-dilemma, I would be forever in your debt. Thanks very much to all members here.
EriktheRed565
Click to expand...
Click to collapse
HELP!! I see that my HTC One X (AT&T) needs a driver update, but cannot find one. HTC's website is NO HELP at all. Can someone help me to find the web page or site where I can obtain a driver update for this phone, PLEASE?
EriktheRed565 said:
HELP!! I see that my HTC One X (AT&T) needs a driver update, but cannot find one. HTC's website is NO HELP at all. Can someone help me to find the web page or site where I can obtain a driver update for this phone, PLEASE?
Click to expand...
Click to collapse
Flash stock firmware dude