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.
hey guys, been here since the launch of evo. rooting, flashing, everything.
today i wanted to switch roms. so i went about my normal process...
d/l new ROM
backup current ROM
backup apps
wipe cache and dalvic
flash new ROM
i got stuck on the last step. i went to flash the new ROM (nocturnal 1.3)
it said something along the lines of blah blah is already unmounted. i didnt pay too much attention to it because i was going to restart and try again. long story short, it will only boot to htc white screen and nothing else.
can anyone help me out?
p.s. im on clockwork recovery
PLEASE CLOSE
did you not wipe system and data? I am not super skilled, but maybe it tried to stick the entire ROM into the left over space of the last ROM that is still on there?
It won't boot to recovery? It should boot to recovery
weezymagic said:
hey guys, been here since the launch of evo. rooting, flashing, everything.
today i wanted to switch roms. so i went about my normal process...
d/l new ROM
backup current ROM
backup apps
wipe cache and dalvic
flash new ROM
i got stuck on the last step. i went to flash the new ROM (nocturnal 1.3)
it said something along the lines of blah blah is already unmounted. i didnt pay too much attention to it because i was going to restart and try again. long story short, it will only boot to htc white screen and nothing else.
can anyone help me out?
p.s. im on clockwork recovery
Click to expand...
Click to collapse
The error message you received is going to be the key to understanding the issue that occured. When it says unmounted, it is referring to a specific partition, either /data or /system most likely.
For starters, when it hangs on the htc white screen, this is usually either a kernel or ramdisk issue. If the kernel is known to be good, then it is probably a ramdisk issue. most ramdisk issues relate to a mismatch/incompatibility between the loaded kernel and the ROM.
First suggestion would be to reflash the ROM, clearing /cache and /data.
Second suggestion would be to restore a backup. This will confirm there is nothing wrong with your device hardware wise and you'll know it is a specific issue with the ROM you wanted to load.
Third suggestion, find the exact error, word for word, which occured in recovery and post up in the ROM thread asking if other users of that ROM also encountered, how they handled. Also feel free to post back up here.
When writing the programming behind a custom recovery, the error messages are added in there to help allow users and developers better knowledge of the exact issue so they can work to resolve them. Without the exact error message, it is similar to going to a car shop and saying, some light came on my dash, but I don't know what it was and now the car doesn't work. Fix it? Another words, it is very vague.
Hope the suggestions and tips help! Good luck!
my first instinct was to reflash the backup or new rom again but it wont boot to any rom, recovery or bootloader. it just hangs on the htc white screen
idk what happened but i got into the bootloader through battery pull, power+vol down. i know ive tried that in the past but this time it worked. now im restoring a nandroid from yesterday
weezymagic said:
idk what happened but i got into the bootloader through battery pull, power+vol down. i know ive tried that in the past but this time it worked. now im restoring a nandroid from yesterday
Click to expand...
Click to collapse
are you on twrp 1.0.x ? There is s charging issue where it won't restart right because it thinks It's already in recovery
sent from my EVO 3D via XDA app
weezymagic said:
hey guys, been here since the launch of evo. rooting, flashing, everything.
today i wanted to switch roms. so i went about my normal process...
d/l new ROM
backup current ROM
backup apps
wipe cache and dalvic
flash new ROM
i got stuck on the last step. i went to flash the new ROM (nocturnal 1.3)
it said something along the lines of blah blah is already unmounted. i didnt pay too much attention to it because i was going to restart and try again. long story short, it will only boot to htc white screen and nothing else.
can anyone help me out?
p.s. im on clockwork recovery
PLEASE CLOSE
Click to expand...
Click to collapse
You missed a step. After you wipe dalvik and cache, you ALWAYS need to wipe /system and /data, do a factory reset to make sure, or download a superwipe tool. The ONLY time you don't need to wipe completely is when you're updating your ROM, but even then it is recommended to wipe everything.
Twolazyg said:
You missed a step. After you wipe dalvik and cache, you ALWAYS need to wipe /system and /data, do a factory reset to make sure, or download a superwipe tool. The ONLY time you don't need to wipe completely is when you're updating your ROM, but even then it is recommended to wipe everything.
Click to expand...
Click to collapse
Agreed^^^^^
I lurked around the GlitchV13 forum for a good long time and didn't find an answer to this.. and because I've only been lurking for about a year I wasn't able to post anything, so it's about time I guess.
I'm having problems with the GlitchV13 kernel. Maybe I'm just being dumb and don't see something here. some help would be greatly appreciated.
I flashed GlitchV13 on my CM7.1 using CWM 5.0.2.7. No problems at all. Running great for two days. Suddenly, my phone won't connect to wifi. Cycled airplane mode and nothing popped up, so I did a reboot.. annnd got stuck in a bootloop between the CM splash and my lockscreen (wtf). Rebooted again, and now I'm stuck on the CM7 screen. Tried to Odin CWM4, still no bueno, and I get a "E:Can't mount recovery/log/"blahblahblah.
Admittedly, this happened one time before- I did a clean install from stock. Then I got gutsy and flashed GV13 again. Any idea why this is happening? After I flashed Glitch I didn't touch any other recoveries, nor did I try to push anything with Odin or Heimdall.
I really just don't wanna flash back to stock again, and a new solution to why this is happening would be super!
Thanks in advance.
EDIT: Got it. Glitch comes packaged with 4.x CWM, while CM7 comes packaged with 5.0.2.7. Any way to reconcile the two? Worth it to push 4.x over 5.x, flash Glitch then backup so I don't have to do a full restore to CM7?
I had the wifi problem on the stock kernel once, so I dont think that problem is with Glitch.
I also just flashed the latest kernel version and they have updated CWM to 5.0.2.7.
That being said are you sure the recovery is making this much trouble on the phone? Usually it doesn't make a difference (besides backups and whatnot).
The glitch recovery has a few extra features that the CM7 recovery does not.
one being able to wipe dalvik and cache at the same time. (very minor but its more convenient)
I personally think its worth it.
So here is one for ya.
I can't access my SD Card at all with this http://forum.xda-developers.com/showthread.php?p=25816870#post25816870 rom installed. I click to mount SD card and nothing happens. In recovery I can access the SD card backups etc
I find it strange. Although I do have to ask, I have been having this weird problem. I have Clean Rom 4.3 Installed (ICS) and I have been getting some random reset's and slow this or that. So I saw 4.5 was out - It literally reset everyime your open something and I mean anything Bam reset. However I installed the above rooted bleh bleh stock os (I do not have s-off so I used the PH img) I made sure I had no other boot images on there. Installed setup got everything ready. I have gotten 3 resets in 11 mins so far so now I backed up to Clean rom 4.3 and I have no idea what to do.
I also did the following:
Flashed back to STOCK o.s.
Then Downloaded the above linked rom, cleared data (everything) installed software patch and rom reset back up and same problem. I have been flasing rom's on this phone for a while now and this is the first time no matter what that I get these crashes and resets. Did I miss something?
You really should s-off that puppy. It is pretty easy, and will get you out of messes.
Sent from my ADR6425LVW using Tapatalk 2
Jason L said:
So here is one for ya.
I can't access my SD Card at all with this http://forum.xda-developers.com/showthread.php?p=25816870#post25816870 rom installed. I click to mount SD card and nothing happens. In recovery I can access the SD card backups etc
I find it strange. Although I do have to ask, I have been having this weird problem. I have Clean Rom 4.3 Installed (ICS) and I have been getting some random reset's and slow this or that. So I saw 4.5 was out - It literally reset everyime your open something and I mean anything Bam reset. However I installed the above rooted bleh bleh stock os (I do not have s-off so I used the PH img) I made sure I had no other boot images on there. Installed setup got everything ready. I have gotten 3 resets in 11 mins so far so now I backed up to Clean rom 4.3 and I have no idea what to do.
I also did the following:
Flashed back to STOCK o.s.
Then Downloaded the above linked rom, cleared data (everything) installed software patch and rom reset back up and same problem. I have been flasing rom's on this phone for a while now and this is the first time no matter what that I get these crashes and resets. Did I miss something?
Click to expand...
Click to collapse
I assume you're always wiping data and cache.
Have to tried Fix Permissions? I don't know if this rom has it in it's settings, but using others I've corrected some weirdness by wiping the cache and then running fix permissions.
Were you seeing the same thing with the stock rom? Or just using clean rom? Might try a different rom for a bit to see if the issues follow you there.
S-OFF isn't going to help you with this. It's perfectly fine to flash your boot image outside of Aman-Ra. I do it all the time.
Are you wiping everything between flashes?
I recommend using this - http://forum.xda-developers.com/showthread.php?t=1562176&highlight=clean
Flash it first and it wipes the needed partitions clean.
If you're still on the GB firmware, you need to flash the old firmware patch after the rom install also to get SD card access.
If none of the above helps and you're still on the GB firmware, set the phone back to stock using the GB RUU, otherwise you will have to s-off it so you can do the same.
Yep full wipes between flashes. I didn't keep the stock Rom for more than about 20 mins.
I didn't see a way with the debloated stock New leak to fix permissions. But with the 4.5 clean Rom I did that and it made no difference.
Delete
Sent from my ADR6425LVW using Tapatalk 2
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Thanks for the reply!
I didn't check the MD5 last night but I did just now and it matches.
I did a cache wipe the first time but not a system wipe. Then I started getting more desperate and tried reinstalling w/ system wipes and factory resets, but it didn't change anything.
No, I didn't change the ROM. Doing the Bootloader unlock exploit was about the absolute maximum of my technical abilities! The only thing I know I did wrong was that I didn't downgrade to the old boot version the first time (mainly because the wifi thing sounded inconsequential and I didn't want to learn the procedure if I didn't have to).
Anyway, I just tried Ultimate KangBang and it seems to work--no error messages so far. I don't know what I did wrong, but hopefully this keeps working!
IceDragon59 said:
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
Click to expand...
Click to collapse
andybones said:
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Click to expand...
Click to collapse
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
franklin411 said:
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
Click to expand...
Click to collapse
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
in the future it is always good practice to backup(nandroid) your current ROM. I have been burned too many times, always do a nandroid before you do anything in recovery.
your photos are normally saved to the SD, flashing ROMs or wiping the system will not delete them
andybones said:
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
Click to expand...
Click to collapse
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
franklin411 said:
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
Click to expand...
Click to collapse
na the name has nothing to do with it. it can be named whatever.
im guessing the wipe worked.
franklin411 said:
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Click to expand...
Click to collapse
weird, i was having the same problem with the same processes stopped working. i wiped cache dalvik and system but not factory reset. once i factory reset, it worked fine. i figured a system wipe would have been enough....