Hello,
I've just bought my new Samsung Galaxy Gio, and on it I had Android 2.3 version.
I performed a Root on my phone, and after that, I updated the Android version with Kies and now I have Android version 2.3.6, Baseband version S5660XXKT6, , Kernel version 2.6.35.7-perf-CL1047966 [email protected]#1 Build number GINGERBREAD.XXKTK
I've downloaded Clorkwork mode recovery and I to installed it, but after that I did a recheck to see if my phone is still rooted and with the help of Root Checker Basic app it says that the device does not have proper root access.
I've tried to root it againg but in recovery, and it's showing these messages : E:Can't mount /cache/recovery/command' and 'E:Can't open /cache/recovery/last_log',
I don't know what to do know, all that I want is to have a proper root on my phone and CMM recovery nicely installed.
Did I do wrong my rooting my phone before updating it to 2.3.6?
How can I make it ok?
arina_arina said:
Hello,
I've just bought my new Samsung Galaxy Gio, and on it I had Android 2.3 version.
I performed a Root on my phone, and after that, I updated the Android version with Kies and now I have Android version 2.3.6, Baseband version S5660XXKT6, , Kernel version 2.6.35.7-perf-CL1047966 [email protected]#1 Build number GINGERBREAD.XXKTK
I've downloaded Clorkwork mode recovery and I to installed it, but after that I did a recheck to see if my phone is still rooted and with the help of Root Checker Basic app it says that the device does not have proper root access.
I've tried to root it againg but in recovery, and it's showing these messages : E:Can't mount /cache/recovery/command' and 'E:Can't open /cache/recovery/last_log',
I don't know what to do know, all that I want is to have a proper root on my phone and CMM recovery nicely installed.
Did I do wrong my rooting my phone before updating it to 2.3.6?
How can I make it ok?
Click to expand...
Click to collapse
i think you are wrong with the step that you performed..
after you upgrade your firmware,root access was lost,so you have to root it again before install the CWM cz root file can only flashed via stock recovery..
to fix it just install stock recovery again (search for that in development forum),root the device and install the CWM again..
CMIIW
Sent from my GT-S5660 using Tapatalk 2
Step is :
1. Upgrade to latest
2. Install Root From stock recovery
3. Install CWM
4. Upgrade to custom...
Many thanks for the answers, but how do I install stock recovery? I didn't find details or I don't get them. Please explain,
arina_arina said:
Many thanks for the answers, but how do I install stock recovery? I didn't find details or I don't get them. Please explain,
Click to expand...
Click to collapse
Have a look here: http://forum.xda-developers.com/showpost.php?p=20896513&postcount=2
You can download the stock recovery and flash it via Odin.
No need for the stock recovery.
However, the stock Samsung ROM uses RFS and most CWM builds out there are meant for ext4 partitions.
Get a proper CWM, along with ChainsDD's super user zip and you'll be good to go.
Darkshado said:
No need for the stock recovery.
However, the stock Samsung ROM uses RFS and most CWM builds out there are meant for ext4 partitions.
Get a proper CWM, along with ChainsDD's super user zip and you'll be good to go.
Click to expand...
Click to collapse
So, I don't need to stock recovery?
Where can I fiind a good root zip for my phone???? After that, what CWM should I use? Please answer because my phone is working really slow and I can't root it for good! :crying:
arina_arina said:
So, I don't need to stock recovery?
Where can I fiind a good root zip for my phone???? After that, what CWM should I use? Please answer because my phone is working really slow and I can't root it for good! :crying:
Click to expand...
Click to collapse
And your PM while I'm at it.
Hello,
I've already posted a new thread and I didn't get the right answer...
I just want to root my phone again and I can't find the propper zip for android 2.3.6, and also I don't know what RFS means,
I know how to install a stock ROM, but before that I need to have my phone rooted and CWM installed .
Sorry for the many questions,
Good day!
Click to expand...
Click to collapse
Keep the conversation in the thread. We're lacking a bit of information...
How did you root the first time, prior to the official Kies update?
Remember, in most situations, official updates will remove root, simply because they completely overwrite the /system partition where your su binary and Superuser.apk reside. You need to put those back, either with CWM or by using an exploit of some kind, SuperOneClick being a very handy tool in this scenario. (It uses the different included exploits to gain a temporary root shell, remount the /system partition in read-write, pushes the binary and the apk, then sets the proper ownership and permissions to them. In contrast, CWM is already rooted without any exploits, but can only be installed from a live and rooted device, or Download Mode, or for some other devices with fastboot and an unlocked bootloader.)
RFS: Robust FAT File System. A Samsung proprietary file system format used in many mid-range, older devices such as the Gio. Deprecated in newer models, which favor ext4. Similar to good old FAT32, but adds *nix style file permissions support amongst other features. For this reason RFS images may be read but not safely modified on most *nix systems and with some Windows based programs. Modified ROMs enable ext4 support on the Gio as well. Switching back and forth between ext4 and RFS is possible, but that is beyond the scope of this post.
This file system also adds a little gotcha to CWM not found in ext4-based devices. Some CWM builds are meant for use with RFS, others with ext4. I'd avoid those claiming support for both if only because they're not very clear in which format they're working for a given operation.
I'm going with the idea that you want an essentially unmodified, Samsung stock ROM with CWM and root, and that you've only flashed over recovery since updating, or that you've reflashed the whole phone to stock with Odin:
Get the real deal ChainsDD "official" superuser zip file for ARM devices from androidsu.com and put it on your MicroSD card.
Find an RFS-compatible CWM image (iirc Phiexz and Hyriand both have built such recoveries) and flash it with Odin.
Reboot in recovery, and mount the /system partition manually prior to installing the superuser zip. I'm pretty sure the mount command in the updater-script will not work since it assumes an ext4 file system.
While you're at it double check that the files are there with adb shell and have the proper permissions. If the superuser zip installation has failed for some reason you could always manually push the two files, and chown/chmod them like the script does.
Reboot the phone, check for root.
You should be done!
Remember, root isn't a magical make-phone-go-fast panacea. The Gio isn't very fast to begin with, and there's only so much you can do...
Darkshado said:
And your PM while I'm at it.
Keep the conversation in the thread. We're lacking a bit of information...
How did you root the first time, prior to the official Kies update?
Remember, in most situations, official updates will remove root, simply because they completely overwrite the /system partition where your su binary and Superuser.apk reside. You need to put those back, either with CWM or by using an exploit of some kind, SuperOneClick being a very handy tool in this scenario. (It uses the different included exploits to gain a temporary root shell, remount the /system partition in read-write, pushes the binary and the apk, then sets the proper ownership and permissions to them. In contrast, CWM is already rooted without any exploits, but can only be installed from a live and rooted device, or Download Mode, or for some other devices with fastboot and an unlocked bootloader.)
RFS: Robust FAT File System. A Samsung proprietary file system format used in many mid-range, older devices such as the Gio. Deprecated in newer models, which favor ext4. Similar to good old FAT32, but adds *nix style file permissions support amongst other features. For this reason RFS images may be read but not safely modified on most *nix systems and with some Windows based programs. Modified ROMs enable ext4 support on the Gio as well. Switching back and forth between ext4 and RFS is possible, but that is beyond the scope of this post.
This file system also adds a little gotcha to CWM not found in ext4-based devices. Some CWM builds are meant for use with RFS, others with ext4. I'd avoid those claiming support for both if only because they're not very clear in which format they're working for a given operation.
I'm going with the idea that you want an essentially unmodified, Samsung stock ROM with CWM and root, and that you've only flashed over recovery since updating, or that you've reflashed the whole phone to stock with Odin:
Get the real deal ChainsDD "official" superuser zip file for ARM devices from androidsu.com and put it on your MicroSD card.
Find an RFS-compatible CWM image (iirc Phiexz and Hyriand both have built such recoveries) and flash it with Odin.
Reboot in recovery, and mount the /system partition manually prior to installing the superuser zip. I'm pretty sure the mount command in the updater-script will not work since it assumes an ext4 file system.
While you're at it double check that the files are there with adb shell and have the proper permissions. If the superuser zip installation has failed for some reason you could always manually push the two files, and chown/chmod them like the script does.
Reboot the phone, check for root.
You should be done!
Remember, root isn't a magical make-phone-go-fast panacea. The Gio isn't very fast to begin with, and there's only so much you can do...
Click to expand...
Click to collapse
Thanks for the answers:
After I bought the phone, I've rooted it with an update.zip which I found on google. It worked and my phone was rooted. After that, I updated through KIES to 2.3.6 and then I noticed that my phone wasn;t rooted anymore. I should've read firs the instructions I found on xda forum, but I was too eager on updating and playing with this phone.
From your explanations I understand that I should do the following:
- install superoneclick
- find a good superuser app
- install cwm.
Am I right? I originally thought that I should install a root zip file again and then cwm....
Nope, reread the second to last paragraph, it's: CWM, then su.zip. No need for SuperOneClick this way.
Or, just use SuperOneClick and leave the stock recovery as is.
Sent from my Nexus S using xda app-developers app
Darkshado said:
Nope, reread the second to last paragraph, it's: CWM, then su.zip. No need for SuperOneClick this way.
Or, just use SuperOneClick and leave the stock recovery as is.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
I searched for a propper CWM and I couldn't find it...where can I find CWM for android 2.3.6?
The Android version you're using is unrelated to the CWM version. So the same 5 or 6.something will work with GB, ICS and JB.
Well, I've downloaded Odin and the S5660M_CWM-5.0.2.7_ext4+rfs_feb_23_12.tar.md5 file which I found on this thread : http://forum.xda-developers.com/showpost.php?p=20896513&postcount=2
I switched to downloading mode, connected the phone with the pc and started the cwm installation through Odin, but after 50 minutes nothing happens and it's stuck on this :
Download Start...
<0> Create File...
<1> StartThread Detected : 1
<2> StartThread Detected : 0
<3> StartThread Detected : 0
<4> StartThread Detected : 0
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
<1> setup connection...
<1> odin mode.. check plcatform verification.
<1> VerifyPlatform:V0, P0,R0
<1> START!!!
<1> set download environment.
<1> big partition size!!
<1> recovery.img download..
What did I do wrong?
Did I downloaded the wrong CWM file for my android 2.3.6 version?
Did I downloaded the wrong ops file?
If so, where are the corret CWM and ops files?
Please answer!!!
Related
This application *requires* root.
This app can flash a kernel within android on Samsung i9000, Captivate, Fascinate, Vibrant and more.
Features:
* backup kernel as update.zip (for recovery)
* flash kernel from zImage, any .tar or .zip that contains a zImage
* reboot
Usage:
backup kernel: creates an update.zip (for recovery) containing a backup of the current kernel with time and date in /sdcard/sgs-kernel-flasher/backup/
choose kernel: choose kernel image (mostly named zImage) or any .tar or .zip that contains a zImage
flash kernel: flashes the kernel
reboot: reboot the phone
Android market: SGS kernel flasher
DISCLAIMER:
The author of this app is not responsible for any damage to your phone that may be caused by usage of this app or by deficient kernel images.
Im curious, is it "bad" to flash to the partitions when in use ?
Shouldn't it be done via recovery ? Something like cwm where you'd choose flash kernel, it would safely restart your phone into recovery where it would flash your zimage and reboot.
Thnx
Daneshm90 said:
Im curious, is it "bad" to flash to the partitions when in use ?
Shouldn't it be done via recovery ? Something like cwm where you'd choose flash kernel, it would safely restart your phone into recovery where it would flash your zimage and reboot.
Thnx
Click to expand...
Click to collapse
This partition is safe to be flashed from within android - otherwise i would not publish an app that can do that.
The partition is not used while android is running - only read at boot.
Just dont use the app with wrong files - you have to know what you are doing.
I improved the app:
v1.0.1 stable:
* added: manual reboot
* added: check selected file for valid zImage
This app is now stable - happy flashing.
oooh naice!
What are the benefits of flashing the kernel while the OS is running ?
EarlZ said:
What are the benefits of flashing the kernel while the OS is running ?
Click to expand...
Click to collapse
For me, it hurts when pressing the Volume keys up/down in Recovery!
Whats the difference between this and the Tuxility app.? It does the same thing..?
/H
Sent from my GT-I9000 using Tapatalk
what about checking ( disabling ) lagfix?
Hrc4u said:
Whats the difference between this and the Tuxility app.? It does the same thing..?
/H
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
This app does not use the redbend_ua binary - no forced reboot.
And the only purpose of this app is to flash the kernel, nothing else.
iiixda said:
what about checking ( disabling ) lagfix?
Click to expand...
Click to collapse
I will implement a check that will show a warning, but disablinf or removing of a lagfix is too much at the moment. There are too much different lagfix approaches and considering them all is pretty complex.
I keep most of kernels on /sdcard/kernals/ directory in .zip (CWM) format.
Any chances of adding support of such files?
Adding .tar should be straightforward too
I have updated the app one more time:
v1.2.1:
added: PDA.tar and update.zip file support
added: choose file starts in /sdcard/sgs-kernel-flasher/
added: lagfix detection and warning
That means you can now select any .tar or .zip that contains a zImage and the app will automatically extract and flash that zImage.
Major break through for easy kernel flashing on i9000, Captivate, Fascinate and Vibrant- please propagate this awesome news.
Btw. the app is now on market.
Ok this is awesome!
(you beat me to it, you know, congrats!)
I'm running the 2.2.1 firmware ( JPX trough KIES) and used the "SuperOneClick 1.5.5" application to root.
When I run the kerner installer, it would tell me that I have a lagfix installed (AFAIK I don't have any) and also tells me that my device is not rooted.
I can confirm that it's rooted by using the root-explorer and have super-user and busybox installed.
Pierreken said:
I'm running the 2.2.1 firmware ( JPX trough KIES) and used the "SuperOneClick 1.5.5" application to root.
When I run the kerner installer, it would tell me that I have a lagfix installed (AFAIK I don't have any) and also tells me that my device is not rooted.
I can confirm that it's rooted by using the root-explorer and have super-user and busybox installed.
Click to expand...
Click to collapse
Did you see the root request dialog?
If not, you may restart the app or just have look what the superuser app says about the permissions of the sgs kernel flasher.
Does it support 'CWM' .zip files?
I mean these where not only zImage resides, but also some other thingies.
I ask this question because I wasn't able to flash SO_4_5_1 kernel using CWM file provided in this topic: http://forum.xda-developers.com/showthread.php?t=811660
file: http://forum.xda-developers.com/attachment.php?attachmentid=467462&d=1292684343
Attempt on JPX+SO_4_5_1 kernel (so basically it was an attempt to reflash of the same kernel)
Code:
zImage extraction failed!
Kernel flash failed!
xan said:
Does it support 'CWM' .zip files?
I mean these where not only zImage resides, but also some other thingies.
I ask this question because I wasn't able to flash SO_4_5_1 kernel using CWM file provided in this topic: http://forum.xda-developers.com/showthread.php?t=811660
file: http://forum.xda-developers.com/attachment.php?attachmentid=467462&d=1292684343
Attempt on JPX+SO_4_5_1 kernel (so basically it was an attempt to reflash of the same kernel)
Code:
zImage extraction failed!
Kernel flash failed!
Click to expand...
Click to collapse
I will check that.
edit: fixed will be released in a few minutes
Bugfix release:
v1.2.8:
fixed: zImage not correctly extracted from .zip-files
Hello,
Many thanks for this so nice app .
I have to inform You that he detects lagfix is running on my phone, but that is not true.
My phone is running on 2.2.1 Froyo, XXJPUI9000, and i flashed all .PIT, PDA, MODEM and CSC files trough Odin.
I rooted My phone with CF-Root.
And ofcourse differenc is visible, I charge my phone each 3 days .
So if this BUG can be fixed would be nice.
Thanks.
xipod said:
Hello,
Many thanks for this so nice app .
I have to inform You that he detects lagfix is running on my phone, but that is not true.
My phone is running on 2.2.1 Froyo, XXJPUI9000, and i flashed all .PIT, PDA, MODEM and CSC files trough Odin.
I rooted My phone with CF-Root.
And ofcourse differenc is visible, I charge my phone each 3 days .
So if this BUG can be fixed would be nice.
Thanks.
Click to expand...
Click to collapse
I will also check that - it is only a warning message, you can ignore that for the moment.
Edit: I need some mount listings, if you have working adb, please run something like this: "adb shell mount > mount-listing.txt" and attach that file to a post in this thread. That will help me to improve the lagfix detection. Thanks.
I do not know why you say this...
MOD EDIT: Rooters beware. Proceed with extreme caution, as these are highly uncharted waters.
Hi,
I am here to provide you a new method in rooting your xoom, it does not require to flash the decrypted boot.img image.
I have tried it only on my Wifi XOOM, which is a UK version. (With a Japan version of ROM, downloaded from Motodev and upgrade to 3.1)
***EDIT***
I have also tried on a HK 3g xoom (which shows MZ601 in MTP but MZ602 in fastboot). It works without any problem, and internal storage preserved untouched.
===============================================================
I am NOT a xoom developer, nor a rom cook. I am just a user of xoom, which know
a little on developing and are willing to try new things.
So, I can not be sure that the method below works on your device. By following the
things below, your xoom may have a chance to brick.
I am not responsible for any brick or mulfunction device.
===============================================================
To root your xoom, you should start with flashing your device with the clockworkmod recovery (Please refer to the post by solarnz).
After flashing the clockworkmod recovery, do the following.
1. Download the attached ROOT.zip, place it on the root directory of the external sd card, and rename it to update.zip
2. Restart your device to the recovery by:
Type "adb reboot recovery" from your pc
OR press volumn down ~2 seconds after the motorola logo appears when the device starts,
then volumn up when "-->Android recovery" appears.
3. Apply the update in the recovery.
That's it. Your device should be already rooted.
=======================================================================
I am not the inventor of the method, I think about this since I have a Samsung i9000,
and the method of rooting the i9000 is by applying a update.zip file.
I have created the ROOT.zip file by changing the i9000 root zip file with the newer su and superuser.apk (From here: http://forum.xda-developers.com/showthread.php?t=1010568)
I have also changed the updater-script in order to let the updater mount the correct partition for the update.
I am not sure if this update applies to other devices (especially for the 3g ones). This should work if the system partition have name "/dev/block/platform/sdhci-tegra.3/by-name/system".
I would like to thank solarnz for providing the clockmodwork recovery for xoom,
the one who invented the method of rooting the i9000 with a update.zip (I cannot find who make that, sorry...),
and also Xaositek for providing the su and superuser.apk files (I am too lazy to find it by myself...).
========================================================================
That's all. Please try on your device (especially for those stock 3.2) if you would like to take some risk, and report if it is success or not.
Thanks.
eddielo said:
Hi,
I am here to provide you a new method in rooting your xoom, it does not require to flash the decrypted boot.img image.
I have tried it only on my Wifi XOOM, which is a UK version. (With a Japan version of ROM, downloaded from Motodev and upgrade to 3.1)
===============================================================
I am NOT a xoom developer, nor a rom cook. I am just a user of xoom, which know
a little on developing and are willing to try new things.
So, I can not be sure that the method below works on your device. By following the
things below, your xoom may have a chance to brick.
I am not responsible for any brick or mulfunction device.
===============================================================
To root your xoom, you should start with flashing your device with the clockworkmod recovery (Please refer to the post by solarnz).
After flashing the clockworkmod recovery, do the following.
1. Download the attached ROOT.zip, place it on the root directory of the external sd card, and rename it to update.zip
2. Restart your device to the recovery by:
Type "adb reboot recovery" from your pc
OR press volumn down ~2 seconds after the motorola logo appears when the device starts,
then volumn up when "-->Android recovery" appears.
3. Apply the update in the recovery.
That's it. Your device should be already rooted.
=======================================================================
I am not the inventor of the method, I think about this since I have a Samsung i9000,
and the method of rooting the i9000 is by applying a update.zip file.
I have created the ROOT.zip file by changing the i9000 root zip file with the newer su and superuser.apk (From here: http://forum.xda-developers.com/showthread.php?t=1010568)
I have also changed the updater-script in order to let the updater mount the correct partition for the update.
I am not sure if this update applies to other devices (especially for the 3g ones). This should work if the system partition have name "/dev/block/platform/sdhci-tegra.3/by-name/system".
I would like to thank solarnz for providing the clockmodwork recovery for xoom,
the one who invented the method of rooting the i9000 with a update.zip (I cannot find who make that, sorry...),
and also Xaositek for providing the su and superuser.apk files (I am too lazy to find it by myself...).
========================================================================
That's all. Please try on your device (especially for those stock 3.2) if you would like to take some risk, and report if it is success or not.
Thanks.
Click to expand...
Click to collapse
How do you flash cwm if your device if locked? Also the purpose of the rooted boot.img is to allow you to mount your device for adb commands.
Sent from my PG86100 using Tapatalk
yeah no offense but this sounds a little sketch... I see you make a quote at the bottom asking people to report success if they try... I personally would not try this.
Unlocking and rooting is really not that hard and not very time consuming using current methods
Of course, for installing CWM, you have to unlock your device by using "fastboot oem unlock", but that will not brick your device anyway.
For this method, you do not need to issue adb commands to root your device, so no need to have a modified boot.img.
Also, for the current rooting methods, it is not 100% work on some device (like the HK 3g version, which reported missing of internal storage after rooting with currently available method), I would like to see if this work on that.
Rooters beware. Proceed with extreme caution, as these are highly uncharted waters.
eddielo said:
For this method, you do not need to issue adb commands to root your device, so no need to have a modified boot.img.
Click to expand...
Click to collapse
I think you missed my point. Rooted boot.img isn't used for rooting. Its used for adb commands like adb remount. Say i want to adb push a file to my xoom, ls a directory on my xoom, or adb rename system files. Those are all reason you need the rooted boot.img.
Sorry, this is not a rooting method. All what this is doing is flashing su, busybox and Superuser.apk.
There is more to rooting a device than this. You also need an insecure boot image.
I am sorry if I do not catch the real meaning of rooting a device.
What I think of rooting is to let my device, starting from everything stock, untouched, to a state that applications that need root, like Titanium backup or root explorer, works without problem.
I have tried on my two devices with this method, titanium backup works perfectly, root explorer can remount the system partition to rw and can successfully copy files and delete files from that.
The insecure boot.img image, as far as I know, provides everyone to use "adb remount" and make changes to the system directory. But my method do not need adb in copying the binaries and chmod them. You may call it flashing, but after that, su works without problem.
Please, try it first. If you think it is not a method of rooting, I am sorry about that.
Actually guys, don't dismiss him just yet, over in the Galaxy S II forums we only flash insecured images long enough to root the OS then flash back to a secure one, so you have root access but no remount or system r/w.
It's a (fairly) legitimate method and is exactly how I rooted my xoom this time round, well not exactly, I did it like this:
unlock
flash solarnz CWM
adb mount system r/w
push su and busybox
reboot
install superuser from market
done
This is how most people run their GSII and means you can use root apps but no insecure boot image (because the GSII shows a warning on every boot with insecure images and keeps a binary flash counter, cheeky samsung).
This will at least get you to the point where you can su from within android and dump your boot image to modify it yourself, which is what I just did to update my Euro 3G root guide.
So does this mean just "rooted".....like can't flash a rom?
Sent from my Xoom using XDA Premium App
roughneckboren said:
So does this mean just "rooted".....like can't flash a rom?
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Rooting has nothing to do with installing a rom. To install a rom, you just need to unlock and fastboot flash CWM. This guide in noway helps you flash a rom.
alias_neo said:
Actually guys, don't dismiss him just yet, over in the Galaxy S II forums we only flash insecured images long enough to root the OS then flash back to a secure one, so you have root access but no remount or system r/w.
It's a (fairly) legitimate method and is exactly how I rooted my xoom this time round, well not exactly, I did it like this:
unlock
flash solarnz CWM
adb mount system r/w
push su and busybox
reboot
install superuser from market
done
This is how most people run their GSII and means you can use root apps but no insecure boot image (because the GSII shows a warning on every boot with insecure images and keeps a binary flash counter, cheeky samsung).
This will at least get you to the point where you can su from within android and dump your boot image to modify it yourself, which is what I just did to update my Euro 3G root guide.
Click to expand...
Click to collapse
Without an rooted boot.img your recovery will get wiped out every time you boot the OS.
So will this let you make a titanium backup of your data? That way you could recover your data after using the regular unlock method that erases everything?
silvinoa said:
So will this let you make a titanium backup of your data? That way you could recover your data after using the regular unlock method that erases everything?
Click to expand...
Click to collapse
Yes and NO...
Yes this method will allow you to run titanium backup. But to use this method you have to unlock, which erases everything.
I was looking at the auto root for FB15 and was wanting to know if it would work for my phone, Android version: 2.3.6, Baseband: S:R760.01 K.FB14. Any help is greatly appreciated.
Sent from my SCH-R760 using Tapatalk
^^ Second this. Just got SCH-R760 (SGS II) from USCC, there is currently ZERO support. Thanks!
I've tried the ek02 autoroot three times and it's not able to push the files. SuperOneClick didn't work either.
Sent from my SCH-R760 using xda premium
themac79 said:
I was looking at the auto root for FB15 and was wanting to know if it would work for my phone, Android version: 2.3.6, Baseband: S:R760.01 K.FB14. Any help is greatly appreciated.
Sent from my SCH-R760 using Tapatalk
Click to expand...
Click to collapse
The fb15 on this phone is ics so not going to work on your GB ROM .....maybe steady Hawkin can make you a kernel to root it with Odin ....all you have to do is ask him he may do it
He may port cwm for you too don't hurt to ask
Sent from my SPH-D710 using xda premium
Epix4G said:
The fb15 on this phone is ics so not going to work on your GB ROM .....maybe steady Hawkin can make you a kernel to root it with Odin ....all you have to do is ask him he may do it
He may port cwm for you too don't hurt to ask
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
That would be great! Thanks for the advice, really appreciate it.
not working
from what I hear zergrush no longer works in 2.3.6. I tried manually installing but it fails on the USCC GS2 (SCH-R760)
[+] Found a GingerBread ! 0x00000118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
mostly working
So I tried it with my SCH-R760 SGS2 I was able to get root boot recovery. Having the FB14 kernel would make this a snap however the Epic 4g Touch is so close it mostly worked. I seem to have intermittent wifi problems but everything else appears to work without issue.
I got the kernel from step two WISHLINK:wiki.rootzwiki.com/index.php/Samsung_Epic_4G_Touch or directly WISHLINK:goo-inside.me/epic4gtouch/kernel/acs-eb30-clockwork-epic-touch-4g-sep-20-4-00-pm.tar
I tried sweet talking USCC, evidently I'm not as charming as I think I am they told me I'm screwed and don't yet have the re-image. However, the above has the phone working and rooted minus a few problems with wifi.
Good luck.
Margey said:
So I tried it with my SCH-R760 SGS2 I was able to get root boot recovery. Having the FB14 kernel would make this a snap however the Epic 4g Touch is so close it mostly worked. I seem to have intermittent wifi problems but everything else appears to work without issue.
I got the kernel from step two WISHLINK:wiki.rootzwiki.com/index.php/Samsung_Epic_4G_Touch or directly WISHLINK:goo-inside.me/epic4gtouch/kernel/acs-eb30-clockwork-epic-touch-4g-sep-20-4-00-pm.tar
I tried sweet talking USCC, evidently I'm not as charming as I think I am they told me I'm screwed and don't yet have the re-image. However, the above has the phone working and rooted minus a few problems with wifi.
Good luck.
Click to expand...
Click to collapse
If you can get the E4GT kernel to boot on your phone then just use it to install su onto your ROM (/system), then put back your original USCC kernel and you'll be rooted with everything working.
So basically if your adb shell has a "#" prompt, you can just use Auto Root Option A on your phone and install root onto your phone's ROM. Just ignore the zergrush status, even though it fails, the script is still smart enough to install root onto your rom in your situation.
Then to get your original kernel back, figure out which partition has the recovery.bin, which is an unused mirror of your original kernel/zImage.
In the case of E4GT, this is partition /dev/block/mmcblk0p6
To get the mirror of your zImage type the following in adb shell
Code:
cd /sdcard
dd if=/dev/block/mmcblk0p6 of=zImage bs=256 count=32765
Now it is very important that the partition you chose above is really the recovery.bin partition, otherwise the file you just created will essentially be junk and won't allow you to boot your phone (ie *IF* you installed it, your phone *would not boot*)
Assuming you had the correct partition, to install it as your running kernel, you can do
Code:
cd /sdcard
dd if=zImage of=/dev/block/mmcblk0p5 bs=256 count=32765
Please don't go jumping into this unless you fully understand what I suggested.
YOU CAN MAKE YOUR PHONE UNBOOTABLE IF YOU DO THINGS WRONG.
I don't have your phone and the partitions could be different, so I'm depending on you to figure out if things don't make sense.
If you are unsure, ask questions before doing anything.
While I'm just understanding partitions and the like I'm able to follow your instructions but the *IF* parts I'd like to question.
I have:
/dev/block/mmcblk0p6
and
/dev/block/mmcblk0p5
I'm not sure how this correlates to the recovery.bin unless it is apart of one of those files. So for the SCH-R760 with FB14 I'd be looking for how to verify this. I can easily run the suggested lines and looks like everything is there. However to get this far it's been several hours and I'm a bit gun shy as I have to work tomorrow and actually need my phone. Again thank you for the suggestions and help. I'm very close. Everything but wifi is working and very well.
did anyone try flashing the cwm from the touch. it should work because the mount points line up the same. if so i can finish the ics rom and give it to who ever is willing to try
---------- Post added at 09:13 PM ---------- Previous post was at 08:56 PM ----------
sfhub said:
If you can get the E4GT kernel to boot on your phone then just use it to install su onto your ROM (/system), then put back your original USCC kernel and you'll be rooted with everything working.
So basically if your adb shell has a "#" prompt, you can just use Auto Root Option A on your phone and install root onto your phone's ROM. Just ignore the zergrush status, even though it fails, the script is still smart enough to install root onto your rom in your situation.
Then to get your original kernel back, figure out which partition has the recovery.bin, which is an unused mirror of your original kernel/zImage.
In the case of E4GT, this is partition /dev/block/mmcblk0p6
To get the mirror of your zImage type the following in adb shell
Code:
cd /sdcard
dd if=/dev/block/mmcblk0p6 of=zImage bs=256 count=32765
Now it is very important that the partition you chose above is really the recovery.bin partition, otherwise the file you just created will essentially be junk and won't allow you to boot your phone (ie *IF* you installed it, your phone *would not boot*)
Assuming you had the correct partition, to install it as your running kernel, you can do
Code:
cd /sdcard
dd if=zImage of=/dev/block/mmcblk0p5 bs=256 count=32765
Please don't go jumping into this unless you fully understand what I suggested.
YOU CAN MAKE YOUR PHONE UNBOOTABLE IF YOU DO THINGS WRONG.
I don't have your phone and the partitions could be different, so I'm depending on you to figure out if things don't make sense.
If you are unsure, ask questions before doing anything.
Click to expand...
Click to collapse
Here is a mount print out of the sgs2 from uscc that i had someone give me.
http://pastebin.com/k0nXEcKt
---------- Post added at 09:19 PM ---------- Previous post was at 09:13 PM ----------
Can't they just odin flash or heimdall flash the kernel/recovery in, that would be easier, then they truly don't have to root the rom first.
ironfisted said:
Can't they just odin flash or heimdall flash the kernel/recovery in, that would be easier, then they truly don't have to root the rom first.
Click to expand...
Click to collapse
They already did that. That is why they have rooted adb through the kernel. The issue is they are using an Epic 4G Touch kernel which causes some things to not work on their phone. I am suggesting they install their root functionality in the ROM and restore their original USCC kernel/zImage.
Since (according to them) they don't have a package to return to stock, basically they don't have a kernel/zImage to flash in ODIN because it was never provided to them.
Their original kernel/zImage is gone because they flashed over it (presumably before backing it up). That is why I gave them instructions to pull the backup kernel/zImage. Once they do that, whether they install that zImage within Android or through ODIN is not really important. The important part is they get the correct partition to use to pull the backup from so that they have a valid kernel/zImage to flash.
---------- Post added at 09:55 PM ---------- Previous post was at 09:42 PM ----------
Margey said:
While I'm just understanding partitions and the like I'm able to follow your instructions but the *IF* parts I'd like to question.
I have:
/dev/block/mmcblk0p6
and
/dev/block/mmcblk0p5
I'm not sure how this correlates to the recovery.bin unless it is apart of one of those files. So for the SCH-R760 with FB14 I'd be looking for how to verify this. I can easily run the suggested lines and looks like everything is there. However to get this far it's been several hours and I'm a bit gun shy as I have to work tomorrow and actually need my phone. Again thank you for the suggestions and help. I'm very close. Everything but wifi is working and very well.
Click to expand...
Click to collapse
Based on the previous pastebin that was posted it looks like the partitions on the USCC GS2 line up with the Sprint E4GT so it should be safe to run what I suggested.
Both /dev/block/mmcblk0p5 and /dev/block/mmcblk0p6 are linux device files that map to partitions in your phone's EMMC memory.
mmcblk0p5 is labeled zImage (on Sprint) and mmcblk0p6 is labeled recovery.bin (on Sprint). They have the exact same contents. zImage is the kernel and recovery for your phone.
recovery.bin is not being used (on Sprint) so it basically ends up being a backup of your zImage/kernel. Since you overwrote your USCC zImage with the Sprint E4GT zImage (presumably before backing it up) you cannot recover the original from your phone using the partition assigned to zImage.
I am suggesting you retrieve your original zImage from what is essentially a backup in the partition labeled recovery.bin (mmcblk0p6). This can then be installed in your zImage partition (mmcblk0p5) either directly through Android or through ODIN.
Once you create the zImage file as above, keep a copy off your phone on your PC just in case.
The whole purpose of putting back your original USCC zImage/kernel is so all the features work again, but since your root was achieved through the kernel, putting back the original zImage/kernel would cause you to lose root. That is why I suggested, prior to putting back the original USCC kernel, you install persistent root inside your ROM (ie /system)
You can do that by running Auto Root - Option A and ignoring the Blue Hellions error. If your adb is rooted as you described above, Auto Root will still install persistent root in your ROM despite the failure of the zergrush exploit. Once you install the persistent root in your ROM, you can restore the original USCC kernel/zImage and still have root for your applications. You can confirm that Auto Root - Option A did its job by typing:
Code:
ls -l /system/xbin/su
and verifying su is there and it has the proper permissions. If you are unsure, post the output and I can confirm.
What didn't work? maybe its a matter of the rom difference that makes stuff not work. Just an idea. I was thinking of porting the ics rom over to the sgs2 for them.
ironfisted said:
What didn't work? maybe its a matter of the rom difference that makes stuff not work. Just an idea. I was thinking of porting the ics rom over to the sgs2 for them.
Click to expand...
Click to collapse
As mentioned by Margey's post, the wifi wasn't working well. wifi drivers are in the kernel. Margey installed just the kernel/recovery, not the ROM.
sfhub said:
As mentioned by Margey's post, the wifi wasn't working well. wifi drivers are in the kernel.
Click to expand...
Click to collapse
hmmm, so ics is still doable then. hmmmmmm
I just wanted to thank everyone for their help it is very much appreciated. I'm going to try what sfhub posted. I still have my stock kernel since I've been working and haven't had time to do anything. I will try and make a copy of my stock kernel. Can I push superuser into my rom using adb or do I need to flash the Epic 4G's kernel then push superuser and then flash my stock kernel back.
Sent from my SCH-R760 using xda premium
eureka
sfhub said:
They already did that. That is why they have rooted adb through the kernel. The issue is they are using an Epic 4G Touch kernel which causes some things to not work on their phone. I am suggesting they install their root functionality in the ROM and restore their original USCC kernel/zImage.
Since (according to them) they don't have a package to return to stock, basically they don't have a kernel/zImage to flash in ODIN because it was never provided to them.
Their original kernel/zImage is gone because they flashed over it (presumably before backing it up). That is why I gave them instructions to pull the backup kernel/zImage. Once they do that, whether they install that zImage within Android or through ODIN is not really important. The important part is they get the correct partition to use to pull the backup from so that they have a valid kernel/zImage to flash.
---------- Post added at 09:55 PM ---------- Previous post was at 09:42 PM ----------
Based on the previous pastebin that was posted it looks like the partitions on the USCC GS2 line up with the Sprint E4GT so it should be safe to run what I suggested.
Both /dev/block/mmcblk0p5 and /dev/block/mmcblk0p6 are linux device files that map to partitions in your phone's EMMC memory.
mmcblk0p5 is labeled zImage (on Sprint) and mmcblk0p6 is labeled recovery.bin (on Sprint). They have the exact same contents. zImage is the kernel and recovery for your phone.
recovery.bin is not being used (on Sprint) so it basically ends up being a backup of your zImage/kernel. Since you overwrote your USCC zImage with the Sprint E4GT zImage (presumably before backing it up) you cannot recover the original from your phone using the partition assigned to zImage.
I am suggesting you retrieve your original zImage from what is essentially a backup in the partition labeled recovery.bin (mmcblk0p6). This can then be installed in your zImage partition (mmcblk0p5) either directly through Android or through ODIN.
Once you create the zImage file as above, keep a copy off your phone on your PC just in case.
The whole purpose of putting back your original USCC zImage/kernel is so all the features work again, but since your root was achieved through the kernel, putting back the original zImage/kernel would cause you to lose root. That is why I suggested, prior to putting back the original USCC kernel, you install persistent root inside your ROM (ie /system)
You can do that by running Auto Root - Option A and ignoring the Blue Hellions error. If your adb is rooted as you described above, Auto Root will still install persistent root in your ROM despite the failure of the zergrush exploit. Once you install the persistent root in your ROM, you can restore the original USCC kernel/zImage and still have root for your applications. You can confirm that Auto Root - Option A did its job by typing:
Code:
ls -l /system/xbin/su
and verifying su is there and it has the proper permissions. If you are unsure, post the output and I can confirm.
Click to expand...
Click to collapse
I doubled checked su, good. Re-ran the image per your suggestion, all good. I have wifi, I have 3G, I have phone and I have root and CWM.
Thank you.
I have been trying to use the auto-root method after installing the recovery kernel and it keeps saying waiting for device to connect? How can I get it to see my device?
themac79 said:
I have been trying to use the auto-root method after installing the recovery kernel and it keeps saying waiting for device to connect? How can I get it to see my device?
Click to expand...
Click to collapse
You can actually just copy the files to your sdcard and run the script by hand, but the specific reason it is waiting for your phone is because ADB cannot see your phone.
That might be because you haven't enabled USB debugging. It might be because of driver problem. It could be because your ##8778# setting is incorrect.
Have you ever been able to use "adb" with your phone?
sfhub said:
You can actually just copy the files to your sdcard and run the script by hand, but the specific reason it is waiting for your phone is because ADB cannot see your phone.
That might be because you haven't enabled USB debugging. It might be because of driver problem. It could be because your ##8778# setting is incorrect.
Have you ever been able to use "adb" with your phone?
Click to expand...
Click to collapse
I finally got it, the problem was I was missing a driver for my phone. Now I'm trying to make a copy of my stock kernel using your instructions but for some reason when I type cd /sdcard it says it can't find the path specified. It shows my device listed, I don't know what I'm doing wrong? Wait..do you mean to use my phone to make a copy?
themac79 said:
I finally got it, the problem was I was missing a driver for my phone. Now I'm trying to make a copy of my stock kernel using your instructions but for some reason when I type cd /sdcard it says it can't find the path specified. It shows my device listed, I don't know what I'm doing wrong?
Click to expand...
Click to collapse
Are you doing that from an "adb shell"?
You can replace with "cd /data/local/tmp", it can really be any directory where you have write permissions.
If you want to be more bold, you can skip the step of creating a zImage file and write directly from the recovery.bin partition into the zImage partition. The zImage file is nice because if you screw things up and your phone won't boot, you can still use ODIN to flash the zImage (assuming you moved it to your PC)
Code:
dd if=/dev/block/mmcblk0p6 of=/dev/block/mmcblk0p5 bs=256 count=32765
This is an all new way to root and install bootmenu (2nd init) with only one click!
Just running runme.bat you will have a Bravo ready to use new roms in less than a minute.
Instructions:
1. Download: http://www.mediafire.com/?yfgvds9a1w8sbds
2. Extract files whenever you want.
3. Enable USB debugging (menu > Settings > Applications > Development) and connect your phone to the PC.
4. Run runme.bat, in folder Root+Boot-AIO.
5. Press Enter when script ask you to do it and READY!
Note: remenber to install motorola drivers first.
Reserved for instructions in spanish and other language!
Thanks. Finally find another one click option.
Sent from my HTC Sensation using Tapatalk 2
Tested, worked like a charm!
Thank you! :good:
Wow
Just one word, wow, works like a charm. Now we can install a custom rom with like 4 steps now. Your 1 click would be step one for sure!
Good job and lots of props man!
Junkyardjames87 said:
Just one word, wow, works like a charm. Now we can install a custom rom with like 4 steps now. Your 1 click would be step one for sure!
Good job and lots of props man!
Click to expand...
Click to collapse
I've looked into it. While there are a few options to install roms from the pc, some of the commands are known to hang on completion, which means you can't really script them safely (you could add in some kill and restart commands, but you'd have to put like 2-5 min buffers on them to make sure it was done).
I've found that the quickest way to install roms is to use TWRP in the Defy Forums. It allows you to select multiple zips at a time to flash at once. I haven't used clockwork touch recovery yet.
I'll look into it a little more, cause typing something like "./rom_install.sh /path/to/rom.zip -gbgapps" to install a rom and gb gapps would be easy. If I can find a way to execute edify scripts (the ones used to install roms) from adb then this can be done. I can only make and test linux scripts since I no longer have windows, but Josuearisty can port it to windows shell script. I formatted my old windows drive to use my android compile drive .
skeevy420 said:
I've looked into it. While there are a few options to install roms from the pc, some of the commands are known to hang on completion, which means you can't really script them safely (you could add in some kill and restart commands, but you'd have to put like 2-5 min buffers on them to make sure it was done).
I've found that the quickest way to install roms is to use TWRP in the Defy Forums. It allows you to select multiple zips at a time to flash at once. I haven't used clockwork touch recovery yet.
I'll look into it a little more, cause typing something like "./rom_install.sh /path/to/rom.zip -gbgapps" to install a rom and gb gapps would be easy. If I can find a way to execute edify scripts (the ones used to install roms) from adb then this can be done. I can only make and test linux scripts since I no longer have windows, but Josuearisty can port it to windows shell script. I formatted my old windows drive to use my android compile drive .
Click to expand...
Click to collapse
Im not using TWRP either Touch Clockworkmod, both of them are not working as they should sometimes.
I supose that a fully working Touch Clockworkmod would restore an old backup made with our actual Clockworkmod recovery, but does not.
In the case of TWRP, works fine for some time but later it seems to get tired and when you make a backup, it says its complete inmediatly but it is still creating backup files.
It would be great to install roms with just hitting Enter coming from froyo. Do you think that just making some changes to the script, is it possible to install a rom the pc?
josuearisty said:
It would be great to install roms with just hitting Enter coming from froyo. Do you think that just making some changes to the script, is it possible to install a rom the pc?
Click to expand...
Click to collapse
I'm sure its possible somehow, I've just never looked too deep into doing it. What ways I have found either used commands that would hang and require you to quit after 2 mins of activity and start the 2nd command which hangs the same thing -- not safe enough to script. The other ways were for broke\no sdcard and involved copying the rom to /data and then installing as normal.
What I think needs to be done is set up a script that copies the rom & gapps to the sdcard and executes their edify scripts. We need to figure out what command recovery uses to execute the script\install roms then incorporate it into an install script. You'd still have to reboot to bootmenu and enable adb, but that's all (unless we find a way to reboot and have adb already enabled (not good for all the time use, security concerns - it'd be possible to get around the bootmenu pin if adb was enabled on power up).
skeevy420 said:
I'm sure its possible somehow, I've just never looked too deep into doing it. What ways I have found either used commands that would hang and require you to quit after 2 mins of activity and start the 2nd command which hangs the same thing -- not safe enough to script. The other ways were for broke\no sdcard and involved copying the rom to /data and then installing as normal.
What I think needs to be done is set up a script that copies the rom & gapps to the sdcard and executes their edify scripts. We need to figure out what command recovery uses to execute the script\install roms then incorporate it into an install script. You'd still have to reboot to bootmenu and enable adb, but that's all (unless we find a way to reboot and have adb already enabled (not good for all the time use, security concerns - it'd be possible to get around the bootmenu pin if adb was enabled on power up).
Click to expand...
Click to collapse
Well, look at the rom manager, watch how it does it. I think that looking into adb commands we can make a script works like rom manager.
When you select the rom, rom manager lets you wipe data & cache and also install gapps. The rom manager goes to recovery and inmediatly do all steps it self, you can also backup your actual rom.
Try it, download it from market and try it, I see your roms there too.
Some windows commands are:
Adb reboot recovery = reboot into recovery mode
Adb push FILE = copy files to whatever place into out phones. Example to copy a rom.zip to sdcard
Adb push rom.zip /sdcard/rom.zip
Those are windows commands, dont know if they could work on linux. If my pc wasnt broke I would be making some tests!
Does this install a custom recovery? And if not how do I install one? Will a goo manager from the play store install one?
Sent from my Nexus 4
obsanity said:
Does this install a custom recovery? And if not how do I install one? Will a goo manager from the play store install one?
Sent from my Nexus 4
Click to expand...
Click to collapse
This will root and install a custom recovery.
Excellent tool, recommended! :good:
josuearisty said:
This will root and install a custom recovery.
Excellent tool, recommended! :good:
Click to expand...
Click to collapse
Great. Thank you. I'm rooting a friend's phone. He just wants something more reliable than stock. Would you say the CM7 is stable and reliable or should I put CM10 on it?
obsanity said:
Does this install a custom recovery? And if not how do I install one? Will a goo manager from the play store install one?
Sent from my Nexus 4
Click to expand...
Click to collapse
CM7 is more stable now, I have installed an official cm7 and then a patch for it.
Give me some minutes to upload it!
josuearisty said:
CM7 is more stable now, I have installed an official cm7 and then a patch for it.
Give me some minutes to upload it!
Click to expand...
Click to collapse
Which one should I use? Also, what is the SBF for Motorola Bravo? Sorry about the questions in this thread, I'm not familiar with this phone.
obsanity said:
Which one should I use? Also, what is the SBF for Motorola Bravo? Sorry about the questions in this thread, I'm not familiar with this phone.
Click to expand...
Click to collapse
Use cm7. Very fast and stable with no random hiccups, rare force-closes. The SBF is the Motorola Bravo "factory ROM". To install it, you can use RSDlite or do it in linux, both of those tuts are found in the bravo general section. You probably won't have to use the SBF unless you brick your phone, which is a possibility, but flashing the sbf will unbrick it 99% of the time.
Current ROM: CM7.2 Euroskank Cherry Picks | Bravo port
I think I have a problem. The sim I put in to this phone is asking to log in with moto blur and nothing I try is working. So I can't switch the debug mode on. I even tried the bypass suggested by someone but fastboot is not preinstalled on this phone. All I get is the bootloader or stock recovery.
I also tied resetting the password but after I go thru it it just says there is no phone on this moto blur account.
Any help would be appreciated.
Edit:
I got it. I factory reset the phone and then was able to use the bypass motoblur ****.
Sent from my Nexus 4
Ruined my device,now it won't even boot.
How do I fix it? factory reset doesn't help
shvelo said:
Ruined my device,now it won't even boot.
How do I fix it? factory reset doesn't help
Click to expand...
Click to collapse
Post a little more info.
What did you do?
Can you access custom, stock, or bootloader recovery?
Does it still charge?
And did you factory reset from Custom recovery or Stock recovery? Custom only wipes all data where Stock actually formats the partitions.
The easy way and a common issue we're having now.
Unless this is one of those CM10 ext4 issues, just flash the sbf and you should be good to go.
If you downgraded from CM10 and you were using ext4 /data and /cache, reinstall CM10, format back to ext3, then flash whatever you want.
skeevy420 said:
Post a little more info.
What did you do?
Can you access custom, stock, or bootloader recovery?
Does it still charge?
And did you factory reset from Custom recovery or Stock recovery? Custom only wipes all data where Stock actually formats the partitions.
The easy way and a common issue we're having now.
Unless this is one of those CM10 ext4 issues, just flash the sbf and you should be good to go.
If you downgraded from CM10 and you were using ext4 /data and /cache, reinstall CM10, format back to ext3, then flash whatever you want.
Click to expand...
Click to collapse
What is that issue with cm10 ext4? Is that very dangerous for us?
I have been sometime out of the forum and I have lost some things!
josuearisty said:
What is that issue with cm10 ext4? Is that very dangerous for us?
I have been sometime out of the forum and I have lost some things!
Click to expand...
Click to collapse
The CM10 ext4 issue is when you flash a CM10 custom kernel rom and select format /data & /cache to ext4 in the bootmenu. Only custom kernels can use the ext4 file system, so what happens is you format them as ext4, install CM9, and it doesn't load because it can't mount /data and /cache to write them because they're on an unsupported file system. The only things you can do are reinstalling CM10 and formatting back to ext4 of flash the sbf in extreme cases. Its not dangerous at all, just very annoying if you forget to format back to ext3 .
HTC One Mini - AT&T
Tried installing Busybox from GooglePlay .apk, FAILED.
Now what?
I'm guessing I have root, not sure how to be completely sure.
Unlocked fastboot, flashed recovery w/ orange, installed SU from .zip
Gave BB SU permission.
FAILED.
Now what? I need BB. Tried looking for flashable .zip to flash from orange, but can't find any DL's.
S = ON :/
I have no idea where to begin fixing this issue...
On a side note...
Still can't find flashable .zip BB version.
Tried using Jrummy BB installer w/ root, still crashes.
Someone help before I manually brick this POS... i.e. throw it at a brick wall....
I just did a search on Google it said you need an app called busy box installer from the playstore
Sent from my GT-P3113 using xda app-developers app
.APK Method/Apps DO NOT WORK.
djerk said:
I just did a search on Google it said you need an app called busy box installer from the playstore
Click to expand...
Click to collapse
They do not work. Both of these:
google*com/store/apps/details?id=stericson.busybox[/url]
google*com/store/apps/details?id=com.jrummy.busybox.installer[/url]
(Official GooglePlay Online Store)
...either crash/reboot during "Advanced/smart" install, or fail using "Normal" install.
I need to to turn "S" off to enable write to nand possibly?
Tried both /xbin/ and /bin/ install directory through .apk
Also tried both Advanced & Normal install on both apps...
OP Specifically says .apk method = FAIL....
Next answer please, lol
Also....
I also verified root, it's there. Both .apk's (Apps) had SU privelage.
Even restarted the apps to make sure they had SU right from the beginning of their loading.
So to summarize:
AT&T HTC One mini
- fastboot : UNLOCKED
- recovery flashed : recovery-clockwork-touch-6.0.3.6-m4.img
- gained root : ClockWorkMod loaded "root.zip" (.zip courtesy root-wiki)
- DL'ed BusyBox .apk's : TWO FAILURES.
- And here I am....
Android version : 4.2.2
HTC Sense Ver : 5.0
Software number : 1.24.502.3
HTC SDK API level : 5.41
Kernel version:
- 3.4.10-10-gae2031e
[email protected] #1
SMP PREEMPT
Baseband version : 1.19.40d.00.14_10.20.40.4408L
Build number : 1.24.502.3 CL224405 release-keys
Browser version : Webkit/534.30
Moderator please move post
Move post to "AT&T HTC One Q&A"
Plz & TY:angel:
I just installed busy box with no issues on my Verizon htc one running 4.3 maybe you have the wrong version for 4.22
Sent from my GT-P3113 using xda app-developers app
Which ver?
djerk said:
I just installed busy box with no issues on my Verizon htc one running 4.3 maybe you have the wrong version for 4.22
Click to expand...
Click to collapse
Which version of Busy did you use?
1.20.2
1.20.1
1.20
1.19
or earlier?
screens
Here's my screens
I installed version 1.22.1
Sent from my GT-P3113 using xda app-developers app
This needs to be in proper section. This is the HTC One Verizon section. Not mini.
http://forum.xda-developers.com/htc-one-mini
Typed on a HTCone via rumrunners
I know this is the wrong forum, but im gonna help a guy out anyways.
Does the mini have ext4 formating for system and cache partitions? If so flash this https://www.dropbox.com/s/losui4x6nkt47nx/busybox_recovery_flashable.zip
cmlusco said:
I know this is the wrong forum, but im gonna help a guy out anyways.
Does the mini have ext4 formating for system and cache partitions? If so flash this https://www.dropbox.com/s/losui4x6nkt47nx/busybox_recovery_flashable.zip
Click to expand...
Click to collapse
DL'ed your .zip, but i'm waiting to figure out if my Mini has this "ext4" formating.
I don't know how to check if it does, and I don't want to flash something w/o knowing more.
I know ext4 is the newest? linux file structure, but I'm not sure if my Mini is formatted to it....
Anybody know how to check this?
The Mini when hooked up to a PC is recognizable as an external storage device,
so doesn't that mean its FAT or NTFS if windows can recognize it? Right?
Windows won't automatically recognize ext4 w/o installing something right?
If you have to alter or change your phone to ext4, then mine is not. I have never formatted my phone.
How can I check if this is safe for my phone?
I plan on using ClockworkMod to install this through the GUI.
What exactly is this "recovery-flashable-busybox"?
Does it get flashed over top of my recovery partition?
If so, does that mean I will lose my clockworkmod recovery?
Somehow with no idea what I was doing, I managed to unlock fastboot, and get SU.
Now I'm thinking I have no real idea of how this all works......
I would feel more comfortable installing BusyBox using an .APK because I'm a n00b
at this with an expensive toy that i don't want to break.... Like I mentioned before, would
turning S "off", would that allow me to use an .APK to install BusyBox? Or did my two .APK
installations I attempted before fail bc my internal "emulated" SD card is not formatted to
"ext3/4"? I'm lost now...
I guess in summary I need to know WHY I can't install busybox via GooglePlay .APK's,
and is this .zip safe for me to use, and if it is, how would I even use it?
It seems like the more answers I get, the more complications and questions I have...
How would I message or get help from somebody "high up" on this forum, somebody that knows all the in and outs?
I'm not gunna lie, I need a "babysitter" for this....
All I want to do is install Busybox, and after that I'm good, I don't need to play around with the "sensitive internals" of my phone.
I don't want any special roms, or anything else special. I just want SU privelages, and busybox installed.
Soooo.... how do I find a babysitter lol....
cmlusco said:
I know this is the wrong forum, but im gonna help a guy out anyways.
Does the mini have ext4 formating for system and cache partitions? If so flash this https://www.dropbox.com/s/losui4x6nkt47nx/busybox_recovery_flashable.zip
Click to expand...
Click to collapse
Also, I forgot to ask, did you mean can my phone "READ" ext3/4, or did you mean is my device "FORMATTED" to ext3/4
Neither of which do I know how to check or verify, but it would at least tell me what to do next i guess....
I think I'm may be on to something... The Util's known as "BusyBox", are a bunch of basic/necessary/commonly.used Linux commands wrapped up in a package, correct? So if they are Linux commands, then they probably have to be written to a Linux formatted partition? Correct? And if they are Linux commands, on a Linux partition, then that means my phone must be able to "speak" Linux? Correct?
So essentially I need to create an ext3/4 partition, and then write/install BusyBox to that partition?
Is my assumption correct?
Now another assumption is that the .APK's I want to use, which require these Linux commands, act as an interpreter to translate these Linux commands for my phone? Essentially, my phone does not need to speak Linux bc the .APK's know how to use the Linux commands "automatically" or "within themselves" so to speak?
lgally80 said:
I think I'm may be on to something... The Util's known as "BusyBox", are a bunch of basic/necessary/commonly.used Linux commands wrapped up in a package, correct? So if they are Linux commands, then they probably have to be written to a Linux formatted partition? Correct? And if they are Linux commands, on a Linux partition, then that means my phone must be able to "speak" Linux? Correct?
So essentially I need to create an ext3/4 partition, and then write/install BusyBox to that partition?
Is my assumption correct?
Now another assumption is that the .APK's I want to use, which require these Linux commands, act as an interpreter to translate these Linux commands for my phone? Essentially, my phone does not need to speak Linux bc the .APK's know how to use the Linux commands "automatically" or "within themselves" so to speak?
Click to expand...
Click to collapse
All you need to do is flash it thru recovery. If your phones partitions are not formated ext4, the install will fail before anything is ever changed.
To find out how there fornated type mount into a terminal emulator, or at an adb shell. Look for lines with /system and /cache. In those same lines it will say ext4, ext3, etc. If there not ext4 tell me, and i will edit the flashable with the correct partitions.
All this zip does is install the busybox binary file to /system/xbin, and then make the appropirate symlinks.
Yes i reccomend getting s-off. The reason the apk wont work is because your s-on and have a secured boot.img
Busybox is a bunch of linux commands rolled into one. Your phone is already linux, but busybox puts all these commands in one place, and adds some additiinal commands not native to the phone.
Your partitions are most likely ext4 as the regular one is. Are you sure you have an unsecured boot img installed. Pretty sure busy box won't work without one. If you are not s off flashing a rom will not change the boot img. You will have to extract the image and flash via fastboot manually.
Typed on a HTCone via rumrunners
Sounds good, hopefully w this info I can move on, stuck at the laundrmat w my b**** gf, so ill post results in or about 2 hours. Thnx in adv.:good:
Hello guys, I've been trying to install BusyBox myself too today, but without success.
The flashable via Recovery Mode linked file is dead.
Could somebody please re-upload the file ?
Thanks!
htc_one_mini_m4 said:
Hello guys, I've been trying to install BusyBox myself too today, but without success.
The flashable via Recovery Mode linked file is dead.
Could somebody please re-upload the file ?
Thanks!
Click to expand...
Click to collapse
http://vzw1files.dyndns.org/BUSYBOX/busybox_recovery_flashable.zip