Database Info

[HowTo] Infuse ADB Flashing Guide - Kernels, Roms, Modified 3e Recovery, Busybox

ABOUT:
This tutorial explains how to use adb to flash the following items starting from a UCLB3 base w/ root.
- Custom kernel w/ CWM recovery
- Modified 3e recovery
- Custom firmware (ROMS)
- Busybox
These instructions will most likely work coming from other rooted Infuse firmwares, but were tested starting from my Odin UCLB3 Unbrick package with root.
ADB SETUP:
Download: adb.zip
Download: SAMSUNG_USB_Driver_for_Mobile_Phones.exe
Setup instructions are for Windows, but adb is also available for Linux and Mac.
a.) If necessary, uninstall any previous Kies or Samsung USB Driver installations, and install the Samsung USB driver from the above download link.
b.) Unzip contents of adb.zip and copy the folder contents to C:\Windows\
c.) If your phone is booted up and running, make sure you select USB debug mode in settings. ADB also works in CWM recovery, and in modified 3e recovery.
d.) To test your installation, open a command prompt (Press WINDOWS KEY + R - type cmd - press Enter).
Type:
Code:
adb devices
If all is working, you will see your device listed.
Some quick command tips:
To move a file from your computer to the phone, "push" it:
Code:
adb push myfile.zip /directory-on-phone/
Of course, you need to be in the computer directory for your file in the command line to push it to the phone.
To get a file from your phone onto your computer, "pull" it:
Code:
adb pull /sdcard/myfile.zip
To access a command prompt for the phone:
Code:
adb shell
Inside that shell, you can use unix commands from within the Android OS to manipulate your phone.
------------------------------------------------------------
INSTRUCTIONS FOR GINGERBREAD:
(Scroll down for ICS Instructions.)
------------------------------------------------------------
Instruction steps must be followed in order.
Step 1: Use adb to install a custom kernel
Download: flash_image.zip (Extract and use flash_image for instructions below.)
You'll also need a Gingerbread kernel zImage.
Code:
adb push flash_image /data/local/tmp/flash_image
adb push zImage /data/local/tmp/zImage
adb shell
$ su
# chmod 755 /data/local/tmp/flash_image
# chmod 755 /data/local/tmp/zImage
# /data/local/tmp/flash_image boot /data/local/tmp/zImage
# reboot recovery
Step 2: Use adb to install modified 3e recovery
Necessary for Step 3.
Download: 3e_recovery_no_sig_check.zip (Extract and use recovery for instructions below.)
Code:
adb remount
adb push recovery /system/bin/recovery
adb shell "chmod 755 /system/bin/recovery"
adb reboot recovery
Step 3: Use adb to install a custom firmware
This step uses the modified 3e recovery to flash unsigned firmware.
You'll need to download the zip file for the Gingerbread (or possibly Froyo) rom that you would like to flash. These instructions have been tested by flashing my Ethereal rom.
Replace YourFirmware.zip with the actual name of your rom zip.
Code:
adb push YourFirmware.zip /sdcard/
adb remount
adb shell
# echo "boot-recovery" > /cache/recovery/command
# echo "--update_package=SDCARD:YourFirmware.zip" >> /cache/recovery/command
# reboot recovery
Let firmware flash complete, and then type:
Code:
adb reboot
EXTRA: Use adb to install busybox
Download: Busybox-1.20.2.zip (Extract and use busybox for instructions below.)
Code:
adb remount
adb push busybox /system/xbin/busybox
adb shell
# chmod 755 /system/xbin/busybox
# ln -s /system/xbin/busybox /system/bin/busybox
# /system/xbin/busybox --install -s /system/xbin
# exit
----------------------------------------
INSTRUCTIONS FOR ICS:
----------------------------------------
STEP: Use adb to flash an ICS kernel; then use blue CWM recovery to install an ICS rom.
Download: flash_image.zip (Extract and use flash_image for instructions below.)
You'll also need an ICS kernel boot.img and it is recommended that you push an ICS rom zip to your sdcard. Once you are in blue CWM recovery, you won't be able to use adb to push anything else to the device.
Replace YourFirmware.zip with the actual name of your rom zip.
Code:
adb push YourFirmware.zip /sdcard/
adb push flash_image /data/local/tmp/flash_image
adb push boot.img /data/local/tmp/boot
adb shell
$ su
# chmod 755 /data/local/tmp/flash_image
# chmod 755 /data/local/tmp/boot
# /data/local/tmp/flash_image boot /data/local/tmp/boot
# reboot recovery
From here, just follow the normal instructions for flashing your ICS rom in blue recovery.
I'll add to these instructions as I find more for ICS, and as support increases for adb in the CWM recovery we're using in ICS roms. At this time, adb support isn't fully working in Infuse ICS CWM recoveries. If you use adb to get an ICS kernel / CWM recovery combination, just use the recovery menu to do anything else. If you need to get other files onto the device while in blue CWM recovery, go to mounts and storage, mount /sdcard/, and mount USB storage.
Hope this is useful to someone else. I mainly wanted to see how much could be done with just adb, and I learned quite a bit about how the phone works in the process.

Wow my friend...nice and thx for what you provide the Infuse Community.
It is people like you, why i stay!

very nice how-to!

bigjoe2675 said:
Wow my friend...nice and thx for what you provide the Infuse Community.
It is people like you, why i stay!
Click to expand...
Click to collapse
SiL3nTKiLL said:
very nice how-to!
Click to expand...
Click to collapse
Thanks fellas. And, by the way, I know that most general users aren't going to use adb to flash kernels and firmware. It's of course easier to use all of the Heimdall one-click and Odin tools that we have - as well as the Infuse Toolkit, Heimdall suite, SGS Kernel Flasher, and CWM recovery. So, for the person asking, "Why would someone still do this, when we have all of the tools that we have?" - this isn't for you.
I approached this from the standpoint of asking, "What if we didn't have access to all of the easy tools?".
At some point, if someone is having issues with Odin and Heimdall, or if they can't use their hardware buttons, maybe they will find this useful. I like to do things from the command line and not have to touch the phone while I'm working on development stuff - plus I type fast, and since I spent years in the command line on Slackware linux, prefer using unix commands. I'm actually faster at CLI stuff than with GUI stuff, plus I like the control that CLI gives you.
I had to help a forum member restore his phone over a remote tech support session using https://join.me/ . He claimed that he couldn't get Heimdall or Odin to recognize his phone. I was able to use adb to do things from his computer, which was helpful, since I couldn't see or directly use his phone. I had to ask him to do some things on the phone, so I later wanted to figure out how to do more using just adb. That's what this is all about. If I had to help someone over a remote session now, I could do most everything without them ever touching their phone.

