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.
Related
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
Hi Guys,
So i've been away from flashing ROMs for awhile but have been playing with my HTC one and have had no issues until today.
I downloaded the new ARHD, put it on my SD card and went to install it. Aroma played nice for once but as soon as it started installing and doing the full wipe the phone rebooted. So i tried again with the same result. In the end i passed by the full wipe option and managed to get to the final step of rebooting and then it would freeze which it did 3 times.
Now i can see the ROM but i can't mount the SD card in CWM to put anything else on there so my phone is useless. I am not really experienced with ADB having only used it briefly with my sensation a few years back.
Can anyone help?
Thanks in advance
connect phone to comp, open cmd in folder that you have rom on computer (cd/location/here/rom.zip) then do (as long as you set up adb correctly) adb push rom.zip while selecting flash rom from sideload. cwm will do the rest.
I think all that happened was Aroma crashing every time. Correct me if I'm wrong but that's what it sounds like to me.
Hi,
I cannot get the phone recognized in fastboot, if i let the phone start to boot i can see my device.
Sorry if this isn't clear
Glenn.Bre said:
Hi Guys,
So i've been away from flashing ROMs for awhile but have been playing with my HTC one and have had no issues until today.
I downloaded the new ARHD, put it on my SD card and went to install it. Aroma played nice for once but as soon as it started installing and doing the full wipe the phone rebooted. So i tried again with the same result. In the end i passed by the full wipe option and managed to get to the final step of rebooting and then it would freeze which it did 3 times.
Now i can see the ROM but i can't mount the SD card in CWM to put anything else on there so my phone is useless. I am not really experienced with ADB having only used it briefly with my sensation a few years back.
Can anyone help?
Thanks in advance
Click to expand...
Click to collapse
If it got all the way to the "Reboot Phone" stage--meaning that the phone wiped and installed the new OS--you should be fine to boot the phone up normally. I'm sure you have, but have you tried just powering it up and seeing if it'll load into Android? Reminder: First boot after a new ROM always takes a few minutes.
Hey guys,
So i ended up continuing to flash it trying various options and eventually it came up ok... The scary thing was the random reboots during install whilst aroma was trying to wipe everything...
But all sorted, thanks everyone!
The title says most of it.
Loaded cm-10.1.3-RC2-m7spr.zip with recovery-clockwork-6.0.3.6-m7spr
Then loaded gapps-jb-20130813-signed.zip.
The phone boots, and/or i can get into the recovery, but when booted the android keyboard crashes whenever I need to enter text. In recovery it fails to load the extSD so even though the first thing I did was backup after fishing the ROM I cannot use the recovery.
It charges, but isn't recognized by my windows 7 or Linux computers. I can push files to it via Bluetooth.
Also have no access to the play store due to not being able to sign in.
I also tried a BT keyboard, which paired, but failed to type and also produced the crash message.
Has anyone had this particular issue before? All my previous cyanogenmod experiences were painless. I've gotten no help on the cm boards, so please, please tell me there is hope.
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
Hello everyone,
first of all thanks for your amazing work and all the stuff you provide. I was a silent reader for a long time, but now my phone is trolling that much, I cannot fix it on my own/with the guides I found here.
I do have an HTC One M7, rooted (superuser) and S-OFF (revone) with Androidd Revolution HD 71.1. I used to update my ROM every month, but I got stuck after the last update. My recovery was TWRP as CWM did not work properly when I rooted my phone.
My issues as a list:
- cannot enter recovery anymore
- cannot connect via USB (tried every port)
- screen turning randomly black on homescreen and sometimes in apps (but they usually work), screen does work, but i cannot see a thing
- since today graphical issues after a reboot (flickering screen, parts of the screen get duplicated)
Since the last update I cannot enter recovery anymore. Getting in bootloader is no problem but i get stuck in the "entering recovery...." screen. It does not move, tested it for some hours. I tried updating the recovery (-), trying to flash stock recovery and reflashing custom (-), trying cwm (-).
After I tried cwm i noticed that it didnt overwrite the recovery but i got both. cwm and twrp, but i cannot delete one of them (didn' work before either). I can start TWRP oder CWM on a booted phone, but updating both bugs and I can't enter recovery with these tools too.
Today I wanted to try again on my own, but my phone won't connect on USB. Tried every port on my computer with and without USB-Debugging. I will try on a other computer, but I could not do this until now. Additionaly I want to wait for some ideas of fixing, as I think "my" trys are not going to work suddenly .
Screen started to turn black a few days ago. Dont know why but I think it could be a software issue. but i cannot update (see above ). When i try to turn my screen on it often just turns instantly black. soft keys are enlightend and it does work (more or less). if i success in sliding down the service bar on the top, i can start my alarm clock app and from there use the soft keys to get in other started apps. From there it works most of the time. Sometimes i need a couple of trys, sometimes it just works as its intended without turning black and sometimes i need several minutes to succeed.
Cannot say more as I did to the graphical issues. Just had them once until I started an app (screen worked). could not reproduce this error.
I would prefer a solution without wiping, but if necessary i will ofc.
Thanks in advance for your help, as I am rather helpless right now.
I attached a photo of the bootloader.
Yours Laexxi