[FIX] No Power Menu, No Lockscreen, Corrupt Efs FIX! Skyrocket and T989 - AT&T Samsung Galaxy S II Skyrocket SGH-I727

If your phone shuts straight down after pressing the power button and your have no lock screen, read below for solution. Before you do any of this, please note that this was caused by the note radio, aka uclc5, and if u still have it, please remove it! Also causes include a corrupt efs partition. This guide will help to restore key files important to the operation of your phone
There are three methods available. The first and second one are recommended. If you are uncomfortable with adb and command prompt please use method one
UPDATE: This has been confirmed as working on T989!
WARNING!
Method 3 is only to be used if one and two fail, or if you are positive your efs is corrupt!
Original source for solution, with a few method changes by me:
http://forum.xda-developers.com/showthread.php?t=1438451
METHOD ONE
1.) Use busy box installer from the market and re-install even if u have it working
2.) If step one doesn't work, install super su updater, and update it, then try step one again.
3.) Boot into cwm and dark side wipe 3x
4.) Flash rooted 2.3.5 from thread below
5.) Boot into rom and install root explorer
6). Navigate to /efs/imei/
7.) Press menu and select new file
8.) Name it "keystr" exactly as in quotes
9.) Long press keystr and select edit in text editor
10.) Type "ON" and press back, selecting save.
11.) Reboot and make sure keystr file is still present.
12.) Now u have a few options. U can flash ics back using either Odin one click (UCLA4 or UCLD2), but I don't recommend this. Flash one of the ics roms from the development section, we have great devs!
Rooted 2.3.5 zip:
http://d-h.st/ce75z460t847
METHOD TWO
1.) You must have the Samsung drivers installed for the skyrocket, available from here:
http://downloadcenter.samsung.com/c...ng_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
2.) Once installed, download the attached zip, its a copy of ADB with the needed file inside
3.) Unzip to any location
4.) Boot phone into cwm
5.) Go into Mounts and Storage, and select "mount /efs". Once done connect usb cable to phone and computer
6.) Open command prompt and navigate to the unzipped adb. Issue the following command "adb devices" it should list phone
7.) Now issue the following command "adb push keystr /efs/imei"
8.) Reboot phone and check presence of keystr file in /efs/imei directory with Root Explorer
METHOD 3
Flash attached EFSFix.zip in cwm and reboot.
A SPECIAL THANKS AND SHOUT OUT TO:
mahausrath and Colombiano80 for providing the efs dumps i needed
cmbrown for being a faithful tester!

No download link at thread for Rooted 2.3.6
---------- Post added at 04:03 PM ---------- Previous post was at 03:32 PM ----------
Found a mirror
http://d-h.st/ce75z460t847
---------- Post added at 04:50 PM ---------- Previous post was at 04:03 PM ----------
Still not working. It wont let me write the file keystr to the directory, just says failed, but I can write other things to it. I'm really really confused please help.

I found the error Confusing
instead of putting "NO" put "ON"

Dwolf16 said:
I found the error Confusing
instead of putting "NO" put "ON"
Click to expand...
Click to collapse
typo, main op edited

This may be just me, but I still can't get this method to work. I can't make a file called keystr. I've tried several times using a multitude of Root exploring programs (EStrong, Root Browser, Root Explorer, Astro, ect.) I make sure it's mounted as write and do the works and it just don't work.

did u try the stuff in the pm I sent?

yea im having the same problem its not saving after shut down..

ConfusingCurve said:
This may be just me, but I still can't get this method to work. I can't make a file called keystr. I've tried several times using a multitude of Root exploring programs (EStrong, Root Browser, Root Explorer, Astro, ect.) I make sure it's mounted as write and do the works and it just don't work.
Click to expand...
Click to collapse
I can't create the file either, any help would be appreciated.

i've updated the op with a new method. since efs won't allow you to write from inside android, i've used adb with the push command.

icenight89 said:
i've updated the op with a new method. since efs won't allow you to write from inside android, i've used adb with the push command.
Click to expand...
Click to collapse
Do we need the android sdk for this?

mimart7 said:
Do we need the android sdk for this?
Click to expand...
Click to collapse
nope, I included EVERYTHING u need

Yo ice nthn is working i did everything that it says plus what you've sent me and still nothing

Still nothing

Dwolf16 said:
Still nothing
Click to expand...
Click to collapse
What's the problem? You can't use adb?

Ok so here's the break down
i flashed the efsfix.zip
i go into mounts and storage, and mount /efs ( a error saying Cant Mount /efs!)
i go to cmd.exe and find the Adb folder that has been unzipped
i detect devices with adb devices
i then adb push keystr /efs/imei
it says
C:\ADB>adb push keystr /efs/imei
0 KB/s (2 bytes in 0.002s)
I then reboot go into root explorer and nothings in efs/imei/ and theres nothing in there but the parent folder

Dwolf16 said:
Ok so here's the break down
i flashed the efsfix.zip
i go into mounts and storage, and mount /efs ( a error saying Cant Mount /efs!)
i go to cmd.exe and find the Adb folder that has been unzipped
i detect devices with adb devices
i then adb push keystr /efs/imei
it says
C:\ADB>adb push keystr /efs/imei
0 KB/s (2 bytes in 0.002s)
I then reboot go into root explorer and nothings in efs/imei/ and theres nothing in there but the parent folder
Click to expand...
Click to collapse
alright, that's it. ur efs partition is corrupt, but I need a dump from a fresh stock untouched phone to make sure its fixed properly. In the mean time, I have made a zip of my efs. So change the instructions and do this.
Make a new folder I'm the same folder as adb.exe and name is efs. Extract the contents of attached zip inside efs folder. When u use adb inside cmd, type "adb push efs /". Then reboot. Report back on if that works or not