First of all thank you very much for the guide, but I seem to be having a problem
Whenever I try this:
Code:
adb push YourFirmware.zip /sdcard/
adb remount
adb shell
# echo "boot-recovery" > /cache/recovery/command
# echo "--update_package=SDCARD:YourFirmware.zip" >> /cache/recovery/command
# reboot recovery
the first issue is the phone reboots but continues to system and not to recovery.
now if I manually make it boot recovery, CWM gives me an error that it couldn't mount: SDCARD:update.zip
the update.zip that I'm trying to flash is CM9 RC2, also tried other zip files and also failed.
what am I doing wrong ?!
Thanks in advance.

DeepUnknown said:
First of all thank you very much for the guide, but I seem to be having a problem
Whenever I try this:
Code:
adb push YourFirmware.zip /sdcard/
adb remount
adb shell
# echo "boot-recovery" > /cache/recovery/command
# echo "--update_package=SDCARD:YourFirmware.zip" >> /cache/recovery/command
# reboot recovery
the first issue is the phone reboots but continues to system and not to recovery.
now if I manually make it boot recovery, CWM gives me an error that it couldn't mount: SDCARD:update.zip
the update.zip that I'm trying to flash is CM9 RC2, also tried other zip files and also failed.
what am I doing wrong ?!
Thanks in advance.
Click to expand...
Click to collapse
If you follow the steps correctly from Gingerbread (including the step to install modified 3e recovery), and replace "YourFirmware.zip" with the name of your firmware, these adb commands use 3e recovery to flash firmware. These flashing instructions are not for CWM recovery, and the steps you are following aren't for flashing ICS from Gingerbread. Look further down in the first post for ICS adb instructions.
Sent from my SGH-I997 using Tapatalk 2

jscott30 said:
If you follow the steps correctly from Gingerbread (including the step to install modified 3e recovery), and replace "YourFirmware.zip" with the name of your firmware, these adb commands use 3e recovery to flash firmware. These flashing instructions are not for CWM recovery, and the steps you are following aren't for flashing ICS from Gingerbread. Look further down in the first post for ICS adb instructions.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for clearing it up. The reason why I used that method is because I looked online and I found it on another forum and the post owner didn't mention anything about it should be used with GB.

infuse CM9 rainbows
I'm caught with a half-done CM9 install of the infuse upgraded from cm7.
Somehow I was able too boot once sucessfully into CM9 though with the initial rainbow screen, but now my device hangs in recovery which is also garbled. I've been searching all over for a nice thorough guide to getting this thing going again and your post here was the only one I found remotely applicable to my situation.
I've been trying your ADB instructions for flashing with ICS but I'm stuck at second step: where I only get: cannot stat "flash-image": no such file or directory.
Since I'm stuck in CWM recovery none of the other options seems to see my device, ie. Heimdall or Odin.
Is there a better solution out of my woes?
Excuse my noobiness.

By stucked at recovery you mean it always boots up into recovery (recovery bootloop)?
You should go back to ULCB3 stock, preferably using Jscott's "option C" and flash the GB bootloaders. Then proceed to installing CM9, and remember to do a double flash. (wipes, flash, reboot, phone hangs, boot into cwm with 3-finger combo, wipe and flash!)
This way you'll solve both the recovery bootloop and the rainbows, and bring you CM9
Sent from my sweet and buttery Infuse

andros11 said:
By stucked at recovery you mean it always boots up into recovery (recovery bootloop)?
You should go back to ULCB3 stock, preferably using Jscott's "option C" and flash the GB bootloaders. Then proceed to installing CM9, and remember to do a double flash. (wipes, flash, reboot, phone hangs, boot into cwm with 3-finger combo, wipe and flash!)
This way you'll solve both the recovery bootloop and the rainbows, and bring you CM9
Click to expand...
Click to collapse
Yes the problem right now is that the only understandable thing I get out of the phone is the samsung logo at boot.
I think it goes into recovery but I can't really tell because the screen is garbled. Also using "adb reboot download" seems to make no difference to Odin or Heimdall which both refuse to see the phone.
I would love to find out exactly which state the phone is in but my knowledge of adb isn't that great to say the least.
How do I flash bootloaders using adb only?
I totally appreciate your help Andros, totally out of luck with this so far.

