Related
I am trying to install mini 2.3.5 on my infuse 4g. It is rooted and everything. When I tried to instal the recovery.img, it wasn't in the system/bin folder. I used terminal and busy box to put it there. Then i used clockworks mod to flash it. Then when i reboot into CWM it says
Signature Verification Failed
I did notice a recovery file in /system. not in the bin folder.
sounds like you're totally lost. I don't know what a recovery.img is, well I guess most android phones have a recovery partition and a boot partition and you would flash a recovery.img to those but the galaxy s series doesn't work anything like that.
lets start with you sharing some information. open settings>about phone and tell me the baseband and android version. because if I have to guess you are trying to use a froyo proceedure that was only needed before custom kernels existed and you're trying it on stock gingerbread firmware, either a Rogers phone or a phone that has been flashed with a gingerbread leak.
also do you mean miui??? auto correct is a *****. and if you flash miui then why an old build? wouldn't you want 2.3.7???
singhtjay said:
I am trying to install mini 2.3.5 on my infuse 4g. It is rooted and everything. When I tried to instal the recovery.img, it wasn't in the system/bin folder. I used terminal and busy box to put it there. Then i used clockworks mod to flash it. Then when i reboot into CWM it says
Signature Verification Failed
I did notice a recovery file in /system. not in the bin folder.
Click to expand...
Click to collapse
huh .....
oh and this should be in the [email protected]
Yes it's a Rogers phone. I'm sorry if I'm making this difficult it is my first time doing this so I'm kinda nervous anyways. Basically its asking me to replace the recovery.img with the 3e modded one. The recovery.img is not in system/bin (where it should be), its in the root folder however. May kernel version os 2.6.35.7-1997. My firmware is 2.3.3 and my baseband is i997RUXKG3
singhtjay said:
I am trying to install mini 2.3.5 on my infuse 4g. It is rooted and everything. When I tried to instal the recovery.img, it wasn't in the system/bin folder. I used terminal and busy box to put it there. Then i used clockworks mod to flash it. Then when i reboot into CWM it says
Signature Verification Failed
I did notice a recovery file in /system. not in the bin folder.
Click to expand...
Click to collapse
Yes it's a Rogers phone. I'm sorry if I'm making this difficult it is my first time doing this so I'm kinda nervous anyways. Basically its asking me to replace the recovery.img with the 3e modded one. The recovery.img is not in system/bin (where it should be), its in the root folder however. May kernel version os 2.6.35.7-1997. My firmware is 2.3.3 and my baseband is i997RUXKG3
singhtjay said:
Yes it's a Rogers phone. I'm sorry if I'm making this difficult it is my first time doing this so I'm kinda nervous anyways. Basically its asking me to replace the recovery.img with the 3e modded one. The recovery.img is not in system/bin (where it should be), its in the root folder however. May kernel version os 2.6.35.7-1997. My firmware is 2.3.3 and my baseband is i997RUXKG3
Click to expand...
Click to collapse
well first off its not a .img its a binary file with no extension a .img is something you get when you dump a partition or drive on a low level so all the Metadata and everything is copied exactly and it would be used for reproducing a drive as a backup or on another device, well it could be any extension really but .img is common.
other androids have a different partition layout and may have a recovery partition.
now what is going.g on is you are trying to do a proceedure for froyo on a gingerbread rom. Samsung changed the boot scripts making it impossible to use cwm without a custom kernel. the boot scripts are in the initramfs which Samsung uses in place of the boot partition which means cwm and init.d support can't be added without replacing the whole kernel.
good news is Samsung has a flash tool called Odin. and there is an open source substitute called heimdall and if you are rooted there is a phone based program called sgs kernel flasher that will flash the kernel. look into the Rogers infuse root thread. the root kernel will also give you cwm. you could also use the hellraiser kernel, entropy's dd kernel, or the infusion gb kernel.
since i have successfully swapped memory before using the vold.fstab here for gingerbread..i though it might be done again using xxkpq + JP_MIUI_V8 since its stable and has faster release cycle than others..
after doing the vold.fstab procedure, SD card as checked in Settings->Phone becomes unavailable..
maybe this GB version or the fact that i used UC Kernel V09 screws the start/end memory targets..
hopefully i would be able to restore using the backup.
my first attempt to restore results in this error:
cp /sdcard/external_SD/vold.fstab.png /system/etc
cp: can't stat '/sdcard/external_SD/vold.fstab.png': Not a directory
Check this forum out, it's for froyo but the Procedure is same, maybe it'll help
http://forum.xda-developers.com/showthread.php?t=1088474
hi sikander, thanks!
i've been trying that and some other linux kungfu from different forums(android and linux) in file copying/moving but somehow to no avail as of the moment...worst case scenario is maybe i really need to reflash kpq+miuiv8 again...
I am also using modified vold.stab with stock xxkpq and uc kernel v6 using root explorer. instead of using adb shell use root explorer to restore file.
Why .png
Cheers
Sent from my GT-i9003 powered by MIUI
hi bscraze, that's what was in the original swap thread...but just to be sure...i tried vold.fstab only without the png extension..yet the result is the same.
i have now restored my nandroid backup since i need to use the phone. i was hoping to discover the cause and share but i failed
lastly, i confirm the transfer from backup vold copy to external_SD is successful, only the cp command from external_SD to system/etc failed.
cYbOrG5 said:
hi bscraze, that's what was in the original swap thread...but just to be sure...i tried vold.fstab only without the png extension..yet the result is the same.
i have now restored my nandroid backup since i need to use the phone. i was hoping to discover the cause and share but i failed
lastly, i confirm the transfer from backup vold copy to external_SD is successful, only the cp command from external_SD to system/etc failed.
Click to expand...
Click to collapse
You tried the mod for gingerbread on miui? There's a swap specially for miui, search in the gm007's miui thread for it
Cheers
Sent from my GT-i9003 powered by MIUI
original vold.fstab
can anyone provide original vold.fstab.. mine got replaced by froyo vers.. forgot to backup.. silly me.. plss help.. thx
Hey all. I did something silly and deleted a file in system/bin folder while troubleshooting a problem. I made a backup of the file before deleting it in sdcard/download but my phone wont boot so I can copy the backup file back to system/bin. I am able to get my phone into download mode and I believe I could copy the file via adb. However I do not know how to get adb to recognize the phone in download mode. I type...
adb devices
and it states "List of devices attached" and there is nothing under the list but when I plug my phone via USB it shows "SAMSUNG Mobile USB CDC Composite Device" in device manager so I know my pc is recognizing it. I have used adb before with batch files like 1click root and things like that so I know its just me not knowing the right commands to get my device recognized.
Any and all help is appreciated! I just need to copy 1 file from sdcard/download to system/bin and I would assume it would boot back up with no problem!
Thanks!
do u have cwm installed?
I just installed CWM v5.5.0.4 via download mode using this method. http://www.theandroidsoul.com/skyrocket-root-clockworkmod-cwm-recovery/
So now that I am in CWM I am trying to mount things like /system and it shows an error mounting /sdcard and I get that error messaging for mounting all except mount usb storage which works great. I was however able to get the file off my phone but now how do I get the file back to system/bin?
Yes.. you can (and really should) flash CWM from download mode via your PC/laptop. A few weeks ago I did something very similar and soft-bricked my SR by renaming an in-use file (framework-res.apk)... I also only had 3e, so couldn't just restore a nandroid or flash a rom zip. Go to the Dev section and find the thread by Copperhed ("Root the ATT SGH-I727 Skyrocket..."). read through the OP and follow instruction exactly. You will be Odin3 flashing just the CWM recovery partition... this will NOT trip your flash counter. If you are already rooted, you should retain root... if not, you can root via his OP. After you have CWM recovery, there's a way you can mount the sdcard so you can transfer files between your PC and SR... then, you can put the sbin file back and see if it reboots fine... if not, with CWM installed, you can flash (via zip.. not Odin) any rom/kernel/modem zip package you want.
Even though I installed CWM from a different source I thanked you anyways DoctorQMM! Now that I have CWM installed how to I transfer the file from my pc to the system/bin directory? I have been able to mount usb storage and it show up as a drive on my pc but when I mount /system nothing shows up. What am I missing?
Thanks for all your help! I am almost there! ^_^
hey, I recommended it first . Seriously though, download a kernel from the dev section, any kernel. Open it up in winrar, winzip, etc... and delete everything except the system folder. Now take the bin file u copied to ur computer and put it in a folder called bin. Put this bin in the kernel zip inside the system folder. Now delete everything else in the system folder. Put this file on a microsd, slip it in ur phone and flash it through cwm. this will put the bin back, and allow u to reboot phone
JDub... PM cdshepherd.... he's the one who shared with me you can use the mounts and storage option in cwm (then click "mount USB storage")... then you can copy files between your sd and computer without having to do what I did (which was pull external sd out of SR, mount in micro adapter, plugged into laptop and loaded files on the sd... then put sd back in phone.. booted into CWM and flashed the rom zip I put on there). Yes.. you are close! If you can't get that one file back to sbin on root, you could try to flash a stock rom/kernel zip (KK1 or LA3)... you only need to put that rom/kernel zip on your sd or external sd so CWM will see it.
icenight89 your right you provided the inspiration so I thanked you as well and appreciate the explanation. I will perform it now and see where I get. Let me understand this correctly in steps..
1. Download a kernel, any kernel.
2. Open it up, delete everything except the system folder.
3. Create a folder named bin and put the backed up file in the bin folder.
4. Delete everything else within the system folder except the bin file and bin folder. So it should be /system/bin/xxx.file
5. Put this on a microsd card and flash it through cwm. I assume I do this by selecting "install zip from sdcard?"
Thanks for the continual help! ^_^
I am having trouble with the kernel part. I downloaded a i727 kernel from here http://forum.xda-developers.com/showthread.php?t=1340114&page=2. Opened it up and it has boot.img in it. Am I missing something?
Alright. I downloaded the kernel from here http://www.mediafire.com/?85g701ate11zdc9. The kernel contained a folder named system and deleted everything else. I then added the folder bin and added the backed up file I deleted to the system/bin/ directory. I then mounted usb storage via CWM and put the new .zip in there. I then selected "install zip from sdcard", "choose zip from internal sd card" located the zip file and selected "yes." I then get the following read outs...
Installing update...
Installation aborted.
--Installing: /emmc/sgh-1727-skyrocket-att-original-kernel_2.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
So it looks like it is not installing. Am I doing something wrong?
wrong kernel, download this one:
http://faux.androidro.ms/sky-kernel-010b1.zip
delete everything from in there except system folder, including boot.img, and follow instructions again, should work
JDubbed said:
icenight89 your right you provided the inspiration so I thanked you as well and appreciate the explanation. I will perform it now and see where I get. Let me understand this correctly in steps..
1. Download a kernel, any kernel.
2. Open it up, delete everything except the system folder.
3. Create a folder named bin and put the backed up file in the bin folder.
4. Delete everything else within the system folder except the bin file and bin folder. So it should be /system/bin/xxx.file
5. Put this on a microsd card and flash it through cwm. I assume I do this by selecting "install zip from sdcard?"
Thanks for the continual help! ^_^
Click to expand...
Click to collapse
these steps are exact, nice
Unfortunately I get the same error message with the kernel you supplied. x.x
010b1.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
Are you sure I can just delete and add stuff like that and It will work? I mean it makes sense to me but since it keeps aborting there may be something crucial missing that I need to keep in the .zip file. Any ideas?
Here is a link of my modified zip. http://dl.dropbox.com/u/6778642/Android/sky-kernel-010b1.zip
pm me when u get a chance
JDubbed said:
Unfortunately I get the same error message with the kernel you supplied. x.x
010b1.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
Are you sure I can just delete and add stuff like that and It will work? I mean it makes sense to me but since it keeps aborting there may be something crucial missing that I need to keep in the .zip file. Any ideas?
Here is a link of my modified zip. http://dl.dropbox.com/u/6778642/Android/sky-kernel-010b1.zip
Click to expand...
Click to collapse
download a rom from Dev section. Doesn't matter which one. Try silvers rom you'll like it. Mount USB storage in cwm. Copy rom to sd. Eject SD from computer. Go back to main menu in cwm. Wipe data/factory reset. Wipe cache partition. Wipe dalvik cache(under advanced in cwm) format system under mounts and storage. Back to main menu in cwm. Install zip from sdcard. Choose zip(rom) you just placed on your SD. Flash it. Reboot device. Enjoy. And make a nandroid after it boots for the first time.
Sent from my SAMSUNG-SGH-I727 using xda premium
Did you make a cwm backup of rom you were using prior to this?
Sent from my SAMSUNG-SGH-I727 using xda premium
No, I did not make a nandroid backup. I had to install CWM from download mode and then I was able to get into CWM all without booting.
I appreciate your time in writing a solution however I am not interested in wiping everything and starting from scratch which is what your proposing. I simply deleted a file in system/bin named mediaserver so system/bin/mediaserver. When I rebooted the phone would not boot. I made a backup of the mediaserver before deleting it and placed it in the sdcard/download folder. All I need to do is copy the mediaserver file back to system/bin/ directory and phone should boot backup as if nothing ever happened. That's is how I understand it. Its just missing a file and I know what the file is and I have the file I just need to figure out how to copy it back over to where it belongs.
I do know how to install stock and other roms but after spending numerous hours on my first phone, SGS Captivate, to experience others roms like Darky's Rom the end result was that it was not worth me having to keep up with all the releases and bug fixes, loading in working kernels to make things work correctly and the like. I would rather just stick with stock. Its just a personal preference.
If anyone knows how to copy a file from my pc or from internal sdcard to my Skyrocket using Download mode or ClockWorkMod using any means but without wiping my data please let me know. Eventually if I do not get a solution I will be forced to revert back to the stock rom but I would rather leave that as a last resort.
I look forward to any other suggestions!
Thank you!
Without the ability to push/pull with adb your running out of solutions. I do hope that you get your skyrocket up and running no matter what method you use. And I do hope that someone with the ability comes along to help you. My way is prob the easy way out. If it were me ide cut my losses. Start from scratch, and try to figure out where my prob starts. Good news is there is a great community with plenty of help. Good luck mate.
Sent from my SAMSUNG-SGH-I727 using xda premium
Since my zip suggestion didn't work, try flashing a different kernel, romracer stockish 0.3 is a good choice, from cwm
JDubbed said:
No, I did not make a nandroid backup. I had to install CWM from download mode and then I was able to get into CWM all without booting.
I appreciate your time in writing a solution however I am not interested in wiping everything and starting from scratch which is what your proposing. I simply deleted a file in system/bin named mediaserver so system/bin/mediaserver. When I rebooted the phone would not boot. I made a backup of the mediaserver before deleting it and placed it in the sdcard/download folder. All I need to do is copy the mediaserver file back to system/bin/ directory and phone should boot backup as if nothing ever happened. That's is how I understand it. Its just missing a file and I know what the file is and I have the file I just need to figure out how to copy it back over to where it belongs.
I do know how to install stock and other roms but after spending numerous hours on my first phone, SGS Captivate, to experience others roms like Darky's Rom the end result was that it was not worth me having to keep up with all the releases and bug fixes, loading in working kernels to make things work correctly and the like. I would rather just stick with stock. Its just a personal preference.
If anyone knows how to copy a file from my pc or from internal sdcard to my Skyrocket using Download mode or ClockWorkMod using any means but without wiping my data please let me know. Eventually if I do not get a solution I will be forced to revert back to the stock rom but I would rather leave that as a last resort.
I look forward to any other suggestions!
Thank you!
Click to expand...
Click to collapse
Based on your first post, I don't think your pc is FULLY installed your device. Download mode requires additional drivers.........adb devices should return a serial number.
I have not tried adb on my skyrocket...I will do that for your sake and reply with my experience..
Often, folks ask how to root the Samsung UCLB3 leak or how to root the official AT&T Gingerbread release for the Infuse 4G (both are one and the same at the time of writing this). This how-to explains how to do this.
Note that this also works for rooting the earlier UCL** and UCK** leaks.
Easiest option - flash a rom that is already rooted.:
An easy option is to flash this Odin tar.md5 that I put together. It flashes stock UCLB3 with root already installed.:
http://forum.xda-developers.com/showthread.php?t=1613523
Another easy option, if you already have cwm recovery, is to download and flash this version.:
http://forum.xda-developers.com/showthread.php?t=1508619
And another easy option from qkster to get UCLB3 + cwm recovery in a Heimdall One-Click package.:
http://forum.xda-developers.com/showthread.php?t=1524081
Another easy option - do it yourself.:
Another easy option is to flash one of the custom Gingerbread kernels with CWM recovery from here. This won't wipe your current OS, data, or apps.:
http://forum.xda-developers.com/showthread.php?p=27123262
Download and place this file on your internal sdcard.:
http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
Then, put your phone in recovery mode. Shut phone off. Hold down power button and both volume buttons, and once the Samsung logo appears, let go of the power button. Keep holding volume buttons down until you get to red CWM recovery.
From there, install the Superuser zip by choosing "install zip from sdcard".
More involved option - do it yourself.:
If you're like me, though, and like to do things the hard way, then below is another way to root the official release and leaked versions.
(Don't have the AT&T GB release or the UCLB3 leak yet? You can get the UCLB3 Gingerbread leak at this link: (http://forum.xda-developers.com/showthread.php?t=1507658). Extract the file in 7zip. Place the extracted file in the PDA slot in Odin. Flash.)
a.) Assuming that you have already flashed the Samsung UCLB3 leak, or that you already have it through AT&T and Kies mini, know these two things.: First, SuperOneClick WILL NOT root this release at the time of writing this. Second, you won't be able to root with the stock kernel, so you will need to flash a custom kernel at least temporarily.
b.) If you intend to go back to the stock UCLB3 kernel after using a custom kernel to root (not a bad idea if you want to keep all stock functionality), then follow this step. If you plan to keep the custom kernel (which allows for improvements such as CWM recovery, Voodoo lagfix, etc.) then skip this step.
If you intend to go back to the stock UCLB3 kernel, save some time and disable Voodoo lagfix by creating a directory on your internal sd card (/sdcard/), labeled Voodoo. Inside that folder, place an empty file named disable-lagfix (with no extension).
If you go back to flash the stock kernel, you will have issues doing so if you have Voodoo lagfix enabled.
c.) Use Heimdall to install a recent custom GB kernel.
Download a recent custom GB kernel. A good custom kernel to use is Entropy's Daily Driver, which can be found at this link.:
http://forum.xda-developers.com/showthread.php?t=1212795
Download and install the Heimdall suite on your computer. Follow ALL installation instructions in the README.txt file included with the program, including instructions for installation of the usb driver in zadig. If you don't install the libusb driver that comes with the program, your phone won't be detected, and you'll only receive error messages. Here is the download link.:
https://github.com/Benjamin-Dobell/Heimdall/downloads
d.) Put your Infuse 4G in download mode
Battery pull method: Pull battery, hold down volume keys, replace battery, connect usb cable, and continue to hold volume keys until phone is in download mode.
e.) On your computer, place the custom kernel zImage in the same directory as heimdall.exe. In a command prompt, make this your working directory, and type this into the prompt on your computer.:
Code:
heimdall flash --kernel zImage
If kernel flash is successful, the phone will reboot. If you disabled Voodoo lagfix, the phone will boot up without much wait. If you didn't disable Voodoo lagfix, wait for the robotic lady voice to go on about all that is being done to enable Voodoo lagfix. Hope you don't mind waiting. You remember that I suggested that you disable Voodoo lagfix, right?
f.) Download the cwm installable zip at the link below, and place it on your internal sdcard (/sdcard/). You'll flash this in recovery in a moment to get root.
ChainsDD Superuser zip (to flash in cwm recovery):
http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
g.) Put the phone in Recovery Mode.
Button method: With the phone turned off, press and hold both volume buttons, as well as the power button. Release the power button after you see the Samsung logo on screen, and continue to hold the volume buttons.
h.) In recovery, choose "Install zip from sdcard". Select "Choose zip from sdcard", and choose the Superuser zip file that you placed on the internal sd card. Select "Yes -Install zip". When installation is complete, go back in the menu and choose "Reboot system now" After the reboot, you should now have the Superuser program and all system files necessary to be rooted.
i.) If you intend to keep Entropy's custom kernel, then you are done. You have rooted UCLB3 at this point, with a custom kernel.
If you want to flash the stock kernel now, you can do so, and you will keep root. To do that, download and extract the stock kernel zImage from HERE. Be sure that Voodoo lagfix is disabled before going back to the stock kernel. Use the same steps outlined in part e.) of this tutorial to flash the stock zImage, or just use SGS Kernel Flasher on the phone.
External sdcard issues?: If you go back to the stock kernel after flashing a custom kernel, you will most likely have trouble seeing your external sdcard. To fix this, use Root Explorer (or a similar app) to edit /system/etc/vold.fstab. In Root Explorer, browse to /system/etc and choose "Mount R/W" to gain write permission to the directory. Open vold.fstab in the built in text editor. Change the mmc2 in the last line to mmc1. Save and exit. Reboot, and you will regain use of your external sd card.
Hope that helps someone!
Is there a way to do this in Odin. Heimdall doesnt recognize the phone to be connected and Im much more comfortable doing it in Odin. Is there a tar file of the kernel to be able to flash it?
jscott30 said:
External sdcard issues?: If you go back to the stock kernel after flashing a custom kernel, you will most likely have trouble seeing your external sdcard. To fix this, use Root Explorer (or a similar app) to edit /system/etc/vold.fstab. Change the mmc2 in the last line to mmc1. Save and exit. Reboot, and you will regain use of your external sd card.
Click to expand...
Click to collapse
Can this step be avoided if we remove the external card before flashing the temporary kernel, then replace it after flashing back to the stock kernel?
(Thanks for the great summary, by the way!)
elivaldez84 said:
Is there a way to do this in Odin. Heimdall doesnt recognize the phone to be connected and Im much more comfortable doing it in Odin. Is there a tar file of the kernel to be able to flash it?
Click to expand...
Click to collapse
To get Heimdall to recognize your phone:
Put your device in download mode, and with the usb cable attached, open zadig (in the Drivers folder of your Heimdall install). In the "Options" menu in zadig, choose "List All Devices" and install the "Samsung USB Composite Device" driver. Then, Heimdall will recognize the device.
Sent from my SGH-I997 using Tapatalk 2
Gary02468 said:
Can this step be avoided if we remove the external card before flashing the temporary kernel, then replace it after flashing back to the stock kernel?
(Thanks for the great summary, by the way!)
Click to expand...
Click to collapse
You can try, but I'm pretty sure that you will still have to edit vold.fstab. Let us know what you find.
Sent from my SGH-I997 using Tapatalk 2
Even though my phone is already rooted, I wanted to thank you for this. I followed the best method I could find a few weeks ago: flashing the already rooted rom. If your phone isn't rooted, doesn't have CWM, and you want to make a backup, that method is more involved than the DIY one you have here.
So, if anyone is facing a similar problem (you need CWM to do the nandroid, you need root to install CWM), follow this.
jscott30 said:
Inside that folder, place an empty file named "disable-lagfix" (without quotes, and with no extension).
Click to expand...
Click to collapse
I'm using the stock "My files" application, can create the folder no problem, how to create the empty file with no extension?
I can copy any file from another folder, rename it but it still has its original extension. Even from PC I can only create a file with a certain extension.
toshik1 said:
I'm using the stock "My files" application, can create the folder no problem, how to create the empty file with no extension?
I can copy any file from another folder, rename it but it still has its original extension. Even from PC I can only create a file with a certain extension.
Click to expand...
Click to collapse
There are several ways to do this.
On the phone, I use ES File Explorer. With that app, you can create a new file without an extension.
Easy way on a Windows PC is to create an empty file in Notepad++ or even Notepad. Choose "Save As", and put quotes around the file name: "myfile"
In Linux, I just use the touch command to create the file, and then push it to the device with adb.
Sent from my SGH-I997 using Tapatalk 2
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
Heimdall? Did you install drivers in zadig while in download mode?
Sent from my SGH-I997 using Tapatalk 2
Ran the file from zadig directory-not noted anywhere in description :-(
3. Got the error message...
I succeeded in installing Entropy's custom kernel and the ChainsDD via cwm, per your instructions. But when I try to reinstall the stock kernel (zImage extracted from UCLB3), Heimdall gets as far as "Uploading KERNEL 100%" but then says "ERROR: Failed to confirm end of file transfer sequence! KERNEL upload failed!".
The phone then reboots, and the kernel version is reported as 2.6.35.7-I997RUXKG3-CL366622. I tried a second time, with same results.
UPDATE: I tried re-extracting zImage and running heimdall again, but it still failed. Then I tried using SGS Kernel Flasher instead and it worked. So I'm happily back to 2.6.35.7-I997UCLB3-CL977492 now.
toshik1 said:
Ran the file from zadig directory-not noted anywhere in description :-(
3. Got the error message...
Click to expand...
Click to collapse
Yeah, check your Heimdall install. And you're right, instructions for installing Heimdall aren't in this tutorial. Plenty of good documentation at the link where you downloaded Heimdall, and that would be another good tutorial topic. A few posts back in this thread, I did explain to someone else how to use zadig to install usb drivers for Heimdall. Find that and see if that helps. Until you have correctly installed drivers, you won't have a working Heimdall install. Read well at the install link.
Edit: The install link directs you to the README.txt file in the Heimdall install folder. Follow ALL of the steps there.
Sent from my SGH-I997 using Tapatalk 2
Gary02468 said:
UPDATE: I tried re-extracting zImage and running heimdall again, but it still failed. Then I tried using SGS Kernel Flasher instead and it worked. So I'm happily back to 2.6.35.7-I997UCLB3-CL977492 now.
Click to expand...
Click to collapse
Good! Glad you figured it out. Not sure why your transfer was wonky in Heimdall, as I've yet to see it fail like that.
Sent from my SGH-I997 using Tapatalk 2
Having trouble now getting the external_sd back. I'm using Root Browser Lite to edit vold.fstab, but when I save the file, the browser goes through the motions of saving it and claims to have succeeded, but when I examine the file it's unchanged. (The browser does claim to have superuser privileges.)
Gary02468 said:
Having trouble now getting the external_sd back. I'm using Root Browser Lite to edit vold.fstab, but when I save the file, the browser goes through the motions of saving it and claims to have succeeded, but when I examine the file it's unchanged. (The browser does claim to have superuser privileges.)
Click to expand...
Click to collapse
Does root browser have an option to mount a system folder as read/write? It sounds like you haven't mounted the directory for writing to it.
In Root Explorer, all you do is browse to the folder, select mount r/w, open the file in the built in text editor, edit, and choose "Save and Exit".
Sent from my SGH-I997 using Tapatalk 2
jscott30 said:
Does root browser have an option to mount a system folder as read/write?
Click to expand...
Click to collapse
No, not that I could find. So I switched to another app (FileSlick) for that, and now it's all working. Thanks again!
I'm still at the same error.
toshik1 said:
I'm still at the same error.
Click to expand...
Click to collapse
Same libusb error still means the same thing: You don't have the libusb drivers installed properly. Keep at it, and good luck.
Update: For those who don't want to mess with Heimdall and swapping kernels to get root on stock UCLB3, I've put together an Odin tar.md5 that will install the AT&T / Samsung 2.3.6 Gingerbread release with root already installed. This will install just like the Samsung leaks, and comes with all of the same stuff: stock kernel, etc. After I finish testing and uploading it, I'll start a thread in Development.
This will eliminate having to go through a long list of difficult steps to get root on stock UCLB3.
EDIT - I have a working tar.md5 for this, but need to work on it a little more before I post later this weekend.
having a 750mb for data partition like in my previous post seems interesting for everyone. however, make a 2nd rom isn't easy for everyone. there are some people who can't download a rom, which makes dualboot mod useless for them. well...I want to share the joy of having a bigger data partition, so I modify a kernel to enable 2nd ext3 sdcard partition as data partition. for now on lets call this mod **data-2sd**. the steps is quite easy.
preparation step:
1. download a modified kernel from here
2. rename the file to 'boot.img'.
3. repartition your sdcard. all partition is primary. 1st partition fat32. 2nd partition ext3. adjust the partition size to any size you want.
Click to expand...
Click to collapse
the steps:
1. install the kernel
2. make a blank file named 'bootsdcard' in your root sdcard
3. reboot your device.
notes:
1. this kernel is made based on irfanbagus's kernel. (credits for him)
2. if you already have 2nd partition in your sdcard, please reformat it.
3. don't use link2sd or a2sd.
4. clean you init.d folder (optional)
5. you'll need a fast sdcard for best result. our default sdcard is too slow.
Click to expand...
Click to collapse
well...thanks for irfanbagus who has make a dualboot kernel for us. as I have said, I modify the kernel based on his work. the modified script is not an efficient one. I have to admit that. feel free to edit the kernel if you don't satisfy with my work.
btw, I realize that not everyone want to use sdcard's 2nd partition, especially when their sdcard is slow and they have to wait till they have enough money to buy a faster one. well...you don't have to uninstall this kernel since I've made an option to turn off data-2sd feature simply by delete 'bootsdcard' from your sdcard. now, it will act as stock DXLC stock kernel with init.d support. when you already have a fast sdcard you can turn on data-2sd feature again by make 'bootsdcard' file in your sdcard.
you could find the modified files here
www.mediafire.com/download.php?cc1kg8s7cx27onb
www.mediafire.com/download.php?0xydu66254ic6yz
DISCLAIMER:
do it with your own risk. no need to thanks or press it. I'm just a noob. give that to the original dev instead.
KNOWN ROM INCOMPATIBILITY ISSUE
============================
please read this before install this kernel. these roms are reported to incompatible with this kernel. some user said it work, but some other said it doesn't work in these rom. to minimilize the risk, I'll list all reported incompatibility issue with my kernel.[/b]
Incompatibility list
1. chobits digital v1.8 and v2
2. m.u.r (merruk ultimate rom) v1
please inform me if you got another incompatibility issue with other custom rom[/quote]
ADDITIONAL STUFF
==============
if your rom incompatible with this kernel you may try this guide to increase your /data partition as well. you'll need a kernel with init.d support to use this method. please read carefully before modify your system.
1. go to system/etc/init.d
2. delete all a2sd and link2sd related stuff
3. create a new file named 01data2sd. put this script inside it
Code:
#!/system/bin/sh
unmount /data
mount -t ext3 -o nosuid,nodev /dev/block/mmcblk0p2 /data
4. set the permission to 777 (rwxrwxrwx)
5. open your terminal manager. type these command.
Code:
su
mkdir /data/sd-ext
mount -t ext3 -o nosuid,nodev /dev/block/mmcblk0p2 /data/sd-ext
note: its blk-zero-p-two, not blk-O-p2
6. via root explorer go to /data.
7. copy all stuff in /data into /data/sdext.
8. open terminal manager. type these command.
Code:
umount /data/sd-ext
9. restart your device.
if you got bootloop, via adb, type these command
Code:
adb shell
su
mount -o remount rw /system
chmod 222 /system/etc/init.d/*
exit
exit
adb reboot
KNOWN ISSUE: gps not working.
NOTE: the bug is a lil bit annoying for several person. if you want a BETTER-FASTER-BUGLESS-BATTERY FRIENDLY method to save your internal memory, you can use my akuro tweak.
TERM OF USE AND SHARING:
this thread intent is for sharing. feel free to use, edit, distribute all material inside this thread which came from me. if there any parts of this mod which comes not from me please refer to the original dev I've mentioned in this thread. if want to share it to another forum or modify it you don't have to ask my permission. no need to credits, put links or whatsoever. you'll only need to remember that you should held all the responsibility by using this mod, modify it or distribute it. DO IT WITH YOUR OWN RISK
Click to expand...
Click to collapse
what is the advantage?
sgy's original data partition size is only 190mb. you can get 1gb or bigger data partition for your device by using this mod.
I see. I will try this, does it work on creeds 2.0?
it will work on all rom but will make your a2sd didn't work. please remove all a2sd script in init.d before use this mod.
So this will be my steps?
1. FLash your ROM/CUSTOM ROM
2. Delete the scripts in data/system/init.d via Root Explorer.
3. Make a file name "bootsdcard" in root directory of your sdcard.
Question : What file? .txt? .exe?
4. Flash the Kernel via Odin or other methods.
5. Reboot your device.
So now all my apps are on my SD? or all futured apps are on it?
just a plain file without any extension.
for the second question...this mod will change your data partition to 2nd sdcard ext3 partition. its completely different with a2sd or link2sd since it won't move any installed app in your device. your previous app will remain in your original data partition. when you activate the feature and reboot your phone, it would be like when you turn on the device for the first time.
so it will show 750mb not 190mb?
I will try this tomorrow
bla bla bla
devion14 said:
so it will show 750mb not 190mb?
Click to expand...
Click to collapse
it depends on your partition size. you can make it 750mb, 1gb, or any size you want.
does it support init d tweaksthe kernel is based on what??
---------- Post added at 06:23 PM ---------- Previous post was at 06:22 PM ----------
and what stock rom should i used? what roms have no sd card issues? im using dxlc1..
Sir. I dont have to modified the custom rom with modified updater-script? I just have to flash the kernel and then custom rom with the formated 1st. Fat32 and 2nd. Ext3. ?
Sent from my GT-S5360 using Tapatalk 2
kurotsugi said:
sgy's original data partition size is only 190mb. you can get 1gb or bigger data partition for your device by using this mod.
Click to expand...
Click to collapse
Now I am using DDLC2 official firmware and my 2nd partition (ext3) size is 1.06 GB,
but I am not using any kernal and other thing, I am using pure official ROM and
rooted my mobile thats all. From lot of months I am using this second partition
with Link2sd app.
See this attachment
devion14 said:
does it support init d tweaksthe kernel is based on what??
---------- Post added at 06:23 PM ---------- Previous post was at 06:22 PM ----------
and what stock rom should i used? what roms have no sd card issues? im using dxlc1..
Click to expand...
Click to collapse
it supports init.d script. however, there are some script in init.d which will mount your 2nd partition in different place. its better to remove them before you activate this feature.
it works for both custom and stock rom.
krishna_nirvana said:
Now I am using DDLC2 official firmware and my 2nd partition (ext3) size is 1.06 GB,
but I am not using any kernal and other thing, I am using pure official ROM and
rooted my mobile thats all. From lot of months I am using this second partition
with Link2sd app.
See this attachment
Click to expand...
Click to collapse
thats your choice. however this mod doesn't require any app and you don't have to link your app to to ext partition. when you uninstal link 2sd you'll lose all your app in ext partition.
tandob said:
Sir. I dont have to modified the custom rom with modified updater-script? I just have to flash the kernel and then custom rom with the formated 1st. Fat32 and 2nd. Ext3. ?
Sent from my GT-S5360 using Tapatalk 2
Click to expand...
Click to collapse
nope. you don't need to install any rom. but make sure that you have a clean 2nd ext partition.
What is the Base Firmware of This Modified Kernel?
I Hope its DXLC1? Or ?
tandob said:
Click to expand...
Click to collapse
is it for real?
kurotsugi said:
it supports init.d script. however, there are some script in init.d which will mount your 2nd partition in different place. its better to remove them before you activate this feature.
it works for both custom and stock rom.
thats your choice. however this mod doesn't require any app and you don't have to link your app to to ext partition. when you uninstal link 2sd you'll lose all your app in ext partition.
nope. you don't need to install any rom. but make sure that you have a clean 2nd ext partition.
Click to expand...
Click to collapse
ok...ill try...i will use
v6 supercharger only
yup...its based on DXLC kernel. we do only a minor modification in init.rc and /sbin folder.
ok, downloading now..will give this a shot
BTW does increasing internal memory with this increase speed a little bit? coz the more internal memory the faster right?
internal memory space doesn't related to device speed. in fact, it will a little bit slower since ext3 partition is slower than rfs. nevertheless, the differences is not significant. and could only seen in benchmarking test.