ok so i rebooted what should i be looking for? when i was in root explorer nothing changed. When i went back into cwm it's still saying "Can't mount efs!" But in the cmd prompt it showed the "adb push efs /" worked

do u have a keystr right in /efs? does ur lock screen work, or power button? If not ur gonna have to wait til I get an efs dump from someone

icenight89 said:
do u have a keystr right in /efs? does ur lock screen work, or power button? If not ur gonna have to wait til I get an efs dump from someone
Click to expand...
Click to collapse
yea i got nothing....also when i did method one originally i would make the file
keystr
type in "ON"
Saved
and it would work until i rebooted...i just there was a way to save it after boot

The push worked, but there is nothing in the imei directory.

Related

More Detailed Perm Root Instructions

I take no credit whatsoever for obtaining root or anything development related.
I simply took BCNice20's instructions and added more detail for less experienced users. In fact I copied most of this directly from his thread and added more detail.
I take absolutely no responsibility for your phone if you brick it, if it melts, if it sleeps with your wife, or if it burns your house down.
Proceed at your own risk.
If you need to get started with the SDK and ADB start here
Step 1
Temp root your device using Visionary or Z4 (I prefer Visionary)
If you are already temp rooted skip this step
Step 2
Download the file linked at this address http://www.thebcblends.com/shift/Shift-root.zip
Extract the contents to the root of your SD card.
If you are having trouble extracting download 7-Zip
Once installed connect your phone to your computer as a disk drive
right click on the shift-root.zip, select extract here, then use the dropdown to locate your device, more specifically your SD card
Once you have extracted the file to the root of your sd card change your connection type back to charge only
Step 3
If you have followed my other thread you already have adb working
Open the cmd prompt and paste the following
Code:
cd C:\AndroidSDK\platform-tools
hit enter
type
Code:
adb shell
hit enter
you will see this
Code:
$
no type
Code:
su
hit enter
Superuser will prompt you to click allow on your phone. Click it quickly to allow permissions!
Now you will see
Code:
#
you have root permissions.
Step 4
Verifying md5sum
Make sure you copy and paste this exactly
Code:
md5sum /sdcard/Shift/hboot_orig.bin
then hit enter
Your result should look like this 386c19451e8dd18f9b98fad6b11be4c0 hboot_orig.bin make sure the numbers match. You may have some extra path in front of hboot_orig.bin.
Next copy and paste this exactly
Code:
md5sum /sdcard/Shift/hboot_eng.nb0
then hit enter
Your result should look like this 60ec1006e6ec2e8acb370d6aad35b17e hboot_eng.nb0 make sure the numbers match. You may have some extra path in front of hboot_eng.nbo.
If these do not match do not proceed. Delete the file placed on the root of your sd card and repeat step 2 and redownload.
Step 5
Now we're going to flash the eng spl. This is where the unpleasant things can happen.
Make sure you are in adb shell with superuser(root) permission. This was explained in Step 3.
If you are not in adb shell with root permissions then do not proceed. Do not pass go, do not collect $200.
Now DO NOT REBOOT until you are instructed to do so!!
Now paste this exactly into cmd prompt
Code:
dd if=/sdcard/Shift/hboot_eng.nb0 of=/dev/block/mmcblk0p18
and hit enter
You have flashed the eng spl. Now we will make sure it flashed properly.
Step 6
Check the md5 of new flash hboot and restore if necessary
run this command to pull the newly flashed hboot to your sdcard
type
Code:
dd if=/dev/block/mmcblk0p18 of=/sdcard/Shift/hboot_check.nb0
in the command prompt and hit enter
now we check the md5 to see if it matches
Enter
Code:
md5sum /sdcard/Shift/hboot_check.nb0
in the command prompt and hit enter
it should read 60ec1006e6ec2e8acb370d6aad35b17e
if the md5sum matches then congratulations its safe to reboot!! you can skip the next bit and continue on to step 7
if you absolutely cannot get the eng hboot to flash right then run this to restore the stock hboot
Type
Code:
dd if=/sdcard/Shift/hboot_orig.bin of=/dev/block/mmcblk0p18
in the command prompt and hit enter
then pull it to check md5
Type
Code:
dd if=/dev/block/mmcblk0p18 of=/sdcard/Shift/hboot_check1.bin
in the command prompt and hit enter
then check the md5sum
Type
Code:
md5sum /sdcard/Shift/hboot_check1.bin
in the cmd prompt then hit enter
it should read 386c19451e8dd18f9b98fad6b11be4c0
if it doesnt keep trying until it does but DO NOT!! reboot till it matches
Step 7
check hboot and perm root!!
ok now reboot your phone into bootloader
turn off phone and hold power+vol down till it boots into bootloader
look at the top and make sure it says s off
if so reboot the phone back into android
put the phone into airplane mode
Go to setting, applications, manage applications and uninstall superuser
Next temp root with visionary
after you are temp rooted then attempt to perm root with visionary
your phone will reboot and you are now officially perm rooted any changes you make will now stick on reboot
**Edit Recovery Added**
Download ROM Manager from the Market. (Pay for the donate version!)
Open ROM Manger and install recovery.
Im having problems on the CMD prompt. On the command line Im getting C:\users\Dizidi> instead of C:\>. Did I miss a step somewhere?
dizidi said:
Im having problems on the CMD prompt. On the command line Im getting C:\users\Dizidi> instead of C:\>. Did I miss a step somewhere?
Click to expand...
Click to collapse
Nope, that's sounds right.
Next you'll want to
Code:
cd C:\AndroidSDK\platform-tools
dizidi said:
Im having problems on the CMD prompt. On the command line Im getting C:\users\Dizidi> instead of C:\>. Did I miss a step somewhere?
Click to expand...
Click to collapse
You may want to learn some basic DOS commands first. See:
http://www.lsi.upc.edu/~robert/teaching/foninf/doshelp.html#chdir
dizidi said:
Im having problems on the CMD prompt. On the command line Im getting C:\users\Dizidi> instead of C:\>. Did I miss a step somewhere?
Click to expand...
Click to collapse
Type cd\ to get to the c:
The command prompt just started out in your user directory. You can just do the cd\Android......... stuff. Using cd\ it doesn't matter which directory you're in when you start.
Sent from my HTC EVO Shift 4G using XDA App.
Im such a noob, thanks guys. forgot to type in "cd".
Good Job typing this up!
Although I have rooted many phones before through adb it is helpful to see it wrighting in simple English
Thought I'd add that I needed to download an app like BusyBox in order to get md5sum to work.
Getting a lot of PM's for help so I'm bumping this back to page one
Any quick instructions for the 2nd part of that post, installing recovery?
tcd2004 said:
Any quick instructions for the 2nd part of that post, installing recovery?
Click to expand...
Click to collapse
First follow BCNice's instructions for backing up your Wimax Keys. You need to be in adb shell, then paste and enter. That easy!
After that place this file on the root of your sd card.
Disconnect from the computer then power down your shift.
Enter the bootloader by pressing power and volume down. The bootloader should recognize the zip and flash it automatically. Select yes to reboot when prompted.
Connect to your computer and remove the zip from your sd card.
If you want to verify your recovery is now working power down and turn back on by pressing power and holding the volume down button. You should now be looking at Clockwork Recovery.
BrandoKC said:
Enter the bootloader by pressing power and volume down. The bootloader should recognize the zip and flash it automatically. Select yes to reboot when prompted.
Click to expand...
Click to collapse
I'm not sure why, but I cannot for the life of me get this to work.
SD Checking...
Loading PG06IMG.zip
No Image!
idaed said:
I'm not sure why, but I cannot for the life of me get this to work.
SD Checking...
Loading PG06IMG.zip
No Image!
Click to expand...
Click to collapse
Delete the file off of your SD card and follow the instructions included in the Wiki Just download the fastboot file linked in the wiki and put it in the same folder you put adb in.
Thank for this guide!!!!!!!!!!!!!!!
I am now rooted . Thank you BrandoKC. I know you copied the instructions from bcnice20 ( Thank you bcnice20), but you dumbed it down enough for me to get brave. I'm a total noob to Android. It was a bit nerve racking, but I got it on the first shot. Thanks to everyone. Now it's time to OC my Shift .
Is there a video guide to root my shift?
HTC Evo Shift 4G
Thans for the more detailed guide! I'm now permarooted in under an hour
Sent from my PG06100 using XDA App
for some reason.. whenever I do temp root with visionary or z4... It says its rooting.. then my phone "restarts" does the sprint 4g slaph screen and gets stuck on the big 4G logo...
I ran visionary when I first got the shift(temp root to run titanium backup) but now it's not working. anyone know why?
Uninstall superuser, reboot, rerun Visionary
Sent from my PG06100 using XDA Premium App
BrandoKC said:
Uninstall superuser, reboot, rerun Visionary
Sent from my PG06100 using XDA Premium App
Click to expand...
Click to collapse
ah, gotcha. will try thanks.