The only way to flash bootloaders is in download mode using either odin or heimdall.
Adb reboot download should get you into download mode as long as you have adb access while on recovery. If not, get into download mode this way:
Take out battery, and put it back in.
Hold both vol+ & vol- (don't press power)
plug in usb cable to phone.
Once in download mode, your phone should be recognized by Odin. If not, try reinstalling the drivers using the ones in the iset thread.
There are many threads about this situation that should also help you out, just search around
Sent from my sweet and buttery Infuse

Okay, somehow I missed how to use the keys to enter download state.
In my mind using adb to enter download state should be the same as the keys but somehow that isn't the case.
Got the GB bootloaders installed and used an odin package and then redid the CM9 installation.
Sorry about spamming this thread, and thanks to andros for getting me going again.

Interesting, I also didn't know that could make a difference. Lesson learned lol
Glad you got it running again
Sent from my sweet and buttery Infuse

hi , i am having serious problem ,
my i997 was ok before after doing a mess , now its in 3e reocvery restarts in samsung logo comes to 3e recovery again and so on.....i did everything ,flashed with I997UCKH1 but all in vain .
Could somebody guide what to do ?

umairrashid1 said:
hi , i am having serious problem ,
my i997 was ok before after doing a mess , now its in 3e reocvery restarts in samsung logo comes to 3e recovery again and so on.....i did everything ,flashed with I997UCKH1 but all in vain .
Could somebody guide what to do ?
Click to expand...
Click to collapse
Use odin or heimdall to repartition back to uclb3 stock.

andros11 said:
Use odin or heimdall to repartition back to uclb3 stock.
Click to expand...
Click to collapse
i used heimdall ,it flashed successfully but still no result .
how to do he same using odin ?
could you please add more steps in order o recover the phone fully .
i am in a big problem .

[RECOVERY]CWM Touch 6.0.2.8 for MEDION LIFETAB P9514 [25.2.2013]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello everybody!
The long wait has finally come to an end, as I successfully compiled CWM Touch Recovery for Medion Lifetab P9514. It works great on IceCreamSandwitch 4.0.3 Release 2 and it should also work on previous ICS updates. However, it is not compatible with Honeycomb 3.2!
Before we begin a warning is in order: You are making changes to your tablet’s software at your own risk!
So let's start. I advise you to first backup your stock recovery, just in case something goes wrong. There are couple of methods to do this. I will describe in my opinion the easiest, with adb commands for Microsoft Windows or Linux OS. This way you are not required to boot your tablet in special modes (fastboot or APX).
GETTING STARTED
When you connect LIFETAB to your PC, drivers should be installed automatically in Windows Vista/7. If they are not or if you encounter any erros, try the guide for Windows XP (original guide by @Pummelchen - android-hilfe.de).
Download drivers for WinXP: http://www.medion.com/au/service/_lightbox/treiber_details.php?did=10725
Extract the drivers - double click on "usb_p9514wxp.exe"
"Medion" folder will be created on C:/ drive, in there you will see "android_winusb.inf".
Open Device Manager: either by following the path "Start/Control Panel/System/Advanced System Settings/Hardware/Device Manager" or by right-clicking on "Computer" - "Properties" in start menu.
Connect your LIFETAB with a microUSB/USB Cable to the PC an wait for a few seconds.
In Device Manager "Other devices" should appear, there you will see "MTP" with a yellow exclamation mark. Right-click on it and choose "Properties".
Under "Driver tab" choose "Update driver".
Browse to C:/Medion and start the installation.
ADB/Fastboot tool for windows (USB drivers included): http://www.mediafire.com/download/bklnjn2x0fbln4b/MD_LT_P9514_Drivers_ADB_Fastboot.zip
You can install adb tools in Linux by following this guide: http://forum.xda-developers.com/showthread.php?t=2431956
Make sure you have USB-debugging enabled on your tablet (Settings – Developer options – USB debugging)
Run Windows Command Prompt (Start Menu – Run… – write in “cmd” – press OK); point the cursor to the ADB folder by using “cd” command (a simpler way: press SHIFT and right-click on ADB folder, choose "Open this folder in command window")
Open Terminal in Linux
Write the following order of commands in cmd:
BACKUP STOCK RECOVERY
See if your device is recognized (a long number)
Code:
adb devices
Enter the adb session
Code:
adb shell
Get root privileges
Code:
su
Make /system partition readable-writable, so you can make changes
Code:
mount -o rw,remount /system
Backup 1st file
Code:
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.backup
Backup 2nd file
Code:
mv /system/recovery-from-boot.p recovery-from-boot.p.backup
Create and backup stock recovery image file
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/download/original-recovery-p9514.img
RESTORE STOCK RECOVERY
Should you at any time encounter problems with cwm touch, or you simply don't like it, you can restore your stock recovery. The commands are therefore reversed:
Restore 1st file
Code:
mv /system/etc/install-recovery.sh.backup /system/etc/install-recovery.sh
Restore 2nd file
Code:
mv /system/recovery-from-boot.p.backup /system/recovery-from-boot.p
Restore stock recovery to mmcblk0p1 partition
Code:
dd if=/sdcard/download/original-recovery-p9514.img of=/dev/block/mmcblk0p1
Warning: Be carful to use the right number in mmcblk0p1. This is /recovery partition, if you use others you might brick your tablet!
An easier way to have stock recovery back is to simply re-flash ROM update zip file. But by doing this you will loose root privileges, configuration and possibly user data.
I suggest you save "original-recovery-p9514.img" also to your external sdcard and possibly to your PC. You can use your USB connection cable or a file explorer (like ES File Manager) to transfer the file to an external data storage. Another option is this adb command:
Code:
adb pull /sdcard/download/original-recovery-p9514.img
FLASH CWM TOUCH RECOVERY
Now that you’ve successfully backed-up our stock recovery, let’s flash the new cwm touch. Again there are a couple of ways to do this, I will describe in my opinion the easiest.
First download attached file, extract it and copy cwm-recovery-p9514.img to your internal sdcard. You can simply use a USB connection cable and transfer the file to the path “/sdcard/download” or use a file explorer (like ES File Manager) to copy the file.
Another method is with ADB commands. Put cwm-recovery-p9514.img in ADB folder on your PC. Open windows command window and check that your tablet is recognized (adb devices). The following line will transfer the .img file to “download” folder (you can use any other name, but the folder needs to exist on your sdcard):
Code:
adb push cwm-recovery-p9514.img /sdcard/download
To flash cwm recovery on the recovery partition, use the following commands:
Code:
adb shell
su
mount -o rw,remount /system
dd if=/sdcard/download/cwm-recovery-p9514.img of=/dev/block/mmcblk0p1
You can now reboot your tablet.
INSTALL CWM TOUCH RECOVERY USING TERMINAL EMULATOR
This is a simpler and faster way to flash my cwm touch recovery, without needing a PC/Laptop.
Install one of free terminal emulators from Google Play Store.
Here are a couple of options:
ConnectBot
Android Terminal Emulator
Providing you already copied "cwm-recovery-p9514.img" to your tablet, skip this step. If not, look at the previous steps.
Open the terminal emulator app and insert these lines:
Code:
su
mount -o rw,remount /system
dd if=/sdcard/download/cwm-recovery-p9514.img of=/dev/block/mmcblk0p1
To restore your original recovery:
Code:
su
mount -o rw,remount /system
dd if=/sdcard/download/original-recovery-p9514.img of=/dev/block/mmcblk0p1
USING CWM TOUCH RECOVERY
To enter cwm recovery mode press hard buttons in combination: power off your tablet, press and hold VOLUME UP (PLUS) and press POWER. Once you see "Ota…" in the top left corner of the display, quickly press:
1X VOLUME DOWN (MINUS),
2X VOLUME UP (PLUS),
1X VOLUME DOWN (MINUS).
You will see the counter go to 4 and cwm recovery will start.
For a more practical access to the recovery, use this app: Quick Reboot.
Make a backup of your rom as soon as possible, to save your data.
Please do not attempt to flash any zip files using this recovery. You may damage your tablet in doing so.
"Wipe cache partition", "wipe dalvik cache" and "fix permissions" are safe processes, but use "wipe data/factory reset" only when needed.
ADDITIONAL INFORMATION
NOTE: I will leave older versions of cwm touch recovery available, should you have any problems with newer ones.
This guide wouldn't be possible, without the help from guys on http://www.avi-plus.com, Yves & Micky.
XDA:DevDB Information
[RECOVERY]CWM Touch 6.0.2.8 for MEDION LIFETAB P9514 [25.2.2013], ROM for the Android General
Contributors
MMWolverine
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2015-02-04
Last Updated 2015-11-01

Briliant! Just found out, that there is CWM for my "old" P9514 ... great work!
Hope there will be some Custom-ROMs soon; maybe on CM basis - the Stock ROM is not that what I would call "well".

d3rm1k said:
Briliant! Just found out, that there is CWM for my "old" P9514 ... great work!
Hope there will be some Custom-ROMs soon; maybe on CM basis - the Stock ROM is not that what I would call "well".
Click to expand...
Click to collapse
Thanks! Actually not to difficult making a cwm recovery, but when it comes to custom roms I'm still a bit of a noobie. I am learning fast though, so maybe in the near future.
Oh btw, here's the recovery guide in german language: http://www.handy-faq.de/forum/medio...on_lifetab_p9514_13_1_2013_a.html#post2385512

Yes, I know. Because of that German post I searched here, hoping that there already might be a Custom ROM.
But I only have a LogIn here and not the muse to sign up at handy-faq.de, yet

Many thanks for this cwm, the installation worked like a charm.
One small remark, to enter cwm you have to hold the Volume Up (Plus) and Power button. You could perhaps change this in your guide (it is correctly in the guide in german language)
I have translated your guide to Dutch on my blog, I'll hope it's no prob:
http://blog.johanvanbogaert.be/2013/02/clockworkmod-voor-de-medion-lifetab.html
Rgrds Johan

Jopeke said:
Many thanks for this cwm, the installation worked like a charm.
One small remark, to enter cwm you have to hold the Volume Up (Plus) and Power button. You could perhaps change this in your guide (it is correctly in the guide in german language)
I have translated your guide to Dutch on my blog, I'll hope it's no prob:
http://blog.johanvanbogaert.be/2013/02/clockworkmod-voor-de-medion-lifetab.html
Rgrds Johan
Click to expand...
Click to collapse
Thanks for notifying me about the mistake, I already corrected it.
I updated the cwm to newest 6.0.2.8 and will change the adb drivers part of the guide, as some users have difficulties understanding it.
I see no problem that you translated my guide, after all it's from different sources and made to be used for free.

MMWolverine said:
Thanks for notifying me about the mistake, I already corrected it.
I updated the cwm to newest 6.0.2.8 and will change the adb drivers part of the guide, as some users have difficulties understanding it.
I see no problem that you translated my guide, after all it's from different sources and made to be used for free.
Click to expand...
Click to collapse
Hi MMWolverine, already flashed v6.0.2.8, only took a minute.
I've updated my own blog as well.
Instead of using adb it is much easier to use a terminal emulator (like ConnectBot) on Android todo the update.
To install cwm someone only needs his tablet, ConnectBot and ES File Explorer. No PC, adb, usb connection necessary for flashing cwm.
If someone has rooted his lifetab, your guide is more then easy to understand to do this installation.
But if you don't wan't to use a PC for flashing the following is possible: From the lifetab download the zip, extract with ES File Explorer,Flash with ConnectBot (only the 3 last commands from your guide are necessary: su,mount..., dd....)

Actually, I did plan to do both guides. But I wasn't sure how many people would agree to install the terminal. Will probably do this, as you recommend.
I was also hoping, that the recovery would be uploaded to Rom manager app. Says on recovery maker website, that you need to be the device owner. Medion still isn't added to device list.

I have checked ROM Manager before doing the installation manually, its a pitty its not jet implemented in ROM Manager. But the installation is quit straight forward.
If someone is ever making a custom ROM for the LifeTab P9514, please implement USB OTG, because thats an option I'm waiting for.

Great that you added the instructions todo the installation through a terminal emulator on Android. Just one remark, the adb shell command can be removed while using a terminal on Android.

What happens if you try to flash a zip with CWM? Why doesn't it work and what would break?

You need a properly written updater-script. If a zip isn't compatible, you will only get an error, but nothing will be changed.

Do you know if the CM10 based ROM that works on the P9516 would work on the P9514 too?
Thanks

The answer is no. CM roms are hardware based and if you would flash p9516 rom on p9514 it wouldn't even boot.

lost p9514 Stock rom
Hi together!
I have a problem! I want to get back to unrooted original stock rom in lifetab p9514.
Somehow, dont ask me how, I lost the backed up version.
Is there a possibility to download such rom - I couldnt find anything!
Thanks in advance!
W

wfmagic said:
Hi together!
I have a problem! I want to get back to unrooted original stock rom in lifetab p9514.
Somehow, dont ask me how, I lost the backed up version.
Is there a possibility to download such rom - I couldnt find anything!
Thanks in advance!
W
Click to expand...
Click to collapse
Hello,
you can get official rom by typing in your MSN number (written on the back of your tablet): http://www.medion.com/de/service/download/software.php
And I have a mirror here: http://www.mediafire.com/download/xi5b93rj55bc0e7/Lifetab_p9514.20120719.2-ICS-signed-ota-update.zip
Hope that helps.

works like a charm!
I love this Forum - thank you very much!

root auxus core x2 3g using Android Debug Bridge ADB

Build Properties of Auxus Core X2 3G contains the ro.build.user=root by default firmware update and also Default Properties contains ro.secure=0, ro.debuggable=1. So rooting the devices made very easy.
The following are the things to do to get root access in the front end
Update the binary of the Superuser
Setting the chown & chmod to the Superuser binary
Install the Superuser.apk
Optional:Installing the Root Checker & Root Unistaller
The following are the files required to do the above
ADB Driver for the Rockchip board (Auxus Core X2 Shipped with RK3066)
ADB file & ADB library files
Latest Superuser binary & apk files
Optional:Rootchecker & Root Uninstaller files
Source:
ADB Driver : XDA Post (http://78.140.134.121/d/6ea124157e9cda25ab1707cbcba7/usb_driver.zip)
ADB Files : http://forum.xda-developers.com/showthread.php?t=1987280
SU Files : http://downloads.androidsu.com/superuser/
Optional:RootCheck: http://joeykrim.com/
Optional: RootUnistaller:http://www.apkmania.co/2012/12/root-uninstaller-pro-v32-apk.html
Customizing the folder for the Auxus
Create folder e.g., C:\Auxus\
Extract the ADB files and Copy the adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll to Auxus
Extract the Superuser files and Copy the \system\app\Superuser.apk and \System\bin\su to Auxus
Optional:Also place the RootCheck & RootUnistaller apk
Creating batch file named ROOT.bat
Creating batch file : ROOT.bat
The following code to be added to batch file
Code:
echo off
echo Check list of devices connected
adb devices
pause
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
echo Rebooting 1/3
adb reboot
echo After Reboot to home screen unlock and press any key
pause
echo Setting Kernel Properties
adb shell rm /data/local.prop > nul
adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
echo Rebooting 2/3
adb reboot
echo After Reboot to home screen unlock and press any key
pause
adb shell id
pause
echo ADB Mounting root drive
adb remount
echo Pushing Superuser files
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
echo Removing changes except ROOT
adb shell rm /data/local.prop
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.bak /data/local/tmp
echo Installing application
adb push superuser.apk /system/app/superuser.apk
echo Rebooting 3/3
adb reboot
echo ROOTED
pause
Also append below code if optionals downloaded
Code:
echo ADB Mounting root drive
adb remount
echo Installing Root Check & Root Uninstall
adb push Root_Uninstaller_Pro.apk /system/app/Root_Uninstaller_Pro.apk
adb push RootCheckPro.apk /system/app/RootCheckPro.apk
echo Done
pause
echo Rebooting
adb reboot
echo After Reboot to home screen unlock and press any key
pause
Steps to root
Install the ADB driver by double clicking the DPInst-32bit.exe
Now windows will prompt for the Driver security - Click Install anyway to proceed
Now connect the Auxus Core X2 3G in USB Debugging mode, the driver will be identified by windows (if not restart)
Now run the ROOT.bat (Run as Administrator)
The tablet will be reboot 3 times (if optional files used reboot 4 times)
Now run the ROOT.bat file and Auxus Core X2 3G rooted successfully.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer :
Though tested many times with my tablet and the post drafted carefully. Kindly Backup data before proceed; All the files download from various link from internet and the attachment (Auxus.rar) contains the combination of them. Screenshots generated by author.
ROOT AT YOUR OWN RISK. Author is not responsible for what you do on your device. Author is not responsible for liability of any kind.

combined attachment included
Update: Auxus.rar is combination made from the above said link and with root batch files. ROOT AT YOUR OWN RISK. Author is not responsible for what you do on your device. Author is not responsible for liability of any kind.

Thanks a bunch!!
I will try this method on my corex2 this weekend and let you know the result. Thanks a lot!:good:

my tabs back camera is very slow and lagging in preview, does anyone having corex2 3g can confirm?

Rear camera- laggy- known issue
guyton100 said:
my tabs back camera is very slow and lagging in preview, does anyone having corex2 3g can confirm?
Click to expand...
Click to collapse
Yes, this is a known issue with the CoreX2. Lets hope that they will fix this issue with future firmware updates.

Please tell me how to unroot the same

Kudremukh said:
Please tell me how to unroot the same
Click to expand...
Click to collapse
muruggan_a has reported a post.
Reason:
Hi Friends,
I have done a pre-booking of X2 3G, i have faced the following issues
1) I was unable to send any 2010 MS office documents from win 7 laptop to auxus x2 3g
2)Even after i paired my tablet with my laptop, i cannot connect the media service from my tablet to laptop using bluetooth
3)Nokia BT head set doesnt get paired
And my last query is if i can root the device whether i can use 3G dongle instead of using SIM slot?
Please help me,
I have handedover to iberry service center and asked for replacement because of the bluetooth issue which i mentioned above. I got the replacement device but that also have the same problem. The new device had some scratches behind so given them back and asked for replacement.

