Scroll to the bottom for a fix to the newest clockwork recovery flasher...
UPDATING TO DI07
First things first, you must update to the latest firmware and kernel, but in order to do this you must un-root and return to the stock kernel in order to avoid problems.
Simply download the zip here, and run the run.bat inside, after extracting the folder to your desktop.
You must have debugging mode enabled for this to work.
Once that's finished you can update to DI07 using the stock recovery. You do this, like any other update, by renaming the zip (found here, to update.zip on throwing it onto the root of your sdcard.
Then, boot up into the stock recovery (power+camera+volume down) and press home to apply the update.zip.
The update will install and your phone will reboot into DI07.
First boot will take some time, so be patient.
Now onto the fun part, rooting your phone.
OBTAINING ROOT
Just as you obtained root before DI07, you obtain root on DI07, if you have the right tools. Download the one click root here, and once more extract the included folder to you desktop, make sure you have usb debugging enabled, and run the run.bat. Your phone will reboot, and you will have root.
FLASHING CUSTOM RECOVERY
Here is where it gets a tad bit more complicated. First off, you have to download the zip here, but this time before running the bat you have to open up command prompt and redirect it to your C:/android-sdk-windows/tools folder and then run the following code.
adb devices
adb shell
su
remount rw
exit
exit
Now the command prompt should close, and you can run the run.bat for build 31 of clockwork recovery flasher. Once more, your phone will reboot and after the script is done running and says "press any key to exit...." you can press enter and boot into recovery.
That's it, three simple steps to updating, obtaining root, and flashing clockwork recovery!
Also, don't forget to check out my ROM coming later today, as well as noobnl's Andromeda Galaxy ROM v1, just released.
great tutorial...and i can use these instructions even if i am using aridons v4 rom and heros overclocked kernel?
Well, it basically reverts you back to the stock kernal, so you will for sure lose the overclocked kernal. However, I'm not sure about the ROM. Your best bet would be either to hold off on this as the ROM you are suing isn't based on DI07, or flash to stock and then follow this guide. Your choice.
bubby323 said:
Well, it basically reverts you back to the stock kernal, so you will for sure lose the overclocked kernal. However, I'm not sure about the ROM. Your best bet would be either to hold off on this as the ROM you are suing isn't based on DI07, or flash to stock and then follow this guide. Your choice.
Click to expand...
Click to collapse
Well I just ran this and at first glance, it got me right into clockwork. I selected one of my nandroid and restored it. After the phone finished restoring and everything, I wanted to make sure that I still had clockwork but instead it was stock recovery once more.
Since I still had root, I redid the steps starting with entering the commands, then I re-ran the bat file for clockwork. I checked and clockwork is back...unknown as to how long though.
Thank you!!! the remount rw was what I needed to get the clockwork custom recovery to flash!!!
I have another question for you? Is it possible to install the custom recovery without having root? I suspect not? The reason I ask is that I would like to have a nandroid backup of the completely stock rom although I guess I could use the one noobnl has posted
well, i got back to a stock rom....applied the stock kernal...but when i went to apply the update.zip...it took me back to clockwork...not the stock recovery....so i tried to apply the update from there but it aborted...how do i get rid of clockwork so i can go into stock recovery and will that fix it?
mrkrabs said:
well, i got back to a stock rom....applied the stock kernal...but when i went to apply the update.zip...it took me back to clockwork...not the stock recovery....so i tried to apply the update from there but it aborted...how do i get rid of clockwork so i can go into stock recovery and will that fix it?
Click to expand...
Click to collapse
Three options I can think of- if you use adb reboot recovery I believe it will load the stock recovery- the other option is to use odin to go back to complete stock. Finally you could use the option for clockwork in this thread look for the link under "B]Update.zip (for clockwork recovery and includes all the listed apps below)"
EDIT: I can confirm that "adb reboot recovery" loads the stock recovery when you have clockwork
bubby323 said:
FLASHING CUSTOM RECOVERY
Here is where it gets a tad bit more complicated. First off, you have to download the zip --- but this time before running the bat you have to open up command prompt and redirect it to your C:/android-sdk-windows/tools folder and then run the following code.
adb devices
adb shell
su
remount rw
exit
exit
Now the command prompt should close, and you can run the run.bat for build 31 of clockwork recovery flasher. Once more, your phone will reboot and after the script is done running and says "press any key to exit...." you can press enter and boot into recovery.
Click to expand...
Click to collapse
Im having a little issue with this. Im running windows 7. Can I do this in windows 7? Also when it says redirect it to your C:/Android---- do I have to change the drive to ex. cd c:/ first or do i just type in the command prompt C:/android-sdk-windows/tools and hit enter and follow the rest of the commands? Sorry extreme noob here..
Thank you for any help!!
I have ClockworkMod Recovery installed, how can I get into the stock recovery to apply this?
Look 2 posts up
Sent from my SPH-D700 using XDA APP
You need to use the DG27 uninstaller instead of the DI07 uninstaller to update to DI07.
The DI07 uninstaller is just to go back to stock DI07 kernel if you already updated
DG27 uninstaller: http://www.sdx-downloads.com/devs/noobnl/one.click.stock.&.root.uninstallerv1.0.1.zip
I think it needs to be pointed out that this alone won't work if you are like me and have removed apps from the phone. All those apps must be restored in addition to reverting to stock kernel before the OTA update can be applied. At least that's how I understand it. Feel free to correct me if I'm wrong.
Thanks a lot, I appreciate step-by-step tutorials like this for noobs like myself ... this made things a lot easier since some of the stuff (files, instructions, etc.) was all over the place.
would seem that way because I removed the alarmclock to start and when i try to run update.zip from sd it fails when checking current system @ /system/app/AlarmClock.odex
i tried rerooting and reinstalling alarm clock using the backup from titanium. says it is successful but i do not find it in my apps drawer. it still fails there too..
WisdomWolf said:
I think it needs to be pointed out that this alone won't work if you are like me and have removed apps from the phone. All those apps must be restored in addition to reverting to stock kernel before the OTA update can be applied. At least that's how I understand it. Feel free to correct me if I'm wrong.
Click to expand...
Click to collapse
Titanium backup does not restore apps in /system. You have to restore those by hand.
Im officially struggling, undid the root then copy/paste the update to the sdcard, renamed it. It unzips but says its failed to open /sdcard/update.zip(no such file or directory)...suggestions?
I know that in the step it said to copy it to the root on the sd but im am very green to this stuff, and didnt see a folder marked that, therefore I just copied it to the sd card
I can't get Clockwork to flash now. I walked through the steps...I did the remount crap and ran the bat and it rebooted the phone but when i reboot into recovery it goes to the normal recovery screen. Now if I try to redo it it does not recognize the remount rw and i can't get anywhere with it and i'm stuck with no clockwork.
but this time before running the bat you have to open up command prompt and redirect it to your C:/android-sdk-windows/tools folder and then run the following code.
adb devices
adb shell
su
remount rw
exit
exit
Click to expand...
Click to collapse
This part is unnecessary because the recovery zip comes with adb built in
is there a manual way to push this to the phone? These one clicks never seem to work for me ever it's just easier to do it myself.
Whosdaman said:
This part is unnecessary because the recovery zip comes with adb built in
Click to expand...
Click to collapse
No you must do this in order to get clockwork.
Related
This will be an often-updated guide to getting the most out of the Eclair (Android 2.1) that comes stock on the Kyros 2015.
Things we have working: Root, Market, Texting via Google Talk.
Things we have kinda working: Connecting to Ad-Hoc networks
Things that do not work/Issues: Contacts crashes if you try to edit.
Further Reading:
Most of the development for the Kyros 7015 has taken place in this thread.
Also check out my tutorial on installing CyanogenMod onto this same device.
Instructions
1. If you haven't already rooted, download the official update.zip from Coby. Reboot into recovery and choose "apply sdcard:update.zip" to apply the update.
If you have already rooted, downloaded the modified update.zip, which works with clockwordmod. Reboot into recovery and make a backup. Once your back is complete, choose "apply sdcard:update.zip" to apply the update.
2: Rooting Your Tablet. Download z4root 1.3.0 APK and place on your sdcard. Open Settings, go to Applications and check the Unknown Sources box. Use File Manager to navigate to the z4root APK (it's in the /sdcard folder) and click to run. You should now have root access (you may need to reboot). You will also notice a new app, Superuser, has been installed.
3. Installing ClockworkMod. You must complete this step even if you already had ClockworkMod installed, as the update.zip has replaced it with the stock recovery. If you have not already, install Android SDKto your PC, so you will be able to issue ADB commands. Download ClockwordMod. Open the ZIP file and extract the IMG. For simplicity, rename the IMG file "recovery.img" and place on your SDcard. From ADB,issue the following commands:
Code:
adb remount
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
adb shell
flash_image recovery /sdcard/recovery.img
4: Enabling Google Apps, such as Market. Download gapps-passion-EPE54B-signed.zip and place onto your SD card and reboot into recovery. Choose "Install Zip from SDcard" and install gapps-passion-EPE54B-signed.zip. Reboot and accept the terms of the market!
5: Texting using Google Voice. Here is how to text with Google voice. You will need a working android phone (probably needs to be rooted) with Titanium Backup installed. Set up Google Voice on the phone-- make sure you opt for the Google phone number as that is the number you will be texting from. Once up and running, back up the program using Titanium. On the tablet, install Titanium Backup and use it to restore the Google Voice program (App+Data) to your tablet. (You may have to copy the backup files to the Titanium directory on the INTERNAL drive.) Once Google Voice Launches, switch back to Titanium Backup-- do not try to set up Google Voice. Titanium backup will then restore the data for Google Voice. You should now be able to text from your tablet.
6: Work-around for Connecting to Ad-Hoc Networks. If your Ad-Hoc network is an Android phone, download and install Wireless Tether to the phone (this version works well). Follow instructions in this thread to install work-around on your tablet.
This is all I have right now, more to follow. I hope I didn't forget anything!
Is CWM installed the same way as you would apply the update.zip firmware from Coby?
jmfrost said:
Is CWM installed the same way as you would apply the update.zip firmware from Coby?
Click to expand...
Click to collapse
Sorry, I had a fragment of another post mixed in there. See step three for complete details.
Google Apps
I followed the directions and every thing worked except I only have google maps from the google apps. No Market. Any help would be appreciated.
tpace75 said:
I followed the directions and every thing worked except I only have google maps from the google apps. No Market. Any help would be appreciated.
Click to expand...
Click to collapse
First off, you what tablet are you using?
The gapps-mdpi-tiny-20101020-signed.zip has vending.apk (the market) in it, if properly installed according to the steps provided, it should be working.
But since it is not, here is my suggestion.
1. Reboot into clockworkmod
2. Wipe Cache Partition -- Make sure you choose yes from the menu.
3. Choose Advanced and then Wipe Dalvik Cache -- Make sure you choose yes from the menu.
4. Choose "Install Zip from SDcard" and select gapps-mdpi-tiny-20101020-signed.zip -- Make sure you choose yes from the menu.
5. Choose "Install Zip from SDcard" and select MarketUpdateFroyoHdpi.zip -- Make sure you choose yes from the menu.
6. Reboot
You should now have market.
Google Apps
Thanks that seemed to do it. I have the Kyros Mid-7015. One thing though both times I install those zip files I lose root. And have to reroot. Thanks Again
tpace75 said:
Thanks that seemed to do it. I have the Kyros Mid-7015. One thing though both times I install those zip files I lose root. And have to reroot. Thanks Again
Click to expand...
Click to collapse
Are you losing root or just losing clockworkmod? If this is the case, it is a known issue that the update (step one) overwrites clockworkmod on reboot, and that is why we have more than just the one line of code for installing clockworkmod.
From ADB:
Code:
adb remount
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
adb shell
flash_image recovery /sdcard/recovery.img
If clockworkmod is what you are having issues with, that should make it say put.
Using MarketUpdateFroyoHdpi with 2.1
I have already installed gapps-passion-EPE54B-signed.zip to get Market. Can I upload MarketUpdateFroyoHdpi.zip to my SDcard and use your ClockworkMod instruction: "Choose "Install Zip from SDcard" and select MarketUpdateFroyoHdpi.zip" to get the new version of Market.
I was reading in original development thread for Kyros 7015 that their might be some problems with the new version of Market. Would the Update Market problems be true for 2.1 version of Android as well?
I am using Kyros 7015 with Coby's update, gapps-passion-EPE54B-signed.zip installed, and various apps installed by AppsLib, side loading, and Market.
lschroeder said:
I have already installed gapps-passion-EPE54B-signed.zip to get Market. Can I upload MarketUpdateFroyoHdpi.zip to my SDcard and use your ClockworkMod instruction: "Choose "Install Zip from SDcard" and select MarketUpdateFroyoHdpi.zip" to get the new version of Market.
I was reading in original development thread for Kyros 7015 that their might be some problems with the new version of Market. Would the Update Market problems be true for 2.1 version of Android as well?
I am using Kyros 7015 with Coby's update, gapps-passion-EPE54B-signed.zip installed, and various apps installed by AppsLib, side loading, and Market.
Click to expand...
Click to collapse
MarketUpdateFroyoHdpi only unlocks some previously restricted apps in the market. We do not have the new version of the market running on this device yet.
Also, I believe I misspoke in my directions to use that file in the market process, a result of me copying an pasting from my other guide. I will fix this immediately.
adamdietrick said:
MarketUpdateFroyoHdpi only unlocks some previously restricted apps in the market. We do not have the new version of the market running on this device yet.
Also, I believe I misspoke in my directions to use that file in the market process, a result of me copying an pasting from my other guide. I will fix this immediately.
Click to expand...
Click to collapse
Since my Market is somewhat restricted, I could load MarketUpdateFroyoHdpi to my SDCard and install it from ClockworkMod to remove some of my restrictions.
lschroeder said:
Since my Market is somewhat restricted, I could load MarketUpdateFroyoHdpi to my SDCard and install it from ClockworkMod to remove some of my restrictions.
Click to expand...
Click to collapse
Give it a shot (do a backup first), let me know how it turns out. However, I do believe that MarketUPdateFroyoHdpi only unlocked gapps-mdpi-tiny-20101020-signed.zip to the same extent that gapps-passion-EPE54B-signed.zip is already unlocked, so I doubt that it would do any good.
adamdietrick said:
Give it a shot (do a backup first), let me know how it turns out. However, I do believe that MarketUPdateFroyoHdpi only unlocked gapps-mdpi-tiny-20101020-signed.zip to the same extent that gapps-passion-EPE54B-signed.zip is already unlocked, so I doubt that it would do any good.
Click to expand...
Click to collapse
I backuped my tablet to the SDcard using ClockworkMod yesterday. No major changes made since then. I only used it to surf web and play music and videos.
In case something goes wrong. I have never recovered from a backup of the my tablet before. I assume that their is an option to recover from the backup folder created by ClockworkMod. I assume some data from my use would be lost, but nothing meaningful to me. Is that correct?
A couple more questions. Is the major difference between gapps-mdpi-tiny-20101020-signed.zip and gapps-passion-EPE54B-signed.zip that the later has Market unlocked and has addtional applications as well as applications that do not work on our Kyros 7015? Thus using gapps-mdpi-tiny-20101020-signed.zip and MarketUPdateFroyoHdpi,zip would give a cleaner but more complicated install for 2.1.
lschroeder said:
I backuped my tablet to the SDcard using ClockworkMod yesterday. No major changes made since then. I only used it to surf web and play music and videos.
In case something goes wrong. I have never recovered from a backup of the my tablet before. I assume that their is an option to recover from the backup folder created by ClockworkMod. I assume some data from my use would be lost, but nothing meaningful to me. Is that correct?
A couple more questions. Is the major difference between gapps-mdpi-tiny-20101020-signed.zip and gapps-passion-EPE54B-signed.zip that the later has Market unlocked and has addtional applications as well as applications that do not work on our Kyros 7015? Thus using gapps-mdpi-tiny-20101020-signed.zip and MarketUPdateFroyoHdpi,zip would give a cleaner but more complicated install for 2.1.
Click to expand...
Click to collapse
A backup will backup everything, even your cache.
I have noticed no differrence between the different installations, I just go with what works-- gapps-passion-EPE54B-signed.zip works with 2.1.
adamdietrick said:
Are you losing root or just losing clockworkmod? If this is the case, it is a known issue that the update (step one) overwrites clockworkmod on reboot, and that is why we have more than just the one line of code for installing clockworkmod.
From ADB:
Code:
adb remount
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
adb shell
flash_image recovery /sdcard/recovery.img
If clockworkmod is what you are having issues with, that should make it say put.
Click to expand...
Click to collapse
No I still have clockwork recovery but I lost root. I just rerooted with z4root.
tpace75 said:
No I still have clockwork recovery but I lost root. I just rerooted with z4root.
Click to expand...
Click to collapse
Thanks for confirming that.
3. Installing ClockworkMod. You must complete this step even if you already had ClockworkMod installed, as the update.zip has replaced it with the stock recovery. If you have not already, install Android SDKto your PC, so you will be able to issue ADB commands. Download ClockwordMod. Open the ZIP file and extract the IMG. For simplicity, rename the IMG file "recovery.img" and place on your SDcard. From ADB,issue the following commands:
Code:
adb remount
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
adb shell
flash_image recovery /sdcard/recovery.img
I really don't know how to use this ADB. From my computer, from Coby or?
Please help me!
Thank you!
hayted7 said:
3. Installing ClockworkMod. You must complete this step even if you already had ClockworkMod installed, as the update.zip has replaced it with the stock recovery. If you have not already, install Android SDKto your PC, so you will be able to issue ADB commands. Download ClockwordMod. Open the ZIP file and extract the IMG. For simplicity, rename the IMG file "recovery.img" and place on your SDcard. From ADB,issue the following commands:
Code:
adb remount
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
adb shell
flash_image recovery /sdcard/recovery.img
I really don't know how to use this ADB. From my computer, from Coby or?
Please help me!
Thank you!
Click to expand...
Click to collapse
You will need to install the Androik SDK on your computer-- extract the files to your desktop for simplicity. Then connect your tablet to your PC via USB cable. On your PC, open a command prompt window and enter the following commands:
Code:
cd desktop
cd tools
adb remount
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
adb shell
flash_image recovery /sdcard/recovery.img
Backup
adamdietrick said:
Instructions
1. If you haven't already rooted, download the official update.zip from Coby. Reboot into recovery and make a backup. Once your back is complete, choose "apply sdcard:update.zip" to apply the update.
Click to expand...
Click to collapse
Thank you for posting these instructions.
I am sorry to say I am stuck on #1. Can you please explain how to "Reboot into recovery and make a backup". I don't see a backup option. Thanks.
niki2008 said:
Thank you for posting these instructions.
I am sorry to say I am stuck on #1. Can you please explain how to "Reboot into recovery and make a backup". I don't see a backup option. Thanks.
Click to expand...
Click to collapse
Good point, you can reboot into recovery but you likely can't make a backup without having clockworkmod installed.
Here is what we will do:
Hold down the Back Button (on the front) and then use the stylus to momentarily press the reset button (on the back). Keep holding the back button until you see the recovery screen. Don't worry about the backup, just install zip from card.
WARNING: IN THE EVENT THAT ANYTHING GOES WRONG, I WILL NOT BE HELD ACCOUNTABLE. I CANNOT STRESS THIS ENOUGH!!!
EDIT: I FORGOT, BEFORE CHANGING RECOVERY OR DOING ANYTHING, ALWAYS DO A NANDROID BACKUP!!!
If you have flashed a custom recovery (clockwork, j_r0dd, etc.) but you want to
1) accept OTA updates but cant do so with the custom recovery
2) send your phone for repair and not void your warranty
3) or UNROOT YOUR PHONE,
it should be easy to revert back to your stock recovery that came with your phone.
NOTE: THIS PROCEDURE WILL ONLY WORK IF THERE IS AN AVAILABLE OTA UPDATE FOR YOUR PHONE!!!
YOU WILL HAVE TO RE-ROOT YOUR PHONE IF YOU WANT ROOT ACCESS AFTER UPDATING! DO NOT RE-ROOT IF YOUR PHONE IS TO BE SENT FOR REPAIR!
Step 1) Download the OTA update. (I have a uploaded a sample update zip at
www . sidsoftinc . com / Blur_Version.0.3.9.MB300.Retail.en.03.zip
*remove the spaces)
Step 2) On completion, the phone should reboot and enter recovery mode, using the custom recovery to update. However, this should fail as most custom recoveries prevent original updates. Note the location of the downloaded update (likely at /cache)
Step 3) Power down the phone and enter into recovery mode manually
Step 4) Using ADB, pull the folder containing the update zip to your computer
Code:
adb pull /**storedlocation**/**nameoftheupdate**.zip update.zip
Step 5) Open the update.zip in your adb folder and look for a file called recovery.img (most likely in system folder)
Step 6) Open up the adb shell and flash the new recovery (recommended)
Code:
adb shell
su
flash_image recovery recovery.img
or you can place it in /system and it will be auto-flashed (not recommended)
Code:
adb push recovery.img /system/recovery.img
Step 7 (if possible) Make it permanent by deleting the custom recovery in /system
Code:
adb shell
cd system
su
mount -o rw,remount /dev/block/mtdblock1 /system
rm recovery.img
mount -o ro,remount /dev/block/mtdblock1 /system
exit
exit
Step 8) Reboot the phone and if you see a triangle warning sign, reboot your phone again. You should see your homescreen before it reboots to install the update again. This time, the original recovery will be used.
Once finished, your phone will be upgraded, unrooted and your applications and data will still be retained.
If you wish to install your previously used custom rom again, you must flash the custom recovery and install the rom, again
If I made a mistake, please do inform me. Thank you
I'm trying to do this for the Tmo G2 and I have reverted using another technique but the clockworkmod is still there. I thought it would get removed!
I have no idea how to get rid of it. Can you give me alittle help?
Did your clockworkmod recovery flash itself into your nv ram. If so then no one can help you there. If you have an ota update and pulled it to your pc, send me a coy and I'll see if I can help you. If you can, send me your ota update zip to [email protected].
Sent from my Motorola Backflip using the XDA App
I'm honestly unsure if it flashed to the nv-ram. Possibly, basically if I do a system boot (power +vol down) and select recovery, it will load the HTC green text with white background then go into clockword recovery. I'm not exactly sure why it still does this.
I used the method on this FORUM THREAD to un-root and get back to stock (using the available files there and method 1-a). I'm just unsure why the clockwork recovery is still there. I'm hoping I can still get back to stock recovery. Possibly I just need to flash the stock recovery.img??
Also, I had some troubles initially with ADB, which is why I used the VISIONary method of rooting. I'd love to try out the gfree method since I believe my ADB is working correctly now and test out some other roms to see what I like the most.
I know you are probably in a different time zone that is way ahead of mine........but can't I just reflash the stock or update ota recovery.img in fastboot mode.......OR is this a bad Idea???
Many users have accidently accepted ota updates on custom rims and recoveries. for fastboot, I did mention that flashing stock recovery and update is possible via adb shell.
Sent from my Motorola Backflip using the XDA App
siidheesh said:
Many users have accidently accepted ota updates on custom rims and recoveries. for fastboot, I did mention that flashing stock recovery and update is possible via adb shell.
Sent from my Motorola Backflip using the XDA App
Click to expand...
Click to collapse
I tried flashing the stock recovery but I'm not sure why it didn't work, I had hboot and flash_image. I used the adb shell way as well. It gave me error in partitions or whatever. I don't know what to do.
do you have Blur_Version.0.3.10.MB300.Retail.en.03.sbf file?
I dont happen to have that file, but i do have Blur_Version.0.3.9.MB300.Retail.en.03.zip
if you need it.
Cockwork Mod
I'm pretty green so this may sound really dumb, but can you flash sbf files to your phone via Clockwork Mod, or does it have to be done via RSD Lite. I cannot get RSD to recognize my device in 4.7 or 4.8. Please help.
do you have a stock image for the huawei ascend for cricket or does anyone here have it?
Unrooting......
I download the RECOVERY file you supplied (thank you)
"Blur_Version.0.3.9.MB300.Retail.en.03.zip"
If I reboot into Recovery and just flashed that zip file, would it work that way to unroot?
Provided you are flashing on a MOTOROLA BACKFLIP, yes. However, you might want to flash the AT&T 2.1 update for the backflip instead, if you reside in the US. Flashing back any official firmware unroots your phone
I'm looking to root and unlock my AT&F Motorola Backflip (MB300).. Any suggestions?
Sent from my NexusHD2 using Tapatalk
OTA for Samsung Galaxy Ace is a CFG file, not ZIP
Hello,
Just for interest, I received an OTA for my Samsung Galaxy Ace but it didn't come as a ZIP file - it came as a CFG file (which is not a ZIP, but actually a proprietary package - which I can't remember the name right now).
However, I did find the stock recovery elsewhere in this forum, and I installed it. But that wasn't enough for the OTA to be installed - it still fails.
Corrupted?
siidheesh said:
Step 5) Open the update.zip in your adb folder and look for a file called recovery.img (most likely in system folder)
Click to expand...
Click to collapse
I can't find it. I have an Alcatel Pop C1 4015X. Help?
Trying to unroot Xperia Z2
I am trying to unroot using update files from the Sony Xperia Companion. I found the update files (I think). I used Flashtool to decrypt the FILESET, but there is no recovery.img in the decrypted folder. The folder I decrypted is in Xperia Companion/Sony Mobile Update Engine/localstorage/db/13740270 and that is the only folder that has decryptable files. They are named FILE_8977018 and similar before decryption and various .sin .ta files (examples auto-boot.ta, cust-reset.ta, simlock.ta). Am I using the right decryption to get the recovery.img?
So, I
got myself an i9023 (yay!),
unlocked the bootloader,
updated it to 2.3.4 (GRJ22),
booted (not flashed) recovery-clockwork-3.0.2.4-crespo.img and applied su-2.3.6.1-ef-signed.zip from there and rebooted --> root.
Then I installed Superuser from Market and verifed that it works and
celebrated ...
... - as it turns out, rather prematurely. Apparently this doesn't give adb root because for that "ro.secure" in default.prop needs to be 0, and that file sits in the ro rootfs, which in turn is a part of the boot image ... ...
I guess my question is, how can I get root access for adb?
Is there an easy way to extract the boot image, change that detail and repack it?
EDIT: Solved, see http://forum.xda-developers.com/showthread.php?p=14219782.
fallenguru said:
So, I
got myself an i9023 (yay!),
unlocked the bootloader,
updated it to 2.3.4 (GRJ22),
booted (not flashed) recovery-clockwork-3.0.2.4-crespo.img and applied su-2.3.6.1-ef-signed.zip from there and rebooted --> root.
Then I installed Superuser from Market and verifed that it works and
celebrated ...
... - as it turns out, rather prematurely. Apparently this doesn't give adb root because for that "ro.secure" in default.prop needs to be 0, and that file sits in the ro rootfs, which in turn is a part of the boot image ... ...
I guess my question is, how can I get root access for adb?
Is there an easy way to extract the boot image, change that detail and repack it?
Click to expand...
Click to collapse
flash a custom rom through the recovery. they all pretty much have root.
I'm sure there's a way to get what you want exactly. I don't know it exactly though.
If it was my phone and i wanted to keep it stock. I would flash ~This Rom~. It's a stock deodexed zipaligned rom with a few minor tweaks.
I'm not 100 percent here but i believe if you just wanted the boot.img you could extract it from that rom then flash it using "fastboot flash boot boot.img" If you're running a stock build the boot image from a stock rom should work for you. but like i said i'm not 100% sure. I'm only a moderately well informed nub.
fallenguru said:
So, I
got myself an i9023 (yay!),
unlocked the bootloader,
updated it to 2.3.4 (GRJ22),
booted (not flashed) recovery-clockwork-3.0.2.4-crespo.img and applied su-2.3.6.1-ef-signed.zip from there and rebooted --> root.
Then I installed Superuser from Market and verifed that it works and
celebrated ...
... - as it turns out, rather prematurely. Apparently this doesn't give adb root because for that "ro.secure" in default.prop needs to be 0, and that file sits in the ro rootfs, which in turn is a part of the boot image ... ...
I guess my question is, how can I get root access for adb?
Is there an easy way to extract the boot image, change that detail and repack it?
Click to expand...
Click to collapse
If you type “su” in a terminal emulator, do you get a “$” or “#”? # means that you have root, otherwise you only have su app installed, nothing more. Same thing goes for “adb shell” "su" in your command prompt (in windows). If this is your situation then you could try this procedure:
-Flash or boot into clockwork recovery
-mount system partition (this part does the trick, I don’t see this steep in you post)
-install su-2.3.6.1-ef-signed.zip
-reboot
-enable USB debugging
simms22 said:
flash a custom rom through the recovery. they all pretty have root.
Click to expand...
Click to collapse
I'd rather stay with the stock ROM (+Voodoo module) for now, I'm not bored yet.
NVMENOR said:
If you type “su” in a terminal emulator, do you get a ...
Click to expand...
Click to collapse
#. Root on the phone and within adb shell is working fine, it's just adb itself that doesn't have root access. I'm used to modifying system files using adb pull - modify - adb push and uninstalling system apps via adb ... ...
Solved, see http://forum.xda-developers.com/showthread.php?p=14219782.
Excellent!
Thank you! Thank you! I've been trying for weeks to figure out why my rooted nexus s 4g was getting permission denied when trying to use push/pull (among other adb commands). Now I can backup my app's sqlite database using pull!
For my own education, what might the downside of flashing this boot image be? I know there is an obvious security vulnerability since adb runs as root by default now on the device. I'm willing to tolerate that for the time being. Are there any other possible issues or gotchas to be aware of?
peterwbeck said:
Thank you!
Click to expand...
Click to collapse
You're welcome.
peterwbeck said:
For my own education, what might the downside of flashing this boot image be?
Click to expand...
Click to collapse
As opposed to just booting it? I don't think there are any but I'm far from sure - maybe some incremental OTA updates won't work, for example.
Since the change only affects adb and you need to connect the phone to a computer for that anyway you might as well just boot the image whenever you need full adb access.
Hello,
I am stuck with rooting process. I tried rooting, unrooting before but this time, for some odd reason. I am unable to proceed
I followed this procedure from unlockr website to root the nexus S. Could not post the exact link because of restrictions
Phone is unlocked , USB debugging is ON. ADB mode is working, I can use other commands. But its giving me the following error on step 6 . Line 3
Mount : Operation Not permitted
Attaching image !
When I boot using volume up & Power button and go to Recovery, It gives me exclamation mark & Android Sign... So I cant unroot it either.
I always tried to unroot so I can go back to original state and restart the process. If I flash through recovery.img I can go into recovery but after few steps, I am stuck
Yeah that's normal. The mount command requires root permission (which you don't have yet)
Generally what you have to do after flashing the (right version of) custom recovery is:
copy the su.zip to your SD card
reboot into custom recovery
choose apply zip from SD card and select the su.zip
reboot
That's it.
Su have already been installed in previous step. Infact, I can even see its icon in menu...
Then it sounds like your recovery reverted back to stock. Did you rename the .sh file that rewrites the recovery on reboot? If not, do that using root explorer or any other method you find in the guide. Then flash the recovery again and it will stick.
Sent from my Nexus S using Tapatalk
No I didnot renamed. I was just following the process. I tried to unroot but cant do it either. I am stuck
ahaseeb said:
Su have already been installed in previous step. Infact, I can even see its icon in menu...
Click to expand...
Click to collapse
If su is installed correctly then for the "Mount : Operation Not permitted" problem, you just have to type su in adb shell (there may be a Superuser permission popup on the phone, just allow it) -- the prompt should change from $ to #, which means you are now root. After that the mount command should work.
To make custom recovery stick on every boot, rename /system/etc/install-recovery.sh to other name e.g. install-recovery.sh.disabled
When I typed su it said Permission denied !
Just because you have superuser in your app drawer does not mean you're rooted. You can downloaded from the market on any phone/rom.
You are not rooted.
Flash custom recovery via fastboot
Boot directly into recovery etc.
ahaseeb said:
When I typed su it said Permission denied !
Click to expand...
Click to collapse
Then I suggest you re-install Superuser from Android Market. Normally it shouldn't just say permission denied, there should be a Superuser popup asking for permission.
Or better, try to redo everything following this guide instead.
Again YOU HAVE TO FLASH SU FROM CUSTOM RECOVERY.
Do not install from market. Hell don't even boot up the OS. Flash recovery. Boot directly into recovery and flash su.zip from your phones internal storage/sdcsrd in recovery. The you're rooted.
Now you can update delete/rename the script to make the custom recovery stick. Update su in market or whatever else you want to do.
.
I believe i got it fixed. When ever the phone used to boot after installation of SU, dialogue box to ask for unlock. That dialogue box disappear very quickly. It took me time to figure it out. Thanks, I guess I am good now.
Thanks every one
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