I've been through the ringer here. Any help is appreciated.
I have an international HTC One X (although it only has 16GB of memory and I'm inclined to beleive it has a dual core processor)
I wanted Slim Bean on my phone. So I installed SDK and rooted my phone with CWM successfully.
I flashed everything, everything was fine. I got Slim Bean up and running but when setting up, a persistent message appeared saying "Unfortunately, the process com.android.phone has stopped". Which is something to do with the play Store (?), so i re-flashed to the backup of the stock original OS to disconnect my username from the play store.
However when reflashing i do remember typing "fastboot flash boot [recovery].img" or something similar instead of "fastboot flash recovery [recovery].img"
After this it now only boots into CWM, trying to backup and doing all sorts of restores don't work (caches etc)
This turns out to be a 1a brick, but that needs adb shell. When i try to use this it says 'error: device not found', however flashing is fine, and when my phone started to run low on battery, it came up in CMD. so there IS feedback.
I have done a lot of driver fiddling to try and solve this, PDAnet etc and I can't seem to get it fully working.
Thanks for reading
Did you read what forum this is?
Sent from my Desire HD using xda premium
Related
Very noobish issue. Rooted, unlocked bootloader on Atrix HD. Set up SafeStrap as recovery. Everything checked and working. After letting SafeStrap install Cyan 10.3 and rebooting, phone entered CyanogenMod boot screen and become stuck for an hour. Realized that I forgot to reset and wipe all stock settings and cache (yes, I know that should have been obvious step). Figured I could just go into SafeStrap and make the quick fix.
Seems that I'm unable to enter my custom recovery, instead I'm lead to the familiar bricked android stock recovery. No options to access stock rom (assuming it was deleted during install or lost, etc). Tried installing a different recovery, but fastboot on PC is unable to find device. Help at this point is very much appreciated, either to do any of the following:
1. Somehow access SafeStrap again (assuming that it wasn't wiped aswell) so I can clear stock settings and cache, get Cyan 10.3 going properly.
2. Instructions/links to another method to otherwise forcibly delete stock settings and cache (please keep in mind, fastboot is currently unable to find device).
3. Otherwise completely clear phone of EVERYTHING, then reinstal stock recovery and or/stock ROM so I can give up on flashing custom and stick with stock.
*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.
Update Motorola drivers on your computer and check threads for fastboot files from skeevydude.
Sent from my MB886 using XDA Premium 4 mobile app
Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX
http://forum.xda-developers.com/showthread.php?t=2226527
Sent from my MB886 using XDA Premium 4 mobile app
SkunkID said:
*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.
Click to expand...
Click to collapse
The error is from using the wrong fastboot executable. Look at post 5. If you get a stickybit error, search our general forums for "stickybit" and you'll find that fix.
deeje00 said:
Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
With a bit of creativitity one could use SSR to dual boot Holo Blur and Batakang....or two custom 4.3's that use the same kernel....PAC + Carbon both with arrrghhh's kernel.....Only problem is ya can't be a noob at all if ya do it.
Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.
When you're at the "dead Android" screen pressing Vol Down + Power pushes it into recovery, iirc - might seem random but there's a purpose behind it.
SkunkID said:
Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.
Click to expand...
Click to collapse
Hi, I am having the same issue you had... how the heck were you able to get back into stock recovery? Every time I try my phone just reboots and gets stuck again. I cant even turn off my phone with out it rebooting. I have read your posts and followed that other forum you mentioned but if I cannot boot into recovery and if my computer cant see my phone it wont work. Please help when you get a chance.
Hello. I'm very new to the whole process of rooting my device and installing roms, so please bear with my lack of knowledge.
I recently tried to install the Stock Google Play 4.4 ROM for my HTC One (m7-tmo).
Everything went smoothly, up until I actually tried to use the phone with the new rom installed.
After briefly allowing me to go through the setup menu (language settings), the device restarted itself back to the HTC boot screen after about 5 seconds. This cycle went on indefinitely.
I then found out that I needed to have S-Off installed before I installed the rom, but sadly it doesn't appear as if I can install that at this stage (but if anyone knows of a way, that would certainly help).
I proceeded to looked for a ROM that could work without S-Off, but now I'm stuck without a means of being able to install it.
I tried to install it during the brief period of time I have that the phone is in setup mode, but that is too short for the computer to recognize my device before it reboots again.
Does anyone know of a way I can transfer the file of the rom to my device in fastboot mode or directly transfer the file to my phone while in TWRP? Or is anyone aware of a possible solution that involves a completely different method? It's a rather sticky predicament, and any help would be greatly appreciated. Thanks.
adb commands (such as adb push) usually work while you in recovery..
Sent from my HTC One using xda app-developers app
First and foremost I am a newb when it comes to rooting. I tried installing the newest Viper Rom on my phone and everything was successful until the phone tried to reboot. It is now stuck in the fastboot/bootloader screen and I cannot go into recovery mode at all. I tried doing a factory reset and it just keeps taking me back to the same screen.
I was running Cynogen MOD 4.4 Rom and everything was working fine. I backed up my phone and wiped my phone before I ran the Viper Rom. I don't know what happened and I'm kind of freaking out. I tried connecting my phone to my computer via USB when I run "fastboot devices" through the command prompt it keeps giving me "waiting on device". I did some research and everywhere kept saying that I needed to install the htc drivers through both htc sync manager and the individual driver files I found on the internet. I did everything possible and it still doesn't seem to recognize it.
I'm currently stuck/lost on what to do hopefully someone here can point me in the right direction. Attached is a screen shot of both my device manager and command prompt. I will continue to look on the internet for any type of answer. Thanks everybody.
(Sorry for starting a new thread I just didn't know where to put it.)
Does your phone boot? Can you get to recovery or bootloader?
Sent from my HTC One using Tapatalk
It boots but it keeps going back to the same screen where it says bootloader, factory reset, fastboot, etc... I had cwm installed but every time I push recovery it takes me back.
kal3l15 said:
It boots but it keeps going back to the same screen where it says bootloader, factory reset, fastboot, etc... I had cwm installed but every time I push recovery it takes me back.
Click to expand...
Click to collapse
Are you sure you selected sprint during setup? Maybe this is your solution http://forum.xda-developers.com/showthread.php?t=2503646
Sent from my HTC One using Tapatalk
I finally got my second hand M7 yesterday and installed CM11 - install process was fine, everything ran smoothly, I've got CWM 6.0.4.8 running as recovery on it. However:
1. When I boot into CM11 proper to try to use the phone, I get "Unfortunately, Lockscreen has stopped" repeatedly and cannot get it out of the way. This appeared during first start-up and continues to hinder use of the phone (e.g. no keyboard will pop up - thus no typing in wifi passwords, no turning Developer Options on so no USB debugging, etc). I tried updating to a more recent nightly but nothing seems to work: unzipped file, flashed boot.img using fastboot.
2. Why can't I mount USB storage from CWM? I remember on my old Samsung S2 that was an option - or I may have remembered incorrectly, that was so long ago!
Somebody please help, this is pretty frustrating! I haven't had such a problem with CM before, I wonder if it's a reproducible issue...
Anyway, I am also wondering - what are the pros/cons of a Sense ROM versus a non-Sense one?
EDIT: Have tried using ADB sideload with TWRP now, but progress stops at "Starting ADB sideload feature..." with the progress bar continually scrolling but never filling up. Checking for devices on terminal results in no devices listed.
okay, i had a slim rom running on my fire (5.1.1) and tried to go to cm12 using flashfire. i made sure that wipe was at the top of the list. it got stuck on installing the new rom, so after 30 minutes i restarted tablet. i got stuck in the cm logo bootloop. i do still have access to the amazon stock recovery. tried to do a data wipe/factory reset. still stuck at logo bootloop. i tried to sideload the amazon stock bin file, but it stops after 5 seconds and says "failed to read command: invalid argument" and goes back to the recovery main menu. if you try to do another sideload, it instantly says "timed out waiting for package. installation aborted" before you even press anything. have to restart device to try sideloading again.
at one point i had it almost install cm12 from a zip file through sideload, but at the very end it gave me a signature verification fail. since i can't boot the phone, i can't turn on usb debugging. sometimes it'll show up in the device manager as mtp but never shows up as fire or android device or any of that. it will show up on adb devices command when its in fastboot, but can't do anything with it from there. i've tried all the different ways in the forums here and rootjunky, but nothing seems to work at all. any ideas if i'm doing something wrong or is this just bricked, regardless of stock recovery?
tried a few commands to see if i could fastboot one of the roms or stock images, but they all tell me its missing the android-info.txt
dorkydroid said:
okay, i had a slim rom running on my fire (5.1.1) and tried to go to cm12 using flashfire. i made sure that wipe was at the top of the list. it got stuck on installing the new rom, so after 30 minutes i restarted tablet. i got stuck in the cm logo bootloop. i do still have access to the amazon stock recovery. tried to do a data wipe/factory reset. still stuck at logo bootloop. i tried to sideload the amazon stock bin file, but it stops after 5 seconds and says "failed to read command: invalid argument" and goes back to the recovery main menu. if you try to do another sideload, it instantly says "timed out waiting for package. installation aborted" before you even press anything. have to restart device to try sideloading again.
at one point i had it almost install cm12 from a zip file through sideload, but at the very end it gave me a signature verification fail. since i can't boot the phone, i can't turn on usb debugging. sometimes it'll show up in the device manager as mtp but never shows up as fire or android device or any of that. it will show up on adb devices command when its in fastboot, but can't do anything with it from there. i've tried all the different ways in the forums here and rootjunky, but nothing seems to work at all. any ideas if i'm doing something wrong or is this just bricked, regardless of stock recovery?
tried a few commands to see if i could fastboot one of the roms or stock images, but they all tell me its missing the android-info.txt
Click to expand...
Click to collapse
try stock 5.1.2 firmware
otherwise there is no fix that I know of
Sent from my KFFOWI using XDA Labs
i started trying to get it going, but got the same results. eventually the battery died and it doesn't want to charge anymore, so hopefully i'm still under warranty. thanks for all the help though, been a reader here for a really long time. just sucks to get a hard brick for the first time. used a droid x for four years straight with a locked bootloader and never came across a problem like this
dorkydroid said:
i started trying to get it going, but got the same results. eventually the battery died and it doesn't want to charge anymore, so hopefully i'm still under warranty. thanks for all the help though, been a reader here for a really long time. just sucks to get a hard brick for the first time. used a droid x for four years straight with a locked bootloader and never came across a problem like this
Click to expand...
Click to collapse
I fear I'm in the same boat. Which version of flash fire were you using?
Any further progress?
Sent from my Nexus 7 using XDA-Developers mobile app