Device Not found
When I oopen ROOT.bat In,
Win 8 it says error:device not found
Win 7 it says path not recognized or something like that
plz help me how to fix it and the
ADB unknown USB driver you gave when i open it win rar says that the file is corrupted or what i dont know
plz help me here:crying:

Will this work for Auxe CoreX4?
skv_vlr_mech said:
Build Properties of Auxus Core X2 3G contains the ro.build.user=root by default firmware update and also Default Properties contains ro.secure=0, ro.debuggable=1. So rooting the devices made very easy.
The following are the things to do to get root access in the front end
Update the binary of the Superuser
Setting the chown & chmod to the Superuser binary
Install the Superuser.apk
Optional:Installing the Root Checker & Root Unistaller
The following are the files required to do the above
ADB Driver for the Rockchip board (Auxus Core X2 Shipped with RK3066)
ADB file & ADB library files
Latest Superuser binary & apk files
Optional:Rootchecker & Root Uninstaller files
Source:
ADB Driver : Unknown (http://78.140.134.121/d/6ea124157e9cda25ab1707cbcba7/usb_driver.zip)
ADB Files : http://forum.xda-developers.com/showthread.php?t=1987280
SU Files : http://downloads.androidsu.com/superuser/
Optional:RootCheck: http://joeykrim.com/
Optional: RootUnistaller:http://www.apkmania.co/2012/12/root-uninstaller-pro-v32-apk.html
Customizing the folder for the Auxus
Create folder e.g., C:\Auxus\
Extract the ADB files and Copy the adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll to Auxus
Extract the Superuser files and Copy the \system\app\Superuser.apk and \System\bin\su to Auxus
Optional:Also place the RootCheck & RootUnistaller apk
Creating batch file named ROOT.bat
Creating batch file : ROOT.bat
The following code to be added to batch file
echo off
echo Check list of devices connected
adb devices
pause
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
echo Rebooting 1/3
adb reboot
echo After Reboot to home screen unlock and press any key
pause
echo Setting Kernel Properties
adb shell rm /data/local.prop > nul
adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
echo Rebooting 2/3
adb reboot
echo After Reboot to home screen unlock and press any key
pause
adb shell id
pause
echo ADB Mounting root drive
adb remount
echo Pushing Superuser files
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
echo Removing changes except ROOT
adb shell rm /data/local.prop
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.bak /data/local/tmp
echo Installing application
adb push superuser.apk /system/app/superuser.apk
echo Rebooting 3/3
adb reboot
echo ROOTED
pause
Also append below code if optionals downloaded
echo ADB Mounting root drive
adb remount
echo Installing Root Check & Root Uninstall
adb push Root_Uninstaller_Pro.apk /system/app/Root_Uninstaller_Pro.apk
adb push RootCheckPro.apk /system/app/RootCheckPro.apk
echo Done
pause
echo Rebooting
adb reboot
echo After Reboot to home screen unlock and press any key
pause
Steps to root
Install the ADB driver by double clicking the DPInst-32bit.exe
Now windows will prompt for the Driver security - Click Install anyway to proceed
Now connect the Auxus Core X2 3G in USB Debugging mode, the driver will be identified by windows (if not restart)
Now run the ROOT.bat (Run as Administrator)
The tablet will be reboot 3 times (if optional files used reboot 4 times)
Now run the ROOT.bat file and Auxus Core X2 3G rooted successfully.
Disclaimer :
Though tested many times with my tablet and the post drafted carefully. Kindly Backup data before proceed; All the files download from various link from internet and the attachment (Auxus.rar) contains the combination of them. Screenshots generated by author.
ROOT AT YOUR OWN RISK. Author is not responsible for what you do on your device. Author is not responsible for liability of any kind.
Click to expand...
Click to collapse
Will the above procedure work for the Corex4 as well?

guyton100 said:
my tabs back camera is very slow and lagging in preview, does anyone having corex2 3g can confirm?
Click to expand...
Click to collapse
yes, it is there, but front camera is good. I posted support query in manf webpage and searching the firm update to make custom rom

cdwarak said:
Will the above procedure work for the Corex4 as well?
Click to expand...
Click to collapse
try root methods of Samsung Exynos 4412 for CoreX4 3g

iNOXIA2012 said:
When I oopen ROOT.bat In,
Win 8 it says error:device not found
Win 7 it says path not recognized or something like that
plz help me how to fix it and the
ADB unknown USB driver you gave when i open it win rar says that the file is corrupted or what i dont know
plz help me here:crying:
Click to expand...
Click to collapse
If Root.bat not worked manual use the code as mentioned in the thread.
I'm using windows 7 only and also verified with the XP.
Try downloading the files from source links. If device not recognized then it is the issue of the USB driver installation; Also refer the Screenshots and steps in the post

Kudremukh said:
Please tell me how to unroot the same
Click to expand...
Click to collapse
in command prompt, path to the adb folder
adb remount
adb shell rm /system/app/superuser.apk
adb shell rm /system/bin/su
adb reboot
and so on...

!!!Rooted!!! This method works like a charm. Thanks man!! Trying to figure out if we have cwm recovery for corex2. I tired a couple of them meant for other rockchip 3066 devices but no dice.

clockworkmod-recovery-for-auxus-core-x2
s.rahus said:
!!!Rooted!!! This method works like a charm. Thanks man!! Trying to figure out if we have cwm recovery for corex2. I tired a couple of them meant for other rockchip 3066 devices but no dice.
Click to expand...
Click to collapse
Check out for CWM
http://forum.xda-developers.com/showthread.php?p=37584364#post37584364

Link Error
ADB Driver URL that you gave wont work gives me Error

iNOXIA2012 said:
ADB Driver URL that you gave wont work gives me Error
Click to expand...
Click to collapse
Please find attachment file that i downloaded from the link what i mentioned in first post

skv_vlr_mech said:
please find attachment file that i downloaded from the link what i mentioned in first post
Click to expand...
Click to collapse
thank you so much

Great It worked flawlessly. I wasn't able to root using moborobo or Zhuo. But this method worked. Thanks

Has it got GPS or not???
Hi,
Can anyone please tell whether Auxus core X2 3G has got inbuild GPS or not.

[GUIDE] Root for chinafonino I9300DDKL1

I have this phone:
I9300DDKL1
2.6.35.7-I9300XXKL3-CL793489roo[email protected]#2
GINGERBREAD.XXKL3
android: 4.1.9
this is a very cheap phone... it have a spreadtrum cpu 1ghz, 512mb di ram, 180mb for apps, no internal memory, android 2.3.7
many many chinese app and it don't have a international play store and google account... only chinese store,
but it is fast and have a good display,
i want root... i have tried many famous exploit and programs, but nothing...I have tried all the known ways, but nothing worked.
I flashed a cwm recovery to a similar phone (i9270) but when you get into recovery the screen is illuminated, making it unusable.
But the phone has no problems once powered on.
but i'm be very lucky and now i have root:
Here the luck:
I go into recovery, I connect it to the USB port ... I realize that the computer recognizes it!
I start randomly MTKdroids .... and I realize with amazement that recognizes it and tells me that the "root shell"!!
practically even if the recovery is not usable ... (Matter of display driver I think) this works!! I open directly from mtkdroid prompt for adb and can install the root manually with ADB commands!!
preparation:
A) install the drivers (ok for win8 64bit)
SCI-android-new i9300ddkl1.rar (12.7 MB)
https://mega.co.nz/#!00NUkARJ!EGBrqAcjV3_MHiFhmBzifW3u2yQc7rsbyirbS_LCvNU
B) flash the recovery
1) download this
recovery.img (10.0 MB)
https://mega.co.nz/#!x4sEmSoa!JC1YkjyJ6b2-TC5o1JaXHCws22UqIjWkuF8n5LwnXxA
2) Download fastboot
adb_fastboot_and_other_tools.zip (11.1 MB)
https://mega.co.nz/#!YhsgmBjR!O3_dXhqPVVXR7FPlv_4EARFoDEUnKbTj9ocNXIuicuc
3) You must log in fastboot mode. you must try all combinations of buttons, I worked by holding power, then volume more then home in fast time.
4)copy recovery.img inside directory with fastboot
4) from the cmd prompt, type:
fastboot flash recovery recovery.img
Mtk Dorids:
MTKdroidTools_v230.exe (4.3 MB)
https://mega.co.nz/#!lgFyQQbY!DNNtAwVP24u2RPpl7M_CFjAW_m98PEdwraLiPIWtcWA
install mtkdroids
copy files SU, superuser.apk and busybox in the directory adb in directory of mtkdroids
pull them by this file:
https://mega.co.nz/#!511zRR6J!B9vcRCGuBsQ6iqvrK3piwUxbu75p-kyof3cJsgcr2G0
connect your phone switched on
open mtkdroids
reboot into recovery with "reboot" button
when the phone will reboot into recovery
you will see a green square and the "root shell" in the lower left
open "adb terminal"
then:
1) mount the file system:
adb shell
# mount -o rw -t /dev/block/mtdbblock11 /system
# exit
2) copy the file root:
adb push to / system / xbin / su
adb push Superuser.apk / system / app / Superuser.apk
adb push busybox / system / xbin / busybox
3) set the permission
adb shell
# Chmod 06755 / system / xbin / su
# Chmod 0644 / system / app / Superuser.apk
# Chmod 0755 / system / xbin / busybox
exit
4) Restart

