Long story short (details here: http://forum.xda-developers.com/showthread.php?t=1318263), my phone has been stuck in a perpetual boot cycle, despite all the help others have provided me.
Well, I've gotten to the point where I was able to flash CWM and access it's recovery menu. This is a big victory, as most of the time when I try to access the recovery menu, I get "deleting cryption meta data" and a reboot. I was able to mount the internal SD card (USB storage) to my computer using CWM's menu, and to my dismay, it was completely empty, save for the error log generated by CWM. No boot partition, no anything.
Does anyone have the original contents of the internal SD card dumped (contents as shipped)? Similar to this thread (http://forum.xda-developers.com/showthread.php?t=1060497). I figure anything is worth a shot now. Much appreciated.
This might be something worth trying:
http://galaxys2root.com/att-galaxy-s2/how-to-unroot-att-galaxy-s2-sgh-i777/
Take you phone back to out of box and start over
penguin356
+1
If you can get cwm, you can get download mode. And the url penguin356 posted is the answer.
Sent from my SAMSUNG-SGH-I777 using XDA App
penguin356 said:
This might be something worth trying:
http://galaxys2root.com/att-galaxy-s2/how-to-unroot-att-galaxy-s2-sgh-i777/
Take you phone back to out of box and start over
Click to expand...
Click to collapse
Thanks for responding, but I'm well beyond that point, as noted in the other thread. Among other things, I've already:
Dranakin said:
1. Flash Entropy512's Return/Unbrick to Stock, Kernel + non-rooted system package using Odin3 v1.85,
Tried it with the PDA + modem package at the same time, PDA without modem, and vice versa. No dice.
2. After flashing to stock, I can sometimes do the SGH-I777_ClockworkMod-Recovery_5.0.2.3. From there, I sometimes can access CWM, wich I then proceed to "Wipe Dalvik Cache", "Wipe Cache Partition", and "Wipe Data/Factory Reset". Usually after I reboot after this, I get same boot loop at the logo, but then it says "deleting cryption meta data" when I try to access the recovery menu.
I've tried flashing back to stock and then to CWM, and the only selecting "Wipe Data/Factory Reset" and then rebooting, but that doesn't help either.
3. I've tried: flash PIT (I777UCKH7.pit), PDA (PDA.tar) and PHONE(UCKH7_modem.tar) at the same time, with REPARTITION, AUTO REBOOT, and RESET TIME checked in Odin.
After doing so, this will usually allow me to reach the stock recovery/e3. If I select "Wipe Data/Factory Reset" from there and reboot, I will still be in a boot loop. Then if I try to get back into the recovery menu, I get "deleting cryption meta data".
4. I followed this:
XXKI3
Android 2.3.5
This original (unmodified) Wipe Package with new bootloader has: PDA: XXKI3| Modem/phone: XXKI3| CSC: OXAKI3
Download: http://www.multiupload.com/NJV6PR87Y3
These packages have the new bootloader removed and repacked with the old ones so you can safely reset the binary counter with a Jig.
I still get a boot loop.
5. If I flash the i9100 ROM, I can enter download mode either by holding down + power, or using the jig that started it all. If I then flash Entropy512's Return/Unbrick to Stock, Kernel + non-rooted system package, I still get a bootloop.
6. I did this: I found this 100% stock i9100 rom with all four parts needed for a complete Odin flash.
PIT select u1_02_20110310_emmc_EXT4.pit
PDA select CODE_I9100XXKI3_CL577579_REV02_user_low_ship.tar.m d5
PHONE select MODEM_I9100XXKI3_REV_02_CL1062028.tar.md5
CSC select GT-I9100-CSC-MULTI-OXAKI3.tar.md5
Same boot loop issue.
Click to expand...
Click to collapse
Have you tried getting into download mode after successfully getting into stock 3e recovery(step #3) ?
Just on the off chance getting 3e recovery working might mean more of the framework needed for a successful odin flash is in place. Just a thought.
Sent from my SAMSUNG-SGH-I777 using XDA App
gr8hairy1 said:
Have you tried getting into download mode after successfully getting into stock 3e recovery(step #3) ?
Just on the off chance getting 3e recovery working might mean more of the framework needed for a successful odin flash is in place. Just a thought.
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
As mentioned previously, most of the time, stock recovery is inaccessible. It'll state "deleting cryption meta data" and then reboot into a loop.
---
So, does no one have the contents of their internal SD card from a stock image?
I don't think it's possible to drag and drop android os and it work.
That having been said, I can't imagine the frustration you're going through. I'll do my best to get my contents extracted and posted for you on this thread tmrw.
I'll be busy all morning and afternoon, but I'll do my best.
Hopefully someone will get it to you sooner.
Sent from my SAMSUNG-SGH-I777 using XDA App
gr8hairy1 said:
I don't think it's possible to drag and drop android os and it work.
That having been said, I can't imagine the frustration you're going through. I'll do my best to get my contents extracted and posted for you on this thread tmrw.
I'll be busy all morning and afternoon, but I'll do my best.
Hopefully someone will get it to you sooner.
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Much thanks if you're able to get around to it!
Android commander will be able to pull everything needed. Unfortunately I just realized I would be uploading my personal files. And if this does work, everyone would have access to:
Google account, my programs and login info, pictures...... just not good.
I've been meaning to go back to stock to try a few things out. Looks like I'll be doing it sooner than I thought. Running titanium backup now. Once I get back to bare bone unrooted stock I'll upload that.
Hopefully it'll be done tonight and finish uploading through the night.
Sent from my SAMSUNG-SGH-I777 using XDA App
Sheesh this is taking awhile. While bored out of my mind, and it's 2am, I noticed in the transfer log every once and awhile there are folders that it says can't be created because they don't exist and files that it can't copy because it says permission denied. I also noticed the program can see that my phone is not rooted.
I obviously haven't used this program before. I'll keep the copy of that transfer and will now root the phone using Entropy512's method and see if root will allow the program to transfer everything. It definitely won't get posted tonight as I'm way too tired. Hopefully I will be able to have it all uploaded tmrw. Or at least uploading, first transfer was 1.49gb. It'll take me a bit to get that uploaded.
gr8hairy1 said:
Sheesh this is taking awhile. While bored out of my mind, and it's 2am, I noticed in the transfer log every once and awhile there are folders that it says can't be created because they don't exist and files that it can't copy because it says permission denied. I also noticed the program can see that my phone is not rooted.
I obviously haven't used this program before. I'll keep the copy of that transfer and will now root the phone using Entropy512's method and see if root will allow the program to transfer everything. It definitely won't get posted tonight as I'm way too tired. Hopefully I will be able to have it all uploaded tmrw. Or at least uploading, first transfer was 1.49gb. It'll take me a bit to get that uploaded.
Click to expand...
Click to collapse
Don't want you to stay up late for this! Just do what you can when you can get around to it, I'll keep trying to use ODIN to fix my phone.
No problem. Seems like it's going to be trickier than expected to get everything off the phone. May end up trying root manager. In the meantime here's the files (minus the parts that wouldn't transfer) that I did pull off (stock not rooted). Give you an idea of what it will be while I try getting the rest off.
http://goo.gl/pq9xn
And I have two (hopeful) answers for you!
The first is (what should be) a full pull of the entire phone:
http://goo.gl/VihRa
The second is a nand backup done through CWM:
http://goo.gl/B6vey
Keep in mind with the nand backup I used Entropy512's kernel (DD_11032011) to get CWM. So by going that route it will give you a yellow triangle at boot screen, not sure if you've been trying to avoid that.
And for the record, Wow that took way too long! And caused me to be on unmodified stock and un-signed in to sync with google for over two days so that I could get the info off I needed without inadvertently giving you my account sign in info or apps, pics, etc.
Really hope it helps. I'd do it all over again just for the fun of learning new things, sorry, you're not that special to be reason enough.
Dranakin said:
Long story short (details here: http://forum.xda-developers.com/showthread.php?t=1318263), my phone has been stuck in a perpetual boot cycle, despite all the help others have provided me.
Well, I've gotten to the point where I was able to flash CWM and access it's recovery menu. This is a big victory, as most of the time when I try to access the recovery menu, I get "deleting cryption meta data" and a reboot. I was able to mount the internal SD card (USB storage) to my computer using CWM's menu, and to my dismay, it was completely empty, save for the error log generated by CWM. No boot partition, no anything.
Does anyone have the original contents of the internal SD card dumped (contents as shipped)? Similar to this thread (http://forum.xda-developers.com/showthread.php?t=1060497). I figure anything is worth a shot now. Much appreciated.
Click to expand...
Click to collapse
I've been driving myself crazy. I am in the same boat. No matter what i try I keep going straight into a boot loop.
Did you try the cwm backup? I never did hear from the op if he got his phone fixed. Might want to send him a pm.
Sent from my páhhōniē
gr8hairy1 said:
And I have two (hopeful) answers for you!
The first is (what should be) a full pull of the entire phone:
http://goo.gl/VihRa
The second is a nand backup done through CWM:
http://goo.gl/B6vey
Keep in mind with the nand backup I used Entropy512's kernel (DD_11032011) to get CWM. So by going that route it will give you a yellow triangle at boot screen, not sure if you've been trying to avoid that.
And for the record, Wow that took way too long! And caused me to be on unmodified stock and un-signed in to sync with google for over two days so that I could get the info off I needed without inadvertently giving you my account sign in info or apps, pics, etc.
Really hope it helps. I'd do it all over again just for the fun of learning new things, sorry, you're not that special to be reason enough.
Click to expand...
Click to collapse
I HAD nand backups. Tried one but it still kept looping. Then without realizing i erased the internal SD so I lost them.
Not sure why but i'm receiving the following errors on the nand backup
! D:\Downloads\clockworkmod.rar: CRC failed in clockworkmod\backup\2011-11-07.06.29.39\boot.img. The file is corrupt
! D:\Downloads\clockworkmod.rar: CRC failed in clockworkmod\backup\2011-11-07.06.29.39\data.ext4.tar. The file is corrupt
! D:\Downloads\clockworkmod.rar: CRC failed in clockworkmod\backup\2011-11-07.06.29.39\system.ext4.tar. The file is corrupt
That file is just a clockworkmod backup folder with the nand in it. Extract that folder and copy it to the backup folder on your phone.
With cwm you'll have adb access. Might want to look up what things you can do with adb.
Wish I could be of more help. Pretty much everything I can think of is included in this thread.
I guess let it be overnight without a battery and see what it does in the morning.
Sent from my páhhōniē
hmm well that's quite the predicament you've got yourself into... Odin I'd usually last resort. Having said that I've khyber had any problems studying my phone with it. Id first make sure that the recovery your using I'd for your phone, it may seem silly but you will find that hours if redoing something well not work because of the smallest things. In cwm you're going to want to error your cache, at least but since you're having so many problems, try reformatting everything, and i mean really reformatting (did an install of a2sd go wrong) to get your positions right (although Odin should do this. Make sure Odin is actually doing things). And i would regain from randomly flashing things. If you flashed an i9000 ROM then use that tread but that is the only time you should use it.
Sent from my SGH-I777 using XDA App
gr8hairy1 said:
That file is just a clockworkmod backup folder with the nand in it. Extract that folder and copy it to the backup folder on your phone.
With cwm you'll have adb access. Might want to look up what things you can do with adb.
Wish I could be of more help. Pretty much everything I can think of is included in this thread.
I guess let it be overnight without a battery and see what it does in the morning.
Sent from my páhhōniē
Click to expand...
Click to collapse
The problem for me is that i'm getting those errors when i try to unzip clockwordmod.rar. I am using Winrar.
I'm trying to do every suggestion I can see. I do have a question though, just so I definitely understand, when using the 1-click or the return back to stock files, they should put EVERYTHING back to stock right? I'm talking about all mounts, bootloaders, kernel, and every single file that android uses correct?
---------- Post added at 10:39 AM ---------- Previous post was at 10:23 AM ----------
I just reread the OP original post and noticed that there's a slight difference between our issues. They originally stated that they could get into their lock screen for a few seconds. I cannot. I get the Samsung Galaxy SII boot screen for about 6 seconds and then it goes off then back to the GSII boot screen. And that's the loop it stays in.
Weird. I'll try reuploading it. Maybe by the end of the day or tmrw before I can. Dr's appointment and windows decided to quit booting for me. Running out of hard drives here, so frustrating. Should've hit up some black Friday deals.
Sent from my páhhōniē
Related
****THIS POST IS NOT FOR BEGINNERS*****READ COMPLETELY BEFORE PROCEEDING*********************************************************************
I had to do this because I had flashed wrong thing in ODIN, and I had NO other choice....I did not do this by choice but this REALLY WORKS and I THINK ITS GREAT I was taking a RISK and I understood the consequences....I Could have ended up with a BRICKED PHONE, but that was not to be. I am VERY VERY happy with the results.
I WANT TO SAY THAT ALOT OF THE MATERIAL IN THIS POST WAS USED FROM LINKS AND POSTS FROM XDA WEBSITE THEY ARE A GREAT FORUM AND ANYONE DOING THIS SHOULD BECOME A MEMBER OF "XDA" AND "MOD A DROID"....THANK YOU XDA AND ALL THE DEV'S FOR ALL YOUR WORK ALL THE MATERIAL IN THIS POST I WILL PUT LINKS TO PAGES AT THE BOTTOM FROM PAGES USED "BUT I HAVE CHANGED SOME OF THE STEPS SO FOLLOW THIS POSTS INSTRUCTIONS ON HOW TO DO THIS PROCEDURE"....TO FASCINATE YOUR MESMERIZE.
******************************READ ENTIRE POST BEFORE YOU DO ANYTHING TO YOUR PHONE********************************************************
******************************READ ENTIRE POST BEFORE YOU DO ANYTHING TO YOUR PHONE********************************************************
******************************READ ENTIRE POST BEFORE YOU DO ANYTHING TO YOUR PHONE********************************************************
First -You NEED to download everything and have it on your PC ready to use !!! DO NOT START WITHOUT DOING THIS.
Second -You NEED to backup your contacts. DO NOT USE MY CONTACTS BACKUP !!! You will not have that app yet so there is no way to restore them. I used an app. called LOOKOUT from the market. You have to install on phone and sign-up on LOOKOUTS web sight and make sure you run a backup of contacts, as well you need to move any apps you want to your PC or SD card. I recommend the PC to leave space on SD Card....Have at least 1GB free on card to be plenty safe.
Ok heres the deal this may or may not be something you will want to do to your phone....DO THIS AT YOUR OWN RISK....This is what I did to turn my phone into a Fascinate even though I was a US Cellular Mesmerize. I WARN THIS WORKS BUT THERE ARE PROS AND CONS TO DOING THIS. To date there is NO, I REPEAT NO WAY to date to go back from this procedure to a MESMERIZE. Someone may have a way but I have not seen or found it yet. I do believe it is only a matter of time before the DEV'S come up with a restore and then you could go back to stock. SUMMARY= THERE IS NO WAY TO DATE TO REVERSE THIS PROCEDURE !!! DO AT OWN RISK !!!
First thing you need to do is download ROM MANAGER from the market and put the App on the SD Card for later install. Next Download this file here>>>>
http://dl.dropbox.com/u/458252/Fascinate Files/update.zip ---- to the ROOT of your SD Card it is a file called "UPDATE.ZIP" "DO NOT RENAME" put that on there and do not remove it you need it do a restore to access Clockwork later. This is where you need to have this located on SD. ---- /sdcard/update.zip.
Second you need to download...DI01 update with root and busybox here>>>>http://www.megaupload.com/?d=S7IFCKX0
Important:"DO NOT RENAME" and DO NOT put this on the root of your sdcard as /sdcard/update.zip. That's where clockwork mod lives. PUT IN FOLDER you name what ever on SD Card. You will need to go here later in the post to install this in step#12
/sdcard/"FOLDER YOU NAME"/update.zip.
Next thing you need the samsung drivers for windows for this to work. Those can be found on this thread: http://forum.xda-developers.com/showthread.php?t=779238 [this page has a good write up on how to down load and install.] or direct link BELOW>>>> Thank you DIRRK XDA member.
Download and Install Samsung Drivers to your WINDOWS PC this whole procedure was done on a WINDOWS 7 PC. WARNING: You need different drivers for mac/Linux and I do not know where to get them as I have only a WINDOWS PC.
64bit:
http://www.wikifilez.com/root files/epic4g/usb_drivers_GalaxyS_x64.zip
32bit:
http://www.wikifilez.com/root files/epic4g/SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe
*************************AFTER THIS POINT THERE IS NO WAY TO GO BACK PROCEED WITH CAUTION !!! ************************************************
For this next step THANK YOU FALLINGUP SENIOR MEMBER XDA....I have altered his orig. post to give more detail for people, using ODIN please follow my post to do this !!
****************************FROM HERE ON ONLY FOLLOW INSTRUCTIONS IN THIS POST TO DO THIS***************************************************
****************************FROM HERE ON ONLY FOLLOW INSTRUCTIONS IN THIS POST TO DO THIS***************************************************
****************************FROM HERE ON ONLY FOLLOW INSTRUCTIONS IN THIS POST TO DO THIS***************************************************
**************************GET ODIN AND ALL FILES NEEDED BEFORE PROCEEDING DOWNLOAD TO PC FOR USE*********************************************
LINKS ATTACHED TO FILES BELOW.
Next download ODIN and run. Make sure ODIN sees your phone by putting phone in DOWNLOAD MODE by pulling battery LEAVE OUT. Run ODIN. HOLD VOL DOWN AND PLUG INTO PC with cable that came with phone, a yellow rectangle with id# means ODIN sees it----once this is connected DO NOT UNPLUG UNTIL ODIN IS FINISHED. If you do you will see a PC connected to a phone by a triangle this means you prematurely unplugged and you will need to re-flash whichever step failed to flash. It is only OK to unplug once a step is finished and Odin says reset in blue, but you do not need to you can load the next file and go. But I've got steps below so if you are here you didn't read entire post. CAREFUL Now follow step 4.1
ONLY FLASH ONE OF THESE AT A TIME. START WITH THE /SYSTEM ODIN AND WORK YOUR WAY DOWN THE LIST.---You do not just flash the pit file it is used with the other files like system,kernel,and recovery. ****FILES BELOW STEPS****READ ENTIRE POST BEFORE USING ODIN AND KNOW THE RISKS*************************************
************************ONCE YOU FLASH ANYTHING YOU CAN NOT GO BACK YOU WILL BRICK YOUR PHONE**********************************************
************************ONCE YOU FLASH ANYTHING YOU CAN NOT GO BACK YOU WILL BRICK YOUR PHONE**********************************************
Steps:
1. Pull battery from device
2. Open Odin on desktop
3. Hold volume down button and plug device into computer-This will place the device into download mode
4. Verify device shows up in Odin ---This should be a yellow rectangle with id #----As well the phone will also say download mode with a yellow triangle on it
4.1: Select PIT button
4.2: Select PIT file downloaded from this post and load it into Odin. (I Never loaded the pit file when I did this in Odin and worked fine for me but from what I understand it is good practice to do so to Quote a post ---"You need to load the pit file into Odin---Missing these steps usually results in major FC hell issues." Thanks PHOENIXPATH senior member XDA
4.1: To Flash the "Stock-i500-VZW-System.tar.md5" file you,
5. Click "PDA" button in Odin ---MAKE SURE YOU ONLY USE PDA "DO NOT USE PHONE" YOU HAVE BEEN WARNED!!
6. Select "Stock-i500-VZW-System.tar.md5" from where you downloaded it
7. Click "Start" This will reboot your phone when complete. This flashes both the kernel and the recovery partition to enable you to flash update.zips signed with test keys. ---When done ODIN should say reset leave pit alone and load next file of the three needed to be flashed.(YOU MAY NEED TO UNPLUG and REDO STEPS 1-4 AGAIN)and jump/proceed to step#8 and continue on.
8. Flash "Stock-i500-VZW-Kernel.tar.md5" when done says reset move to next step.
8.1 Flash "Stock-i500-VZW-Recovery.tar.md5" when done says reset move to next step.
9. Flash "CWMrecovery.tar" ----THANK YOU JT1134 Senior member XDA
10. Replace the battery and Boot in to Recovery= HOLD VOL UP + VOL DOWN same time and PRESS POWER, all three need to be pushed to enter recovery.
11. In recovery navigate UP=vol. up/ DOWN=vol. down /ENTER=home key----You need to select "apply sdcard:UPDATE.ZIP" on ROOT of SD Card to enter the next recovery screen.
12.In this recovery "CLOCKWORK RECOVERY" navigation is different UP/DOWN=SAME but ENTER=power key---you need to navigate to the "ADVANCED" and then apply "WIPE DALVIK CACHE" when done select "REBOOT RECOVERY" (brings you to stock recovery) navigate to "WIPE DATA/FACTORY RESET" once done go to "APPLY SDCARD UPDATE.ZIP" then "INSTALL ZIP FROM SD CARD" once there select "CHOOSE ZIP FROM SD CARD" navigate to the folder "YOU GAVE A NAME TO" and inside is the 2nd "UPDATE.ZIP" you put there and select it...wait until it is finnished...once done.."GO BACK"and"GO BACK AGAIN" then select "REBOOT SYSTEM NOW"
13. Enjoy your stock Fascinate phone with DI01 update and root and busybox . You still will have phone call ability but a couple of apps like contacts backup and vcast are "Verizon" and we at US Cellular can not use. But once you install custom ROMS in Rom Manager you will be able to get roms with them removed or get apps to shut down/freeze them and sub. them out.
Alot of the ROMS have apps taken from the MESMERIZE so this is not really an issue at least not to me.
INSTALL ROM MANAGER FROM SD CARD OR LOAD TO PHONE FROM PC AND INSTALL ON PHONE......
NOW GO INTO ROM MANAGER AND "BACKUP CURRENT ROM" so any changes made from here you can get back to this point.....once done you can NOW LOAD CUSTOM ROMS,KERNELS AND ENJOY THE HELL OUT OF YOUR "FASCINATED-MESMERIZE"
Buy the latest PRO version of ROM MANAGER and use to upgrade kernels thru clockwork or load roms in rom manager......
These are the files to put in ODIN PDA Flashing one at a time with the PIT file. ONLY USE PIT AND PDA......You have been warned again. PS-NEVER DUMP IN ODIN,and do not check anything but PDA AND PIT...there are things checked in ODIN when it loads leave them alone.
Download: "To PC for use in ODIN before you begin"
Odin: http://dl.dropbox.com/u/458252/Odin Files/Odin3 v1.3.exe -This is program to use to flash.
Odin Restore file for system: http://dl.dropbox.com/u/458252/Odin Files/Stock-i500-VZW-System.tar.md5 -----THIS IS FIRST.
Odin Restore file for kernel: http://dl.dropbox.com/u/458252/Odin Files/Stock-i500-VZW-Kernel.tar.md5 -----THIS IS SECOND.
Odin Restore file for recovery: http://dl.dropbox.com/u/458252/Odin Files/Stock-i500-VZW-Recovery.tar.md5 ----THIS IS THIRD.---this is just to be safe
Odin Clockwork recovery file: http://dl.dropbox.com/u/458252/CWMrecovery.tar ------THIS IS FOURTH ONE I FLASHED.
PIT file for use in Odin Restores: http://dl.dropbox.com/u/458252/Odin Files/Stock-i500-VZW-pit.pit ----THIS IS PIT TO USE "WITH" ABOVE FILES.
*************************THANK YOU TO XDA WITHOUT YOU THIS WOULD NOT BE POSSIBLE**********************************************************
LINKS REFERENCED FROM XDA's WEBSITE THANK YOU AGAIN XDA MEMBERS !!! YOU GUYS ROCK !!!
http://forum.xda-developers.com/forumdisplay.php?f=721
http://forum.xda-developers.com/showthread.php?t=782204
http://forum.xda-developers.com/showthread.php?t=790004
http://forum.xda-developers.com/showthread.php?t=790085
http://forum.xda-developers.com/showthread.php?t=779238
http://forum.xda-developers.com/showthread.php?t=789868
http://forum.xda-developers.com/showthread.php?t=788099
IF YOU LIKE THIS LEAVE ME SOME FEED BACK PLEASE.....................THANKS AND ENJOY........ANDROIDMAN
EXTRA NOTE: DO NOT TRY THIS WITH ANYTHING OTHER THAN THE SCH I-500 MESMERIZE......AS IT HAS ONLY BEEN DONE ON THAT MODEL..........
FLASHING ANY OTHER GALAXY S VARIANTS ODIN FILES WILL BRICK YOUR PHONE !!!!!!!!!
How odd.
Why would you want to make your phone a fascinate? Most of us went the other way in order to debing.
Sent from my SCH-I500
lowkee said:
How odd.
Why would you want to make your phone a fascinate? Most of us went the other way in order to debing.
Sent from my SCH-I500
Click to expand...
Click to collapse
Because There is no way mainstream to use clockwork or rom manager. Hense you can only root, thats it without this.
lowkee said:
How odd.
Why would you want to make your phone a fascinate? Most of us went the other way in order to debing.
Sent from my SCH-I500
Click to expand...
Click to collapse
My thoughts exactly?! I thought people that had a fascinate were wishing it wasn't so fascinatish?
Whatever floats your boat I guess.
JT
danrosinski said:
Because There is no way mainstream to use clockwork or rom manager. Hense you can only root, thats it without this.
Click to expand...
Click to collapse
Correct, No Way of FLashing ROM MANAGER so you can apply the first update.zip
You Can Flash but when you apply the update to a MESMERIZE you get E:signature verify fail -hence No Clockwork, NO Roms. No Way to Customize
jtsharps said:
My thoughts exactly?! I thought people that had a fascinate were wishing it wasn't so fascinatish?
Whatever floats your boat I guess.
JT
Click to expand...
Click to collapse
When I orig. did this I had No Choice, This is something that I had to do...and Thankfully Worked just thought I would Share because now I can Use CLOCKWORKMOD and ROM MANAGER and customize my phone as if it were a Fasinate.
lowkee said:
How odd.
Why would you want to make your phone a fascinate? Most of us went the other way in order to debing.
Sent from my SCH-I500
Click to expand...
Click to collapse
Did you read the entire post I had NO choice as stated in the beginning....Thank You.
Can't link it now but doesn't Koush have a post on compiling Clockwork for new phones?
Sent from my Voodoo-powered Fascinate with XDA
s44 said:
Can't link it now but doesn't Koush have a post on compiling Clockwork for new phones?
Sent from my Voodoo-powered Fascinate with XDA
Click to expand...
Click to collapse
If he dose I havent seen it can you throw that up for everyone?
androidman78 said:
If he dose I havent seen it can you throw that up for everyone?
Click to expand...
Click to collapse
Now I'm home, so here's the post.
Awesome job. Glad you got it working. Now all we need its a way to reverse these steps so us fascinate users can go to 'stock' mesmerize.
(...or better yet, stock android...)
Sent from my stupidfast blackish hole...
What are the other possible applications for this?
PhoenixPath said:
Awesome job. Glad you got it working. Now all we need its a way to reverse these steps so us fascinate users can go to 'stock' mesmerize.
(...or better yet, stock android...)
Sent from my stupidfast blackish hole...
Click to expand...
Click to collapse
Yea, was worried origionally that I was screwed but its a draw/Im happy its only a matter of time before the Fasinate users will be able to go stock mesmerize because this SHOULD?see no reason why not, go both ways.
I know that Sprint is doing an I-500 can we go there too, at least for apps and features. I wonder? And what about the 4G...USC and VZW are 3G would switching/Moding give any advantages I think NOT but still wonder how much of that speed is controled by phone software. I really think its all the network but not 100% sure.
Post above looks interesting the one for Koush's site am checking it out now....Thanks
Sent from my Stupid Fast Blackhole of a Fasinated-Mesmerize
Just need the odin files for the mesmerize.
Sent from my stupidfast blackish hole...
PhoenixPath said:
Just need the odin files for the mesmerize.
Sent from my stupidfast blackish hole...
Click to expand...
Click to collapse
Got any open space to host?
It's called dropbox.
PhoenixPath said:
It's called dropbox.
Click to expand...
Click to collapse
3 hours to upload that small of a file... Dropbox blows for something like that. We'll see.
So i have clockwork working on my mesmerize and running jts super clean but does this allow you to use all facinate roms and kernels on the mesmerize? if so i wanna try this
so if i did this and i used clockwork to perform a backup before i did this could i possibly just restore that backup and have it be a mesmerize again?
and it was said there are pros and cons of doing this? the pros are great but what are the cons besides not being able to go back to stock mesmerize????
tweakymattman said:
and it was said there are pros and cons of doing this? the pros are great but what are the cons besides not being able to go back to stock mesmerize????
Click to expand...
Click to collapse
I can't get mms working....
Sent from my SCH-I500 using Tapatalk
This makes about 100 times more sense.
http://androidforums.com/behold-2-all-things-root/54424-creating-custom-roms-backups-odin.html
I'm an admitted noob, but my hope is that somebody here will take pity and be able to shed some light on what I've done and how to fix it.
Here is a general high-level list of what I've done:
1. I attempted to root my phone with SuperOneClick (I think 2.3.3)
2. It hung one Step #7 (as I recall) for about 10 minutes.
3. I disconnected USB cable and reset the phone - it wouldn't boot
4. Started researching, discovered Recovery Mode, selected reset to factory.
5. Reset appeared successful, but then phone went into reboot loop.
6. Tried to access Recovery Mode again, but this time it came to different screen, saying "Deleting cryption meta data".
7. Tried flashing several times with odin and stock PDA's suggested in this forum.
8. Same behavior, so flashed CWM 4.0.0.2 (unfortunately it was for I9100)
9. Flashed new CWM 5.0.2.3
10. When I enter Recovery mode now and I select the wipe data/factory reset option, it just goes to a hat icon with a circular arrow and stays there.
Like I said, I'm new here and have already given up hope on recovering any useful data on my phone. I just want to get it working again so I don't have to buy a new one.
Thanks in advance!
In you item #10, that's a common mistake. The 5.0.2.3 version does not use the power button to select. Use the home softkey to select and the back softkey to go back.
Try to wipe data/factory reset again from this version of CWM Recovery, and then try flashing the one-click downloader return to stock in the "Return to the store or for warranty replacement" thread stickied in general.
Post your results back here and I'll try to keep an eye out to help, but I won't be on the computer every minute.
creepyncrawly said:
In you item #10, that's a common mistake. The 5.0.2.3 version does not use the power button to select. Use the home softkey to select and the back softkey to go back.
Click to expand...
Click to collapse
This guy is right. The power button is the menu/logo button in that version. The newer version changes that mapping though.
You'll likely need to flash the return to stock image. One of them is already prerooted, too!
Sent from my SAMSUNG-SGH-I777 using xda premium
creepyncrawly said:
In you item #10, that's a common mistake. The 5.0.2.3 version does not use the power button to select. Use the home softkey to select and the back softkey to go back.
Try to wipe data/factory reset again from this version of CWM Recovery, and then try flashing the one-click downloader return to stock in the "Return to the store or for warranty replacement" thread stickied in general.
Post your results back here and I'll try to keep an eye out to help, but I won't be on the computer every minute.
Click to expand...
Click to collapse
Thanks so much for your quick reply and help. I followed the instructions you outlined and all went as outlined. Upon final reboot I'm back at Stage 6 in my original post. The original Samsung logo is back (which is a relief), but so is the incessant rebooting and upon trying to enter Recover Mode, I get the Deleting cryption meta data message and then more reboot loop.
Looking forward to your next suggestion(s) and a little sleep.
Oh, by the way, the wipe data/factory reset within CWM appeared to run properly but made no apparent change.
digitalsdc said:
Thanks so much for your quick reply and help. I followed the instructions you outlined and all went as outlined. Upon final reboot I'm back at Stage 6 in my original post. The original Samsung logo is back (which is a relief), but so is the incessant rebooting and upon trying to enter Recover Mode, I get the Deleting cryption meta data message and then more reboot loop.
Looking forward to your next suggestion(s) and a little sleep.
Oh, by the way, the wipe data/factory reset within CWM appeared to run properly but made no apparent change.
Click to expand...
Click to collapse
Tried to answer you this morning, but didn't hit the submit button until a few minutes after 8:00. Let me see if I can do it again.
You did a factory reset and then installed the stock firmware. Now try a factory reset again to see if that will clear the bootloop.
If that does not do it, then you may need to replace another part of the system. We need to know exactly what you flashed for the I9100 while you were trying to fix the original problem (point 8 in your list.) So far, you have flashed everything in the stock UCKH7 firmware except the bootloaders and the param.lfs. You may need to flash param.lfs next to see if that will do it. Is there any chance that what you flashed for the I9100 contained bootloaders?
...........
By the way, having Super OneClick hang on step #6 is a known issue, and the solution is posted in the Super OneClick thread OP as well as in the Library sticky thread in the development section of the I777 forum. If you had been better informed, you could have avoided this problem.
creepyncrawly said:
Tried to answer you this morning, but didn't hit the submit button until a few minutes after 8:00. Let me see if I can do it again.
You did a factory reset and then installed the stock firmware. Now try a factory reset again to see if that will clear the bootloop.
If that does not do it, then you may need to replace another part of the system. We need to know exactly what you flashed for the I9100 while you were trying to fix the original problem (point 8 in your list.) So far, you have flashed everything in the stock UCKH7 firmware except the bootloaders and the param.lfs. You may need to flash param.lfs next to see if that will do it. Is there any chance that what you flashed for the I9100 contained bootloaders?
...........
By the way, having Super OneClick hang on step #6 is a known issue, and the solution is posted in the Super OneClick thread OP as well as in the Library sticky thread in the development section of the I777 forum. If you had been better informed, you could have avoided this problem.
Click to expand...
Click to collapse
First, you're a true gentleman (assuming 'creepyncrawly' to be male) for sticking with me on this issue - Thanks!
To address your first point, I could't do a factory reset after this most recent flash because that dialog doesn't exist any longer. All I get is the "Deleting cryption meta data" message when I try to enter recover mode.
As for the I9100 flash, I used CF-Root-SGS2_XW_XEU_KE7-v4.0-CWM4 first which took me to 4.0.0.2 and then realizing what I'd done, flashed with SGH-I777_ClockworkMod-Recovery_5.0.2.3 which took me to 5.0.2.3, though the I9100 logo still showed during boot.
Thanks again for your help. I will "flash at will" whatever you suggest as at least I feel I'm making progress now.
digitalsdc said:
First, you're a true gentleman (assuming 'creepyncrawly' to be male) for sticking with me on this issue - Thanks!
To address your first point, I could't do a factory reset after this most recent flash because that dialog doesn't exist any longer. All I get is the "Deleting cryption meta data" message when I try to enter recover mode.
As for the I9100 flash, I used CF-Root-SGS2_XW_XEU_KE7-v4.0-CWM4 first which took me to 4.0.0.2 and then realizing what I'd done, flashed with SGH-I777_ClockworkMod-Recovery_5.0.2.3 which took me to 5.0.2.3, though the I9100 logo still showed during boot.
Thanks again for your help. I will "flash at will" whatever you suggest as at least I feel I'm making progress now.
Click to expand...
Click to collapse
The CF-Root-SGS2_XW_XEU_KE7-v4.0-CWM4.tar contains only the kernel zImage, so it doesn't flash any of the wrong bootloaders or param.lfs, so no clue there.
However, the message "deleting cryption meta data" seems to be associated with the lfs, so I would suggest that you try flashing just the UCKH7 param.lfs file using Odin3. Go to the Download Repository where you will find the Odin3 flashable tar of the UCKH7 param.lfs.
creepyncrawly said:
The CF-Root-SGS2_XW_XEU_KE7-v4.0-CWM4.tar contains only the kernel zImage, so it doesn't flash any of the wrong bootloaders or param.lfs, so no clue there.
However, the message "deleting cryption meta data" seems to be associated with the lfs, so I would suggest that you try flashing just the UCKH7 param.lfs file using Odin3. Go to the Download Repository where you will find the Odin3 flashable tar of the UCKH7 param.lfs.
Click to expand...
Click to collapse
I successfully flashed the I777 param.lfs from your download repository. Unfortunately, with the same results. I still get the boot loop and when trying to access recover mode I get "Deleting Cryption Meta Data".
Would you suggest I try flashing the secondary boot loader or .pit files?
digitalsdc said:
I successfully flashed the I777 param.lfs from your download repository. Unfortunately, with the same results. I still get the boot loop and when trying to access recover mode I get "Deleting Cryption Meta Data".
Would you suggest I try flashing the secondary boot loader or .pit files?
Click to expand...
Click to collapse
Well, I had a little extra time tonight so I tried a couple more things after my last post. I went back to the Download Repository and got the secondary boot loader (i777 UCKH7 sbl), flashed with that. No change. Then I got the full set of binaries (I777UCKH7-CL503881-Full), flashed that, and still no change. I think I've tried everything except the .pit and that appears the most risky so I'll await further instruction before trying that.
Am I running out of options at this point?
I had a similiar problem with the deleting meta cache data. I couldn't get it back to working order although I didn't flash pit either. Luckily mine was within 30 days so I gave up and returned for a new one.
Hopefully this deleting meta cache thing can be figured out to see what the cause is. Mine happened from a working rom browsing the web, not from flashing. So I believe it was from aftermarket charger creating some hardware problems to my phone, but not sure what it could have messed up.
If ya can't exchange yours, I hope you figure it out.
Sent from my SAMSUNG-SGH-I777 using XDA App
digitalsdc said:
Well, I had a little extra time tonight so I tried a couple more things after my last post. I went back to the Download Repository and got the secondary boot loader (i777 UCKH7 sbl), flashed with that. No change. Then I got the full set of binaries (I777UCKH7-CL503881-Full), flashed that, and still no change. I think I've tried everything except the .pit and that appears the most risky so I'll await further instruction before trying that.
Am I running out of options at this point?
Click to expand...
Click to collapse
I have always understood that if a phone will boot in any way, or show any sign of life, then it can be recovered. Since you can still get into download mode, you should be able to recover your phone. However, since I am not an Android developer, and I don't really understand the low level workings of the phone, I can't offer any more suggestions myself.
You have flashed the complete I777UCKH7 software package including bootloaders and param.lfs, which also rebuilds the csc, so I don't know what is causing the bootloop.
You need to seek the help of someone more experienced. I have two people on xda in mind who specialize in recovering hard bricked phones, and both have a better understanding of the low level workings of the phone.
Adam Outler is a fantastic hardware level developer who published the unbrickable mod for the Galaxy S series of phones, and is currently moving into the Galaxy S II phones. I have heard that he wants an I777 to work on to try to make the unbrickable mod for our phone. He would probably not charge anything since he is using the phone to learn how to do it, but he might keep the phone for a while.
Connexion2005 of Mobile Tech Videos offers hard brick recovery on the Galaxy S and Galaxy S II series of phones. He also has a very good understanding of the low level functions of the phone.
If it was my phone, I would be contacting these two to see if I could get any guidance about how to recover the phone, probably Adam Outler first. I would try to pm them and I would try to get phone numbers and talk with them in person.
You are not hard bricked. And about the pit, that re-partitions the phone. But I don't have enough experience to know if partitioning could cause the problem you are experiencing.
Good luck moving forward.
Any chance flashing a ROM would do the trick...like Unnamed or SHOstock? Just thinking that maybe he's flashed so many things nothing is playing nice anymore. Just a thought, not necessarily a suggestion. ;-)
Also, how long are you letting it sit in boot loop now? It might be taking a while to rebuild everything...?
Sent from my SAMSUNG-SGH-I777 using XDA App
Nerz said:
I had a similiar problem with the deleting meta cache data. I couldn't get it back to working order although I didn't flash pit either. Luckily mine was within 30 days so I gave up and returned for a new one.
Hopefully this deleting meta cache thing can be figured out to see what the cause is. Mine happened from a working rom browsing the web, not from flashing. So I believe it was from aftermarket charger creating some hardware problems to my phone, but not sure what it could have messed up.
If ya can't exchange yours, I hope you figure it out.
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
So, had you rooted and put a custom rom on prior to yours going south, or was it completely stock? What made you think it was related to the aftermarket charger?
Jank4AU said:
Any chance flashing a ROM would do the trick...like Unnamed or SHOstock? Just thinking that maybe he's flashed so many things nothing is playing nice anymore. Just a thought, not necessarily a suggestion. ;-)
Also, how long are you letting it sit in boot loop now? It might be taking a while to rebuild everything...?
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Thanks for your thoughts. I had a similar thought last night and so let it sit through the night rebooting. Sure enough, when I checked it (roughly 8 hours) this morning, it was nice and warm, but still rebooting away.
creepyncrawly said:
I have always understood that if a phone will boot in any way, or show any sign of life, then it can be recovered. Since you can still get into download mode, you should be able to recover your phone. However, since I am not an Android developer, and I don't really understand the low level workings of the phone, I can't offer any more suggestions myself.
You have flashed the complete I777UCKH7 software package including bootloaders and param.lfs, which also rebuilds the csc, so I don't know what is causing the bootloop.
You need to seek the help of someone more experienced. I have two people on xda in mind who specialize in recovering hard bricked phones, and both have a better understanding of the low level workings of the phone.
Adam Outler is a fantastic hardware level developer who published the unbrickable mod for the Galaxy S series of phones, and is currently moving into the Galaxy S II phones. I have heard that he wants an I777 to work on to try to make the unbrickable mod for our phone. He would probably not charge anything since he is using the phone to learn how to do it, but he might keep the phone for a while.
Connexion2005 of Mobile Tech Videos offers hard brick recovery on the Galaxy S and Galaxy S II series of phones. He also has a very good understanding of the low level functions of the phone.
If it was my phone, I would be contacting these two to see if I could get any guidance about how to recover the phone, probably Adam Outler first. I would try to pm them and I would try to get phone numbers and talk with them in person.
You are not hard bricked. And about the pit, that re-partitions the phone. But I don't have enough experience to know if partitioning could cause the problem you are experiencing.
Good luck moving forward.
Click to expand...
Click to collapse
Thanks very much for all your help! I'll try to reach out to these other gentlemen as well.
I've seen other people on these forums with the same problem, but unfortunately, every thread seems to end unresolved. I still hold out hope as I really don't want to eat the cost of the phone and start over.
digitalsdc said:
So, had you rooted and put a custom rom on prior to yours going south, or was it completely stock? What made you think it was related to the aftermarket charger?
Click to expand...
Click to collapse
I figured it was the charger because it was connected when it happened. Was driving home from a Christmas vacation, with maps navigation going, stopped at a rest stop surfing the web. Also on another thread that I read that had a similiar problem, they too thought it was the charger.
And no it was not stock, running unnamed at the time, (though I doubt that is the cause). Like yours I think, I could flash from cwm without success. Wasn't until I flashed stock with stock recovery that I got the deleting meta cache or whatever it is.
Sent from my SAMSUNG-SGH-I777 using XDA App
Any luck so far? I think I'm having the same issues. Although I can flash the stock rom, then a CWM .tar file and get into recovery. But no matter what I do, after boot, the phone starts boot looping.
You can see my thread in the Q&A section.
Shut Guys There is a solution for this !!!! Just make sure you flash back to stock on 2.3.4 (I777UCKH7) and flash the kernel on this post:
http://forum.xda-developers.com/showthread.php?t=1367800
it will take a bit to load but this should do it!!
hardgrid said:
Shut Guys There is a solution for this !!!! Just make sure you flash back to stock on 2.3.4 (I777UCKH7) and flash the kernel on this post:
http://forum.xda-developers.com/showthread.php?t=1367800
it will take a bit to load but this should do it!!
Click to expand...
Click to collapse
THX THX THX THX THX! It worked!
hardgrid said:
Shut Guys There is a solution for this !!!! Just make sure you flash back to stock on 2.3.4 (I777UCKH7) and flash the kernel on this post:
http://forum.xda-developers.com/showthread.php?t=1367800
it will take a bit to load but this should do it!!
Click to expand...
Click to collapse
Hi, did anybody tried this solution??? I'm having the same issue, even tried to contact JTAG unbrick service but these guys told me I'm having a emmc chip failure.
I have tried to read as many posts on this topic as possible, and I haven't found a proper solution. I've found a few threads where the issue was apparently fixed but they never bothered posting how they did it. If there is a thread that addresses and fixes this issue, my apologies and please redirect me.
First off, I've had my phone rooted since February and it has been working fine. I forget exactly what I rooted with but I have the super user app icon. Last week my Fascinate crashed and re-booted into startup wizard, and all my apps were erased, and I kept getting the force close error boxes. I dont know exactly what caused this but think I might have erased super user when I was going through and deleting apps to free up space. When I reboot everything erases and I go into the start up wizard. My internal memory is 0 and I cannot download any apps. I tried to do factory reset but the data could not be wiped. I tried flashing with odin all the possible .tar packages out there and they all get stuck on the movinand.bin file and fails. I've tried flashing in heimdall but couldnt get it to reboot at all. I've booted into cwm, and every time I try to factory reset/wipe data i get the "error mounting data!" message. I know there's definitely a memory problem and a data problem that has been consistent, and everything I've tried can't get around it.
My current temporary fix has been installing the cyanogen mod, which allows me to use the basic phone functions without the force close boxes. I still have the memory issue and cannot receive text messages, and my network settings are deleted when I reboot. Again, I've read quite a bit of threads on this topic and there seems to be a consensus that I might need the original.mbr and stock.zip files, which I tried downloading from that link everyone posts and they dont work. CWM says the .zip file is bad. Also, the link is like 2 years old as well as most of the threads on this topic, and I havent found anything recent. I've also read about using adb shell to address the issue in the HOW TO guide, and it seems i really need those files. Sorry this was long, I just want to make sure I'm not repeating something that has already been addressed and fixed. Please help. Thanks.
JSlice said:
I have tried to read as many posts on this topic as possible, and I haven't found a proper solution. I've found a few threads where the issue was apparently fixed but they never bothered posting how they did it. If there is a thread that addresses and fixes this issue, my apologies and please redirect me.
First off, I've had my phone rooted since February and it has been working fine. I forget exactly what I rooted with but I have the super user app icon. Last week my Fascinate crashed and re-booted into startup wizard, and all my apps were erased, and I kept getting the force close error boxes. I dont know exactly what caused this but think I might have erased super user when I was going through and deleting apps to free up space. When I reboot everything erases and I go into the start up wizard. My internal memory is 0 and I cannot download any apps. I tried to do factory reset but the data could not be wiped. I tried flashing with odin all the possible .tar packages out there and they all get stuck on the movinand.bin file and fails. I've tried flashing in heimdall but couldnt get it to reboot at all. I've booted into cwm, and every time I try to factory reset/wipe data i get the "error mounting data!" message. I know there's definitely a memory problem and a data problem that has been consistent, and everything I've tried can't get around it.
My current temporary fix has been installing the cyanogen mod, which allows me to use the basic phone functions without the force close boxes. I still have the memory issue and cannot receive text messages, and my network settings are deleted when I reboot. Again, I've read quite a bit of threads on this topic and there seems to be a consensus that I might need the original.mbr and stock.zip files, which I tried downloading from that link everyone posts and they dont work. CWM says the .zip file is bad. Also, the link is like 2 years old as well as most of the threads on this topic, and I havent found anything recent. I've also read about using adb shell to address the issue in the HOW TO guide, and it seems i really need those files. Sorry this was long, I just want to make sure I'm not repeating something that has already been addressed and fixed. Please help. Thanks.
Click to expand...
Click to collapse
Is your sdcard broke? Try another if you have...
Use this guide! http://forum.xda-developers.com/showthread.php?p=17050028 you'd want section 2....Use Odin and follow the directions to a tee. You want to restore...so use how to flash eh03
DROID DOES, Apple did...like I forgot when
I don't think my sd card is broken, as I can still save files and music to it. That is how I was able to install cyanogen mod - I did it through clockwork recovery and then install from .zip. Could there still be something wrong with it?
Also, are you absolutely sure I'll be able to flash the eh03 in Odin without it getting stuck on "movinand.bin" ? Every .tar file I've tried so far has had that happen.
JSlice said:
I don't think my sd card is broken, as I can still save files and music to it. That is how I was able to install cyanogen mod - I did it through clockwork recovery and then install from .zip. Could there still be something wrong with it?
Also, are you absolutely sure I'll be able to flash the eh03 in Odin without it getting stuck on "movinand.bin" ? Every .tar file I've tried so far has had that happen.
Click to expand...
Click to collapse
when using Odin, try different USB port, different USB cable, be sure battery is out..
Also, are you using Odin to flash a stock tar? you should be, and if so are you using the v2.2 pit with the repartition box checked?
See also, droidstyles guide in the fascinate general section
Sent from my SCH-I500 using xda premium
neh4pres said:
when using Odin, try different USB port, different USB cable, be sure battery is out..
Also, are you using Odin to flash a stock tar? *you should be, and if so are you using the v2.2 pit with the repartition box checked?*
See also, droidstyles guide in the fascinate general section
Click to expand...
Click to collapse
I've used all my USB ports and 2 different cables, including the one that came with my phone
Here are all the files I've tried:
CI500_VZW_ED05_FROYO_REL.tar
CI500_VZW_EH03_GB_CM.tar
eh03_full_odin.tar
DI01package3.tar
stock_kernel.tar
I'm also using atlas_v2.2.pit
All of the .tar files get stuck at movinand.bin for about half an hour then it fails. I've tried checking and unchecking the re-partition box with the same result.
Pixelation also recommended the droidstyle guide, I was just afraid of running into the same issue with the movinand.bin file. I've found numerous other threads about people having this same problem and never found a clear solution. I think one person was able to get it fixed with help from adrynalyne, but it was through IRC, so it was never posted in the thread. Any other ideas on what I should try?
Cloyne venlyt
Update: Trying Section 2 of droidstyle's guide. Currently stuck at 99% on movinand.bin, trying to flash the PowerWashed 2.3.4 eh09 rom
ahhhhh!!!! Why, God?
I really don't know. Besides glitched usb drivers on the computer.. Did you try setting up drivers for the fascinate on another pc yet? There is always unbrickable mod if no other fix works
Sent from my SCH-I500 using xda premium
I've tried it on another computer and it still hangs on movinand.bin. It's definitely not a computer issue, since I rooted the phone in February just fine. I think something must have happened when I accidentally deleted the superuser app last week. The only files that I've been able to flash successfully are atlas_v2.2, cwm4-bml-i500, and cwm3_voodoo.tar. Then from clockwork I can install cyanogen from the sd card so I sort of have a working phone. What's the unbrickable mod?
JSlice said:
I've tried it on another computer and it still hangs on movinand.bin. It's definitely not a computer issue, since I rooted the phone in February just fine. I think something must have happened when I accidentally deleted the superuser app last week. The only files that I've been able to flash successfully are atlas_v2.2, cwm4-bml-i500, and cwm3_voodoo.tar. Then from clockwork I can install cyanogen from the sd card so I sort of have a working phone. What's the unbrickable mod?
Click to expand...
Click to collapse
Well, first you don't flash the atlasv2.2pit. that file is a partition map. It repartitions the phone when combined with a factory image. when doing so you need to have the repartition box checked.
The unbrickable mod by adam outler is a hardware mod that allows you to recover from a brick. Google it.
Sent from my SCH-I500 using xda premium
As some possible help, Have you tried sixstringsg one click. Not sure if it re-partitions but here's the link! EH03 Heimdall One-Click
Also you say the tar's are failing at 99%, have you tried flashing them individually? IE: extract the tar and use the following!
Code:
heimdall flash --repartition --pit atlas_v2.2.2.pit --factoryfs factoryfs.rfs --cache cache.rfs --dbdata dbdata.rfs --primary-boot boot.bin --secondary-boot Sbl.bin --param param.lfs --kernel zImage --modem modem.bin --recovery recovery.bin
neh4pres said:
Well, first you don't flash the atlasv2.2pit. that file is a partition map. It repartitions the phone when combined with a factory image. when doing so you need to have the repartition box checked.
The unbrickable mod by adam outler is a hardware mod that allows you to recover from a brick. Google it.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Oops sorry, I didnt actually flash the atlas.pit file. I meant the only files I got to PASS in Odin were the ones mentioned. The unbrickable mod looks way to complicated, and I dont feel comfortable taking apart my phone and soldering it.
What do you know about unbricking via adb? I just installed it yesterday so I dont know all the shell commands. If my phone can't wipe or mount data, i cant get past this damn movinand.bin in odin, and my internal memory is zero - is there a folder i need to go in and delete in adb that is preventing me from flashing in odin? Can't I just delete all data so I'm free to flash anything? It seems like something is still present in my phone to be showing 0 internal memory and not letting me wipe data that needs to be removed.
JSlice said:
Oops, sorry man , I didnt actually flash the atlas.pit file. I meant the only files I got to PASS in Odin were the ones mentioned. The unbrickable mod you mentioned requires that I need to take the phone apart and solder the hardware, is that correct? If that's the case, then I'll go ahead and cross that out as a possible solution.
What do you know about unbricking via adb? I just installed it yesterday so I dont know all the shell commands. If I my phone can't wipe or mount data, i cant get past this damn movinand.bin in odin, and my internal memory is zero - is there a folder i need to go in and delete in adb that is preventing me from flashing in odin? Can't I just delete all data so I'm free to flash anything? It seems like something is still present in my phone to be showing 0 internal memory and not letting me wipe data that needs to be removed.
Click to expand...
Click to collapse
I'm just a user, I think your looking for a 1337 mofo.
I think you need to get familiar with irc, and contact the overlords
Sent from my SCH-I500 using xda premium
I seriously doubt that all this was caused by deleting Superuser. You likely have a corrupt filesystem. Have a look at this thread:
http://forum.xda-developers.com/showthread.php?t=1705257
Hey there,
I'm trying to get CyanogenMod on my friend's aging Vibrant. I first rooted, and then I attempted to install ClockworkMod through the stock recovery. At first it just restarted back to the stock recovery, so I installed it again, and boom- CWM. From there, I wiped, went to mount USB storage, and the drive didn't show up on my computer. I figured it needed to be rebooted, so I tried that. This time, it reverted BACK to stock recovery. I figured, okay, all I have to do is flash CWM again. It won't work anymore. I don't know what to do, because I can't flash CWM, a Rom, or even restore the original rom because I can't get into CWM.
Please help!
vindication84 said:
Hey there,
I'm trying to get CyanogenMod on my friend's aging Vibrant. I first rooted, and then I attempted to install ClockworkMod through the stock recovery. At first it just restarted back to the stock recovery, so I installed it again, and boom- CWM. From there, I wiped, went to mount USB storage, and the drive didn't show up on my computer. I figured it needed to be rebooted, so I tried that. This time, it reverted BACK to stock recovery. I figured, okay, all I have to do is flash CWM again. It won't work anymore. I don't know what to do, because I can't flash CWM, a Rom, or even restore the original rom because I can't get into CWM.
Please help!
Click to expand...
Click to collapse
Okay, I've never had this issue personally, nor have I read of anyone else having a similar issue. However, despite the lack of CWR, you can still restore the device back to stock via Odin. There is a guide on the usage of Odin that can be found here. Download links to the program along with the required .pit and .tar files can also be found in said guide. Once you've got the device restored, you can go through the process of installing CyanogenMod... But, keep in mind that the installation process is going to vary slightly depending on what version of CyanogenMod you wish to install. Are you trying to install CyanogenMod 7 (Gingerbread), 9 (Ice Cream Sandwich), 10 (Jellybean 4.1), or 10.1 (Jellybean 4.2)?
I know about Odin, but I'm on a Mac right now. I was really hoping there was a way around this so I didn't have to install Windows via Boot Camp. I'm planning on installing CM10.
vindication84 said:
I know about Odin, but I'm on a Mac right now. I was really hoping there was a way around this so I didn't have to install Windows via Boot Camp. I'm planning on installing CM10.
Click to expand...
Click to collapse
You could use Heimdall, an alternative to Odin that is compatible with OS X. You can download it here.
Now, in regards to the process of installing CM10, you could refer to this video... http://forum.xda-developers.com/showthread.php?t=1812882. Hopefully you won't get that weird CWR issue this time around. Let me know how it goes. :fingers-crossed:
No matter what, I can't get Heimdall to detect the phone. It just says "Failed to detect compatible download-mode device".
vindication84 said:
No matter what, I can't get Heimdall to detect the phone. It just says "Failed to detect compatible download-mode device".
Click to expand...
Click to collapse
Hmm... Perhaps this post might be of some help? Sorry, but I don't own a Mac, nor have I ever personally used Heimdall... So I've never had that issue before. However, a little Google searching uncovered a bunch of threads discussing this exact error. Perhaps a little digging may uncover your answer? Link. Again, best of luck dude.
Can you get back into the stock recovery and transfer files to the internal SD? If so, you need to flash update.zip(attached). It will add a custom recovery. You may need to flash it twice to get it to show up. From there, I would suggest you do the following: 1) wipe user data, cache and davlik(under advanced) 2) reboot recovery, if the stock recovery comes back, just reflash update.zip. 3) Flash whichever ROM you want on the phone, again, may take two flashes.
If you cannot add files to the internal SD, this solution won't work, in which case you'll have to play around a little more. I would suggest, as an alternate method, that you pull the battery and SD card. replace the battery and try to enter download mode. Try using Heimdal One-Click(http://forum.xda-developers.com/showthread.php?t=1278683). It's much easier than using Heimdal or Odin and will flash the Vibrant to stock. View the download mode shortcut below.
Side note: hardware shortcuts help a lot. If you don't know them, they are here:
Hold volume up + volume down + power =
1. When off, boots recovery
2. When on, reboots into recovery
Hold volume up + volume down +plug in computer USB = download mode.
^This is what you use for Odin and/or Heimdal. They won't recognize the device unless it's in download mode.
May also take a few tries.
Let me know how it goes and if you have any questions.
EDIT: You may need to have the phone on the stock ROM to flash that update.zip. I ran into that problem and couldn't figure out why it wasn't working for a long time. Don't update the vibrant to stock 2.2 to use the update.zip.
danvsullivan said:
Can you get back into the stock recovery and transfer files to the internal SD? If so, you need to flash update.zip(attached). It will add a custom recovery. You may need to flash it twice to get it to show up. From there, I would suggest you do the following: 1) wipe user data, cache and davlik(under advanced) 2) reboot recovery, if the stock recovery comes back, just reflash update.zip. 3) Flash whichever ROM you want on the phone, again, may take two flashes.
If you cannot add files to the internal SD, this solution won't work, in which case you'll have to play around a little more. I would suggest, as an alternate method, that you pull the battery and SD card. replace the battery and try to enter download mode. Try using Heimdal One-Click(http://forum.xda-developers.com/showthread.php?t=1278683). It's much easier than using Heimdal or Odin and will flash the Vibrant to stock. View the download mode shortcut below.
Side note: hardware shortcuts help a lot. If you don't know them, they are here:
Hold volume up + volume down + power =
1. When off, boots recovery
2. When on, reboots into recovery
Hold volume up + volume down +plug in computer USB = download mode.
^This is what you use for Odin and/or Heimdal. They won't recognize the device unless it's in download mode.
May also take a few tries.
Let me know how it goes and if you have any questions.
EDIT: You may need to have the phone on the stock ROM to flash that update.zip. I ran into that problem and couldn't figure out why it wasn't working for a long time. Don't update the vibrant to stock 2.2 to use the update.zip.
Click to expand...
Click to collapse
I already have the update.zip on the phone. I can get into the stock recovery and flash it (it says "replacing recovery with Clockwork" and everything), but every time I attempt to flash it, the phone reboots to the stock recovery. I can't add files to the internal SD because the only options are Reboot System Now, Reinstall Packages, Delete All User Data, and Delete Cache Data"
One-Click doesn't see the phone either. I'm starting to get really worried. Is there some sort of driver or something I need to have installed on the system?
SOLVED!
Alright, I finally figured it out. I'm exhausted, haha.
I finally just bit the bullet and installed Windows. I used ODIN, which was such a breeze. I wish I would have just done that in the first place.
Thanks for your help guys!
vindication84 said:
Alright, I finally figured it out. I'm exhausted, haha.
I finally just bit the bullet and installed Windows. I used ODIN, which was such a breeze. I wish I would have just done that in the first place.
Thanks for your help guys!
Click to expand...
Click to collapse
Glad to hear the good news!
Hope this time you'll be able to update the phone seamlessly, and your friend can enjoy a newly updated Vibrant. If you ever have any questions, don't hesitate to PM me. I'll try my best to help you out.
danvsullivan said:
Try using Heimdal One-Click(http://forum.xda-developers.com/showthread.php?t=1278683).
Click to expand...
Click to collapse
Although I had heard of Bay_wolf's AIO Vibrant Toolbox, which is also a one-click software (but only compatible w/Windows), I had never heard of "Heimdal One-Click". This is good to know about, and I've added the program to the The Official XDA Vibrant Bible Thread. I learn something new every day. Thanks!
vindication84 said:
Alright, I finally figured it out. I'm exhausted, haha.
I finally just bit the bullet and installed Windows. I used ODIN, which was such a breeze. I wish I would have just done that in the first place.
Thanks for your help guys!
Click to expand...
Click to collapse
Great news! You can follow the instructions I wrote out to install a custom ROM from stock. Just put all the files on the internal SD, wipe everything and flash update.zip and then the ROM and gapps.
If you have questions, you may PM me as well.
Good luck!
Hi Guys,
Sorry to bother you with this, but I'm out of ideas...
I decided to root my i9100 using this guide9.
As I was doing this, the recovery rom would reboot when using the volume buttons to navigate (only on the first "page") - This was easily worked around by using the touchscreen, but now I'm wondering if this was the start of my issues...
I applied the SU busy box installer, and got root. I installed rom manager, and noticed that it seemed to lock up when doing certain things. I put this down to CWM saying there was no official mod for the i9100.
The next day I decided to try and install a CM10.1 nightly, so I took a backup, wiped cache and data, and applied the rom and gapps.
When I rebooted, the phone wouldn't finished booting, it just sat at the initial logo screen.
After that, I tried following this recovery guide but the odin flash failed at around 80% (I retried and the same happened again).
Since then I've had difficulty getting in to recovery mode. I've tried flashing various stock roms with odin, and trying to restore with Kies.
In Kies I get as far as it conencting to the phone in download mode, but it pops up a "notice" in a foreign language - presumably Korean (and I can't copy the text to even attempt a google translation).
I tried flashing Siyah-s2-v5.0.1 to get a different recovery - that seemed to have a garbled progress bar, before hanging when I tried to wipe /data again.
When I use odin to flash a stock rom - is it supposed to restore absolutely everything? I'm not sure how I'm still getting problems if this is the case. Any ideas on what to try next?
(The current stock rom I'm try ing to use is this one)
Let me know if I'm missing any info, and thanks in advance for any help.
Using rom manager would have been the start of your problems-not the temp cwm recovery in the rooting guide.
If you can boot into download mode then I would download LP7 stock rom, disable kies and flash that with Odin.
{go back to your iphone since you are an android noob}
Thanks for the reply.
Rom manager didn't work properly for me, so I stopped using it. I used the temp cwm recovery to install the CM nightly.
I can boot in to download mode, but I've already tried an LP7 rom, - as with the others, it doesn't boot.
Any ideas on how to tell why it isn't booting? logcat doesn't seem to want to to work. Not sure if it's broken / too early in the boot process / etc
Silly Billy said:
Thanks for the reply.
Rom manager didn't work properly for me, so I stopped using it. I used the temp cwm recovery to install the CM nightly.
I can boot in to download mode, but I've already tried an LP7 rom, - as with the others, it doesn't boot.
Any ideas on how to tell why it isn't booting? logcat doesn't seem to want to to work. Not sure if it's broken / too early in the boot process / etc
Click to expand...
Click to collapse
I9100 right?
Try this:
- Download this ROM.
- Kies installed? uninstall it, re install it. Close it all up with Task manager (3 or 4 applications running).
- Flash ROM via Odin (CSC, MODEM, PHONE).
- If that doesn't fly, try another usb port & usb cable. Another PC would also be recommended.
- Repeat the process.
- Still no luck? try flashing a previous siyah version.
- No go? repeat all the above.
- Let us know how you did.
gastonw;37017081- Download this ROM.[/QUOTE said:
Thanks, I'll give it a go. (Will take a while for the file to download from hotfile...).
Are odin images for stock roms supposed to restore the stock recovery, or do they leave that alone?
Click to expand...
Click to collapse
As a matter of interest, how far did you go with Phistachios repair guide.
{go back to your iphone since you are an android noob}
Silly Billy said:
Thanks, I'll give it a go. (Will take a while for the file to download from hotfile...).
Are odin images for stock roms supposed to restore the stock recovery, or do they leave that alone?
Click to expand...
Click to collapse
Focus on getting a ROM to boot.
That ROM will install stock recovery.
gastonw said:
Let us know how you did.
Click to expand...
Click to collapse
For some reason, I can't get Odin to flash that rom - it just hands for a while at the start of data.img, before saying "Complete(Write) operation failed."
There a .pit file in the archive, although the link says not to repartition (so I didn't).
Some roms seem to get written, some don't, I'm not sure why...
theunderling said:
As a matter of interest, how far did you go with Phistachios repair guide.
Click to expand...
Click to collapse
Odin failed about 80% through flashing (step 4, after taking the ICS steps). I tried flashing the kernel afterwards, which flashed, but didn't help with my boot issues.
gastonw said:
Focus on getting a ROM to boot.
That ROM will install stock recovery.
Click to expand...
Click to collapse
Of course, I was just trying to get a better understanding of how things work - I'd settle for anything booting right now.
I was meaning how far did you go with his guide.He says (near the end) to flash a bootloader/kernel/rom.
You can try everything in his guide, but understand about the risks involved with pit and bootloaders.
{go back to your iphone since you are an android noob}
theunderling said:
I was meaning how far did you go with his guide.He says (near the end) to flash a bootloader/kernel/rom.
You can try everything in his guide, but understand about the risks involved with pit and bootloaders.
{go back to your iphone since you are an android noob}
Click to expand...
Click to collapse
He's right.
Keep trying, consider pit files & bootloaders as a last resort.
Tried everything?
Used another usb cable for the flash? tried in another PC? tried in a laptop?
Are you sure kies is all shut down?
I've read about so many people having the same issue than you, they keep on flashing as in trial & error and most times they come out winners.
GL!
gastonw said:
He's right.
Keep trying, consider pit files & bootloaders as a last resort.
Tried everything?
Used another usb cable for the flash? tried in another PC? tried in a laptop?
Are you sure kies is all shut down?
I've read about so many people having the same issue than you, they keep on flashing as in trial & error and most times they come out winners.
GL!
Click to expand...
Click to collapse
I guess I'll keep at it then.
I'd tried another cable with kies shut down. Just tried a different machine, and flashed the ROM you suggested with heimdall. It flashed without complaining (unlike odin), but I'm still getting a boot loop.
Looking at the initial recovery guide I was following - I suspect that I might've flashed the bootloader (the guide shows in bold which file goes in which box, so I probably loaded them all). Maybe this is the source of my troubles...
I also noticed that heimdall can pull data from the phone too - if I can pull and mount these, am I likely to find any useful log files?
For completeness (and anyone else who finds themselves with the same issue): It seems I hit the EMMC brick bug, which rendered some of my EMMC storage unusable.
This helpful chap came up with a workaround to partition around the dead space. (Please read the post carefully and make sure this really is your problem before flashing!)
That method will let you know what part of your memory is corrupted. It's done via recovery as far as I remember.
Did you bring your device back to life?
Sent from the little guy
gastonw said:
That method will let you know what part of your memory is corrupted. It's done via recovery as far as I remember.
Did you bring your device back to life?
Click to expand...
Click to collapse
Yes, that's right. IIRC, I flashed a working recovery with Odin, then did most of the work from adb shell.
I got my device back to life for the most part. I get the occasional hang but haven't investigated much (have since bought a Nexus 4, so not using the S2 so much).
Just thought I'd share for the next poor soul who has the same problem