Hey there,
I recently rooted my HTC one and loaded up Cyanogenmod. I loaded the most recent version yesterday, the nightly from 2/1 and it caused the phone to go into a bootcycle. I updated via CyanDelta, so it was a small file that was downloaded, and I dirty flashed using CWM. The issue is that my phone now is stuck in a bootcycle. Because I used CyanDelta, I do not have any full versions of CyanogenMod. Infact the only zips on the my phone are the update to the 1/31 nightly and the update to the 2/1 nightly.
Somehow my phone has its usb debugging turned off now, meaning I can not see it on my computer. I am wondering if there is anyway to reconcile this with my phone, since it is basically a brick right now.
I know there is Odin for samsungs, but it does not work for HTC? Is there something like Odin that does work from HTC?
Thank you all for the help.
Sounds like you need to push a ROM onto your sdcard and flash it, then go from there. This may help you out:
http://forum.xda-developers.com/showthread.php?t=1667929
raczoliver said:
Sounds like you need to push a ROM onto your sdcard and flash it, then go from there. This may help you out:
http://forum.xda-developers.com/showthread.php?t=1667929
Click to expand...
Click to collapse
Thank you for the suggestion, however my phone does not have an sdcard, and if I try doing this with any of filepaths I do have show up in CWM I get a message no device found. my /sdcard path is apparantly /data/media but nothing works to push to my phone. I have also tried to sideload and again it does not work. any other ideas?
Fixed It
OK, so I figured out how to fix it.
I flashed the update file (about 4mb) from my phones memory of the 1/31 version, then gapps4.4. Once that was done I got into the phone and enabled USB debugging and after doing so, I loaded up the new full version of Cyanogen, the nightly from today (2/2) and installed it, along with gapps, and the radio update.
Thanks for the help guys.
Related
Ok, here's the deal:
Rooted the device, everything was a-ok.
Installed Clockwork, everything still a-ok.
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Ever since, it won't go past the screen you get at the beginning (w/ the yellow sign indicating an unsecured rom). It just stays there forever.
What I have to work with:
- Clockwork Recovery is available.
- The device is recognized by Odin when in download mode.
- The device is not recognized by the computer/Kies.
What I've tried:
- Followed the instruction for boot loop w/ both stock rom and Villain (no dice).
I'm sorta freaking out now. I have yet to see anyone having the same problem online and I really hope it's not bricked - a 600$ paperweight...
Is there something else I can try? Is it possible to flash stock PIT/Bootloader/PDA/everything else? If it is, would it fix the problem?
Please just point me in the right direction.
Thank You,
Edit: In recovery mode, the following error appears:
- Can't access to "/system/csc/VMC/system/"
Edit: In download mode, the current binary is set to "Samsung Official". Therefore I think this isn't the problem.
Edit: OMG OMG holy crap. Problem has been solved. Got a friend who had the same phone from the same provider to tell me what the firmware for the phone was. Downloaded it. Installed it w/ Odin. I almost turned religious when it booted a bit slower than what I remembered. It works well enough now, although I will probably go exchange it for a new one ASAP, before my warranty expires.
If anyone has similar problems. Don't panic and re-install stock firmware.
Cheers Folks!
Rovah said:
Ok, here's the deal:
Rooted the device, everything was a-ok.
Installed Clockwork, everything still a-ok.
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Ever since, it won't go past the screen you get at the beginning (w/ the yellow sign indicating an unsecured rom). It just stays there forever.
What I have to work with:
- Clockwork Recovery is available.
- The device is recognized by Odin when in download mode.
- The device is not recognized by the computer/Kies.
What I've tried:
- Followed the instruction for boot loop w/ both stock rom and Villain (no dice).
I'm sorta freaking out now. I have yet to see anyone having the same problem online and I really hope it's not bricked - a 600$ paperweight...
Is there something else I can try? Is it possible to flash stock PIT/Bootloader/PDA/everything else? If it is, would it fix the problem?
Please just point me in the right direction.
Thank You,
Edit: In recovery mode, the following error appears:
- Can't access to "/system/csc/VMC/system/"
Edit: In download mode, the current binary is set to "Samsung Official". Therefore I think this isn't the problem.
Edit: OMG OMG holy crap. Problem has been solved. Got a friend who had the same phone from the same provider to tell me what the firmware for the phone was. Downloaded it. Installed it w/ Odin. I almost turned religious when it booted a bit slower than what I remembered. It works well enough now, although I will probably go exchange it for a new one ASAP, before my warranty expires.
If anyone has similar problems. Don't panic and re-install stock firmware.
Cheers Folks!
Click to expand...
Click to collapse
Same problem. anyone?
Vincho said:
Same problem. anyone?
Click to expand...
Click to collapse
Did you read the answer ???
jje
Look online (samfirmware), ask friends or on forums for anyone who has the SGS2 w/ the same carrier in the same country and try to find the firmware version (I9100***** - the stars are letter codes). Then just download that firmware and use Odin to install it.
If you can't find it,you presumably could just flash any stock firmware and it might work (or it might make things worse, try at your own risk)
Rovah said:
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Click to expand...
Click to collapse
The progress bar not moving is a known issue with the CM7 Recovery. All you need to do is wait for it to say that it's finished. There is nothing wrong with your phone and no need to return it. You just cancelled the CM7 install part way through which meant not all required files were installed on the phone, causing it to not boot.
As for it taking longer to boot into android after the odin reflash. That's because it has to build up it's dalvik-cache again. This is completely normal any time you install a new rom. It only happens on first boot of a rom.
So again, no need to return your device and feel free to try CM7 again. Just remember to let it finish even if the progress bar isn't moving.
Ahh. Ok that makes sense. This ought to teach me to read before screwing around w/ my phone.
I wanted to exchange it because I wasnt sure i'd still be able to install official Samsung firmware updates through Kies.
Suppose an official 2.3.4 firmware comes out, would i be able to install it through Kies?
Sent from my GT-I9100 using XDA App
Rovah said:
Ahh. Ok that makes sense. This ought to teach me to read before screwing around w/ my phone.
I wanted to exchange it because I wasnt sure i'd still be able to install official Samsung firmware updates through Kies.
Suppose an official 2.3.4 firmware comes out, would i be able to install it through Kies?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Yes, as long as the firmware you're flashing is the same as the stock version that came on the phone. And even if not, you'll get the kies updates for whatever region firmware you did flash onto the phone.
I see. Thanks a lot!
Is there any danger to flashing firmware from a different region than the one youre from?
Sent from my GT-I9100 using XDA App
I have searched everywhere for an answer to this. I apologize if its been answered before. here is my issue:
I acquired an amaze 4g. S-on no rom. Freezes at white HTC screen. tried stock GB RUU but apparently it has ICS. So I loaded ICS OTA RUU. 3 different ones OTA and leaks. I also have ADB shell access if this matters. I can get to my sd card through CWM but not through 4ext because I am unable to mount the internal sd. I have pulled my hair out for days on end trying to fix the unable to mount /internal_sdcard issue. I did however find a CWM ICS stock recovery download and tried that through CWM since that seemed to be able to acces my external SD somehow (apparently the same way the bootloader does when updating the ph85img). But i get an MD5 sum error. so... this leads me to a new post. How do I fix the mounting issue? Also before the mounting issue happend (i think after trying to install a ROM using a super wipe method). And once that is clear apparently the "roms" hang at the boot animation and go into a bootloop. But first things first. got to get the mount issue fixed. anyhelp will be greatly appreciated!
one last thing. I also have hansoon2000's toolkit v. 3.1 & 3.2 although i prefer 3.1 because 3.2 seems to be very buggy.
Johnny.Sleven said:
I have searched everywhere for an answer to this. I apologize if its been answered before. here is my issue:
I acquired an amaze 4g. S-on no rom. Freezes at white HTC screen. tried stock GB RUU but apparently it has ICS. So I loaded ICS OTA RUU. 3 different ones OTA and leaks. I also have ADB shell access if this matters. I can get to my sd card through CWM but not through 4ext because I am unable to mount the internal sd. I have pulled my hair out for days on end trying to fix the unable to mount /internal_sdcard issue. I did however find a CWM ICS stock recovery download and tried that through CWM since that seemed to be able to acces my external SD somehow (apparently the same way the bootloader does when updating the ph85img). But i get an MD5 sum error. so... this leads me to a new post. How do I fix the mounting issue? Also before the mounting issue happend (i think after trying to install a ROM using a super wipe method). And once that is clear apparently the "roms" hang at the boot animation and go into a bootloop. But first things first. got to get the mount issue fixed. anyhelp will be greatly appreciated!
one last thing. I also have hansoon2000's toolkit v. 3.1 & 3.2 although i prefer 3.1 because 3.2 seems to be very buggy.
Click to expand...
Click to collapse
When you flashed the stock ruu, did you allow it to boot up properly before attempting any flashing or custom recovery using of any sort?
Dark Nightmare said:
When you flashed the stock ruu, did you allow it to boot up properly before attempting any flashing or custom recovery using of any sort?
Click to expand...
Click to collapse
what do you mean by "boot up properly"?
after ruu loads, checks, then updates... i wait until it turns off before i jump into bootloader/recovery. Should i have let it continue to the HTC screen? it just freezes there.
update: ok, reloaded OTA ICS RUU... when it was done I went to fastboot and rebooted left it on htc screen for a few min. then pulled battery > bootlader > unlocked with hansoons > reflashed 4ext > rebooted > no good > did it a second time and went to fastboot > reboot let it load and freeze on HTC. cleared the /internal_sdcard error and its working now. THANKS!!! would have never guessed that all i had to do is reboot and thats all it needed. I was just taking battery out after it was done. on to next issue :/
formatted and cleared everything 3 times... loaded stock ICS rom.. gets half way through boot animation and locks... formatted again.. loaded energy rom, bootlooped at boot animation once, rebooted. and VOILA!
THANK YOU SOOOOOOOOO MUCH MAN! I would give you a thanks but I have no idea how. This is my first post.
There's a button right there , always let the phone boot properly, you may think it freezes on the HTC screen but it's actually setting up files, etc. Don't disturb it, let it be and the set up screen will pop up in a minute or so, it need to add files, remove files and properly map everything on first boot.
Thanks again man! Running perfect. I saw the thanks button, it was right in front of me. haha. :good:
Not the first post a noob really wants to make...but I've been searching the forums for an answer to my problem, but can't seem to find the info on the issue I'm having. I've seen some that were close & tried what was posted there without any success. I've checked out the Don't Panic -- Please Read First, includes troubleshooting guide Thread By: om4
A few days ago, I tried to install CM10 on my 4G LTE w/S-ON / HBOOT- 1.19. I was able to unlock the bootloader & install TWRP. Everything seemed to go okay until I rebooted my phone after installing CM10. It just hung on the Cyanogenmod splash screen. I tried re-installing it & kept getting the same problem. Today, I tried to install MeanROM ICS v6.5, but it keeps saying install failed. If I let the phone boot up, it'll hang on the MeanRom splash screen. I can still get into fastboot so I know it has to be a software issue. I've been beating my head against the wall for the past few days & just don't know how to fix it. Right now I have a very expensive paperweight. I'm hoping someone can help me fix this & get my phone back up & running.
TIA
for the millionth time
flash the boot.img seperately in hboot
Get (Flash Image GUI) off the Play Store.
If yr S-ON then u have to flash the kernel separate. That's why the ROM's keep hanging.
sent from my EVO LTE
http://forum.xda-developers.com/showthread.php?t=1772769&highlight=fastboot+gui
flex360 said:
for the millionth time
flash the boot.img seperately in hboot
Click to expand...
Click to collapse
I've been trying this all day, but must be doing something wrong. I found this: http://forum.xda-developers.com/showpost.php?p=29417266&postcount=1397, but was wondering if you might have more info on option 3.
TIA
if you know how to Fastboot, go for it, but use the Boot.img from the ROM you are flashing.
popper668 said:
if you know how to Fastboot, go for it, but use the Boot.img from the ROM you are flashing.
Click to expand...
Click to collapse
It's the only option I have now, so I hope I can figure it out. Wish me luck. I know it's probably something stupid that I'm missing & it's driving me crazy. lol
For meanrom make sure you have twrp 2.2.2.0 or later to be able install. The kernel installer will force the phone to reboot upon first run, this is when the kernel installs. For cm10 or other aosp based roms be sure to properly wipe phone. Cache, dalvik, factory reset, and system. Fastboot the kernel using SDK, mini SDK, uniflash, or boot image flasher. Do not use clockwork mod recovery to install roms as it is known to damage internel storage and or misc partitions.
ADB Tools Mini SDK
Thanks for all the info!!! I'm glad I found this place!!! I was able to get my phone working again. I found this post: http://forum.xda-developers.com/showthread.php?t=1937949 from back in October and found out that I was putting the boot.img in the wrong location. Once I fixed that, I have my phone back. Now I have to get it re-activated because I had to switch back to my Hero because I wasn't sure how long this would take. I hope Sprint will activate it even though is not stock anymore.
buddahj said:
Thanks for all the info!!! I'm glad I found this place!!! I was able to get my phone working again. I found this post: http://forum.xda-developers.com/showthread.php?t=1937949 from back in October and found out that I was putting the boot.img in the wrong location. Once I fixed that, I have my phone back. Now I have to get it re-activated because I had to switch back to my Hero because I wasn't sure how long this would take. I hope Sprint will activate it even though is not stock anymore.
Click to expand...
Click to collapse
have your first thanks
lol
the thanks is for using the search function lol
Well now I have another small problem. When I try to use the camera or go into gallery, it says no external storage available. Looks like I'm off to search the forums again for a fix. I'm sure it's something minor.
It looks like it's the internal SD card. Under storage in settings it shows the external card's total space & the 3 GBs used for app data, ect...
When I try and mount the SD card, it says preparing card but doesn't do anything. I think I say something about changing something in TWRP.
Forgot to mention, I can't connect the phone via USB either.
Ha, fixed my SD card/USB issues by following the directions in this thread - http://forum.xda-developers.com/showthread.php?t=1812774
Ok, I had carbon rom on my DNA (Verizon). It was getting buggy on me so I decided to return to ViperDNA. However TWRP continuosly failed to flash the file. No matter what I tried. Eventually I formatted my phone thinking that would help me install it. Well no luck. Now however I still cannot flash any of the roms I have tried and my phone boots straight into recovery. Any ideas on how to fix my phone?
EDIT:
Well, I cannot seem to figure out how to delete this post. However I ended up downloading CM 10.2 through my pc and put it on a usb. Then flashed it from the usb and it worked. I must have had corrupted files
EvolutionXJ said:
Ok, I had carbon rom on my DNA (Verizon). It was getting buggy on me so I decided to return to ViperDNA. However TWRP continuosly failed to flash the file. No matter what I tried. Eventually I formatted my phone thinking that would help me install it. Well no luck. Now however I still cannot flash any of the roms I have tried and my phone boots straight into recovery. Any ideas on how to fix my phone?
EDIT:
Well, I cannot seem to figure out how to delete this post. However I ended up downloading CM 10.2 through my pc and put it on a usb. Then flashed it from the usb and it worked. I must have had corrupted files
Click to expand...
Click to collapse
Are you trying to flash sense 4 viper or sense 5 viper?
Hey, guys, I made a mess.
A long time ago I decided to try out CyanogenMod for my S3 and then everything went well. I got it up and running and it was a cool ROM but I decided to stick to stock at that time. So I looked for a tutorial online and managed to get it back to stock 4.1 Android running well and as usual.
The issue I had then was that I couldn't update my phone from Google's servers anymore. Every time the phone tried to update the firmware I'd get an error, no matter if I tried it through Kies, the phone or whatever. So I decided I'd just install a ROM for a more recent version.
I found a post on a tech blog here in Brazil saying that OmniROM promised they finally had a somewhat stable version of KitKat 4.4
I went on to install it to then find a beautiful, but still very glitchy ROM. My phone froze all the time and it was starting to bother me. My initial plan was to stick to it until it got better, get the daily updates and stuff, but my phone was way too unstable for that too. So I said to myself: "Okay, no problem, so let's get a stable ROM on this little guy."
I downloaded PA 4.3 and proceeded to get it on my phone. That's when the issues started happening. I couldn't find the .zip from CWM no matter where I put it, and my sdcard1 was full because of the previous backup I created (there was a problem with that too, MD5 mismatch, but I didn't lose anything important so that's okay).
Then I did something even more stupid. I figured, why not clean up the backup and get the .zip there, so maybe it'll show up? At that point the sdcard0 (internal storage) was all different and I couldn't find the .zip for the OmniROM, but when I was on CWM it showed up instead of PA's. The problem with that is that I somehow wiped out CWM and now I can't get to recovery. If I boot up my cellphone through OmniROM, it loads up fine but I can't download the ROM Manager or the superuser from the Play Store. I'm trapped with OmniROM and it's working even less well than at first.
What should I do? Is there a way back from this? I'd really like to have my phone running again soon, I need it to keep in touch with my parents since my grandma died recently.
Thank you in advance.
EDIT: Okay, some progress. I remembered that I got CWM on the phone through Odin and went through that again. I have CWM back but still, my internal storage fails to recognize the new .zip files and only shows OmniROM's. The folder is completely different when I connect the phone to my computer. I got to see the .zip files at the sdcard1 but CWM says they're bad files. I'll trust it and redownload/transfer again. We'll see what happens.
EDIT 2: Trapped again. Can't find anything on Google. It sure sucks to be me. I can't even figure out how to get everything back to stock so I can try again. Tried turning USB debugging off but it didn't make a difference. The CWM shows me the two OmniROM .zip files and my computer shows me the PA .zip files. I'm just...
first- try to flash newer cwm based recovey. I suggest philz (is has both Odin / cwm based install):
http://forum.xda-developers.com/showthread.php?t=2002953
after flashing is complete- try to download this rom:
http://forum.xda-developers.com/showthread.php?t=2060403
and check if you can see it.
(you can put it in your internal or external sd, philz can access them both)
Before installing the new rom, I strongly recommend doing a 'wipe to istall new rom', cache wipe and delvik.
good luck
Sent from my GT-I9300 using Tapatalk
Yay, thank you! I'm not trapped anymore. The PA rom I downloaded is still "bad", but that's probably its own fault. I'll wait until NeatROM's download is complete and try with that. I'll edit this if things turn out well.
Thanks again!
EDIT: So, I tried with NeatROM and it also says it's bad. But I only tried on the external storage, so maybe that could be it. My sdcard has been returning some really funky errors when I get it on my computer so I'm worried it might be a bit compromised (and I actually found it at a bus terminal, so it never really worked properly even after formatting).
Thing is when I did the wipe I picked the option that wipes it for a new ROM, so OmniROM is gone. Is there a way to get USB connection through CWM so that I can transfer NeatROM to the internal storage? I only have this one sdcard.
EDIT 2: Finally got it! Thanks so much, amirTor, my S3 is back on track! The sdcard was the bad one, not the file. But the PA ROM didn't work anyway. I might stick to NeatROM or maybe look later. I'm gonna take a week off of all this after so much trouble.
Glad I could help (even though it seems that you pretty much helped yourself...)
1)If you got Sandisk SD card, make sure to follow my post on thread: http://forum.xda-developers.com/showthread.php?t=2614170
2)You can mount your phone to be shown in your pc even when in recovery mode: Mounts and storage-> moun usb mass storage
3)You should definitely stick with neat- the best stock (and aosp) rom there is :good::good::good:
ps- hitting the 'thanks' button will be appreciated :angel:
Done and done!