Hi Angelo,
link A and B dont work...mega ask me for encryption key!
could you check it please?
thanks

ok..
i have fixed links... (new driver for fastboot mode) and make some adjustment.
Angelo

hi
i need this driver...
plz help me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
plz help me

angelobiz said:
I have this phone:
I9300DDKL1
[email protected]#2
GINGERBREAD.XXKL3
android: 4.1.9
this is a very cheap phone... it have a spreadtrum cpu 1ghz, 512mb di ram, 180mb for apps, no internal memory, android 2.3.7
many many chinese app and it don't have a international play store and google account... only chinese store,
but it is fast and have a good display,
i want root... i have tried many famous exploit and programs, but nothing...I have tried all the known ways, but nothing worked.
I flashed a cwm recovery to a similar phone (i9270) but when you get into recovery the screen is illuminated, making it unusable.
But the phone has no problems once powered on.
but i'm be very lucky and now i have root:
Here the luck:
I go into recovery, I connect it to the USB port ... I realize that the computer recognizes it!
I start randomly MTKdroids .... and I realize with amazement that recognizes it and tells me that the "root shell"!!
practically even if the recovery is not usable ... (Matter of display driver I think) this works!! I open directly from mtkdroid prompt for adb and can install the root manually with ADB commands!!
preparation:
A) install the drivers (ok for win8 64bit)
SCI-android-new i9300ddkl1.rar (12.7 MB)
https://mega.co.nz/#!00NUkARJ!EGBrqAcjV3_MHiFhmBzifW3u2yQc7rsbyirbS_LCvNU
B) flash the recovery
1) download this
recovery.img (10.0 MB)
https://mega.co.nz/#!x4sEmSoa!JC1YkjyJ6b2-TC5o1JaXHCws22UqIjWkuF8n5LwnXxA
2) Download fastboot
adb_fastboot_and_other_tools.zip (11.1 MB)
https://mega.co.nz/#!YhsgmBjR!O3_dXhqPVVXR7FPlv_4EARFoDEUnKbTj9ocNXIuicuc
3) You must log in fastboot mode. you must try all combinations of buttons, I worked by holding power, then volume more then home in fast time.
4)copy recovery.img inside directory with fastboot
4) from the cmd prompt, type:
fastboot flash recovery recovery.img
Mtk Dorids:
MTKdroidTools_v230.exe (4.3 MB)
https://mega.co.nz/#!lgFyQQbY!DNNtAwVP24u2RPpl7M_CFjAW_m98PEdwraLiPIWtcWA
install mtkdroids
copy files SU, superuser.apk and busybox in the directory adb in directory of mtkdroids
pull them by this file:
https://mega.co.nz/#!511zRR6J!B9vcRCGuBsQ6iqvrK3piwUxbu75p-kyof3cJsgcr2G0
connect your phone switched on
open mtkdroids
reboot into recovery with "reboot" button
when the phone will reboot into recovery
you will see a green square and the "root shell" in the lower left
open "adb terminal"
then:
1) mount the file system:
adb shell
# mount -o rw -t /dev/block/mtdbblock11 /system
# exit
2) copy the file root:
adb push to / system / xbin / su
adb push Superuser.apk / system / app / Superuser.apk
adb push busybox / system / xbin / busybox
3) set the permission
adb shell
# Chmod 06755 / system / xbin / su
# Chmod 0644 / system / app / Superuser.apk
# Chmod 0755 / system / xbin / busybox
exit
4) Restart
Click to expand...
Click to collapse
Bro is possible you make a full backup from this phone i need too i have one need full rom..thx