[ROOT] G2X Gingerbread 2.3.3. stock ROM with flashable zip in Clockworkmod Recovery

Update on 9/11/11: Thanks to phburks there is now a flashable zip to root the G2X stock rom. He figured out that the update-binary we were using was not compatible with the G2X. He found the compatible binary that allows us to create flashable zip files. Hats off to phburks. This is an unsigned zip and you should not be required to toggle signature verification. Of course the files required to root the phone (su and Superuser.apk) were created by Chainsdd.
There are two flashable zip packages. The first one roots the G2X. You simply flash it with Clockworkmod Recovery. The second zip unroots the phone for those who wish to unroot their device for whatever reason.
After rooting go to the Android Market and get the Busybox installer referenced below. Use that to install and keep Busybox updated.
Root Zip for G2X: http://www.mediafire.com/?92qpr525ztblh8w
Unroot Zip: http://www.mediafire.com/?2vr7cmgg7qcdn14
HOW TO ROOT
1. Install latest Clockworkmod Recovery using NVFlash, if you haven’t already done so.
http://forum.xda-developers.com/showthread.php?t=1056847
2. Download the root zip package referenced above.
3. Put the zip package on your internal or external sd card on your G2X. Do not unzip the package.
4. Turn off phone and boot into Clockworkmod Recovery by pressing volume down and power and hold until the fancy LG (second one) appears.
5. Select install zip from sd card. Select and flash the root zip package. Note: You navigate in Clockwordmod Recovery by using the volume keys up and down and commit the action by pressing the power button.
6. Reboot your phone. You are now rooted.
NOTE: THE FOLLOWING BELOW IS OBSOLETE. IT IS LEFT FOR HISTORICAL PURPOSES ONLY.
Original post made on 9/9/11:
I wanted to run the stock Gingerbread ROM and wanted to root it without flashing a new ROM. I was able to succesfully do it and the instructions are below. I was attempting to make an update.zip to do this but it kept getting a "status 0" error. The original superuser zip by ChainDD also gets this error. So I decided to try and root it using ADB commands while running Clockworkmod Recovery. Here is how I did it. If someone can help me get an update.zip that will install without error in Clockworkmod Recovery to make this easier for people to install it would be much appreciated.
1. Download my G2X root package that includes necessary ADB files (Android SDK install not required) and unzip the contents. The package contains the latest versions of “su” and “Superuser.apk”.
http://www.mediafire.com/?6rdrdfxvdoq9nkv <download link for my root G2X package>
2. Install latest Clockworkmod Recovery using NVFlash, if you haven’t already done so.
http://forum.xda-developers.com/showthread.php?t=1056847
3. Boot into Clockworkmod Recovery by holding down volume down and power until fancy LG logo shows (about ten to fifteen seconds). This is not the first one displayed when the phone powers up. Wait for recovery to start. Just to be safe perform a backup of your device’s current state.
4. Using the recovery menu scroll down to “mounts and storage,” press the power button, scroll down to “mount system” and press the power button.
5. Now that your system is mounted plug your phone into your computer (let drivers install if you have not done before – requires LG USB driver package).
http://bit.ly/qyoAxY <shortened link for direct download from LG server>
6. Open a command prompt windows on your computer. In the command prompt window change to the directory to where you unzipped the G2X root package.
7. Issue the following ADB commands. Do not type the the text in the brackets <>. That is just information on what the command is doing.
adb kill-server
<make sure no conflict with another version of adb server running>
adb devices
<checks to see if phone is connected to adb>
adb push system /system
<make sure you type a space before “/system”>
adb shell chmod 6755 /system/bin/su
adb shell ln -s /system/bin/su /system/xbin/su
<make sure you type a space before “/system/xbin/su ”>
8. System is now rooted. You can unplug the USB cable now.
9. Now in Clockworkmod Recovery choose “unmount system.”
10. Go back to the main menu and choose “reboot system now.”
11. If you want busybox (some root programs such as Titanium Backup require it) on your system go to the Android Market after rebooting your phone and search on “Busybox.” Download and run the Busybox installer by Stephen (Stericson). When you are prompted allow it to have superuser permissions.
http://bit.ly/qIAoXZ <link to Android Market page for Busybox>
12. You are now rooted with a working busybox installation.
13. It is a good idea to go back into recovery and make a backup of your newly rooted system before you start installing and running programs that obtain superuser permissions.
14. Enjoy the power!
Please click the Thanks button if this helped you out.
Reserved for future use.
Much appreciated for the help, but I don't think I will be using it.
Why not just load a rooted GB or xboards GB, same thing isn't it? lol.
Paul Nur said:
Much appreciated for the help, but I don't think I will be using it.
Why not just load a rooted GB or xboards GB, same thing isn't it? lol.
Click to expand...
Click to collapse
This is for people who have been using the phone after applying the update and don't want to start from scratch again. This lets you just root the phone without needing to flash a rom and format the system.
Wow, I've been waiting fire this thanks jboxer.
Sent from my LG-P999 using XDA App
jboxer said:
This is for people who have been using the phone after applying the update and don't want to start from scratch again. This lets you just root the phone without needing to flash a rom and format the system.
Click to expand...
Click to collapse
Ohhhhhhhhhhhhhhh, I got it lol thanks for showing me it from a different angle
still realy no point xboarders is more stable and much faster then stock and all u need to do is flash his rom then go to advanced restore and only restore data ive gotten away with that doesnt always work though
Always good to have more options.
phburks said:
Always good to have more options.
Click to expand...
Click to collapse
Damn straight. Keep it up, jboxer.
Sent from my LG-P999 using xda premium
Very nice! Thanks man, much appreciated.
Sent from my LG-P999 using XDA App
awesome i tried it on another g2x phone running 2.3.3 root the phone so fast plus with no lost data
thread rated 5 stars ^-^
Change Directory
jboxer said:
I wanted to run the stock Gingerbread ROM and wanted to root it without flashing a new ROM. I was able to succesfully do it and the instructions are below. I was attempting to make an update.zip to do this but it kept getting a "status 0" error. The original superuser zip by ChainDD also gets this error. So I decided to try and root it using ADB commands while running Clockworkmod Recovery. Here is how I did it. If someone can help me get an update.zip that will install without error in Clockworkmod Recovery to make this easier for people to install it would be much appreciated.
1. Download my G2X root package that includes necessary ADB files (Android SDK install not required) and unzip the contents. The package contains the latest versions of “su” and “Superuser.apk”.
http://www.mediafire.com/?6rdrdfxvdoq9nkv <download link for my root G2X package>
2. Install latest Clockworkmod Recovery using NVFlash, if you haven’t already done so.
http://forum.xda-developers.com/showthread.php?t=1056847
3. Boot into Clockworkmod Recovery by holding down volume down and power until fancy LG logo shows (about ten to fifteen seconds). This is not the first one displayed when the phone powers up. Wait for recovery to start. Just to be safe perform a backup of your device’s current state.
4. Using the recovery menu scroll down to “mounts and storage,” press the power button, scroll down to “mount system” and press the power button.
5. Now that your system is mounted plug your phone into your computer (let drivers install if you have not done before – requires LG USB driver package).
http://bit.ly/qyoAxY <shortened link for direct download from LG server>
6. Open a command prompt windows on your computer. In the command prompt window change to the directory to where you unzipped the G2X root package.
7. Issue the following ADB commands. Do not type the the text in the brackets <>. That is just information on what the command is doing.
adb kill-server
<make sure no conflict with another version of adb server running>
adb devices
<checks to see if phone is connected to adb>
adb push system /system
<make sure you type a space before “/system”>
adb shell chmod 6755 /system/bin/su
adb shell ln -s /system/bin/su /system/xbin/su
<make sure you type a space before “/system/xbin/su ”>
8. System is now rooted. You can unplug the USB cable now.
9. Now in Clockworkmod Recovery choose “unmount system.”
10. Go back to the main menu and choose “reboot system now.”
11. If you want busybox (some root programs such as Titanium Backup require it) on your system go to the Android Market after rebooting your phone and search on “Busybox.” Download and run the Busybox installer by Stephen (Stericson). When you are prompted allow it to have superuser permissions.
http://bit.ly/qIAoXZ <link to Android Market page for Busybox>
12. You are now rooted with a working busybox installation.
13. It is a good idea to go back into recovery and make a backup of your newly rooted system before you start installing and running programs that obtain superuser permissions.
14. Enjoy the power!
Please click the Thanks button if this helped you out.
Click to expand...
Click to collapse
Hi,
Sorry i'm new on rooting android phone.
on step 6. how i change the directory in the command prompt to go to the g2x root file i saved?
thanks
yogieajuz said:
Hi,
Sorry i'm new on rooting android phone.
on step 6. how i change the directory in the command prompt to go to the g2x root file i saved?
thanks
Click to expand...
Click to collapse
That's a Command Prompt windows on your computer. The easiest way is to open the desired folder in Windows Explorer and then click on the address bar. Highlight the entire location and copy it. Then in your command prompt windows type "cd" a space, right click and paste the copied location and hit return. You will now be in the correct folder in your command prompt windows.
Thank you for quick reply
jboxer said:
That's a Command Prompt windows on your computer. The easiest way is to open the desired folder in Windows Explorer and then click on the address bar. Highlight the entire location and copy it. Then in your command prompt windows type "cd" a space, right click and paste the copied location and hit return. You will now be in the correct folder in your command prompt windows.
Click to expand...
Click to collapse
Thanks jboxer, work like charm....
but when i did back up they said error can not back up image data ???
whats wrong???
never mind, i found out i run out of space on my sd card
@jboxer, I figured out the flashable zip. Just tested it on an unrooted 2.3.3 installation and it worked perfectly. I PM'd you a link to the zip. Please add it to your OP if you'd like. There's no need for me to create a separate thread.
phburks said:
@jboxer, I figured out the flashable zip. Just tested it on an unrooted 2.3.3 installation and it worked perfectly. I PM'd you a link to the zip. Please add it to your OP if you'd like. There's no need for me to create a separate thread.
Click to expand...
Click to collapse
Thanks to phburks for the good work in figuring out why our update zip packages were being rejected by Clockworkmod Recovery. We now have flashable zips to root the G2X (works on stock GB rom) and to unroot it. They are listed in the first post that I have edited.
http://forum.xda-developers.com/showthread.php?p=17398464

