There appear to be two main options for rooting Samsung devices on linux and mac.
Option 1: (un-tested) root.zip (recovery)
This method roots your stock 2.3 rom from in recovery (stock or CWM)
1. Copy Root.zip to your sdcard.
2. Turn your phone off
3. Boot your phone into recovery mode. (Hold HOME+POWER buttons. When the screen turns on let go of POWER but keep holding HOME. After you enter recovery mode, let go of HOME.)
4. Select “apply update from sdcard”
5. Find and select Root.zip
6. When it’s done installing, select “reboot system now”
7. Go to apps and look for 'superuser'. If you see it, your phone is rooted.
Option 2: (un-tested) flash CWM from stock recovery:
This gives you the freedom of a custom recovery, flashed on the device from stock recovery
1. Download recovery-clockwork-5.0.2.6-galaxyace-fix.zip
2. Put recovery-clockwork-5.0.2.6-galaxyace-fix.zip on your sdcard
3. Boot into current stock (default) recovery (zip also compatible with CWM recovery)(Hold HOME+POWER buttons. When the screen turns on let go of POWER but keep holding HOME. After you enter recovery mode, let go of HOME.)
4. Go to "apply update from sdcard"
5. Select "recovery-clockwork-5.0.2.6-galaxyace-fix.zip"
6. When it finishes, power off and boot back into recovery mode to check it has installed (it should say "ClockworkMod Recovery v5.0.2.6" somewhere)
Option 3 (un-confirmed): use Heimdall.
An open source, cross-platform, alternative to Odin.
Heimdall is officially supported on the Galaxy S (and S variants including Galaxy Tab)
It allows you to do pretty much anything Odin can do (interact with download mode), and so you can flash a root kernel to gain root and CWM recovery.
Although supposedly untested on the Galaxy Ace, heimdall should be able to flash the usual root precedure (rooting kernel with CWM).
It would be great if someone could verify heimdall works for the Galaxy Ace
Option 4: (un-tested) root your ROM using the zergRush exploit (from the Revolutionary team).
zergRush rooting scripts: Linux, Mac, Windows
For the zergRush exploit scripts, you only root your firmware, so CWM will need to be installed manually afterwards if you want it.
Now that you have root, you should be able to (optionally) flash CWM from an app or over adb using flash_image) (DO YOU NEED ROOT IF THIS IS DONE IN RECOVERY(STOCK)?)
Apps that can flash CWM include:
* CWM Manager
* Flash image GUI
_DO NOT USE_ ROM Manager (reported unstable)
To flash using ADB and flash_image, download flash_image and an CWM recovery img then run:
Code:
cd directory-containing-files/
adb remount
adb push flash_image /system/bin/flash_image
adb shell chmod 0755 /system/bin/flash_image
adb push recovery.img /sdcard/
adb shell
flash_image recovery /sdcard/Recovery.img
rm /sdcard/recovery.img
reboot recovery
Or from the phone's terminal (if BusyBox is installed):
first put recovery.img & flash_image onto /sdcard/
Code:
cd directory-containing-files/
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mv /sdcard/flash_image /system/bin/flash_image
chmod 0755 /system/bin/flash_image
flash_image recovery /sdcard/Recovery.img
rm /sdcard/recovery.img
reboot recovery
DISCLAIMER: I do not personally own a Samsung phone, and have not yet tested these methods (although I am interested to hear how well they work,and will do my best to update the post). I am however planning to root a friends Galaxy Ace and possibly also an Galaxy S2, so will be testing some of these soon (I'm not sure I should try the untested heimdall on a friends Ace though)
This seems almost utterly pointless, prove me wrong?
Bofu said:
This seems almost utterly pointless, prove me wrong?
Click to expand...
Click to collapse
+1... I don't understand the point.. Why take a longer way when the shorter way is faster, efficient and trustworthy...
ace_viknesh said:
Why take a longer way when the shorter way is faster, efficient and trustworthy...
Click to expand...
Click to collapse
Sorry, which way is this shorter more trustworthy way?
The point of this is listing the methods I believe to be compatible with linux (and by extension mac)
I am new to Samsung phones and do not possess one myself, but understand that using Odin is restricted to Windows.
I will be flashing CWM Recovery to a Galxacy Ace soon and will try methods that have been tested (friend's phone)
If you know of other methods or if one of the listed methods does not work, I will update the post
Also if anyone can confirm heimdall to work with the Ace this would be the first time on xda (searching I've found only people saying it may work) the Ace is not on its supported list, however as it uses the same protocol (right?) it should work?
If however the mods believe this post to be useless or irrelevant, they are welcome to move it to the appropriate location
Point 1- Hopefully useful for Linux and Mac users.
Point 2- If on Windows its much easier and takes very less time..
Also u told about ROM Manager (reported unstable),... Dude leave unstable it bricks our phone... mAking it unusable...
Best way to root is to put the upd.zip in rooting section and flashing in recovery... Can thr be any other way better than that?
Bofu said:
This seems almost utterly pointless, prove me wrong?
Click to expand...
Click to collapse
I use OS X exclusively and this was a very useful post, and at least well written and clear. Most guides blindly assume we all use Windows, not everyone does!!!
For context, owning OS X I originally used the upd1.zip method, flashed via original recovery and it worked, which I suppose is the fastest method you don't cover.
I certainly didn't know about heimdall, great to see an open-source cross platform alternative to odin! Don't need to use it just yet, though testing will be invaluable for future use...
So thanks to the OP for writing clearly about alternative options.
But instaling CWM isn't rooting, you can have CWM without root.
Wysłane z mojego GT-S5830 za pomocą Tapatalk
actually speaking in case of SGA you don't need a PC to root or to anything except heavy logcat
What restrictions using odin on windows are you referring to?
Restriction: it doesn't work if you're not using Windows is the restriction... ;-)
dragonnn said:
But instaling CWM isn't rooting, you can have CWM without root.
Click to expand...
Click to collapse
Thanks, I wasn't sure of this as on my Desire I had to unlock the bootloader (s-off it) due to security features (and this was closely related to the rooting process). I use the term rooting as it seems the most generic, if anyone suggests a better word I will gladly consider changing the title
Prashanthme said:
Also u told about ROM Manager (reported unstable),... Dude leave unstable it bricks our phone... mAking it unusable...
Click to expand...
Click to collapse
I've updated the post advising against using ROM Manager, thanks
Prashanthme said:
Best way to root is to put the upd.zip in rooting section and flashing in recovery... Can thr be any other way better than that?
Click to expand...
Click to collapse
Thank you for this, I will get some details and update the post shortly to include this
Edit: I added the root.zip method
btw, I may rework the post to reflect whether current ROM will be rooted, recovery installed, or both and then list methods for each outcome.
matts95 said:
Thanks, I wasn't sure of this as on my Desire I had to unlock the bootloader (s-off it) due to security features (and this was closely related to the rooting process). I use the term rooting as it seems the most generic, if anyone suggests a better word I will gladly consider changing the title
I've updated the post advising against using ROM Manager, thanks
Thank you for this, I will get some details and update the post shortly to include this
Edit: I added the root.zip method
btw, I may rework the post to reflect whether current ROM will be rooted, recovery installed, or both and then list methods for each outcome.
Click to expand...
Click to collapse
Anyone tested Heimdall yet?
Related
I installed Rom Manager and then downloaded the recovery for Samsung galaxy s2. When hit reboot into recovery. I am unable to perform any operations in CWM. I had to connect the phone via usb and issue a "adb reboot" command to get back.
How do we make cwm work.
http://forum.xda-developers.com/showpost.php?p=18160002&postcount=26
ptulluri said:
I installed Rom Manager and then downloaded the recovery for Samsung galaxy s2. When hit reboot into recovery. I am unable to perform any operations in CWM. I had to connect the phone via usb and issue a "adb reboot" command to get back.
How do we make cwm work.
Click to expand...
Click to collapse
Also must people are having issues flashing in cwm after using ROM manager. If you try installing from cwm and get verification error you needed to flash again then kernel and don't use ROM manager
Flashed CWM and nothing is happening
I flashed CWM Recovery 5.0.2.3 using the instructions here http://forum.xda-developers.com/showthread.php?t=1285823. However, when i go into CWM and select something the only thing that happens is the logo for CWM shows up with a black screen. When I push the power button again it will go back to the list.I am using the stock rom and it hasn't even been rooted yet. When I try to root using super one click, it gets stuck at step #5. Please Advise.
NDN
Dont use Rom Manager. It is known to have issues with the S2
I use CWM Manager and have no problems.....
noobdeeznutz said:
I flashed CWM Recovery 5.0.2.3 using the instructions here http://forum.xda-developers.com/showthread.php?t=1285823. However, when i go into CWM and select something the only thing that happens is the logo for CWM shows up with a black screen. When I push the power button again it will go back to the list.I am using the stock rom and it hasn't even been rooted yet. When I try to root using super one click, it gets stuck at step #5. Please Advise.
NDN
Click to expand...
Click to collapse
The key mapping is different. I had the same issue. Try the home key to select in place of the power button and the back key for back
Also if not rooted I do not think CWM will work...
Use this by Entropy512 it is flawless.
http://forum.xda-developers.com/showthread.php?t=1286432
SNadler said:
The key mapping is different. I had the same issue. Try the home key to select in place of the power button and the back key for back
That was it... THANKS!!!
Click to expand...
Click to collapse
SNadler said:
Also if not rooted I do not think CWM will work...
Click to expand...
Click to collapse
Root is having access to root account in os. It has nothing to do with cwm since cwm is loaded before the os loads.
They are irrelevant
Sent from my SAMSUNG-SGH-I777
Pirateghost said:
Root is having access to root account in os. It has nothing to do with cwm since cwm is loaded before the os loads.
They are irrelevant
Sent from my SAMSUNG-SGH-I777
Click to expand...
Click to collapse
In addition, all of our CWM-enabled kernels are "insecure" kernels - They give root at all times to ADB sessions, this is why SuperOneClick works after flashing them.
But only ADB sessions get root, so you use the "rooted" ADB shell to root the system partition. After that you've got perma-root until you nuke su and Superuser.apk from /system
Entropy512 said:
In addition, all of our CWM-enabled kernels are "insecure" kernels - They give root at all times to ADB sessions, this is why SuperOneClick works after flashing them.
But only ADB sessions get root, so you use the "rooted" ADB shell to root the system partition. After that you've got perma-root until you nuke su and Superuser.apk from /system
Click to expand...
Click to collapse
I think I am confused again?
When I flash a kernel, I have root. I have never used super one click. Just flashed your kernel. I thought that is what gave me root? Are you saying I still do not have root for /system files? Or does your kernel push su and superuser when it is flashed?
SNadler said:
I think I am confused again?
When I flash a kernel, I have root. I have never used super one click. Just flashed your kernel. I thought that is what gave me root? Are you saying I still do not have root for /system files? Or does your kernel push su and superuser when it is flashed?
Click to expand...
Click to collapse
Mine does, codeworkx's doesn't.
Setting a kernel to be insecure is a lot easier and takes less time than putting in a robust root-inject script.
SNadler said:
I think I am confused again?
When I flash a kernel, I have root. I have never used super one click. Just flashed your kernel. I thought that is what gave me root? Are you saying I still do not have root for /system files? Or does your kernel push su and superuser when it is flashed?
Click to expand...
Click to collapse
Entropy512 said:
Mine does, codeworkx's doesn't.
Setting a kernel to be insecure is a lot easier and takes less time than putting in a robust root-inject script.
Click to expand...
Click to collapse
Entropy512: Does this mean that codeworkx's kernel must be flashed with SuperOneClick in order to have complete root (to /system)... but with your kernels we don't need to flash SuperOneClick? If so, in order to unroot (without SuperOneClick) I suspect one would have to flash the non-root stock kernel? Thx
DoctorQMM said:
Entropy512: Does this mean that codeworkx's kernel must be flashed with SuperOneClick in order to have complete root (to /system)... but with your kernels we don't need to flash SuperOneClick? If so, in order to unroot (without SuperOneClick) I suspect one would have to flash the non-root stock kernel? Thx
Click to expand...
Click to collapse
Yes. (Unless you flash an su package with CWM instead of SuperOneClick)
Really, all SuperOneClick is doing are the following commands, assuming you've got a proper su binary and Superuser.apk:
Code:
adb remount
adb push su /system/xbin/su
adb shell chmod 6755 /system/xbin/su
adb push Superuser.apk /system/app/Superuser.apk
adb shell chmod 644 /system/app/Superuser.apk
Entropy512 said:
Yes. (Unless you flash an su package with CWM instead of SuperOneClick)
Really, all SuperOneClick is doing are the following commands, assuming you've got a proper su binary and Superuser.apk:
Code:
adb remount
adb push su /system/xbin/su
adb shell chmod 6755 /system/xbin/su
adb push Superuser.apk /system/app/Superuser.apk
adb shell chmod 644 /system/app/Superuser.apk
Click to expand...
Click to collapse
I understand (I think) that chmod 644 is to set the permission but what is chmod 6755?
SNadler said:
Dont use Rom Manager. It is known to have issues with the S2
I use CWM Manager and have no problems.....
Click to expand...
Click to collapse
I have downloaded CWM Manager and I have tried to install it but it has failed. Is there a different type of process to doing this other than opening it through root explorer?
what are you trying to do? just use the 3 button combo or extended power option to boot into recovery and flash away?
Ok, I am having a huge issue with trying to flash a custom rom. I will try to explain this the best way I can. I have had the same problem as above when trying to use CWM in recovery. Here is what I did:
- I unrooted my phone
- flash CWM with "SGH-I777_ClockworkMod-Recovery_5.0.2.3.tar"
- then it boots into CMW recovery and I can't do jack. When I try to select anything I just get a blank screen with the clock workz logo. If I hit the volume up and down buttons again the list of options comes back, but I will be stuck with the same situation if I try to select any options.
I was able to successfully root my phone in another instance using galaxys2root.com's method, however when I tried to use cwm I also ran into the same problem. I have yet to be able to use anything in cwm recovery. Please help me. I have flashed my phone multiple times and probably bricked it also. Luckily i haven't done any damage yet, but i would like to be able to flash roms. I am still kinda new to flashing roms, but i was able to flash my old infuse like a champ without any of these problems.
ducksauce88 said:
Ok, I am having a huge issue with trying to flash a custom rom. I will try to explain this the best way I can. I have had the same problem as above when trying to use CWM in recovery. Here is what I did:
- I unrooted my phone
- flash CWM with "SGH-I777_ClockworkMod-Recovery_5.0.2.3.tar"
- then it boots into CMW recovery and I can't do jack. When I try to select anything I just get a blank screen with the clock workz logo. If I hit the volume up and down buttons again the list of options comes back, but I will be stuck with the same situation if I try to select any options.
I was able to successfully root my phone in another instance using galaxys2root.com's method, however when I tried to use cwm I also ran into the same problem. I have yet to be able to use anything in cwm recovery. Please help me. I have flashed my phone multiple times and probably bricked it also. Luckily i haven't done any damage yet, but i would like to be able to flash roms. I am still kinda new to flashing roms, but i was able to flash my old infuse like a champ without any of these problems.
Click to expand...
Click to collapse
Use the home soft key to select stuff in CWR, not the power button.
Sent from my SGH-I777 using XDA App
i didnt read all of the posts until after i posted. thanks for not slashing me. so it looks like i use the home button to select then the back button still goes back. got it.
On a side not, I do not remember reading about that within the posts for rooting and flashing clockworkz. I tend to skip over things when reading, but I think someone should put that in big fat red letters "USE HOME BUTTON TO SELECT".
I would like to flash the new Rom that is rooted and teamed in the development section. My question is how? Im a noob and have no clue. I used odin to root, but had to do a system restore because my phone was acting very slow. (laggy and only 1800 on benchmarks. Now its at 2700.) it also says i need to use a new kernel. I would like to use the overclocked one but don't know how to do anything. Please give me detailed step by steps. Think you
Sent from my SAMSUNG-SGH-I717 using Tapatalk
There is step by step directions in each one of the posts. But the simple version is download Odin 1.85 and put your phone into download mode then connect odin and the phone should show up as a COM port. After that put the kernel in the pda section and hit start. That flashes the kernel and you are done.
Orange_furball said:
I would like to flash the new Rom that is rooted and teamed in the development section. My question is how? Im a noob and have no clue. I used odin to root, but had to do a system restore because my phone was acting very slow. (laggy and only 1800 on benchmarks. Now its at 2700.) it also says i need to use a new kernel. I would like to use the overclocked one but don't know how to do anything. Please give me detailed step by steps. Think you
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
not to sound like a jerk or rude , my best advice to you is instead of asking for someone to tell you step by step, is to read the threads for the modifications you want to do in your phone, and re read the steps, when I first started in the flashing game back in the winmo days I would print out pages from here with the guides and steps the devs would post so I could sit in front of the pc and have the info right in
front of me without having the need to open and close the browser while trying to use the pc for flashing. I also made friends so I could just pm someone if I had any issues/questions, keeping me from having the need for posting and making too many questions on the threads , thus helping me avoid the famous "use the search button" comment.
Good luck and have fun!!
roloracer said:
not to sound like a jerk or rude , my best advice to you is instead of asking for someone to tell you step by step, is to read the threads for the modifications you want to do in your phone, and re read the steps, when I first started in the flashing game back in the winmo days I would print out pages from here with the guides and steps the devs would post so I could sit in front of the pc and have the info right in
front of me without having the need to open and close the browser while trying to use the pc for flashing. I also made friends so I could just pm someone if I had any issues/questions, keeping me from having the need for posting and making too many questions on the threads , thus helping me avoid the famous "use the search button" comment.
Good luck and have fun!!
Click to expand...
Click to collapse
I read them about ten times each. I just want to know what i should do if there is anything special to do.
So do i flash the overclocked kernel first or the Rom?
Oh, and you don't sound like a jerk. Im just very nervous and don't want to brick this and have to go back to my 3gs...
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Orange_furball said:
I read them about ten times each. I just want to know what i should do if there is anything special to do.
So do i flash the overclocked kernel first or the Rom?
Oh, and you don't sound like a jerk. Im just very nervous and don't want to brick this and have to go back to my 3gs...
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
if you're going all the way I would suggest flashing clockworkmod recovery thru odin, doing a nandroid backup, then flash the rom, then flash the kernel, most roms already have a kernel included, but not in the case of twopumpchump's rom, as he states his don't have the kernel, so you flash the kernel afterwards, I'm sure in the future when they start to have more roms and kernel choices the devs will probably add their kernel of choice for their rom/build, therefore if you decide to use a different kernel in that situation you flash the desired kernel after the rom so if the rom has one it won't replace the one you want, you understand? meaning you always flash the kernel after the rom.
roloracer said:
if you're going all the way I would suggest flashing clockworkmod recovery thru odin, doing a nandroid backup, then flash the rom, then flash the kernel, most roms already have a kernel included, but not in the case of twopumpchump's rom, as he states his don't have the kernel, so you flash the kernel afterwards, I'm sure in the future when they start to have more roms and kernel choices the devs will probably add their kernel of choice for their rom/build, therefore if you decide to use a different kernel in that situation you flash the desired kernel after the rom so if the rom has one it won't replace the one you want, you understand? meaning you always flash the kernel after the rom.
Click to expand...
Click to collapse
Ok thanks.
I'm trying to do a clockworkMod recovery, but the galaxy note isn't listed.... What do i do?
Now im not sure if you can answer this, but what do i do with this? Its from Da_G's kernel guide
"You will need modified libraries to take full advantage of this kernel as they override speeds at times, you can find these here.
You'll have to push them over adb for now after flashing the kernel, when CWM is up I will make a CWM zip for it.
From the directory with adb and the three .so files:
Code:
adb remount
adb push libhardware_legacy.so /system/lib/
adb push librpc.so /system/lib/
adb push libandroid_runtime.so /system/lib/
adb shell chmod 0644 /system/lib/libhardware_legacy.so
adb shell chmod 0644 /system/lib/librpc.so
adb shell chmod 0644 /system/lib/libandroid_runtime.so
adb reboot
Souce code available at: https://github.com/dagnarf/sgh-i717-dagkernel"
thanks!
Orange_furball said:
Ok thanks.
I'm trying to do a clockworkMod recovery, but the galaxy note isn't listed.... What do i do?
Now im not sure if you can answer this, but what do i do with this? Its from Da_G's kernel guide
"You will need modified libraries to take full advantage of this kernel as they override speeds at times, you can find these here.
You'll have to push them over adb for now after flashing the kernel, when CWM is up I will make a CWM zip for it.
From the directory with adb and the three .so files:
Code:
adb remount
adb push libhardware_legacy.so /system/lib/
adb push librpc.so /system/lib/
adb push libandroid_runtime.so /system/lib/
adb shell chmod 0644 /system/lib/libhardware_legacy.so
adb shell chmod 0644 /system/lib/librpc.so
adb shell chmod 0644 /system/lib/libandroid_runtime.so
adb reboot
Souce code available at: https://github.com/dagnarf/sgh-i717-dagkernel"
thanks!
Click to expand...
Click to collapse
this is for the use of adb(android debug bridge) and you need android sdk/jdk installed on pc to have commands for android thru command prompt.
if you want to install cwm from androiduser00110001 all you need is odin in your pc and the rest is this.
Follow these instructions:
You will need Odin to flash recovery. Check the threads on how to use and where to download it from.
Download recovery HERE
Start Odin
Click on PDA
Browse to file odin_n1717_cwm_recovery_a1.tar
Make sure your phone is in download mode so Odin can flash
Flash file
Let phone reboot
Boot into recovery - Either use adb reboot recovery or power down phone, press volume up, volume down and power at same time to boot into recovery
Once in recovery, select power down phone
Let phone power down and then power it back up
Phone should reboot into OS fine, if not go into recovery and try again.
That is one bug so far. Mostly everything else works. If you get stuck in a CWR boot loop than just flash stock recovery that can be found HERE.
roloracer said:
this is for the use of adb(android debug bridge) and you need android sdk/jdk installed on pc to have commands for android thru command prompt.
if you want to install cwm from androiduser00110001 all you need is odin in your pc and the rest is this.
Follow these instructions:
You will need Odin to flash recovery. Check the threads on how to use and where to download it from.
Download recovery HERE
Start Odin
Click on PDA
Browse to file odin_n1717_cwm_recovery_a1.tar
Make sure your phone is in download mode so Odin can flash
Flash file
Let phone reboot
Boot into recovery - Either use adb reboot recovery or power down phone, press volume up, volume down and power at same time to boot into recovery
Once in recovery, select power down phone
Let phone power down and then power it back up
Phone should reboot into OS fine, if not go into recovery and try again.
That is one bug so far. Mostly everything else works. If you get stuck in a CWR boot loop than just flash stock recovery that can be found HERE.
Click to expand...
Click to collapse
Well, i couldnt get clockworkmod to work, but i went along with everything else (except the nandroid backup) My flash counter is at 11 now.... but i have a new rom! thanks again!
Orange_furball said:
Well, i couldnt get clockworkmod to work, but i went along with everything else (except the nandroid backup) My flash counter is at 11 now.... but i have a new rom! thanks again!
Click to expand...
Click to collapse
you're welcome, glad you got it done.
Eric-1987 said:
There is step by step directions in each one of the posts. But the simple version is download Odin 1.85 and put your phone into download mode then connect odin and the phone should show up as a COM port. After that put the kernel in the pda section and hit start. That flashes the kernel and you are done.
Click to expand...
Click to collapse
go to the saurom thread all ur answers r there DAGs oc kernel
JB calhoun said:
go to the saurom thread all ur answers r there DAGs oc kernel
Click to expand...
Click to collapse
Been solved a long while ago! Thanks tho!
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Do I have root?
First you install the unlock APK, unlock it...Install goo beta, Install Open-Script Recovery, reboot and ill have TRWP? and be able to install custom roms?
IM READY TO JUMP SHIP!
You have your recovery to install everything.....
Inviato dal mio Transformer Prime TF201 con Tapatalk 2
It has its own recovery? or do i need to install one...
David522d said:
It has its own recovery? or do i need to install one...
Click to expand...
Click to collapse
install one. get goo manager from market place. then go in goo manager, go to settings I believe. then tell it flash open script recovery. It will flash the TWRP recovery for prime. all touch screen based. then with goo manager, you can find all the great toms for prime in there and flash directly from there. plus it'll let you know when there is updates for your custom rom. check it out. IMO, has alot more features and more straight forward that CWM recovery.
actually there a sticky thread in developement section that has video guides for the prime. one of them shows you how to install this recovery I mentioned if you unsure.
also a video showing you how to flash a custom rom, with TWRP and goo manager, is there also
demandarin said:
install one. get goo manager from market place. then go in goo manager, go to settings I believe. then tell it flash open script recovery. It will flash the TWRP recovery for prime. all touch screen based. then with goo manager, you can find all the great toms for prime in there and flash directly from there. plus it'll let you know when there is updates for your custom rom. check it out. IMO, has alot more features and more straight forward that CWM recovery.
actually there a sticky thread in developement section that has video guides for the prime. one of them shows you how to install this recovery I mentioned if you unsure.
Click to expand...
Click to collapse
1. Install Unlock APK. Unlock.
2. Reboot, Install Goo Manger, Install Open script recovery. Reboot into TWRP recovery
3. Install ROMS?!?!!?!
As in I don't have to root after I unlock it already does?
I don't have root on this tablet, its on .21. I don't want to brick it, so will these steps be perfect?!
THANKS!!!
Anyone ?
I don't know about goo manager but I flashed cwm touch with fastboot (normal cwm didn't work and twrp wasn't out)
Sent from my sgs2 running cm9
David522d said:
1. Install Unlock APK. Unlock.
2. Reboot, Install Goo Manger, Install Open script recovery. Reboot into TWRP recovery
3. Install ROMS?!?!!?!
As in I don't have to root after I unlock it already does?
I don't have root on this tablet, its on .21. I don't want to brick it, so will these steps be perfect?!
THANKS!!!
Click to expand...
Click to collapse
Yeah steps sound good. you could always flash a ROM that has root. I dont think you need root to install twrp. Double check though. post in twrp thread to make sure.
Hate to be a pain the butt
But does anyone know if that method will work 100%
Sorry fellas dont want to end up with a 500$ paprr weight
David522d said:
1. Install Unlock APK. Unlock.
2. Reboot, Install Goo Manger, Install Open script recovery. Reboot into TWRP recovery
3. Install ROMS?!?!!?!
As in I don't have to root after I unlock it already does?
I don't have root on this tablet, its on .21. I don't want to brick it, so will these steps be perfect?!
THANKS!!!
Click to expand...
Click to collapse
Unlocking will not root your prime. I think Goomanager needs superuser rights so you will need to be rooted to flash TWRP (at least it asks for SU when I check for rom updates).
I use CWM since there have been a few stories floating around of people bricking their primes when trying to restore using TWRP. I am sure it is fine but it just makes me a little nervous...
If you're unlocked, not rooted and want to install CWM follow method 1 here:
http://forum.xda-developers.com/showthread.php?t=1576937
David522d said:
Hate to be a pain the butt
But does anyone know if that method will work 100%
Sorry fellas dont want to end up with a 500$ paprr weight
Click to expand...
Click to collapse
There is nothing that will work 100%, but its pretty close, maybe 98%? Anytime someone does anything with the bootloader, recovery rom, or OS rom, there is a chance for bricking: interuption in the write process, loss of power, corrupted dl (crc check should catch most of those). If your worried about bricking it, leave your TFP stock and await the OTA's - that way if it gets bricked by Asus then they are responsible and you havent nullified your warranty.
Unlocking the bootloader allows the use of non stock bootloaders/recoveries to be installed and used. From the new bootloader/recovery, you can install a rom that either has root, or not. You don't even have to change roms after unlocking. The 2 are independent.
Right -
Unlocking with the APK does not root or in any other way modify or prep the prime for what you're about to do. Depending on your stock ROM revision this is either very easy or a complete pain in the ass, I'll provide both versions:
For Stock ROM ending .15 or earlier -
* DO NOT RUN THE GOO IM.MANAGER FIRST. Follow these steps below.
* Download Sparky's APK to root - it's in the development forum for the TF Prime. Run it. This will get you root access on the system. It's automated and practically idiot proof, just follow the on screen instructions.
* If you're going the Team Win route, once rooted, load up the Goo.im manager, then follow the instructions as per a rooted installation for getting TW Recovery into place. This is pretty painless really and works automatically, approve the Superuser permissions as required. Once the recovery is in, you can reboot into it and then get with the flashy.
-----
If you're on the Stock ROM ending .21, you're going to have to do what I did. As you're already unlocked using the BLOB files to downgrade -will- result in a hard brick. SO!
* Install ADB and Fastboot onto your system, as well as the universal USB naked driver which you can find on this forum.
* Search for DotTech install ADB and Fastboot - follow this guide, it's probably the easiest way to get a working fastboot and ADB environment up and running.
* Enable USB debugging on the tablet under developer options.
* Set up the universal driver, you'll need to reboot your TF201 and hold the POWER and VOLUME DOWN buttons until you see some text in the top corner. Do NOT press volume up to go into Recovery Image mode or you'll just walk into a dead end.
* Shortly after you'll see three icons, press volume down ONCE and then volume UP once, the USB icon in the middle should be highlighted and you should see text saying "Entering Fastboot Protocol" or similar.
* Plug the USB cable into the tab and the PC, test whether you have a working fastboot install by typing fastboot -i 0x0b05 reboot, if your tablet reboots without you touching it, then you've got working fastboot access. Remove the cable, reboot to fastboot mode as described above.
* Meantime, download openrecovery-twrp-2.1.3-tf201.blob from the team win site, and stuff it in the same directory that you set up Fastboot/ADB, rename it to twrp.blob. Plug your tablet back in and then issue the command fastboot -i 0x0b05 flash recovery twrp.blob , if this goes to plan you'll see a couple of lines of text on the command window which will tell you that it's been successfully flashed in. YOU STILL DO NOT HAVE ROOT THOUGH, SO NO SILLY STUFF
* Finally, download the ROM of your choice, place it in the base /sdcard directory, then reboot the tab and hold POWER and VOLUME DOWN, when you see the text, this time hit VOLUME UP, and you'll be sent into the team win recovery suite, at this point you can wipe and flash the newly prepared ROM as per normal.
* For the first occasion I -strongly- recommend you use Virtuous Prime-S as you can generate a solid backup environment out of it, as well as the fact it's not too departed from Stock, so it's a good way to break yourself in.
Hope this helps.
This whole blob thing is new for me since i have always insta-rooted, and CWM'ed any android device i get; but from what I've gathered, it is used by ASUS to lowlevel write the os on locked systems, similar to the way nvflash dumps img's directly to the memory. Once your unlocked with the CWM or twrp, then you can no longer use blobs, just the rom zips. The recovery rom handles the unpacking and dumping of the kernel and OS into the appropriate partitions. Some roms are zipped with install scripts that wipe your cache, user space and dalvik - but its always a safe bet to do that anyways.
Nice writeup Hobbesian
Well, some blobs are fine, but generally they're strictly either Team Win Recovery or Clockwork mod recovery suites, and they need to be slipped in using fastboot (I believe ROM manager and GOO managers use their own scripts to handle installation) as a rough rule. The "big" BLOB files which Asus puts out are a guarantee to hardbrick an unlocked device (some days I wonder if it would kill Asus to offer a route to re-lock and re-stock a device on the proviso that if you brick it doing so you're still out of warranty).
That said - Virtuous Prime is definitely an excellent first step into Custom ROM tinkering, it gives you root and all the associated useful features, as well as the ability to start experimenting with more feature heavy ROM builds such as Cyanogen and AOKP Cornerstone. They're even nice enough to include a partially tweaked build.prop which saves you a lot of the work in modifying that.
I should point out my guide is relevant only if you already applied the unlock APK to your system, if you haven't done so, there's alternative routes including the downgrade blob option to get root without unlocking your device.
paddycr said:
Unlocking will not root your prime. I think Goomanager needs superuser rights so you will need to be rooted to flash TWRP (at least it asks for SU when I check for rom updates).
I use CWM since there have been a few stories floating around of people bricking their primes when trying to restore using TWRP. I am sure it is fine but it just makes me a little nervous...
If you're unlocked, not rooted and want to install CWM follow method 1 here:
http://forum.xda-developers.com/showthread.php?t=1576937
Click to expand...
Click to collapse
1. Unlock Prime...
2. Do method 1
3. Then goo manger, install script. Reboot in team win recovery
4. Install AKOP =) !??!?!
yes?
David522d said:
1. Unlock Prime...
2. Do method 1
3. Then goo manger, install script. Reboot in team win recovery
4. Install AKOP =) !??!?!
yes?
Click to expand...
Click to collapse
The method 1 in the link will install ClockWorkMod which I use as my recovery. You can completly miss step 3. If you really want to use TWRP then do the goomanager thing.
However, before you do a wipe and install AOKP (ethher from CWM or TWRP) MAKE A BACKUP OF YOUR CURRENT ROM!! That's important (hence caps ) - people are always on here complaining that they are soft bricked because of a bad download and not making a backup.
EDIT: if you're in fastboot and you cannot get adb to recognize your prime you need to install the correct drivers for your pc/mac. Hobbesian describes how to do this a few posts above this. In his nice write up he also describes how to flash TWRP directly from fastboot. If you want TWRP, follow his instructions since you'll have less messing around to do.
paddycr said:
The method 1 in the link will install ClockWorkMod which I use as my recovery. You can completly miss step 3. If you really want to use TWRP then do the goomanager thing.
However, before you do a wipe and install AOKP (ethher from CWM or TWRP) MAKE A BACKUP OF YOUR CURRENT ROM!! That's important (hence caps ) - people are always on here complaining that they are soft bricked because of a bad download and not making a backup.
Click to expand...
Click to collapse
And flashing a rom with root therefor should give me root correct?
I sound like an idiot, but just to make sure
David522d said:
And flashing a rom with root therefor should give me root correct?
I sound like an idiot, but just to make sure
Click to expand...
Click to collapse
Yes, all of the roms will have root. Hit my thanks button if it works for you
paddycr said:
Yes, all of the roms will have root. Hit my thanks button if it works for you
Click to expand...
Click to collapse
Would it be easier to install CWM, then install TWR
David522d said:
Would it be easier to install CWM, then install TWR
Click to expand...
Click to collapse
I think both ways are the same. There's no correct answer to that. It depends on whether you would prefer to use CWM or TWRP.
Warning:
I will not be responsible for damage to your device(s) by using this exploit. Antivirus software and Play services will likely detect this as potentially malicious. It is an exploit, deal with it or don't use it. Do not mirror these applications without my permission!
PwnMyMoto is a replacement for my previously released MotoRoot. PwnMyMoto exploits three vulnerabilities, to gain root access, then to gain write to system. This is a traditional root, and doesn't use any 'hackery' to maintain su access unlike MotoRoot.
First we use bug 9695860 (aka second masterkey) to gain system user, then it uses a symlink attack to gain root access. After gaining root we exploit a flaw in the bootloader, allowing us to bypass the write protection applied to system. In the process we remove stock recovery, so OTAs will not be a worry.
Install PwnMyMoto by running:
adb install -r PwnMyMoto-<version and model go here>.apk
Click to expand...
Click to collapse
Then run PwnMyMoto, depending on the current root status of your phone it will reboot 2 or 3 times, after the last reboot it will uninstall it self and su will be installed on the actual system partition. Please install SuperSu from the market after this step is done.
We have two (ok more but were not going into that) boot modes. First is normal, which boots regular Android, and in this case boots with system write protected. Second is recovery mode, normally it boots recovery without write protection. Our exploit will hijack recovery bootmode and boot Android without write protection.
After running this exploit, if you boot normally /system will be write protected. If you boot to "recovery", Android will boot without write protection. If you wish to edit system, you must boot into "recovery" to do so, any changes made will stick and will work in either bootmode. My suggestion is to make your changes in "recovery" and run the device day to day in normal mode, until we are certain "recovery" mode will be 100% stable for day to day use.
The exploit will uninstall itself after successful exploitation.
To see if write protection is applied, you can run:
adb shell getprop ro.boot.write_protect
Click to expand...
Click to collapse
If it returns '1' then write protection is applied to /system, if it returns '0' then no write protection has been applied.
In the future we will have a replacement recovery, but at this time it is still in development. Enjoy.
Change Log:
1.4.3 allows detection of failed su installation (0 size su) and reinstallation)
1.4.1 adds reliability, and fixes issues for users when improper permissions are applied to su (Preventing updates).
1.2 - Bug fix for devices which had recieved OTAs.
If you used 1.1 and have a problem with recovery coming back, run the following command:
adb shell su -c "dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/dev/block/platform/msm_sdcc.1/by-name/recovery"
Click to expand...
Click to collapse
1.1 - initial release
Thanks!
Figure I should add that this does not allow usage of custom kernels at this time because everything is still signature checked.
Is there an unroot process?
alee said:
Is there an unroot process?
Click to expand...
Click to collapse
I'd assume you could boot into the recovery mode and just delete superuser, su, and busybox, but someone more knowledgeable should confirm.
Sent from my Nexus 7
Just an FYI, since I panicked a little, when the little Andy is shown lying on his back and it says "No command", just wait it out
Dr. Carpenter said:
Just an FYI, since I panicked a little, when the little Andy is shown lying on his back and it says "No command", just wait it out
Click to expand...
Click to collapse
It probably didn't work for you then. I was having the same problem earlier and again now.
I still have root. It did the same thing when booting to recovery. Guess I'll reinstall and give it another go.
Sent from my XT1080 using Tapatalk 4
Dr. Carpenter said:
I still have root. It did the same thing when booting to recovery. Guess I'll reinstall and give it another go.
Sent from my XT1080 using Tapatalk 4
Click to expand...
Click to collapse
It shouldn't boot to recovery since it is being replaced.
Sorry, meant when booting to "recovery". It went to the no command screen for a minute then rebooted to Android.
Sent from my XT1080 using Tapatalk 4
If you are running into an issue where it is booting into normal recovery, come find me on IRC. I think 1.1 fixed the bug but if it didn't i need to release 1.2/
OK, not sure what's going on now... The first time I ran it, the button said something like Click to root, now this time it said Boot into WP bypass. Hit it and same thing, back to the no command screen for a while and then a reboot. I was previously rooted, but based on the OP, that shouldn't make a difference. Back up now, and the app is still installed (it uninstalled the first time), still says the same thing.
Worked for me... Rooted w.o wp when booting to recovery
jcase said:
If you are running into an issue where it is booting into normal recovery, come find me on IRC. I think 1.1 fixed the bug but if it didn't i need to release 1.2/
Click to expand...
Click to collapse
first of all, thanks so much, and i apologize for the noob questions below, but i'd like some clarification if possible (perhaps a video would be helpful like on your previous releases).
1) does it matter which version of your moto root app and SU we are currently using?
2) what do you mean in the OP by normal mode and recovery mode? I mean i've used custom recovery and normal (adb) mode, but when you say "recovery mode" will have write access, does that mean you will have write access only while you are in recovery? I think it means that you get into regular android operating system (that is adb), but through some extra boot/recovery step. This is confusing.
3) which custom recovery is the stock recovery being replaced with?
4) how do we tell it to boot in "recovery mode" or "normal mode"?
5) which version of supersu should we use? is the regular one OK?
6) which IRC are you referring to in the above quote?
Version 1.2 should work on devices that had taken the OTA, 1.1 didn't reflash the recovery partition with boot for them.
a manual fix for those that used 1.1 is a single command
adb shell su -c "dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/dev/block/platform/msm_sdcc.1/by-name/recovery"
Click to expand...
Click to collapse
So am I to understand that in order to install this apk you have to use adb. Because it doesn't install like a normal apk it says that a signed version is already installed. Which is the other apk 1.1 if so this sucks I nuked my computer last night no adb. Will the 1.2 version allow me to install the apk normally over the 1.1
Never mind I see that its 1.2 now and it did install no problem and deleted itself and I have root. However like mistermojo I am confused as to how to get r/w I know how to get into recovery but once there do you just reboot and then you have r/w a little clarification would be appreciated. Thank you for the exploit and especially it being an apk since my computer took a **** last night.
bigv5150 said:
So am I to understand that in order to install this apk you have to use adb. Because it doesn't install like a normal apk it says that a signed version is already installed. Which is the other apk 1.1 if so this sucks I nuked my computer last night no adb. Will the 1.2 version allow me to install the apk normally over the 1.1
Never mind I see that its 1.2 now and it did install no problem and deleted itself and I have root. However like mistermojo I am confused as to how to get r/w I know how to get into recovery but once there do you just reboot and then you have r/w a little clarification would be appreciated. Thank you for the exploit and especially it being an apk since my computer took a **** last night.
Ok I can't get into stock recovery when I get into fastboot and choose recovery it goes to a black screen and like it is off I can get back into fast boot or just boot the phone normal but no recovery.
Click to expand...
Click to collapse
recovery is over written with this method. simply use an app that reboots to recovery and the phone will boot normally only write protection will be disabled.
Bigv
power off your phone
Press vol - and power key at the same time for 3 secs and release
You should be in the fastboot. Press vol - until you highlight recovery.
Press vol + to select and boot to android with write protect turned off
asuhoops8628 said:
Bigv
power off your phone
Press vol - and power key at the same time for 3 secs and release
You should be in the fastboot. Press vol - until you highlight recovery.
Press vol + to select and boot to android with write protect turned off
Click to expand...
Click to collapse
Got it my dumbas was pushing power not + and I was just turning the screen off not rebooting into recovery or normal power up thanks for the help. It sucks not being to run adb to check for write permission. But I was able to modify the media file in the ui and change the effect tick so I know it works.
mistermojorizin said:
first of all, thanks so much, and i apologize for the noob questions below, but i'd like some clarification if possible (perhaps a video would be helpful like on your previous releases).
1) does it matter which version of your moto root app and SU we are currently using?
2) what do you mean in the OP by normal mode and recovery mode? I mean i've used custom recovery and normal (adb) mode, but when you say "recovery mode" will have write access, does that mean you will have write access only while you are in recovery? I think it means that you get into regular android operating system (that is adb), but through some extra boot/recovery step. This is confusing.
3) which custom recovery is the stock recovery being replaced with?
4) how do we tell it to boot in "recovery mode" or "normal mode"?
5) which version of supersu should we use? is the regular one OK?
6) which IRC are you referring to in the above quote?
Click to expand...
Click to collapse
Basically what is going on is if you go to fastboot mode vol - and power at the same time you have the option to boot into recovery, however it isn't actually booting into a normal or custom recovery where you can flash it boots normally but has no write protection so that you can write to the system. Then once you write you can reboot normally. Is that correct jcase?
Q&A for [ROM + KERNEL] Tari's ASUS PadFone 2 (r150301)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM + KERNEL] Tari's ASUS PadFone 2 (r150301). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Hello Tari! I have Running your awesome ROM on my Padfone2, and i find it a very smooth and cool ROM! Thank You, for your Work in it!
I have a Question, - There is a Custom Lollipop ROM on XDA for Padfone S/X! Do you think that work on Padfone2? And the Nexus4 is almost the same hardware as Padfone2, is it possible that a Nexus4 Custom Lollipop ROM works on Padfone2?
Many, Thanks to you for your Work, Time and Engagement!
roselanguste said:
Hello Tari! I have Running your awesome ROM on my Padfone2, and i find it a very smooth and cool ROM! Thank You, for your Work in it!
I have a Question, - There is a Custom Lollipop ROM on XDA for Padfone S/X! Do you think that work on Padfone2? And the Nexus4 is almost the same hardware as Padfone2, is it possible that a Nexus4 Custom Lollipop ROM works on Padfone2?
Many, Thanks to you for your Work, Time and Engagement!
Click to expand...
Click to collapse
Thanks for the kind words roselanguste, I am glad you are satisfied with the ROM.
As for the Lollipop, porting it onto the Padfone2 would be lot of work. There are too many ASUS-specific details that would have to be changed, plus for the kernel to work we would need updated hardware modules and firmware. As far as I am concerned, KitKat is the last stop for our device.
can you give me step by step how to flash cwm after unlocking the phone (using ansarijavid method for unlock)?
kinda new for this stuff
running 8.1 64 bit
does this rom fix weird colour contrast after put the phone into sleep?
azurisu said:
can you give me step by step how to flash cwm after unlocking the phone (using ansarijavid method for unlock)?
Click to expand...
Click to collapse
Create a folder, download the needed files into it and open a terminal from there
Make sure the tools are present: sudo apt-get install android-tools-adb android-tools-fastboot
Enable USB Debugging on the phone
Boot into fastboot mode (Power, Volume up)
Install the CWM recovery: sudo fastboot -i 0x0b05 flash recovery cwm.img
Note: The above is for Linux - no extras are needed, you just plug in your phone and go. Windows users should probably need some drivers, enable ADB, and change the "sudo + COMMAND" parts.
azurisu said:
does this rom fix weird colour contrast after put the phone into sleep?
Click to expand...
Click to collapse
I have not had any contrast troubles, so I really can't tell. The kernel is the latest PF2 can handle, and the firmware is also up-to-date. There should be no issues.
tari01 said:
Create a folder, download the needed files into it and open a terminal from there
Make sure the tools are present: sudo apt-get install android-tools-adb android-tools-fastboot
Enable USB Debugging on the phone
Boot into fastboot mode (Power, Volume up)
Install the CWM recovery: sudo fastboot -i 0x0b05 flash recovery cwm.img
Note: The above is for Linux - no extras are needed, you just plug in your phone and go. Windows users should probably need some drivers, enable ADB, and change the "sudo + COMMAND" parts.
I have not had any contrast troubles, so I really can't tell. The kernel is the latest PF2 can handle, and the firmware is also up-to-date. There should be no issues.
Click to expand...
Click to collapse
weird,, i've been experiencing some weird colour issue since kitkat for PF2 released, and still happened on newest fw (11.4.8.23)
locking then unlocking the screen always trigger this, need to restart my device to get it back to normal
something like this..
padfoneclub.com/pl/forum/forum_viewtopic.php?15485
so i thought using custom rom will solve my issue haha
--------
reversiblity
tari01 said:
Create a folder, download the needed files into it and open a terminal from there
Make sure the tools are present: sudo apt-get install android-tools-adb android-tools-fastboot
Enable USB Debugging on the phone
Boot into fastboot mode (Power, Volume up)
Install the CWM recovery: sudo fastboot -i 0x0b05 flash recovery cwm.img
Note: The above is for Linux - no extras are needed, you just plug in your phone and go. Windows users should probably need some drivers, enable ADB, and change the "sudo + COMMAND" parts.
I have not had any contrast troubles, so I really can't tell. The kernel is the latest PF2 can handle, and the firmware is also up-to-date. There should be no issues.
Click to expand...
Click to collapse
i'm a completely noob about linux so my only question is : is the procedure reversible? my only fear is about this " sudo fastboot -i 0x0b05 flash recovery cwm.img" , if i type wrong a value what's going to happen? Brick or simply a failrure in the procedure?
Thanks in advance
Zollolo19 said:
i'm a completely noob about linux so my only question is : is the procedure reversible? my only fear is about this " sudo fastboot -i 0x0b05 flash recovery cwm.img" , if i type wrong a value what's going to happen? Brick or simply a failrure in the procedure?
Thanks in advance
Click to expand...
Click to collapse
This command is fairly safe. It simply means: "use fastboot to write the cwm.img image to an ASUS device (0x0b05 is your PadFone)". If you feel paranoid you can search for a Stock Recovery image. You can always flash that file instead of cwm.img to get your device back to factory state. Bricking is harder than you think. The bottom line: always read the instructions carefully, make sure you have EXACTLY what is required, and go slowly step-by-step. If you are unsure, or there is an error, do not try to fix it by yourself - go to the forums and tell the people about it, someone will surely help you out.
tari01 said:
This command is fairly safe. It simply means: "use fastboot to write the cwm.img image to an ASUS device (0x0b05 is your PadFone)". If you feel paranoid you can search for a Stock Recovery image. You can always flash that file instead of cwm.img to get your device back to factory state. Bricking is harder than you think. The bottom line: always read the instructions carefully, make sure you have EXACTLY what is required, and go slowly step-by-step. If you are unsure, or there is an error, do not try to fix it by yourself - go to the forums and tell the people about it, someone will surely help you out.
Click to expand...
Click to collapse
Thank you for the professional and specially quick answer I'm going to try the procedure tomorrow
i have to leave "A68_signed_030415_031241.zip" zipped?
Thanks
Zollolo19 said:
i have to leave "A68_signed_030415_031241.zip" zipped?
Thanks
Click to expand...
Click to collapse
Yes. ROMs are always packaged in a ZIP - you just send it to your CWM (sideload seems to be the fastest).
it's going automatically in recovery mode? Because i don't know how to enter in it and there're tons of procedure throughout the web.
i'm referring to this point : 3. Boot into recovery mode.
I thought that power + bottom up volume was for the recovery mode, indeed is for the fastboot mode.
Thanks for your courtesy
ULTRA LOL: i forgot to try power + volume down when i wrote this post, sorry xD
Zollolo19 said:
it's going automatically in recovery mode? Because i don't know how to enter in it and there're tons of procedure throughout the web.
i'm referring to this point : 3. Boot into recovery mode.
I thought that power + bottom up volume was for the recovery mode, indeed is for the fastboot mode.
Thanks for your courtesy
ULTRA LOL: i forgot to try power + volume down when i wrote this post, sorry xD
Click to expand...
Click to collapse
So it seems you have got it right, but just for future reference:
Power + Volume Up = fastboot/csc
Power + Volume Down = recovery
It goes for most Android devices, ASUS especially.
i'm blocked at point 9... it says "cannot read sideload".. i've tried solutions found online like rename folder, or use adb push but in this it says "acces: blocked"..
help please :crying:
news: when i tried the normal boot of the padfone it returned to original conditions, it's like new eek: . factory mode returned like new, too
Now how i can use the other procedure (without sideload) ? i have to put simply the file in the root?
Zollolo19 said:
i'm blocked at point 9... it says "cannot read sideload".. i've tried solutions found online like rename folder, or use adb push but in this it says "acces: blocked"..
help please :crying:
news: when i tried the normal boot of the padfone it returned to original conditions, it's like new eek: . factory mode returned like new, too
Now how i can use the other procedure (without sideload) ? i have to put simply the file in the root?
Click to expand...
Click to collapse
I see no reason why sideload or push shouldn't work. When you enter CWM recovery you select the sideload option and then send your ROM from the PC. On Debian and derivatives (Ubuntu, Mint, etc.) adb/fastboot tools are in system locations, so you need to run the commands with "sudo" to elevate your privileges.
Here are the detailed steps:
Boot into fastboot mode (Power, Volume up)
Install the CWM recovery: sudo fastboot -i 0x0b05 flash recovery cwm.img
Boot into recovery mode (Power, Volume down)
Select "wipe data/factory reset"
Select "install zip from sideload"
Send the ROM to the phone: sudo adb sideload ROMNAME.zip
Wait until it says it's done, then select "reboot"
When CWM asks "ROM may flash stock rocovery on boot. Fix?" Choose "No"
When CWM asks "ROM access possibly lost. Fix?" Choose "No"
Alternatively, you could simply plug in your phone, copy the ROM to the root folder (/sdcard) using nautilus/nemo or any other file manager you're using, then go to CWM and select "Install zip from SD card", then browse for it.
As for your phone looking like a fresh one, it's because you still have the stock ROM and it has been reset to factory settings. This should not bother you at all.
I tried everything with ubuntu but nothing... so i put the rom in the root and flashed by sd card. Everything seems to be ok now DDD I'm trying your rom like now.
Thanks a lot
Hey im happy to see a nice Rom for my womens padfone 2! The only Problem is the i have a Invalidit kernel.. And no boot for me) = i can only boot with Superboot trick. I need help to repair this phone.. please help me.
locce said:
Hey im happy to see a nice Rom for my womens padfone 2! The only Problem is the i have a Invalidit kernel.. And no boot for me) = i can only boot with Superboot trick. I need help to repair this phone.. please help me.
Click to expand...
Click to collapse
I think we need to know a little bit more about your problem to see if there is help:
- How did you get an invalid kernel?
- Is the device unlocked/do you have custom recovery on it?
Im New in the asus sector...okay I have root with towelroot and forget to unlock the bootloader!!! The not normal booting and Invalid kernel Problem is coming from twrp flash.
locce said:
Im New in the asus sector...okay I have root with towelroot and forget to unlock the bootloader!!! The not normal booting and Invalid kernel Problem is coming from twrp flash.
Click to expand...
Click to collapse
Unlocking the bootloader is always the first step. You can fix things, though. First, remove towelroot, and any other rooting mechanisms you may have - you do not need them, custom roms are pre-rooted.
If you are running a 4.1 or 4.2 ROM follow the points from this post
If you have KitKat, it is a bit more complicated, see this post
WARNING: If your device has been serviced (specifically the motherboard replaced), you will not be able to unlock it!