[Q] Need Help Ramos W41 bootloop

Hi..
I have a Ramos W41
- quadcore ATM 7025
- RAM 1 GB DDR3
- GPU Vivante GC1000
and now my tablet is bootloop after I upgraded the OS to 4.2.2
I used tablet product tool to flashed it.
I forgot to enter the "ramosvendorapk.img" when I reflash
I try to reflash, the tablet doesn't detected on my PC, and now it's just stuck at the logo, and it can't to enter the recovery mode
please help me to solve this
thank you

Arhick said:
Hi..
I have a Ramos W41
- quadcore ATM 7025
- RAM 1 GB DDR3
- GPU Vivante GC1000
and now my tablet is bootloop after I upgraded the OS to 4.2.2
I used tablet product tool to flashed it.
I forgot to enter the "ramosvendorapk.img" when I reflash
I try to reflash, the tablet doesn't detected on my PC, and now it's just stuck at the logo, and it can't to enter the recovery mode
please help me to solve this
thank you
Click to expand...
Click to collapse
can you get it into recovery?

Try rebooting into recovery.. Then wipe data and cache.
Sent from my Qmobile Noir A10 using Tapatalk

keifus.rahn said:
can you get it into recovery?
Click to expand...
Click to collapse
mrtaim3 said:
Try rebooting into recovery.. Then wipe data and cache.
Sent from my Qmobile Noir A10 using Tapatalk
Click to expand...
Click to collapse
No, this tablet cannot enter the recovery mode
when I see in the buildprop, the recovery mode was disable by its factory, I also tried to enable
but still can't recovery

