Related
All the info and links needed, none of the fluff. If you have questions, simply ask.
This guide aims to be platform independent. However, some cheats may require user contribution. Thanks in advance!
UPDATED 5-4-2010: New, Faster Factory Reset. Thanks rt1oo and johnsongrantr
Root CDMA Hero, Load Custom Recovery & ROM
Forum Post: Step By Step Way to root Using Flashrec(Updated 4/5)
Thanks goku14238
1) Download: flashrec-1.1.3-20091107.apk
1.1) Download: recovery-RA-heroc-v1.6.2.img
1.2) Download ROM ZIP of Choice: XDA Wiki - ROMs
1.3) Market Download: Any File Manager. RootExplorer, ES File Manager, Astro, etc.
2) Rename "recovery-RA-heroc-v1.6.2.img" to "recovery_backup.img"
3) Copy downloads to SD card root (/sdcard/)
4) Fill in check box for: Settings>Applications>Unknown sources
5) Install "flashrec-1.1.3-20091107.apk" via Any File Manager (RootExplorer, ES File Manager, Astro, etc.) or ADB
*Unmount SD Card if mounted through USB*
6) Open "Recovery Flasher" App and select "Restore Backup Image"
7) Power OFF
8) Power ON to Recovery: Press and hold the "Home" button, Continue holding "Home" while pressing and releasing the "Power" button
9) Flash zip from sdcard>select ROM ZIP
10) Reboot
Reset Phone With Loaded ROM (1.5 "Cupcake" ROMs)
Code:
Menu > Settings > Security > Factory data reset > Reset phone > Erase everything
Reset Phone With Loaded ROM (2.1 ROMs)
Code:
Menu > Settings > Privacy > Factory data reset > Reset phone > Erase everything
Factory Reset
Thanks rt1oo: Forum Post
This will return the phone to its out-of-box, factory condition (including radio!).
Search "RUU" if you want it the official Windows way.
NOTE: If you used the 2.1 RUU, this will not work. HBoot version must be 1.41. Read Forum Post for another method.
1) Download: HERCIMG.ZIP
2) Copy to root of SD card (/sdcard/)
3) Turn phone OFF
3) Hold Volume Down while pressing the power button (turn back on)
4) Press trackball when prompted
5) Reboot
Boot to Recovery from Power OFF
Press and hold the "Home" button, Continue holding "Home" while pressing and releasing the "Power" button
Nandroid Backup
-Reboot into recovery mode>Backup/Restore>Nand backup
TIP: If you choose "Nand backup + ext" it will backup your apps2sd apps along with your imaged system.
*CAUTION: you must restore this kind of backup to an SD Card that is similarly formatted (i.e. SWAP/EXT/FAT backup)
COPY THE CONTENTS OF THE "nandroid" FOLDER TO OTHER MEDIA ON REGULAR BASIS IN CASE OF SD CARD FAILURE!
Nandroid Restore
-Reboot into recovery mode>Backup/Restore>Nand restore>Select desired backup
*TIP* If no backups are found, you need to copy the "nandroid" folder back onto your SD Card from your Computer backup (You did make a copy of nandroid to your Computer didn't you!?)
Partition SDCard for apps2sd (A2SD)
-WARNING: This will erase EVERYTHING from the SDCard. Nandroid does NOT backup SD Card data, except for apps2sd apps, and ONLY if you selected "Nand backup + ext"
1) Reboot into recovery mode>Partition sdcard>Follow on-screen instructions (Default values suggested are OK)
Load Custom ROMs
Download ROM ZIP of Choice: XDA Wiki - ROMs
1) Copy ROM ZIP to SDCard Root (/sdcard/)
2) Reboot into recovery mode>Flash zip from sdcard>select ROM ZIP
Load Android SDK [Mac]
1) Download Latest Android SDK: http://developer.android.com/sdk/index.html
2) Unpack and rename the extracted folder to "AndroidSDK", Move it to "Applications"
3) Copy and Paste into TextEdit:
Code:
export PATH=${PATH}:/Applications/AndroidSDK/tools
4) Save as: "~/.bash_profile"
5) Fill check box on Phone: Settings>Applications>Development>USB debugging
How to modify system files from Recovery
Code:
adb shell
mount <MOUNT_POINT>
Replace <MOUNT_POINT> with area you want to modify (ex: /system /data)
Install Apps through ADB
Code:
adb install <PATH_TO_APK>
Replace <PATH_TO_APK> with the location of your apk (ex: ~/Installers/Android/apk/wireless_tether_1_60_htc.apk)
How to tell if apps2sd (A2SD) is working
1) Connect Phone via USB
Code:
adb remount
adb shell
ls /system/sd/app/
If you get a list of applications, or no errors, then apps2sd is *should be* working properly.
Remove Extra Useless Preloaded Apps
Link: Root Explorer
Yes, you CAN do this through adb, but this is MUCH easier. Simply open, hit "mount r/w" button, delete anything in /system/app and /data/app you don't want! I'm well aware of the cost of the app. If you don't want to pay and help the developer, then search the forums and figure it out yourself !
Good stuff. Thanks for the contribution. Would you mind if I put it on GeekFor.Me / would you like to put it on there?
http://geekfor.me/news/wanted-writers-for-faq-tutorial-help/
Let me know.
Please do! Thanks for the read! Also, thank you very much for all of your hard work, the ROMs you make are crucial to all of this stuff advancing forward!
Thanks for putting this together - great post!
Thanks a lot for this Gallias. Definitely helped me out. I wish I had found this a couple weeks ago heh.
When I tried to enable compcache with your instructions I was getting a read-only error. Doing 'adb remount' first seems to have solved it.
AH yes thank you my apologies. Updated.
Hey, I swear i've tried for two hours to get Modacos custom ROM installed. I successfully installed the recovery-RA-heroc-v1.5.2.img and when I power off and reboot into recovery mode, I only get one option -- to CLEARSTORAGE "Delete all user data? <action>yes <send> no, I select YES and it reboots the phone and it looks like the same interface. I've tried flash_image recovery /sdcard/update.zip by renaming the ZIP file modaco 2.2 to (update) and moving it to the SDCARD home directory. I then use Lindas file manager to load the custom recovery image and select SDCARD/update.zip This doesn't work (I'm probably doing something wrong) But I don't understand why I can't boot into recovery mode. I am using the CDMA (sprint) version.
Any tips? I need a bit of some help here.
When you reboot into recovery mode you should see this:
{
"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"
}
If you don't see that, then you haven't actually pushed the new recovery image into the phone. The screen you describe is the default recovery loader that comes with the phone.
Try my "Load Custom Recovery" step over again, or if on a different platform, follow the root guide for your specific platform:
CDMA Hero Guides
I got up to the point of
adb push asroot2 /data/local
it says 836 KB/s <74512 bytes in 0.087s>
C:\hero\tools> aadb shell
$chmod 0755 /data/local/asroot2
chmod 0755 /data/local/asroot2
$ /data/ocal/asroot2 /system/bin/sh
/data/local/asroot2 /system/bin/sh
now get this.... this is what it gives back to me
[+] Using newer pipe_inode_info layout
Opening: /proc/758/fd/3
YES it says 758 NOT 857.
It then says
SUCCESS: Enjoy the shell
Is that right or is it supposed to be 857? I saw the guide and it told me that it should say 857 so it's not giving me the right message I assume.
I'll try again and see if this is right, i'll post an edit later to let you know if I get it workin, if not I guess 758 is incorect
Well, based on the C:\ I'm going to say your using Windows. I don't think that number will be critical, but you do need to perform this after you get the "SUCCESS: Enjoy the shell"
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4775 su
exit
exit
THEN, you also need to push the recovery image. If you are following the link I placed at the top of this guide on how to root with Windows, it should have you go through everything I'm explaining. Don't get worried or hung up on steps that don't exactly match up with what other people are seeing; at the end of the day you may see some differences, but if you are getting "SUCCESS" from asroot2 it means that the technical "rooting" part is working, you just need to finish up and follow through on the rest of the steps. Keep working at it you are really close, don't let inconsistent numbers discourage you!
Just letting you know, you've got a typo in the rooting area. It should be asroot2 not asroot 2
ffolkes said:
Just letting you know, you've got a typo in the rooting area. It should be asroot2 not asroot 2
Click to expand...
Click to collapse
Ah yes very true thanks! Fixed.
I followed the instructions for rooting with a MAC, I did the boot into recovery mode, there is no option for "NANDROID" backup. It just says "Clear User Data" <ACTION> Yes <SEND> No. Wound up clearing everything off my phone.
rlundeen said:
I followed the instructions for rooting with a MAC, I did the boot into recovery mode, there is no option for "NANDROID" backup. It just says "Clear User Data" <ACTION> Yes <SEND> No. Wound up clearing everything off my phone.
Click to expand...
Click to collapse
Ouch! Sorry man, it means something went wrong during "Load Custom Recovery [MAC]". Try that step over again.
theraginasian said:
Ouch! Sorry man, it means something went wrong during "Load Custom Recovery [MAC]". Try that step over again.
Click to expand...
Click to collapse
Did it 3 times, get the same thing over and over. Actually, if you hold the Volume Down key and then power the phone on, I can do the nandroid backup, flash rom, etc.
theraginasian said:
Remove Extra Useless Preloaded Apps
Forum Post 1: How to remove Stocks, Nascar, and other useless apps...
Forum Post 2: APPS that are SAFE to remove
Thanks chuckhriczko and VoXHTC!
Beyond what most custom ROMs remove, I remove:
-Sprint Navigation (Sprint_Navigator.apk/odex)
-Sprint Visual Voicemail (Sprint_Core.apk/odex)
-Device Self-Service (SDSA.apk/odex)
Code:
adb remount
adb shell
cd /system/app
rm <NAME_OF_APP>.apk
rm <NAME_OF_APP>.odex
Replace <NAME_OF_APP> with the name of the app you want removed.
Make sure to check /system/sd/app for duplicate/other unwanted applications if you have apps2sd running.
Click to expand...
Click to collapse
Thanks the cheat sheet. Is this list of apps that can be safely removed still valid for 2.1 ROMs? I am running DC v2.07.2 ROM.
prateekandroid said:
Thanks the cheat sheet. Is this list of apps that can be safely removed still valid for 2.1 ROMs? I am running DC v2.07.2 ROM.
Click to expand...
Click to collapse
Make a NANDROID before removing any of them, so if you remove something you want back or that messes your phone up. You can go back to original.
They arent usually the main choices. But you can if you want to.
Heres some you can remove.
Type this
adb remount
adb shell
cd /system/app
ls
* "ls" this will show you all the apps on your phone.*
These are commonly removed-
Sprint_Navigation.apk
Sprint_TV.apk
Sprint_TVWidget.apk
Sprint_Nscar.apk
Sprint_NFL.apk
Stock.apk
com.htc.StockWidget.apk
HtcRingtoneTrimmer.apk
Youtube.apk
Facebook.apk
There are more, but these are usually the common ones. Pick and choose what you want and what you dont want.
Jus10o said:
Make a NANDROID before removing any of them, so if you remove something you want back or that messes your phone up. You can go back to original.
They arent usually the main choices. But you can if you want to.
Heres some you can remove.
Type this
adb remount
adb shell
cd /system/app
ls
* "ls" this will show you all the apps on your phone.*
These are commonly removed-
Sprint_Navigation.apk
Sprint_TV.apk
Sprint_TVWidget.apk
Sprint_Nscar.apk
Sprint_NFL.apk
Stock.apk
com.htc.StockWidget.apk
HtcRingtoneTrimmer.apk
Youtube.apk
Facebook.apk
There are more, but these are usually the common ones. Pick and choose what you want and what you dont want.
Click to expand...
Click to collapse
Thanks for a prompt response.
Just curious, wat do people prefer instead of Youtube.apk to watch Youtube? Because as far as I know there is no Adobe Flash support yet. So Youtube videos will not work on its website. I use Dolphin browser.
i personally believe the flashrec method is much more practical. i was able to root and flash a custom rom without ever plugging my phone into my computer, i did it all from my phone.
is there a downside to flashrec im not aware of?
Edit: An easier method has been done here, If you feel the need to be challenged, This is your style, But if you prefer a hassle-less method, [Click Here]
{
"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"
}
Credits: Firstly, I thank member’s such as Skin,Vivek,Amit,trip,ron for their work and motive towards the project regarding our phones..
Note: This post has been heavily edited from it’s previous XXKPE RootExploitGuide. This was edited to make deodexing easier for newbies who are new to this.
Great Success .
Deodexing
-NOTE: The Already Deodexed files are placed in the download section, This will save a great amount of time, If you have downloaded the already deodexed files, proceed with Step
1. At this point before you start you must be rooted via SOC or any method you preferred. And you must have Busybox, If you use/flash Skin's CWM or Amit's version they already contain Busybox so your ready to go.
2. Once you've gotten the green signal , Copy done_app and done_frame to your sdcard *Download link in the downloads section* , not external_sd. Disconnect VIA storage and connect via Debugging mode.
3. Launch cmd by pressing Window Key+ R and type "cmd"
4. Launch adb by copying the path of adb into command prompt till it appears something like this
Code:
cd C:\Program Files (x86)\Android\android-sdk\platform-tools
Note: location may differ based on where you downloaded adb into.
5. Then type adb shell
6. Type
Code:
adb shell
$ su
# stop
# mount -o remount rw /system
# rm /system/app/*.odex
# rm /system/framework/*.odex
# cp /sdcard/done_app/* /system/app/
# cp /sdcard/done_frame/* /system/framework/
# mount -o remount ro /system
# reboot
7. After this , Voila you are deodexed!.
- credits to Skin1980 for this.
Note: This is compatible with XXKPE+XXKPH
1. Install a root app such as Root Explorer
2. Navigate to your system/framework and copy android.policy.jar and back it up.
3. Copy and paste the attached to your system/framework and replace file.
4. Reboot
---------------------------
Download android.policy.jar
Download Deodexed System Files [COMPLETE XXKPE]
Download Deodexed System Files [COMPLETE XXKPH]
- Removed xUltimate and added completed deodexed files.
- Added Screenshot's to make it noob friendly.
- Revamped page and added additional info
- Added note on deodexed and outdated info.
- Removed outdated information and updated with latest one.
- Added already deodexed files for XXKPH
Flash the phone with pda file....can u please explain in detail...
Pls consider dis..i was never able to understand clock work mod...on kp9...pls can u guys..i mean thosewho acquie knowledge about dis stufff...can make videos for members like me..if possible plz...or explain in very detail
Sent from my GT-I9003 using XDA Premium App
I shall try to make a video on this later. But for now I shall explain.
Flash it using Odin. Place the file in pda *Note you must have flashed to XXKP9 or XXKPE for this to work* then flash it. Like this
stuck on step 5 of deodex...Help...><
Thanks misledz
Sent from my GT-I9003 using XDA Premium App
Dude I can'd Deodex the Phone
I have used the xultimate to convert the files
But i cant copy files to my phone
CP command is not working!!!
I have installed the busybox
and when i take the busybox installer it installs the busybox
and the busy box path is shown but NOT WORKING(cp command)
Just testing the cp command
vivekkalady said:
Dude I can'd Deodex the Phone
I have used the xultimate to convert the files
But i cant copy files to my phone
CP command is not working!!!
I have installed the busybox
and when i take the busybox installer it installs the busybox
and the busy box path is shown but NOT WORKING(cp command)
Just testing the cp command
Click to expand...
Click to collapse
try using the cp internal to busybox.
ie:
busybox cp /system/bin/am /system/am
IS Deodexing a pre requisite for installing the Vanilla LOck?Anyone reply fast?
tanu_invincible said:
IS Deodexing a pre requisite for installing the Vanilla LOck?Anyone reply fast?
Click to expand...
Click to collapse
Yes because all the files we edit are in the odex file
So to install any modes we must dedox(combine jar or apk with corresponding odex file)
Sent from my GT-I9003 using XDA Premium App
@ fooman123
I made the cp command to work on my phone and i can copy any file with cp command but i cant copy the done_frame to system/frame
There is some problem with mounting sdcard
cp /sdcard/done app ......... Etc as defined in the dedoxing guide
Sent from my GT-I9003 using XDA Premium App
hi,
i done dedox well and i saw no.odex files system->app folder
but every time when i am replacing the framework file ... after rebooting my phone struck at the samsung logo ... then i use recovery (update.zip) to come back ... can anybody give me the process how to copy the framework file
java fail...how??
ok got it now! =)
kchdeepak said:
hi,
i done dedox well and i saw no.odex files system->app folder
but every time when i am replacing the framework file ... after rebooting my phone struck at the samsung logo ... then i use recovery (update.zip) to come back ... can anybody give me the process how to copy the framework file
Click to expand...
Click to collapse
actually you haven't deodexed you only removed the odex file that doesn't mean you have deodexed.
by doing these 2 operations
rm /system/app/*.odex
rm /system/framework/*.odex
you are removing the odex files form the app & framework directory
but the next two steps are not working
so the files from the done_app and done_frame are not copying
so you cannot boot because of the error while copying(no files are copied)
this is the problem i am facing Too
vivekkalady said:
actually you haven't deodexed you only removed the odex file that doesn't mean you have deodexed.
Click to expand...
Click to collapse
ohh ok ok so you are also unable to do all these things... like krazzzy themes and this vinilla lock and all ?
kchdeepak said:
hi,
i done dedox well and i saw no.odex files system->app folder
but every time when i am replacing the framework file ... after rebooting my phone struck at the samsung logo ... then i use recovery (update.zip) to come back ... can anybody give me the process how to copy the framework file
Click to expand...
Click to collapse
How did you create the update.zip ???
explain???
is it [I9003][CWM] ClockworkMod Recovery porting for I9003 ??
so you haven't reflash original??
i have to format each time when i try to deodex
somebody help mee
man u need to install latest java sdk
DEODEXd xxkpe with Vanilla Lockscreen
u must be rooted
busybox
note:when u first time run su command in ur mobile superuser ask allow unknown u have allow
adb config(optional)
right click computer->properties
from lift side advance system setting
click->advanced tab
click->environment variables
from second column->path
select edit->
add aftter ";" this C:\Program Files\Android\android-sdk\platform-tools\(this is ur adb location)
after this u can simply type cmd/run adb shell
download and extract two folder (done_app&done_frame) to sdcard(if u did sdswap u have copy to ur orgenal external sdcard)
in adb run this comound
$ su
# stop
# mount -o remount rw /system
# rm /system/app/*.odex
# rm /system/framework/*.odex
# cp /sdcard/done_app/* /system/app/
# cp /sdcard/done_frame/* /system/framework/
# mount -o remount ro /system
# reboot
after reboot u are done deodexd with vanilla lockscreen
download here
vivekkalady said:
actually you haven't deodexed you only removed the odex file that doesn't mean you have deodexed.
by doing these 2 operations
rm /system/app/*.odex
rm /system/framework/*.odex
you are removing the odex files form the app & framework directory
but the next two steps are not working
so the files from the done_app and done_frame are not copying
so you cannot boot because of the error while copying(no files are copied)
this is the problem i am facing Too
Click to expand...
Click to collapse
after deodexing are you copying the done_app and done_frameworks folders to your internal or external sd card...if you have copied it to external sd card its wrong...copy the folders to internal sd and give it a try
To avoid getting CP error's use stericsons from the market.
Sent from my GT-I9003 using Tapatalk
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.
ClockworkMod Recovery is alternate recovery mode for the android pre-installed devices. The Auxus CoreX2 is shipped with 4.1.1 and without recovery images.
The following is the steps to flash the CWM Recovery to the Iberry Auxus CoreX2
I tried the RK30 Genric Image as just need to backup and restore options.
Steps
Download the CWM Image
Extract CWN Image to the ADB folder (ADB Driver for the Rockchip board)
Connect phone with USB debugging mode
Using ADB push command push the flash_image & recovery.img to /dev/ folder in device
Code:
adb push flash_image /dev/
adb push recovery.img /dev/
Now flash recovery image to recovery partition as follows
Code:
adb shell
chmod 755 /dev/flash_image
/dev/flash_image recovery /dev/recovery.img
chmod 644 /system/etc/install-recovery.sh
to check the recovery use below command
Code:
adb reboot recovery
Source for CWM Image : http://files.androtab.info/rockchip/rk3066/20130203/RK30GENERIC_CWM.zip
Root/Flash AT YOUR OWN RISK. Author is not responsible for what you do on your device. Author is not responsible for liability of any kind.
Rooting Steps for Auxus CoreX2 3g / Rockchip :http://forum.xda-developers.com/showthread.php?t=2126534
skv_vlr_mech said:
ClockworkMod Recovery is alternate recovery mode for the android pre-installed devices. The Auxus CoreX2 is shipped with 4.1.1 and without recovery images.
The following is the steps to flash the CWM Recovery to the Iberry Auxus CoreX2
I tried the RK30 Genric Image as just need to backup and restore options.
Steps
Download the CWM Image
Extract CWN Image to the ADB folder (ADB Driver for the Rockchip board)
Connect phone with USB debugging mode
Using ADB push command push the flash_image & recovery.img to /dev/ folder in device
Code:
adb push flash_image /dev/
adb push recovery.img /dev/
Now flash recovery image to recovery partition as follows
Code:
adb shell
chmod 755 /dev/flash_image
/dev/flash_image recovery /dev/recovery.img
chmod 644 /system/etc/install-recovery.sh
to check the recovery use below command
Code:
adb reboot recovery
Source for CWM Image : http://files.androtab.info/rockchip/rk3066/20130203/RK30GENERIC_CWM.zip
Root/Flash AT YOUR OWN RISK. Author is not responsible for what you do on your device. Author is not responsible for liability of any kind.
Rooting Steps for Auxus CoreX2 3g / Rockchip :http://forum.xda-developers.com/showthread.php?t=2126534
Click to expand...
Click to collapse
You rock!! I tried this on my coreX2, however I receive an error at the last command. Can you please confirm the last command, "chmod 644 /system/etc/install-recovery.sh". When I try to execute this command, I receive the below error:
"[email protected]:/ # chmod 644 /system/etc/install-recovery.sh
chmod 644 /system/etc/install-recovery.sh
Unable to chmod /system/etc/install-recovery.sh: No such file or directory"
s.rahus said:
You rock!! I tried this on my coreX2, however I receive an error at the last command. Can you please confirm the last command, "chmod 644 /system/etc/install-recovery.sh". When I try to execute this command, I receive the below error:
"[email protected]:/ # chmod 644 /system/etc/install-recovery.sh
chmod 644 /system/etc/install-recovery.sh
Unable to chmod /system/etc/install-recovery.sh: No such file or directory"
Click to expand...
Click to collapse
I think CWM install the last command is for suppression the restore of the default recovery, so for Core x2 there might not be no default recovery mode.
You can go to recovery mode by pressing the power + home or power + vol dn
skv_vlr_mech said:
I think CWM install the last command is for suppression the restore of the default recovery, so for Core x2 there might not be no default recovery mode.
You can go to recovery mode by pressing the power + home or power + vol dn
Click to expand...
Click to collapse
Yeah power key + home key did the trick!! Everything looks perfect now.
However I've this strange issue- the cmw recovery mode is running upside down (I have to hold the tab with home key on top). I have the same issue while taking screenshots (power key + volume down), the screenshots are upside down. Any idea why is this so?
Now, do we have a cyanogen based ROM that can be flashed on Corex2? I'm planning to try the ROM listed in this thread, will let you know the result- http://forum.xda-developers.com/showthread.php?t=2108704&page=3
skv_vlr_mech said:
ClockworkMod Recovery is alternate recovery mode for the android pre-installed devices. The Auxus CoreX2 is shipped with 4.1.1 and without recovery images.
The following is the steps to flash the CWM Recovery to the Iberry Auxus CoreX2
I tried the RK30 Genric Image as just need to backup and restore options.
Steps
Download the CWM Image
Extract CWN Image to the ADB folder (ADB Driver for the Rockchip board)
Connect phone with USB debugging mode
Using ADB push command push the flash_image & recovery.img to /dev/ folder in device
Code:
adb push flash_image /dev/
adb push recovery.img /dev/
Now flash recovery image to recovery partition as follows
Code:
adb shell
chmod 755 /dev/flash_image
/dev/flash_image recovery /dev/recovery.img
chmod 644 /system/etc/install-recovery.sh
to check the recovery use below command
Code:
adb reboot recovery
Source for CWM Image : http://files.androtab.info/rockchip/rk3066/20130203/RK30GENERIC_CWM.zip
Root/Flash AT YOUR OWN RISK. Author is not responsible for what you do on your device. Author is not responsible for liability of any kind.
Rooting Steps for Auxus CoreX2 3g / Rockchip :http://forum.xda-developers.com/showthread.php?t=2126534
Click to expand...
Click to collapse
In my computer when i type 'adb devices' it does not shows my Auxus x2 adn when i push it to the /dev/ folder it gives me the same error 'error=no device"
iNOXIA2012 said:
In my computer when i type 'adb devices' it does not shows my Auxus x2 adn when i push it to the /dev/ folder it gives me the same error 'error=no device"
Click to expand...
Click to collapse
Do you have the adb drivers installed on your PC? Please try to install/reinstall the drivers.
s.rahus said:
Do you have the adb drivers installed on your PC? Please try to install/reinstall the drivers.
Click to expand...
Click to collapse
Hi! i would be grateful if can u give me the link or upload it
I'm NOOB in ADB
adb cwm recovery screen shot
{
"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"
}
iNOXIA2012 said:
Hi! i would be grateful if can u give me the link or upload it
I'm NOOB in ADB
Click to expand...
Click to collapse
You can download the usb drivers from http://u12455652.letitbit.net/download/45792.49d38524b49df16a0b360c4e0f4b/usb_driver.zip.html.
By the way, you have to be rooted to install cmw recovery. Are you already rooted? The rooting procedure can be found here: http://forum.xda-developers.com/showthread.php?t=2126534 (by skv_vlr_mech). I can confirm that the method works.
---------- Post added at 08:48 PM ---------- Previous post was at 08:45 PM ----------
iNOXIA2012 said:
Hi! i would be grateful if can u give me the link or upload it
I'm NOOB in ADB
Click to expand...
Click to collapse
skv_vlr_mech said:
Click to expand...
Click to collapse
Hi skv_vlr_mech,
Do you know any ROMs based on CM 10.1 (JB 4.2.1) that can be flashed on Corex2?
iNOXIA2012 said:
In my computer when i type 'adb devices' it does not shows my Auxus x2 adn when i push it to the /dev/ folder it gives me the same error 'error=no device"
Click to expand...
Click to collapse
install the correct USB driver refer the http://forum.xda-developers.com/showthread.php?p=37682648#post37682648
Custom ROM for Auxus X2 3g
Hi Friends,
Could you please help me with a custom rom for Auxus core X2 3g anfd the procedure.
I tried with oma's rom but it booting to recovery mode giving error opening e drive.
skv_vlr_mech said:
ClockworkMod Recovery is alternate recovery mode for the android pre-installed devices. The Auxus CoreX2 is shipped with 4.1.1 and without recovery images.
The following is the steps to flash the CWM Recovery to the Iberry Auxus CoreX2
I tried the RK30 Genric Image as just need to backup and restore options.
Steps
Download the CWM Image
Extract CWN Image to the ADB folder (ADB Driver for the Rockchip board)
Connect phone with USB debugging mode
Using ADB push command push the flash_image & recovery.img to /dev/ folder in device
Code:
adb push flash_image /dev/
adb push recovery.img /dev/
Now flash recovery image to recovery partition as follows
Code:
adb shell
chmod 755 /dev/flash_image
/dev/flash_image recovery /dev/recovery.img
chmod 644 /system/etc/install-recovery.sh
to check the recovery use below command
Code:
adb reboot recovery
Source for CWM Image : http://files.androtab.info/rockchip/rk3066/20130203/RK30GENERIC_CWM.zip
Root/Flash AT YOUR OWN RISK. Author is not responsible for what you do on your device. Author is not responsible for liability of any kind.
Rooting Steps for Auxus CoreX2 3g / Rockchip :http://forum.xda-developers.com/showthread.php?t=2126534
Click to expand...
Click to collapse
hi i've uploaded an attachment tell me if the drivers are installed correctly
Is there any point in having CWM recovery when we don't have any custom ROMs?
Nice CWM Recovery
Thanks
The CWM works perfectly on my Auxus Core X2 3G.
A small bug exists that, CWM interface shows Upside down.
Its ok. I am not worrying abt that
Guys you need to try this
Awesome.
can u give
skv_vlr_mech said:
install the correct USB driver refer the http://forum.xda-developers.com/showthread.php?p=37682648#post37682648
Click to expand...
Click to collapse
hi can u download the attachment Plz
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