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,
I've seen some people asking for numbered battery mods for stock or StreakDroid4 2.5.0 ROMs so I put together a simple theme (thanks to UOT Kitchen) and wanted to share it with anyone who is interested.
The theme simply changes the look of status bar and the icons, battery, system menus, adds new Roboto font ( from ICS), ICS window animations and Blue Android boot animation. Also, due to Raven 2 kindly allowing us use some files from his theme, you will now get ICS-like Phone, Contacts, Gallery and Calendar apk. I'm attaching some screenshots so you can get a visual idea.
I'm running on StreakDroid4 2.5.0 but it may also work on the deodexed or stock 408 ROM.
As usual, I do not take any responsibility for any issues that the process may cause - proceed with caution
To install:
1.Download the zip file below
2. Flash via CWM
Big thanks to TheManii for his ROM and Raven 2 for letting us use his files in this theme.
Just in case you were wondering, the screen lock on the first image is Widgetlocker which isn't free, but you can download MagicLocker or MiLocker that have similar look for free. The launchers I used in the shots (just to show different looks) are Go Launcher EX (with ICS theme) and Espier Launcher both are free too. Also shown and used is another free app - Widgetsoid.
(Updated) Link: http://dl.dropbox.com/u/43165183/ICStockNew.zip
Thanks!
streak4m3 said:
Also, if Raven ever comes back to the site I would like to ask him if we can use his themed Phone and Contacts apks that have an ICS look and I will include it in this theme.
Click to expand...
Click to collapse
you can use my ICS LOOK Phone.apk and Contants.apk
ICS LOOK Phone.apk and Contants.apk files in SB Theme
I fix some apps icon looks like ICS
[Download]
this file has Calendar.apk Contacts.apk Gallery3D.apk Mms.apk Phone.apk Settings.apk
install way is same.
Sorry language, It is my limit.
RAVEN 2 said:
you can use my ICS LOOK Phone.apk and Contants.apk
ICS LOOK Phone.apk and Contants.apk files in SB Theme
I fix some apps icon looks like ICS
[Download]
this file has Calendar.apk Contacts.apk Gallery3D.apk Mms.apk Phone.apk Settings.apk
install way is same.
Sorry language, It is my limit.
Click to expand...
Click to collapse
Your language is fine, no worries. Thanks for letting us use your files. I'm going to update the OP and attach the new theme file.
I'll try it out on my deoxed 408 and see how it goes. I just put TeamDRH ICS on my Viewsonic GTab (no thanks to Viewsonic - you suck) and would like a consistent interface across devices
Cool, let me know how it works/looks. It isn't the actual ICS UI but the color scheme and other mods at least remind you of one
It works great! I flashed with CWM, cleared cache & delvik, and fixed permissions for good measure. I especially like the battery icon. Now to find a way to port ICS over to this and we will be set. Maybe our new Korean friends are working on that?
michaeljwestii said:
It works great! I flashed with CWM, cleared cache & delvik, and fixed permissions for good measure. I especially like the battery icon. Now to find a way to port ICS over to this and we will be set. Maybe our new Korean friends are working on that?
Click to expand...
Click to collapse
Nice, glad to hear that. Yes, I agree about ICS port or a new ROM from our Korean friends would be great. I think one of their main contributors Kukjin11 is going to upload his ROM in a couple of days, so we will see from there
Cool stuff.
Thank you.
thanks, awesome
hey guys iam having the 408 olleh gb running on my phone with ravens theam on top of it..
can i upgrade it to ics them here.. if yes do i have to rename the file that has been given here....
if possible can some one please write the steps since iam very new to this stuff...
thanks alot guys..
hey crainz,
Do you have CWM installed? Are you on deodexed stock 408 ROM created by TheManii? The theme was based on deodexed ROM files from StreakDroid4 2.5.0 (which I use) and I believe it works on the deodexed 408 stock - both of which put together by TheManii. I don't know for sure if it works with a normal odexed ROM - so let's hear from TheManii or anyone else who can verify.
If you have CWM installed, you can easily flash files, like the StreakDroid4 2.5.0 which is basically stock with tweaks and debranded (so no Olleh stuff) and then flash my theme. I recommend you install Titanium backup and back up your apps and data so when you install a new ROM you can restore (or import) you saved data like passwords, shortcuts, game levels, and so on.
Edit: Here's the XDA Wiki page that TheManii created which has the links to SD4 2.5.0 and CWM Recovery downloads:
http://forum.xda-developers.com/wiki/Dell_Venue/ROMs
hi crainz
Thanks a lot for the information...
Rightn now i have the Olleh rom which was given to me by raven
originally i had the stock rom
Android 2.2
Baseband Version GTOUB1A130400-AWS
kernal version : 2.6.32.9-perf
Build number : 13040
Now it shows
Android 2.3.3
Baseband Version GTOUB1A140814-AWS
kernal version 2.3.35.7-perf
build number 20707
i have installed the rom from this link that was given to me by RAVEN
http://205.196.123.33/kobdqv9ci72g/fcubk6gamvc3s65/Thunder_408_20707_14.pkg
I took all the instructions from RAVEN and did the upgrade
the details of which are listed in this post
http://forum.xda-developers.com/showthread.php?t=1441614&page=5
Can u please check and help me to install StreakDroid4 2.5.0 so that i can install the ICS after that.. if possible....
I have CWM 5.5.0.4 installed on my phone...
just want to check if i install the StreakDroid4 2.5.0 on top of the image that i have will it cause any issues....
crainz said:
hi crainz
Thanks a lot for the information...
Rightn now i have the Olleh rom which was given to me by raven
originally i had the stock rom
Android 2.2
Baseband Version GTOUB1A130400-AWS
kernal version : 2.6.32.9-perf
Build number : 13040
Now it shows
Android 2.3.3
Baseband Version GTOUB1A140814-AWS
kernal version 2.3.35.7-perf
build number 20707
i have installed the rom from this link that was given to me by RAVEN
http://205.196.123.33/kobdqv9ci72g/fcubk6gamvc3s65/Thunder_408_20707_14.pkg
I took all the instructions from RAVEN and did the upgrade
the details of which are listed in this post
http://forum.xda-developers.com/showthread.php?t=1441614&page=5
Can u please check and help me to install StreakDroid4 2.5.0 so that i can install the ICS after that.. if possible....
I have CWM 5.5.0.4 installed on my phone...
just want to check if i install the StreakDroid4 2.5.0 on top of the image that i have will it cause any issues....
Click to expand...
Click to collapse
If you have CWM installed then you can go ahead and install StreakDroid4 2.5.0. However, you would need to do a factory reset first so back your data up using Titanium Backup (this is a free version) and then you can restore all your apps and data once you flashed SD4. After that just flash ICStock theme and you're good to go.
Thank a lot for the information streak4m3
Just 2 more question before i start the process of upgrade.
1. when i installed the CWM using this link
http://forum.xda-developers.com/showthread.php?t=1423002
Ans started the phone i was able to get the CWM to work. But once i shut down the phone again and try
You switch mute to OFF hold both volume buttons down and power on. You will see a menu with 3 options, choose the one to upgrage SW package and choose with the camera button.
iam getting the Blue colour screen. iam not getting the CWM options.
Is this how it is suppose to work or am i doing something wrong.
2.Once i have flashed StreakDroid4 2.5.0 after renaming the file to upgrade.pkg.how do i flash the ICS theam?? IF you could kindly give me the steps that would be great..
crainz said:
Thank a lot for the information streak4m3
Just 2 more question before i start the process of upgrade.
1. when i installed the CWM using this link
http://forum.xda-developers.com/showthread.php?t=1423002
Ans started the phone i was able to get the CWM to work. But once i shut down the phone again and try
You switch mute to OFF hold both volume buttons down and power on. You will see a menu with 3 options, choose the one to upgrage SW package and choose with the camera button.
iam getting the Blue colour screen. iam not getting the CWM options.
Is this how it is suppose to work or am i doing something wrong.
2.Once i have flashed StreakDroid4 2.5.0 after renaming the file to upgrade.pkg.how do i flash the ICS theam?? IF you could kindly give me the steps that would be great..
Click to expand...
Click to collapse
OK, first of all you're not supposed to rename SD4 2.5.0 to update.pkg
Let's make sure I understand you correctly. You're saying that you have (or had) CWM installed and you verified that it works (worked), right? That means that you can (could) get to CWM recovery and see all the options, like: reboot system, install zip, wipe cache partition, advanced and so on, correct?
Are you now saying you can't get to CWM recovery? That it somehow goes to Dell stock recovery option which is blue (I think)? CWM mode has blue color text too so that's why it is a little bit confusing.
If you somehow lost CWM recovery just install it again and then simply flash SD4 2.5.0
i have seen the option that come with CWM reboot system, install zip, wipe cache partition, advanced and so on...
This comes once i have installed it using the instruction listed in the post...
http://forum.xda-developers.com/show....php?t=1423002
i even was able to create a back up the rom on my system using CWM.. which got listed in the sdcard as well.
but once i shutdown the phone and start it again i dont get that CWM again it comes up with the blue dell flash tool.(which is in blue colour again) just like CWM
Just wanted to know if this is the same that happens in you case as well or are you able to get CWM evertime.
(if i install it again Iam able to get it to work once and them again back to the dell flash screen)
Just wanted to know if there is a way by which we can get it permenantly to work without having to flast it again and again..
crainz said:
i have seen the option that come with CWM reboot system, install zip, wipe cache partition, advanced and so on...
This comes once i have installed it using the instruction listed in the post...
http://forum.xda-developers.com/show....php?t=1423002
i even was able to create a back up the rom on my system using CWM.. which got listed in the sdcard as well.
but once i shutdown the phone and start it again i dont get that CWM again it comes up with the blue dell flash tool.(which is in blue colour again) just like CWM
Just wanted to know if this is the same that happens in you case as well or are you able to get CWM evertime.
(if i install it again Iam able to get it to work once and them again back to the dell flash screen)
Just wanted to know if there is a way by which we can get it permenantly to work without having to flast it again and again..
Click to expand...
Click to collapse
CWM should be there every time - it's a permanent thing. You can install it again and flash SD4 2.5.0 during that one time that you can get into CWM recovery.
hey
Here is what i did. I flashed SD4 2.5.0 on my phone using CWM.. all went well
Then i flashed your ICS theme.. and restarted the phone.. that went well as well.
But what i did after that was i reset the phone to default using the option in settings.
The phone just stoped working completly.
It got stuck at the Blue Andriod startup... I tryed to do the process all over again...
No luck.... I think i have messed up my phone completly.
But before i started doing all this what i did was i took a back up of my phone using CMW..
So when restored the system back all came back using CWM the phone was back and working again...
What did i do wrong..... and is there any better way of doing this???
crainz said:
hey
Here is what i did. I flashed SD4 2.5.0 on my phone using CWM.. all went well
Then i flashed your ICS theme.. and restarted the phone.. that went well as well.
But what i did after that was i reset the phone to default using the option in settings.
The phone just stoped working completly.
It got stuck at the Blue Andriod startup... I tryed to do the process all over again...
No luck.... I think i have messed up my phone completly.
But before i started doing all this what i did was i took a back up of my phone using CMW..
So when restored the system back all came back using CWM the phone was back and working again...
What did i do wrong..... and is there any better way of doing this???
Click to expand...
Click to collapse
Not really sure what exactly may have happened in your situation. So are you up and running again? And why did you want to do a factory reset after flashing SD4 2.5.0?
If you're phone is not up and runing right now then you need to get to CWM if you can and just reflash SD4 and the theme. If you can't get to CWM, then you need to restore your phone using TheManii's steps in his thread for unbricking your phone (basically you would need to flash via fastboot options).
Alright, hopefully the ridiculous title helped to draw you in...
Anyways, so I was running the unofficial MIUI for my GSM Razr until the official release came out. I installed an OTA ICS and Bootmenu. I installed the hijack and the new recovery, and didn't change any settings in the app. I then booted into the new recovery. I toggled into the 2nd system and installed MIUI. Upon boot, it got stuck on the MIUI logo for 10 mins. I did a hard-reset and tried again, same thing. I then booted into the standard recovery menu and did a factory reset and rebooted. Miraculously, this time it booted up and MIUI is running perfectly now.
Okay, now I downloaded Bootmenu again, and now my MIUI is labeled as my "stock system". I'm perfectly okay with this, the only thing I'm wondering is what happened to my original stock ICS installation? I thought installing in the 2nd partition was supposed to keep my original installation clean. Now it's all confusing, I just want to make sure there's nothing lingering around.
Edit: Ugh, found out what happened. Just needed to do some more digging around. For anyone else that wants to know: "To anyone wanting to flash custom roms from droidrzr and alike you need to modify the update-script a bit to make it work correctly, failure to do this will wipe you primary system regardless that you are in the second system"
You're right. Recovery has no control of what the updater_script contents / do.
My friend and I both have Fascinates. I got mine first, and just rooted the Gingerbread that came with it. I use it for medical purposes, and really needed something stable and reliable.
When my friend got hers, we decided to go for a more recent ROM, and chose GeeWiz 4.4.2 (Jellybean). It was real easy to install and didn't require anything special. It worked great for a little while, but as she added apps to it, it got real laggy and hard-crashed a fair amount.
Yesterday, all hell broke loose with it. Suddenly, every Google app was crashing, including the Play Store. I researched the issue and found many other people with similar problems on various phones. I tried literally 16 different fixes, none of which worked. So I had to hard reset it.
Since it's a blank canvas, and her experience with GeeWiz wasn't all that great, I figure it's a good time to try something else.
What do YOU recommend?
Here's her priorities:
1. Must be super stable.
2. Everything must work. Speakerphone, bluetooth, camera, video, microSD, you name it.
3. Not laggy.
4. Good battery life.
She really likes the Jellybean notifications, so she would prefer Jellybean or later.
I'm very interested in what the community recommends. :highfive:
the newest cm10.1 nightly was rock solid for me. helly bean 4.2.2 was good too. don't go beyond 4.2 if you want good stability, i don't think some basic things work in the cm11 builds yet (GPS and MMS are flaky)
oh also don't feel bad for running stock GB. i'm actually running it right now (rooted, lean kernel, and i gutted out the majority of samsung things)
---------- Post added at 11:04 PM ---------- Previous post was at 11:00 PM ----------
also, for future reference, any thread you post of similar connotation to this will probably get locked by a moderator and he'll say "oh try roms out for yourself blah blah blah"
so if that happens, don't say i jinxed it. also, i've had my fassy for around 6 months and i've tried literally everything under the sun for it.
I agree with sceptic on these ROM selections
rockpaperlizard said:
Yesterday, all hell broke loose with it. Suddenly, every Google app was crashing, including the Play Store. I researched the issue and found many other people with similar problems on various phones. I tried literally 16 different fixes, none of which worked. So I had to hard reset it.
Click to expand...
Click to collapse
I thought Geewiz was only made for the Fascinate? I have been trying the Geewiz rom, and so far the only time it became laggy was when I set the cpu Govenor to a power saving option. Otherwise it has actually been much faster booting up than the kitkat roms.
Sent from my GT-N5110 using xda premium
Okay, trying to get Hellybean working... but am stuck!
Thank you to everyone providing a reply so far. Please keep the suggestions coming. :highfive:
I am trying to install the recommended Hellybean 4.2, and am stuck.
The phone was stock Gingerbread, and then I installed the GeeWiz 4.4 ROM on it. Had some lagging and crashing, so now I'm trying to get Hellybean 4.2 on it, per recommendations of others.
So I downloaded the latest Hellybean 4.2 from the hellybean website. I then booted into recovery, and selected Update from Zip and and tried to install the Hellybean zip. I get a Status 7 error. Some sites said to try it 3 times. I tried it 5 times. No dice.
I can't find a Hellybean 4.2 Fascinate thread on XDA, so details are sparse. Am I blind?
Am I correct in understanding that Hellybean 4.2 includes the devil kernel? Or do I need to ODIN a different kernel first?
I installed ROM Manager to get the latest CWM Recovery, but it says the Fascinate is an "unknown device". There is no CWM Recovery installation file for the Fascinate listed on the Clockworkmod website. UGH! :crying:
Can anyone help? I can follow step by step instructions real well. :good:
Progress Update
I noticed the link in hhp_221's signature, and followed it. I installed his devil kernel for Jellybean 4.2.2. Works a treat. :good:
Then I tried to install the Hellybean 4.2 zip file in the resultant CWM Recovery, and now I get a Status 0 error. Tried it 5 times. Same thing each time.
Help!
rockpaperlizard said:
I noticed the link in hhp_221's signature, and followed it. I installed his devil kernel for Jellybean 4.2.2. Works a treat. :good:
Then I tried to install the Hellybean 4.2 zip file in the resultant CWM Recovery, and now I get a Status 0 error. Tried it 5 times. Same thing each time.
Help!
Click to expand...
Click to collapse
okay here's some instructions (assuming the phone is on stock. if it isn't just go into odin and reflash it again because you're probably bricked)
1. let it boot up after odining EH03 (might want to throw cm10.1, helly, and google apps on the sd card at this point)
2. after it boots, flash GBBootloaders.tar and cwm 4 fixed for cm7. those files can be found here: http://forum.xda-developers.com/showthread.php?t=1238070
3. go into recovery by pressing and holding volume up, down, and power until the samsung logo flashes and reapppears
4. wipe data and cache
5. flash the newest cm10.1 (gapps too if you want to stay on cm, if you want helly don't bother flashing gapps)
6. reboot
7. if you're flashing helly, reboot into recovery from cm and flash helly from CWM. and gapps. wipe data too just to be safe.
if any of my guide didn't help, just follow the thread i linked in step 2. it's a good comprehensive guide.
also never flash anything with ROM Manager, it's useless for this phone because the version of CWM on ROM Manager is really old. i've bricked my phone when trying it.
Getting closer!
skepticmisfit said:
okay here's some instructions (assuming the phone is on stock. if it isn't just go into odin and reflash it again because you're probably bricked)
1. let it boot up after odining EH03 (might want to throw cm10.1, helly, and google apps on the sd card at this point)
2. after it boots, flash GBBootloaders.tar and cwm 4 fixed for cm7. those files can be found here: http://forum.xda-developers.com/showthread.php?t=1238070
3. go into recovery by pressing and holding volume up, down, and power until the samsung logo flashes and reapppears
4. wipe data and cache
5. flash the newest cm10.1 (gapps too if you want to stay on cm, if you want helly don't bother flashing gapps)
6. reboot
7. if you're flashing helly, reboot into recovery from cm and flash helly from CWM. and gapps. wipe data too just to be safe.
Click to expand...
Click to collapse
Thank you for all the tips. Using your tips, I successfully got CM 10.1 onto her phone. But I read her the description of HellyBean, and she would prefer that (of course :cyclops.
So once CM 10.1 is on, I booted into it, and then immediately turned it off. I then booted into CWM recovery, and tried to install the Hellybean ROM. I get the Status 7 error each time. You mentioned wiping data after installing helly, but I think you meant before (let me know if I'm mistaken).
I researched Status 7 errors, and some people say they are because the ROM is expecting a different existing version to be installed over. I took a look at the build.prop file in Hellybean, and it references the Gingerbread 2.3.5 EI20 ROM, whereas all I could find was the stock Gingerbread 2.3.5 EH03 ROM. I tried editing the build.prop file to reflect EH03, but I an aborted error when trying to install that.
The radio and all other items on the phone should be stock. Not sure if that helps or hurts in getting Hellybean installed.
Anyways, any and all help in getting from CM 10.1 to Hellybean 4.2.2 would be most appreciated. Or I can put stock Gingerbread 2.3.5 EH03 back on and start from there. :good:
rockpaperlizard said:
Thank you for all the tips. Using your tips, I successfully got CM 10.1 onto her phone. But I read her the description of HellyBean, and she would prefer that (of course :cyclops.
So once CM 10.1 is on, I booted into it, and then immediately turned it off. I then booted into CWM recovery, and tried to install the Hellybean ROM. I get the Status 7 error each time. You mentioned wiping data after installing helly, but I think you meant before (let me know if I'm mistaken).
I researched Status 7 errors, and some people say they are because the ROM is expecting a different existing version to be installed over. I took a look at the build.prop file in Hellybean, and it references the Gingerbread 2.3.5 EI20 ROM, whereas all I could find was the stock Gingerbread 2.3.5 EH03 ROM. I tried editing the build.prop file to reflect EH03, but I an aborted error when trying to install that.
The radio and all other items on the phone should be stock. Not sure if that helps or hurts in getting Hellybean installed.
Anyways, any and all help in getting from CM 10.1 to Hellybean 4.2.2 would be most appreciated. Or I can put stock Gingerbread 2.3.5 EH03 back on and start from there. :good:
Click to expand...
Click to collapse
wipe data before installing helly. also i've never bothered with build.prop in Hellybean. it only references to EI20 for Voodoo Sound drivers. EI20 is the stock build for.. i believe the US Cellular Mezmerize (aka not the Verizon Fascinate). so don't screw with it
yes stock radio is good. EH03 is a good radio but if you want you can flash EC09, based off of a leak of GB. some people have good luck with it, i used to but i like EH03.
so.. i'm not sure if you can boot the phone into helly bean. it sounds like you were getting a lot of "status 7" errors, which i didn't ever get while trying to use helly. this may or may not be caused by the sd card. try a different card if possible. if you're bricked at this point just start over from EH03.
also be sure you're using the 2013-7-23 build of helly, that's the last one based off of 4.2.2, the rest are broken 4.3 builds.
Good advice!
skepticmisfit said:
also be sure you're using the 2013-7-23 build of helly, that's the last one based off of 4.2.2, the rest are broken 4.3 builds.
Click to expand...
Click to collapse
Thanks for the heads up on the helly build! I got one from the Hellybean website, and it's labeled 20131024. I tried and tried to find the 2013-7-23 but no luck , could you guide me to a source for it? Thanks!
rockpaperlizard said:
Hey, it's the girlfriend here. BF is out, so I was trying to get the right files gathered. Thanks for the heads up on the helly build! I got one from the Hellybean website, and it's labeled 20131024. I tried and tried to find the 2013-7-23 but no luck , could you guide me to a source for it? Thanks!
Click to expand...
Click to collapse
here you go: http://andromirror.com/file/1386
good luck!
Sooooo close...
Thank you for the helly link!
Followed instructions, and successfully got it to helly!:good:
But... been trying to flash the gapps, and no go. It says it's successfully installed, but then nothing happens. Also noticed it can't mount the cache. And noticed that the zip says it's signed but if signature verification is enabled, cwm says the signature is not valid.
Any thoughts/ideas/solutions? Thanks!
rockpaperlizard said:
Thank you for the helly link!
Followed instructions, and successfully got it to helly!:good:
But... been trying to flash the gapps, and no go. It says it's successfully installed, but then nothing happens. Also noticed it can't mount the cache. And noticed that the zip says it's signed but if signature verification is enabled, cwm says the signature is not valid.
Any thoughts/ideas/solutions? Thanks!
Click to expand...
Click to collapse
cache...
give us what the recovery version number is.
Is it the red touch recovery (that is what is included with hellybean)
gapps...
bad download maybe, it does happen...
get and verify the md5 yourself with an app
for windows
or an android one
like this one
are you using this gapps version? http://goo.im/gapps/gapps-jb-20130812-signed.zip
its what you need to start with,, and then after you sign in to your account,, it will check to see what needs to be updated.
.
I tried the cm10 mentioned here. It does seem very nice. It appears to have more features than Geewiz also, along with a lot more ringtones.
Sent from my GT-N5110 using xda premium
Information
hhp_211 said:
cache...
give us what the recovery version number is.
Is it the red touch recovery (that is what is included with hellybean)
.
Click to expand...
Click to collapse
Thank you for the avenues to explore. The recovery that comes up is CWM Recovery v4.0.1.0. Does that mean helly didn't really install successfully? When it boots, it does give the Devil kernel graphic, which I understand is part of helly?
hhp_211 said:
gapps...
bad download maybe, it does happen...
get and verify the md5 yourself with an app
are you using this gapps version? http://goo.im/gapps/gapps-jb-20130812-signed.zip
.
Click to expand...
Click to collapse
I looked at the gapps. It is the gapps-jb-20130812-signed.zip and the md5 checks out.
It's the blue CWM, forgot to mention that...
rockpaperlizard said:
Hi, GF here again. I'm new to all this, thank you for the avenues to explore. The recovery that comes up is CWM Recovery v4.0.1.0. Does that mean helly didn't really install successfully? When it boots, it does give the Devil kernel graphic, which I understand is part of helly?
I looked at the gapps. It is the gapps-jb-20130812-signed.zip and the md5 checks out.
Click to expand...
Click to collapse
whoa you're not supposed to have blue recovery after flashing a 4.x ROM (or MTD as we call it).
go to step 4 in this guide: http://forum.xda-developers.com/showthread.php?t=1238070
you're going to have to reflash EH03 in Odin before doing anything because your recovery is borked.
Got it!!
Finally got helly onto a phone! Ended up starting all over, and then just flashing to helly since had the right file and hadn't tried going directly (skipping CM). And it worked! But the 3-finger salute got us back into blue CWM. So I started all over again, and once helly was on, I thought I'd do a reboot just to make things happier, which is when we noticed the 'reboot to recovery' and remembered that we had read somewhere that you sometimes have to use that instead of the 3-finger. So we did and everything has been golden since then. I love, love this ROM! :laugh:
Big thanks to you guys for helping us through the process! We couldn't have done it without you!!
rockpaperlizard said:
GF here. We finally got helly onto the my phone! We ended up starting all over, and then just flashing to helly since we had the right file and hadn't tried going directly (skipping CM). And it worked! But the 3-finger salute got us back into blue CWM. So I started all over again, and once helly was on, I thought I'd do a reboot just to make things happier, which is when we noticed the 'reboot to recovery' and remembered that we had read somewhere that you sometimes have to use that instead of the 3-finger. So we did and everything has been golden since then. I love, love this ROM! :laugh:
Big thanks to you guys for helping us through the process! We couldn't have done it without you!!
Click to expand...
Click to collapse
that's weird that 3-finger into recovery is broken for you.. it wasn't for me. but whatever, as long as it works
Hi all! I have a slight issue.. So my sisters phone is rooted and on offical kit-kat NAB.
I tried to install @kevinrocksman's hypnotoad boot animation, flashable through twrp. http://forum.xda-developers.com/showthread.php?t=2467543
It didnt work and after the Note 3 screen it stays black till it boots up. I figure it is because the phones only on stock rooted, and that uses a bunch of weird .qmg files. I cant restore the nandroid for several reasons so thats not an option. So I tried the following troubleshooting steps to either get the hypnotoad to work or restore the default sprint sound and animation.
1. I manually pushed the hypnotoad bootanimation.zip into system/media and changed permissions. no go
2. Then in hypnotoad aroma installer I installed it again. Still no go
3. In aroma I tried restore default feature, the sounds back but no yellow sprint animation
4.I deleted the bootanimation.zip in system/media. no go
.5.On the thread @shabbypenguin commented. Posting an enable bootanimation.zip to have the phone look for .zips instead of .qmg. I flashed it. (http://www.mediafire.com/download/xlbsop29q44vlco/Enable-Bootanimation.zip)
6. Then I tried twrping the hypnotoad aroma boot ani again, hoping shabbypenguins enable bootani will make it work. Nada
7. I tried restoring default again through aroma, still boots with sound but no yellow sprint animation.
So if anyone has an idea to either get the hypntoad to work or get back the defualt boot animation, that would be GREATLY appreciated.
I know it was probably dumb to try on stock rooted sorry, but my sister is stuck with no bootanimation, and she does not want to flash a new rom
So thanks
what thread was this??
shabbypenguin said:
what thread was this??
Click to expand...
Click to collapse
All was found on @kevinrocksman s thread. Your comment was at the bottom of the page
Thread: http://forum.xda-developers.com/showthread.php?t=2467543
I hope you have a fix mr. shabbypenguin sir! :fingers-crossed:
Do you know of any fixes @kevinrocksman??
I would think there would be a flashable. Zip laying around but i couldn't find any
if you read to the second page, you would have seen that zip doesnt work
shabbypenguin said:
if you read to the second page, you would have seen that zip doesnt work
Click to expand...
Click to collapse
Ive read the whole thread, and the comments. I believed it would work because I have been on several stock Samsung based roms, and all of either the flashable.zips or manually pushing to /system/media have worked fine. Im even currently on AOSP and pushing the monster attack bootanimation.zip to system/media worked perfectly. So I believe my error lies in possibly two things. Either..
A.these bootanimaton.zips are not NAB compatible; which would seem odd because as far as I know bootanimation.zips are fairly universal. It worked on AOSP just fine
B. Or since this is stock STOCK rooted, the system files have not been configured by a dev to allow changing bootanimation.zips.
If it is scenario B, which i think is more likely, then a solution would be to flash a custom built Nab rom, right? I would think if I flashed Freezas stockISH rom it would be too stock and the boot ani system files would be the same situation. Which is why im thinking @sac23 s kit-kats v1 nab rom would allow me to change bootanimation.zip. Do you think this would be accurate?
I did some further digging and I believe I may have found a way to be able to push bootanimation.zips and have them work even on stock stock roms.
What do you think of this? http://forum.xda-developers.com/showthread.php?p=50218786
I gather if I push the bootanimation.bin in OP and replace it with the current one in /system/bin it will enable me to change bootanimations just like normal. You probably would have a better idea then me, do you think this is an accurate conclusion?
Thanks :good:
kevinrocksman said:
samsung has been using qmg files since before the SGS1, this http://www.mediafire.com/download/xl...tanimation.zip should enable it. it swaps out the bootanimation binary for one looking for .zip's. it may not work if they are still using samsungani
Click to expand...
Click to collapse
this is what it does in adb when u execute bootanimation
CANNOT LINK EXECUTABLE: cannot locate symbol "_ZN7android21SurfaceComposerClient
14getDisplayInfoEiPNS_11DisplayInfoE" referenced by "bootanimation"...
Click to expand...
Click to collapse
as for all the other zips idk, but mine doesnt. as for figureing it out etc, youll have to ask someone who is up to date on samsung software and/or owns a note 3.
shabbypenguin said:
as for all the other zips idk, but mine doesnt. as for figureing it out etc idk, youll have to ask someone who is up to date on samsung software and/or owns a note 3.
Click to expand...
Click to collapse
okay thanks anyway, I happen to have an extra replacement note 3 for a little bit so ill run some tests!
thanks