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?
Related
I'm kinda new to all this mod stuff, so before I do anything I wanna be 100% sure of myself.
I originally had ryanza's OCLF on my Vibrant, but when Voodoo came out with all it's praise, I decided to convert. So I undid OCLF and flashed Voodoo. To be honest, I saw no difference between the two lag fixes. OCLF was working fine for me.
But anyways, all was well for a few days before, one day driving to work in the morning, my phone is playing music when suddenly it freezes. Screen won't unlock, nothing lighting up, totally frozen. So I held down the power button for 5 seconds to shut it off and reboot, and it was fine again. At first it was happening intermittently, now it's pretty much every time I listen to anything. I figured it was a result of Voodoo, so I tried disabling it with the 'disable lagfix' folder. Still the same deal. I feel like it's something with the kernel modification causing the issue. Even if it's not Voodoo causing this, me with my OCD would really like to go back to OCLF, which worked fine. I haven't gotten the JI6 OTA yet, so I wanna go back to stock kernel/firmware before the update hits my phone.
My question is, will following this guide get me back to where I want to be?
forum.xda-developers . com/showthread.php?t=734475
Thanks.
coasterman927 said:
I'm kinda new to all this mod stuff, so before I do anything I wanna be 100% sure of myself.
I originally had ryanza's OCLF on my Vibrant, but when Voodoo came out with all it's praise, I decided to convert. So I undid OCLF and flashed Voodoo. To be honest, I saw no difference between the two lag fixes. OCLF was working fine for me.
But anyways, all was well for a few days before, one day driving to work in the morning, my phone is playing music when suddenly it freezes. Screen won't unlock, nothing lighting up, totally frozen. So I held down the power button for 5 seconds to shut it off and reboot, and it was fine again. At first it was happening intermittently, now it's pretty much every time I listen to anything. I figured it was a result of Voodoo, so I tried disabling it with the 'disable lagfix' folder. Still the same deal. I feel like it's something with the kernel modification causing the issue. Even if it's not Voodoo causing this, me with my OCD would really like to go back to OCLF, which worked fine. I haven't gotten the JI6 OTA yet, so I wanna go back to stock kernel/firmware before the update hits my phone.
My question is, will following this guide get me back to where I want to be?
forum.xda-developers . com/showthread.php?t=734475
Thanks.
Click to expand...
Click to collapse
busybox touch /sdcard/Voodoo/disable-lag && reboot
Let it finish, verifiy by:
mount
/data should mount like this if its disabled:
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
If it is on:
/dev/block/mmcblk0p4, it is still enabled. Good luck.
Once you have that lag fix undone, flash any kernel you need again, then reinstall the OCLF.
If you are still on the Stock ROM or a JFD based ROM:
1.) First disable Voodoo it's currently enabled
2.) Go to the Frankin-Twiz thread and download the Stock-Kernel-Vibrant.zip in the Original Post
3.) Copy the file to your internel SD card.
4.) Boot into Clockwork recovery and flash zip from sdcard.
silow said:
If you are still on the Stock ROM or a JFD based ROM:
1.) First disable Voodoo it's currently enabled
2.) Go to the Frankin-Twiz thread and download the Stock-Kernel-Vibrant.zip in the Original Post
3.) Copy the file to your internel SD card.
4.) Boot into Clockwork recovery and flash zip from sdcard.
Click to expand...
Click to collapse
Doesn't installing Clockwork involve flashing a ROM? I wanna go back to 100% stock, like, fresh out of the box. Because I might exchange my device for a replacement soon. I bought it from Costco so it's a 90 day exchange/return policy that renews every time you exchange. Gotta take advantage of that.
That's also the reason I liked OCLF, because I could lagfix/un-lagfix and root/unroot with one button.
dasunsrule32 said:
busybox touch /sdcard/Voodoo/disable-lag && reboot
Let it finish, verifiy by:
mount
/data should mount like this if its disabled:
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
If it is on:
/dev/block/mmcblk0p4, it is still enabled. Good luck.
Once you have that lag fix undone, flash any kernel you need again, then reinstall the OCLF.
Click to expand...
Click to collapse
Yeah, I already have it undone, I just wanna undo the kernel part. Thanks though!
coasterman927 said:
Doesn't installing Clockwork involve flashing a ROM? I wanna go back to 100% stock, like, fresh out of the box. Because I might exchange my device for a replacement soon. I bought it from Costco so it's a 90 day exchange/return policy that renews every time you exchange. Gotta take advantage of that.
That's also the reason I liked OCLF, because I could lagfix/un-lagfix and root/unroot with one button.
Yeah, I already have it undone, I just wanna undo the kernel part. Thanks though!
Click to expand...
Click to collapse
Then odin flash this kernel:
http://forum.xda-developers.com/showthread.php?t=733792
If you are wanting a full-on restore to stock, then odin:
http://forum.xda-developers.com/showthread.php?t=734475
Good luck.
Moved to Q&A
coasterman927 said:
Doesn't installing Clockwork involve flashing a ROM? I wanna go back to 100% stock, like, fresh out of the box. Because I might exchange my device for a replacement soon. I bought it from Costco so it's a 90 day exchange/return policy that renews every time you exchange. Gotta take advantage of that.
That's also the reason I liked OCLF, because I could lagfix/un-lagfix and root/unroot with one button.
Yeah, I already have it undone, I just wanna undo the kernel part. Thanks though!
Click to expand...
Click to collapse
The lastest release of Clockwork recovery is not a permanent flash. It is kept in an update.zip file on your internal sdcard which can be easily removed.
You can always follow the ODIN steps in the original link you posted. This will return the phone back to the way it was shipped. Note that it doesn't however wipe your internal sdcard.
If you want to keep your data intact flash only the kernel. Using the ODIN method will wipe your data (factory reset, however not your internal sdcard unless you check the repartition option).
If you are a One-Click root/lagfix type of person I wouldn't recommend using ODIN unless you had to resort to it.
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.
FLASHABLE ZIP, (1)RESTORING NC TO STOCK/FACTORY OR (2)CWR REMOVAL ONLY
What you will find here: files to restore to stock (v. 1.0.0 or 1.0.1) and files to remove CWR and thus restore stock recovery (8 failed boots and factory reset [power+n]).
______________CAVEAT________________
Keep in mind that the Nook is really hard to brick. By that, I mean almost impossible. The reason is simple: it has a boot priority on uSD, which means you can always boot your NC from the uSD with, for example, Nookie Froyo (see thread in Dev section). From there you can install Clockwork recovery and other applications (ibid) and repair almost anything. So please, don't panic.
If you ask for help, explain yourself exhaustively on what you have done to require attention. Thank you.
All the usual warnings apply. I cannot guarantee that the following won't have side effects, although I'm pretty sure it won't. Please read complete thread before attempting anything.
Do not attempt flashing files unless you really need to or absolutely know what you are doing.
____________________________
______________UPDATE-01/23/2011_______________
There is another method to restore to stock. If you know your way around ADB, please read this thread: click here, as it will guarantee a clean restoring of your partition. The below files only copy files, but cannot "recreate" your partitions. Both methods can work, but the one linked above (shad0wf0x's thread) will work without exception. Only requirement is that you can use ADB. Thank you.
_______________________________________________
I know a few people out there are struggling after having messed up their Nook's partitions (boot, system, etc.). Hope this will help.
Requirements:
- Rom manager / Clockwork Recovery. This can be easily installed through Nookie Froyo booted from uSD, or through rooted NC. See Clockwork Recovery thread for more information.- A uSD with enough free space (at least 175 MB). Make sure uSD is mounted (see mounts option in Clockwork Recovery). If it doesn't read your uSD, format from an Android device (Memory settings, unmount-> format).
Files to restore NC to stock (1):
If AND ONLY if you choose to restore completely your NC, /data and /system partitions must be formatted before flashing. See mounts and storage option in CWR.
LINKS ARE DOWN: please refer to the following post: http://forum.xda-developers.com/showpost.php?p=22809801&postcount=148
BEWARE: These files will reset you Nook Color to stock and remove Clockwork Recovery, by replacing /boot, /system, and /media with stock
If you choose to flash one of the two files above, formating /data and /system is required BEFORE flashing the file (see mounts and storage in CWR) ! After flashing, resets (8 failed and power+n) shouldn't be necessary, everything should work straight "out of the box" after flashing the file.
Or,
File to remove CWR and restore stock recovery (2):
If you simply wish to remove CW Recovery, use this file, which restores /boot only:
EDIT: files are not available anymore. Sorry for the inconvenience.
Size: 6.1MB, md5sum: 6d00a461a221e69195440355f6706104
Note that this last file will affect your rooting of the NC.
If you should choose to keep your NC rooted, try this:
EDIT: files are not available anymore. Sorry for the inconvenience.
Keep in mind this last file has not been tested on my NC. It's necessarily less dangerous than the other files (which already aren't very dangerous). But still, please give me some feedback on whether it works or not. Cheers.
5. As a last attempt to fixing your NC, if your nook never gets passed the "Touch the future screen" or simply doesn't boot, try this file:
EDIT: files are not available anymore. Sorry for the inconvenience.
________________________________
Comments are welcome.
Sam
Very handy - Thanks for your effort
dude this is just what i needed after my little nook color break down. Thanks!!! a ton!!! also its 11:56 eastern and the downloads are available yet...
Jamdat33 said:
dude this is just what i needed after my little nook color break down. Thanks!!! a ton!!! also its 11:56 eastern and the downloads are available yet...
Click to expand...
Click to collapse
File is now available.
quick question, if we removed cwrecovery then will the 8 boot reset work again?
Yes, it will. That's the point.
beautiful! Thats just what i wanted, thanks alot man
Thank you. I was worried that I wouldn't be able to check out the B & N 2.2 update coming out soon. It worked great. After flashing I had to factory reset the data (three finger salute) and everything worked out great. Now I'm in the process of installing the 1.0.1 update and then will probably go back to where I was before (autonooter with clockwork recovery). I have a nandroid backup and titanium backup of everything so won't take long. Thanks again. Great job!
Tried out method 2. Looks like i have a corrupted recovery now It wont go past the "Touch the future of reading" and when i do the 2 button salute it brings me to a screen that says the install failed
EDIT: Nvm. just magically worked again.
Edit 2: I used the 2nd method and it wasn't smooth sailing. I'm gonna relate what happened and what I did so that samuelhaff can help others if they have the same problem:
I originally auto-nookered the device and then installed CWR. I foolishly tried to do the 8 hard resets and was met with the recovery screen. I also foolishly wiped the data and cache hoping that would do the trick and alas it just left me with a "touch the android" homescreen that didn't work.
At this point I used the second method after I tried froyo and when I reset the nook the nook it would get stuck at the the "Touch the future of reading." So to fix it i tried to get into recovery by holding the N button and the power button and it showed me a screen that said the install failed and then the nook started booting normally again. Not smooth sailing but it worked so thanks a lot!
you're awesome. Wish I had this last week. haha
tytdfn said:
Tried out method 2. Looks like i have a corrupted recovery now It wont go past the "Touch the future of reading" and when i do the 2 button salute it brings me to a screen that says the install failed
EDIT: Nvm. just magically worked again.
Edit 2: I used the 2nd method and it wasn't smooth sailing. I'm gonna relate what happened and what I did so that samuelhaff can help others if they have the same problem:
I originally auto-nookered the device and then installed CWR. I foolishly tried to do the 8 hard resets and was met with the recovery screen. I also foolishly wiped the data and cache hoping that would do the trick and alas it just left me with a "touch the android" homescreen that didn't work.
At this point I used the second method after I tried froyo and when I reset the nook the nook it would get stuck at the the "Touch the future of reading." So to fix it i tried to get into recovery by holding the N button and the power button and it showed me a screen that said the install failed and then the nook started booting normally again. Not smooth sailing but it worked so thanks a lot!
Click to expand...
Click to collapse
Thank you for your contribution.
I don't understand why your NC wouldn't boot pass the splash. Will have to see if that happens again.
But on the other hand, I have noticed that the first boot after restoring may show up an "install failed" notice. Which, again I don't understand just yet. But everything should work if you boot a second time.
Anyway, I'll look into it. In the mean time, both files should help quite a few hot-headed nookers, like myself.
If I new you better, I would fall in love with you. Maybe we should take this slowly.
Is it possible to make a 1.0.1 version
This is a huge step forward. Thanks for posting this. It makes experimentation much more possible.
I'm so happy. I think I'm going to be able to stop crying now.
Good job, sir...
If i can stop screwing up all of my technical endevours, i'm going to start trying to make a rom kitchen, now that there is a streamlined way back...
Nevermind, I can't seem to do anything correctly this weekend...
Sent from my LogicPD Zoom2 using XDA App
straby187 said:
Is it possible to make a 1.0.1 version
Click to expand...
Click to collapse
Most certainly.
Sent from my HTC Desire using XDA App
Ok... I have absolutely no clue what happened... All went well... Flash went through without a hickup... Booted up fine... And then... No wi-fi... I absolutely can not enable wifi now...
ourprisonplanet said:
Ok... I have absolutely no clue what happened... All went well... Flash went through without a hickup... Booted up fine... And then... No wi-fi... I absolutely can not enable wifi now...
Click to expand...
Click to collapse
Ok. Which method did you use? (1) or (2)? Before flashing, were you using v. 1.0.0 ou 1.0.1? Try updating to 1.0.1. See if Wifi is working. If not, try method (1) (again?). Do both resets (8 failed and power+n).
samuelhalff said:
Ok. Which method did you use? (1) or (2)? Before flashing, were you using v. 1.0.0 ou 1.0.1? Try updating to 1.0.1.
Try method (1) (again?). Do both resets (8 failed and power+n).
Click to expand...
Click to collapse
OH THANK GOD :-D I did the power+n and it brought it back... Thank you SOOOO much for such a quick response... I have no clue what the heck caused that... that was weird...
I tried to install a custom boot animation and wound up having to use CWM recovery to get out of weird looping behavior. I'm not sure exactly what the restore function wipes (for instance, my Vegan ROM was still installed).
Since that episode I've been seeing more Forced Closures than before. I wonder if I need to repartition again. What values should I see if am or am not partitioned 2048/0 and where would I look for those? Thanks.
Surely someone can tell me what to look for as an indicator.
I promise to stop calling you "Shirley."
Rick,
I don't think it's personal -- there just is not a place you can look and see your
partitioning.
If you were boot looping, used CWM to stop it, repartitioned 2048/0 and are running
smoothly now I wouldn't worry about it.
Rev
EDIT: On further thought, I think if I were having glitches (like the FCs), I would
reflash back to stock, install CWM and clean up and reset as needed, and make
darn sure everything was working and exactly right -- and then go my way from
there. But that's just the way I work.
Thanks, Rev.
Thing is, I did not repartition (or, rather, re-repartition) after recovery. Have I necessarily reverted, due to CWM recovery, to the unreliable stock partition (bearing in mind that the device wasn't totally wiped; the Vegan ROM was still in place)?
EDIT: I understand that reflashing to stock and starting over will address any issue. I'm just trying to learn.
Rick,
If you boot into recovery using power/volume + and you get CWM you are still in
ClockWorkMod and have not reverted to stock recovery.
I understand you are trying to learn. I just don't like "flaky" anything so I "make sure"!
Rev
Hi I'm a new member,
I rooted my fascinate easily enough. Then searching and learning about ROMs and Kernels I decided to do use ODIN CWM Recovery to 'backup' or whatever most forums tell you to before installing a new ROM. Point is my phone is stuck in manual boot mode and I cannot undo it.
I have tried multiple times using ODIN plus the four stock files
Stock-i500-VZW-Kernel.tar.md5
Stock-i500-VZW-pit.pit
Stock-i500-VZW-Recovery.tar.md5
Stock-i500-VZW-System.tar.md5
(I always would try to implement them in order pit/system, pit/kernel, pit/recovery)
Unfortunately after the first one (pit/system) ODIN says the process fails, I go ahead with the other two and they both amount to nothing happening. My phone does not reset or do anything for this matter and I am forced to shut down ODIN and unplug my phone (upon which it dies with no battery).
Then I put back in the battery and Im back to before in manual boot mode with
Reboot system Now
Apply sdcard:update.zip
wipe data/factory rset
wipe cache partition
Btw wiped data and wiped cache and it didn't help me =(.
Please someone help me, I really don't want this new phone to be dead... Thanks in advance
Oh and when I press "apply sdcard:update.zip" I receive
E:Can't mount \dev\block\vold\179:9
(No such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted.
I really don't care at all about keeping the phone rooted or not or whatever. I just want to be able to make calls again!
So it looks like you're stuck in blue recovery ... sounds like something that Odining a stock package should fix.
Here is a nice thread for getting back to stock (it's a sticky in the general section). The packages include system, recovery, kernel, and radio in a single file (I've actually never odin'd four separate files to get back to stock, or even ever flashed a system-only file), though no pit file.
So open up odin with your phone in download mode (with the battery out, otherwise there's a small chance of odin stalling at the end), and use:
- either the DI01 all-in-one, EB01 all-in-one, or this DL09 package in PDA
- the pit file in PIT (the link says DI01/EB01 but it also works with DL09)
- check "re-partition" if it isn't already checked
- run odin and hopefully in five minutes your phone will work again If for some reason it doesn't, that thread has instructions for using heimdall, although I've never had to resort to it.
So try this and see if it works! (For which package to use, I'd suggest trying DL09 first (since you'll need it to get to the official froyo build) and DI01 if that fails. If you're wondering whether DL09+pit actually works, I've used it to get out of a "stuck in blue recovery after odining stuff" situation myself so yes, it works.)
Thank you for the response! It's encouraging to hear any support and I think yours is promising.
So unfortunately I tried D101 and no go. Turns out this was before I realized this was for 2.1 and I'd prefer 2.2 for the upgrades. Although would you suggest 2.1 for the purpose of rooting/ROMing/Kerneling in the future? I ask because I'm slowly gaining confidence that after fixing this I might be willing to try this again...
Odin (1.7 -> I decided at your poster friend's advice to upgrade from 1.3) worked well said 'pass' and everything. Unfortunately when booting my phone it went straight to the boot screen as always.
Meanwhile I'm downloading the EB01 and your suggested DL09 to test those two.
Hopefully one of those will work but if not, I guess I'll try that heimdall technique the poster suggested in the other forum. Hopefully not tho b/c it looks a bit more complicated.
I'll let ya know if one of these others works.
Yes it worked!! Thank you so much! I would buy you a round at the ale house if I could!
After running EB01 it worked (with the pit file going all the way back to factory settings). So I'm not sure what this means - maybe since it was after upgrading to 2.2 that my phone bugged out, it could only be restored to the 2.2 state which is EB01?? Idk, thanks anways.
Oh ya for the future if I try do this again - would you suggest I stay away from ROM Manager for backing up, which I believe is what started this problem in the first place? It seemed like ODIN did a fine job of managing my OS. Any thoughts? Thankss!!
mattjac1 said:
Yes it worked!! Thank you so much! I would buy you a round at the ale house if I could!
After running EB01 it worked (with the pit file going all the way back to factory settings). So I'm not sure what this means - maybe since it was after upgrading to 2.2 that my phone bugged out, it could only be restored to the 2.2 state which is EB01?? Idk, thanks anways.
Oh ya for the future if I try do this again - would you suggest I stay away from ROM Manager for backing up, which I believe is what started this problem in the first place? It seemed like ODIN did a fine job of managing my OS. Any thoughts? Thankss!!
Click to expand...
Click to collapse
Definately stay away from rom manager cwm if you have the voodoo lagfix enabled, but since all the new fascinate roms are edify scripted, flashing through cwm in rom manager would be ok.
Sent from my Froyo'd Evil Fascinate full of PB&J