[Q] Help with Samsung galaxy showcase

I have a Samsung galaxy showcase through cellular south and on android 2.2 my phone is rooted using superoneclick i am trying to get cwm on it so i can install miui and all the forums dealing with this arent exactly breaking it down so the average user can understand. its not that i dont appreciate their effort because im sure these threads help alot of people but im not familiar with this phone i have done these steps on a motorola milestone with no problems but i need help with this samsung. please if any one out there can help by giving me step by step instructions to get the clockworkmod on it so i can flash roms through the recovery i would be eternally greatful.
I'm looking for the same answer, I would be greatful also.
how to install miui on cspire samsung galaxy s showcase
this will erase your phone data make sure you back up your phone contacts photos or anything you dont want to lose because this will reset it all.. i am not responsible for your phone but i have done this about 4 times on my phone in the past few days as i have been testing other roms and havent had a problem.
Netflix will not work on this rom for some reason. all these files can be found on xda or google i will not post links because im not sure of the forum rules.
Download:
ee25 stock firmware
atlas v 2.2.pit
cwm4 fixed for cms odin
miui showcase v8(copy this zip file to your phones sd card)
step 1. plug in your phone to your computer and let it install all the drivers for your phone.
step 2. open odin and take the battery out of your phone plug it in the computer while holding volume down button you will see yellow triangle
step 3. select pda and find where you downloaded the ee25 stock firmware. make sure you unzip this file if needed as it will most likely be compressed when you download this. select pit and find the atlas v2.2.pit file make sure the re-partition option is checked then click start. 5 minutes later it will finish when it says pass click reset. unplug phone and boot it up.
step 4. turn phone off remove battery and plug into computer while holding volume down button to get in download mode. open odin again and select pda and select the cwm4 zip file(this one you should leave zipped)make sure you uncheck the repartition box and press start. when it says pass press reset. unplug phone and install battery but dont turn the phone on yet.
step 5. press volume up down and power button at the same time dont let go till you see the second samsung logo then let go now you are in recovery..wipe data then wipe cache then select advanced and wipe dalvek cache select go back select install zip from sd then select choose zip from sd then choose the miui file you put on your sd card thats it it will install then select reboot give it 5 minutes to reboot and dont be surprised when your phone starts talking to you then your done you will have miui and be rooted. i hope this helps
the ee25 stock firmware is the cellular south or cspire firmware so this will work for cspire. if you are on another provider i recommend you find out what your stock firmware is
make sure abd shell installed on your pc first
You will need to install redbend_ua first extract the zip file then;
adb push path/to/redbend_ua /sdcard/redbend_ua
then you need to make it executable
adb shell
su
chmod 777 /sdcard/redbend_ua
Now you need to move it to the /system/xbin
adb shell
su
mv /sdcard/redbend_ua /system/xbin/redbend_ua
Take the zImage file and push it to the sd card.
adb push path/to/zImage /sdcard/zImage
Finally we need to flash the zImage
redbend_ua restore /sdcard/zImage /dev/block/bml8
Now you can download clockworkmod from market and install the fascinate version of recovery. When you get done you can then flash the attached zip and it will replace your stock phone kernel with the modded one giving access to bln and some other stuff.
if it helps please hit thanks button
---------- Post added at 09:25 PM ---------- Previous post was at 09:23 PM ----------
have abd shell installed first
You will need to install redbend_ua first extract the zip file then;
adb push path/to/redbend_ua /sdcard/redbend_ua
then you need to make it executable
adb shell
su
chmod 777 /sdcard/redbend_ua
Now you need to move it to the /system/xbin
adb shell
su
mv /sdcard/redbend_ua /system/xbin/redbend_ua
Take the zImage file and push it to the sd card.
adb push path/to/zImage /sdcard/zImage
Finally we need to flash the zImage
redbend_ua restore /sdcard/zImage /dev/block/bml8
Now you can download clockworkmod from market and install the fascinate version of recovery. When you get done you can then flash the attached zip and it will replace your stock phone kernel with the modded one giving access to bln and some other stuff.
if it helps hit thanks

