Related
Sorry to post this here - this relates to this thread. The process seems to have some bugs. Specifically, once I am logged in, the steps say to execute the following:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
flash_image recovery /sdcard/recovery-RA-GNM-thunderc-s-1.1.0.img
reboot recovery
Click to expand...
Click to collapse
Sadly, when I try to move the recovery script, I get a file not found. A quick ls of the /system/etc dir shows there is no install-recovery.sh
# ls system/etc/*.sh
ls system/etc/*.sh
system/etc/init.goldfish.sh
system/etc/init.qcom.bt.sh
system/etc/init.qcom.coex.sh
system/etc/init.qcom.fm.sh
system/etc/init.qcom.post_boo
system/etc/init.qcom.sdio.sh
Click to expand...
Click to collapse
Am I missing something obvious here?
Thanks!
answer my own question
So what I'm seeing is that this step just gets omitted. E.g. (pretend I linked to http colon slash slash forum.androidcentral.com slash optimus-v/58654-custom-recovery-optimus-v.html) this thread at android central (pretend I closed the href here). I guess the script must have been for the S, maybe?
I'm running into the same issue. I looked it up and a lot of places just passed over it for the V. But then after I did that and rebooted into recovery, there was no
"Backup" option, was just the "Android system recover <3e>" with options like reboot, wipecache, and two others...tried multiple times with the same results. Am I just missing something?
- Wright
Did you end up flashing? I decided to go a different route, used superoneclick to get on, pushed a copy of su to the machine, and simply went in as superuser to delete the pre-installed apps that I didn't like. I've yet to actually flash mine.
I did actually...after like 5 attempts I gave up for like an hour. Then I came back, did the exact same thing, except this time it booted custom recovery? No idea why the recover took, but anyway...flashed with the rom, wiped and rebooted, got stuck at the LG screen, flashed/wiped again and it worked perfect?
But, the image in that thread we were using doesn't have a kernel that lets you go over 600 mhz. So just like 30 minutes after flashing I went and downloaded an Xionia rom and flashed it with that...specs are follows:
Rom info:
- Xionia 005 Kernel
- VM crapware removed (No WHERE, Air chat, etc)
- Boot Logo and sound are gone
- Deodexed
- ZipAligned
- Not overclocked (but the kernel IS overclockable using SetCpu or similar)
- Optimus S themes will not work with this rom.
- Overclockable up to 864Mhz (No guarantees on how fast your particular processor will go. Mine is only stable up to 825.)
- CIFS support
- Tons of speed tweaks (see the thread linked above for full details)
Just google like Stock Virgin Mobile + Xionia Kernel (BETA 2).
Now using Setcpu to keep it stable at 806Mhz.
But yeah, really no idea what made the recovery finally take. Although, haven't tested this, but after you set the usb mode to transfer, move the files, the use superone click. It resets the usb connection, and I usually go and turn back on the usb file transfer option, but I didn't the time it worked. Could be a connection, but maybe not? *shrug*
-Wright
(P.S. Sorry if I'm not making any sense, this is my first android phone and I just started trying to do all that last night, so I'm probably confusing terms and stuff I shouldn't be)
Interesting,
seriously people?
Alright. Tomorrow night if im not moving Ill make a video for you peeps
ITS SUPER EASY. But seeing as all of you joined this month and are probably new to rooting and installign custom roms ill cut you some slack.
BTW in a month or so Ill be buying the phone to make sweet roms for. So watch out for that
Looking forward to the new instructions...
Got this fon today & being a total newb...can't wait for an easy, clear-cut way to root.
Thx in advance.
friends here you can find Pantech Sky Vega Racer IM-A770K room, recovery, update zip etc.
Friends
I bought used SKY IM-A770K phone from our local market and used it, although it is with android 2.3.3 but it is really great phone. At first I use Samsung I900, HTC HD, Xperia Arc, I9000 etc. but it gives me more and more pleasure. It is a greeeeeeeeeeeeeeeeeeeeeeeeeet phone.
There is no third party custom rom or kernel found.
I request to XDA developers and other XDA community please works on that phone and create custom roms and kernels for it
I found Pantech SKY IM-A770K update zip, clockworkmod Rom, root, USB drivers and recovery from a china’s website bbs.xda.cn/forum-507-1.html here is a complete forum part on IM-A770K and A760s. You can translate this site using goole chrome.
I also up load these files on mediafire. These links are here. You can also download from mediafire.
SKY_UniUSBDriver_v3.6.6
mediafire.com/?grae6s0x9130y94
UniUSBDriver_v355
mediafire.com/?pgjltz97wkgoitj
a770k root zip
mediafire.com/?q8ipw1xd4aec3e3
VegaRacer-kdh4865-cwm-v101 recovery
mediafire.com/download.php?34rfp6stg34jmj5
770K update zip
A770Kupdate.part1
mediafire.com/?a9ybdy3hc7ye5aa
A770K Rom
A770K clockworkmod rom.part1
mediafire.com/?ogqugupqqensqja
A770K clockworkmod rom.part2
mediafire.com/?8mlsd74fju3h29u
And also download these files from these direct links but these sites are in Chinese.
For update Zip
bbs.xda.cn/thread-10905022-1-1.html
for complete Rom
115.com/file/bhtcie50%20#clockworkmod (1). rar
Need original GB firmware for Sky Vega Racer IM-A770K
Hi amunaf.
Thanks so much for posting those links for the Sky Vega Racer IM-A770K. I also have such a phone. I like it too very much too because of the fast CPU and its large screen.
Unfortunately I am now in a dilemma. When I got this fone, details of the "about phone" were as follows:
Android version - 2.3.3
Baseband version - S0833144.TP15.R1090
Kernel version - 2.6.35.7.perf [email protected] #2
Build number - GINDERBREAD
Board and Software version - MSM8260_SURF V1.44
I was so happy being able to root with the above specs using SuperOneClick v2.3.2
Right after rooting and rebooting the phone, I received a message reminder from SKY (seen at the taskbar) saying there was an OTA update available for download. I then proceeded with the OTA download and upgrade and noted the file for download was only 13MB. Thought the download was quite quick, the file being loaded to my phone unusually took to a long time (almost 30mins to load) and I wondered why since the downloaded file was only 13mb. I noted the following changes on the "about phone" after the upgrade or patch:
Android version - 2.3.3
Baseband version - S0833144.TP15.R1090
Kernel version - 2.6.35.7.perf [email protected] #1
Build number - GINDERBREAD
Board and Software version - MSM8260_SURF V1.47
After the OTA upgrade I then proceeded to again root the phone using the same SuperOneClick v2.3.2. Unfortunately, the rooting process always stalled on step 7 and again I tried several times but no luck. I already tried several rooting apps including the link you gave which uses fastboot but still no luck. There is now an update to SuperOneClick which is v2.3.3 but unfortunately still could not root.
I am recommending all those who are still on software version 1.44 to avoid that update in case they intend to root their Racer.
I'm now thinking if there is firmware out there at that Chinese site you had recommended if they have a version 1.44 for download. I am having a hard time translated that Chinese site, moreover that when I attempt to download any file. though I can't understand the Chinese commands, I'm sure the site was requiring me to enter a user name and password which is impossible for me to do and navigate the Chinese site.
Hoping you could help me on with my dilemma.
And that XDA developer gurus could make us a nice custom rom for the IM-A770K.
Rooting update 1.47
Hi
I was also upgrading my phone from 1.45 to 1.47. After upgrading I was also unable to root my phone then I use VR root to root my phone and successes with V1.47. you can download Vr root zip from here
mediafire.com/?a00ct1cofzbaag9
un zip it on your C: drive then using CMD load rooting.exe before it your phone is plug on to your computer and debugging mode must checked.
This method will install busy box, Superuser and su shell on your phone. You can uninstall the applications using unroot.exe
Hi amunaf,
Thank you again for your assistance. Unfortunately VRRoot via its rooting/unrooting.exe still didn't work for my A770K. Please see the rooting messages below:
The A770K is still DISCONNECTED with these messages:
C:\>rooting
C:\>adb remount
C:\>adb push busybox /data/busybox
C:\>adb shell chmod 6755 /data/busybox
C:\>adb push su /system/bin/su
C:\>adb shell "chown 0:0 /system/bin/su"
C:\>adb shell chmod 6755 /system/bin/su
C:\>adb shell /data/busybox ln -s /system/bin/su /system/xbin/su
C:\>adb push Superuser.apk /system/Superuser.apk
C:\>adb shell chmod 644 /system/Superuser.apk
C:\>adb shell mv /system/Superuser.apk /system/app/Superuser.apk
C:\>adb shell rm /data/busybox
C:\>adb reboot
The A770K is already CONNECTED with these messages
C:\>rooting
C:\>adb remount
remount failed: Operation not permitted
C:\>adb push busybox /data/busybox
C:\>adb shell chmod 6755 /data/busybox
Unable to chmod /data/busybox: No such file or directory
C:\>adb push su /system/bin/su
C:\>adb shell "chown 0:0 /system/bin/su"
Unable to chmod /system/bin/su: No such file or directory
C:\>adb shell chmod 6755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\>adb shell /data/busybox ln -s /system/bin/su /system/xbin/su
/data/busybox: not found
C:\>adb push Superuser.apk /system/Superuser.apk
C:\>adb shell chmod 644 /system/Superuser.apk
Unable to chmod /system/Superuser.apk: No such file or directory
C:\>adb shell mv /system/Superuser.apk /system/app/Superuser.apk
failed on '/system/Superuser.apk' - No such file or directory
C:\>adb shell rm /data/busybox
rm failed for /data/busybox, No such file or directory
C:\>adb reboot
I also tried fastbooting and the process just stops and stalls with no activity at all after sending the boot.img.sk.insecure file
C:\>sk
C:\>adb reboot bootloader
C:\>fastboot boot boot.img.sk.insecure
BTW I've already wiped cache partition, wipe data/factory reset and wipe internal sd partition. Unfortunately doing all that did not help. What do you think will happen if I initialize sd partition? I tried it before but it was cut short because my battery was went dead and that process I'm guess could take around 3-4 hours.
I'm still hoping there's still a way to root my phone.
Thanks a lot for the effort and help you've extended!
installing custom rom
You root it again with custom rom using this method below and after rooting use VR rooting. I hope it will work for you.
It also work even your phone brick or do nothing.
Steps:
1 Turn off the phone
2, while holding down the Volume Up (+) button, power button and search button three key until the boot. Screen will display "S / W Download" message.
into the sky's official website, (skyservice.co.kr/jsp/info/DownSW.jsp) find the USB driver just said that the download page, there is an option (vega racer im-770K (upgrade version 1.47)
to upgrade this system is self-vega, vega is popular to say the rom package itself. But can not download, install only online.
3. install USB drivers
The emergence of an icon and a S / W Upgrade after , plug in a USB port on the computer
4: Go to web address:
(dmfile.isky.co.kr/NewSelfUpgrade/index.html)
Note: for above web site use “internet explorer” browser other browser may be not work
Than will be prompted to install the plugin, click to install!
5: Wait for the icon from gray to pink
this process is relatively long, about 10 minutes or so. Until the progress bar has completed, the phone will automatically restart. This phone will return to factory state.You install the program will be cleared away flies, including the root before the operation. But the good news is that the content is still the phone book, photos, still. . .
At this step, your phone seems to back you just start state, then you have to do is to repeat the beginning of the operation of this tutorial. Re-root, again carefully delete unnecessary procedures, may once again face the risk of bricking again ... until the perfect resume ... so
After this you can root you phone via VR rooting
Success!
Hi amunaf,
I want to thank you with all my heart for being so helpful, patient and for the effort you did for the tutorial in solving my dilemma. My vega is finally again rooted! Though I encountered some problems such as a drained battery, slow inerconnect connection during download process (it took around one hour and fifteen mins. to download), etc. To make a long story short, in addition to the live firmware download from SKY, the SK.exe you pointed to download which vame with Vrroot also helped root the phone.
Thank you so so much more power to you!
Hi Guys,
I'm a newbie using a Vega Racer IM-A770K. Could you step by step guide me how to upgrade S/W, how to enter recovery mode.....
Thanks you so much !!!!
Hello, i have Sky Vega A770K with "too many pattern attempts" !
Please help!
Sky IM-A770K utilities
anthony411 said:
Hi Guys,
I'm a newbie using a Vega Racer IM-A770K. Could you step by step guide me how to upgrade S/W, how to enter recovery mode.....
Thanks you so much !!!!
Click to expand...
Click to collapse
Sky Vega Racer IM-A770K utilities
To go into RECOVERY MODE
1. Turn off phone
2. Simultaneously press:
VOLUME DOWN BUTTON
SEARCH BUTTON
Lastly POWER BUTTON
3. Release all three buttons when the SKY VEGA boot logo appears
4. When Android character w/ white triangle (with exclamation point inside) appears, press the MENU soft key (lower left side of the phone’s front face). The Android system recovery menu should appear
5. To choose a function, use the up/down volume buttons on the left side of the phone
6. To select and activate a function, press the SKY soft key
To go into Soft/Ware download mode
1. Turn of phone
2. Simultaneously press:
VOLUME UP button
MENU button
And lastly press the POWER button
3. S/W Upgrading will now flash on the screen
To upgrade firmware to version 1.47, you first need to download and install the USB drivers. You can get it directly from this site:
mediafire.com/?pgjltz97wkgoitj
Or from the Sky site:
http://www.isky.co.kr/sw/swdownloa...oftware/USB&filename=UniUSBDriver_v355[2].zip
When you reach the above page, there will be a java script with two identically sized boxes (Ignore the smaller box beneath the right box). Clicking the right side box will bring up the download box. Save file to computer.
4. After you have installed the drivers, test your phone’s connection to the computer to initially determine all the required drivers were installed properly. But before doing this, make sure that you have activated USB DEBUGGING on your phone.
>settings
>applications
>development
>usb debugging (must be checked)
5. Using Microsoft Internet Explorer v9, proceed to this page:
http://dmfileidc.isky.co.kr/NewSelfUpgrade/index.html
Notice when that page opens, it will prompt you to install ACTIVE X. Allow that installation to proceed.
6. After ACTIVE X has been installed, notice on the left side there is a phrase noting USB with some Korean characters. Underneath that phrase is a clickable rectangular PINK box. If that box is instead colored gray with a rotating circle, that might mean ACTIVE X did not load or install properly. Or you might be using a different browser or maybe something else. Notice the GRAY box is NOT clickable.
7. Clicking the PINK box will turn it into a progressing lavender bar. At this point, put phone into S/W download mode (volume up/ search /power buttons) and connect the A770k to the computer. Notice the characters on top of the progress bar may change and at this point there is communication between the phone and the Sky download site. It may take a few minutes for the phone to establish a download connection between Sky’s services. Once a connection is established, the characters above the progress bar will turn into a progressing percentage bar starting from 1% and ending into 100%.
There will be two phases of the progressing percentage bar. The first phase is downloading the software while the second is loading the v1.47 software into the phone. After the 2nd phase, the phone will automatically reboot. The first phase will depend who slow or fast your internet connection is. My download took around an hour.
As most tutorials here at XDA say, I take no responsibility if something goes bad after performing the above procedure. Do at your own risk. I’ve done this twice and so far so good.
A high performance-price ratio machine
Seems this is a machine that can draw xiaomi（a very hot machine in china mainland) from a so-called best performance-price ratio position. But as you know, software also play very important role in a phone system.
hi everyone ,
I have a Sky Im A 690s. I use the app " gingerbreak" to root and it worked, now my phone rooted. but I can find any recovery and dont know how to flash recovery. anyone know please help me
Hi Guys,
I got a problem when rooting by VRRoot same as Astro49. After upgrade new firmware via OTA (V1.47) then my IM-A770K cant be rooted by VRRoot. So can you guys help me the way to root my phone step by step.
Thanks you
anthony411 said:
Hi Guys,
I got a problem when rooting by VRRoot same as Astro49. After upgrade new firmware via OTA (V1.47) then my IM-A770K cant be rooted by VRRoot. So can you guys help me the way to root my phone step by step.
Thanks you
Click to expand...
Click to collapse
When you downloaded VRRoot, there were also 3 executable files that came with it. KT, LG and SK. With your phone connected to the computer and also necessary drivers installed, run SK but making sure USB debugging is also checked. Then after that process, run again rooting. Hope it'll work for you 'cause that worked for me when I also upgraded to 1.47 via OTA then could anymore root. Good Luck!
I've loaded CWM based recovery by @KD4865 v5.0.2.7 but my nandroid backups dont work. My phone always restores to its factory state. I've already made several backups but every time it goes back to phone's original settings as in I would have to setup from scratch and all my apps and personal data are gone. What could I be missing or doing wrong???
astro49 said:
When you downloaded VRRoot, there were also 3 executable files that came with it. KT, LG and SK. With your phone connected to the computer and also necessary drivers installed, run SK but making sure USB debugging is also checked. Then after that process, run again rooting. Hope it'll work for you 'cause that worked for me when I also upgraded to 1.47 via OTA then could anymore root. Good Luck!
Click to expand...
Click to collapse
Finally, My A770K has been rooted by VRRoot. Thanks you so much
how do root my device? a770s fw 1.47. I unknow about VRRoot. I used SK.exe => screen back to Fastboot Mode. Next stept?
Hi guys,
I got a problem with my im-a770k that is no Restore & Backup, Install file ZIP from SDCard function in Recovery Mode. So I cant use Restore&Backup to restore recovery. Can any one help me solve this problem?
Thanks
---------- Post added at 03:27 PM ---------- Previous post was at 03:17 PM ----------
zongsheng said:
how do root my device? a770s fw 1.47. I unknow about VRRoot. I used SK.exe => screen back to Fastboot Mode. Next stept?
Click to expand...
Click to collapse
You must wait until the PC install new device complete, then your phone automatically reboot. After that your phone is rooted
anthony411 said:
Hi guys,
I got a problem with my im-a770k that is no Restore & Backup, Install file ZIP from SDCard function in Recovery Mode. So I cant use Restore&Backup to restore recovery. Can any one help me solve this problem?
Thanks
---------- Post added at 03:27 PM ---------- Previous post was at 03:17 PM ----------
You must wait until the PC install new device complete, then your phone automatically reboot. After that your phone is rooted
Click to expand...
Click to collapse
How long is PC install new device complete? Can you help me through teamview?
anthony411 said:
Hi guys,
I got a problem with my im-a770k that is no Restore & Backup, Install file ZIP from SDCard function in Recovery Mode. So I cant use Restore&Backup to restore recovery. Can any one help me solve this problem?
Thanks
---------- Post added at 03:27 PM ---------- Previous post was at 03:17 PM ----------
You must wait until the PC install new device complete, then your phone automatically reboot. After that your phone is rooted
Click to expand...
Click to collapse
don't install file rooting.exe after install file SK.exe????
alt link: http://forums.androidcentral.com/sa...-guide-stock-2-3-6-replenish.html#post1651482
REVISED TUTORIAL IN ROOTING 2.3.6 SAMSUNG REPLENISH
warning for experienced adb users!: this was made with noobs in mind. you may learn something (from me! a noob! XD) but anyways, enjoy!
this does not affect anything on the phone except for adding the ability to access root permissions. CWM is not permanent, it disappears after you use it, and nothing on the phone is affected, as far as i know, but i had just factory reset the phone, so use at your own risk...
you may need to know:
root of a drive- drives are designated C:\ or D:\ or whatever letter in windows. Just go to "computer" and double click the first item. That location is the "root" of a drive.
Note: make sure you have at least 400 mb of memory (i know, thats alot, but just in case) on your sd card so you can back up your entire phone! i reccomend doing every optional step!!! It'll save you hassle if you have problems. If you can't make room for some reason, and you still wanna try, you should skip step 8. I don't suggest it though.
1. download "odin.zip" and "su" here: https://www.box.com/shared/620b03e95cc0814fefc8 and unzip to your desktop. if you dont have the android sdk, simply copy the "adb.exe" file from "odin.zip" to the root of your primary drive for later. Just go to "computer" and double click the top icon/item. It should say something about C:/. If you're on Mac, sorry. Idk much about it. As for Linux, I have no clue how you'd even try to do this. I love Linux but, sadly, can't experiment with this in it. WINE has its limits....... And I don't think adb or Odin would work.
2. download the "su" file and put into into "platform-tools" where you installed the android sdk, if you have it, or put onto the root of your primary drive if you havent.
3. start phone while holding "spacebar" and "p". "downloading..." should appear on the screen in yellow text
4. plug into the computer and run "Odin_Multi_Downloader_v4.42.exe"
5. select SPHM580.ops for "OPS" and Replenish-CWM5.tar for "One Package" (they should be the only options) DO NOT CHANGE ANYTHING ELSE!!!!!
6. hit "Start" and DO NOT REMOVE PHONE FROM USB.
7. as the phone reboots, hold "u" until CWM opens and set the phone down. you should close Odin now.
8. use the volume keys to navigate to the backup and restore option and use enter to select backup. wait for it to finish completely and take you back to the the CWM main UI. backing up here creates a pure recovery, untouched by anything. CWM is NOT installed into this recovery. continue with the guide.
9. open the command prompt (type cmd.exe in search or run in the start menu, depending on your version of windows) or use some form of terminal emulator on your operating system of choice. command prompt is preferred due to the fact i know it can get the job done, but do what you will.
10. navigate to the drive your sdk is on and into "platform-tools" or to the folder you put the adb.exe and su files on. the default should be [name of drive]:\Users\[username]\. use the "cd.." command til youre at the root of the drive, and if you installed the sdk, type "cd android-sdk-windows/platform-tools" or just go to the root of the drive and go to the next step if you havent. just be sure adb.exe and su are there.
11. type this in line for line, with enters in between. the blue "~#" in the later lines is the prompt you should have. do not type this. it will be in blue. (clockworkmod should still be open on your phone at this point)
adb shell
~#mount -o remount,rw -t rfs /dev/block/stl12 /system
~#exit
adb push su /system/bin/
adb shell
~#chmod 777 /system/bin/su
~#reboot
DO NOT CLOSE THE COMMAND PROMPT YET FOR THE SAKE OF CONVENIENCE
If you have problems with that, try using CWM to mount "/system". Some friendly people over at androidcentral pointed that out. I personally didn't have that problem, but I'm glad it's fixed.
12. when your phone has rebooted, go back to the open command prompt, which should be where it was before you typed "adb shell"
13. type "adb shell". you will see a prompt of "$." type "su." if you have a prompt of "#" rejoice! you have permanent root! now you can go on the Play Store and find "Superuser" and "Busybox" (they should be free. if you cant find it, get ahold of me and ill try to supply the newest updates) if not, and you have a backup from optional step 2, you should go through til you hit CWM and restore the backup. if not, make one now and reattempt everything aside from downloads and the moving the files around on your computer. Also, someone said something about "chmod 06755 /system/bin/su", so if you might try using that instead of "chmod 777 /system/bin/su". 777 worked for me, but maybe this works better for you.
OPTIONAL FINISH STEP: I dont know how you install CWM permanently, but you should do this so you can make backups of your rom and store them somewhere like on a box.com or mediafire.com account if you decide to mess with something on your phone. (use hjsplit to break it into pieces for uploading and reassemble after download for flashing if its too big). to use a recovery, enter CWM (either the way i have here or if you have permanently installed, just reboot and hold "u") and navigate to "backup and restore," "restore," and select the recovery you wish to use on your sd card (make sure when you take out a backup for storage, you zip up the entire folder with the name that contains the date and time of your backup.) it will overwrite everything on your phone to be exactly like it was when you backed it up.
good luck! have fun!
Note: if you rename the CWM backup file, make sure it DOESN'T HAVE A SPACE or it'll give you something about md5 or something not matching. If it says this, remove any spaces in the name and try again. I had it happen on my xperia play and freaked, thinking it was soft-bricked permanently one time, til I found out about cwm's glitch with that.
Also, I uploaded pretty much everything needed for rooting the phone, with comments pertaining to each file. This includes current (as of July 31, 2012) copies of Superuser.apk, a busybox installer, and the busybox and su binaries, as well the Odin package containing the tools to temp flash CWM.
the odin.zip file and the process of achieving CWM temp-flashing was found at http://forums.androidcentral.com/sa...method-samsung-replenish-android-2-3-6-a.html and credit for that part is given to joshua.worth, although I took it a different path than he did.
Update to above info: to simplify things, I uploaded all relevant files to box so people can get them easier. The su file went missing from xda, most importantly, so I fixed that, and added an updated binary in case someone has trouble with the other one.
contact me at [email protected] if you cant pm me.
Sorry if it takes a while to respond. Life's been kinda crazy for me lately, and I am using my new phone (no service) to do this over wifi.
ahh... well, turns out unrooting cannot be done with a CWM backup... you probably have to find a nandroid or a clean version of kernel with rom. the su file dissapears, although root is still there. ill keep playing with it, i have an idea why root stays although su disappears from the system files. anyways, i will still supply a backup thats pre-rooted for anyone who is willing to have a fresh start on their replenish. it will have superuser.apk preinstalled along with busybox, and everything else will be wiped. this will be a sprint backup, so if anyone has the boost version and is willing to back up with CWM and factory reset, then follow my guide, install busybox and superuser.apk, then back it up again, id be eternally grateful to have a copy
by the way, if anyone has problems with restoring a backup due to "md5" tags or whatever it is, make sure the name of the backup has no spaces. i was freaking out til i found that tip on an obscure forum (well, to me. i dont have a Motorola. lol. just a Sony Ericsson and 2 Samsungs)
update: sorry i havent uploaded the backup. i realized it would give whoever used it the number on this phone and i have to fix that. havent had time to anyways, plus it would only work on a sprint phone. it would convert any boost mobile to sprint, so thats a no-go. sorry...
does this work for the boost mobile replenish that is 2.3.6 if so how long does it take to odin
It should work. And Odin just flashes cwm (really fast) for the duration of the next boot cycle, which it automatically initiates, so hold the recovery button (I think it's u) as it goes into it and you'll have temp root. Make sure it's in download mode before you start. Remember, it cannot be unrooted, so if you value your warranty, plz think twice before doing it. I'm just here to supply the how-to if you decide to, not to say you have to. If you do, enjoy root access!
isavegas said:
It should work. And Odin just flashes cwm (really fast) for the duration of the next boot cycle, which it automatically initiates, so hold up (I think it's u) as it goes into it and you'll have temp root. Make sure it's in download mode before you start. Remember, it cannot be unrooted, so if you value your warranty, plz think twice before doing it. I'm just here to supply the how-to if you decide to, not to say you have to. If you do, enjoy root access!
Click to expand...
Click to collapse
Thanks. I did not know if there is a fail safe if something went wrong. so I was second guessing. Very simple to do thank you assuming with odin I made a back up. if I where to mess my system up I can use odin and restore my backup and I be back up and running again no need to sbf
i keep getting : ~ # mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount: mounting /dev/block/mtdblock3 on /system failed: Invalid argument
bscabl said:
i keep getting : ~ # mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount: mounting /dev/block/mtdblock3 on /system failed: Invalid argument
Click to expand...
Click to collapse
hmm... i am familiar with the error (ive gotten it with 3 different phones in my attempt to root it, but i have succeeded each time regardless) but are you sure you actually have clockworkmod OPEN on your phone when the error shows up? i cant actually do anything from my end, because i no longer have a computer i can use to test anything, or the replenish i rooted with the method... but i opened the cwm several times before thinking to test the adb and seeing the "~#". i actually restarted the phone and did it again before actually rooting it, seeing if i had rooted it or what, and tho i got the same prompt every time it was booted in cwm, it wouldnt show up if i allowed the phone to boot normally after using odin, i HAD to ACTUALLY boot into the cwm menu, which is completely seperate from the OS itself, although it has access to the system files.
by the way, copy and paste this directly into the command prompt when you get to the step to avoid human error. mount -t rfs -o remount,rw /dev/block/stl9 /system
or, if it wont work, try this mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
sorry bout the babbling XD. anyways, cwm should be circumnavigating the root permissions. hmm.... if you still have problems after that, try skipping to the adb push for the "su" file.
sorry i havent been on top of the thread. ill set up an email notification.
and by the way, something i found very useful on my xperia play when it went into infinite reboot, you can always just restore the system files in the advanced restore option, allowing you to keep all of your app data if, later down the line, your phone needs to be restored. hope this helps. it helped me XD thought id lose all of my messages, but nope. i decided to explore the advanced restore and yay! i got to keep them XD
UPDATE
I don't know if it matters to you anymore, but apparently, some people have trouble with this and fix it by going to the mount menu in CWM and mounting /system
Couple of corrections:
chmod 777 /system/bin/su
should be chmod 06755 /system/bin/su
and then following that command should be
ln -s /system/bin/su /system/xbin/su
and I saw someone say this is unrootable. Thats not correct. Simply running the unroot script would unroot. Doomlord made a nice one.
To use it do the following:
Code:
adb push unroot /data/local/
adb shell chmod 777 /data/local/unroot
adb shell su -c "/data/local/unroot"
adb reboot
[code]
The above will unroot almost any android device.
halfcab123 said:
Couple of corrections:
chmod 777 /system/bin/su
should be chmod 06755 /system/bin/su
and then following that command should be
ln -s /system/bin/su /system/xbin/su
and I saw someone say this is unrootable. Thats not correct. Simply running the unroot script would unroot. Doomlord made a nice one.
To use it do the following:
Code:
adb push unroot /data/local/
adb shell chmod 777 /data/local/unroot
adb shell su -c "/data/local/unroot"
adb reboot
[code]
The above will unroot almost any android device.[/QUOTE]
Unfortunately, Doomlord's method didn't work on it. I tried all manner of one clicks and manual versions and only this got even temporary root. It's a workaround based on forcing the phone to boot into a custom recovery. (I call it custom bc its not an "official" recovery.) And I chose the chmod by looking through many manual ways to root, and that one was popular, and it works. I had full root access afterwards. I tried to unroot afterwards, however, so I could take screenshots and stuff, but the su file would reappear, even after manual deletion or restoring to an unrooted backup. Anyways, point is, this is the only method I could get to work at all, and it does work.
But the "chmod" night help other people, so ill make note of it in the post just in case. Thanks for the info.
Sent from my rooted R800at using xda app-developers app
Click to expand...
Click to collapse
Important fix----
If step 11 doesn't work, go to the "mount" menu in cwm and mount /system. Some people on androidcentral were kind enough to mention that this fixed their problem with mounting /system as rewritable
Sent from my R800at using xda app-developers app
isavegas said:
Important fix----
If step 11 doesn't work, go to the "mount" menu in cwm and mount /system. Some people on androidcentral were kind enough to mention that this fixed their problem with mounting /system as rewritable
Sent from my R800at using xda app-developers app
Click to expand...
Click to collapse
thats because your command is wrong
shabbypenguin said:
thats because your command is wrong
Click to expand...
Click to collapse
How? Throughout my own rooting of one of the phones, I had this working perfectly. Every time I hit a snag, I found a way around it and documented it. A few other people had errors show up because the phone itself hadn't mounted the system, but the problem was resolved, and only a couple people had any other problems, and they were unrelated to that. I assure you, every command works properly, as far as I know.
exactly my point. your command to mount system is wrong.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
lets break it down shall we?
mount - this is teh command
-o remount,rw - this is where you tell it what option you want, in this case remounting as rw.
-t yaffs2 - here you are telling mount that it should expect a yaffs2 formatted device, which is not what the samsung replenish is. the replenish uses RFS (robust file system), the best way i can describe it is like telling your windows computer that your hard drive is fat32 when its actually ntfs.
/dev/block/mtdblock3 - this is where you tell mount what you are looking to mount, the issue here is that the replenish doesnt use MTD blocks, it uses STL's and BML's.
/system here is where you are trying to mount the said device to..
out of 5 parts you did get 3 correct tho. you might wish to modify your guide to reflect the actual mount command, for your device it is the following:
mount -o remount,rw -t rfs /dev/block/stl12 /system
and that will kick out system as r/w
shabbypenguin said:
exactly my point. your command to mount system is wrong.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
lets break it down shall we?
mount - this is teh command
-o remount,rw - this is where you tell it what option you want, in this case remounting as rw.
-t yaffs2 - here you are telling mount that it should expect a yaffs2 formatted device, which is not what the samsung replenish is. the replenish uses RFS (robust file system), the best way i can describe it is like telling your windows computer that your hard drive is fat32 when its actually ntfs.
/dev/block/mtdblock3 - this is where you tell mount what you are looking to mount, the issue here is that the replenish doesnt use MTD blocks, it uses STL's and BML's.
/system here is where you are trying to mount the said device to..
out of 5 parts you did get 3 correct tho. you might wish to modify your guide to reflect the actual mount command, for your device it is the following:
mount -o remount,rw -t rfs /dev/block/stl12 /system
and that will kick out system as r/w
Click to expand...
Click to collapse
Hmmmm.... Odd..... *shrugs* I had no problem with the command, but I guess other ppl had pickier computers or phones. Hell, Vista's buginess might have worked in my favor that time XD. Thanks for the pointer. I didn't really understand the exact way the replenish was built. I just found a lil guide for making it boot into cwm and found it allowed for me to use that as an exploit to root the device. In fact, I've done the same kind of stuff to root the samsung Intercept, except I made their own software flash a pre-rooted kernel. anyways, I'll update the guide on xda and androidcentral. Thanks!
isavegas said:
Hmmmm.... Odd..... *shrugs* I had no problem with the command, but I guess other ppl had pickier computers or phones. Hell, Vista's buginess might have worked in my favor that time XD. Thanks for the pointer. I didn't really understand the exact way the replenish was built. I just found a lil guide for making it boot into cwm and found it allowed for me to use that as an exploit to root the device. In fact, I've done the same kind of stuff to root the samsung Intercept, except I made their own software flash a pre-rooted kernel. anyways, I'll update the guide on xda and androidcentral. Thanks!
Click to expand...
Click to collapse
chances are you had system mounted in cwm without knowing it.
for future knowledge always check the devices fstab for where to mount and filesystem type
https://github.com/Shabbypenguin/android_device_replenish/blob/master/recovery/recovery.fstab
as you can see the proper mounts from the files i used to make CWM for the replenish
shabbypenguin said:
chances are you had system mounted in cwm without knowing it.
for future knowledge always check the devices fstab for where to mount and filesystem type
https://github.com/Shabbypenguin/android_device_replenish/blob/master/recovery/recovery.fstab
as you can see from the files i used to make CWM for the replenish the proper mounts
Click to expand...
Click to collapse
Eh, maybe. For all I know the first thing I did was mount everything with cwm. I DID do this several months ago. I don't even have the phone anymore. The owner of the phone was gonna give it to me after upgrading, but she sold it, so I kept her 500gb laptop hard drive instead. Popped it out of the external hdd casing and stuck it in a laptop. XD. It now has Linux on it.
Anyways, I've updated the guide to have the right command and note that if it doesn't work to use cwm to mount /system. And how do you find the fstab? Just Google it? Or is it somewhere on the device?
Btw, do you know anything about cwm? It refuses to properly back up my xperia play anymore. The .android_secure folder keeps giving it errors.
isavegas said:
Eh, maybe. For all I know the first thing I did was mount everything with cwm. I DID do this several months ago. I don't even have the phone anymore. The owner of the phone was gonna give it to me after upgrading, but she sold it, so I kept her 500gb laptop hard drive instead. Popped it out of the external hdd casing and stuck it in a laptop. XD. It now has Linux on it.
Anyways, I've updated the guide to have the right command and note that if it doesn't work to use cwm to mount /system. And how do you find the fstab? Just Google it? Or is it somewhere on the device?
Btw, do you know anything about cwm? It refuses to properly back up my xperia play anymore. The .android_secure folder keeps giving it errors.
Click to expand...
Click to collapse
its where the recovery is on the device. each device has their own fstab. as for your error sounds like a conflict, either with cwm itself or that folder
shabbypenguin said:
its where the recovery is on the device. each device has their own fstab. as for your error sounds like a conflict, either with cwm itself or that folder
Click to expand...
Click to collapse
It HAS to he cwm, because the folder is regarded as super hidden by the device. The folder itself can be seen, but the contents can ONLY be edited by the rom or a pc, and I haven't touched it with a pc before. It's where your apps go when you move them to the sd card. I've been trying to back my phone up with cwm because I wanted to test the jelly bean alpha release for it. its the xperia play 4g. Stupid backup crashes every time I try and it ends up eating up what room is left in my sdcard.
i followed your guide and have root in shell. however i cant get root permission on any apps, the window doesnt pop up asking me for permission. i also get a toast notification saying superuser access denied for whatever app im trying to open. any ideas?
arodey said:
i followed your guide and have root in shell. however i cant get root permission on any apps, the window doesnt pop up asking me for permission. i also get a toast notification saying superuser access denied for whatever app im trying to open. any ideas?
Click to expand...
Click to collapse
What does your Superuser log show?
Sent from my PC36100
hello guyz i am having a big problem that is my device in in factory mode and there isnt power menu and there isnot a lock screen i tried a lot of solutions but the big problem that my efs folder is empty and i havent any backup cause my device was bootlop on samsung screen so i flashed a ics rom via odin and all the backups i have it to jb i tried to restore a one and its the same please help me I tried To Flash A New frimware and the same
Search via Google >>> Note 10.1 factory mode xda
bilal.23 said:
hello guyz i am having a big problem that is my device in in factory mode and there isnt power menu and there isnot a lock screen i tried a lot of solutions but the big problem that my efs folder is empty and i havent any backup cause my device was bootlop on samsung screen so i flashed a ics rom via odin and all the backups i have it to jb i tried to restore a one and its the same please help me I tried To Flash A New frimware and the same
Click to expand...
Click to collapse
If you don`t have an efs backup, then unfortunately there is nothing you can do except sending it to a service center, happened to me almost 6 months ago, tried all options , nothing was successful, had to send it for repair.:crying:
bilal.23 said:
hello guyz i am having a big problem that is my device in in factory mode and there isnt power menu and there isnot a lock screen i tried a lot of solutions but the big problem that my efs folder is empty and i havent any backup cause my device was bootlop on samsung screen so i flashed a ics rom via odin and all the backups i have it to jb i tried to restore a one and its the same please help me I tried To Flash A New frimware and the same
Click to expand...
Click to collapse
Here is the exact solution for this problem which i have recently had!
You have to root your phone and install Terminal Emulator from Google Play.
Open terminal emulator and type as ;
su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot
You now should not see the that message anymore. Its because of an EFS corruption.
Hope it helps!!!
So, I mistakenly used Ez-Unlocker with 4.4.2 and bricked my GS III. Based on various posts found around here I was able to get it running again. However, no matter how many times I try to reset the phone, either through Odin or the Verizon repair utility, this is what I get:
[[http]] [[://]] www [[dot]] ledzilla [[dot]] us/images/Screenshot_2014-07-19-14-13-55.png
I've tried various methods I've found to resolve this, but the best I've managed was to delete a trio of apps from the phone with the name "Factory Mode" and "Factory Test", but all that accomplished was getting rid of the yellow text that persists across the home screen. I still got the the warning box at the bottom of the screen.
So, is there a way to completely fix this with the phone being on the latest firmware and OS?
Also, on a side note, I received a warranty replacement because I didn't realize it was EZ-Unlocker that caused the problem until I did it on the replacement, too. I was able to restore it back to working condition, too, and without the factory mode issue, except the same exact process caused the EFS data to get corrupted so now there's no IMEI. Here's a screen shot of the system data (there's no SIM card installed, so I don't know if that affects some of these values):
[[http]] [[://]] www [[dot]] ledzilla [[dot]] us/images/Screenshot_2014-07-19-19-37-44.png
Is there any way to fix this issue, too?
And sorry about the links, but I'm assuming most here would know why it's all chunked up like that.
I should also mention that in order to resolve the issue I have rooted using Towleroot, and I installed Superuser for, well, super user rights. In conjunction with this, I also accessed the phone using the ADB shell and entered the following:
Code:
su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot
I was able to confirm changes to the files, but it effected no change on the situation. The yellow text did not go away and the "Factory Mode" message still appeared at reboot and shut off the WiFi.