Hey all.
So, I'm running Audacity B2 on my G2, and I've attempted to load up this modified services.jar file here, using both methods. I'm technical myself, so I tried the manual way first. Followed the steps exactly, and when I rebooted, I never (well, at least not for about 10 minutes that I waited!) got past the flying blocks of color boot screen for Audacity. Seemed to be stuck.
So I tried the CWM zip install method as well, same result. /Sigh. I really didn't expect this to be where I got stuck! Anybody have any thoughts as to what possibly is going on?
The only way I can get back to a working phone is to re-flash Audacity B2, then it will boot. Really wanting to try out V6 Supercharger, but can't get past this first step, which should be the easy one.
Thanks for any insight.
I had this issue today too. I reflashed B2 and gapps, booted, set up google account and apps, flashed new services.jar and after that everything works.
Interesting! So by "flashed new services.jar", I take that to mean you used the zip install via recovery, not manually moving the file?
I'll give that a shot and see what happens....
Thanks!
If you manually move the file make sure you set the proper permissions and ownerships. Also make sure you check the MD5sum of each download with what the site reports.
Either of those may cause issues that will likely boot loop you.
Sent from my HTC Vision using xda premium
Related
Read This
http://forum.xda-developers.com/showpost.php?p=9542514&postcount=662
Alternatively, just read my installation instructions:
http://forum.xda-developers.com/showthread.php?t=842004
I think I'm going to start using a rar format - might be a way to differentiate between the actual release and the update.zip inside. Not sure why I didn't think of that, before.
Still not that simple for me, since even a "Gtablet Vet" like myself tried the OP method and failed. My second out of box new Gtablet went in perma-loop when simply installing straight to 2.0, via recovery folder & update.zip. Ended up having to get CW on the device by putting on the sd card, remapping command and stopping the loop with power + volume to get CW installed. I then had to install TnT 1.02 and then finally got 2.0 installed after that (cache and data wipe of course).
Cleanest way seems install 1.02 via recovery folder / update.zip method and then install 2.0 the same way. Thats is unless I just had bad luck with second Gtablet. VERY possible.
added:
Frankly, we seem at the stage now where CW seems a survival requirement- IF you want to keep trying new roms & updates.
roebeet said:
Alternatively, just read my installation instructions:
http://forum.xda-developers.com/showthread.php?t=842004
I think I'm going to start using a rar format - might be a way to differentiate between the actual release and the update.zip inside. Not sure why I didn't think of that, before.
Click to expand...
Click to collapse
u didn't think of it because it was only a problem to ppl that half read the instructions, downloaded the zips and just tried to install as-is...
Also don't understand why ppl want to keep standard recovery, clockwork is made to install custom roms so its easier for these task
LRiley said:
u didn't think of it because it was only a problem to ppl that half read the instructions, downloaded the zips and just tried to install as-is...
Also don't understand why ppl want to keep standard recovery, clockwork is made to install custom roms so its easier for these task
Click to expand...
Click to collapse
The only issue with cwm is that it's not easy to remove it, once you have it. I think you need to use nvflash to get rid of it. I love cwm but I can't assume that everyone uses it.
And trust me, not everyone does. I sees posts here and I get PM's as well, and many people are still using standard recovery.
roebeet said:
The only issue with cwm is that it's not easy to remove it, once you have it. I think you need to use nvflash to get rid of it. I love cwm but I can't assume that everyone uses it.
And trust me, not everyone does. I sees posts here and I get PM's as well, and many people are still using standard recovery.
Click to expand...
Click to collapse
Installing TnT 1.0 roms appears to zap CW pretty good.
roebeet said:
The only issue with cwm is that it's not easy to remove it, once you have it. I think you need to use nvflash to get rid of it. I love cwm but I can't assume that everyone uses it.
And trust me, not everyone does. I sees posts here and I get PM's as well, and many people are still using standard recovery.
Click to expand...
Click to collapse
I have found that you can put the stock recovery img (let's call it recovery-stock.img) on the sdcard and get an adb shell while booted into cw recovery. Then it's just a
Code:
flash_image recovery recovery-stock.img
That should get you back to stock recovery.
Sent from my Incredible using XDA App
LRiley said:
u didn't think of it because it was only a problem to ppl that half read the instructions, downloaded the zips and just tried to install as-is...
Also don't understand why ppl want to keep standard recovery, clockwork is made to install custom roms so its easier for these task
Click to expand...
Click to collapse
I had to go back to stock at first because I kept getting status 7 errors with CW. Roebeet's suggestion to partition sdcard with CWR seems to have solved that.
Sent from my Incredible using XDA App
Flashed 2.0.0
I liked TnT 2.0.0 and it really helped performance but the gtab is still full of issues....
Out of the box my Gtab's proprietary email and photo app forced closed before ever loading. the viewsonic update didn't fix it and so I flashed it with TnT 2.0.0.
I got a System UID's warning while I did it and I guess that was the cause of those apps not working. I then did a system reset to factory default or whatever its called and lost everything but after flashing TnT 2.0.0 again it worked a lot better and the email app worked great, photo app still doesn't work. My new problems are that the sound and and flash don't work anymore. I reinstalled flash and the browser just crashes whenever flash is involved with a site. Sound will sometimes work when I first boot up but it quits after a while, especially after waking from sleep. A lot of the time I get crackles and pops when I first boot up or wake it from sleep.
I am returning this Gtab and I am going to buy another one from somewhere else in hopes that I don't get these issues out of the box.....I haven't read anywhere that anyone has experienced these specific problems other than the sound; as this is a TnT error; so I warn all, DON'T BUY FROM STAPLES!!!
I'm a relative newbie and not very tech-oriented, and I appear to have screwed up big time. I'd appreciate any help that can be offered. To cut to the chase, when I attempt to boot up my Fascinate, it gets stuck indefinitely on the Samsung logo.
Here's what I did to screw it up. I rooted my phone when I first got it last year and did a lagfix. It unrooted with the update to JD05. Yesterday I attempted to root it again using two different 1-click methods, neither of which worked. I then followed the instructions in the "Modified CWMrecovery for Odin" thread, not having it work until finally succeeding in getting root using CWM Red. The phone rebooted and was rooted, and everything seemed fine, so I used Rom Manager to Boot to Recovery. This did something strange--it took 15 minutes to get to the recovery screen, with a digital voice periodically telling me how much longer it would take. When I got to the recovery screen the first thing I did was to perform a backup. I think this effort to be safe did me in, because the phone must have already been screwed up then and I think I backed up the screw-up.
I then attempted to reboot and since then all efforts get me stuck on the Samsung logo. I've tried almost all options from the Recovery screen: reboot system now, apply sdcard update.zip, wipe date/factory reset, wipe cache partition, install zip from ascard, and restore. All bring the same locked up phone.
I'd appreciate any ideas to bring my Fascinate back to life!
First off the only way to get to red CWM is to install a voodoo 5 kernel. I'm thinking the voodoo kernel and the one click lag fix don't play well together. I'm sure someone else will step in with more info however I would start by looking for a thred called how to completely remove voodoo. Then try odin to restore. Good luck.
Edit. I read your post again and not sure if u did one click lag fix or just an older voodoo kernel. Either way same result u have to disable voodoo 4 and one click to install voodoo 5. Odin it. The voice u hear was the voodoo kernel converting your system to ext4 if this was the first time you've heard this I think your first lag fix may have been the one click.
Sent from my SCH-I500 using XDA App
Yes this happed to me too. If i take it to the Verizon store will they know my phone is rooted and moded? i need help ASAP
Search the forums on how to properly removed the voodoo lag fix. Then you need to reflash dj05. Voodoo doesn't really do much except for show you a higher quadrant score and limit to what roms/themes you can install. Same thing happened to me. Just do a quick search, I think its in the development section. The easiest way to remove it is with and. Hope this is somewhat helpful.
so fresh and so superclean.
Don't bring it to verizon because you would be defrauding them for your mistake. see if you can access your sd card through the computer and put either a file or folder in the voodoo folder called disable_lagfix and try booting again. If that doesn't help (it is probably too late for that) then you need to flash back to stock through odin. find the thread in development on how to do that. Good luck. Your phone is not broken. Breathe.
Sent from my sch-i500 using dl09 supah clean
Here is the ODIN back to stock if you don't want to bother with removing Voodoo. That should fix your phone with or without Voodoo. It's always worked for me.
THANKS SO MUCH its back to normal i cant thank you enough
Many thanks for all of the help.
*********************************************
CM10 is now available.
Requirements: Root
From rooted stock or a custom rom, just download and install updated Rom Manager from the Play Store and download CM10 Nightly and GAPPS. Reboot into ClockWorkMod, factory wipe, disable signature check, flash CM10 twice. The first time partitions our tabs and reboots. Flashing a second time is for good measure. Then flash GAPPS. Done.
Note: I am not sure if Rom Manager can flash ClockworkMod directly. I personally updated from ICS > CM10 by downloading CM10 and GAPPS through GooManager and flashing manually in ClockWorkMod.
Its been reported that you can go directly from rooted stock to CM10. I've actually completed everything below to get to ICS first (Stock > ICS > CM10 JB).
CM10 is a much better experience. The tab works much better, doesn't freak out, lasts longer, plays better.
*********************************************
Wow. Lots of different, confusing, and scattered information about how to go from stock Gingerbread to the latest CM9 build. It is all very confusing and honestly most of the useful information isn't even on this site. So I figured I would help myself (and others) in creating a very detailed walkthrough of the process required to successfully get from GB to CM9 Build 7.
**This specifically outlines the methods to take a COMPLETELY STOCK Sprint Galaxy Tab 7" SPH-P100, unrooted, to a ICE CREAM SANDWICH rom. I "think" it might also work for the Verizon CDMA and a few others. I think the ROM itself is a general overall generic build for all 7" Gtabs. So heads up that if you have a different version, you might want to use this as a guide rather then a step-by-step.**
BACKUP EVERYTHING YOU MAY NEED BECAUSE OBVIOUSLY THIS PROCESS WILL FORMAT YOUR GALAXY TAB
GET CONNECTED!
We need to download Heimdall's App and his Drivers (Main URL). This is the first confusing steps as everyone suggests using an older version, but the included drivers don't work on newer Windows OS's. So you have to mix and match a few different versions to get it working. I've already compiled an archive with everything you need: Heimhall Mixture /w zImage & ClockWorkMod 5.0.2.7
1. Extract everything to a simple folder [ex. C:\GTABICS ]
2. Turn off Gtab. Hold VolDown+Power until you get to a downloading screen
3. C:\GTABICS\Drivers\zadiag.exe to load drivers [try running as Administrator]
4. C:\GTABICS\heimdall-frontend.exe to start the process
5. Kind of confusing. Focus on the "BROWSE" buttons. Look for "Kernel(zImage)" on the left and "Recovery" on the right. Hit browse for each one and select the appropriate file from C:\GTABICS. Obviously "Kernel(zImage)" = "zImage" and "Recovery" = "recovery.bin".
6. Make sure Kernel(zImage) and Recovery both have files selected and a checked box. While GTAB is at the black Downloading screen: Hit "START".
7. The process is pretty fast. Don't rush. At this point your tab will probably just bootloop anyway.
LET'S GET THIS SHOW ON THE ROAD
Now you have ClockWorkMod installed and a proper kernel, most flashers will feel really at ease right now. But there are a few little quirks that will cause this to go bad. You have to install 2 versions of ICS to get to the latest; One using the existing partition table, and a second that will update to a newer format. You obviously have to install GAPPS like always with a CM rom, but not so fast, you have to manually "MOUNT /SYSTEM" in CWM before it will even take. And there is the fact that you have to manually open and edit the CM9 Build7 update and remove code....[holy crap].
But it is pretty easy once you go through it once.
REQUIRED FILES
JT1136 CM9 V5
JT1136 CM9 V7 UPDATE
GAPPS
Prepare CM9 v7 Update
1. On your PC, open "update-cm-9.0.0-RC0-galaxytab7c-KANG-BUILD7.zip" and browse to META-INF\com\google\android
2. Copy "updater-script" to your desktop and open with Notepad and remove the first 3 lines or just Download it.
3. Drag and drop the update-script back into the META-INF\com\google\android folder, overwriting the existing one.
If all goes well, you are now done with the PC.
COPY FILES AND FLASH
1. Copy Build5, the new Build7, and GAPPS to your microSD card.
2. Boot into ClockWorkMod: Power off. Hold VOLUP + POWER
3. Factory Reset / clear cache / wipe Dalvik Cache / Breathe
4. Flash zip from SDCard: locate Build5 and Flash
5. Factory Reset / clear cache / wipe Dalvik Cache / Breathe
5.5 [OPTIONAL] You should be able to boot into ICS at this point if you want to make sure build5 flashed properly before upgrading to build7
6. Flash zip from SDCard: locate Build7 and Flash
At this step, my GTab rebooted in the middle of the process the first time. It freaked me out but I assume (now) that since it changed the partition tables, it needed to reset. So I did it a second time just to be safe:
7. Flash zip from SDCard: locate Build7 and Flash
8. Factory Reset / clear cache / wipe Dalvik Cache / Breathe
Congrats. You should have a working bootable CM9 build. But lets flash GAPPS so we have our Google services. This is tricky.
9. Mounts and Storage > Mount /System
10. Flash zip from SDCard: locate GAPPS and Flash.
11. Finally [!] reset device and prepare for boot.
Now you are on the latest CM9 build [7] and have the latest GAPPS installed. Hopefully you are booting now and see the famous ICS Boot Animation. Have fun. In the future you should be able to simply download new roms as they are available and flash normally like you would any other device.
RECAP:
Drivers and Flash Tool
Pre-Edited updater-script
UPDATES
Convert to Sprint
The above procedure will set your Tab as a Verizon version. If you plan on using the Sprint cellular service or just want everything to match, then flash this via ClockWorkMod.
****************************************
I didn't do any development work. All credit goes to Heimdall for his fantastic Recovery Flasher and jt1136 for his great stills porting this awesome rom over to our Galaxy Tabs. All I did was bump and grind my way through to see a successful working flash. I figured if I didn't post a walkthrough here, I would hate myself in 6 months when I boink something up and have to do this all over again. I would recommend you keeping all of the files safe somewhere to prevent this headache again.
DONATE TO JT1134
DONATE TO HEIMDALL
MAIN HEIMDALL URL
MAIN ROM URL
player911
i have been thinking about moving up to ICS with my sprint sph-p100
just not sure if i should jump now or wait till more things are working ?
do the things working out number those not , is it ready to be a daily driver yet?
Camera fully works but is flaky sometimes. Video out isn't working yet but he's working on it.
Other then that, its golden. Very fast and works well. Really worth it. Feels much better... like an actual tablet vs a large phone.
Iffy Camera and video out aren't worth holding back. One of the benefits is now Wiimotes and PS3 controllers will pair up using their respective apps now.
Sent from my Galaxy Nexus using xda premium
Thanks for the input ill be movin up to ICS soon
Sent from my SPH-P100 using Tapatalk
flashed sprint Tab
Hello all,
Thanks for the files and instructions! Here is my situation/question:
I bought my Gtab off of ebay flashed to work on Boostmobile's 3G network. It works great, and had no problem with the official OTA upgrade to Gingerbread.
Now I'm dying to upgrade to ICS but am worried that this would mess with my 3G connection. I can't provide any details of what went into the flashing (its not a process I understand), but I'm hoping that someone out there will.
So, if I follow the instructions in this thread will I still be able to use my Tab with the boost 3G it connects to now?
Many, many thanks for any help with this!!
Great Thanks! The first complete step-to-step instruction for installing ICS on Sprint p100.
One note- if you have Error 12 - delete all SAMSUNG USB drivers on PC, rebut and instal drivers from first archive.
At least!!! Thanks a lot!
I don't use the cellular network (sprint) but it does come up and show signal. I don't use it as a phone or anything like some people (supposedly you can install phone.apk and make calls over a voice plan).
I just use the tab as a tab. I just wanted to confirm that it appears to see the cellular network fine.
Sent from my Galaxy Nexus using xda premium
just made the plunge had some issues with the drivers for heimdall and after that i got a fail when flashing hit start again and it flashed
followed all the steps and im on cloud 9 now wow
gonna take a few to get used to ICS
Well I found a sprint patch and flashed it all is well now
Sent from my SPH-P100 using Tapatalk 2
LivnDream said:
Well I found a sprint patch and flashed it all is well now
Sent from my SPH-P100 using Tapatalk 2
Click to expand...
Click to collapse
Sprint patch for what? Mind linking? No offense but posts like these without links or more information is what creates confusion.
I haven't used a patch at all and everything seems to be working. I also never heard of a patch to fix anything.
Sent from my Galaxy Nexus using xda premium
scabrerautexas said:
Hello all,
Thanks for the files and instructions! Here is my situation/question:
I bought my Gtab off of ebay flashed to work on Boostmobile's 3G network. It works great, and had no problem with the official OTA upgrade to Gingerbread.
Now I'm dying to upgrade to ICS but am worried that this would mess with my 3G connection. I can't provide any details of what went into the flashing (its not a process I understand), but I'm hoping that someone out there will.
So, if I follow the instructions in this thread will I still be able to use my Tab with the boost 3G it connects to now?
Many, many thanks for any help with this!!
Click to expand...
Click to collapse
you have nothing to worry about, 3g will still work.. i have flashed many roms on mine including ics ones and 3g still worked.
well i shouldn't say many roms...i've flashed it many times to ics and back to gb.
player911 said:
Sprint patch for what? Mind linking? No offense but posts like these without links or more information is what creates confusion.
I haven't used a patch at all and everything seems to be working. I also never heard of a patch to fix anything.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
its a sprint patch on the rootzwiki fourm for this rom ill get you a link
i got a post there with a link to the patch someone there posted
it changes the wireless from showing veirson to sprint and the tab to sph-p100
wasnt tryin to cause any confusion
http://rootzwiki.com/topic/11697-rom-cdma-aosp-ics-cm9-build7-0304/page__st__1040#entry613901
Do I need to be on stock gb or could I do this while rooted? Sorry I'm noob with hiemdall.
Sent from my SPH-P100 using xda premium
As soon as I flash version 5 I get an error that installation was aborted, what did I do wrong?
dog44 said:
As soon as I flash version 5 I get an error that installation was aborted, what did I do wrong?
Click to expand...
Click to collapse
Try re-downloading the version 5 zip again. Make sure you don't edit anything within the zip before you put it on your SD card. This happened to me when I edited the version 7 zip as instructed above.
Ok. Got it working. What is the newest ver.? I'm on 4.03
Sent from my SPH-D700 using XDA
I think 4.0.3 is the latest ported over. I have a Galaxy Nexus and 4.0.4 was just released... so I would expect delays in porting that over to unofficial devices.
The patch, I've found, is just cosmetic. Once you upgrade to ICS using this method, the build.prop has everything setup as a Verizon Device (name, settings, etc). They can all be manually changed but there is a patch that you can flash via ClockWorkMod that does everything for you.
The link was posted a few posts up.
What is DTI? I may just leave it as verizon since I get more signal. LOL
Hey what's up guys I just threw this on my sprint tab... I had a few quirks with it early... when I first flashed the clockwork mod on it, the screen was discombobulated... the capacitive touch orientation was in landscape mode while the actual screen was in portrait.
So when I had to put the files back on the tab after modifying build 7 zip. I had to figure how to unlock the screen and then and also to choose "connect USB to storage"
Then I got a little nervous while doing the wipe because it took long. I thought it froze..
Just a heads up of what could happen to other guys .
Also now after full install, I find that my ram is usually pretty low and my CPU usage is almost always @ 100 percent .
Taking away from the fluidity... any suggestions ?
I restored my email from titanium back up and also my browser bookmarks, now they don't open up or close immediately. This happens with a lot with system data restored things....
Sent from my SPH-P100 using Tapatalk
Whenever my tab starts it says encryption unsucessful, how can I get past this screen?
Here's my issue. I was using the latest racks prepared boot for CM9. The one dated 5/1 or so. I decided I wanted to try my hand at converting a nightly and flashing it on my own. I've been having nothing but trouble with the conversion process and I have no idea what I'm doing wrong.
And I've tried a few different ones of Eyeballers nightlies, but I'm always getting the same error. I just tried it using the Android script and the windows script and I'm getting different issues in each.. When I try to convert in dos, i'm getting really tiny files and most of the time it gives me a bunch of lines with items not found.
I'm really new at this but I've looked and was unable to find any answer to why this wouldnt be working or even what i could be doing wrong. I can get into the recovery, I install the converted nightly and when I try to boot into it I just get a black screen, I waited a few minutes to make sure it wasnt just something with the the device or just a first time thing but nothing happened.
on the android version I get the error attached. Im not sure how else to say whats going wrong but if someone has some suggestions I'd really appreciate it.
You might get a better response if you post this question in Racks conversion thread. Here:
http://forum.xda-developers.com/showthread.php?p=25648626
Sent from my Nook Color running ICS and Tapatalk
unfortunately I am not able to until I reach the 10 post threshold. but rather than spam to hit that. I figured I'd try this first. Thanks though. Hopefully he'll still see this.
kontam said:
unfortunately I am not able to until I reach the 10 post threshold. but rather than spam to hit that. I figured I'd try this first. Thanks though. Hopefully he'll still see this.
Click to expand...
Click to collapse
I will put a post there for you.
kontam said:
Here's my issue. I was using the latest racks prepared boot for CM9. The one dated 5/1 or so. I decided I wanted to try my hand at converting a nightly and flashing it on my own. I've been having nothing but trouble with the conversion process and I have no idea what I'm doing wrong.
And I've tried a few different ones of Eyeballers nightlies, but I'm always getting the same error. I just tried it using the Android script and the windows script and I'm getting different issues in each.. When I try to convert in dos, i'm getting really tiny files and most of the time it gives me a bunch of lines with items not found.
I'm really new at this but I've looked and was unable to find any answer to why this wouldn't be working or even what i could be doing wrong. I can get into the recovery, I install the converted nightly and when I try to boot into it I just get a black screen, I waited a few minutes to make sure it wasnt just something with the the device or just a first time thing but nothing happened.
on the android version I get the error attached. Im not sure how else to say whats going wrong but if someone has some suggestions I'd really appreciate it.
Click to expand...
Click to collapse
1.Are you using latest version of script 1.3?
2.Did you try the terminal emulator for running script?
3.Did you try to delete and extract again the folders of the c2dsd in case something went wrong during first extraction?
thanks for posting there for me.
RASTAVIPER said:
1.Are you using latest version of script 1.3?
2.Did you try the terminal emulator for running script?
3.Did you try to delete and extract again the folders of the c2dsd in case something went wrong during first extraction?
Click to expand...
Click to collapse
1. I updated both scripts and was still getting issues.
2. if you mean the one on android then yes, thats what I was using. I also tried it using the cmd on windows.
3. I've tried that at least two times with each including redownloading all aspects of it to make sure that wasn't the case.
kontam said:
thanks for posting there for me.
1. I updated both scripts and was still getting issues.
2. if you mean the one on android then yes, thats what I was using. I also tried it using the cmd on windows.
3. I've tried that at least two times with each including redownloading all aspects of it to make sure that wasn't the case.
Click to expand...
Click to collapse
Not sure about the windows issue. I'll have DizzyDen take a look at that. But with the Android version, i'll take a look at that in a little while. Looks like it's another mistake on my end. Mkimage is dependent on 'libmusl.so' which I did not include in the tools folder. I overlooked this tidbit because I had "BOTBREW" installed on my system so it never complained about linking to it.
Sorry for all the problems. I'll try and have a fix ASAP. Your feedback is much appreciated. Can't fix things if I don't know if their broken or not.
Thanks,
Racks
EDIT: Fixed I believe. Please try the v1.3a for the Android script.
I'm looking into the DOS version as we speak....
You guys are all really amazing for helping me out.
And as probably mentioned before by rasta Im not sure what the issue is but theres still something not quite gelling for the version. I took another screen to hopefully help you identify where its going weird. It is a little different but its still that crc cd issue. Im not going to try to flash it to see if it works, only because Im pretty certain that won't do it. But I really appreciate you looking into it.
and for clarity I also get a very similar if not exactly the same message when It trys to do the gapps as well. (using the 4/29 signed gapps)
And I decided now to try flashing the rom. it worked. Fantastically! though the boot animation is freezing. I dont even care about that since its actually working again. Awesome. But.. now im having those same issues as Rasta with the gapps. I flashed them and when I went to reboot it brought me to stock. When I converted them, i converted them with the rom. That rom worked. the gapps did not. if theres anything else I can help just ask and Ill try to do. Im just so happy to have a bootable CM9 again. Thank you so much
kontam said:
You guys are all really amazing for helping me out.
And as probably mentioned before by rasta Im not sure what the issue is but theres still something not quite gelling for the version. I took another screen to hopefully help you identify where its going weird. It is a little different but its still that crc cd issue. Im not going to try to flash it to see if it works, only because Im pretty certain that won't do it. But I really appreciate you looking into it.
and for clarity I also get a very similar if not exactly the same message when It trys to do the gapps as well. (using the 4/29 signed gapps)
And I decided now to try flashing the rom. it worked. Fantastically! though the boot animation is freezing. I dont even care about that since its actually working again. Awesome. But.. now im having those same issues as Rasta with the gapps. I flashed them and when I went to reboot it brought me to stock. When I converted them, i converted them with the rom. That rom worked. the gapps did not. if theres anything else I can help just ask and Ill try to do. Im just so happy to have a bootable CM9 again. Thank you so much
Click to expand...
Click to collapse
Thanks for the feedback... looking into gapps issue now... is this for primary or alternate?
Everything I'm referring to is for the alternate. Also not sure if this has anything to do with it but the calendar is broken with the gapps back from the novemeber or whenever dual boot apps. But flashing the fix doesnt fix it anymore, and then a reboot after that brings me to stock.
Also, im having issues doing a factory reset on stock when i take the SD card out.. is there something that clockwork did when it was trying to flash an incorrect rom?
If you want to return to stock situation, you probably should wipe everything and find stock image to flash.
Unleashed from my Revolutionized Desire HD
So like an idiot, I didn't take a nandroid before flashing bootanimation4u, and now, whenever I turn my phone on, my boot animation is black. It boots properly, but I just don't have a boot animation. I still have the sounds that play. Which will fine, isn't ideal. I would rather have some indication that the phone is turning on as normal than just going straight into nothing.
I have tried putting a custom bootanimation.zip file in both /system/media and /data/local and nothing seems to allow me to use a custom animation.
So reading later on in the bootanimation4u thread, it says 4.4.2 or Kitkat in general, isn't able to work with Bootanimation4u. Which is odd because I am about 95% sure that I had it working at one time or another before. So I looked at the files that the flashable zip changes, and replaced those with stock files. Still nothing, I am still getting a straight black screen.
So then I saw this thread: http://forum.xda-developers.com/gal...memade-bootanimations-collection-how-t1897969 and tried to use this, however, I have the same issue.
The custom boot animation I have been trying to use is the stock Google Nexus boot animation (the one with four circles).
This is on a Stock NAE ROM.
EDIT:
Would a dirty flash possibly fix this problem? If I do dirty flash, what issues might that cause me if the device has been modified with Hotspot / SD Card fix, and other things?
Did you try Rom Toolbox? I change these every couple days. Choose the file from your local folder, hit install, reboot. Done. If its still not working maybe it's the zip? Can you install other ani's? Maybe the Rom you use doesn't support custom boot ani's? Just thinking out loud.
Sent from my SPH-L720 using xda app-developers app
HPferoxCraft said:
Did you try Rom Toolbox? I change these every couple days. Choose the file from your local folder, hit install, reboot. Done. If its still not working maybe it's the zip? Can you install other ani's? Maybe the Rom you use doesn't support custom boot ani's? Just thinking out loud.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
I have tried several different animations, none work. All are supposedly built for this device. Using boot animation, not specifically ROM toolbox, I tried to flash some zip files I locally had with no success.
Bootanimation4u and the other link in that post, is supposed to allow for the ability to have/use custom bootanimations regardless of ROM.
slixzen said:
I have tried several different animations, none work. All are supposedly built for this device. Using boot animation, not specifically ROM toolbox, I tried to flash some zip files I locally had with no success.
Bootanimation4u and the other link in that post, is supposed to allow for the ability to have/use custom bootanimations regardless of ROM.
Click to expand...
Click to collapse
Well try Rom Toolbox, you can get the free version. Open that app, grant it root if asked, swipe over to boot animations, choose local tab, find your file and select then choose install and reboot. I don't think you can preview first in free version. When it reboots it should be your Ani. No need to flash anything. If that doesn't work try flashing a different kernel and then retry. I don't know this bootanimation4u app though, never needed it. There's lots of threads here with lots of animations just try a different method, you'll get it.
Sent from my SPH-L720 using xda app-developers app
I too am experiencing the same issue, i have tried everything i can find so far to fix this problem however all to no avail.
i have tried using rom manager and boot animation changer as well as flashing all of the different zips for bootanimation4u
any further info would be great as i really would like to get a custom animantion back
---------- Post added at 11:46 PM ---------- Previous post was at 11:24 PM ----------
ok so i managed to get this fixed right after posting.
Go to http://forum.xda-developers.com/gal...memade-bootanimations-collection-how-t1897969 and downloand "CWM_CustomBootanimation_44_Enable.zip" from the fourth post
Then use rom manager to change your boot animation
Job Done!