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.
Related
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
this is what i get for oding late at night but i managed to do something very very stupid I odined my phone with a one click package for my captivate
I've been able to get the phone back in mostly working order now though.. but i feel in my gut something still may not be right.
here is where i got the package
http://forum.xda-developers.com/showthread.php?t=1300843
This below is what version i accidently installed.
I897UCKI2 Android 2.3.5 Gingerbread
With Bootloaders - Link to thread - Second Post [With CWM Injected Kernel from Boog]
so after i made this mistake.. (noticed my phone had a at&t bootscreen an wouldn't load) I went forth an flashed stock firmware avail for aiotools for the vibrant an then installed the stock froyo bootloader
I'm hoping everything is right in its place well except once i get cm9 flashed it boots up an shows a EU error so i freak yank the battery an odin this phone back into the stoneage an well... surprisingly.... my internal memory is 100% there O.O
anyways current issue is not being able to get cm7 to install though i'm probably missing something due to being tired anyways..
help sugestions banter calling me a noob I just want to make sure i did possibly everything to fix this mistake.
pintek said:
I'm hoping everything is right in its place well except once i get cm9 flashed it boots up an shows a EU error so i freak yank the battery an odin this phone back into the stoneage an well... surprisingly.... my internal memory is 100% there O.O
Click to expand...
Click to collapse
You,my friend, dodged a bullet here.
pintek said:
anyways current issue is not being able to get cm7 to install though i'm probably missing something due to being tired anyways..
Click to expand...
Click to collapse
Well, when you say you are not able to get CM7 to install, what exactly is it doing?
Are you getting thrown into a bootloop (caused by CWR mismatch and pretty common)? If so, pull battery and boot into recovery and re-flash CM7 over itself again. No wipe. Then reboot.
You may have to flash a different kernel, like glitch or something like that. But try the above first. Should work for you. Does it still say ATT when you boot up?
Lucky for you, everything is good, but if you want to flash a GB or higher ROM, i would suggest you flash the bootloaders in this thread: http://forum.xda-developers.com/showthread.php?t=1117990
After that just flash CM9, and you *should* be good, if not, try flashing it again with wiping data, cache, and dalvik cache. I guarantee that will work.
I ended up having to format both SD cards an retrying install custom rom via aio tool an with luck was able to get cm7 installed then cm10 an i dno't have the ime error everyone else seams to have . I did before this flash the gb bootloader over this cause it was the only thing that managed to remove the at&t splash screen before the kernal.
Lesson I learned....
remember that the vibrant you use aio tool not a premade pack >.<
an ya i do own both phones so this does complicate things now an then <,<
I also have both devices. Set up two different folders on your pc, one marked i897 and the other t959. I also add i897 or t959 to any files that could possibly get mixed up in Odin.
Its peanut butter jelly(bean) time...
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.
This will help anyone who keeps having flashing issues.
More detailed instructions in my GUIDE!
http://forum.xda-developers.com/showthread.php?t=2295557
THIS IS ONE QUICK/SIMPLE ERROR FREE ROM FLASHING PROCEDURE
This should eliminate a few posts saying, stuck in download mode, stuck at logo. just vibrates and them MANY other issues that somehow, everyone seems to find.
Here is my quick rom flashing process I use ALWAYS (yes always)
THINGS YOU NEED ON extSDCARD
1. Extra kernels (2 or 3 you know works for your device)
2. Optional: 2 recoveries that can be flashed (I use CWM & TWRP)
3. Optional: apps.zip (a zip created from Titantium BU, containing Root Explorer, TU Backup, Quickpic, ES File Explorer and Terminal Emulator)
Flashing the rom: TOUCHWIZ/AOSP ROMS
1. Backup current rom (to the extsdcard)
2. Complete wipe, (I do complete, some people do not) Complete = No Issues [FACTORY RESET + CLEAR CACHE + CLEAR DALVIK CACHE + CLEAR DATA]
3. Flash the rom
4. Flash the kernel (your device kernel) (I know some roms have their own kernel) this is where your problems start.
AGAIN: FLASH YOUR KERNEL, you KNOW it works. 1 more time FLASH YOUR KERNEL. (you can experiment with other kernels after you boot)
AOSP ROMS - require you to flash gapps before you boot. [This is not required for TouchWiz roms]
5. Boot the rom.
FINISHED!!!! SUCCESS!!!
Total time to flash a rom:
7-10min
Errors - NONE
This goes for every rom in my guide.
TIPS:
This flash procedure is for Touchwiz Roms, if you are flashing AOSP roms, you must flash the gapps package associated with the rom you are flashing.
**** SGH-I337M Users: Often requires flashing a different kernel than the one included in most ATT ROMS. Any GT-i9505 kernel will work and Adam kernel and Faux kernel are both confirmed working for us Canadian users.
Note: Flash KERNEL directly after ROM then reboot device.
[Special thanks to blyndfyre for this helpful tip].
The extra recovery I flash if a rom does not like the recovery I am using.
Yes, you can flash recoveries back and forth.
Apps.zip I flash after the rom is up & running. This I use to get the rom setup (like root explorer and others needed)
I am in no way responsible for anything that may do damage to any device - Use these tips at your own risk - period!
If you found this useful in any way, please hit the THANKS button for my effort.
RESERVED
TheAxman said:
Any questions? Anyone.
Click to expand...
Click to collapse
I've been running into a lot of issues when trying to flash different ROMs. For instance, right now I'm on CleanROM 1.6 - I just tried to install PureGv2.
Steps I took:
Have Goo and ROM Manager installed after clean install of CleanROM 1.6
Flash CWM from ROM Manager
Install Recovery Script from Goo
Reboot into recover from Goo
TWRP loads
Wipe data, cache, dalvik, etc
Install PureGv2
I forget the error off the top of my head but it doesn't install
In a nutshell I'm asking what am I doing wrong? Do I need to flash another kernel?
Flash your verizon kernel. Correct. I know it is a vzn rom, but do it anyway.
TheAxman said:
Flash your verizon kernel. Correct. I know it is a vzn rom, but do it anyway.
Click to expand...
Click to collapse
Was looking through Tomsgt's Youtube channel and stumbled across a video of his that showed his "About Phone". Everything was identical to mine, so I'm still a little lost as to why I can flash certain ROMs but not others. Sac/Gru's ROM soft bricked my phone, Hyperdrive5.7 didn't install, CleanROM does. It's just funky...maybe I'll just Odin back to stock, flash the MDK and start fresh.
Could the downloads be a problem? I downloaded 2 of the ROMs from work today on a 50meg pipe and they didn't work.
Do you download the ROMs to your phone or to your computer and then move them to your SD card?
If you download to your phone, do you move them to the SD card or leave them in the download folder on the internal storage?
If you do the latter, do you use a micro SD adapter or plug the phone in and move them that way?
harrytery said:
Was looking through Tomsgt's Youtube channel and stumbled across a video of his that showed his "About Phone". Everything was identical to mine, so I'm still a little lost as to why I can flash certain ROMs but not others. Sac/Gru's ROM soft bricked my phone, Hyperdrive5.7 didn't install, CleanROM does. It's just funky...maybe I'll just Odin back to stock, flash the MDK and start fresh.
Could the downloads be a problem? I downloaded 2 of the ROMs from work today on a 50meg pipe and they didn't work.
Do you download the ROMs to your phone or to your computer and then move them to your SD card?
If you download to your phone, do you move them to the SD card or leave them in the download folder on the internal storage?
If you do the latter, do you use a micro SD adapter or plug the phone in and move them that way?
Click to expand...
Click to collapse
Download to the computer,then copy to the phones extsdcard, should be ok, make sure you do a md5 check on the files to make sure they are the correct size.
TheAxman said:
Download to the computer,then copy to the phones extsdcard, should be ok, make sure you do a md5 check on the files to make sure they are the correct size.
Click to expand...
Click to collapse
Alright sounds good. Flashing back to stock later today then re-rooting
thanks for the help
Remember always do a BACKUP before you do anything.
First off, big thanks for this thread.
Now I'm running Cleanrom 1.5. If I wanted to install a new rom can someone please explain exactly what I do to go about it? As jargon free as possible would be awesome.
Sent from my SCH-I545
I certainly scared the carp outta me the other night. I'm using the Carbon ROM and while I do like it, I miss a couple of the S4s features. I picked what looked like a good modified stock ROM and proceeded to flash it.
I'm using Goo and TWRP for the job. I checked of all 3 boxes for clearing cache, davik and factory reset.
Then I chose the file and started it.
The first result, it acted like if was doing everything but nothing changed. Phone still worked fine.
On the next try, I waited for TWERP to start and I reselected the ROM I wanted and flashed it.
When it booted up, I was very happy to see the original screens come up. Then it stopped on the one with the Verizon check mark. The blue LED slowly pulsing and nothing else for about 30 min. I removed battery to try and start over. Same thing again.
Time to goto my backup and restore my phone back to Carbon.
IT FAILED.
Now my phone is stuck in a weird looking boot up loop. After a few tries I was able to get into recovery
mode. TWRP started loading, froze and crashed! Even though I am a total noob at this, I still did not panic.
I'd restart my phone by removing the battery, going into recovery mode and then wildly press every button on my phone hoping to break the loop. It worked! I chose a different save and tried it all over again. FAIL.
ON the next I wiped every bit of old data off. Chose Factory restore crossed my fiingers....it work! My phone is fine now.
Thanks to that ordeal and this thread I think I know what I did wrong even though this never happened to me. before.
1) WIPE THE DATA
2)INSTALL A COMPATABLE KERNAL FIRST
V^^^^V
Vampyre111 said:
I certainly scared the carp outta me the other night. I'm using the Carbon ROM and while I do like it, I miss a couple of the S4s features. I picked what looked like a good modified stock ROM and proceeded to flash it.
I'm using Goo and TWRP for the job. I checked of all 3 boxes for clearing cache, davik and factory reset.
Then I chose the file and started it.
The first result, it acted like if was doing everything but nothing changed. Phone still worked fine.
On the next try, I waited for TWERP to start and I reselected the ROM I wanted and flashed it.
When it booted up, I was very happy to see the original screens come up. Then it stopped on the one with the Verizon check mark. The blue LED slowly pulsing and nothing else for about 30 min. I removed battery to try and start over. Same thing again.
Time to goto my backup and restore my phone back to Carbon.
IT FAILED.
Now my phone is stuck in a weird looking boot up loop. After a few tries I was able to get into recovery
mode. TWRP started loading, froze and crashed! Even though I am a total noob at this, I still did not panic.
I'd restart my phone by removing the battery, going into recovery mode and then wildly press every button on my phone hoping to break the loop. It worked! I chose a different save and tried it all over again. FAIL.
ON the next I wiped every bit of old data off. Chose Factory restore crossed my fiingers....it work! My phone is fine now.
Thanks to that ordeal and this thread I think I know what I did wrong even though this never happened to me. before.
1) WIPE THE DATA
2)INSTALL A COMPATABLE KERNAL FIRST
V^^^^V
Click to expand...
Click to collapse
I can not stress enough HOW IMPORTANT THE KERNEL IS!
Hmm so everyone is a now a Oriental Flash Master from the far East now huh?
What recovery is everyone using?
[updated: 07-12-2013]
Flashing Questions
So, if you just need to add something, like different Kernerl, do you have to wipe and start from scratch?
Should you.
If so, and you backup apps and data in Titanium, then what you do a full wipe, flash entire rom, and reinstall the apps and data associated therewith?
Last, I have asked this but cannot seem to get an answer.
Installed Hyperdrive 7 (also had 5.7 and 6). Rom is super smooth and fast, working like a charm. but I want Verizon Visual Voice Mail.
I tried to copy the apk file to the devices system/app directory but get permission denied message....tried to install, and get failed message....
xander45 said:
So, if you just need to add something, like different Kernerl, do you have to wipe and start from scratch?
Should you.
If so, and you backup apps and data in Titanium, then what you do a full wipe, flash entire rom, and reinstall the apps and data associated therewith?
Last, I have asked this but cannot seem to get an answer.
Installed Hyperdrive 7 (also had 5.7 and 6). Rom is super smooth and fast, working like a charm. but I want Verizon Visual Voice Mail.
I tried to copy the apk file to the devices system/app directory but get permission denied message....tried to install, and get failed message....
Click to expand...
Click to collapse
did you set the permissions for the app? That should work actually. Look at one of the apps in that directory, and set the permissions the same for the voice app. Reboot and see what happens.
Good luck.
May want to post this question also in my guide thread.
http://forum.xda-developers.com/showthread.php?t=2295557
Sorry if this is dumb, but how do I know what kernels for sure work with my device and how do I get them to my external sd card? I suppose the one that is currently on my device(how to get that to sd?), but what others?
Thanks.
Painterface said:
Sorry if this is dumb, but how do I know what kernels for sure work with my device and how do I get them to my external sd card? I suppose the one that is currently on my device(how to get that to sd?), but what others?
Thanks.
Click to expand...
Click to collapse
Please bring the question over to my thread up above. It shows also what kernels to use. We will help there.
Another noob question: so you still advise flashing a kernel even if the ROM creator says that the ROM comes with the appropriate kernel and that no extra flashing is required? I've got the Verizon Galaxy S4 variant and specifically am thinking of Dubbsy's Google Play Edition ROM.
Sent from my SCH-I545 using Tapatalk 2
theoneknownasbob said:
Another noob question: so you still advise flashing a kernel even if the ROM creator says that the ROM comes with the appropriate kernel and that no extra flashing is required? I've got the Verizon Galaxy S4 variant and specifically am thinking of Dubbsy's Google Play Edition ROM.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
You would flash the rom, and after, flash your verizon kernel, simple as that.