ok i used nvflash and reloaded the full stock nvflash with cwm 5504 beta 15. i used the directions from ray waldo's website using team drh's files. i've tried 3 different roms and they all get stuck at the 3 birds. i wipe the tablet data, cache, and dalvik, plus repartition to wipe the drive and set it at 2048-0m every time per the instructions. i feel like i haven't missed a thing but i must be. i can nvflash back to the stock roms all day long but as soon as i try ics it get stuck. sorry for the noob post, i've been trolling here for well over a year and have rooted my phones and other tablets with no real problems. any help would be greatly appreciated.
So you can flash back to the stock version. That's a good thing.
You've also put on the Clockwork (I'm assuming with touch) and I assume you can get into the recovery mode.
Have you tried the G-Harmony rom? http://forum.xda-developers.com/showthread.php?t=1645420
I loaded G-Harmony last weekend on my wife's GTab and it worked without a hitch. I know that you can't have ANY previous version on before you try to put on (probably any but at least G-Harmony ICS) ICS.
She took her tablet to work with her this morning so I don't have it here to actually walk through CWM. Since I'm a VERY old man, my memory is kind of spotty and I've eaten since last weekend but here's pretty much what I remember how I did it.
1) Loaded the new CWM (you've already done that)
2) Booted into stock.
3) Rebooted into recovery mode (power and +)
4) there is an option for mount/erase (if I remember correctly). I erased everything that didn't move out of the way.
5) did a wipe data/factory reset
6) wiped every cache that I could find.
7) loaded rom from sdcard
8) rebooted
that seemed to work. You also need to wait about 20 minutes (assuming it worked) for gapps to update.
You might try this and come back here to let me know how it went.
Good luck,
Gregwa
i'm not seeing an option for mount/erase. basically what i do is repartition and that wipes the drive. is that where i'm going wrong? also i'm using only the internal sd to load the g-harmony.
aso i just noticed when i go to wipe the dalvik i get E:unknown volume for path [/sd-ext]. before i even wipe it. is this normal?
That might be the issue. In addition, the missing partition may be another issue.
Did you look under Mounts & Storage (or something like that) near the bottom of the CWM screen?
I'll have to wait until my wife gets home tonight and pry the GTab out of her fingers (she's now addicted to pocket frogs) to get the complete menu items for you if you can't find it.
It's now 10:27am Mountain Time (USA). Try checking back (if you didn't find it) around 8pm Mountain time (9 central, 10 eastern (I sound like an ad for a tv show, huh?)) and I should have the steps for you then.
Gregwa
Ok. With the help of food and a 4 foot crowbar, I was able to get ahold of her gtab for 5 minutes.
The top level menu items of CWMR are:
- Reboot System Now
- Install Zip From SDCard
- Wipe Data / Factory Reset
- Wipe Cache Partition
- Backup and Restore
- Mounts and Storage
- Advanced
- Power Off
What we are interested in right now are Wipe Data/Factory Reset, Wipe Cache Partition, Mounts and Storage and Advanced.
So starting from stock with CWMR Touch 5.5.0.4 Beta 15
Wipe Data/Factory Reset
Wipe Cache Partition
Under Mounts and Storage
Format /boot
Format /cache
Format /sdcard
Format /emmc
Format /data
Format /system
Then mount each in menu order.
Under Advanced
Wipe Dalvik cache
Then install zip from where ever you placed it (usually internal sdcard)
That SHOULD work. As far as I remember that's what I did.
Let me know how it goes.
Gregwa
so in mounts a storage all the stuff listed mount or unmount should read mount? or change them all to unmount?
I BELIEVE the mount/unmount are status & command both. In order to format one of the "drives", you'll need to mount it first.
So yes, you will need to mount before you format.
i i need to format each and then go back and unmount and remount each?
its getting late (11:30) and the beer is starting to kick in. i'm still getting that unknown sd error and everytime i get the 3 birds. i'll have to start again in the morning. thanks for the help. hopefully i'll get it tomorrow.
Yes, it is getting late.
Give it a try tomorrow and I'll try to check in every once and a while.
still no luck. i've followed your install plus many others just to see. i can put it back to stock and that seems to be about it.
Have you tried a lower version rom like GCombover?
You might try that and see if that (at least) works.
Gregwa
i just reloaded the original 1.1 bootloader with nvflash. i then install a version of cm7 with no problems. it booted right signed in open the updated to play store. i'm wondering if the nvflash file for the 1.2 bl might be corrupt.
still no luck. i reloaded all the 1.2 bootloader stuff from the team drh thread and tried their version and still get stuck at 3 birds.
I think that the 1.2 bl is the issue. Since you can deal with a 1.1 rom with no problems, we need to focus that.
Let me do some research and I'll get back to you this evening.
Gregwa
---------- Post added at 10:03 AM ---------- Previous post was at 09:57 AM ----------
I wasn't sure I could find this so quickly.
Here's jamcar's guide to upgrading the 1.1 bl to the 1.2. Have you tried it?
http://forum.xda-developers.com/showthread.php?t=1397728
gregwa said:
I think that the 1.2 bl is the issue. Since you can deal with a 1.1 rom with no problems, we need to focus that.
Let me do some research and I'll get back to you this evening.
Gregwa
---------- Post added at 10:03 AM ---------- Previous post was at 09:57 AM ----------
I wasn't sure I could find this so quickly.
Here's jamcar's guide to upgrading the 1.1 bl to the 1.2. Have you tried it?
http://forum.xda-developers.com/showthread.php?t=1397728
Click to expand...
Click to collapse
man i just can't win. this didn't help either.
so it looks like you are stuck with a 1.1 bl rom.
Just for grins and giggles, try going to the GTabCombOver page http://forum.xda-developers.com/showthread.php?t=1424963 and download the 1.1 version of their rom. If it works, then we know you (for some reason) have to deal only with 1.1 version roms for a while. This is a Honeycomb 3.0.1 version and it worked quite well on my wife's GTab. This will get you closer to your goal until we can find a way to get you up to 1.2 BL for real.
One good thing about GTabCombover is that you don't have to deal with wiping everything for good. The instructions are clear and easy.
I'll keep my body parts crossed for you.
Gregwa
i successfully loaded GTabCombOver with out any glitches. it definitly has something to do with the 1.2 bootloader. i wiped it out again and tried the aokp ics rom and again i'm stuck at the birds. i need to get titanium back up installed so i can save my stuff on GTabCombOver while i'm figuring out the bootloader thing.
your probably not going to beleive this but i just got a version of ics to load and work with the 1.1 bootloader!!!! now i just have to see how stable it is.
Related
So this time I'm going to be a little preemptive. I ordered a GTab like a week ago, spent the time waiting for it to get here doing a ton of reading so I could go ahead and get it flashed right away. It got here and I immediately ran into problems. I got CWM on there no problem and first flashed [ROM-AOSP]G-Harmony Gingerbread 2.3.3 with Honeycomb elements(UPDATED 4/17) with no problem. Didn't like it so tried to flash the CM7 nightly (which I have running on my evo and hero) and it kept getting stuck on the black screen with that just had "android" written on it really small. Since I hadn't anticipated running into something like that, I did even more reading. Decided to try some more roms and see if I had similar problems. Ran into similar problems with the vegan GB except it would hang on the powered by the "gtabdevs" screen or whatever it said. Vegan 5.1 or whatever the other Vegan one is I could get booted up fine though. So I read some mroe since I really wanted CM7. Discovered that I might need to re-partition, so went into CWM and repatitioned to what everyone was saying was the correct settings. Still a no go and got stuck on android screen. So after even more reading I kept seeing everyone saying NVFlash. So I found it, downloaded everything, read the sticky post on how to do it like 4 times before trying it, then gave it a shot. Put the tab into APX mode (vol- and power) and flashed everything and then when it was done, it was stuck in the APX mode. Very irritating considering I had only had it for about 6 hours. Anyways, sent it back and am getting a new one. It will be here tomorrow morning.
Sooooo, after that long winded explanation of everything, here is my question... How the **** can I get CM7 on my tab without wrecking it again? I did a ton of reading, and nothing I had seen helped at all. Everyone says wipe this and wipe that, or mount these then wipe those, or nvflash then do it and so basically I'm just not sure what to do. I WILL NOT use the nvflsh again and risk getting the APX loop, so any good advice would be most appreciated.
Thanks in advance
I just email walked my sister through installing CM7 on her new gtablet.
Have CM7harmony7.02.zip (or whatever.....7.02 is latest stable release....there is a newer nightly though if you prefer that), the gapps.zip on your computer.
install Clockworkmod recovery on your tablet like you did before.
Boot into CWM and partition sd card, 2048 for first partition and 0 for the second one.
attache via USB to your computer, mount usb option in CWM and copy the ROM.zip and the Gapps.zip to your tablet. Eject tablet from computer (USB eject) and unmount in CWM.
- wipe data/cache (factory reset)
- advanced, - wipe davlik cache
install .zip from sd card
(install the ROM, then choose to install .zip from sd card again and install gapps).
Reboot.
Make sure your tablet is NOT running OS 3991 (very unlikely) or 4349 (possible though unlikely) before doing any of this. (ie...boot tablet out of box and check it's OS version in settings).
Thanks for the walk through. Hopefully it will go smoothly this time around. I'll post back tomorrow after it gets here on if it worked out or not.
If it does have one of those 2 versions on it, I assume I just use the down grader from the thread taking about those 2 versions?
Sent from my PC36100 using XDA App
ix3u said:
Thanks for the walk through. Hopefully it will go smoothly this time around. I'll post back tomorrow after it gets here on if it worked out or not.
If it does have one of those 2 versions on it, I assume I just use the down grader from the thread taking about those 2 versions?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Correct, downgrade and then proceed.
Even though I'm 100% sure that at some point of me trying last time that I did in fact do all of those steps, it was a no go.....But this time, I'm sitting here watching the CM7 boot screen
Thanks a ton
I had a working Cyanogen 7 flashed on the gTablet. And due to enthusiasm, I updated with one of the nightly builds and started seeing some issues.
I assumed that clearing the cache and rebooting would help and ended up doing the 'Wipe Cache Partition'. Now the tablet wont boot at all. But I guess its not bricked at all since I am able to get to CWM.
What do I need now to get back to CM7?
Also my search on what the 'wipe cache partition' function doesn't give me the full picture. Now I know that I shouldn't have done it in the first place. But being affected by it I request if one the Gurus on XDA's please shed some lite.
Regards and thanks for the help in advance.
venkavis said:
I had a working Cyanogen 7 flashed on the gTablet. And due to enthusiasm, I updated with one of the nightly builds and started seeing some issues.
I assumed that clearing the cache and rebooting would help and ended up doing the 'Wipe Cache Partition'. Now the tablet wont boot at all. But I guess its not bricked at all since I am able to get to CWM.
What do I need now to get back to CM7?
Also my search on what the 'wipe cache partition' function doesn't give me the full picture. Now I know that I shouldn't have done it in the first place. But being affected by it I request if one the Gurus on XDA's please shed some lite.
Regards and thanks for the help in advance.
Click to expand...
Click to collapse
Hopefully a guru can answer this question. A guru I am not..
But what I think you did should not be an issue. I typically wipe data and then wipe cache partition when flashing a new ROM. sometimes I wipe cache and data just to get the ROM running from scratch again. But this should not affect booting..
One thing I think might be the problem is that you have a new kernel from one of the newer nightlys. Recently they added perhsoots May kernel. Whenever a new kernel is included in a nightly you usually need to clear dalvik cache. this is in CWM under advanced.
I hope this helps.
Tried clearing dalvik cache. No change.
Going back to stock and see.
Copied the stock ROM file and used the CWM to do the update. Now the g Tablet is gioing into a Boot loop. It Tap n Tap then displays a animated icon and after a minute repeats the same.
Tried the recovery option and its going into an installing loop again. Not sure how to get out of this.
Does anybody have this experience before?
Is this bricked now? Call viewsonic support? I am not sure if they support, They may say its nor under warranty.
Just to remind you, the last effort to resolve this is to NVFLash it...
Have you tried CWM method twice or repartition it and do it again? It's a tablet for you to enjoy your Internet, reading, video but not flashing all day long..etc
To pass it quick, if I were you, I would NVFlash it back to 3588, put back my favorite ROM, reinstall the Apps I like and start Internet browsing, converting movie (so I can watch on the road), reading news...
good luck!
rcjpth
After this I definitely agree. But seems I am stuck again. Hope this is the last time.
I followed the steps as in the below URL
http://forum.xda-developers.com/archive/index.php/t-1040434.html
My PC successfully connected to the gTablet and did the bvflash. After that I booted, it still went into the same. I am not sure if the nvflash worked at all.
Not sure what I am missing here!
Called Viewsonic support and the tech support person pointed me to below post on XDA
http://forum.xda-developers.com/showthread.php?t=1036956
When I read the article it talks about a locked boot loader. Does is mean if I use this and fix the tablet, I will not be able to do any more rooting?
venkavis said:
I followed the steps as in the below URL
http://forum.xda-developers.com/archive/index.php/t-1040434.html
My PC successfully connected to the gTablet and did the bvflash. After that I booted, it still went into the same. I am not sure if the nvflash worked at all.
Not sure what I am missing here!
Click to expand...
Click to collapse
So you also tried the alternate file, nvflash_gtablet_46_2010112600.zip? That's what worked for me, but I also have to swap partitions 7 & 8 to get CM7 working again.
Since I'm a glutton for punishment, I wiped my cache from nightly 75 and didn't run into any problem.
Just downloaded the alternate zip and flashed again. Having the same looping issue.
Seems like I Have to send it to viewsonic only. The technician said there is a $75 charge to fix.
So, I have the Samsung Fascinate from Verizon, had this phone when it was new and just found it again and it is much better than my blackberry, or so I thought. I am trying to install ICS build one by following http://forum.xda-developers.com/showthread.php?t=1238070: - I have been able to install PW but when I am trying to install ICS1.zip (I renamed for simplicity purposes) I get the following errors: E: Can't mount /cache/recovery/log and cache/recovery/last_log
I have read enough to know that I needed a class 6 or better SD card so I bought a Class 10 8 GB from Best Buy and gave it another shot. I have mounted and unmounted the SD card multiple times, and when installing it shows:
-- Installing: /sdcard/ICS Build 1.zo[
Finding update package...
Opening update package...
Installing the update...
Installation aborted.
Any suggestions are greatly appreciated by those with positive feedback or calling me ignorant and not finding the answer online. Again, thanks in advance.
P.S. Yes, I have installed everything up until step 19 is where it stops working
Hey, i have had this problem as well when installing ICS. First off i would recommend installing build 6 instead of build 6.1 because build 6.1 actually has more problems that build 6. you can get build 6 from here : http://rootzwiki.com/topic/16630-romicsiml74k-teamhacksungs-ics-port-for-fascinate-build-61-0201/
Now to fix your sd error, you need to use the odin program and flash your phone back to any stock firmware. Here is verizon stock EH03 : http://www.multiupload.com/4LC6JFCSFD I'm sorry it is such a large file, verizon puts a bunch of crap on their firmwares lol As for your sd card, i honestly do not think it makes a difference what class it is. I am using a class 2 16gb sd card and have never ever not been able to get something to work.
Now after that is done, and it has booted to stock verizon firmware, put the phone back into download mode and use the odin program again to flash a cwm recovery kernel. This one should do just fine, if for some reason it doesn't, let me know and i will upload mine and you can have it. http://forum.xda-developers.com/atta...2&d=1311907538
After you have used odin and flashed a cwm recovery, please power off your phone and hold down the volume up, down, and power keys at the same time till the samsung logo comes on, so you can go into the new recovery kernel that you flashed to it. Once there, go to the option where it says wipe data/factory reset. After that has completed, do the next option that says wipe cache. Once that is all done, you will say "install zip from sd card" and navigate to the .zip
Now here is where you have two options....you can either flash build 1 first and then build 6, or you can skip straight to build 6. Personally i would skip straight to build 6!! It should work just fine as long as you have wiped data and cache. The differences between build 1 and 6 are night and day and you would have to clear data and cache anyway after you had build 1, so you should be able to go strait to build 6. Other people i have helped went fine right to build 6
After installing the .zip, navigate to the option that says "reboot system now". if you encounter a boot loop that constantly goes into the cwm recovery, let me know! I have dealt with that first hand! let me know if you have questions
Also i recommend using the magnifying glass capacitive search key to make your selections when in cwm, because for some reason i feel using the power key was partly the reason i encountered the cwm boot loop
So you odined back to stock and then tried flashing build 1 in cwm4 fixed for mtd?
---------- Post added at 09:02 AM ---------- Previous post was at 08:59 AM ----------
kadin.zimmerman said:
Hey, i have had this problem as well when installing ICS. First off i would recommend installing build 6 instead of build 6.1 because build 6.1 actually has more problems that build 6. you can get build 6 from here : http://rootzwiki.com/topic/16630-romicsiml74k-teamhacksungs-ics-port-for-fascinate-build-61-0201/
Now to fix your sd error, you need to use the odin program and flash your phone back to any stock firmware. Here is verizon stock EH03 : http://www.multiupload.com/4LC6JFCSFD I'm sorry it is such a large file, verizon puts a bunch of crap on their firmwares lol As for your sd card, i honestly do not think it makes a difference what class it is. I am using a class 2 16gb sd card and have never ever not been able to get something to work.
Now after that is done, and it has booted to stock verizon firmware, put the phone back into download mode and use the odin program again to flash a cwm recovery kernel. This one should do just fine, if for some reason it doesn't, let me know and i will upload mine and you can have it. http://forum.xda-developers.com/atta...2&d=1311907538
After you have used odin and flashed a cwm recovery, please power off your phone and hold down the volume up, down, and power keys at the same time till the samsung logo comes on, so you can go into the new recovery kernel that you flashed to it. Once there, go to the option where it says wipe data/factory reset. After that has completed, do the next option that says wipe cache. Once that is all done, you will say "install zip from sd card" and navigate to the .zip
Now here is where you have two options....you can either flash build 1 first and then build 6, or you can skip straight to build 6. Personally i would skip straight to build 6!! It should work just fine as long as you have wiped data and cache. The differences between build 1 and 6 are night and day and you would have to clear data and cache anyway after you had build 1, so you should be able to go strait to build 6. Other people i have helped went fine right to build 6
After installing the .zip, navigate to the option that says "reboot system now". if you encounter a boot loop that constantly goes into the cwm recovery, let me know! I have dealt with that first hand! let me know if you have questions
Also i recommend using the magnifying glass capacitive search key to make your selections when in cwm, because for some reason i feel using the power key was partly the reason i encountered the cwm boot loop
Click to expand...
Click to collapse
Build 6 link is dead...and for most flashing build 1 or 2 first is the only way ics build 6 will install. Also many folks have had trouble with class 2 sd cards...your not doing anything special more so just lucky its working for you.
kadin.zimmerman said:
Now after that is done, and it has booted to stock verizon firmware, put the phone back into download mode and use the odin program again to flash a cwm recovery kernel. This one should do just fine, if for some reason it doesn't, let me know and i will upload mine and you can have it. http://forum.xda-developers.com/atta...2&d=1311907538
Click to expand...
Click to collapse
That link does not work for me just FYI. I am currently back to stock (it's what I do when I can't get it to work because I am not to big of a powerwash fan. I have cwm4 to cm7. I believe it is 4.0.1. But I will search for the latest cwm recovery and put it on and see if that fixes any issues. I also saw somewhere a few days back that people format their SD cards on their PC but I do not remember what format so if that is completely irrelevant since the SD card is brand new (Almost 12 hours old) let me know. I will keep you posted and see it works.
New link to build 6 : http://www.mediafire.com/?sjn6x76c48me9su
So if going right to build 6 didn't work, then you would just have to give it another try, but installing build 1 or 2 first. No big deal, however I do know people who have had it work just fine.
I never said i was doing anything special because i had a class 2 sd card. I simply find it hard to believe that the sd card would have that much of a bearing on whether or not you can install a rom on a phone. I realize some roms partition the sd card the way it wants it, but in the end, the rom is flashed onto the actual phone itself, not the sd card. I know what the difference is between different classes of sd cards so you don't have to explain.
---------- Post added at 03:58 PM ---------- Previous post was at 03:52 PM ----------
PushyFurball said:
That link does not work for me just FYI. I am currently back to stock (it's what I do when I can't get it to work because I am not to big of a powerwash fan. I have cwm4 to cm7. I believe it is 4.0.1. But I will search for the latest cwm recovery and put it on and see if that fixes any issues. I also saw somewhere a few days back that people format their SD cards on their PC but I do not remember what format so if that is completely irrelevant since the SD card is brand new (Almost 12 hours old) let me know. I will keep you posted and see it works.
Click to expand...
Click to collapse
Sorry i thought that link was working...here is the one i originally start out with when flashing from stock. : http://dl.dropbox.com/u/32493357/cwm4_fixed_for_cm7-ODIN.tar
Please don't hit me, dropbox link doesn't work either.
PushyFurball said:
Please don't hit me, dropbox link doesn't work either.
Click to expand...
Click to collapse
Give it another try, it is working for me when i click on it
When I go to "wipe data/factory reset" I still receive the errors about opening stuff and this is what it looks like
-- Wiping data...
Formatting /data...
Formatting /cache...
Error mounting cache!
Skipping format...
Formatting /datadata...
Error mounting /datadata!
Skipping format...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
E: Can't open/mount /cache/recovery/log & .../last_long
-Exactly what I am doing step by step including what is clicked-
From stock, I open odin, pull out the battery, connect to PC via USB cord, press vol - on the phone. Then, I click, PDA, go to ..../Downloads and find the cwm4_fixed_for_cm7-ODIN.tar file and populate that portion of odin and put alas.2.2.pit in the pit section with the re-partition clicked. After completed, I go to odin, hit reset while the phone is still connected and then disconnect the phone. I put the battery in the back, press vol +/- and power and hold that until I see Samsung (which I don't see so I hold it for about 45 seconds to a minute and it boots it CWMR 4.0.1.0) and start trying to clear stuff and that is when I get the errors. So what I have done this time, is formatted the SD card in the recovery menu which I saw was not suggested, and I am going to try to just do a fresh install and maybe it was in the wrong format, who knows.
Ok, turn your phone off, remove the memory card, and flash this kernel instead : http://dl.dropbox.com/u/32493357/CWM3_Voodoo.tar.md5
Then put the memory card back in and boot to recovery
---------- Post added at 04:50 PM ---------- Previous post was at 04:32 PM ----------
PushyFurball said:
When I go to "wipe data/factory reset" I still receive the errors about opening stuff and this is what it looks like
-- Wiping data...
Formatting /data...
Formatting /cache...
Error mounting cache!
Skipping format...
Formatting /datadata...
Error mounting /datadata!
Skipping format...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
E: Can't open/mount /cache/recovery/log & .../last_long
-Exactly what I am doing step by step including what is clicked-
From stock, I open odin, pull out the battery, connect to PC via USB cord, press vol - on the phone. Then, I click, PDA, go to ..../Downloads and find the cwm4_fixed_for_cm7-ODIN.tar file and populate that portion of odin and put alas.2.2.pit in the pit section with the re-partition clicked. After completed, I go to odin, hit reset while the phone is still connected and then disconnect the phone. I put the battery in the back, press vol +/- and power and hold that until I see Samsung (which I don't see so I hold it for about 45 seconds to a minute and it boots it CWMR 4.0.1.0) and start trying to clear stuff and that is when I get the errors. So what I have done this time, is formatted the SD card in the recovery menu which I saw was not suggested, and I am going to try to just do a fresh install and maybe it was in the wrong format, who knows.
Click to expand...
Click to collapse
Actually i have never put a pit file into odin. When ever i went back to stock i just did the stock .tar.md5 file and it worked fine. I am not sure what the pit file is used for so maybe i would not use that. Let me know if that voodoo recovery got rid of that error
So the good news first, not putting PIT on their got rid of the errors of mounting and whatnot. Bad news is...
-- Installing: /sdcard/ICS Build 1.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
That is the same for Voodoo Lagfix and cwm4.
Now when I tried just the Build 6, it is constantly going to "Samsung" over, and over, and over again.
Ok good you are making progress lol. So you did try it with build 1 initially and it didnt work? Thats strange because it usually does.
So have you gone completely stock without the pit file, loaded a cwm kernel, and then wiped data and cache and still no luck?
There are two different versions of ICS for the fasciante, one by alphalulz and the much better builds from teamhacksung. No matter what i tried and it didnt work on my device (before i eventually figured it out) , alphalulz's ICS V2 always would load on my device. It also loaded its own custom kernel as well, so when it installed, i would let it boot up to confirm the V2 version was working, and then i would clear all data and cache in the new kernel it gave you, and then would switch over to teamhacksungs builds.
here is the link to download the V2 rom : http://rootzwiki.com/topic/9687-rom-aosp-ics-extreme-alphalulz-v2-1118/
Oh. My. Goodness. We have a good sign that this beast is going to work with Teamhacksung's versions... I don't really know what I did, I went back to stock with the pit file, downloaded build 1 while this was processing, and booted it up after it was finished. Then from there, I put that file, original name on my SD card and turned off my phone. Pulled the battery and odin'd cwm4 to cm7 and unplugged. Put the SD card in, booted to recovery, wiped the appropriate files, clicked install zip from SD card, picked the original name, and BAM!, it worked. So now I am going to try to put on build 6 and will edit this post to let you know if it worked or not. I am so happy I could literally jump up and down screaming like a little girl.
----EDIT----
Well, that failed miserably. Stuck on Samsung screen now. So, I guess back to step one.
PushyFurball said:
Oh. My. Goodness. We have a good sign that this beast is going to work with Teamhacksung's versions... I don't really know what I did, I went back to stock with the pit file, downloaded build 1 while this was processing, and booted it up after it was finished. Then from there, I put that file, original name on my SD card and turned off my phone. Pulled the battery and odin'd cwm4 to cm7 and unplugged. Put the SD card in, booted to recovery, wiped the appropriate files, clicked install zip from SD card, picked the original name, and BAM!, it worked. So now I am going to try to put on build 6 and will edit this post to let you know if it worked or not. I am so happy I could literally jump up and down screaming like a little girl.
----EDIT----
Well, that failed miserably. Stuck on Samsung screen now. So, I guess back to step one.
Click to expand...
Click to collapse
Hey your getting closer...you will get it dont worry lol
so you just had build 1 working right?? go from build 1 to build 5 (being sure to clear data and cache) and then from build 5 to 6, ONLY clearing cache. Going from build 5 to 6 does not require a data reset.
I am a new proud member of having a Samsung Fascinate with 4.0.3 . Thank you so much for your help kadin.zimmerman!
-Thread Closed- ^_^
Now download ROM manager and do a backup so you can revert back to that state in case something goes wrong! I do backups about once a week
Sent from my SCH-I500 using XDA App
I installed FA16 (2012/1/16): ODIN CWM that was listed on the first page of the developement forum. There were no issues - only took a few minutes. Afterwards - nothing seems to have changed on my phone. the firmware is still 2.3.5, the kernel is still 2.6.35.7 and the build number is sch-i500-eh03. Have I missed something? The phone seems to be working OK. Note: I installed CWM from the ZIp file after I put it on the SD card in the root directory. Thanks for your help
No you haven't missed anything - you flashed a new recovery kernel. Do you know what the purpose of the recovery kernel is? The recovery does not effect your 2.3.5 operating system, the cwm recovery allows you to boot to it (by powering the phone completely down, and then holding the up volume, down volume, and power button simultaneously) and then you will be presented with a menu to install a custom rom such as the new android 4.0 or the cm7 cyanogen mod etc...so its pretty cool
Thanks for 'learning me'. Anyway, before i started playing with my Fascinate today, I had ver 2.2.1 installed - worked fine. After all the changes, I lost the Google search box on the home page - is there anyway I can get that back? I have the icon - just like the search box better. Thanks
Well what all changes did you do other than installing a recovery? Did you flash any files?
And you have 2.3.5 now right, so how did you get it. Did you do a Verizon over-the-air update or did you flash that file as well. I am just confused as to what you did because technically if all you did was install a recovery, it wouldn't mess with you Google search
kardin - recoveries and kernels are 2 completely different things. You keep saying CWM recovery kernel, but that doesn't make any sense. I'm not saying you don't understand what a kernel or recovery is, but they're not the same thing and I think you might confuse people when you say recovery kernel.
Ok so I rooted and RoM'd my phone a long time ago with Cherryblur which apparently is no longer supported or updated. It has been so long that I forgot what I did and did not do to get cherry on it. Yesterday I spent most of the day researching how not to brick my phone. Today after doing everything I could find, I am stuck at the motorola screen. It is unlocked on the moto screen, has fastboot and adb installed, I can get into recovery and what seems to successfully recover the cherryblur install just results in a bootloop at the custom animation that is past the motorola screen.
I was trying to flash CM7 (tried neutrino as well) non nightly when this happened. After spending all day on here bouncing around while I was at work I found a fruitcake that seems to be the only thing that will allow my phone to boot which of course I cannot send the link to. Its titled [Fruit Cakes] XDA Re-Release [feb\18\2012] if you need to see it. What am I missing, I have clearly searched and searched these great forums (I do love to research, but find I'm at an impasse now) and am not sure what I need to do to proceed. That fruitcake updated my phone to 4.5.91 and I'm pretty sure I was 4.5.2 from the Cherryblur previously.
Thanks for any help!
Update: After getting fruitcake to work, I figured maybe this fixed my previous issues and tried to install CM7 again. Same story, not moving past the first Moto screen. So I tried recovery of the fruitcake and now the M screen comes up, waits a bit, then looks like it's going to load and starts to flash for about a second on, then off for 2-3, then on and so forth. I reflashed fruitcake after this and it is still working as a new install.
You are probably only softbricked. Do you know what "recovery" software you are using? If you are using romracers or one of the better respected recovery software packages, you should be able to use fastboot (if you have a windows machine) to wipe the relevant partitions on your phone and start again. Essentially, you will want to reinstall cherryblur (or install a new ROM - Neutrino, Nottachtrix, CM9s are all excellent) from your sd card. To do this, you will boot to fastboot and run "fastboot -w" from your pc. Then boot to recovery, and wipe cache, and dalvic for good measure, then install cherryblur or another package from the zip file. This will hopefully square you away and get rid of the boot loops.
My guess is that you did not wipe your partitions completely before attempting a new install, and may be having problems with ext3 vs. ext4 formatting between rom versions. Good luck to you.
Thank you for the reply!
Originally I'm pretty sure it was CWM, through the process of backing stuff up I installed Rom Toolbox from market and that seemed to have changed something? (Not sure here...) The text changed color from what I thought was white to blue and it looked a tiny bit different. The only thing I did not do was the fastboot -w, but I did download the link from [Batch] FFW - Fastboot Full Wipe and ran the fastboot from there, which was supposed to do a full wipe from what I read. Fastboot was previously installed on the phone.
I downloaded the 1.1 version which apparently may not be able to wipe the webtop, though when watching the text during the wipe it seemed to go through. Would you recommend me going to romracers, is it possible that my recovery software is borked somehow or just not compatible with the newer roms? If I got to RomRacer will the process of doing that just get rid of the current recovery software I have on the phone or will I run into issues? As far as the dalvik and cache I did run those, though the instructions for the CM7 said to do that after the install which felt backwards....
Oh yes, and I can't reinstall cherryblur, that rom is gone - you can't even download it anymore. I am doing this because I recently purchased a lapdock and the cherryblur was not doing so hot on it so looking to install a good clean rom (with a nice GUI) that works well on the lapdock as well. Yes, I will put an OC'd kernel on it as well, battery life has never been more than a day on my current rom and I am reading that the newer ones have over 1 day life on them so you could say I'd be used to the battery drain on the 1.3 kernels.
I see...that's frustrating. I think given your situation, I would probably not attempt to go from Blur to CM (at least while attempting to get the phone running again). If I were in your shoes, I would do the following...other more knowledgeable folks may steer you in varying directions, but I have been in your shoes before, and this should work. I am assuming you have use of a PC...if not, this won't be helpful.
1. Install ROMRacers recovery using these instructions: http://forum.xda-developers.com/showthread.php?t=1204500
2. Download Nottachtrix 1.3.1 to your SD card using your PC if necessary, and you will probably want to download the webtop 2.3.6 at the same time. These can be found here: http://www.nottachtrix.com/forum/
3. Boot into fastboot (hold volume down on power up, until fastboot appears, then hit volume up, and use a DOS prompt to do the fastboot commands through the USB on your PC), and do a fastboot -w, then fastboot -reboot.
4. This time boot into recovery by holding volume down on powerup, and hitting volume down seven times (I think) until you see the word recovery, then hit volume up.
5. Use recovery to wipe cache partition, then go to advanced and wipe dalvic cache, and then select factory reset/wipe data. Some of these steps may be duplicative, but I am a belt and suspenders kind of guy.
6. Now go to "install from sd card" and select the Nottachtrix build that you put on your external SD, and make selections using the cool Aroma installer. Once this installs, you can install the newer 2.3.6 webtop (if you need it).
7. Reboot when complete, and you should have the latest stock build in working order, and then you can repeat the process to install Neutrino, CM9 or whatever. Feel free to fire back any questions.
Good luck to you, and if this helps, please hit the "thanks" button!
Ill give this a shot when I get home, darn work blocking the download links for mediafire..... The fruitcake is driving me nuts, no notification bar (my biggest complaint) unless I use ADW launcher, which has for some reason no way for me to get into my texts..... Broken apps, and a real stock feel that is just making me grit my teeth lol.
Can't wait to have a nice ROM on my phone again. Glad the fruitcake got me back up and functional though!
So far so good! Had the notification bar problem like others with the 2.3.6 issue and found that fix (disable email notifications....). When / if I can 'thank' I will! And will keep you updated when I get the time to flash another rom.
Good news that you are back rolling again. Let the ROM flashing addiction continue
So, CM7 is pure sexy - and an OC'd kernel to 1.3 makes me so happy in both CM7 and Nottachrix. Wish I would have done it sooner, I wouldn't have been spending so much time searching for a new phone because my atrix was annoyingly laggy. Lag? What is that? Also, undervolting is AMAZING for battery life, for the first time since owning the phone I did not plug it in last night and even though my usage was in the light to medium area, im still at 66% after 22 hours off charger ! Can't wait to play with CM9.
Happy new owner of Amaze after three plus years on my Nexus One.
My device is unlocked, rooted, with S-On.
I purchased and successfully used 4ext, tried two CM ROMs in the last week.
Before trying these Roms, I Nandroid backed up the ROM installed on the phone when I first got it, which was running ICS 4.0.3 / Sense 3.6. (Didn't like Sense UI - was dissatisfied with one UI over another); I like the mimimalism of the CM ROM, as I've gotten used to CM7 on my Nexus one.
Anyways, settled on a CM10 ROM. This too is backed up in addition to the first Sense Rom. Man.... wish the audio skip wasn't there when playing music and was really not thrilled with low speaker volume after putting up with that on my Nexus One for years.
So I decided to try CM9.
Downloaded a CM9 zip from Goo and the correct Gapps.
Before asking for help, I have Googled several variants of my problem until I see purple links highlighted: translation, I have not been lazy to not try and look and find a solution - the links on the page aren't blue anymore, but purple because I looked and read those. I have seen plenty of threads describing my problem; maybe I've overlooked something , but this is the first time in years I have decided to ask for help. Moreover, I spent a good week bookmarking over 40 threads - organized into specific headings - in order that I could fast search for typical problems like I have now. Hate being defensive, but I see the last couple years the landscape is rife with folks rightfully being told to search before asking questions.
'nuff talk, here's the problem.
I placed the CM9 and Gapps thread onto my internal sd card as usual, then booted into recovery, into 4ext no problem. Prepared to wipe "data/factory rest/wipe and wipe cache, wipe dalvik cache".
This is what I did different from previous flash. After wiping data/factory reset... I choose "format all partitions (except sdcard" I had read enough tutorials to see that was an additional option to the wipe cache/wipe dalvik cache. Also, I was prompted to - (and this was maybe the stupid thing I did differently) - prompted with an option to uninstall smartflash. I choose the tick box... big no-no? (But I have seen in several repeated attempts to recover and restore either Rom back up, the option to "enable or disable" smartflash.
So maybe it never was actually uninstalled from 4ext? since I can see it as an option when I return to recovery. Of course I have done this after my first attempt to reboot - after installing CM9... which is described next
So after wiping data/factory reset and "format all partitions (except sdcard" ...then I installed the CM9 zip and the gapps zip, then selected reboot.
Upon selecting 'reboot' - got the infamous HTC splash screen. Then I calmly read many threads, thinking I'd solve the problem.
So far, here's what I tried as an attempt to fix/restore or learn something useful that will help me with any future steps i need to take.
1) I tried to reflash the CM9 zip. (Still did the wipe/rest but then wiped cache/dalvik cache" (no change, got splash screen)
2) Tried to restore either back up a couple times. (Each time did the wipe/reset but then wiped cache/dalvik cache" (no change, got splash screen)
3) Tried to reflash the 4 ext zip. (Hmm... won't install it aborts installation)
4) I can toggle usb storage
5) Looked at all the options within the 4ext UI just to be a 'rat in the maze' and get familiar with all the options so when i ask fort help i can perhaps navigate their faster with some confidence.
6) Went to sleep at 4am... not complaining at all.. we all have done this playing with these devices. This is just an inconvenience, I get it. I'll be putting my sim card into my Nexus one to be phone functional today while I stay on the road to figuring this out. (I know I need a 4g sim card if I want to use wifi callling on my Amaze.... but I don't care about that right now)
7) Fully charged Ruby just in case battery power could be an issue. Tried to reflash again this morning. No dice.
I know there's an answer. I know I have probably read the answer.. or the steps I need to take are in a thread somewhere... but I am a rat in a maze and don't know where to turn.
Thanks fellas.
Ed
Instead of wiping
additonal info/may help
Update:
I'm still reading, and I just read:
"There are some ROM specific files on the SDcard but a full wipe (all partitions except sdcard) clears them too"
This seems to say it was wrong to 'wipe all partitions except sdcard'. Was this cause of my problem?
Also:
1) I have enabled "smart flash" under the option. (so I assume smartflash was never uninstalled)
2) Looking in the 4-ext "boot_backup" folder. I see boot.img files. There are three new ones that were added after my problems started.
I just read:
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just what thee name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of something called a Linux kernel. This means that your bootloader boots the Linux kernel and the hardware of the device. The Linux kernel then boots the Android OS. The kernel is also the connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on the system partition you will have troubles like Wifi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for the ROM or you will more than likely have troubles.
3) Is the wrong boot.img being appplied and causing the splash screen issue?
Thanks...
discslinger said:
Update:
I'm still reading, and I just read:
"There are some ROM specific files on the SDcard but a full wipe (all partitions except sdcard) clears them too"
This seems to say it was wrong to 'wipe all partitions except sdcard'. Was this cause of my problem?
Ed
Click to expand...
Click to collapse
do a full wipe from 4ext recovery,reflash cm9 and gapps,
and for splash screen,you are missing kernel as you are S-ON,use hasoon tookit to flash your kernel here
http://forum.xda-developers.com/showthread.php?t=1493905
read above mentioned thread instructions completely...and for your kernel,its in your cm9 zip file named as boot.img,extract it and you will find it...
if i've helped you,don't forget to hit the thanks button
---------- Post added at 09:59 PM ---------- Previous post was at 09:00 PM ----------
discslinger said:
3) Is the wrong boot.img being appplied and causing the splash screen issue?
Thanks...
Click to expand...
Click to collapse
thats what i am talking about.. glad to see a good reader
Read the cm9 thread (just after the last release date). I believe cm9 is messed up. Missing or a bad boot.IMG. there are steps there to fix.
Sent from my HTC_Amaze_4G using xda app-developers app
Thanks guys!
Fixed.:good: