Related
Ok, I have a small of a damned problem. I got to Gingerbread 2.3.6 and Now I can't root D: I tried downloading superuser from Play store too.
I've also tried root it normally (CWM Update method) I used 2 of them upd_1.zip and FitGingerRoot.zip Both didn't work (Although, FitGingerRoot.zip says it finishes, while upd_1.zip give me an error 7)
What should I do?
lordsolrac2 said:
Ok, I have a small of a damned problem. I got to Gingerbread 2.3.6 and Now I can't root D: I tried downloading superuser from Play store too.
I've also tried root it normally (CWM Update method) I used 2 of them upd_1.zip and FitGingerRoot.zip Both didn't work (Although, FitGingerRoot.zip says it finishes, while upd_1.zip give me an error 7)
What should I do?
Click to expand...
Click to collapse
Flash any custom rom and your device will get rooted
Best stock based rom is creed v_4
Edward Cullen
I'm trying to make a Stock based rom myself, therefore I'm trying to refrain from using a Custom ROM
lordsolrac2 said:
Ok, I have a small of a damned problem. I got to Gingerbread 2.3.6 and Now I can't root D: I tried downloading superuser from Play store too.
I've also tried root it normally (CWM Update method) I used 2 of them upd_1.zip and FitGingerRoot.zip Both didn't work (Although, FitGingerRoot.zip says it finishes, while upd_1.zip give me an error 7)
What should I do?
Click to expand...
Click to collapse
Please Check Rooting File(.zip) Corrupt or Not
Sent from my GT-S5670 using xda app-developers app
lordsolrac2 said:
I'm trying to make a Stock based rom myself, therefore I'm trying to refrain from using a Custom ROM
Click to expand...
Click to collapse
Add the root .zip files manually.. !
Edward Cullen
Seems Logical But also, I'm trying to do Certaind Modifications... Such as, GO Launcher's Main Theme By Default? In my case it's to set another theme as default...
Try SuperOneClick
It *might* work,it works on most fons/firmwares
Read the list of supported devices from their site
And don't blame me if something goes wrong
Might work. Yet, I preffer to do it the Normal Recovery Way
Sorry to revive but, I tried SuperOneClick... It gets stuck in Step #7 (Waiting For Device) ._.
lordsolrac2 said:
Sorry to revive but, I tried SuperOneClick... It gets stuck in Step #7 (Waiting For Device) ._.
Click to expand...
Click to collapse
means you didn't connect the device in debugging mode
Belive Me I *DID* Otherwise I wouldn't be able to use adb in the first place.
I downloaded another package, with a Batch script. Since it failed, I wanted to see what was going on, I did each step one by one manually.
And I found out, the error is on remounting /system...
I did :: 'adb shell "/data/local/tmp/busybox mount -o remount,rw /system" and returned "Busybox: access declined (are you root?)"
I'm guessing besides adb I would use CWM to root it, but as told, it didn't work...
use update.zip then run using stock recovery not cwm.....
Ok. But then how do I restore my normal Stock ROM Recovery? (Without Resetting?) My Custom ROM's nearly finished though. Well... The Pre-alpha.
lordsolrac2 said:
Ok. But then how do I restore my normal Stock ROM Recovery? (Without Resetting?) My Custom ROM's nearly finished though. Well... The Pre-alpha.
Click to expand...
Click to collapse
By flashing the stock rom again
Press Thanks on getting Helped by me
Well that was easy ._. lol Thanks (Fixed)
I'm running 4.1.1 on my I9020A rooted. Stock Rom and Kernel. I searched the forums and the web, and every article I find gives instructions on going back to 2.3.X, THEN removing root. I don't want to go back, in fact I only want to un-root shortly, then go back to a rooted phone.
So my question is, Can I go through the locking steps of un-rooting, but leave the current ROM (4.1.1) installed?
Christopher_M said:
I'm running 4.1.1 on my I9020A rooted. Stock Rom and Kernel. I searched the forums and the web, and every article I find gives instructions on going back to 2.3.X, THEN removing root. I don't want to go back, in fact I only want to un-root shortly, then go back to a rooted phone.
So my question is, Can I go through the locking steps of un-rooting, but leave the current ROM (4.1.1) installed?
Click to expand...
Click to collapse
Delete, IN THIS ORDER:
/system/Superuser.apk
/system/xbin/su
/system/bin/su
Reboot your phone.
Root gone. If you want to root again, go to Androidsu.com, download the appropriate zip file, flash it, and you have root again.
oldblue910 said:
Delete, IN THIS ORDER:
/system/Superuser.apk
/system/xbin/su
/system/bin/su
Reboot your phone.
Root gone. If you want to root again, go to Androidsu.com, download the appropriate zip file, flash it, and you have root again.
Click to expand...
Click to collapse
Thanks for the quick reply! Should I additionally go through the fastboot steps of locking the bootloader as well?
Christopher_M said:
Thanks for the quick reply! Should I additionally go through the fastboot steps of locking the bootloader as well?
Click to expand...
Click to collapse
No. Unlocked bootloader and root are 2 different things.
polobunny said:
No. Unlocked bootloader and root are 2 different things.
Click to expand...
Click to collapse
What he said. Unless you're returning your phone for warranty repair or you're worried about security (like me), there's no reason to lock your bootloader.
I see. Thank you guys!
I have no Superuser.apk in the System/ folder.
I can only find com.noshufou.android.su-1.apk in data/app/
The other two files you listed I have found.
Christopher_M said:
I have no Superuser.apk in the System/ folder.
I can only find com.noshufou.android.su-1.apk in data/app/
The other two files you listed I have found.
Click to expand...
Click to collapse
That's the one. Delete it, it's the app to manage the su rights. su in xbin/bin is the binary for SuperUser
Ok, so I attempted to unroot. I opened es file explorer (Which launched with SU rights) and I was able to delete com.noshufou.android.su-1.apk in data/app/.
Then when I tried to delete su in /xbin, I was denied. Tried deleting su in /bin as same results. Denied.
Any thoughts?
Just flash stock. Now unrooted. To go back flash CWM and SU. This sounds a lot easier if oldblue's suggestion isn't working for you.
Use this for step by step.
http://forum.xda-developers.com/showthread.php?t=1785672
Sent from my Nexus S using xda premium
jayjay3333 said:
Just flash stock. Now unrooted. To go back flash CWM and SU. This sounds a lot easier if oldblue's suggestion isn't working for you.
Use this for step by step.
http://forum.xda-developers.com/showthread.php?t=1785672
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Yea, that was the conclusion I was coming too. Thanks for the help guys. :good:
You need to delete su binary via adb. Don't believe you can delete it while phone is under Android...
polobunny said:
You need to delete su binary via adb. Don't believe you can delete it while phone is under Android...
Click to expand...
Click to collapse
I'm new to android / linux. Been a Windows admin for 15+ years. I thought it not possible to delete SU while using SU, but I figured I'd try anyway. So ADB requires phone in FASTBOOT mode, correct?
Christopher_M said:
I'm new to android / linux. Been a Windows admin for 15+ years. I thought it not possible to delete SU while using SU, but I figured I'd try anyway. So ADB requires phone in FASTBOOT mode, correct?
Click to expand...
Click to collapse
No, just debugging mode.
MercilessLTD said:
No, just debugging mode.
Click to expand...
Click to collapse
In this case I think he would need to be in fastboot though.
For A701 users only running Jelly Bean Only.
Boot image used: AV051_A701_1.021.00_WW_GEN1. Should work fine on other JB builds.
New Version 3 uploaded 23/10/2012
Should fix ADB commands for /System Remount Thanks Vorbeth
2 Parts. Part 2 is full /system RW.... also know as ROOT for the A701 on JB who took the OTA
Part 1 is For people using the previous "andlommy" image flash..... For JB OTA see part 2...
Part 1
This is meant to replace your boot.img after performing the Root image flash from this thread by andlommy;
http://forum.xda-developers.com/showthread.php?t=1911437
Ok people, as some may realize, the current "root" procedure of fastbooting images doesn't allow full /system remount. This can be seen if you try to update your superuser binary. Superuser can't remount /system. Yes, you can probably delete some files via file manager, however, if you use a root app that calls for a /system remount, well, it's not going to happen. Not like it should be.
Also, the 701 doesn't have a reliable CWM, so we do things the old fashioned (and safer) way.
This method has been around in the 500 forums for some time now. Recently, I gave info to the 210 users to get the /system remount working on their tabs. I currently use the same. Why nobody tried it here, well.....
Basically it involves modifying the zimage to change security, and allow remounts. It does not involve the kernel itself, as it remains stock.
Replaces Stock A701 Boot.img
1. Allows for full /System RW
2. Increased IO over stock.
And yes, I do use the modified boot image, 2nd revision.
As always, you have to thank people who helped you in the past and present:And I owe a lot to these guys. (which is why I hit the Donate button for them)
Vorbeth
Civato
EZTerry
Skrilax_CZ
LinuxSociety
NOTE" You must have unlocked bootloader"
Also, you do this at your own risk.Most of you know this already.
Installation:
For previous somewhat Rooted JB installations.
Download the following package and unzip to your system.
FIX-JB-ROOT
1. Connect your tablet
2. USB Debugging is on
3. Open a command window where you unzipped the Fix-JB-Root
4. Type: adb reboot bootloader
after tab reboots to bootloader download, Type;
5. fastboot flash boot JB_701V3_boot.img
6. After success, reboot tablet.
7. Start Superuser and update binaries.
Part 2
AS A ROOT PROCESS. 701 only After OTA to JB.
Note that this is an alternative to the image flash method. You need only to OTA to JB, then follow the instructions.....
Needs Testing on a Stock JB 701 Make sure you've unlocked your bootloader
1. Follow the above procedures in part 1
2. After restart, with tab connected, open a CMD Window where you unzipped the package.
3. Type the following commands;
a. adb devices (and hit Enter. You should see your device listed)
b. adb remount /system (and hit Enter. You should see remount successful)
c. adb push su /system/xbin
d. adb shell chmod 6755 /system/xbin/su
e. Get Superuser and Busybox from the Playstore. Start Superuser, check for updating binaries. Install Busybox.
Hopefully this roots and grants /system RW. I don't have a stock 701JB, so would appreciate feedback if this works or not.
MD
Works perfect Thank you. Now we only nee CM10 for our 701
Thanks MD! Going to give the 4.1.1 another go this weekend, using this boot. Will let you know how it goes )
MD are you able to delete apk from "/system/vendor/app"?
IronFly said:
MD are you able to delete apk from "/system/vendor/app"?
Click to expand...
Click to collapse
Absolutely. Just moved Solitaire.apk into /Data/app
Use your root explorer and check for RW.
Remember, this just fixes a shortcoming in the original "pre-rooted image flashing" from 4.0.4 to 4.1.1 where you can't get system remounts from some root apps.
As stated near the end of the post, I haven't tried it on a "stock non-rooted" JB build.
MD
Hi,MD,Can you help me for the problem:
http://forum.xda-developers.com/showthread.php?t=1934569
fishwood said:
I installed a update.zip(Acer_AV043_A701_0.006.00_WW_GEN1.zip).
then,My A701 restarted, but it's stuck at the ACER logo.
I hook up this device to the PC ,but not go to fastboot mode , "MTB drivers" is no found.
I pressed the "volume up"- and the "power"-button at the same time, released the power-button when the screen turns on and switched the lock switch on and off and on and off: top left corner of the screen says "Erasing Userdata... Unrecoverable bootloader error (0x19000008).
Who can help me? thks.
Click to expand...
Click to collapse
fishwood said:
Hi,MD,Can you help me for the problem:
http://forum.xda-developers.com/showthread.php?t=1934569
Click to expand...
Click to collapse
I answered in your original thread.
MD
Hi MD,
Slightly off-topic, but just to let you know. Tried this with the flawed 4.1.1 install we've discussed in the other thread, still no joy!! It was a long shot that I thought was worth a go anyway
misteral1970 said:
Hi MD,
Slightly off-topic, but just to let you know. Tried this with the flawed 4.1.1 install we've discussed in the other thread, still no joy!! It was a long shot that I thought was worth a go anyway
Click to expand...
Click to collapse
Yeah, I meant to tell you yesterday it won't help your situation. Your issue, is you're stuck on the ICS bootloader and it won't update to the JB one. Not to mention now, you have that "Hybrid Mix". Maybe one day can come up with a solution for it. Trying to get my hands on a 701 Service Rom.
Acer won't fess up the SBK (Secure Bootloader Key), so it sort of makes NVFlash non-usable unless we have it.
The service rom uses NVFlash, which in theory will change bootloaders (it's what we used in the 500 forums).
But until then, we're sort of stuck. I still have one trick up my sleeve, but's it's a long shot, and not even sure it'll work. Might perma-brick your tab. Will look at my old files.
MD
MD got your method working thanks for sharing this MOD!
RiceDie said:
MD got your method working thanks for sharing this MOD!
Click to expand...
Click to collapse
Which method? Experimental Root? Or just the full System RW?
Also, which build Rom are you running Mate?
MD
MD -- Any chance to get this working on the A700 with OTA 4.1.1? Your post seems very specific about being only for the A701, so I don't want to risk it.
I tried looking into the exploit involving adb restore, but it looks like the A700 must have this fixed as "ADB Restore xxx" results in being told how to use ADB commands.. (a la http://forum.xda-developers.com/showthread.php?t=1886460)
Also I looked into symlinking, like they do for the Kindle HD exploit but that only works since 4.0 let you rename tmp to tmp.bak and then do a link exploit.. :\
Also I was thinking if we could somehow maybe apply this root, if it's still applicable in 4.1?
http://sed.free.fr/root_android.html
My problem is I don't know how to get the init.rc file to read what's going on -- does anyone have a stock init.rc file and can provide the contents?
--edit--
Oh I see, this may not work for the A700 as there hasn't been a "full ROM" released, therefore we don't have the boot.img to modify? Is that correct? As I can see the kernel is actually blocking the system remount, right?
bschrib said:
MD -- Any chance to get this working on the A700 with OTA 4.1.1? Your post seems very specific about being only for the A701, so I don't want to risk it.
I tried looking into the exploit involving adb restore, but it looks like the A700 must have this fixed as "ADB Restore xxx" results in being told how to use ADB commands.. (a la http://forum.xda-developers.com/showthread.php?t=1886460)
Also I looked into symlinking, like they do for the Kindle HD exploit but that only works since 4.0 let you rename tmp to tmp.bak and then do a link exploit.. :\
Also I was thinking if we could somehow maybe apply this root, if it's still applicable in 4.1?
http://sed.free.fr/root_android.html
My problem is I don't know how to get the init.rc file to read what's going on -- does anyone have a stock init.rc file and can provide the contents?
--edit--
Oh I see, this may not work for the A700 as there hasn't been a "full ROM" released, therefore we don't have the boot.img to modify? Is that correct? As I can see the kernel is actually blocking the system remount, right?
Click to expand...
Click to collapse
The root method should work the same as with ICS and JB.
Basically need an 700 ICS and JB boot.img. to do the mod. Takes about 10 minutes. Fastboot the boot image, download SU and BB. Should be good to go.
MD
I've posted a full A700 JellyBean ROM in the general section - http://forum.xda-developers.com/showthread.php?t=1946415
I extracted the boot.img and made the required changes but it didn't seem to work.
Either it failed to boot (tested using fastboot boot) or "adb remount" failed.
I will have another try later today once I get time on the laptop again.
Sent from my A700 using Tapatalk HD
Vorbeth said:
I've posted a full A700 JellyBean ROM in the general section - http://forum.xda-developers.com/showthread.php?t=1946415
I extracted the boot.img and made the required changes but it didn't seem to work.
Either it failed to boot (tested using fastboot boot) or "adb remount" failed.
I will have another try later today once I get time on the laptop again.
Sent from my A700 using Tapatalk HD
Click to expand...
Click to collapse
Should have a modded boot image in a day or so. Seems the boot images are the same for all builds for 700 JB.
It's the weekend, so some family time is on order.
Thanks for the GB full update rom.
MD
Hi,
I was one of the first people who updated their A701 with the unrooted JB ROM which was posted on XDA forums. The update was flawless and smooth using the external SD card and normal recovery method. Last night I tried to unlock my device and root it using step by step instructions given on OP. Device has unlocked but it is still not rooted. I checked using Root Checker app. Have I missed any steps in performing the root operation? Please help.
Additionally after doing all the steps in the OP I reinstalled the original JB update ROM using external SD card and recovery method. Bootloader is still unlocked and device is still not rooted. Device is working fine as far as I can tell.
Awaiting expert advice and help!
Best regards,
So how can I revert back to the original locked boot image as the current boot image cannot be locked using "fastboot oem lock"?
farazjk said:
So how can I revert back to the original locked boot image as the current boot image cannot be locked using "fastboot oem lock"?
Click to expand...
Click to collapse
Did you try updating your superuser binaries after you completed? Start Superuser, select the "i" icon at the top, and tap the "update binaries" from the menu.
Did you install BusyBox?
I haven't had a lot of feedback on the JB stock alternative root.
The alternative "root" process was reported successful by one member who did 2 tabs. However, it doesn't mean it works on all it seems. The original intent, was to fix the inability to update binaries (/system remount) when using the "image flash" of the pre-rooted JB image andlommy provided us in his thread. Which it does indeed fix.
As for reinstalling the locked bootloader, there is only one way to do it. And that is, to install a full rom, not an update. The patch update probably sees the unlocked bootloader, and just ignores it. EDIT: Seems Acer hasn't released a FULL JB Rom for the 701 yet.
Or, you can fastboot install the pre-rooted JB image that andlommy posted. It's what I used after I took the OTA.
Or, you can install the German JB CWM, and use zero-nulls CWM root install Option 3 from HERE. I have it (German JB CWM) installed, but personally only use it for flashing an install, and NOT for making a recovery backup or doing wipes. So far, the Germans haven't had any issues with it. (this is probably the method I would use).
The working version of JB CWM can be found HERE
Also, you can use the Superuser CWM install from HERE
Until Acer gives us the SBK (secure bootloader key), we can't use NVFlash to flash an unlocked bootloader back unfortunately.
Understand though, the 51x and 70x are extremely temperamental. Some of us already found out the hard way a few months ago. They are not so forgiving as the 50x tabs were.
So I would be very careful about major changes.
MD
Moscow Desire said:
Did you try updating your superuser binaries after you completed? Start Superuser, select the "i" icon at the top, and tap the "update binaries" from the menu.
Did you install BusyBox?
I haven't had a lot of feedback on the JB stock alternative root.
The alternative "root" process was reported successful by one member who did 2 tabs. However, it doesn't mean it works on all it seems. The original intent, was to fix the inability to update binaries (/system remount) when using the "image flash" of the pre-rooted JB image andlommy provided us in his thread. Which it does indeed fix.
As for reinstalling the locked bootloader, there is only one way to do it. And that is, to install a full rom, not an update. The patch update probably sees the unlocked bootloader, and just ignores it. EDIT: Seems Acer hasn't released a FULL JB Rom for the 701 yet.
Or, you can fastboot install the pre-rooted JB image that andlommy posted. It's what I used after I took the OTA.
Or, you can install the German JB CWM, and use zero-nulls CWM root install Option 3 from HERE. I have it (German JB CWM) installed, but personally only use it for flashing an install, and NOT for making a recovery backup or doing wipes. So far, the Germans haven't had any issues with it. (this is probably the method I would use).
The working version of JB CWM can be found HERE
Also, you can use the Superuser CWM install from HERE
Until Acer gives us the SBK (secure bootloader key), we can't use NVFlash to flash an unlocked bootloader back unfortunately.
Understand though, the 51x and 70x are extremely temperamental. Some of us already found out the hard way a few months ago. They are not so forgiving as the 50x tabs were.
So I would be very careful about major changes.
MD
Click to expand...
Click to collapse
Thanks MD for your informative reply. I tried to update SU binaries but there was no option to do it. superuser app only states su binaries not found. Busybox cannot start because it does not get all the required permissions.
I could flash rooted JB ROM by andlommy but that would wipe all my apps and data. As you have suggested that only full stock ROM can restore bootloader so till Acer releases this getting back to original state is not possible.
I guess if the unlocked boot image is not harmful in anyway and if any future updates pushed by Acer will still be receivable and applicable then best thing to do would be to let the device stay with unlocked boot loader.
Once again thank you for your help and support.
Best regards,
Faraz
farazjk said:
Thanks MD for your informative reply. I tried to update SU binaries but there was no option to do it. superuser app only states su binaries not found. Busybox cannot start because it does not get all the required permissions.
I could flash rooted JB ROM by andlommy but that would wipe all my apps and data. As you have suggested that only full stock ROM can restore bootloader so till Acer releases this getting back to original state is not possible.
I guess if the unlocked boot image is not harmful in anyway and if any future updates pushed by Acer will still be receivable and applicable then best thing to do would be to let the device stay with unlocked boot loader.
Once again thank you for your help and support.
Best regards,
Faraz
Click to expand...
Click to collapse
The unlocked bootloader will have no effect on normal day to day operations.
I'll try and get a 700 or 701 stock user to run a couple of things to get the SU issue sorted out. Shouldn't take that long. Probably a matter of using adb to push it through.
The 700 already has a JB Full rom update package, so hopefully the 701 will get one soon as soon as somebody locates it
Think it's time to bother Acer, and see about a SBK......
MD
the root is now possible by using a hack: 1st flash the retail china boot, root, flash back the Retail Hong Kong boot
@echo off
cls
adb reboot bootloader
moto-fastboot flash boot boot_china.img
moto-fastboot reboot
adb kill-server
adb wait-for-device
adb shell mv /data/local/12m/batch /data/local/12m/batch.bak
adb shell ln -s /data /data/local/12m/batch
adb reboot
adb wait-for-device
adb.exe shell rm /data/local.prop
adb.exe shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
adb.exe reboot
adb.exe wait-for-device
adb.exe remount
adb.exe push su /system/bin/su
adb.exe shell chmod 04755 /system/bin/su
adb.exe push Superuser.apk /system/app
adb.exe shell chmod 0666 /system/app/Superuser.apk
adb.exe push RE.apk /system/app
adb.exe shell chmod 0666 /system/app/RE.apk
adb.exe shell "echo \"ro.kernel.qemu=0\" > /data/local.prop"
adb.exe shell rm /data/local.prop
adb.exe shell rm /data/local/12m/batch
adb.exe shell mv /data/local/12m/batch.bak /data/local/12m/batch
adb reboot bootloader
moto-fastboot flash boot boot.img
moto-fastboot reboot
echo ROOTED
PAUSE
#echo on
download files from dropbox.com/s/ff3jjxt6vf3faj0/4.0.4HKTW_Root.7z
Please not that I've found the info on a chinese site, but i can't find for the moment the reference for it in my bookmarks. Similar info can be found bbs.angeeks.com/thread-2387514-1-1.html
Thank you for the link.I also saw this topic but I could not register and get the link.so I did this manually.
Thank you,this rom is the best!
Sent from my ME865 using xda app-developers app
Thank you...
Been searching how to root A2 ICS ME865 Asian Retail for months!
Tried and tried til gave up until found this post!
Thank you again!
THANK YOU
Questions
Hi,
I tried several methods with no success. The issue is that the /system is read only, so it can't be written. Now I'm planning to try this one also.
The questions are:
1. Does it reflash only the bootloader or the whole Android on my mobile?
2. If just the bootloader is reflashed how will the /system mounted to rw?
3. If it reflashes Android what image will be finally put on my device? Will I have problems with my mobile after having boot.img flashed?
4. Is there any way to save the existing image before reflashing it?
Thanks,
T
Thanks
I have had my me865 for about a month, have tried many different ways to root. This one worked. Thank you very much.:victory::highfive:
I'm a newb here so excuse the stupidity.
When i dl the file from the link you provided do i just run ROOT (the batch file) or do i need to do something else first.
I tried other rooting methods for my me865 but they didn't work.
Any help would be much appreciated.
SwordsmanK said:
I'm a newb here so excuse the stupidity.
When i dl the file from the link you provided do i just run ROOT (the batch file) or do i need to do something else first.
I tried other rooting methods for my me865 but they didn't work.
Any help would be much appreciated.
Click to expand...
Click to collapse
No stupidity exist in a genuine problem you need help with. As for your question, yes it's basically to run the root batch file as long as you enable Unknown sources and USB debugging. If you've already tried all of this and still no go then I'm not sure. One thing when I'm always re-rooting is that when my phone is rebooting, I sometimes unplug and reinsert the USB so that it completes successfully. Keep trying and I recommend the newer one-click root files. :thumbup:
Sent from the Ace's MB865 using xda-developers app
Well that was easy, the phone is now rooted.
Many thanks to both Ace and h1ms3lf ! :good:
SwordsmanK said:
Well that was easy, the phone is now rooted.
Many thanks to both Ace and h1ms3lf ! :good:
Click to expand...
Click to collapse
You're very welcome, glad it worked out for you. :thumbup::thumbup:
Sent from the Ace's MB865 using xda-developers app
Not working in my ME865 (ICS) :crying:
mescalyto said:
Not working in my ME865 (ICS) :crying:
Click to expand...
Click to collapse
You are sure that You have a Hong Kong Firmware (HKTW 6.7.2_GC-220-EDS-3-65)? If you don't have HK firmware, You should use this
alrojas said:
You are sure that You have a Hong Kong Firmware (HKTW 6.7.2_GC-220-EDS-3-65)? If you don't have HK firmware, You should use this
Click to expand...
Click to collapse
Yes, I have a Hong Kong Firmware. I already tried many root options and none work (sorry for the English)
alrojas said:
You are sure that You have a Hong Kong Firmware (HKTW 6.7.2_GC-220-EDS-3-65)? If you don't have HK firmware, You should use this
Click to expand...
Click to collapse
OK... so Have you enabled Unknown sources and USB debugging?
alrojas said:
OK... so Have you enabled Unknown sources and USB debugging?
Click to expand...
Click to collapse
You joking when you ask me that? ... Normally I did that already, I know what are the steps to root. Just not work!
what doesn't work? maybe if you tell us more we can help. it work for 99.99% of people using this method.
Help with directions
Good morning , this is my first post on xda. I recently bought an atrix 2, and been reading the most i could. However im still unsure on how to get the things done. I post in this thread cause it think i might have the Honk kong firmware, but i want to know how do i check that?. The phone is a ME865 model and came with 2.3.6 GB, and i did an update to this system version, 55.91.109.ME865.Retail.en.05 succefull. Now i get another OTA that i suspect is ICS which is 67.220.3.en.05. I have not done any modifications or installed any recovery yet.
So my first question is,am i in HKTW firmware? if yes, should i use the OTA ICS upgrade?.
If positive, then when im on ICS what rom should i flash, i know its the retail china rom but can i use the one form here? http://forum.xda-developers.com/showthread.php?t=1934874 and then after rooting , should i use the HTKTW rom from the link, to go back?
From there i would like to know if i can use the BMM recovery. And if i can do any type of backup with it before or after some point in case of any trouble. I know theres a method called FXZ , but i dont know to what rom i should fxz back in this particular case. After the ICS update can i fxz back to GB , or theres no need and i could fxz back to a clean ICS HKTW rom?
Finally. iwould like to try 4.2.2 roms, like Mokee. What steps do you recomend me to follow from my current version 2.3.6 GB. Sorry if my grammar isnt good, ill try to explain again if needed. Thanks in Advance.
Alemossa said:
Good morning , this is my first post on xda. I recently bought an atrix 2, and been reading the most i could. However im still unsure on how to get the things done. I post in this thread cause it think i might have the Honk kong firmware, but i want to know how do i check that?. The phone is a ME865 model and came with 2.3.6 GB, and i did an update to this system version, 55.91.109.ME865.Retail.en.05 succefull. Now i get another OTA that i suspect is ICS which is 67.220.3.en.05. I have not done any modifications or installed any recovery yet.
So my first question is,am i in HKTW firmware? if yes, should i use the OTA ICS upgrade?.
If positive, then when im on ICS what rom should i flash, i know its the retail china rom but can i use the one form here? http://forum.xda-developers.com/showthread.php?t=1934874 and then after rooting , should i use the HTKTW rom from the link, to go back?
From there i would like to know if i can use the BMM recovery. And if i can do any type of backup with it before or after some point in case of any trouble. I know theres a method called FXZ , but i dont know to what rom i should fxz back in this particular case. After the ICS update can i fxz back to GB , or theres no need and i could fxz back to a clean ICS HKTW rom?
Finally. iwould like to try 4.2.2 roms, like Mokee. What steps do you recomend me to follow from my current version 2.3.6 GB. Sorry if my grammar isnt good, ill try to explain again if needed. Thanks in Advance.
Click to expand...
Click to collapse
mmmm... I don't see the HKTW on the System Version, so I think you have the Chinese Version. Anyway You should try OTA Upgrade if you want ICS. If you use OTA Update or FXZ files then It's not possible go back to GB. But in my expirience ICS is much better and smooth than GB.
If your upgrade is the Hong Kong Version... and You dont want that version always You could try another ICS Firmware (MB or ME) from the link you posted above. But again in my experience the ME Firmware are much more smooth than MB Firmware.
To flash firmwares... You need 3 things:
The firmware (ICS 4.0.4): http://forum.xda-developers.com/showthread.php?t=1934874
RSD Lite: http://fwteam.grupoandroid.com/OTAs/RSDLite6.1.5.zip
and Drivers: https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/78863/p/30,6720,8109
Later of download the firmware and install RSD Lite and drivers What you need to do is:
Connect the phone to PC
Turn off the phone and then press the volumen +, volumen - and power button, the three at the same time.
Then, you select AP Fastboot.
Open RSD Lite and click the three points (...) and select the firmware downloaded
Click Decompress only wait and...
Click Start button and wait...
Obviously in the proccess do not disconnect the phone. And you need 60-70% of battery at least.
It takes about 10 minutes aprox and the first boot takes another 10 minutes. All you need to do is wait until your phone ask you to SELECT A LANGUAGE.
This video can help you. http://www.youtube.com/watch?v=prToF5JXqSA
the difference is that you must select your firmware downloaded.
On the other hand... If you want to try ROMs based on JB 4.2.2... It's necessary upgrade to ICS.
I dont test Mokee ROM, but usually Its necessary to install ClockWorkMod Recovery (a.k.a. CWM Recovery)... and for that You should install Atrix2Bootstrap app ( 1st Attached, Unknown sources must be enable), then:
Open the app, XD
Click Bootstrap Recovery Button to install the Recovery (You must be root for this, so if you are not... You can read this thread (if you don't have the Hong Kong Version), download the files and execute the bat file for root your phone.
Click Reboot Recovery Button and wait... and that's all. XD
For flashing ROM, First...
Select Wipe cache partition and Yes. Then
Select install zip from sdcard,
Then... Choose zip from sdcard (The Mokee ROM should be on the sdcard) and Yes
Finally Reboot System Now.
I hope this can help you.
Rooting
Thanks a lot you cleared some important questions i had. So now i successfully upgraded via OTA to ICS 4.0.4 to 6.7.2_GC-220-EDS-3. That means im on HKTW rom right?. From this point on, how should i root this phone? Do i first flash with RSD Lite the fastboot-p3_edison-edison-user-4.0.4-6.7.2_GC-180-EDS-20-31-release-keys-ChinaRetail-CN_chn.tar, then i use the root(still dont know how) and then flash back the fastboot-p3_edison-edison-user-4.0.4-6.7.2_GC-220-EDS-3-65-release-keys-Retail-05_hktwn.tar with RSD lite?.
Also should i wipe any data or cache before flashing with RSD lite?. Can i install the BMM recovery ( needed for most 4.2.2 roms) before doing the rooting process and make some sort of backup just to be safe?. Thanks in advance
Alemossa said:
Thanks a lot you cleared some important questions i had. So now i successfully upgraded via OTA to ICS 4.0.4 to 6.7.2_GC-220-EDS-3. That means im on HKTW rom right?. From this point on, how should i root this phone? Do i first flash with RSD Lite the fastboot-p3_edison-edison-user-4.0.4-6.7.2_GC-180-EDS-20-31-release-keys-ChinaRetail-CN_chn.tar, then i use the root(still dont know how) and then flash back the fastboot-p3_edison-edison-user-4.0.4-6.7.2_GC-220-EDS-3-65-release-keys-Retail-05_hktwn.tar with RSD lite?.
Also should i wipe any data or cache before flashing with RSD lite?. Can i install the BMM recovery ( needed for most 4.2.2 roms) before doing the rooting process and make some sort of backup just to be safe?. Thanks in advance
Click to expand...
Click to collapse
Hi!, If you have an image same as first attached file (specially the HKTW between the red lines) then Yes, You have the Hong Kong/Taiwan version XD.
Now, RSD Lite is a tool for flashing Factory ROMs also known as Stock ROMs, XD. The Stock ROM don't have root access. Everytime you flash Stock ROM with RSD Lite... you loose the root access if you already have it.
On the other hand, I understand you want to have root access, then as you have the HK/TW version, you need an "special" method for gain root access (download it from here). First of all, You need to install the drivers and connect the phone to PC. Then follow the steps:
The Connection to PC must be MTP mode (it's the default connection I think, but just in case you read this)
Open settings on your phone and tap on developer options
Check/Enable "USB Debugging"
Go back to settings and tap on security
Check/Enable "Unknown Sources"
Unzip the file on your desktop
Execute ROOT.bat and wait... (The phone will reboot several times... so don't freak out, lol)
If the method works well, you should see an image like 2nd attached file, and you should have installed an app named Superuser.
That's it!. Congrats you have root access and don't forget the words from uncle Ben: With great power comes great responsibility
PD: You can install any custom Recovery you want, Honestly...I never do Backup (I like clean installs) and only tested CWM Recovery (require root access) and Stock Recovery... That's all I needed, but you are a free man! so test all you want, but be careful in the process. Read the post several times. Always remenber the words from uncle Ben, always. LoL.
Hello folks,
just wanted to share with you the subject. I'm not a developer, so I cannot go too deeply in the procedure below. what I can ensure is that is working on my personal device, Padfone 2 model A68, bought in Italy with stock firmware IMM76I.WWE_9.8.8.55-0.
DISCLAIMER
should you decide to go for it, remember, I'm just a simple user willing to share a procedure that worked for him, I'm not a smartphone OEM... Accordingly:
I'll not be held responsible if you brick, melt, destroy your device, by following the below procedure... you are the solely and ultimate responsible of your actions and your property.
if after you unlock or root your phone you need to lock it back, or put it in a Virgin "out-of-the-box" state.... cannot help. consider this procedure irreversible.
If you understand the above and concur, well, you can go for the below procedure. otherwise you're kindly requested to stop reading here and NOT continue. tks a lot.
Backgroung
the rooting method is quite straight-forward, getting a stock boot.img and manipulate its ramdisk so that the device can then boot insecure.
Credits
A HUGE thanks to Schriss for his strong support in letting me understand what I was doin on my device:good:
And also a thanks to ChainFire and his insecure adbd (here)
WHAT YOU NEED
1. a padfone 2 with more than 70% battery available, and the above firmware installed (you might wanna try also if your device has different firmware, but I cannot garantee on the results you'll get.
2. this INSECURE ICS boot.img
OR
2a this insecure JB boot.img
OR
2b. you might wanna try this TW JB boot.img from TW JB
3. a valid ADB and FASTBOOT package (lots available within XDA, or already available if you have andorid SDK installed from http://developer.android.com/sdk/index.html)
4. a valid "su" binary, again you can find it in XDA or attached to this post.
5. Valid usb drivers (see mama ASUS website)
6. the infamous "UnLock.apk" (again kindly provided by ASUS)
ONE CLICK procedure (script based) kindly provided by Padfone.cl
here
OR
STEP BY STEP PROCEDURE (MS WINDOWS OS Only)
0. place all of the files (boot.img, adb and fastboot exe's, SU binary) in one folder of your pc and open a cmd session in it.
1. install drivers at point 5 above
2. Unlock your bootloader: install the apk at point 6. above follows all the instructions to get a bootloader unlocked
3. once done the phone can be put in FASTBOOT mode (black screen with "Fastboot MODE !!!" and ASUS LOGO) , with one of the two methods below.
3a. power off device. then push and hold power on + vol up.
3b. if your device is connected to your pc, verify it is in debug mode (under setup/development) and run "adb reboot-bootloader"
4. if not already done connect the device to your pc and wait the drivers selfconfiguring
5. check if fastboot.exe see your device, type in cmd "fastboot devices", if nothing is shown means you're missing drivers, or using a bad fastboot exe.
6. check if your device boots with the insecure img at point 2. of what-you-need list. type in cmd "fastboot boot boot.img"
6a. if it reboots normally... CONGRATS your device is ok with my boot.img and you can root your phone
6b. if it goes into bootloop or bootlock or in QHUSB_DLOAD state, well sorry you cannot go ahead. just push and hold power on your device. it will reboot using its boot.img Sorry no root for you
7. if you're lucky and you get 6a response, you can now ROOT your device
7a. in cmd session type the below
adb remount (system answer "remount succeded" that's a confirmation you can act as superuser)
adb push su /system/bin/
adb shell
chmod 06755 /system/bin/su
type exit, to get off the adb shell.
7b. Collect superuser.apk at the end of this post and place it in same folders of adb.
In cmd session type
"adb push Superuser.apk /system/app
adb shell chmod 06755 /system/app/Superuser.apk"
IF YOU JUST WANT YOUR DEVICE ROOTED PROCEDURE STOPS HERE FOLLOWING IS JUST an ADDED-ON
8. OPTIONAL just in case you want to keep the insecure adbd onboard, not necessary to mantain root condition.
8a. put the device in FASTBOOT mode as above and type in cmd "fastboot flash boot boot.img", this just overwrite your stock boot.img and inoculate the insecure boot.img in your device on a stable basis.
guess it's all.
let me know if it's working for you gentlemen, and remember the disclaimer above and in general just make sure you always know what you're doin... I'll post the boot.img file shortly during today.
reserved
reserved
Hi,
Thanks for a guide, that should make it very easy for Padfone 2 users to get root
Disclaimer mentions going back to Stock and relocking - this would need a separate Guide with disclaimers because it's a little dangerous IF you have flashed anything non-stock into Boot partition and then re-locked. But if rooting was done by fastboot boot, then I believe the device could be re-locked and you would still have your root. Until you flash some Asus official Update which would overwrite /System/bin, making SU disappear.
as for points 8 and 8a, it is possible, that you don't need to permanently flash insecure boot.img. After SU has been pushed to /System/bin, you can try simply rebooting as normal and the file should remain on System partition, which is separate from boot.img. It's quite likely, that root will remain and so no flashing would be needed at all if you want to stay on Stock ROM and just need root
Root is really all about putting SU in /System/bin folder, the rest are tricks to make it happen.
schriss said:
Hi,
Thanks for a guide, that should make it very easy for Padfone 2 users to get root
Disclaimer mentions going back to Stock and relocking - this would need a separate Guide with disclaimers because it's a little dangerous IF you have flashed anything non-stock into Boot partition and then re-locked. But if rooting was done by fastboot boot, then I believe the device could be re-locked and you would still have your root. Until you flash some Asus official Update which would overwrite /System/bin, making SU disappear.
as for points 8 and 8a, it is possible, that you don't need to permanently flash insecure boot.img. After SU has been pushed to /System/bin, you can try simply rebooting as normal and the file should remain on System partition, which is separate from boot.img. It's quite likely, that root will remain and so no flashing would be needed at all if you want to stay on Stock ROM and just need root
Root is really all about putting SU in /System/bin folder, the rest are tricks to make it happen.
Click to expand...
Click to collapse
yes, I got your points I'm amending the first post. tks
Thumbs up guys. U all did it!
Padfone 2 just got epic! I have been following your thread every single day schriss and ivalex. Well done and heaps of gratitude.
After rooting,do you think its possible to flash jellybean using clockworkmod in the near future?Thanks!
Sent from my PadFone 2 using xda app-developers app
Scarletdeath said:
After rooting,do you think its possible to flash jellybean using clockworkmod in the near future?Thanks!
Sent from my PadFone 2 using xda app-developers app
Click to expand...
Click to collapse
this kind of stuff require time and testing. and as you said first we need a good CWM porting, than someone to port CM10 or a stock-modified JB when it will be available.
we'll see
Ivalex said:
this kind of stuff require time and testing. and as you said first we need a good CWM porting, than someone to port CM10 or a stock-modified JB when it will be available.
we'll see
Click to expand...
Click to collapse
I think getting CWM should be very straightfoward as soon as someone dumps Recovery partition with the commands posted earlier or in the other thread. Testing it should also be simple because it can be booted like insecure boot :victory:
A very good step for our padfone2!
4.1 is coming very soon (within Dec if Asus didn't lie on us) and unlocking at this stage may void the OTA.. (Given CWM is not avail ATM and it is uncertain how soon can the new rom.zip can be made)
even OTA can be performed, boot img is updated and need to be exploited again (with your experience I think it will be much more straight forward later on tho )
These makes me struggling whether I should unlock my padfone2 now or not..
Anyway, as said this is really a good step to our padfone2 at this stage, keep it up and I am looking forward to some point that I have no more struggle and unleash my beast at once!
Greatly appreciated! :good::good:
Hmmm I keep failing at the last step 7b. Keep getting err msg that installation failed when SuperSU tried to update the binary. On WWE stock now and have tried various SU binaries all with same results....
Any suggestions?
kahei036 said:
A very good step for our padfone2!
4.1 is coming very soon (within Dec if Asus didn't lie on us) and unlocking at this stage may void the OTA.. (Given CWM is not avail ATM and it is uncertain how soon can the new rom.zip can be made)
even OTA can be performed, boot img is updated and need to be exploited again (with your experience I think it will be much more straight forward later on tho )
These makes me struggling whether I should unlock my padfone2 now or not..
Anyway, as said this is really a good step to our padfone2 at this stage, keep it up and I am looking forward to some point that I have no more struggle and unleash my beast at once!
Greatly appreciated! :good::good:
Click to expand...
Click to collapse
I'm pretty sure that unlocked Padfone 2 can be relocked with fastboot command just like for example HTC One X. Then it would be possible to use Asus OTA updates.
But I also think Asus OTA could be flashed with CWM. Then, same insecure rooting story starts over.
---------- Post added at 05:20 PM ---------- Previous post was at 05:17 PM ----------
turtle76 said:
Hmmm I keep failing at the last step 7b. Keep getting err msg that installation failed when SuperSU tried to update the binary. On WWE stock now and have tried various SU binaries all with same results....
Any suggestions?
Click to expand...
Click to collapse
So you installed SuperSU, then rebooted just to be sure and then tried updating?
Anyway, in case of such problems, I think we could push latest SuperSU.apk and other files same way as SU, we just push them to /System/app folder where all apk belong, then reboot.
schriss said:
I'm pretty sure that unlocked Padfone 2 can be relocked with fastboot command just like for example HTC One X. Then it would be possible to use Asus OTA updates.
But I also think Asus OTA could be flashed with CWM. Then, same insecure rooting story starts over.
---------- Post added at 05:20 PM ---------- Previous post was at 05:17 PM ----------
So you installed SuperSU, then rebooted just to be sure and then tried updating?
Anyway, in case of such problems, I think we could push latest SuperSU.apk and other files same way as SU, we just push them to /System/app folder where all apk belong, then reboot.
Click to expand...
Click to collapse
Worked finally Thks for the advice pal
turtle76 said:
Worked finally Thks for the advice pal
Click to expand...
Click to collapse
Thanks for the advice. I'll add also push and chmod commands for supersu as add-on In case of problem as the one You had.
Inviato dal mio PadFone 2 con Tapatalk 2
Great news
The only thing I was waiting for before deciding on buying this device was to see how well its supported by this community. Thanks guys, may be finally time to let my good ol HTC HD2 rest now
Great work Padfone 2 community!
Would like to know if anyone has tried this on the IMM761.TW_9.8.8.55-0 firmware?
Did it work?
RagnarokRO said:
Great work Padfone 2 community!
Would like to know if anyone has tried this on the IMM761.TW_9.8.8.55-0 firmware?
Did it work?
Click to expand...
Click to collapse
It shld work. I was trying on tw firmware and didn't encountered issues till step 7b which was due to other issue.
getting mine friday did see on asus site there is a tool for unlock of boot loader.
Is this phone and pad any good? Can not wait for mine
I guess I am stupid because I can't get anything to work.
downloaded everything
but I can't make any commands work
I open the cmd and don't know if the " are suppose to be there or not and nothing works
Burley1 said:
I guess I am stupid because I can't get anything to work.
downloaded everything
but I can't make any commands work
I open the cmd and don't know if the " are suppose to be there or not and nothing works
Click to expand...
Click to collapse
Have you switched to the folder that contains fastboot and those stuffs in command prompt?