A day ago I flashed the highly unstable Viper3D ROM successfully (if you count random bootloops successful). Ever since then I've tried flashing CM10 and I can't do it successfully. That's not the only problem; today, I found out I'm unable to flash ANY AOSP ROMs. I figured out that Viper3D actually changes hboot by itself and I changed mine to 1.04. I even changed recoveries from 4EXT to TWRP V2.3.1.0 (which I'm currently using) and I can't flash CM10. What's weird is... the CM10 boot animation is the only thing that shows, even when flashing a different ROM that has a different boot animation. Does anybody know what I'm missing here? I've spent 5 hours on this and yet I'm still unsuccessful.
Chronosin said:
A day ago I flashed the highly unstable Viper3D ROM successfully (if you count random bootloops successful). Ever since then I've tried flashing CM10 and I can't do it successfully. That's not the only problem; today, I found out I'm unable to flash ANY AOSP ROMs. I figured out that Viper3D actually changes hboot by itself and I changed mine to 1.04. I even changed recoveries from 4EXT to TWRP V2.3.1.0 (which I'm currently using) and I can't flash CM10. What's weird is... the CM10 boot animation is the only thing that shows, even when flashing a different ROM that has a different boot animation. Does anybody know what I'm missing here? I've spent 5 hours on this and yet I'm still unsuccessful.
Click to expand...
Click to collapse
I get bootloops with CM10 too. Usually when I reboot from the ROM. I'm forced to fullwipe or install a backup. Sometimes CM10 ROMs won't even boot after a fresh install. Always stuck on the bootanimation. Same thing regardless of firmware, hboot or ROM.
I was actually going to post this question because I saw a few others had the same or similar issues. I wonder if it's a common thing.
DarkRazorZ said:
I get bootloops with CM10 too. Usually when I reboot from the ROM. I'm forced to fullwipe or install a backup. Sometimes CM10 ROMs won't even boot after a fresh install. Always stuck on the bootanimation. Same thing regardless of firmware, hboot or ROM.
I was actually going to post this question because I saw a few others had the same or similar issues. I wonder if it's a common thing.
Click to expand...
Click to collapse
I had CM10 -- DisarmedToaster 2.6.7 -- for months and it was working. The problem occurred after flashing Viper3D.
Not sure if your post was a troll or not, but... Hboot actually matters a lot when it comes to CM10.
I discovered through 4EXT that some of my internal partitions are not accessible. I'm going to follow the guide on 4EXT and on-top of that, I will turn on Smart Flash. I formatted my SD card, but "cache is still accessible.
Chronosin said:
A day ago I flashed the highly unstable Viper3D ROM successfully (if you count random bootloops successful). Ever since then I've tried flashing CM10 and I can't do it successfully. That's not the only problem; today, I found out I'm unable to flash ANY AOSP ROMs. I figured out that Viper3D actually changes hboot by itself and I changed mine to 1.04. I even changed recoveries from 4EXT to TWRP V2.3.1.0 (which I'm currently using) and I can't flash CM10. What's weird is... the CM10 boot animation is the only thing that shows, even when flashing a different ROM that has a different boot animation. Does anybody know what I'm missing here? I've spent 5 hours on this and yet I'm still unsuccessful.
Click to expand...
Click to collapse
Don't feel bad buddy. I can't get past splash screen on any AOSP roms either, and I have not flashed Viper3D, and have always been on the 1.04 ENG h-boot, so that's not the problem. Like you, I've flashed different versions of recovery, reflashed my h-boot, even fastboot flashed the AOSP boot image and confirmed that it did flash. In fact, I haven't changed anything that would cause this, since I last successfully ran AOSP a few weeks ago. No radios, firmware.....nothing. Wish I had some answers for you, but I'm in the same boat and haven't found the solution yet.
hockeyfamily737 said:
Don't feel bad buddy. I can't get past splash screen on any AOSP roms either, and I have not flashed Viper3D, and have always been on the 1.04 ENG h-boot, so that's not the problem. Like you, I've flashed different versions of recovery, reflashed my h-boot, even fastboot flashed the AOSP boot image and confirmed that it did flash. In fact, I haven't changed anything that would cause this, since I last successfully ran AOSP a few weeks ago. No radios, firmware.....nothing. Wish I had some answers for you, but I'm in the same boat and haven't found the solution yet.
Click to expand...
Click to collapse
I got it working! Woot!
And you should get: PG86IMG_Revolutionary_1.40.1100-hboot.zip
Turn on SmartFlash for 4EXT. Format cache, format SD card using computer (Default allocation). Reboot recovery from 4EXT. Then, click on every single option on the wipe menu. Even full wipe, except for SD card. Then, flash CM10 DisarmedToaster (latest), I did custom, no PA, and unchecked all except Titanium Backup. Then flash Gapps 4.2. I rebooted, and at first it boot looped once around the HTC logo then it loaded and worked.
And "buddy", next time you shouldn't give up so easily or rely on useless forums like this.
Chronosin said:
I got it working! Woot!
And you should get: PG86IMG_Revolutionary_1.40.1100-hboot.zip
Turn on SmartFlash for 4EXT. Format cache, format SD card using computer (Default allocation). Reboot recovery from 4EXT. Then, click on every single option on the wipe menu. Even full wipe, except for SD card. Then, flash CM10 DisarmedToaster (latest), I did custom, no PA, and unchecked all except Titanium Backup. Then flash Gapps 4.2. I rebooted, and at first it boot looped once around the HTC logo then it loaded and worked!
And "buddy", next time you shouldn't give up so easily or rely on useless forums like this.
Click to expand...
Click to collapse
Congratulations.....I didn't give up either. I just haven't found the cause of the problem yet. Nothing revealing in recovery logs or last_kmsg....and there's no way I'm dumping and formatting a 64gig card that's nearly full lol. SmartFlash shouldn't have an impact either if you're s-off and I've already confirmed boot.img flashed..... I will try Disarmed Toaster again tonight though, since that was the last AOSP rom that I was able to boot. Multiple versions of AOKP and Gangnam Style have been what's failed on my device.
hockeyfamily737 said:
Congratulations.....I didn't give up either. I just haven't found the cause of the problem yet. Nothing revealing in recovery logs or last_kmsg....and there's no way I'm dumping and formatting a 64gig card that's nearly full lol. SmartFlash shouldn't have an impact either if you're s-off and I've already confirmed boot.img flashed..... I will try Disarmed Toaster again tonight though, since that was the last AOSP rom that I was able to boot. Multiple versions of AOKP and Gangnam Style have been what's failed on my device.
Click to expand...
Click to collapse
Do you have 4EXT installed?
Chronosin said:
Do you have 4EXT installed?
Click to expand...
Click to collapse
Yeah, I've been using 4 ext since I can't remember when. I did switch to TWRP the other day in an attempt to get AOSP to boot, but went right back to 4 ext. I just tried Agrabren's last CM10 update too...... Also failed to boot. I don't even get past the splash screen. Not the end of the world just frustrating that there's nothing of use in the logs, I've checked my partition structure, checked for bad cylinders....There's not even a clue as to what's going wrong.
hockeyfamily737 said:
Yeah, I've been using 4 ext since I can't remember when. I did switch to TWRP the other day in an attempt to get AOSP to boot, but went right back to 4 ext. I just tried Agrabren's last CM10 update too...... Also failed to boot. I don't even get past the splash screen. Not the end of the world just frustrating that there's nothing of use in the logs, I've checked my partition structure, checked for bad cylinders....There's not even a clue as to what's going wrong.
Click to expand...
Click to collapse
You have a corrupted SD card for sure.
Chronosin said:
You have a corrupted SD card for sure.
Click to expand...
Click to collapse
You know, I ran a file system check and partition check on my sd card, when I was checking all of the device partitions and that was all fine, but I never stopped to consider the possibility that there's some data on the card somewhere pissing off the AOSP roms. I suppose it wouldn't kill me to find another sd floating around somewhere and give that a shot. Bizarre that it's only affecting CM based roms though.
***Edit***
I kind of expected as much, but swapping out my sdcard for a freshly formatted one, did not fix the problem.
Related
I had rooted my TB using TB auto root, and flashed Gingeritis 3d when I first got my TB last month.
I wanted to try out an aosp rom like CM7.
So I dled the rom, dled zoom kernel, and got the MR2.5 radio to be sure.
I flashed the radio first, booted into Gingeritis just fine with signal.
So I then rebooted into recovery, did a factory wipe, dalvik, and cache.
I then hit instal zip from sd, found the zoom kernal zip, installed it, and then did the same for the CM7 rom. But when I reboot, It just sits on the white HTC splash screen.
I had tried it through ROM Manager last week, and it had done the same thing. I thought it was the kernal, but as I flashed the kernel this time.. and it's still doing it. I don't know whats wrong.
Can someone tell me what I'm doing wrong?
I'd really like to get CM7 running on this thing.
Thanks guys
Deviant6 said:
I had rooted my TB using TB auto root, and flashed Gingeritis 3d when I first got my TB last month.
I wanted to try out an aosp rom like CM7.
So I dled the rom, dled zoom kernel, and got the MR2.5 radio to be sure.
I flashed the radio first, booted into Gingeritis just fine with signal.
So I then rebooted into recovery, did a factory wipe, dalvik, and cache.
I then hit instal zip from sd, found the zoom kernal zip, installed it, and then did the same for the CM7 rom. But when I reboot, It just sits on the white HTC splash screen.
I had tried it through ROM Manager last week, and it had done the same thing. I thought it was the kernal, but as I flashed the kernel this time.. and it's still doing it. I don't know whats wrong.
Can someone tell me what I'm doing wrong?
I'd really like to get CM7 running on this thing.
Thanks guys
Click to expand...
Click to collapse
I'm not familiar with cm7 on this phone. I enjoy sense roms so I haven't played with cyanogen.
Are you positive the kernel is compatible with asop roms? If yes, download the ROM again and verify the md5 after you place it on the phone.
Also make sure you delete the radio pg05img.zip or whatever the correct spelling is from the phone as well. Sounds like you already did that but just making sure.
Flash from recovery not ROM manager.
Sent from my Synergy driven Thunderbolt...
I'm restoring it now.
I had tried flashing through RM 3 times last week and got the same issue.
And I'm pretty sure the kernels I flashed are aosp kernels.
I searched for CM7 kernels, and I know for sure the zoom one is an aosp kernel.
I've found lots of people with the same issue online, but found no fixes.
I don't know what to do.
I really need some help here guys. someone experienced flashing cm7 or aosp roms.
Does it have something to do with me trying to go from a sense rom to a aosp rom?
I thought all I had to do was change the kernel...?
If someone can give me a link to a cm7/kernel/radio combo they KNOW works, I would really really appreciate it.
Has anyone gotten through this issue before?? If so, what did you do to get past it!?!?!?
Are you positive you downloaded cm 7 for the thunderbolt and not some other device? I would try wiping everything from recovery (system, data, etc.) then install just the rom and see if it boots. And, as stated above, check the MD5. Could just be a corrupt file.
Sent from my ADR6400L using Tapatalk
bpyazel said:
Are you positive you downloaded cm 7 for the thunderbolt and not some other device? I would try wiping everything from recovery (system, data, etc.) then install just the rom and see if it boots. Are you letting it sit long enough? First boot of a fresh rom can take a while (5 - 10 minutes).
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Well, I've searched around and found: update-cm-7.1.1-Thunderbolt-signed.zip
which I assume is the correct one.
And I know the first boot takes a good while, but it doesn't sit at the splash screen, they take a long time during the boot animation. Which mine doesn't even get to.
And I've let it sit 15+mins. so it's not that.
I'm trying it through RM this time (again) and even though I had the most up to date version of it, I reflashed RM (hoping that was the issue) and i downloaded and im installing CM7 from RM now.
EDIT:
I found the issue. Well, the only thing I did differently this time was to reflash Clockwork Mod Recovery from Rom Manager.
I had the most current one already, but I did it anyways, and redid all the steps, and now I'm in.
So I don't know if it was corrupted, or w/e, but that seemed to do it.
So for everyone else getting stuck at the white splash screen after flashing: Restore your phone to the previous rom, open Rom Manager, and hit the very top button: Flash Clockwork Mod Recovery (even if its allready updated)
After that, do your flash like normal.
It solved my issue and everything went fine.
Hi guys, so i decided to install the new CM10 so i already had root, i unlocked using the official tool, then installed CWM from Rom manager.
I then downloaded CM10 and GAAPS and kept them in a folder and also copied them to an sd card for safety.
I booted into CWM sucessfully, took a deep breath, then did a full wipe/factory restore, then wiped Cache, then wiped Dalvik Cache.
Then i proceeded to TRY to flash CM10.......... Firstly, CWM didn't list my external SD Card so i selected from the one i had saved on the internal storage.
It began to do the install then failed stating something about symlinks??? I retried the install and got the same thing.
I rebooted the Prime and now it's just stuck on the Eee Pad splash screen with "The Device Is Unlocked" written in the top left corner and it wont do anything else.............
I can reboot into CWM but how can i fix this and get CM10 installed??
PLEASE help!?!?!?!?!?
Thanks in advance.
Currently, no recovery can access external memory of any sort. Did you make a backup? Is it in the internal memory? Make sure you can flash back to your original settings BEFORE trying to flash something as experimental as CM10.
Please remember any Jelly Bean roms are highly experimental, and probably won't work correctly for everyone.
Read this thread for more help:
http://forum.xda-developers.com/showthread.php?t=1514088
I thought I replied to my own post shortly after the original post. I ended up rebooting into CWM and starting over again from the start and everything went smoothly. I endedup not liking the fact that flash and YouTube aren't supported yet so I flashed CM9 instead and I'm loving that.
Predtechhacker said:
I thought I replied to my own post shortly after the original post. I ended up rebooting into CWM and starting over again from the start and everything went smoothly. I endedup not liking the fact that flash and YouTube aren't supported yet so I flashed CM9 instead and I'm loving that.
Click to expand...
Click to collapse
Good to hear. One last advice is to use TWRP instead of CWM. CWM has issues with the prime while TWRP is more stable.
Predtechhacker said:
I thought I replied to my own post shortly after the original post. I ended up rebooting into CWM and starting over again from the start and everything went smoothly. I endedup not liking the fact that flash and YouTube aren't supported yet so I flashed CM9 instead and I'm loving that.
Click to expand...
Click to collapse
so how many time had u gone back then tried it.... i have the same problem i tried it like 10 times but it still stuck
what step did u do
I'm stuck in the same predicament! Did you just keep trying, and it finally worked????
I have confirmed that I have root access and that my bootloader is unlocked
I have tried flashing CWM recovery via rom manager and various img files found throughout this site and others.
Despite this, when I boot into cwm I get the android guy with the yellow ball
If I hit vol up and down I get only a few options:
Bgackup and restore, reboot, apply update, whipe data factory reset, whipe cache partition.
No advanced (this is one I've seen mentioned but didn't see on my device)
But as long as I got that far, I went through the steps to install CM9.
I whiped data then cache
Applied the CM9 zip
then rebooted
When my phone came back on I still have moto gingerbread and it just wants me to relogin to blur and sign in to google.
Also tried Another SD card with the same results. CWM couldn't see any zips on the cards after reentering cwm after a reboot. Reformatting the cards and trying again produced the same results.
What am I missing here? I've followed and refollowed letter by letter with all the guides I've been seen.
Thanks for any help and I apologize for any newb stuff as this is my first attempt at android roms.
Well it looks like this is magically solved now.
After TWRP failed earlier I decided to go back into fastboot and did a erase recovery, reboot, then reflash twrp
Then tried booting into it and it worked!
So I went back into fastboot and flashed cwm instead since I'd prefer the non touch recovery.
Thanks for all the tips
Please remember to post questions in the Q&A forum.
I honestly don't know what's wrong. It looks like your doing everything properly.
seem like you're not with CWM installed on your device..
try to put another one like TWRP and see what happens
You are certain your bootloader is unlocked? (you see "unlocked" on the Moto splash screen)
First, try to fix permissions from Rom Manager.
If that doesn't work fastboot flash the most recent recovery. Go here and get the latest version.
I would advise against using ROM manager. It's been known to cause many issues.
ravilov said:
I would advise against using ROM manager. It's been known to cause many issues.
Click to expand...
Click to collapse
Oh ravilov, you and your crazy stories. I've been using Rom Manager since the day I rooted my phone. Never had one problem (well, except for the way koush does the premium license).
Make sure you're choosing "install zip from SD card" not "install update from SD card".
LÄvLab / HostileSlothRecords
ravilov said:
I would advise against using ROM manager. It's been known to cause many issues.
Click to expand...
Click to collapse
ROM Manager is perfectly fine for fixing permissions.
upndwn4par said:
Oh ravilov, you and your crazy stories. I've been using Rom Manager since the day I rooted my phone. Never had one problem (well, except for the way koush does the premium license).
Click to expand...
Click to collapse
It was reportedly the culprit of randomly appearing ".nomedia" files on some ROMs. After that I don't think I'd want to trust it.
Some people also had problems installing stuff through it, no matter what they tried. Once they switched to cmd/fastboot/manual install, everything worked fine.
So I'm not exactly pulling stuff out of my butt here.
I also don't really like it personally, I always remove it if it comes bundled with a ROM. But that's just me. To each their own. If it's working fine for you, by all means keep using it.
ravilov said:
It was reportedly the culprit of randomly appearing ".nomedia" files on some ROMs. After that I don't think I'd want to trust it.
Some people also had problems installing stuff through it, no matter what they tried. Once they switched to cmd/fastboot/manual install, everything worked fine.
So I'm not exactly pulling stuff out of my butt here.
I also don't really like it personally, I always remove it if it comes bundled with a ROM. But that's just me. To each their own. If it's working fine for you, by all means keep using it.
Click to expand...
Click to collapse
If I remember correctly, that was for epinter's and joker's CM10 ROMs. And it was never even close to proven that CWM was the culprit. Doesn't make sense that CWM is to blame for suddenly doing random stuff. Especially since both of those ROMs have had serious media issues since day one.
Anyway, I'm not saying that CWM is perfect - it's not. But RomRacers recovery is unsupported, and I try to never use unsupported software. TWRP is nice, but I don't like touch recoveries and old CWM backups are useless. Anyway, to each his own.
upndwn4par said:
If I remember correctly, that was for epinter's and joker's CM10 ROMs. And it was never even close to proven that CWM was the culprit. Doesn't make sense that CWM is to blame for suddenly doing random stuff. Especially since both of those ROMs have had serious media issues since day one.
Anyway, I'm not saying that CWM is perfect - it's not. But RomRacers recovery is unsupported, and I try to never use unsupported software. TWRP is nice, but I don't like touch recoveries and old CWM backups are useless. Anyway, to each his own.
Click to expand...
Click to collapse
Um...
I'm talking about ROM manager, not CWM. CWM is great, I'm using it too (well, I'm using RomRacer's recovery which is CWM-based).
I don't mind using older and possibly unsupported software if it's this stable and works without any problems and glitches.
I'm going to assume that was a typo and you really meant ROM manager.
But yeah, ".nomedia" files don't appear out of nowhere. People were unable to find their media files and they were indeed blaming the ROM for doing that. Then someone realized it's due to some ".nomedia" files being created randomly. Then people were deleting all such files but the files would appear again. And then someone noticed removing ROM manager made the madness stop. Now I will admit this is not proof enough, but it really seems very likely that ROM manager was to blame. I think nobody had any problems with media files since.
Oh, and as for the problem OP is mentioning... No, this is not related to ".nomedia" files, and frankly I have no idea what's going on there... :dunno:
ravilov said:
Um...
I'm talking about ROM manager, not CWM. CWM is great, I'm using it too (well, I'm using RomRacer's recovery which is CWM-based).
I don't mind using older and possibly unsupported software if it's this stable and works without any problems and glitches.
I'm going to assume that was a typo and you really meant ROM manager.
But yeah, ".nomedia" files don't appear out of nowhere. People were unable to find their media files and they were indeed blaming the ROM for doing that. Then someone realized it's due to some ".nomedia" files being created randomly. Then people were deleting all such files but the files would appear again. And then someone noticed removing ROM manager made the madness stop. Now I will admit this is not proof enough, but it really seems very likely that ROM manager was to blame. I think nobody had any problems with media files since.
Oh, and as for the problem OP is mentioning... No, this is not related to ".nomedia" files, and frankly I have no idea what's going on there... :dunno:
Click to expand...
Click to collapse
Yeah, you know what I meant. :cyclops:
I still think it is more likely that the ROM made RM go wacky than the other way around. Especially with the history of JB ROM media issues.
ravilov said:
Um...
I'm talking about ROM manager, not CWM. CWM is great, I'm using it too (well, I'm using RomRacer's recovery which is CWM-based).
I don't mind using older and possibly unsupported software if it's this stable and works without any problems and glitches.
I'm going to assume that was a typo and you really meant ROM manager.
But yeah, ".nomedia" files don't appear out of nowhere. People were unable to find their media files and they were indeed blaming the ROM for doing that. Then someone realized it's due to some ".nomedia" files being created randomly. Then people were deleting all such files but the files would appear again. And then someone noticed removing ROM manager made the madness stop. Now I will admit this is not proof enough, but it really seems very likely that ROM manager was to blame. I think nobody had any problems with media files since.
Oh, and as for the problem OP is mentioning... No, this is not related to ".nomedia" files, and frankly I have no idea what's going on there... :dunno:
Click to expand...
Click to collapse
I remember this happening when rom manager updated. Then a few days later they put another update distinctly saying "fixed problem of rom manager adding .nomedia to internal and external sd" so yes rav is right that rom manager was the culprit THEN. However that being said, I had tried a jb rom (can't remember which) that added those .nomedia files to my internal and external so you both could be correct in your assumptions.
EDIT: in the changelog for ROM manger here https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager it shows that it did place those .nomedia files.
Yes, I am certain that my phone is unlocked or at least I think I am since it says "unlocked" in the corner when I turn it on
I didn't want to sign back into everything quite yet so I haven't been able to try the rom manager fix permissions thing yet.
I flashed the TWRP recovery instead of the CWM one and got the same result when booting into the recovery so I assume that neither CWM or TWRP was successfully installed.
Shouldn't flashing these with fastboot get them in there? (technically tried installing from rom manager once too)
drsatan316 said:
Yes, I am certain that my phone is unlocked or at least I think I am since it says "unlocked" in the corner when I turn it on
I didn't want to sign back into everything quite yet so I haven't been able to try the rom manager fix permissions thing yet.
I flashed the TWRP recovery instead of the CWM one and got the same result when booting into the recovery so I assume that neither CWM or TWRP was successfully installed.
Shouldn't flashing these with fastboot get them in there? (technically tried installing from rom manager once too)
Click to expand...
Click to collapse
Yes, fastboot should be installing recovery properly.
I see three possibilities:
1) Something happened during the unlock process, so despite seeing "unlocked" you are not fully unlocked.
2) Fastboot is not writing recovery recursively
3) You have a hardware problem
I would try the following first:
1) Check to make sure you have the correct drivers installed on your PC and you have the most recent version of fastboot
2) Erase recovery with fastboot
3) Re-flash recovery with fastboot
Next I would try unlocking your bootloader again
Did you ever solve your problem?
Yes I got it working now.
TWRP booted after I did a fastboot erase and reflashed the recovery.
So I then reflashed CWM and that booted.
When I actually went to install a ROM a few days later it didn't boot again so I reflashed and ran the recovery on the next reboot OK again.
I was able to successfully get Joker's CM10 flahsed and running.
Not sure why I'd have to reflash every time I want to run the recovery but I think that that isn't a big deal for me anymore as this was just a test and this is no longer my primary device.
Thank you all for the help
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
I could use some advice on any options I have for trying to salvage this Rezound. Here is what I know:
The Symptoms:
-Was completely stock and actively used phone
-Charging port began misbehaving. I believe it may be loose/damaged. It will only charge reliably on one particular USB cable (an Amazon Basics, but only one of my dozen or so of those)
-Started randomly rebooting
-Did a factory reset, seemed to help for a while, then it started rebooting again
-It started getting stuck in a bootloop. HTC screen up ~2s -> black ~0.2s -> HTC screen up ~28s -> black ~5s -> repeat. Does this for a variable amount of time, sometimes minutes, sometimes hours before it will actually boot all the way into the OS
-If it does boot, it usually does not last long before it reboots and will typically get stuck again
The Facts:
-I can into bootloader with no issues
-Because I can get into bootloader, I went ahead and unlocked and flashed TWRP 2.6.3.0
-I can get into TWRP and use all of it's functions reliably
-I decided to try wiping data and cache then system several times, flashing a custom ROM (Global_OTA_RED_DESENSED-v1.0) in TWRP and then flashed boot.img with fastboot, but the new ROM has the same issue. In fact I've yet to boot all the way into the ROM
-Does the same thing with the SD card and SIM card removed
My Guesses:
Based on the fact that it is rock solid in the bootloader and in recovery, I thought that it was possibly corruption on system or boot, which is why I tried to install a custom ROM. Now I'm leaning towards bad memory, either where system or boot reside, possibly data or even RAM, perhaps caused by electrical damage from the charge port issues. I just don't understand why I've not seen any sort of read/write errors while doing anything with fastboot or recovery.
At this point I don't know what to do beyond throwing it out. If anyone has any fresh ideas for salvaging this thing, I'd appreciate it.
If not, any ideas for replacing are also appreciated. A new phone isn't really in the budget at the moment, particularly because I desperately want to get away from Verizon (most likely will lose unlimited data if we I start swapping and don't really have $600-$700 to throw around at the moment. I have 4 lines to move and the Rezound line is on contract, so I'm sort of feeling the rock one side and a hard place on the other.
Thanks in advance, folks!
Because you are staying in ICS at the moment and not playing with JB/KK, try booting up Amon Ra recovery, it has an option to wipe/format the /boot partition (TWRP does not) so wipe that and everything else (except external SD) at lease twice... then, assuming you are on HBoot 2.28 and 0123/0124 radios, flash this and the boot image: http://forum.xda-developers.com/showthread.php?t=2260154 it is a completely stock build with full bloat, only root is added, and see if it comes up. This ROM is my go to ROM for issues when an RUU is not possible.
acejavelin said:
Because you are staying in ICS at the moment and not playing with JB/KK, try booting up Amon Ra recovery, it has an option to wipe/format the /boot partition (TWRP does not) so wipe that and everything else (except external SD) at lease twice... then, assuming you are on HBoot 2.28 and 0123/0124 radios, flash this and the boot image: http://forum.xda-developers.com/showthread.php?t=2260154 it is a completely stock build with full bloat, only root is added, and see if it comes up. This ROM is my go to ROM for issues when an RUU is not possible.
Click to expand...
Click to collapse
Thanks for the suggestion. I had let the phone sit turned off all afternoon to charge and tried this after work. I grabbed Amon Ra from http://forum.xda-developers.com/showthread.php?p=37362226, made sure to wipe boot in excess and installed the ROM you linked. It booted up on the first try unlike the last ROM, and I've been able to load some things on it and delete some bloat for a bit with no reboots. I've even powered off and went back into recovery to do a backup, and had a successful reboot afterwards. I don't know if it was wiping boot that did it, but I hope it holds. I'll keep you posted, and either way, thanks again.
Still going. Getting a random reboot here and there, but I've yet to have it get stuck while booting. Now I'm trying to decide if I want to take my chances and try to get S-off.
"Haus" said:
Still going. Getting a random reboot here and there, but I've yet to have it get stuck while booting. Now I'm trying to decide if I want to take my chances and try to get S-off.
Click to expand...
Click to collapse
Are you still on the stock ROM from above? You will need to unlock with Linux if you are, otherwise you will need a custom ROM (actually, an unsecure kernel) to use rumrunner for Windows.
acejavelin said:
Are you still on the stock ROM from above? You will need to unlock with Linux if you are, otherwise you will need a custom ROM (actually, an unsecure kernel) to use rumrunner for Windows.
Click to expand...
Click to collapse
I'm still on the stock ROM. Unfortunately it quit booting again.
"Haus" said:
I'm still on the stock ROM. Unfortunately it quit booting again.
Click to expand...
Click to collapse
Hmm... Honestly looking like a hardware issue... Sorry bro
Sent from my Nexus 4 using Tapatalk