you must contact to the developer of this Tablet.

mrtaim3 said:
you must contact to the developer of this Tablet.
Click to expand...
Click to collapse
okay..don't you have a solution ?
I tried to contact the developer, but they don't reply yet..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Ur device is not in use of many ppl so its hard to find the solution of it.. The only way u can reset ur device is by going into recovery. or try resetting ur device through tablet tool. Or try reflashing.. Switch off the tablet connect it with usb.. And wait till it detects. Make sure u have installed ur tablet drivers.
Sent from my Qmobile Noir A10 using Tapatalk

mrtaim3 said:
Ur device is not in use of many ppl so its hard to find the solution of it.. The only way u can reset ur device is by going into recovery. or try resetting ur device through tablet tool. Or try reflashing.. Switch off the tablet connect it with usb.. And wait till it detects. Make sure u have installed ur tablet drivers.
Sent from my Qmobile Noir A10 using Tapatalk
Click to expand...
Click to collapse
thank you for your responds
my tablet is not detected on my PC, and when usb connected to my computer it's just charging..
the usb drivers is installed.
and this tablet not supported recovery mode, I already tried.

Arhick said:
thank you for your responds
my tablet is not detected on my PC, and when usb connected to my computer it's just charging..
the usb drivers is installed.
and this tablet not supported recovery mode, I already tried.
Click to expand...
Click to collapse
I feel sorry that i couldn't help you.. Take it to any repair shop or just wait for the developers to respond.