(Help) SD can not be mounted??

Not sure what happened during a ROM flashing, however, all in all, I can only boot my phone into Bootloader and recovery...nothing else, it says *error mounting /sdcard*So I can't restore or flash a previous backed up ROM. So I guess it would be called a soft brick. Any way of getting out of this? I tried to adb push, doesn't work. Tried the All in One kit, still nothing.
For anyone who can help me with my phone, I will compensate you for your time and knowledge.
If all else fails, I will just have to call and have the phone replaced.
Thanks in advance.
dont panic try this http://forum.xda-developers.com/showthread.php?t=1630459
I got as far as being able to mount my sdcard, now I can't push any files on to my phone?
put the rom in your adb folder, Use the command
adb push nameofrom.zip /sdcard
then in CWM it should appear
Check here for a full guide http://forum.xda-developers.com/showthread.php?t=1667929
C:\androidsdk\tools>adb push ROM.zip /sdcard/ROM.zip
cannot stat 'ROM.zip': No such file or directory
This is what it says when I try to push the ROM
and the rom is in the tools folder ?
you also naming it right ?
don't add the rom.zip after sdcard
i think that means you are pushing it to a rom.zip folder already on card--not 100% sure though
Thongvilay said:
C:\androidsdk\tools>adb push ROM.zip /sdcard/ROM.zip
cannot stat 'ROM.zip': No such file or directory
This is what it says when I try to push the ROM
Click to expand...
Click to collapse
Could also be you're not typing the path to the file correctly.
Do this, on your PC navigate to the folder where you have the ROM.zip file (in your case the tools folder in androidsdk.
Hold down the SHIFT button while right clicking on the "tools" folder
A drop down menu will appear and chose "Open Command window here"
You should get a CMD window with the correct path.
Also for me it's always "platform-tools" folder that I put my file to be push in.
hey BBF nice to see still around--loving my 1s
sorry for off-topic guys

HOW TO FIX CHAINFIRE 3D SOFTBRICK (This is a Guide, Not A Question)

HOW TO FIX Chainfire3d SOFTBRICK AND KEEP EVERYTHING
(I know this isn't a question, but it's a popular issue and many people seem to have it)
If you're like me, you installed Chainfire 3d, You ran the thing inside the app, it restarted your phone,
and you are just stuck at the boot screen. Don't worry, you can fix this without having to lose any of your files.
I would have killed to have a guide like this when my phone bricked instead of having to search the internet for
hours and hours trying to find a solution which was really cryptic.
1.www(DOT)youtube(DOT)com/watch?v=MVXX-YdhRU0
Follow this tutorial to install and open a program which you will use to delete the driver Chainfire installed.
2. Start your phone into recovery mode (home+volup+press+power)
3. Plug in your phone via USB cord to your computer.
4. Once you have adb opened in command prompt, type "su" (without quotes) to gain superuser acess
5. After that, you type "cd /system/lib" (Without quotes)
6. Then you type "cf3d_uninstall.sh" (without quotes)
Your phone should reboot back to exactly like it was before. All your files, apps, etc. will all be there. Now it is
time for you to uninstall that dreaded chainfire 3d app so you never have to worry about it.
Sherkbert said:
(I know this isn't a question, but it's a popular issue and many people seem to have it)
Click to expand...
Click to collapse
Excuse me, I thought that it was required for all forums to be questions so I believed I had to specify that, so ignore it please.
Matthew
Hi, I, too, bricked my android phone. However, your solution did not work for me. Typing "su" in the adb folder in cmd did not give me super user access. It just told me that su is not an internal or external command. Is there another way to get super user access? Thanks in advance
Heeelp!
Im going nuts over this, "cd/system/lib: not found"
Any ideas?
JRkkTheGamer said:
Im going nuts over this, "cd/system/lib: not found"
Any ideas?
Click to expand...
Click to collapse
If You have CWM Recovery, then You need to go: "Mounts & storages" and mount /system
Then command: cd /system/lib will be working.
installed chainfire 3d/cant find the driver in lib
i installed chainfire 3d on my ceros motion (mtk6589,ct7008-w) it got stuck in a boot loop ,went through hell getting adb shell to come up but i got it ....my problem is that when i checked the "cd system /lib" directory there is no such file as "cfd3d_uninstall" no file name in that dir is even close so does chainfire 3d install the gpu driver under a different name?all /99% of all the file names start with "lib"
i have the same problem. when i type in "su" it says it is not recognized as an internal or external command. i'm using TWRP recovery, does that make any difference?
ok, i solved the problem. if you have TWRP, do the following (credit: pancit):
Under TWRP, click Mount, click System, then go back to Home page.
Click Advance, click File Manager, browse to /system/lib
Look for libGLESv1_CM.so and rename it to libGLESv1_CMcf.so
Then, look for libGLESv1_CM_ORG_CF3D.so and rename it to libGLESv1_CM.so
Then, click chmod and change it to 644.
Look for libGLESv2.so and rename it to libGLESv2cf.so
Then, look for libGLESv2_ORG_CF3D.so and rename it to libGLESv2.so
Then, click chmod and change it to 644.
Reboot and wait. Phone is fixed.
hojzz said:
i have the same problem. when i type in "su" it says it is not recognized as an internal or external command. i'm using TWRP recovery, does that make any difference?
ok, i solved the problem. if you have TWRP, do the following (credit: pancit):
Under TWRP, click Mount, click System, then go back to Home page.
Click Advance, click File Manager, browse to /system/lib
Look for libGLESv1_CM.so and rename it to libGLESv1_CMcf.so
Then, look for libGLESv1_CM_ORG_CF3D.so and rename it to libGLESv1_CM.so
Then, click chmod and change it to 644.
Look for libGLESv2.so and rename it to libGLESv2cf.so
Then, look for libGLESv2_ORG_CF3D.so and rename it to libGLESv2.so
Then, click chmod and change it to 644.
Reboot and wait. Phone is fixed.
Click to expand...
Click to collapse
can you make be more specific? i'm a little bit confused on how to proceed
Please help t-t
Sherkbert said:
HOW TO FIX Chainfire3d SOFTBRICK AND KEEP EVERYTHING
(I know this isn't a question, but it's a popular issue and many people seem to have it)
If you're like me, you installed Chainfire 3d, You ran the thing inside the app, it restarted your phone,
and you are just stuck at the boot screen. Don't worry, you can fix this without having to lose any of your files.
I would have killed to have a guide like this when my phone bricked instead of having to search the internet for
hours and hours trying to find a solution which was really cryptic.
1.www(DOT)youtube(DOT)com/watch?v=MVXX-YdhRU0
Follow this tutorial to install and open a program which you will use to delete the driver Chainfire installed.
2. Start your phone into recovery mode (home+volup+press+power)
3. Plug in your phone via USB cord to your computer.
4. Once you have adb opened in command prompt, type "su" (without quotes) to gain superuser acess
5. After that, you type "cd /system/lib" (Without quotes)
6. Then you type "cf3d_uninstall.sh" (without quotes)
Your phone should reboot back to exactly like it was before. All your files, apps, etc. will all be there. Now it is
time for you to uninstall that dreaded chainfire 3d app so you never have to worry about it.
Click to expand...
Click to collapse
CAN YOU PLS HELP HOW YOU ACCESS WITH ADB? UPON ENTERING "su" it wont do anything pls help
i have problem
I type everithing you said like "adb (...........)" but nothing happens. If i type "adb reboot" my phone reboots but when i type what you wrote i dont see responses from pc or phone.Help me please and sorry for my bad english
Not able to load su command..
jokuwa said:
CAN YOU PLS HELP HOW YOU ACCESS WITH ADB? UPON ENTERING "su" it wont do anything pls help
Click to expand...
Click to collapse
I am also not able to enter into su..
I have Karbonn A12+ with no custom recovery but Rooted..
I started Chainfire 3D but when I installed it my phone was stuck on the boot...
It is not working..
Please Help Me..:crying::crying:
I don't know but best way to survive is just take a backup before u try chainfire's 3d app.
su problem fast
:crying:
lobbster123 said:
Hi, I, too, bricked my android phone. However, your solution did not work for me. Typing "su" in the adb folder in cmd did not give me super user access. It just told me that su is not an internal or external command. Is there another way to get super user access? Thanks in advance
Click to expand...
Click to collapse
how did you solve this problem please help
---------- Post added at 07:02 AM ---------- Previous post was at 06:58 AM ----------
when i wrote su is not recognised as as an internal or external command. please help me.
---------- Post added at 07:14 AM ---------- Previous post was at 07:02 AM ----------
Sherkbert said:
HOW TO FIX Chainfire3d SOFTBRICK AND KEEP EVERYTHING
(I know this isn't a question, but it's a popular issue and many people seem to have it):crying:
If you're like me, you installed Chainfire 3d, You ran the thing inside the app, it restarted your phone,
and you are just stuck at the boot screen. Don't worry, you can fix this without having to lose any of your files.
I would have killed to have a guide like this when my phone bricked instead of having to search the internet for
hours and hours trying to find a solution which was really cryptic.
1.www(DOT)youtube(DOT)com/watch?v=MVXX-YdhRU0
Follow this tutorial to install and open a program which you will use to delete the driver Chainfire installed.
2. Start your phone into recovery mode (home+volup+press+power)
3. Plug in your phone via USB cord to your computer.
4. Once you have adb opened in command prompt, type "su" (without quotes) to gain superuser acess
5. After that, you type "cd /system/lib" (Without quotes)
6. Then you type "cf3d_uninstall.sh" (without quotes)
Your phone should reboot back to exactly like it was before. All your files, apps, etc. will all be there. Now it is
time for you to uninstall that dreaded chainfire 3d app so you never have to worry about it.
Click to expand...
Click to collapse
when i wrote su it says it is not recognised as an internal or external command
This is how I solved it on Karbonn titanium S5
Sherkbert said:
HOW TO FIX Chainfire3d SOFTBRICK AND KEEP EVERYTHING
(I know this isn't a question, but it's a popular issue and many people seem to have it)
If you're like me, you installed Chainfire 3d, You ran the thing inside the app, it restarted your phone,
and you are just stuck at the boot screen. Don't worry, you can fix this without having to lose any of your files.
I would have killed to have a guide like this when my phone bricked instead of having to search the internet for
hours and hours trying to find a solution which was really cryptic.
1.www(DOT)youtube(DOT)com/watch?v=MVXX-YdhRU0
Follow this tutorial to install and open a program which you will use to delete the driver Chainfire installed.
2. Start your phone into recovery mode (home+volup+press+power)
3. Plug in your phone via USB cord to your computer.
4. Once you have adb opened in command prompt, type "su" (without quotes) to gain superuser acess
5. After that, you type "cd /system/lib" (Without quotes)
6. Then you type "cf3d_uninstall.sh" (without quotes)
Your phone should reboot back to exactly like it was before. All your files, apps, etc. will all be there. Now it is
time for you to uninstall that dreaded chainfire 3d app so you never have to worry about it.
Click to expand...
Click to collapse
1. www(DOT)youtube(DOT)com/watch?v=MVXX-YdhRU0
Follow this tutorial to install sdk and adb.
2. Follow this - www(DOT)dominantwire(DOT)com/2012/11/how-to-solve-adb-device-not-found-error.html#.U3nsHoGSwpk
3. Start your phone into recovery mode (volume up+power),till red screen
4.For CWM, go to mount and storage and "mount/system"
5. Plug in your phone via USB cord to your computer.
6. type "adb pull /system/lib /device" (in adb cmd)
7. Now all the files are in C:/device, browse to that and
look for libGLESv1_CM.so and rename it to libGLESv1_CMcf.so
Then, look for libGLESv1_CM_ORG_CF3D.so and rename it to libGLESv1_CM.so
Look for libGLESv2.so and rename it to libGLESv2cf.so
Then, look for libGLESv2_ORG_CF3D.so and rename it to libGLESv2.so
8. type "adb push /device /system/lib" (in adb cmd)
9. After this, Disconnect - Reboot - Done!
Do Not try Chainfire3D again.
This post helped me so much!
Thanks to this post I recovered my device, I thought it was lost forever!
many many thanks
BSFrost said:
1. www(DOT)youtube(DOT)com/watch?v=MVXX-YdhRU0
Follow this tutorial to install sdk and adb.
2. Follow this - www(DOT)dominantwire(DOT)com/2012/11/how-to-solve-adb-device-not-found-error.html#.U3nsHoGSwpk
3. Start your phone into recovery mode (volume up+power),till red screen
4.For CWM, go to mount and storage and "mount/system"
5. Plug in your phone via USB cord to your computer.
6. type "adb pull /system/lib /device" (in adb cmd)
7. Now all the files are in C:/device, browse to that and
look for libGLESv1_CM.so and rename it to libGLESv1_CMcf.so
Then, look for libGLESv1_CM_ORG_CF3D.so and rename it to libGLESv1_CM.so
Look for libGLESv2.so and rename it to libGLESv2cf.so
Then, look for libGLESv2_ORG_CF3D.so and rename it to libGLESv2.so
8. type "adb push /device /system/lib" (in adb cmd)
9. After this, Disconnect - Reboot - Done!
Do Not try Chainfire3D again.
Click to expand...
Click to collapse
this one worked for me thank u mwaaah
BSFrost said:
1. www(DOT)youtube(DOT)com/watch?v=MVXX-YdhRU0
Follow this tutorial to install sdk and adb.
2. Follow this - www(DOT)dominantwire(DOT)com/2012/11/how-to-solve-adb-device-not-found-error.html#.U3nsHoGSwpk
3. Start your phone into recovery mode (volume up+power),till red screen
4.For CWM, go to mount and storage and "mount/system"
5. Plug in your phone via USB cord to your computer.
6. type "adb pull /system/lib /device" (in adb cmd)
7. Now all the files are in C:/device, browse to that and
look for libGLESv1_CM.so and rename it to libGLESv1_CMcf.so
Then, look for libGLESv1_CM_ORG_CF3D.so and rename it to libGLESv1_CM.so
Look for libGLESv2.so and rename it to libGLESv2cf.so
Then, look for libGLESv2_ORG_CF3D.so and rename it to libGLESv2.so
8. type "adb push /device /system/lib" (in adb cmd)
9. After this, Disconnect - Reboot - Done!
Do Not try Chainfire3D again.
Click to expand...
Click to collapse
Thank you! This is the correct solution. :good:
adb shell
After you connect your phone, you have to run the "adb shell" command to get into the shell. someone neglected to mention that. hope this helps.
BSFrost said:
1. www(DOT)youtube(DOT)com/watch?v=MVXX-YdhRU0
Follow this tutorial to install sdk and adb.
2. Follow this - www(DOT)dominantwire(DOT)com/2012/11/how-to-solve-adb-device-not-found-error.html#.U3nsHoGSwpk
3. Start your phone into recovery mode (volume up+power),till red screen
4.For CWM, go to mount and storage and "mount/system"
5. Plug in your phone via USB cord to your computer.
6. type "adb pull /system/lib /device" (in adb cmd)
7. Now all the files are in C:/device, browse to that and
look for libGLESv1_CM.so and rename it to libGLESv1_CMcf.so
Then, look for libGLESv1_CM_ORG_CF3D.so and rename it to libGLESv1_CM.so
Look for libGLESv2.so and rename it to libGLESv2cf.so
Then, look for libGLESv2_ORG_CF3D.so and rename it to libGLESv2.so
8. type "adb push /device /system/lib" (in adb cmd)
9. After this, Disconnect - Reboot - Done!
Do Not try Chainfire3D again.
Click to expand...
Click to collapse
When I try step 8, I get an error saying permission denied any help?
Life Saver - Thanks -Done on mu Note III
Thanks. WOrk like charm on note 3
hojzz said:
i have the same problem. when i type in "su" it says it is not recognized as an internal or external command. i'm using TWRP recovery, does that make any difference?
ok, i solved the problem. if you have TWRP, do the following (credit: pancit):
Under TWRP, click Mount, click System, then go back to Home page.
Click Advance, click File Manager, browse to /system/lib
Look for libGLESv1_CM.so and rename it to libGLESv1_CMcf.so
Then, look for libGLESv1_CM_ORG_CF3D.so and rename it to libGLESv1_CM.so
Then, click chmod and change it to 644.
Look for libGLESv2.so and rename it to libGLESv2cf.so
Then, look for libGLESv2_ORG_CF3D.so and rename it to libGLESv2.so
Then, click chmod and change it to 644.
Reboot and wait. Phone is fixed.
Click to expand...
Click to collapse

Categories

Resources