Related
So i'm going to consolidate and give everyone a brief recap on how I fixed my phone since it required the use of SEVERAL posts. I figured someone will eventually get caught in the same situation I was.
This is by no means the best way, or the correct way to fix any phone, do this at your own pace and liability. I am, and no one mentioned in this thread is liable for your phone.
Please excuse any of my grammar mistakes, this is spewing out as I type.
History: Stock DI01 update w/ JT's Voodoo .2 OC Kernel.
Flashed JT's Super Clean ROM V.4 & Remix Incognito Theme.
** Market would no longer work. I had this issue before updating to the 2.2 market after the DI01 update, so I uninstalled and worked again, however, that option wasn't available with the ROM Flash.
I couldn't find a single fix that would work to get the market to work, even ADB pushing older market apk's to the system wouldn't fix it. I decided to do a flash of JT's Super Clean ROM V.2, that didn't fix the issue either.
**I was clearing data and wiping dalvik after each flash**
With nothing seeming to work, I decided to try Deodexe's Zinc ROM, and this is where **** hit the fan. After doing this, I sent my phone into FC boot loop hell. I was getting the process.acore FC everytime I pressed a key. I rebooted back into Clockwork, tried to recover from an old ROM I had backed up the previous day, notta. Damage was done. I was getting FC bootloop hell with a very crappy performance.
I decided it was time to Odin restore and start over. These aren't the exact steps I took, but if I had to do it over again, this is how I would do it. If at any point you're getting a process.media FC, remove your SD Card, and leave it out until you need it for CWM.
STEP ONE:
If you installed Voodoo (at any point, removed or not, do this step)
Thanks to adrynalyne
http://forum.xda-developers.com/showthread.php?t=804784
This was the main culprit behind my phone not working correctly after a complete restore. I moved this to the top of the list, because after that, it's downhill.
STEP TWO:
Completely Restore with Odin Restore Files
Thanks to fallingup
http://forum.xda-developers.com/showthread.php?t=782204
The instructions are a little un-clear, but do this. First, Only use the PDA option, and flash each backup one at a time along with the PIT file. You're not out of the clear yet. Read on.
STEP THREE:
Flash CWM Recovery (read my notes below)
Thanks to fallingup
http://forum.xda-developers.com/showthread.php?t=788099
After you've flashed CWM. Boot into CWM Recovery, Boot back in Stock Recovery and wipe data and cache. Boot back to CWM (select sd:update.zip) and do the exact same thing there. Reboot phone.
STEP FOUR:
Do a data factory reset
Even though you have just restored the **** out of your phone, you're still not there. Get through all the account setup fields and go to Settings > Privacy > Factory Data Reset.
After a reboot, you should be on your way to a completely 100% stock fixed phone. At this point, I would suggest making a ROM back up of this point before moving ahead with flashing again.
LAST STEP (for me anyway):
Restore apps via Titanium Backup
This restored most my apps and settings that I had already saved, including LauncherPro and the backups I had for that. If you haven't used Ti, then use whatever app backup app you do have, if you do indeed have one.
I decided to re-flash JT's Super Clean ROM V.4 found here. Thanks to JT
http://forum.xda-developers.com/showthread.php?t=796171
I am also running the Remix Incognito Theme here: Thanks to frostman89
http://forum.xda-developers.com/showthread.php?t=801867
Right now I'm mixed on updating a new Voodoo Kernel, I haven't decided if I want to do that again or wait for something else.
Thanks again for all the DEV support, hopefully someone searching will find this thread useful.
Pretty much my standard routine when trying new kernels.
I have a nandroid with my basic rooted setup (apps and data intact), so this doesn't set me back by a huge amount.
Just a few differences...
I use:
Odin (System, then kernel) (step only needed if things are *really* messed up...won't boot)
Boot into Recovery
flash update.zip to get into CWM
Wipe Data/Cache/Davlik
Reboot into recovery
run jt's voodoo_uninstall (flashes stock.zip and replaces mbr with stock mbr)
reboot into recovery
restore nandroid image.
This has yet to fail me and usually takes under 10 minutes. The nandroid image is key. Most of the time, I can skip the Odin step completely if I am not seeing anything truly, staggeringly horrific going on.
Again, jt's voodoo-uninstall seems to solve a lot more than just voodoo issues. This thing should get it's own topic/forum/entry in ROM Manager/zip code/nobel award...you get the picture.
PhoenixPath said:
Again, jt's voodoo-uninstall seems to solve a lot more than just voodoo issues. This thing should get it's own topic/forum/entry in ROM Manager/zip code/nobel award...you get the picture.
Click to expand...
Click to collapse
+1 I agree
Nice write up! I'm sure this will help many people.
Thanks
This along with several other threads allowed me to recover from my own mental retardation.
Gotta remember to remove voodoo before doing stuff. I should know better.
Thanks again.
This is not working for me. I removed voodoo (using the uninstaller). I then did odin and my phone boots but I cant do anything past the unlock bc of all the fcs I get. I wiped the cache and data. CWM is not working, when I try to do the update.zip I get a "failed to verify whole-file signiture". - I deleted the voodoo folder from the sd-card after uninstalling voodoo, dont know if that contributed to the problem. Any ideas?
Ke1evraTi said:
This is not working for me. I removed voodoo (using the uninstaller). I then did odin and my phone boots but I cant do anything past the unlock bc of all the fcs I get. I wiped the cache and data. CWM is not working, when I try to do the update.zip I get a "failed to verify whole-file signiture". - I deleted the voodoo folder from the sd-card after uninstalling voodoo, dont know if that contributed to the problem. Any ideas?
Click to expand...
Click to collapse
Sounds like you need to re-flash ClockworkMod through Odin. I'm guessing it got wiped out when you went back to stock.
Well I was one of the people with issues with that Kernal. I just got back to stock by ODINing to (I think) the samsung JKL/a voodoo kernal. Something like that.
Anyhow. Now I was trying to install the one-click-root, when it informed me I have too little internal space. I can't download form the market either. My phone has NOTHING on it.... help? I seem to remember this being an old problem.
Really, thank you everyone who takes the time to help. I'm super-thankful for the excellent support XDA members offer.
Oxirane said:
Well I was one of the people with issues with that Kernal. I just got back to stock by ODINing to (I think) the samsung JKL/a voodoo kernal. Something like that.
Yea i had the same issue with that Kernel. seems that if you unmount the sd in the settings menu you can install apps again. Whitehawx (i think) suggested it in the vibrant 4g rom thread. so far it works for me.
good luck!
Click to expand...
Click to collapse
dwa_jeff said:
Yea i had the same issue with that Kernel. seems that if you unmount the sd in the settings menu you can install apps again. Whitehawx (i think) suggested it in the vibrant 4g rom thread. so far it works for me.
good luck!
Click to expand...
Click to collapse
No such luck here....
Thinking I may have to mess around a bit more with ODIN tomorrow, bleh.
If anyone knows how to get a recovery mode working, that'd be great too. I just want my apps and custom roms back! D:
i have just recovered from this same problem today
but unfortunately i cannot say exactly what i have done to remedy the issue
but i will try , hopefully someone more knowledgeable can enlighten...
1st i rooted and then flashed bionix v! with the voodoo and it was great
2nd saw kernel with voodoo sound and thought that would be awesome
since i am noob, this went fubar
i think i interrupted the "process", and i certainly didn't disable the lagfix, oh and the kernel was from i9000, idunnoifthatmatters....
at any rate the phone booted but there was 0 space for apps, and the volume buttons were inverted, lol
so i reflashed the original kernel and the buttons were good again but the apps still had no space and 'linda' kept saying, "creating partition, zero space on partition" on boot up and shutdown.
in clockwork recovery mode i learned that it was data drive that would not mount
the error message was cant mount dev/block/mmcblk0p1 (file exists)
using clockwork recovery i tried to format the data 'drive' to no avail
i also turned off all options for voodoo lagfix
then i tried to reflash the boinix-v, that crashed out quick, and at last the phone would not boot!! it really took some effort
finally i tried to flash a non-voodoo rom over all this stuff, which seemed to go through, but i still could not boot the phone, stuck at the vibrant screen.
it is at this time that i finally get the drivers to work and odin registers the device, i downloaded the ADK and i am ready to use some shell commands, so i am going to reboot into download and give ODIN a shot, but my fingers slips and i am in stock recovery mode? i have no idea where clockwork has gone but now
but this is immed executed upon entering stock recovery
-- Movi_check Start..!!
checksum confirmation need_checksum[0]
Not need checksum confirmation
--Movi_check already executed!!...
-- movi_checking done!...
update media, please wait
update media, finished
# MANUAL MODE #
-- Appling Muti-CSC...
Installing Muti-CSC
install default apk-files, please wait
install default apk-files, finished
ASR also has an option to format the internal sd, and to delete cache, i did all of that!
and attempted to reboot the system, and to my surprise the **** did!
It booted to that last no voodoo rom that i flashed and the application partition is functioning!?!
i lost all data that was on the internal sd however, but i am back up and running, although i am not sure why
Thanks gqs, I'll try that later....
Thing is, my clockwork disappeared. :/ Supposing I'll try to odin another rom and see if that works, any roms in particular that may fix this?
Sorry guys, this thread could go on and on for a long time explaining what all has happened so I'll put the current problem here and all the junk that led up to it below in case anyone wants to troubleshoot.
First of all my MOST thanks to Roebeet the best most patient person I have worked with. I wish I could give 1000 thanks at once.
The current problem is that I am stuck in a bootloop that not even nvflash will recover. No matter what I do even Vol+/Pwr just leads to big triangle exclamation. Because I nvflashed it back to stock and tried to (stock security wipe/factory). Viewsonic/Gtablet boot loop over and over. Vol-/Pwr allows access to APX mode works, but flashing nvflash, result bootloop.
How did I get here?
- March 10th z4root, vegan 5.1, perfect. No issues, great!
- March 15th got a bright idea to run ubuntu on it. Followed steps perfectly, no go.
Magic Value Mismatch. Panic (flashed with nv flash, got tnt 5.00)
- March 16th Worked great but wouldn't copy any apps to sd. Got titanium backup to
move user apps to sd. Titanium crashed and I lost all my user apps. Frustrated so
decided to flash nv again and go back to Vegan. No go.
- Tried several different ways to run nv, update to 3885, z4root, cw.08 no go
- Tried nv, stock, wipe, cw.08 no go
- Tried nv, 3885, no cw, pwr/vol+, bootloop permanent.
- Apx linux install successful, bootloop permanent
i'm stuck in bootloop too.
I'm no expert, but just out of curiosity, have you tried to get back into CW and format your SD to 2048/256? Maybe the partition is hosed?
1st, try to FORMAT with this tools: http://forum.xda-developers.com/showthread.php?t=974422
you can change the image #9 with CW, once format done, when it reboot, you will have a message error in RED just power it off and on again, you will be in recovery mode, now follow the NVFLASH here:
http://forum.xda-developers.com/showthread.php?t=861950
also you can change image#9 to CW this will get you back to the base of stock VS rom
good luck
Wysdym said:
Sorry guys, this thread could go on and on for a long time explaining what all has happened so I'll put the current problem here and all the junk that led up to it below in case anyone wants to troubleshoot.
First of all my MOST thanks to Roebeet the best most patient person I have worked with. I wish I could give 1000 thanks at once.
The current problem is that I am stuck in a bootloop that not even nvflash will recover. No matter what I do even Vol+/Pwr just leads to big triangle exclamation. Because I nvflashed it back to stock and tried to (stock security wipe/factory). Viewsonic/Gtablet boot loop over and over. Vol-/Pwr allows access to APX mode works, but flashing nvflash, result bootloop.
How did I get here?
- March 10th z4root, vegan 5.1, perfect. No issues, great!
- March 15th got a bright idea to run ubuntu on it. Followed steps perfectly, no go.
Magic Value Mismatch. Panic (flashed with nv flash, got tnt 5.00)
- March 16th Worked great but wouldn't copy any apps to sd. Got titanium backup to
move user apps to sd. Titanium crashed and I lost all my user apps. Frustrated so
decided to flash nv again and go back to Vegan. No go.
- Tried several different ways to run nv, update to 3885, z4root, cw.08 no go
- Tried nv, stock, wipe, cw.08 no go
- Tried nv, 3885, no cw, pwr/vol+, bootloop permanent.
- Apx linux install successful, bootloop permanent
Click to expand...
Click to collapse
Can you get back to a state where you can at least get into CWM, even if it is still bootlooping? If so, go into the advanced settings and perform a fix partition (use the settings 2048 / 0). Please note, this will wipe any data you have on your /SDCARD folder (which is the flash card disk installed on your gtab, not the microSD card you may be using)
I agree with butch1326.
You can't move on to other roms until you know the G-Tablet is working right.
I would try to either nvflash or load the regular way CWM and just get CWM working right.
If CWM seems to be working right, then I would re-partition -- but to 2048 and 0 (not what was given above). Then I would do a factory data wipe.
Once that is done, then I would nvflash the bekit image as is described in a bunch of threads. That will get you all the way back to one of the old, stock setups.
If you get that far successfully, the get on wifi and the OTA should update you to
3588.
Once there, you can take a deep breath, do a bunch of studying on what has been working and what has not, and then move ahead.
Rev
P. S. --- Changing too much too fast is poison in the IT world.
butchconner said:
I agree with butch1326.
If CWM seems to be working right, then I would re-partition -- but to 2048 and 0 (not what was given above). Then I would do a factory data wipe.
QUOTE]
I was under the impression that 2048/256 was the default for the Gtab and that 2048/0 was used primarily for TnT Lite builds. Was I mistaken on this? I'd hate to be giving out the wrong suggestions.
Click to expand...
Click to collapse
From what I gather android in general is 2048 0. I believe stock gtab may have come with something else but never saw a reason why.
I'm pretty sure what jasco13 said is right.
I think way back last year when we started it may have been the other -- but ever since I can remember, the standard advice has been 2048 and 0.
Rev
butchconner said:
I'm pretty sure what jasco13 said is right.
I think way back last year when we started it may have been the other -- but ever since I can remember, the standard advice has been 2048 and 0.
Rev
Click to expand...
Click to collapse
Damn....I must be getting old. 2048/0 it is. My apologies.
Ronin916,
No need for an apology. It was what it was and someone improved it and it is what it is.
Enjoy.
Rev
SOLVED
For the replies and more, No.. cwm was wiped out and did not exist any longer so that was not an option.
This took a LOT of doing. I'm talking about over 4 hours of nvflash, replacing parts of nvflash with other parts of cwm .8 and more. I was walked step by step through by a few devs. Because they tell me that mine had "other" issues, it would be specific to my machine alone and probably not help anyone else to post all of it. (However, I did find an IRC for the dev chat and that made all of the difference) Thank you to all of you Roebeet, EJ, Bad, and all the rest!
I was told that you haven't bricked it until you pitch it in the water, so keep your heads up.
Thank you to EVERYONE who replied to me.
You are a great community of helpful gents.
i have the same problem as you! I need help=(
Come on man you gotta close a thread like this out! It leaves everyone else stranded by not doing so. Glad you got this fixed though.
I'm STUCK in the same spot.. are you ablet to post your fix? PLLLLEEEAAASEEE
HELP!! HELP!! Stuck in bootloop for days!!
Hello all,
I have been stuck in boot loop for two days now!! I have nvflashed about 50 times (even used the format utility too in the mix) no luck!! I want to flash back to stock, then update to 3588 and use either Illuminate or Roebeets Honeycomb rom.
If some one has had this problem, can you help with some steps to fix??
Please please help!! I am ready to throw the G-tab out the window!!
THANKS!!
Anthony
Have you tried repartitioning?
Try installing clockworkmod and fixing permissions?
Sent from my Droid using XDA Premium App
I would love to be able to re-partition or install CWM, but I can't get by the boot screen.
Is there another method other than NVflash??
Thanks for responding!!
You need to nvflash...
1) Use bekit's 1105 nvflash image
2) replace part9.img with the recovery.img from clockworkmod install zip
3) type in the command to nvflash but hold down the volume up key on the tablet while you press the return key to start it. Continue holding the volume up while the nvflash starts.
4) When the flash ends you should enter CWM recovery mode. Repartition and wipe everything
5) swap part9.img back into the nvflash image and nvflash one more time.
If you are still looping after that you'll need to force the tablet to load a stock update. It will require a little more tinkering with nvflash. Let me know if you need the additional steps.
Hi, all. Relative noob here. Fascinate, Stock ED04 OTA, Rooted, modified stock kernel to "stick" CWM, Bloat frozen using TB.
I want to take the next step of flashing a ROM, and am doing (I feel) due dilligence by reading everything possible in this forum. However, I think I'm starting to suffer from information overload, and confusion has set in.
I used Odin to flash CWM 3.0.2.8x.ti. Immediately after selecting backup and restore/backup, I get "Error while backing up boot image". I see a few posts with the same statement, but no resolution. Flashed back to CWM 2.5; and backup appears to complete successfully. However, the date of the backup is 2000-01-01; and this is consistent on repeated attempts. The time and date on my phone (when booted) is correct.
Am I missing something? Any help would be greatly appreciated.
dhartman977 said:
Hi, all. Relative noob here. Fascinate, Stock ED04 OTA, Rooted, modified stock kernel to "stick" CWM, Bloat frozen using TB.
I want to take the next step of flashing a ROM, and am doing (I feel) due dilligence by reading everything possible in this forum. However, I think I'm starting to suffer from information overload, and confusion has set in.
I used Odin to flash CWM 3.0.2.8x.ti. Immediately after selecting backup and restore/backup, I get "Error while backing up boot image". I see a few posts with the same statement, but no resolution. Flashed back to CWM 2.5; and backup appears to complete successfully. However, the date of the backup is 2000-01-01; and this is consistent on repeated attempts. The time and date on my phone (when booted) is correct.
Am I missing something? Any help would be greatly appreciated.
Click to expand...
Click to collapse
i have had the same thing happen every time i try and backup. I'm wondering if it has anything to do with the newer recovery b.c when i had 2.5 i had no issues with it. Anybody have an answer for this?
I was in the same boat as you: rooted and bloat frozen via TB since the first week, and just added the modified kernel with CWM 3 earlier this past week. Haven't had any problems with it. I used Heimdall to flash CWM and the kernel. Now I'm running Evil Fascination with the LG Alternate Launcher. Tried ComRom but didn't care for it, though the default wallpaper was very pretty.
Back to the point, after I flashed the kernel and CWM I restarted the phone, let it boot, then rebooted into recovery to backup, instead of unplugging it and immediately booting Recovery.
Honestly, you've made it this far, you want to get a new ROM, I say download one and follow the directions (read them three times top-to-bottom) before flashing, and you should be good.
Yeah - I think Evil is where I want to end up until CM7 is fully functional (just spent all morning reading the CM7 waiting room thread).
Unfortunately, I'm apprehensive about flashing a new ROM until I can get a good backup image. I'm not sure why I'm getting the erroneous date on the backups. I could certainly be doing something wrong; just not sure what (if anything).
Maybe I need to use a different CWM? 2.5.1 and 3.0.2.8. don't seem to have worked for me. Also, If I understand what eulipion2 said, I have already fully booted, then powered down and rebooted into CWM to do a backup. 3.0.2.8 fails and 2.5.1 gives be incorrect dates.
Going to do a few hours of reading on CWM, I guess!
I'm using the first kernel listed in this thread from times_infinity. I initially flashed ComRom, didn't like it, kept this recovery, and flashed EF. Works great so far.
Give the Nandroid a go with this Recovery and see if it works for you.
hey i figured out how to get the back up to work. you have to enable voodoo and then it will work
Hey guys. Thanks for the suggestions. Tried the CWM 3 link from above, still no dice. I suspect I may need to have a voodoo kernel installed to actually enable the voodoo and try the backup again. Makes sense I guess.
Getting frustrated.
Success! Flashed a voodoo kernel, and was able to get (what appears to be) a successful nandroid backup with 3.0.2.8 (red). Never did get 2.5.1 (yellow) working. Strange, but irrelevant. CM7 build 7 is looking like it's ready for a test drive.
removed for lack of interest in subject matter
also found result of similar work; removed overlap
found flashable zip using different technique to cause full restore but it didn't flash stock recovery; unable to find creator of zip but felt it was not in any ones best interest to leave my files and info posted and may offend the creator of the zip even though my technique is completely my own work!
good luck
OK, I've missed some part of this. I used the 1.1 file on an SD card and I'm guessing without some sort of image for factory software it's not going to work. I get a menu to completely reformat and restore to factory or skip the steps. I choose to restore, it went through some operations, then booted up through Cyanoboot and into my CM7 rom.
From what I have seen it looks like the problem is that I don't have a stock recovery on the device, so it's probably just re-writing the CWM or Cyanoboot.
Any ideas?
zeropants said:
OK, I've missed some part of this. I used the 1.1 file on an SD card and I'm guessing without some sort of image for factory software it's not going to work. I get a menu to completely reformat and restore to factory or skip the steps. I choose to restore, it went through some operations, then booted up through Cyanoboot and into my CM7 rom.
From what I have seen it looks like the problem is that I don't have a stock recovery on the device, so it's probably just re-writing the CWM or Cyanoboot.
Any ideas?
Click to expand...
Click to collapse
I am working on a new version that prints errors to the screen. The first thing this does in flash stock recovery to the proper partition, then flashes the described file and unmounts everything. In other words it flashes stock recovery, obviously that failed so it couldn't mount the recovery partition.
I have yet to find a proper method of displaying errors such as this. (sorry I should have said that cwm is flashed to the recovery partition so only stock or cwm can exist in that partition at a time). You may need to look at your partitions for errors.
I'll post a new version as soon as possible. I was working on that problem(error reporting) when I received your reply.
Note: it will not fix partition problems(only what is written to the partitions), only flash stock recovery and use that to rewrite everything from there and your rom. It does not write rom either as that contains your serial number, mac address, etc.
Good Luck!
zeropants said:
OK, I've missed some part of this. I used the 1.1 file on an SD card and I'm guessing without some sort of image for factory software it's not going to work. I get a menu to completely reformat and restore to factory or skip the steps. I choose to restore, it went through some operations, then booted up through Cyanoboot and into my CM7 rom.
From what I have seen it looks like the problem is that I don't have a stock recovery on the device, so it's probably just re-writing the CWM or Cyanoboot.
Any ideas?
Click to expand...
Click to collapse
I was running cm9 with cwm internal. Downloaded file with Nook, reboot recovery, flashed zip, reboot. Full factory restore! Back to B&N video screen and everything clear and clean. I did this after my previous post to ensure everything is ok. In looking I see many posts in the last three or four days about cm7 and partition problems. celticwebsolutions has a thread about it.
Give the link a try! celticwebsolutions is the op for cm7 and seems to be a very nice guy!
http://forum.xda-developers.com/showthread.php?t=1513583
Good Luck!
zeropants said:
OK, I've missed some part of this. I used the 1.1 file on an SD card and I'm guessing without some sort of image for factory software it's not going to work. I get a menu to completely reformat and restore to factory or skip the steps. I choose to restore, it went through some operations, then booted up through Cyanoboot and into my CM7 rom.
From what I have seen it looks like the problem is that I don't have a stock recovery on the device, so it's probably just re-writing the CWM or Cyanoboot.
Any ideas?
Click to expand...
Click to collapse
corrected incorrect link in previous post!