thanks shady for the toggles and letting me use your theme. After installing boot will take approx 3-5 mins. Update superuser from the market.
Deodexed, Rooted, Overclocked, Webtop via HDMI mod, Toggles, Zipaligned.
....Flash at your own risk....
WIPE DATA/FACTORY RESET
http://depositfiles.com/files/wk7i3b1n1 <----Stock Rooted 2.3.5
http://www.mediafire.com/?rt4v29ompo3am6s <----Alt Link 2.3.5
http://www.multiupload.com/IZVCVPRNGJ <----Alt Link 2.3.5
Good luck and let me know about any issues not already covered.
ps. voice search and maps would not deodex so get them from the market.
http://forum.xda-developers.com/showthread.php?t=1385283
^--This works for us. I cant tell you how many times this has saved me from using rsd just b/c of a bootloop.
There seems to be some confusion with overclocking, If you don't understand it please read through this thread.
http://forum.xda-developers.com/showthread.php?t=1341514
___________________________________________________________________
Stock Rooted Deodxed 2.3.6
http://depositfiles.com/files/dmi40o4qx <----2.3.6
^---This is a cwm backup. You will need to wipe data/factory reset then restore the backup. Extract zip to root of sd card
________________________________
***********MD5**************
StockRootedDeodex 2.3.5 36E1DE744C0144C70AFF4BFD624BA369 *StockRootedOcWebDeodex.zip
StockRootedDeodex 2.3.6 BA6AF46EF4A2E0904422E6F73E8893AE *236_Rooted_Deodex_Do_No_Flash.rar
[Theme's]
1.) adb push framework-res.apk /mnt/sdcard
2.) adb push SystemUI.apk /mnt/sdcard
3.) adb push Settings.apk /mnt/sdcard
4.) adb push BlurPhone.apk /mnt/sdcard
5.) adb push BlurDialer.apk /mnt/sdcard
6.) adb push GoogleQuickSearchBox.apk /mnt/sdcard
7.) su
8.) mount -o rw,remount /dev/null /system
9.) cp /sdcard/framework-res.apk /system/framework
10.) cp /sdcard/SystemUI.apk /system/app (case sensitive)
11.) cp /sdcard/Settings.apk /system/app (case sensitive)
12.)cp /sdcard/BlurPhone.apk /system/app (case sensitive)
13.)cp /sdcard/BlurDialer.apk /system/app (case sensitive)
14.)cp /sdcard/GoogleQuickSearchBox.apk /system/app (case sensitive)
15.) reboot
16.) click thanks!
http://db.tt/qd0dVE0p <--Ics/Artic
Flashable Zip http://www.multiupload.com/9ANWSIAPA9
http://db.tt/21dhrctR <--ICS
Flashable Zip http://www.multiupload.com/SN3DKIIVNI
(Ports from shadys various themes)
***Wanna be sure your not going to boot loop? Make a backup and install the cwm on boot linked above. Commands are the same in recovery omitting 5&6 instead go to mounts and mount /system***
**The first 2 pictures are from Ics/artic, The last 4 pics are from ICS***
You peronally use the unofficial atrix 2 bootstrap for flashing correct?
Awesome man. I'm gonna hide in a corner and see what happens for now, but definitely exciting news.
Jimmy273 said:
You peronally use the unofficial atrix 2 bootstrap for flashing correct?
Click to expand...
Click to collapse
Yes
Everything downloaded well and is up and running!!! BTW boot took no longer than a usual boot on mine
Could you give some clarification on some of the notification drop down toggles and what they are? What is the little sun like icon and the circle arrow icon?
Will leave feedback as more proper use comes
I would guess the sun icon is brightness control and the circle arrow is sync
Sent from my MB865 using xda premium
Flashing it right now!
Jimmy273 said:
You peronally use the unofficial atrix 2 bootstrap for flashing correct?
Click to expand...
Click to collapse
Yes sir I do.
We need some step by step on how to install this ROM.
already flashed, so far so good.
Here is what i dou need to root first)
1: go here and download Bootstrap Recovery
http://forum.xda-developers.com/showthread.php?t=1346977
2: Download the rom and put it on sd card
3: install the app and boot into recovery.
4: do a backup first
5: factory reset
6: flash the rom
7: reboot!
last thing !!!!! Flash at your own risk!!!!!!!!!!
OH almost forgot. HAPPY NEW YEAR!!!!!
Just flashed so far so good
Sent from my MB865 using xda premium
What is this overclocked to and what other changes does it have. Maybe someone thats done it can do a video demonstration on youtube.
Running great so far..awesome job..thought I was gonna have to wait months for something..on point..just came reluctantly over from a g2x due to T-Mobiles lack of sympathy for the broke...any way to get instructions on how to overclock via terminal emulator?
Sent from my MB865 using xda premium
Are we able to restore Nandroid backups successfully? I read in the other thread that .img files were not present in the Nandroid backup. Has that been resolved?
devsk said:
Are we able to restore Nandroid backups successfully? I read in the other thread that .img files were not present in the Nandroid backup. Has that been resolved?
Click to expand...
Click to collapse
Yup! You can use it like you would any other cwm.
pretty much all cwm features are working, nandroid backup, restore, flash rom, wipe......
Thanks for the ROM!
So, let's see if I understand how this works: the only thing we can't do yet without unlocking the bootloader is to install a different kernel. Everything else can be changed, right?
devsk said:
Are we able to restore Nandroid backups successfully? I read in the other thread that .img files were not present in the Nandroid backup. Has that been resolved?
Click to expand...
Click to collapse
Yup! Everything restored perfectly for me...
Sent from my MB865 using xda premium
Its telling me that its at 300-1000Mhz. I don't believe its OC'd? Otherwise, LOVING it. Thanks a ton.
Sent from my MB865 using XDA App
---------- Post added at 09:40 AM ---------- Previous post was at 09:36 AM ----------
Zoide_ said:
Thanks for the ROM!
So, let's see if I understand how this works: the only thing we can't do yet without unlocking the bootloader is to install a different kernel. Everything else can be changed, right?
Click to expand...
Click to collapse
Can't flash new radios either.
Calundle said:
Its telling me that its at 300-1000Mhz. I don't believe its OC'd? Otherwise, LOVING it. Thanks a ton.
Click to expand...
Click to collapse
I think right now its not, but the scripting is there so if you want the OC you have to do it manually via terminal emulator or ADB shell.
I've had no problems as well. Cant wait to see the OC and a theme on it BTW loving the notification toggles!!! If airplane mode was included it would be set!!!
Related
Defy Froyo 3.4.2 Cookie Cutter Rom​
Q. How Do I use the Update.zip?
A. Go to Market & Download Defy SD-Recovery & Install..
1. Next place the Update.zip on the /sdcard via PC
2. Turn on MoTo Phone Portal ( SD-Recovery is SD Based so you need to Turn Off USB Mass Storage )
3. ADB Debugging does not have to be Turned Off on my version
Once Booted into the Recovery apply the update.zip
wait a few minutes & it should be done...
Please Reads the notes I left in the Update.zip if you build a Custom Update.zip, this will save you trouble down the road.
What's Flashed?
A. Boot.img
B. dev_tree
C. Moto Blur 3.4.2 Rom ( Yes I know it's not the latest, built off what I had )
D. UNO & TMO-TV Removed
E. Rooted ( SU & Superuser )
F. Busybox Installed to xbin
G. Rest of Rom is stock
Once installed, remove eugene.apk from /system/app ( Old boot strap that need adb turned off before rebooting / defy sd-recovery does not have this issue)
Q. I Edited the update.zip & Now it fails verf. in recovery when trying to flash!
A. example of signapk on signing the edited update
java -Xmx1024m -jar signapk.jar -w testkey.x509.pem testkey.pk8 update1.zip update.zip
Download: Original Post
To Update other parts of the Phone: Add this to the update-scripts for what you are flashing.
If we had all these Parts from 2.1 we could go back.
package_extract_file("lbl", "/tmp/lbl");
write_raw_image("/tmp/lbl","lbl");
delete("/tmp/lbl");
package_extract_file("device_tree.bin", "/tmp/device_tree.bin");
write_raw_image("/tmp/device_tree.bin","devtree");
delete("/tmp/device_tree.bin");
package_extract_file("cdrom", "/tmp/cdrom");
write_raw_image("/tmp/cdrom","cdrom");
delete("/tmp/cdrom");
package_extract_file("logo.bin", "/tmp/logo.bin");
write_raw_image("/tmp/logo.bin","logo.bin");
delete("/tmp/logo.bin");
package_extract_file("umts_wrigleyref_build.bin", "/tmp/umts_wrigleyref_build.bin");
write_raw_image("/tmp/umts_wrigleyref_build.bin","bpsw");
delete("/tmp/umts_wrigleyref_build.bin");
package_extract_file("cdt.bin", "/tmp/cdt.bin");
write_raw_image("/tmp/cdt.bin","cdt.bin");
delete("/tmp/cdt.bin");
Hey eugene,
Glad to see you working on Defy too
I think this will be major help for developers and btw that 3.4.2 version did you used? since there are many of them.
Thanks.
um. 107 I think since it has a floating update.zip someplace & sbf.
Ill update to the latest when I start building roms
Sent from my MB525 using XDA App
i don't understand. is the boot.img still the signed cg35.smg?
if so, can't we just use the cmw to do that?
can you post more detailed chages you made over cmw?
other than the signapk and usb debugging described.
many thanks.
eugene373 - great work!
racca said:
i don't understand. is the boot.img still the signed cg35.smg?
if so, can't we just use the cmw to do that?
can you post more detailed chages you made over cmw?
other than the signapk and usb debugging described.
many thanks.
Click to expand...
Click to collapse
Same here, i'm pretty interested in more details, thank you
this Zip File is for what ?
Thanks
Greetings
you can not use cwm due encryption. If you dont know what an update.zip is stick to nandroid...
This is for rom builders.
Heading out, when I get home ill make it clearer.
Though, now that I think about it cwm might be fine due to the nature of how it works.
Ill test later and let everyone know
Sent from my MB525 using XDA App
So we are able to install updates via the "normal" Motorola Recovery mode? So we are able to get a "unbrickable" Defy?
Edit: got it myself. The ZIP File won't be recognized by the motorola recovery... anyway thanks for your job
Now, what can SD-recovery do? Can it write other partitions, like cdt.bin?
Simplestas said:
Now, what can SD-recovery do? Can it write other partitions, like cdt.bin?
Click to expand...
Click to collapse
Yes. I can add the string if you would like
eugene373 said:
To Update other parts of the Phone: Add this to the update-scripts for what you are flashing.
package_extract_file("lbl", "/tmp/lbl");
write_raw_image("/tmp/lbl","lbl");
delete("/tmp/lbl");
package_extract_file("device_tree.bin", "/tmp/device_tree.bin");
write_raw_image("/tmp/device_tree.bin","devtree");
delete("/tmp/device_tree.bin");
package_extract_file("cdrom", "/tmp/cdrom");
write_raw_image("/tmp/cdrom","cdrom");
delete("/tmp/cdrom");
package_extract_file("logo.bin", "/tmp/logo.bin");
write_raw_image("/tmp/logo.bin","logo.bin");
delete("/tmp/logo.bin");
package_extract_file("umts_wrigleyref_build.bin", "/tmp/umts_wrigleyref_build.bin");
write_raw_image("/tmp/umts_wrigleyref_build.bin","bpsw");
delete("/tmp/umts_wrigleyref_build.bin");
package_extract_file("cdt.bin", "/tmp/cdt.bin");
write_raw_image("/tmp/cdt.bin","cdt.bin");
delete("/tmp/cdt.bin");
Click to expand...
Click to collapse
eugene373 said:
Yes. I can add the string if you would like
Click to expand...
Click to collapse
CwM can do exactly the same afaik, i've already made quite a few update.zip with it.
after reading all your notes, do you actually mean that we can't use format on those patitions?
if you do, well, i learned it the hard way, and delete_recursive also works for me.
thanks for putting up an excellent example if not for anything else, it's much needed.
racca said:
CwM can do exactly the same afaik, i've already made quite a few update.zip with it.
after reading all your notes, do you actually mean that we can't use format on those patitions?
if you do, well, i learned it the hard way, and delete_recursive also works for me.
thanks for putting up an excellent example if not for anything else, it's much needed.
Click to expand...
Click to collapse
Correct, you can only format with the stock recovery ( Hence the reason why I used the Stock Recovery ) any Partition with cwm recovery will cause a non-booting system..
regarding cwm I've not tested it, so Likely it will work.. Steven is still working on the cwm recovery & there is no point in me adding another cwm bootstrap recovery... Mine is just pure stock & works perfect.
I'm still weeding through the /bin /etc file's to find exactly what needs left...
but main goal was to provide an example of what is needed to make an update.zip with out breaking the system.
what exactly is the benefit of this new method?
drsouly said:
what exactly is the benefit of this new method?
Click to expand...
Click to collapse
um? Your joking right!
Update versus a nandroid, I would have thought it was a no brainier....
Build & edit roms on the fly + being able to flash boot.img & downgrading is fine without sbf unless you screw up completely..
eugene373 said:
um? Your joking right!
Update versus a nandroid, I would have thought it was a no brainier....
Build & edit roms on the fly + being able to flash boot.img & downgrading is fine without sbf unless you screw up completely..
Click to expand...
Click to collapse
ok now i got it thx
drsouly said:
ok now i got it thx
Click to expand...
Click to collapse
no problem, wasn't sure if you was being a smart-ass or honestly didn't know...
either way, sorry If I offended you.
~Eugene
I didn't understand yet . I can or not apply the update file using stock recovery?
EDIT: forget I understood now.
Sent from my MB525 using XDA App
psicodelico said:
I didn't understand yet . I can or not apply the update file using stock recovery?
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Read OP.... Download Defy SD-Recovery from Market
Yeah, I read again slowly and understood.
Sent from my MB525 using XDA App
I am putting this up for new users of the Samsung Galaxy S 4g that are having issues with flashing, well, pretty much any rom right now.
1) The main issue right now is our recovery and rom manager not working together....NOT THE ROM's!
2) Here is a walk through for problem free flashing (I have officially flashed every rom posted here right now and have no issues whatsoever)
So here we go:
1) I'll start this assuming you have already rooted.
2) Download the update.zip and recovery from HERE
3) Place files on the root of your sdcard (not in any file) DO NOT UNZIP THE UPDATE.ZIP!!!
4) You must have a file system explorer with root permissions (IE...Root Explorer or equivalent)
5) Once in Root Explorer, your system MUST BE MOUNTED AS R/W, navigate to your sdcard, find the recovery file you downloaded and long press....select "copy"
6) Hit the back button until you return to the file marked "/" and make sure it is still mounted r/w, then navigate to system, then bin. Once you are in bin (this is important) hit "paste" on the bottom of your screen. It will ask if you want to overwrite the existing recovery. Select yes. DO NOT REPLACE IT, ONLY OVERWRITE IT!!!
7) Keep hitting the back button on your phone until you exit out of root explorer.
8) Power off your phone, then, after fully shut down, holding volume up AND down plus power (yes, hold all 3 of them) you will enter a blue stock recovery screen. Scroll down 1 option to "reinstall packages", press power........you should now be in the orange Clockwork Mod recovery.
9) Scroll down to "backup and restore" and hit power, then go to "Backup" and hit power. Let it do it's thing. This will create a backup on your sdcard in a file called "clockwork". Keep this so you can restore in case something goes wrong (or like me, like to change things up all the time).
10) Now, again, I will assume that you have the rom of your choice on the root of your sdcard. This is where things get screwy....so pay attention to the OP's instructions for mounts. Scroll to "mounts and storage" and hit power.
11) The first 4 things you will see are : /cache, /data, /sdcard, and /system. This is where you need to pay close attention to what you are doing.
A) For KD1 and Bionix Frost your mounts must appear like this:
/cache : unmount
/data : mount
/sdcard : mount
/system : unmount
B) For Trigger your mounts must appear like this:
/cache : unmount
/data : unmount
/sdcard : mount
/system : unmount
If they are not in this order,change them so they are, or it will flash but will not boot. YOU WILL BE IN A SOFT BRICK STATE THAT REQUIRES ODIN TO FIX!!!!
12) Install RomManager if you wish, but DO NOT, I REPEAT DO NOT FLASH CLOCKWORKMOD RECOVERY FROM THE LIST, this will cause your phone to get stuck at wiping a file called /.android_ secure in recovery.....so once again, HELLO ODIN! Also DO NOT REBOOT RECOVERY from rom manager, this will also cause /.android_secure to not wipe.....so once again, HELLO ODIN!
Last but not least, follow instructions on the OP to the "T" and you will be fine, unless you enjoy odin that much.....personally, I hate it.
If anything here is wrong or not working for you, please let me know so I can fix/update this. Please double/triple check everything that you did and make sure it is correct before *****ing "It's still not working".......because it does work. I have flashed and flashed and flashed with only 1 soft brick, and that was my fault.....not these instructions fault.
To see if I can make this make a little more sense now, here we go: The reason for changing mounts is that, by default, /system is not mounted. To be able to flash and boot successfully, it has to be. When you are looking at them, it will say "mount", this means that it is NOT mounted. If it says "unmount", then it means it IS mounted, confused yet? Just remember it like this: It is the opposite of what it says...so make sure that system says "unmount", which actually means it's mounted. This step is absolutely CRUCIAL.
Enjoy the hell out of your bad ass Samsung Galaxy S 4g, because I am
This should definitely make the sgs4g bible. Its a great tutorial on getting through the flashing issues people are having. Thank you this is ( . ) ( . )
Sent from my SGH-T959V using XDA Premium App
mad_fitter said:
I am putting this up for new users of the Samsung Galaxy S 4g that are having issues with flashing, well, pretty much any rom right now.
1) The main issue right now is our recovery and rom manager not working together....NOT THE ROM's!
2) Here is a walk through for problem free flashing (I have officially flashed every rom posted here right now and have no issues whatsoever)
So here we go:
1) I'll start this assuming you have already rooted.
2) Download the update.zip and recovery from HERE
3) Place files on the root of your sdcard (not in any file) DO NOT UNZIP THE UPDATE.ZIP!!!
4) You must have a file system explorer with root permissions (IE...Root Explorer or equivalent)
5) Once in Root Explorer, your system MUST BE MOUNTED AS R/W, navigate to your sdcard, find the recovery file you downloaded and long press....select "copy"
6) Hit the back button until you return to the file marked "/" and make sure it is still mounted r/w, then navigate to system, then bin. Once you are in bin (this is important) hit "paste" on the bottom of your screen. It will ask if you want to overwrite the existing recovery. Select yes. DO NOT REPLACE IT, ONLY OVERWRITE IT!!!
7) Keep hitting the back button on your phone until you exit out of root explorer.
8) Power off your phone, then, after fully shut down, holding volume up AND down plus power (yes, hold all 3 of them) you will enter a blue stock recovery screen. Scroll down 1 option to "reinstall packages", press power........you should now be in the orange Clockwork Mod recovery.
9) Scroll down to "backup and restore" and hit power, then go to "Backup" and hit power. Let it do it's thing. This will create a backup on your sdcard in a file called "clockwork". Keep this so you can restore in case something goes wrong (or like me, like to change things up all the time).
10) Now, again, I will assume that you have the rom of your choice on the root of your sdcard. This is where things get screwy....so pay attention to the OP's instructions for mounts. Scroll to "mounts and storage" and hit power.
11) The first 4 things you will see are : /cache, /data, /sdcard, and /system. This is where you need to pay close attention to what you are doing.
A) For KD1 and Bionix Frost your mounts must appear like this:
/cache : unmount
/data : mount
/sdcard : mount
/system : unmount
B) For Trigger your mounts must appear like this:
/cache : unmount
/data : unmount
/sdcard : mount
/system : unmount
If they are not in this order,change them so they are, or it will flash but will not boot. YOU WILL BE IN A SOFT BRICK STATE THAT REQUIRES ODIN TO FIX!!!!
12) Install RomManager if you wish, but DO NOT, I REPEAT DO NOT FLASH CLOCKWORKMOD RECOVERY FROM THE LIST, this will cause your phone to get stuck at wiping a file called /.android_ secure in recovery.....so once again, HELLO ODIN! Also DO NOT REBOOT RECOVERY from cwm, this will also cause /.android_secure to not wipe.....so once again, HELLO ODIN!
Last but not least, follow instructions on the OP to the "T" and you will be fine, unless you enjoy odin that much.....personally, I hate it.
If anything here is wrong or not working for you, please let me know so I can fix/update this. Please double/triple check everything that you did and make sure it is correct before *****ing "It still not working".......because it does work. I have flashed and flashed and flashed with only 1 soft brick, and that was my fault.....not these instructions fault.
Enjoy the hell out of your bad ass Samsung Galaxy S 4g, because I am
Click to expand...
Click to collapse
HAHAHAHA man good job on sending me that personal message i was in the process of typing everything!!! wonderful guide! keep up the good work!!
dsexton702 said:
HAHAHAHA man good job on sending me that personal message i was in the process of typing everything!!! wonderful guide! keep up the good work!!
Click to expand...
Click to collapse
Thanks brudda I wanted to hurry up and get ahold of you before you wasted all of your time and talent
@Mr. Clown , Any chance this could get a sticky in general until these issues disappear? I only ask so that the development threads can stop getting CLOGGED with "I can't get it to flash" and "I can't get it to boot" or "I still can't get into recovery" (making your life easier )
Great post!..quick question as for the rom..I heard that the mounts should look diffirent before and after flash..so after flash how should i order them?
Sent from my SGH-T959V using XDA App
johndrdragon said:
Great post!..quick question as for the rom..I heard that the mounts should look diffirent before and after flash..so after flash how should i order them?
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Don't be concerned with how they look afterwards. I never have. Just make sure that when you flash they are set up properly
Thanks..one more question im currently running odex kd1 meaning original tmobile stock because i was actually waiting for roms...should I flash straight to bionix or trigger or go to kd1 first then flash those 2? because I"m concerned odex might mess it up
Sent from my SGH-T959V using XDA App
johndrdragon said:
Thanks..one more question im currently running odex kd1 meaning original tmobile stock because i was actually waiting for roms...should I flash straight to bionix or trigger or go to kd1 first then flash those 2? because I"m concerned odex might mess it up
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
No need to worry. Go ahead and flash away, just make sure to follow this and anything else the dev's tell you to
mad_fitter said:
No need to worry. Go ahead and flash away, just make sure to follow this and anything else the dev's tell you to
Click to expand...
Click to collapse
Don't forget his thanks button for this everyone
Sent from my SGH-T959V using XDA Premium App
dsexton702 said:
Don't forget his thanks button for this everyone
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
+1 brutha! Thank you
mad_fitter said:
No need to worry. Go ahead and flash away, just make sure to follow this and anything else the dev's tell you to
Click to expand...
Click to collapse
thanks a million,just flashed it!
Nice post, yo.
Sent from my SGH-T959V using XDA Premium App
johndrdragon said:
thanks a million,just flashed it!
Click to expand...
Click to collapse
I like to hear thanks
But, ummmm, ya >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>thanks button lol.
robbbbit said:
Nice post, yo.
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
Shanks dude
Great job! I just came from the HD2 and was wondering if any of these roms helps the ****ty battery life?
They are all better than stock for sure. Also if you use the battery recalibration trick.....its much better.
sent from the pits of hell (from an sgs4g)
yes im a noob and yes i approve of these directions lol ya followed to the letter got clock work installed and bali installed ty
I got a question. I have this problem since I screwed up flashing the first Trigger, and then, with a brain fart, odining with the Vibrant .pit file. I got it fixed but now it will not let me change the /cache mount. I am running Trigger .4 with no problems but just curious why I can't change that mount. When I go into root explorer the only file in there is "lost&found"????
Let me do some research on that one, lol.
sent from the pits of hell (from an sgs4g)
Nevermind, figured it out.
Trying to restore a stock backup in cwm. I get md5 mismatch error. Cause/solution inquiry.
Sent from my SAMSUNG-SGH-I727 using xda premium
hcyplr29 said:
Trying to restore a stock backup in cwm. I get md5 mismatch error. Cause/solution inquiry.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Couple of things...
Your backup might be corrupt if the md5 doesn't match.
or you might want to try and make sure you have the latest version of CWM installed on your phone. I read in one of the other threads that someone had an md5 mismatch problem that was solved with a newer version of CWM. I hope this helps.
hcyplr29 said:
Trying to restore a stock backup in cwm. I get md5 mismatch error. Cause/solution inquiry.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I had this happen to me once. Turned out the nand backup was bad....used the previous one I had made and was back in action. Had a few moments to sweat it out though. Just make sure to backup regularly and archives them.
Sent from my SAMSUNG-SGH-I727 using xda premium
same problem
i just encountered the same md5 mismatch problem. i have the lastest version of cwm but it doesnt help. i dont have previous stock roms as this was the first time i backed the rom up. any other solutions?
bshebib said:
i just encountered the same md5 mismatch problem. i have the lastest version of cwm but it doesnt help. i dont have previous stock roms as this was the first time i backed the rom up. any other solutions?
Click to expand...
Click to collapse
Disclaimer: This is just my opinion and I am not responsible if you have issues after taking my advice, etc., etc.
With that said...
Is the only issue that you can't make a backup or have you encountered other problems? Did you flash the superuser zip before making a backup? Did you try making a nadroid backup more than just once and it errored multiple times? Will the phone boot for you?
You could try to boot the phone up and reboot into recovery and try making a backup again. If all else fails you can just reflash everything back to stock and re-root. Make sure to read through all the guides very carefully and then...read them again....and when you get done with that....read them again. =)
1. Reflash stock.tar through Odin.
http://forum.xda-developers.com/showthread.php?t=1342348
2. Reflash CWM through Odin.
http://forum.xda-developers.com/showthread.php?t=1340526
3. Make a nandroid backup!!!
4. Flash SU zip.
5. Reboot
Good luck.
Presbycusis said:
Disclaimer: This is just my opinion and I am not responsible if you have issues after taking my advice, etc., etc.
With that said...
Is the only issue that you can't make a backup or have you encountered other problems? Did you flash the superuser zip before making a backup? Did you try making a nadroid backup more than just once and it errored multiple times? Will the phone boot for you?
You could try to boot the phone up and reboot into recovery and try making a backup again. If all else fails you can just reflash everything back to stock and re-root. Make sure to read through all the guides very carefully and then...read them again....and when you get done with that....read them again. =)
1. Reflash stock.tar through Odin.
http://forum.xda-developers.com/showthread.php?t=1342348
2. Reflash CWM through Odin.
http://forum.xda-developers.com/showthread.php?t=1340526
3. Make a nandroid backup!!!
4. Flash SU zip.
5. Reboot
Good luck.
Click to expand...
Click to collapse
This is exactly how I do it. I've never needed it but have always had it for emergency. Now that ICS is out I've been going back and forth from the sandwich to gingerbread because the bugs are well.......bugging me. I odin'd the leak then I backed it up after I installed cwm so I could always go back to that after testing out these other roms, cwm flashes, and even the backups of ICS, then I root. I basically have started from scratch twice and both times I went back to my backup I got the mismatch ( 2 different backups of the leak). I know its me (possibly cwm) because the cwm ics backup that's out there restores fine.
Sent from my SAMSUNG-SGH-I727 using XDA
Are you extracting on your PC? There seems to be some problems with unzips on the phone causing a mismatch
I've been using 7-zip for mine, and it works great. Extract files on the desktop, place on the external SD using USB
Got this from another forum
You can actually manually do it, and maybe get that backup fixed. Go to the backup folder /sdcard/clockworkmod/backup/*rom name (date and time usually)/
See if there is a nandroid.md5 file in there. If so, delete it, you can back it up if you want but it is busted so no point.
Next step to open adb shell or terminal emulator and type:
Code:
su
cd /sdcard/clockworkmod/backup/*rom name (date and time usually)/
md5sum *img > nandroid.md5
reboot recovery
Click to expand...
Click to collapse
Toggle signature works for me alot
Sent from my SAMSUNG-SGH-I727 using XDA
Not totally sure that I'm correct but I had made two backups on one version of cwm and then upgraded my cwm to the touch version and the two backups from the previous version wouldn't restore because of md5 mismatch. Those same two backups had worked several times perfectly on the other version of cwm as well. So I just assumed that maybe the version change had something to do with it.
Sent from a payphone at the quick-e-mart down the street from you
hcyplr29 said:
Trying to restore a stock backup in cwm. I get md5 mismatch error. Cause/solution inquiry.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
If you renamed backup directory to one w spaces... that too will give md5 err. Rename without spaces
Sent from my SAMSUNG-SGH-I727 using xda premium
Just flashed cwm touch from another recovery before trying to flash new rom zip and md5 mismatch accured...after darkwipe..dang..that was close call....think your correct with the change theory...
Sent from my SAMSUNG-SGH-I727 using XDA
Yes
yes that wass the problem. Tnk you NO spaces on backup folder name.
Tnk s
mindmajick said:
If you renamed backup directory to one w spaces... that too will give md5 err. Rename without spaces
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
hisham027 said:
You can actually manually do it, and maybe get that backup fixed. Go to the backup folder /sdcard/clockworkmod/backup/*rom name (date and time usually)/
See if there is a nandroid.md5 file in there. If so, delete it, you can back it up if you want but it is busted so no point.
Next step to open adb shell or terminal emulator and type:
Code:
su
cd /sdcard/clockworkmod/backup/*rom name (date and time usually)/
md5sum *img > nandroid.md5
reboot recovery
Click to expand...
Click to collapse
Worked perfect, thanks
adb Problem
Hey Guys,
nice tutorial. Everything worked but the adb shell itself.. I had to type all in one command. My adb shell freezed after entering the second command. Anybody knows how to fix it?
I used SiyahKernel S2-v3.4.1 and the ADB Shell in the Recovery.
funatkill said:
Hey Guys,
nice tutorial. Everything worked but the adb shell itself.. I had to type all in one command. My adb shell freezed after entering the second command. Anybody knows how to fix it?
I used SiyahKernel S2-v3.4.1 and the ADB Shell in the Recovery.
Click to expand...
Click to collapse
Isn't that for the international gs2?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
funatkill said:
Hey Guys,
nice tutorial. Everything worked but the adb shell itself.. I had to type all in one command. My adb shell freezed after entering the second command. Anybody knows how to fix it?
I used SiyahKernel S2-v3.4.1 and the ADB Shell in the Recovery.
Click to expand...
Click to collapse
Try using terminal emulator from your device
ADB Shell
Yeah, it is the international i9100, but the way to fix a broken CWM-backup is the same. I've tested an cm10 alpha and after this I wanted to restore my ICS, because of sdcard problems. So I did a fullwipe and only have had the Recovery left. How can I get a Terminal in there?
I thought about another way to fix the MD5: Maybe its possible to do a MD5Sum within windows over the boot.iso and save it to a .md5-file. You have to format the md5-file the way CMW needs it: "MD5sum /sdcard/.../boot.iso". Would this work properly?
funatkill said:
Yeah, it is the international i9100, but the way to fix a broken CWM-backup is the same. I've tested an cm10 alpha and after this I wanted to restore my ICS, because of sdcard problems. So I did a fullwipe and only have had the Recovery left. How can I get a Terminal in there?
I thought about another way to fix the MD5: Maybe its possible to do a MD5Sum within windows over the boot.iso and save it to a .md5-file. You have to format the md5-file the way CMW needs it: "MD5sum /sdcard/.../boot.iso". Would this work properly?
Click to expand...
Click to collapse
Not sure if it will work or not. Try to follow the steps given in the following thread and also just incase you may need it make a copy of the backup folder. 20 seconds tutorial to fix MD5 mismatch error no terminal needed
hisham027 said:
Not sure if it will work or not. Try to follow the steps given in the following thread and also just incase you may need it make a copy of the backup folder. 20 seconds tutorial to fix MD5 mismatch error no terminal needed
Click to expand...
Click to collapse
I fixed my md5 with the adb shell.. but I had to do this in one command . After reading this tut, I think there only has to be the MD5 of *.img, not of the .tar. Am I right?
Maybe its possible to script a zip-file for CWM which recalculates the MD5 of existing Backups?
The bash commands are simple. You only have to do this in a loop for all folders in /sdcard/clockworkmod/backup.
Here is a dump of my /system/app and /system/framework that is deodexed/zipaligned. Its just the directories; its not flashable in CWM. I'll try and put together a stock zip later, but I don't have time at work. If someone else wants to do it, feel free to PM me a link and I'll host it.
For now, developers will know how to use this. In addition, if you feel brave, you can use the following steps:
Prework:
Download the zip. Extract it. Copy the deodex_app and deodex_framework directories to your external SD card.
1) Boot your phone into recovery
2) Mount /system and /sdcard from the mount menu
3) adb shell rm /system/app/*.odex
4) adb shell rm /system/framework/*.odex
5) adb shell cp /sdcard/deodex_app/* /system/app/
6) adb shell cp /sdcard/deodex_framework/* /system/framework/
7) adb shell chmod 644 /system/app/*
8) adb shell chmod 644 /system/framework/*
9) Wipe Dalvik cache from the advanced menu
10) Make sure /system, /data, and /sdcard are unmounted in the mounts menu
11) Reboot. It took about 5 minutes for my phone to boot and then it said "Upgrading Android" or something like that and went through 175 apps or so.
Download here.
ROM developers, feel free to use this to base your ROMs on. Please give credit for the base source of your ROM as always.
Edit: Clarified its also zipaligned.
Awesome!! I wish I was brave enough to try this..
So rom does this mean you'll be whippin up a kernel?? : ))))))
Sent from my SAMSUNG-SGH-I727 using xda premium
pingfl00d said:
So rom does this mean you'll be whippin up a kernel?? : ))))))
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I need the source which is not available yet. I suspect it will be shortly after this is OTA'ed. But yes, once it is, I will be updating my stock-ish
Procedure works perfectly.
At "Android is upgrading... " message now
Edit: Home button dead.
rjohnstone said:
Procedure works perfectly.
At "Android is upgrading... " message now
Edit: Home button dead.
Click to expand...
Click to collapse
My home button works fine. This seems to be a common problem if you restore with TiBu. Did you do that?
romracer said:
My home button works fine. This seems to be a common problem if you restore with TiBu. Did you do that?
Click to expand...
Click to collapse
Only user apps, no system data.
And the button worked prior to replacing files, so I'm curious what was deleted/changed that caused the button to stop working?
rjohnstone said:
Only user apps, no system data.
And the button worked prior to replacing files, so I'm curious what was deleted/changed that caused the button to stop working?
Click to expand...
Click to collapse
My guess would be something that "Android is updating..." did. I'm still not entirely sure what that is doing.
romracer said:
My guess would be something that "Android is updating..." did. I'm still not entirely sure what that is doing.
Click to expand...
Click to collapse
Most likely... no biggie.
Factory reset should take care of it.
Worst case, I have a nandroid backup.
Edit: factory reset didn't fix it... time for a restore.
I will try and add this too a zip. Thank you
EDIT:
I added this to my ROM. I am still working on ironing out all of the issues, but this helped!
http://forum.xda-developers.com/showthread.php?t=1566820
And if you want to mirror that would be amazing.
that actually worked perfectly! although you should probably add in there that people can use emmc instead of sdcard if they dont have an external card (i dont).
Thanks for this.
Sent from my SAMSUNG-SGH-I727 using xda premium
thanks
I waiting for .Zip flasheable
if you don't mind me asking, how did you come across deodexing this rom? I know others were having troubles doing so. Also how did you zipalign it? I zipaligned my leak by using rom toolbox pro, did you use the kitchen?!?!
Thanks romracer, always run into issues with the kitchen. I'm going to try your classpath includes in a sh script and see if it works where the kitchen hadn't.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2 Beta-4
mjwhirly said:
if you don't mind me asking, how did you come across deodexing this rom? I know others were having troubles doing so. Also how did you zipalign it? I zipaligned my leak by using rom toolbox pro, did you use the kitchen?!?!
Click to expand...
Click to collapse
I do most of it by hand. I'm a Linux/Windows System Administrator by day, so I'm comfortable with the command line I do use Cygwin for just about everything though rather than the Command Prompt.
promiseofcake said:
Thanks romracer, always run into issues with the kitchen. I'm going to try your classpath includes in a sh script and see if it works where the kitchen hadn't.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2 Beta-4
Click to expand...
Click to collapse
The one liner I pasted in the other thread should work for both app and framework. It has more includes in the class path than are necessary for framework, but I don't think it'll break it.
It assumes the following:
You are in a directory with app, framework, deodex_app, deodex_framework and tmp subdirectories. app and framework contain the originals from the phone. The one liner should be run from this top level directory. I'd recommend doing framework first. You'll also need to Google java.awt.jar and put it in the framework directory too. Don't upload this to your phone though, its just needed for deodex'ing.
finally abit stable with these deodexed files
flash ics leak through odin
boot into android and get past the attready2go
flash cwm through odin
copy your deodexed files to sd and boot into cwm
follow your adb commands to copy and replace
reboot
only problems were superuser being a pain to flash in cwm. someone else mentioned toggle signature verification which is just before choosing your zip to install in cwm. looks good now.
mjwhirly said:
if you don't mind me asking, how did you come across deodexing this rom? I know others were having troubles doing so. Also how did you zipalign it? I zipaligned my leak by using rom toolbox pro, did you use the kitchen?!?!
Click to expand...
Click to collapse
i think the problem most people are having isnt related to the deodexing (anymore) but trying to flash it in CWM. it seems that flashable zips are messing up everything, as i used the same files i tried flashing in a zip this way and it works now. the zip version was unusable.
quikt said:
finally abit stable with these deodexed files
flash ics leak through odin
boot into android and get past the attready2go
flash cwm through odin
copy your deodexed files to sd and boot into cwm
follow your adb commands to copy and replace
reboot
only problems were superuser being a pain to flash in cwm. someone else mentioned toggle signature verification which is just before choosing your zip to install in cwm. looks good now.
Click to expand...
Click to collapse
That's basically exactly what I did (and my phone seems stable). Thanks for typing out the parts I left out
I've always had to flash the Superuser zip twice for some reason. I just flash it twice right on top of each other (without rebooting, exiting CWM, etc). Never have any problems in the actual OS doing it that way.
Grab the official Superuser zip from goo-inside.me/superuser
EDIT: I solved my own problem. Scroll down to post #8 for the solution.
My problem was that my phone (T-Mobile USA HTC One S) would not boot into ICS anymore, but I was still able to get into recovery (CWM), yet I had no access to the sdcard ("unable to mount /sdcard").
Post #8 below tells you how you can restore access to the sdcard in CWM so that you can push a ROM zip file to the sdcard via adb.
-J
Have you made any nandroids? If you have maybe you can restore. Also check in the download file in cwm that is possible place where that file may be.
Sent from my myTouch 4G Slide using xda premium
archie53 said:
Have you made any nandroids? If you have maybe you can restore. Also check in the download file in cwm that is possible place where that file may be.
Sent from my myTouch 4G Slide using xda premium
Click to expand...
Click to collapse
Unfortunately I didn't have the foresight to make a nandroid backup. My previous phone was a Samsung Galaxy S 4G, which, like most Android phones, has a removable SD-Card that stuff can be copied onto (and then flashed). Not so here obviously.
Is it even possible to push files to the sdcard using the method I tried when in CWM?
When you push the file via ADB, have you tried placing it into a folder that you know is on the /sdcard?
joshnichols189 said:
When you push the file via ADB, have you tried placing it into a folder that you know is on the /sdcard?
Click to expand...
Click to collapse
It just got worse. I got the idea to format all partitions (data, system, cache, sdcard) through CWM, and now CWM can't even mount /sdcard/ anymore...
I had to do the same thing:
adb push "NameOfFile.zip /sdcard
then go to install from zip.
Look on sd card and it will be there.
I always rename the zip files to there can be less errors.
you can also do
adb shell pull "nameOfFile.zip /sdcard
make sure the zip file is where your adb and fastboot is
My problem is CWM can't mount the /sdcard directory, so I can't flash the new OS. Is there anybody that knows how to recover from that problem?
LuckyMethod said:
My problem is CWM can't mount the /sdcard directory, so I can't flash the new OS. Is there anybody that knows how to recover from that problem?
Click to expand...
Click to collapse
Yes, I just fixed my problem yesterday after some serious trial-and-error.
1) Use the All-in-One-Kit and flash your recovery back to stock
2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.
3) Go back to the all-in-one-kit and flash a CWM recovery version again.
4) Reboot into recovery (CWM). Your /sdcard should now be mounted and visible.
5) Now, try the UTB rom (it worked for me), rename the zip file to something short (i.e. utb.zip), and push it to the sdcard using adb as follows:
Code:
adb push utb.zip /sdcard
6) While still in CWM, flash the zip.
The trick here is that only the stock recovery is capable of restoring access to the sdcard by it's proprietary "clear storage" option.
Good luck!
-J
If that doesn't work an easy fix is boot into bootloader, goto fastboot and use "fastboot flash boot boot.img" and so fouth. In the dev section I seen a stock tmobile naindroid. Download it and you'll have your data.img and boot.img. You should be able to flash them without needing to push to /sdcard. letme know how it works
I know you fixed this already just thought this still might help
cannondale0815 said:
Yes, I just fixed my problem yesterday after some serious trial-and-error.
1) Use the All-in-One-Kit and flash your recovery back to stock
...cut...
-J
Click to expand...
Click to collapse
It worked like a charm, thank you very much. You saved my life, I was in a time crunch.
LuckyMethod said:
It worked like a charm, thank you very much. You saved my life, I was in a time crunch.
Click to expand...
Click to collapse
Happy it worked for you. Took me several days to figure this out
Sent from my HTC One S using xda premium
I too formatted my sd card but a little trial and error and using your direction, I am back in business ! Thank you , this should really be a sticky
Sent from my HTC VLE_U using xda premium
j3.cole said:
I too formatted my sd card but a little trial and error and using your direction, I am back in business ! Thank you , this should really be a sticky
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
Thank you. I changed the title and original post to make it easier for people to find this thread.
I am going to try this trick tomorrow after having spent endless hours trying to fdisk/parted via adb, and flashing endless roms and updates to no avail. I will post the outcome here. I really hope this works for me like it has for you guys...
mrmoretti said:
I am going to try this trick tomorrow after having spent endless hours trying to fdisk/parted via adb, and flashing endless roms and updates to no avail. I will post the outcome here. I really hope this works for me like it has for you guys...
Click to expand...
Click to collapse
IT WORKED! This thread should be made sticky! I'm sure a lot of users who have HTC One S with built-in SD will have the same issue when mucking about with their phone. Thank you!
Bump, as too many people are having this problem.
Sent from my HTC One S using Tapatalk 2
cannondale0815 said:
Yes, I just fixed my problem yesterday after some serious trial-and-error.
1) Use the All-in-One-Kit and flash your recovery back to stock
2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.
3) Go back to the all-in-one-kit and flash a CWM recovery version again.
4) Reboot into recovery (CWM). Your /sdcard should now be mounted and visible.
5) Now, try the UTB rom (it worked for me), rename the zip file to something short (i.e. utb.zip), and push it to the sdcard using adb as follows:
Code:
adb push utb.zip /sdcard
6) While still in CWM, flash the zip.
The trick here is that only the stock recovery is capable of restoring access to the sdcard by it's proprietary "clear storage" option.
Good luck!
-J
Click to expand...
Click to collapse
THANK YOU SO MUCH! THIS WORKED PERFECTLY!
This should definitely be included in a stickied guide for people like me who have managed to corrupt their recoveries.
Got it after several tries
hey guys i have the same problem, the solution sort of work, but when i try to do a adb push its show it was sucessful but when i do to flash it i cant see it.
yasir_jan87 said:
hey guys i have the same problem, the solution sort of work, but when i try to do a adb push its show it was sucessful but when i do to flash it i cant see it.
Click to expand...
Click to collapse
Try to shorten the filename, i.e. "rom.zip".
And try this slightly modified command instead:
adb push rom.zip /sdcard/rom.zip
Sent from my aokp_tenderloin using Tapatalk 2