Arhick said:
Hi..
I have a Ramos W41
- quadcore ATM 7025
- RAM 1 GB DDR3
- GPU Vivante GC1000
and now my tablet is bootloop after I upgraded the OS to 4.2.2
I used tablet product tool to flashed it.
I forgot to enter the "ramosvendorapk.img" when I reflash
I try to reflash, the tablet doesn't detected on my PC, and now it's just stuck at the logo, and it can't to enter the recovery mode
please help me to solve this
thank you
Click to expand...
Click to collapse
So I've did some Research on your device and it seems like everyone is having the same problem and there seems that a fix hasn't been Resolved yet. But here are a few things you can try to resolve this issue... (1) If you can take the battery out plug it in to the charger / Then take the battery out and unplug /\ This is to make shure you have no power left in the device wait about a minit then place the battery back in and press the volume down for about 30 seconds and the press and hold the power button while holding the volume down key When the screen lights up let go of the power and keep holding volume down for 15 seconds that should give you some options on restoring your device if that dont work then try doing the same with vol up instead of down or try holding both volume keys and ive noticed that there is a restart hole next to the volume keys if so do the charger steps but with out the vol keys....Find somthing to press and hold the reset button and while holding the reset button power on the device and see if any luck..
(2) PC NEEDED WITH SDK if you have a pc and you have the android sdk set up u can try connecting to your device using / adb /echo/ if you dont have the sdk you can get it here with a tut on using adb= http://developer.android.com/sdk/index.html now if your ready here is a way to connect to your device threw adb... Using ADB as solution
ADB can be used to access the phone while booting, be aware that some bootloops make it unable to use ADB since they do not go further then the manufacturer logo. (In new CWM versions it’s possible to use adb)
The only tricky part about using ADB with bootloops is that you have to do it on the right time, this is different from every device, but normally it’s after the manufacturer logo that the partitions get mounted. The easiest way to enter your phone in this part is using a batch script that monitors the state of your device and connects directly when possible.
I use this script for example, called ondemand.bat (requires adb.exe and the 2 dlls)
1 @ECHO off
2 cd /d %~dp0
3 echo.
4 echo Waiting for device…
5 adb wait-for-device
6 echo.
7 adb -d shell stop
8 adb push mycwmfix.zip /sdcard/mycwmfix.zip
9 adb reboot recovery
Linux Version (ondemand.sh):
1 #!/system/bin/sh
2 echo " "
3 echo "Wating for device..."
4 ./adb wait-for-device
5 echo " "
6 ./adb -d shell stop
7 ./adb push mycwmfix.zip /sdcard/mycwmfix.zip
8 ./adb reboot recovery
This script will wait for the device to become ready, when it’s ready it freeze the device, so the script has more time to push the file (instead of keep rebooting). Then it will push the specified cwmfix zip to your sdcard, and after that it will reboot in recovery so you can install the cwm fix you made. You can also make an batch script that pushes the files automatically to your phone, here is an example:
(1 @ECHO off
(2)cd /d %~dp0
(3)echo.
(4)echo Waiting for device...adb wait-for-device
(5)echo.
(6)adb -d shell stop
(7)adb -d shell su -c "mount -o remount rw /system"
(8)adb push framework-res.apk /system/framework/framework-res.apk
(9)adb -d shell chmod 644 /system/framework/framework-res.apk
(10)adb push SystemUI.apk /system/app/SystemUI.apk
(11)adb -d shell chmod 644 /system/app/SystemUI.apk
(12)adb reboot
(13)Linux version:
1#!/system/bin/sh
2echo " "
3echo "Waiting for device..."
4./adb wait-for-device
5echo " "
6./adb -d shell stop
7./adb -d shell su -c "mount -o remount rw /system"
8./adb push framework-res.apk /system/framework/framework-res.apk
9./adb -d shell chmod 644 /system/framework/framework-res.apk
10./adb push SystemUI.apk /system/app/SystemUI.apk
11./adb -d shell chmod 644 /system/app/SystemUI.apk
12./adb reboot
This script will wait for the device to become ready, when it’s ready it freeze the device, so the script has more time to push the file (instead of keep rebooting). Then it will push framework-res.apk and SystemUI.apk to the directory it belongs to, after that it changes the permissions of the files to RW-R-R (644) and then it will reboot.
Please note that on some devices the command “su -c” cannot be used after using the “stop” command, it gives an error then (Segmentation Fault).
What you can do to prevent this is adding “adb remount” just under the “adb wait-for-device” line, and remove the “adb -d shell su -c “mount -o remount rw /system” line.
Save the script and run it again.
You are probably able to fix your bootloop with this guide, in some rare cases some other partitions could be damaged, then I advice you to install the stock rom (which is no .zip in most cases)
Once you master the fixing of bootloops you can fix your phone independently !
You can try this if all else fails GOOD LUCK SIR :fingers-crossed: http://www.mediafire.com/?9oghmlgoqpm44qe