I seem to be having trouble with my install of CWMT 6.0.3.1; Aroma freezing (known issue) and the nandroid I made of my original image tells me the md5 doesn't match (!!).. i get all sorts of failed to mount messages when starting it too.
I notice there's version 6.0.3.2 for Sprint and T-Mobile, so how is that different to the regular HTC One? Hoping that a reinstall and update might fix some of these problems, but just wanted to check if these other versions would work on an international version.
Finner42 said:
I seem to be having trouble with my install of CWMT 6.0.3.1; Aroma freezing (known issue) and the nandroid I made of my original image tells me the md5 doesn't match (!!).. i get all sorts of failed to mount messages when starting it too.
I notice there's version 6.0.3.2 for Sprint and T-Mobile, so how is that different to the regular HTC One? Hoping that a reinstall and update might fix some of these problems, but just wanted to check if these other versions would work on an international version.
Click to expand...
Click to collapse
Have you renamed your Nandroid backup at all?
Sent from my HTC One using xda premium
Nope, didn't touch a thing. Just tried to restore the backup after an install of ARHD seemed to crash mid-install, and CWMT restarted the phone when I didn't tell it to so I got stuck in a bootloop - couldn't even turn the phone off despite holing down the power button, it just kept turning back on. Couldn't load recovery either..
Got all that sorted with loading CWMT via fastboot and reinstalling ARHD. Got Aroma freeze, but at the end this time, so after reboot it finally booted in to the system... but not convinced all is stable.
Not sure if it's a CWMT thing, or something else? My bootloader now also says 'tampered', not sure why or if that changes anything?
Sent from my Nexus 7 using xda app-developers app
Finner42 said:
Nope, didn't touch a thing. Just tried to restore the backup after an install of ARHD seemed to crash mid-install, and CWMT restarted the phone when I didn't tell it to so I got stuck in a bootloop - couldn't even turn the phone off despite holing down the power button, it just kept turning back on. Couldn't load recovery either..
Got all that sorted with loading CWMT via fastboot and reinstalling ARHD. Got Aroma freeze, but at the end this time, so after reboot it finally booted in to the system... but not convinced all is stable.
Not sure if it's a CWMT thing, or something else? My bootloader now also says 'tampered', not sure why or if that changes anything?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Its an Aroma thing. Just go through the install slowly, try not to use the touchscreen - use the volume and power buttons instead. Also, people say that it tends not to crash if the phone is cool in temperature.
Tampered, I think, is just because you have a custom recovery. Nothing to worry about.
Sent from my HTC One using xda premium
Thanks for clarifying Still seem to have Aroma problems even when using the buttons, and occasionally it crashes mid-install. Get there in the end though, and have switched to TWRP which seems to work a bit better with the Aroma installs.
I read that CWM 6.0.3.2 has fixed the Aroma problems, but is only available for Sprint and T-Mobile at the moment.
Related
I have a HTC Hero, today I tried to update my cyanogen mod 7 to 7.0.3 however when I did, I did all the proper steps to update the Rom properly however it did not work. So I tried a fresh install, and even tried a few new Roms still nothing worked. Recoveries work fine. When I restart my phone it hangs at the HTC screen then restarts and it will do this so far for up to 15 mins. someones gotta have an idea on whats going on. btw phone is rooted and running clockwork.
goshxjosh said:
I have a HTC Hero, today I tried to update my cyanogen mod 7 to 7.0.3 however when I did, I did all the proper steps to update the Rom properly however it did not work. So I tried a fresh install, and even tried a few new Roms still nothing worked. Recoveries work fine. When I restart my phone it hangs at the HTC screen then restarts and it will do this so far for up to 15 mins. someones gotta have an idea on whats going on. btw phone is rooted and running clockwork.
Click to expand...
Click to collapse
What version of cwm? Try flashing a different recovery version (maybe 2.7.0.5)
Make sure you factory wipe as well as format, system, data, cache.
Bad download maybe?
®patience is a virtue©
is your battery charged well above 30%?
Sent from my HERO200 using XDA App
Guys i had this problem when i flashed my first ROM too ...(alas)
Buy my problem was a simple fix ,
: restart in recovery
: wipe all data
: restart and Enjoy
i have the most recent cwr and i wiped my data and everything. i have been flashing for more that a year now this is the first time ive had this issue. im gonna unroot and reroot the phone.
If you haven't unrooted yet try just reflashing your current recovery.
#Root/Hack-Mod_Always*
This has happened to me with different builds ( of all of the different gingerbread roms) since the switch from 2.3.2 to 2.3.3 and .4.
When this happens, I will either try a different Rom, or use something called Fix Flash that is in the development section for the CDMA Hero. My phone currently is liking the Jaybob build. Also, as silly as this might sound, but formatting the partitions 3x can actually help too ( boot, system, data, and cache).good luck, I've been there.
Sent from my HERO200 using XDA App
Can't get past the HTC screen...
I got a new HERO200 as a replacement for a damaged one and am able to root it with confirmed SU permissions. I have tried clockwork 2.5.0.7 and RA 1.6.2 for the heroc. I tried flashing Cyanogenmod 7 (7.0.2 / 7.0.3 / 7.1.0 / and even a 6), AOSP and it keeps hanging at the HTC screen when I reboot the device out of recovery. The first reboot after flashing a ROM will briefly display the HTC screen and then go black. I have to remove the battery to reset the phone. When I power it up again, it will display the HTC screen and just hang, even after multiple restarts via a battery removal. I have wiped all the data/cache/etc. multiple times as from a previous post in this thread, but without luck. I'm getting very frustrated to say the least and any help would be GREATLY appreciated.
never had a rom not booting, but i haven't tried them all,
try the older version again see if it works
I just run the nightlies and skipped the rc and haven't experience such things. could be something to do with the signing?
Sent from my HERO200 using XDA App
i was running the latest AndroidNow ROM and then i downloaded Android Revolution HD since i saw Sprint Support on it and stupidly flashed on mine. not realizing its not for me *yet*
and so it didnt boot. so i went back and boot to recovery. TWRP 2.6.3.0 and restored my phone to my last ROM AndroidNow.
it boots. i noticed i dont have a signal but i was connected to wifi. so i tried doing 4636 code. then selected GSM/WCDMA since im outside US. (Vietnam) but it didnt work and after a few minutes. it rebooted itself. and since that time everytime i boot. it goes all the way to the main screen only to reboot once again.
i tried reflashing AndroidNow. it finishes with no problems. But never boots. itll reboot once it finishes but will go back to TWRP recovery.
Im having problems with drivers of it too. Im using Windows 8.1 x86 and i cant seem to find a working Driver for Sprint HTC One. Please help.
kianjhay03 said:
i was running the latest AndroidNow ROM and then i downloaded Android Revolution HD since i saw Sprint Support on it and stupidly flashed on mine. not realizing its not for me *yet*
and so it didnt boot. so i went back and boot to recovery. TWRP 2.6.3.0 and restored my phone to my last ROM AndroidNow.
it boots. i noticed i dont have a signal but i was connected to wifi. so i tried doing 4636 code. then selected GSM/WCDMA since im outside US. (Vietnam) but it didnt work and after a few minutes. it rebooted itself. and since that time everytime i boot. it goes all the way to the main screen only to reboot once again.
i tried reflashing AndroidNow. it finishes with no problems. But never boots. itll reboot once it finishes but will go back to TWRP recovery.
Im having problems with drivers of it too. Im using Windows 8.1 x86 and i cant seem to find a working Driver for Sprint HTC One. Please help.
Click to expand...
Click to collapse
Read this http://forum.xda-developers.com/showthread.php?t=2460013
Sent from my HTCONE using Tapatalk
Thanks
elvisypi said:
Read this http://forum.xda-developers.com/showthread.php?t=2460013
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Thanks ive done it with RUU. Went back to Windows 8. Drivers ont seem to work on 8.1
That happened to me and I just flashed the latest radio and it worked fine. I can reupload it and link it if you haven't tried it already
So here's what happened. I was planning on getting the M8 when it comes out on TMO. So I was returning my phone to stock, removing tampered flag and so on. After I did all of that I went to update my phone to 4.4.2 via the official update. However, during that process something happened and the update failed. I rebooted my phone and now it loads a pink, pixelated screen then goes to the HTC One loading screen then just freezes there (and the colors are off). I cannot boot my phone up completely. I can still push custom recoveries and my computer is making connect/disconnect sounds when I plug in my phone (if I do adb devices it says nothing is connected though). I'm s-off with hboot 1.56 and I was rooted. I can still boot into fastboot and my recovery and that's it. I do not have a backup that I can flash. I have also tried sideloading via twrp and that just fails.
I'm kind of just lost on what to do at this point. I have searched the forums and google and I haven't really found anything else that I can try at this point.
I was able to flash the firmware again. Now the pixelated screen is gone and the colors are right on the boot up screens.
Same thing happened to me. Pixelated pink/purple splash screen and then boot "animation" had a blue Beats logo and then froze. I actually forget how I fixed it, but it may have involved manually flashing some firmware. At the time I searched around to see if anyone else had ever experienced this. Apparently I was not alone.
Sent from my HTC One using xda app-developers app
I flashed the newest firmware and then unlocked my phone again and flashed twrp again.When I try to sideload it says nothing is attached to my computer. When I try to push a file I get an error saying no device is connected. When I try to flash it with adb commands I get the same thing as sideloading.
Did you install the HTC drivers on your computer?
R34LY said:
Did you install the HTC drivers on your computer?
Click to expand...
Click to collapse
Yes.
In my case, I had a working nandroid backup stored on the phone, so once I got into recovery, I just restored the nandroid and went on with my life. Not sure if that would work for you or if it's even an option for you. Or even if I remember it correctly. But "that's that my story and I'm sticking with it"..
Sent from my HTC One using xda app-developers app
So i got a new lg g2 for verizon last week. ive had good experiences with cyanomod and other roms so i figured off the bat that i would install one of these. turns out they were alot more problems than it was worth. so i went back to stock rom and rooted. for some reason i took OTA. now phone is stuck in fastboot. so i went through this thread http://forum.xda-developers.com/showthread.php?t=2582142. so i got everything done and figured out (running live ubuntu so getting automount to stop was a challenge and then figuring out the new file paths). so now i reboot phone and try to get into twrp (from complete power off hold power button and volume down, release when logo shows and press again). so i get the "do you want factory reset" screen and i click yes, yes then it just goes into fast boot again. problem is now not even linux is reconizing the device. device doesnt go into twrp. cant get into download mode to reflash. all i got is "[16370]fastboot mode started [16420]udc_start() [16590]-reset- [1660]-portcharge- [16640] fastboot: processing commands.
do i have any hope? the phone is new from a third party so i dont think i have a chance to return to the seller, and im not sure if lg will take it either
added info
also, just read and possibly part of problem, twrp was 2.7.1.0, either way though im still stuck with it at this point
ok, so just a bit more info. now when the phone is plugged into windows 7 computer it automatically installed a driver "USB Movem Phone ADB port". so i figured id try to run adb devices and see if it showed, no luck. dont know if this puts me in a different situation or not...
Did you try via terminal $ reboot-bootloader you may be able to force into bootloader for adb sideload twrp 2.7.0.0
Sent from my VS980 4G using XDA Premium 4 mobile app
---------- Post added at 09:12 PM ---------- Previous post was at 09:03 PM ----------
Adb and fastboot are two different programs. If your in fastboot mode computer won't recognize adb devices. While in fastboot mode, reboot-bootloader then see if you can get adb through toggling vol + or -
Sent from my VS980 4G using XDA Premium 4 mobile app
actually i just got a step farther.... now i have twrp installed and working (turns out version 2.7.1.0 and 2.7.0.0 both didnt work with my phone even though i specifically got the versions for my phone. now im using 2.6.3.2 in case anyone else is having issues).
so twrp is on the phone. by random luck i apparently had all the rom zips left on the SD card. so i was able to flash a known working rom (at least it was working well enough to get by...). so i flashed the rom and rebooted the phone. unfortunatly it went straight back into twrp. i dont know if there is a flag i havent set or what. i thought i saw a walkthrough about what to do at this point, so im still working on it and i will update if i can fix it... but as i stated right now have twrp 2.6.3.2 working, still no download mode apparently(ill mess with this more because originally this is how i was flashing back to stock when things went wrong), and even though twrp installed a known working rom its still booting straight into twrp (without the whole power and volume down seqeunce...)
Some ROMs won't work on 2.6.3.2
Sent from my VS980 4G using XDA Premium 4 mobile app
would it automatically go to twrp if the rom didnt work? the reason im asking is because when i was messing around with the roms throughout the week some of them didnt work (either black screen at boot, or bootloop with logo). and i would have to manually shut the phone off, then go through factory reset, then it would turn on twrp. right now the phone just turns on and goes straight to twrp
If recovery doesn't detect a compatible ROM it bootloops. That or corrupt download itself, make sure to verify md5s whenever possible.
Sent from my VS980 4G using XDA Premium 4 mobile app
YAY, got it mostly back kinda sorta. so i followed this http://forum.xda-developers.com/showthread.php?t=2451696 after getting back into twrp. i dont know what this did or if it helped. then i flashed a new rom (which i also by chance had on the SD already) i believe it was malladus 1.2.9 and it worked (except i didnt put gapps or anything so it was having a fit about play... now its restarted and i have download mode back so ill just flash the whole thing with the regular rom (the rom on this website might even be older than the phone, but for me it worked well...). here is that website i case anyone needs it http://www.lg-phones.org/guide-to-flash-restore-unbirck-verizon-lg-g2.html i will reflash and post results, hopefully a bone stock phone to start over with...
glenn3451 said:
would it automatically go to twrp if the rom didnt work? the reason im asking is because when i was messing around with the roms throughout the week some of them didnt work (either black screen at boot, or bootloop with logo). and i would have to manually shut the phone off, then go through factory reset, then it would turn on twrp. right now the phone just turns on and goes straight to twrp
Click to expand...
Click to collapse
As far as a straight to recovery, I haven't had that problem on my g2. On my tablet,I run multi ROM recovery and it will go straight to recovery if a ROM is not installed. I would think it would do the same on vs980 twrp.
Sent from my VS980 4G using XDA Premium 4 mobile app
btw thankyou for suggesting a different rom, wouldve probably been stuck for awhile without that advice. so flashed verizon stock firmware(which also deletes everything) and its 100% running with the exception of the activation (switched back to old phone while working on getting this guy running again). i feel like ive learned alot more than i ever wanted so ill stay subscribed to this thread and if anyone has similar issues when you post hopefully ill be able to help alittle... no promises though
Edit: FIXED IT
I made a back up of stock 5.1.1 after I got my new RMA phone and after I updated it ..went through rooting unlocked bootloader.
I backed up stock ROM, flashed a few times since .
When I try to restore I get a unable to mount system error in twrp then the back starts and right around resorting system image twrp goes blank and reboots to Google screen and sticks there like glue Nothing reboots ???
What's causing my back up to not restore?
It was most definitely a successful back up to!
I still have it in storage .
Sent from my Nexus 6 using XDA Free mobile app
androidddaaron said:
I made a back up of stock 5.1.1 after I got my new RMA phone and after I updated it ..went through rooting unlocked bootloader.
I backed up stock ROM, flashed a few times since .
When I try to restore I get a unable to mount system error in twrp then the back starts and right around resorting system image twrp goes blank and reboots to Google screen and sticks there like glue Nothing reboots ???
What's causing my back up to not restore?
It was most definitely a successful back up to!
I still have it in storage .
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Edit: Fixed
You can not restore system image evidently as i with twrp as its checked by default
Uncheck system image and restore completes 100%
Sent from my Nexus 6 using XDA Free mobile app
androidddaaron said:
Edit: FIXED IT
I made a back up of stock 5.1.1 after I got my new RMA phone and after I updated it ..went through rooting unlocked bootloader.
I backed up stock ROM, flashed a few times since .
When I try to restore I get a unable to mount system error in twrp then the back starts and right around resorting system image twrp goes blank and reboots to Google screen and sticks there like glue Nothing reboots ???
What's causing my back up to not restore?
It was most definitely a successful back up to!
I still have it in storage .
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
If you are trying to restore a backup, then all you need to do is select that backup. If I'm misunderstanding what you mean to do or what the issue is, you may want to either upgrade or downgrade your version of TWRP. I had read the previous version wasn't working right for backup and restores. The app updated today in the Play store.
Did you even READ what the issue was?
He's talking about one thing (a problem I've experienced, in fact) and you're talking about something totally different.
Just saying.