Related
there are a number of problems with the recovery in the just leaked
Froyo ROM.
1. signature checking
2. passing API version 3 to the updater binary
3. forced wipe after installing an update.zip
the attached zip has a 3e recovery modified to disable signature checking
report API version 2 for backwards compatibility with clockwork mod recovery
and disable the forced wipe after installing any update.
I don't know of any reason to run this version over 2e but it
might be useful to someone.
Installing:
1. turn on USB debugging
2. plug into computer
3. run script and follow on screen prompts.
UPDATED 01/23/2011
fixed path error when space in user name
UPDATED 01/22/2011
compressed the rageagainstthecage resource to prevent anti-virus detection
new anti-virus report
http://virscan.org/report/8e83f338fd7b8631c6b0bc0679efbd29.html
the /system file system is full on the newer ROM's
use the attached update.zip to root then install clockwork
Nice
Sent from my SGH-T959 using XDA App
ummmm... what attached zip?
kuhan said:
ummmm... what attached zip?
Click to expand...
Click to collapse
forgot to upload it.
kuhan said:
ummmm... what attached zip?
Click to expand...
Click to collapse
The one attached to the message(?)
fearmonkey said:
The one attached to the message(?)
Click to expand...
Click to collapse
yeah, he attached it after that post lol
how do you use this?
ok i wil bite. how do you use/flash this it cw is not accesible?
rename to update.zip i assume...... i mean thats how u flash everythign thats zip file if u cant get into clockwork.....
you cant flash this you will have to put the files on the internal sdcard
then use root explorer or adb to move the files into place, recovery goes to
/system/bin and the keys to /efs, update.zip is the clockwork recovery and
stays on the sdcard.
when you boot into recovery and choose re-install packages clockwork will
be able to do its thing.
I do like the sig verification but it's a PITA and may disable it, this is a temp
fix until I can finish hacking on recovery there is very little clues as to where
the functions are so it may be a few days.
forgot to mention to you also have to remount /system rw
mount -o rw,remount /dev/block/stl9 /system
Be-ware. Doing so on the ODIN 2E version will break Recovery all together.
Fine to replace on the Stock 2.2 ..
Ps.
Another Awesome Job untermensch
Not to sound like a total noob, but what benefit does this have over the current 2e recovery?
option94 said:
Not to sound like a total noob, but what benefit does this have over the current 2e recovery?
Click to expand...
Click to collapse
I haven't tried just replacing 3e with 2e, I doubt there is any advantage to
3e, to us anyway. but it is always worth while to find ways around these
things.
EDIT:
just replacing 3e with 2e did not work cant find the update.zip
Im suprised more people havent commented. I downloaded the first Stock version of JK2 and i tether so redownloading is not really what i wanted to do...plus i have a Mac so Id have to borrow my buddys pc again...anyway
This workedvgreat! For thise who might need it:
Place all files on the root of SD internal memory card
Copy keys file to /efs
Copy recovery file to /system/bin/ (backup old on first)
Leave all other files on SD internal
Reboot into stock recovery and select Reinstall Packages
itll do its thing and reboot into stock recovery again. From there youre set...just select reinstall packages each time.
Youre a life saver...thank you sir!
TJD319 said:
Im suprised more people havent commented. I downloaded the first Stock version of JK2 and i tether so redownloading is not really what i wanted to do...plus i have a Mac so Id have to borrow my buddys pc again...anyway
This workedvgreat! For thise who might need it:
Place all files on the root of SD internal memory card
Copy keys file to /efs
Copy recovery file to /system/bin/ (backup old on first)
Leave all other files on SD internal
Reboot into stock recovery and select Reinstall Packages
itll do its thing and reboot into stock recovery again. From there youre set...just select reinstall packages each time.
Youre a life saver...thank you sir!
Click to expand...
Click to collapse
thanks...
just updated the first post with a new version.
whats new
Code:
dissables forced post install wipe, dissables signature checking, and reports
API version 2 for backwards compatability with clockwork mod recovery.
Thanks man i rreally appreciate this like i said before. Working perfect snd no issues. Loving being able to CWM again ha. Anyway thank you again sir keep it up!
TJD319 said:
Im suprised more people havent commented. I downloaded the first Stock version of JK2 and i tether so redownloading is not really what i wanted to do...plus i have a Mac so Id have to borrow my buddys pc again...anyway
This workedvgreat! For thise who might need it:
Place all files on the root of SD internal memory card
Copy keys file to /efs
Copy recovery file to /system/bin/ (backup old on first)
Leave all other files on SD internal
Reboot into stock recovery and select Reinstall Packages
itll do its thing and reboot into stock recovery again. From there youre set...just select reinstall packages each time.
Youre a life saver...thank you sir!
Click to expand...
Click to collapse
Thanks untermensch for your work and thanks to the TJD319 for the clear step by step instructions.
Getting can't mount partition after I select a zip file to flash. I can get to cwr fine and it sees the sdcard (internal) fine since I can navigate and select the file I want. The error comes when I try flash. All the files in the zip are in the root of the sd internal, except for recovery and keys that are in the directory /system/bin and /efs respectively. Any advice?
untermensch said:
thanks...
just updated the first post with a new version.
whats new
Code:
dissables forced post install wipe, dissables signature checking, and reports
API version 2 for backwards compatability with clockwork mod recovery.
Click to expand...
Click to collapse
I personally want to say Thanks for Working on this... I Honestly like this version better than the 2e due to being able to wipe the SD-card now..
Thanks for everything.
eugene373 said:
I personally want to say Thanks for Working on this... I Honestly like this version better than the 2e due to being able to wipe the SD-card now..
Thanks for everything.
Click to expand...
Click to collapse
Thanks for the support Eugene....
updated the no sig check version again, too fix the issue that even though the key
is never used, recovery still looked for the existence of the file and would error out if not found.
untermensch said:
Thanks for the support Eugene....
updated the no sig check version again, too fix the issue that even though the key
is never used, recovery still looked for the existence of the file and would error out if not found.
Click to expand...
Click to collapse
Yo man i really appreciate your work. Froyos been great to me Stock 2.2 and this is perfect man. Working flawlessly for me and Im just happy to be able to nandroid.
Here are the Steps I took to convert the data folder to ext 2. I'm sure we can do more folders but I'm unable to write (anyone?) the update scripts.
Start with a fresh install of Team Whiskey's Rom
Goto to the I9000 thread and follow the instruction on uploading a kernel to be repacked.
I selected all the check marks before re packing and downloaded the new kernel.
Download the ext2 update zip from the thread. Rename the zip file to update.zip.
Grab the kernel(tar file) you downloaded from the site and use odin to install.
After booting back up rename the z4mod.ext2.update zip file to update.zip.
Reboot into clockwork and apply update.zip
After booting back up your data file should now be ext2.
To check use terminal emulator our adb and type mount. The data line should now say ext2 instead of rfs.
Note: When I tryed to use the ext2 update zip file without renaming to update.zip it did not work. I continuously recieved SD mount errors.
I can't stress enough to read the topic in the I9000 development thread titled z4mod breaking free from rfs(link below) so you understand what you are doing and the process that is required.
My instruction does not detail that whole process. I'm not responsible for you or what you do by following this brief instruction.
Very Snappy after this mod. Absolutely no issues for me.
Quadrant = 1700
Enjoy!!!
Credit goes to RyanZA and the z4ziggy ; not me.
Source: [z4mod] Breaking free from RFS [Stage II - version 0.3 Alpha - With online patcher!]
Files I used to get this to work.
zImage.tar (The Zimage I used to repack was taken out of Obsidian V2. (DO NOT USE THIS FOR IMAGE FOR ANY OTHER ROM THAN OBSIDIAN V2)
Also, XDA does not allow uploads of tar files so I compressed the tar into a zip format. Make sure you extract this file and use the .tar file within Odin.
Update.zip - This file was downloaded from the I9000 Z4Mod Thread entitled z4mod.ext2.update.zip. All I did was renamed to update.zip which for some reason allows this conversion process to take place.
Sent from my SGH-T959 using XDA App
I would highly suggest posting links to the threads you refer to as well as any files you have available. Good post though, I plan on using this.
Sent from my SGH-T959 using XDA App
Thanks - 1632 Quadrant on Onyx 2.2
Does your kernel have the stock or clockwork recovery? Easy way to check is do adb reboot recovery. If it goes into clockwork then the stock recovery was replaced.
The file you attached is ready to use or do we need to repack?
Greenarcher707 said:
The file you attached is ready to use or do we need to repack?
Click to expand...
Click to collapse
Ready to use.
Sent from my SGH-T959 using XDA App
Ashex1 said:
Does your kernel have the stock or clockwork recovery? Easy way to check is do adb reboot recovery. If it goes into clockwork then the stock recovery was replaced.
Click to expand...
Click to collapse
I'm using cwm. But I could not use "select zip option" you can try it though.
Sent from my SGH-T959 using XDA App
Bugger, from what I know ClockworkMod has some compatibility issues with JK2 unless the version that z4build uses is compatible.
Great, this broke busybox. Now I'm in 2.2 w/o root...
Xencer said:
Great, this broke busybox. Now I'm in 2.2 w/o root...
Click to expand...
Click to collapse
Use Titanium Backup to fix busybox.
Is there one for ext4?
funkyu00 said:
Is there one for ext4?
Click to expand...
Click to collapse
Seconded. It'd be great to get /dbdata, /cache, /system onto ext4 too (I thought that was the main benefit of z4mod?)
jamesyl said:
Seconded. It'd be great to get /dbdata, /cache, /system onto ext4 too (I thought that was the main benefit of z4mod?)
Click to expand...
Click to collapse
Unlikely as the kernel does not support Ext4.
Also, to anyone who has tried this: Is the kernel from the op already patched? I tried throwing it into the the online patcher and the patcher just spit out a message informing me that what I uploaded was already patch. However, when I jump into recovery, I get recovery 2e and not clockwork, which leads me to believe otherwise.
Perhaps odin did not actually install it?
how did u boot into clockwork? 3 button or through rom manger? it doesnt work for me with three button still says can not mount
hoipefully someone adds to the script so it can convert more partitions.
How did you get into Clockwork recovery if you replaced the update.zip file the stock recovery uses to get into it?
I booted through RomManager. It gave the little green Android dude with the download box and got right into recovery. Working great so far.
RobBull69 said:
I booted through RomManager. It gave the little green Android dude with the download box and got right into recovery. Working great so far.
Click to expand...
Click to collapse
Yes, I figured out that the Z4 patch kernel replaces the stock recovery with clockwork.
kangxi said:
How did you get into Clockwork recovery if you replaced the update.zip file the stock recovery uses to get into it?
Click to expand...
Click to collapse
the way this phone is set up has the recovery image packaged with the kernel in the file called zImage. when u use the z4mod to modify that zImage file, the website unpacks the whole zImage file, does its thing with the kernel modding, and now (i say now because this is a newer feature) replaces the standard 2e recovery with clockwork recovery. when you flash the zImage, whether repackaged in a rom or as a tar in odin, the new clockwork recovery is flashed to '/system/bin/recovery' replacing the 2e recovery. i have confirmed this by running the command 'recovery' from terminal while booted after flashing a z4modded kernel. i do not recommend trying to run recovery while booted as the phones display started going crazy.
the problem with having clockwork mod as the primary recovery is the fact that there is a major issue with mounting both the internal sd and external sd (even one at a time as well as both together) as clcokwork mod reports it doesnt recognize device at 'mmcblk0' or 1 when clockworkmod recovery is the primary recovery.
jmart211in said:
the problem with having clockwork mod as the primary recovery is the fact that there is a major issue with mounting both the internal sd and external sd (even one at a time as well as both together) as clcokwork mod reports it doesnt recognize device at 'mmcblk0' or 1 when clockworkmod recovery is the primary recovery.
Click to expand...
Click to collapse
That's why I backed out of it and went back to the stock kernel - that and the fact there was a weird flicker at the top of the screen when booting.
because usb port of my phone not working, its only charging. How to root my phone without connect it to pc? (like z4root.apk, I've try z4root and gingerbreak but it doesnt work) Anything help?
I think a preroot rom which can be flash with stock recovery does it so anybody make for me a preroot rom like firmware.nb0 so i can try it by stock recovery pleasezz!
dtbang721 said:
because usb port of my phone not working, its only charging. How to root my phone without connect it to pc? (like z4root.apk, I've try z4root and gingerbreak but it doesnt work) Anything help?
I think a preroot rom which can be flash with stock recovery does it so anybody make for me a preroot rom like firmware.nb0 so i can try it by stock recovery pleasezz!
Click to expand...
Click to collapse
hi
if u have CWM then down load the RC2 put it on root of ur SD
and flash it via CWM RC2 is pre rooted
dtbang721 said:
because usb port of my phone not working, its only charging. How to root my phone without connect it to pc? (like z4root.apk, I've try z4root and gingerbreak but it doesnt work) Anything help?
I think a preroot rom which can be flash with stock recovery does it so anybody make for me a preroot rom like firmware.nb0 so i can try it by stock recovery pleasezz!
Click to expand...
Click to collapse
refer to this thread
http://forum.xda-developers.com/showthread.php?t=1268695
parrkhi had explaind it well
or else go to this thread directly
http://forum.lowyat.net/topic/1985476
here loock down for the clockwork mode method
u can download these zip files directly to ur phone jst keep them in root folder
Always click thankx if u find it useful
here is the mediafire link for .zip files that u need for all this work.
http://www.mediafire.com/?evfo2dlq9m92w
go to this link download file ( i consider u have cwm already installed on your phone) if u dont have cwm dont worry give it a try in this link u will find a .zip file named as recovery,..zip jst rename it to update.zip and install it from recovery menu// u can also give this update thing a try with the su.zip files file are main for rooting
Thanks for reponse. But I mention that my phone cant connect to pc, I've tried it alot, I cant connect my phone to pc in download mode so I cant instant cwm. everything I can try is self root apk or flash a rooted rom with base stock recovery.
okk if u cant flash cwm then its quite troubling
if ur usb dosn't work why don't u rush to the service center they will solve this problem in say 15 to 20 mins... better go there and get it serviced ...
Not possible yet without getting it in download mode...
dtbang721 said:
Thanks for reponse. But I mention that my phone cant connect to pc, I've tried it alot, I cant connect my phone to pc in download mode so I cant instant cwm. everything I can try is self root apk or flash a rooted rom with base stock recovery.
Click to expand...
Click to collapse
vibhor15 said:
Not possible yet without getting it in download mode...
Click to expand...
Click to collapse
Well you can do that. I mean you can install CWM recovery without connecting your device via USB.
If you can download CWM recovery or Recovery menu directly on your device, follow these instructions.
Extract recovery.img file from downloaded zip file.
Keep it in sdcard's root directory. (/sdcard/recovery.img)
Now copy following commands and save it as Install_recovery.sh in your sdcard's root directory
Code:
#!/system/bin/sh
mkdir /sdcard/fih
mount -t vfat /dev/block/mmcblk0p1 /sdcard/fih/
cd /sdcard/fih/image/
mv /sdcard/fih/image/recovery.img ./recovery.img
cd /
umount /sdcard/fih
rm -r /sdcard/fih/
And use any script manager or Terminal emulator to run this file.
Using terminal emulator:
Code:
cd /sdcard/
sh Install_recovery.sh
Now boot into recovery. You should boot into new recovery.
P.S. Similar How-To is also posted in a thread: Restoring stock recovery: (without Download mode). I have just modified it a bit.
Thanks! I'll give it a try. But does Script manager and terminal emulator is a apk that i can install and use to run the command saved in Install_recovery.sh?
So that I run terminal emulator apk and type
"cd /sdcard/
sh Install_recovery.sh" ?
ok. I've tried but the emulator report errors. I think I must have rooted phone to install cwr with your solution. The error is
$ export PATH=/data/local/bin:$PATH
$ cd /sdcard/sh install_recovery.sh
cd: bad substitution
$ cd /sdcard/
$ sh install_recovery.sh
, Invalid argumentsdcard/fih
mount: No such file or directory
cd: can't cd to /sdcard/fih/image/
failed on '/sdcard/fih/image/recovery.img' - No such file or directory
cd: can't cd to /
failed.
rm failed for /sdcard/fih/, No such file or directory
$
So how do I get cwr on my phone to root it via cwr method?
dtbang721 said:
ok. I've tried but the emulator report errors. I think I must have rooted phone to install cwr with your solution. The error is
$ export PATH=/data/local/bin:$PATH
$ cd /sdcard/sh install_recovery.sh
cd: bad substitution
$ cd /sdcard/
$ sh install_recovery.sh
, Invalid argumentsdcard/fih
mount: No such file or directory
cd: can't cd to /sdcard/fih/image/
failed on '/sdcard/fih/image/recovery.img' - No such file or directory
cd: can't cd to /
failed.
rm failed for /sdcard/fih/, No such file or directory
$
So how do I get cwr on my phone to root it via cwr method?
Click to expand...
Click to collapse
Oh yes! I forgot.
Will try to come up with an answer as soon as possible.
Sent from my CSL-MI410 using XDA App
dude ... do you have a memory card reader ...???
if u have a card reader then jst remove ur card from phone plug into pc copy all the files i.e cwm recovery update.zip and su.zip
[Installation Instructions]
[Using CWM recovery]
Copy CWM recovery-fb0-v5_signed.zipin sdcard
Boot into recovery (Steps are given below for how-to-boot-into-recovery)
Use "install zip from sdcard" option
Locate and choose CWM recovery-fb0-v5_signed.zip from sdcard for instllation
After installation reboot into recovery (advanced > Reboot recovery)
i suggest rename the .zip file to update.zip
and then follow rooting instruction
I mean that I've got a stock rom without root. So I havent CWM recovery installed on my phone.
My usb hub on my phone has broken and the phone waranty service not avainable in my country so I need a root solution without usb connecting.
As I know I need rooted phone first to install CWM recovery. Or I need a method to install CWM recovery by stock recovery.
I also try to flash back to 2.2 froyo version to root my phone by gingerbreak apk but not successed. When I try to flash any stock rom 2.2 or 2.3.4 the stock recovery allways report error and didnt worked. The error that stock recovery say is:
Enter lauch_image_update
Prepare failed rc= -209
PID doesnt match!
You cant download this nb0
Some error during preparing
So now I cant do anything with stock recovery only hardreset can done. No flash firmware.nb0 rom no update the update.zip
And when I try to flashing update.zip (CWM recovery-fb0-v5_signed_2.zip I renamed it to update.zip) stock recovery say error that:
verifying update package
E:signature verification failed
dtbang721 said:
I mean that I've got a stock rom without root. So I havent CWM recovery installed on my phone.
My usb hub on my phone has broken and the phone waranty service not avainable in my country so I need a root solution without usb connecting.
As I know I need rooted phone first to install CWM recovery. Or I need a method to install CWM recovery by stock recovery.
I also try to flash back to 2.2 froyo version to root my phone by gingerbreak apk but not successed. When I try to flash any stock rom 2.2 or 2.3.4 the stock recovery allways report error and didnt worked. The error that stock recovery say is:
Enter lauch_image_update
Prepare failed rc= -209
PID doesnt match!
You cant download this nb0
Some error during preparing
So now I cant do anything with stock recovery only hardreset can done. No flash firmware.nb0 rom no update the update.zip
And when I try to flashing update.zip (CWM recovery-fb0-v5_signed_2.zip I renamed it to update.zip) stock recovery say error that:
verifying update package
E:signature verification failed
Click to expand...
Click to collapse
There is still one option left.
You can create your own nb0 file (since thats the only option working), which has cwm recovery and rooted ROM.
Right now i am away from my work place so cant help you till next monday.
Sent from my CSL-MI410 using XDA App
I'm right here waitting!
dtbang721 said:
I'm right here waitting!
Click to expand...
Click to collapse
napstar is right make ur own .nb0 i m working on it too still no success having boot loops with usb when i flash it ... dont know why nd don't have plenty of time to log cat the problem ...
kshitij_bhatt said:
napstar is right make ur own .nb0 i m working on it too still no success having boot loops with usb when i flash it ... dont know why nd don't have plenty of time to log cat the problem ...
Click to expand...
Click to collapse
I have another android ( x10 mini pro) and I know that we can make a backup by stock recovery or cook a rom for flashing by stock recovery. But before public the rom the deverloper have to tested it because bootloop is the problem of flashing rom. So before flashing new rom we need do a hardreset and after flashing rom we also need a hard reset to solve boot looping problem.
because of brocken usb hub on my phone. I need tested before flashing. :'(
the test is:
1 make a nb0 file from a phone that working good.
2 try to flash nb0 by stock recovery to another phone to confirm that nb0 work good for all phone.
3 Note that some rom is working realy good for some phone but can make bootloop for another phone because of different keynell they are ussing or we dont make factory reset and do a wipe data and cache also get bootloop problem
nanana its not beautyfull life.
My First post...
dtbang721 said:
nanana its not beautyfull life.
Click to expand...
Click to collapse
Hi...
Are you sure that your phone has this usb problem? Not the usb cable?
I've an experienced with usb cable which has problem to connect, then I use blackberry usb data cable, then it works. My problem is the cable can't powered enough the phone to make data connection.
OR... you can flash Andro-ID RC1 first before other ROMs, which Andro-ID RC1 is the nb0 file (may be you can flashed it using stock recovery) and this RC1 is pre rooted and it has CWM recovery in it. Then you can use CWM to flash other zip based ROMs, including to update CWM it self to a newer version.
Hope it help....
Sorry if I missed understood of your problem! If you want to stay on WellCom 2.3.4 and rooted unwired, someone has to make update.zip with the su+superuser.apk and signed with appropriate key (FIH)
CacingKalung said:
Hi...
Are you sure that your phone has this usb problem? Not the usb cable?
I've an experienced with usb cable which has problem to connect, then I use blackberry usb data cable, then it works. My problem is the cable can't powered enough the phone to make data connection.
OR... you can flash Andro-ID RC1 first before other ROMs, which Andro-ID RC1 is the nb0 file (may be you can flashed it using stock recovery) and this RC1 is pre rooted and it has CWM recovery in it. Then you can use CWM to flash other zip based ROMs, including to update CWM it self to a newer version.
Hope it help....
Sorry if I missed understood of your problem! If you want to stay on WellCom 2.3.4 and rooted unwired, someone has to make update.zip with the su+superuser.apk and signed with appropriate key (FIH)
Click to expand...
Click to collapse
yes. that's my problems. Ill try to flash rc1. may be the problem is my usb cable. but i have not got any blackberry cable. I just have a stock cable and a sony erricson cable and a nokia cable. but none of them work.
CacingKalung said:
Hi...
Are you sure that your phone has this usb problem? Not the usb cable?
I've an experienced with usb cable which has problem to connect, then I use blackberry usb data cable, then it works. My problem is the cable can't powered enough the phone to make data connection.
OR... you can flash Andro-ID RC1 first before other ROMs, which Andro-ID RC1 is the nb0 file (may be you can flashed it using stock recovery) and this RC1 is pre rooted and it has CWM recovery in it. Then you can use CWM to flash other zip based ROMs, including to update CWM it self to a newer version.
Hope it help....
Sorry if I missed understood of your problem! If you want to stay on WellCom 2.3.4 and rooted unwired, someone has to make update.zip with the su+superuser.apk and signed with appropriate key (FIH)
Click to expand...
Click to collapse
dtbang721 said:
yes. that's my problems. Ill try to flash rc1. may be the problem is my usb cable. but i have not got any blackberry cable. I just have a stock cable and a sony erricson cable and a nokia cable. but none of them work.
Click to expand...
Click to collapse
Thats a good option. I thought you have already tried it and received an error saying "### ID mismatch"
Anyway if you have not downloaded it yet, then I have one other option for you. I have created an nb0 file which contains only CWM recovery and nothing else.
This file will install Recovery menu v2 which includes both CWM and stock recovery and no system files/data files.
To install, download attached file to your device and extract firmware.nb0 file from it. (For zip file extraction, you can use ES_explorer).
And then install it using your stock recovery.
After installation system will boot in your current ROM. Reboot into recovery and you will find recovery menu instead of stock.
Disclaimer: I am not an expert in creating nb0 file. Here I have just deleted all unnecessary files from stock nb0 file and replaced recovery image with recovery menu's image. So far this works on my device. I have tried it installing when I am on stock ROM. (Though it was not necessary)
I am not to be held liable/responsible if you damage your phone by following / not following this post.
MD5SUM hash code:
0b72eea3bc419bc66d64173df193a915 firmware.nb0
Doesn't meter what rom I Flash I get this error: http://imageshack.us/photo/my-images/823/img201207201510251.jpg/
I have copyed all files: parted, e2fsck etc and did what says on this post: http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/page__st__20 (number 23)
When im trying to parted, its just says: "no such file or directory" http://imageshack.us/photo/my-images/844/shell2.jpg/
If i try to format - i receiving such errors: http://imageshack.us/photo/my-images/801/img201207201436181.jpg/
http://imageshack.us/photo/my-images/841/img201207201437371.jpg/
please advice how to use parted?
Edit:
I have managed to open parted, but now i cant remove any partitions, after rm command its remains same.
http://img685.imageshack.us/img685/5201/printuo.jpg
How can i remove partitions?
Bezeq said:
Doesn't meter what rom I Flash I get this error: http://imageshack.us/photo/my-images/823/img201207201510251.jpg/
I have copyed all files: parted, e2fsck etc and did what says on this post: http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/page__st__20 (number 23)
When im trying to parted, its just says: "no such file or directory" http://imageshack.us/photo/my-images/844/shell2.jpg/
If i try to format - i receiving such errors: http://imageshack.us/photo/my-images/801/img201207201436181.jpg/
http://imageshack.us/photo/my-images/841/img201207201437371.jpg/
please advice how to use parted?
Edit:
I have managed to open parted, but now i cant remove any partitions, after rm command its remains same.
http://img685.imageshack.us/img685/5201/printuo.jpg
How can i remove partitions?
Click to expand...
Click to collapse
You do not need to remove any partitions... Just flash stock rom, and try again... Same happened to me, i couldnt mount any partition in recovery, now it fine
foggydisaster said:
You do not need to remove any partitions... Just flash stock rom, and try again... Same happened to me, i couldnt mount any partition in recovery, now it fine
Click to expand...
Click to collapse
I have tryed to flash many roms, 2.2.1 2.3.1 2.3.5 .2.3.6, (JVT, JVR, LPY, and new ones) always same issue: "E: failed to mount /data (invalid argument) and then bootlooping.
I`m sure my mmcblk0p2 is broken, question is how to force delete this partition or flash rom in to external SDcard!
Bezeq said:
I have tryed to flash many roms, 2.2.1 2.3.1 2.3.5 .2.3.6, (JVT, JVR, LPY, and new ones) always same issue: "E: failed to mount /data (invalid argument) and then bootlooping.
I`m sure my mmcblk0p2 is broken, question is how to force delete this partition or flash rom in to external SDcard!
Click to expand...
Click to collapse
Well you cant flash roms onto sdcard... But if your partition is broken, then sorry but im a noob
Sent from my GT-I9000 using xda app-developers app
Have you tired using a pit file?
flash a stock rom from samfirmware.com with ODIN.(eg. jw5)
to extract the password is "samfirmware.com"
tick repartition and use 512 pit file(included in rom from samfirmware).
check youtube for "flash with odin" if u dont know how.
edit:u are trying to flash from from samsungs 3 recovery.u need cwm(clockworkmod) to flash.
go to CF-ROOT(for i-9000) thread and follow instructions and read all in the OP(1-2-3 posts)
again u need ODIN to flash it.
hey
there is the best wasy to do that...just go to sammobile.com
there sign up first and then download the firmware (in firmware tab) and flash-programs...
the make sure to use oidn3_v1.0 only...
you can also download the flash-guide if you need it...
its simple..:laugh:
Thanks to everyone for replays, but nothing helped me x_x
if i flash 2.2.1 or 2.3.6 i receiving this error:
https://www.box.com/s/4d4b108a0246f9f56c7c
If i flash 2.3.3 or 2.3.4:
https://www.box.com/s/f09fd945620c03daffa9
And then it keep showing me GT 9000 logo......
yes i used 512pit and using 1.82 odin
I know there is way to install in to external SDcard: http://www.youtube.com/watch?v=zdMhYYdMB08
I had such error and successfully installed rom in to sdcard but i had issue with phone signal, so tried to re install rom and now its keep teling me cant mount data..
What can i do?
Hello,
Did you try this http://forum.xda-developers.com/showthread.php?t=984140 ?
mystic324 said:
Hello,
Did you try this http://forum.xda-developers.com/showthread.php?t=984140 ?
Click to expand...
Click to collapse
Yep, keep shows only gt-9000 logo..
I had a very similar problem earlier this year.
From what I could see the partitions on the phone's internal storage weren't able to be accessed. In adb I tried using parted and rm but the partitions there (/dev/block/mmc/blk0) didn't ever change. I also tried various .pit files and Android versions through Odin but nothing worked.
I took my phone in for repairs after flashing a really old version; as close as possible to what it came with, and they fixed it. The repair was due to 'mechanical fatigue' according to them. I assumed the internal storage was some how broken or corrupted and couldn't be written to.
Not sure, if you manage to solve this.
From you screenshots I can see you are using 3e recovery. I would suggest you to flash a kernel which support cwm recovery mode.
I have heard peoples getting this error while using it on 3e.
Captain_17
Yes Captain_17, i have exactly same problem, cant give it to repair since purchased it from abroad.
erpurohit said:
Not sure, if you manage to solve this.
From you screenshots I can see you are using 3e recovery. I would suggest you to flash a kernel which support cwm recovery mode.
I have heard peoples getting this error while using it on 3e.
Click to expand...
Click to collapse
3e recovery because i`ve flashed 2.2 and 2.2.1 or any other official roms, i can flash CWM easy but as Captain_17 said i can see but cant touch
files or partitions.
If flash CWM then phone will boot to CWM only, and i cant flash any rom from CWM because i cant copy files to internal storage and external (sdcard) cwm doesn't see it.
Sorry man, wish I could be of more help. I tried every available option I could find online but nothing worked.
Seems to be a hardware problem and replacing the damaged part is the only solution.
Silly question, but you ticked re-partition? try flash 2.2.1 or 2.3.3 with 512 pit and repartition
Also, you could try to flash Darky ressurection via odin, not completely stock rom. I know that this is just tweaked stock, but you could try do that.
And, you could try to use Heimdall instead of odin - http://forum.xda-developers.com/showthread.php?t=1196179
I have read somewhere that heimdall is more preferable than odin in some cases.
Bezeq said:
Yep, keep shows only gt-9000 logo..
Click to expand...
Click to collapse
I once also a similar problem and flash2.1 Eclayr. But then I had to restore recowery to flash. as with you, I do not know if it helps.
Hello
I've tried installing guestekrnL on WIUI. When installing guestekrnL, the only thing I've ticked extra that was other than defaults was:
"Activate init.d functionality and convert file system to EXT4?
- yes
select if init.d is not working yet or if you don't know"
Well, after reboot WIUI was screaming that my sd card is broken and format may help. It formatted it, but it still didn't work. So I've rebooted to recovery via option in power dialog in order to restore old firmware. However there's a problem now: CWM Touch says that it can't write logs to /cache. Mounting /cache, /data or /emmc from recovery doesn't work, only /system and /sdcard are mounting correctly. I've tried BackToExt3 with no luck. I've tried wiping it many times, with no luck. My phone only boots now to CWM. I can't flash stock via APX mode, because I have broken USB port in my phone. What can I do?
Does restoring a backup, flashing a zip file or wiping work?
Ok, I was searching for almost whole hour now and it seems it's a problem with partition table. Fixing can be done via zip, but I need some dumps. First one from "cat /proc/mounts" and second from "parted".
Here's the zip for nook color if someone wants to do that for me: http://forum.xda-developers.com/showthread.php?t=1759558
exinepl said:
Ok, I was searching for almost whole hour now and it seems it's a problem with partition table. Fixing can be done via zip, but I need some dumps. First one from "cat /proc/mounts" and second from "parted".
Here's the zip for nook color if someone wants to do that for me: http://forum.xda-developers.com/showthread.php?t=1759558
Click to expand...
Click to collapse
the Touch CWM might be the issue......most of the times it is found as the source of some unknown issues for some or intermittent issues.
I use the non-touch one always
Hope it helps
Well, how do I flash new recovery from CWM using zip then?
exinepl said:
Well, how do I flash new recovery from CWM using zip then?
Click to expand...
Click to collapse
check for the CWM thread by Rusty....you have the instructions and process in it.
THERE YOU GO>>>SEE HERE
Hope it helps
Unfortunately, it needs USB. I need to flash it via existing recovery.
Mounting problems occur on some zips using touch recovery . Change cwm to non touch 5.0.2.8. But hey, did you flash a stock kernel on wiui ? you need another kernel, like etana, symbiosis.....or just use the one shipped with rom