1. I'm new here. Xperia Mini is first Android. I really have no idea on what should I do.
2. I've just read trough all replies in
Revolutionary - zergRush local root 2.2/2.3 [22-10: Samsung/SE update]
And I'm wondering, does this way of rooting affect the DRM and TrackID, and all that stuff, as SE site says? I really don't want to lose any functions permanently on my phone, but I want root access, so I can mod small things, and especially install apps like WifiKill.
So, does this root break stuff , as said on SE unlock site?
AFAIK, unlocking the bootloader can erase the DRM keys. Rooting is a different thing. Originally, you could only root after unlocking the bootloader. Apparently this new method can bypass that? But I'm not 100% sure.
barrist said:
AFAIK, unlocking the bootloader can erase the DRM keys. Rooting is a different thing. Originally, you could only root after unlocking the bootloader. Apparently this new method can bypass that? But I'm not 100% sure.
Click to expand...
Click to collapse
Okay, I'm downloading ADB at the moment. Since either it works or can't do any harm, I'm glad to try it.
TrackID works, i don`t use FB so i can not confirm that it works too.
My BL is (re)locked with S1 Tool and the phone was fresh flashed with .335 by wotanclient.
And, yes, by the way, my firmware is 4.0.2.A.0.42 (Android 2.3.4)
And I'm unclear with this:
The binary is available from here: zergRush binary.
The exploit source is available here: Revolutionary GitHub.
Usage:
You will need adb shell to execute this exploit. We need shell permissions.
Push the binary onto /data/local/ and execute these commands in a shell:
Click to expand...
Click to collapse
1. is binary any different from exploit source? I guess we don't need exploit source at all?
is ADB shell same as ADB? How can I get shell permissions?
why do you not use this script:
http://forum.xda-developers.com/showthread.php?t=1320350
? everythis is automatic.
Telemuddi said:
why do you not use this script:
http://forum.xda-developers.com/showthread.php?t=1320350
? everythis is automatic.
Click to expand...
Click to collapse
Wow, this seems alot easier!
I guess I still need ADB (it needs adb drivers) ?
Wow,running that batch file, I have SU, does this mean it's rooted?
Related
I've searched all day for info on wether it is possible to install recovery without unlocking the bootloader? Right now all points to not possible, but please give me a deffinate answer.
Thx in advance.
stalkerzone said:
I've searched all day for info on wether it is possible to install recovery without unlocking the bootloader? Right now all points to not possible, but please give me a deffinate answer.
Thx in advance.
Click to expand...
Click to collapse
Nope
10chars
I was looking only half of a day and then got to this post - thanks.... Damn you ASUS for you wicked tricks
I like CWM on my Desire phone... kinda want me riverdancing... void my warranty
Someone correct me if I am wrong but changing out a recovery.img requires bootloader access. Unless a dev can crack the bootloader or the manufacturer allows it, def hard, help that helps.
stalkerzone said:
I've searched all day for info on wether it is possible to install recovery without unlocking the bootloader? Right now all points to not possible, but please give me a deffinate answer.
Thx in advance.
Click to expand...
Click to collapse
.21 downgrade & unlock bootloader
The 9.2.4.21 firmwware presently cannot be rooted. The way to get root is to use version 9.2.4.15 or earlier, (I used .11) using a linking trick and then use ViperMOD to complete with root and unlock.
Tutorial by Wolf849 - over here - will get you to .11 firmware and working super user / root access.
Then use ViperMOD PrimeTime by - viperboy - which includes an option to install Clockwork Mod recovery and install the Asus Unlock Tool.
Once the bootloader is unlocked, you can install a custom recovery, such as CWM, CWM Touch, Open Recovery or other as you wish.
Unlocking does have the penalty of voiding any warranty and you might possibly get into a boot loop, which can be resolved with;
Code:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13
Roach2010 has a thread here explaining the boot loop issue in better detail and Diamondback has some very helpful unbricking tips.
I've decided to post a little blurb about the difference between rooting and unlocking your bootloader because I've seen too many posts using the terms incorrectly. I will update this based of off information posted here and as more information comes to mind.
Unlocking your bootloader:
First, let me describe what the bootloader is.The bootloader is a piece of software that is (essentially) the first thing that runs when you start up a device (bootloaders are on almost every device with an operating system.) The bootloader is what loads the operating system into memory. Now, unlocking the bootloader modifies the bootloader through a hack or a flag that is toggled in the bootloader (this is how the HTC Dev unlock works) that allows the recovery partition to be flashed (or a non-oem recovery to be flashed.) JCase's exploit (http://forum.xda-developers.com/showthread.php?t=2011611) is not a bootloader unlock; it is a method to allow the bootloader to be unlocked by modifying part of your device to emulate another device. This method allows you to use the HTC Dev website to semi-unlock the bootloader.
Rooting your device:
Rooting your device is gaining what is called root access to your device. On some devices, like the DNA, you must unlock your bootloader before you can gain root access. This is because after you unlock your bootloader you can put a file call 'su' in the /system/bin folder. Root privileges in Linux are equatable to administrator privileges in Windows. This is done by flashing the 'su' file to your device. The 'su' file is called by any program that would like to do things that need root privileges to do. The Superuser or SuperSU app on your phone is a manager for the su binary allowing you to allow and deny access to su. The su manager applications are equatable to firewalls for network access.
If anyone has any suggestions or comments for changes/mis-information let me know, please.
Edit:
Made some changes based off of Jarocks' information.
I'm not positive on this, but don't you need to unlock the bootloader to achieve permanent root on the Droid DNA? (Or even temporary root for that matter?)
Jarocks said:
I'm not positive on this, but don't you need to unlock the bootloader to achieve permanent root on the Droid DNA? (Or even temporary root for that matter?)
Click to expand...
Click to collapse
Yessir, you do.
Edit: I misunderstood your reply, and have modified my answer thusly.
I have xperia pro and rooted it with eroot. Bootloader is not unlocked. When I flash APKs using ADB or Fastboot it gives error that device is not rooted but superuser is already there on the phone. I don't know if I can flash APKs to locked bootloader. I tried everything CWM but doesn't go into recovery mode.
rcreation33 said:
I have xperia pro and rooted it with eroot. Bootloader is not unlocked. When I flash APKs using ADB or Fastboot it gives error that device is not rooted but superuser is already there on the phone. I don't know if I can flash APKs to locked bootloader. I tried everything CWM but doesn't go into recovery mode.
Click to expand...
Click to collapse
What do you mean by "flash apk" ? If it is install then adb install apkname.apk should work...
HIT Thanks if you like my post
-------------------------------------------
My work:
[TOOL]Kernel/Boot.img (un)packer
Actually I am trying to install Cybershot APK which will replace my original Camera app but still after rooting it is not allowing to do that.
Is this because I don't have unlocked bootloader???
But in the threads it said that you just need rooted phone.
So please let me know if I can replace standard APKs with custom ones in locked bootloader.
rcreation33 said:
Actually I am trying to install Cybershot APK which will replace my original Camera app but still after rooting it is not allowing to do that.
Is this because I don't have unlocked bootloader???
But in the threads it said that you just need rooted phone.
So please let me know if I can replace standard APKs with custom ones in locked bootloader.
Click to expand...
Click to collapse
Yes, you only need an unlocked bootloader. Mount system as RW. And then replace the cam app in /system/priv-app, but I would suggest you to unlock bootloader, install cwm and make a nandroid
-------------------------------------------------------------------
HIT Thanks if you like my post
-------------------------------------------
My work:
[TOOL]Kernel/Boot.img (un)packer
[ZIP]Flashable zip to bypass lockscreen for LG E975
But can I backup locked bootloader. If in case phone gets issues like bootloop and all can I lock my phones bootloader again.
If I unlocked bootloader then can I able to use repair operation from Sony PC Companion.
Like yesterday I tried to delete all system files from root and my phone was not able to start. So what I have done is repaired it using PC Companion and it has been started.
I mean to say can I backup my existing ROM, bootloader and all and if so can you please let me the process to do so.
Because there are so many threads and there are so many applications to do it and I am not able to figure out the correct procedure.
I also have the RW permissions and can replace the app but its meta files and all will not be replaced then. So do you know method to flash this APK.
rcreation33 said:
But can I backup locked bootloader. If in case phone gets issues like bootloop and all can I lock my phones bootloader again.
If I unlocked bootloader then can I able to use repair operation from Sony PC Companion.
Like yesterday I tried to delete all system files from root and my phone was not able to start. So what I have done is repaired it using PC Companion and it has been started.
I mean to say can I backup my existing ROM, bootloader and all and if so can you please let me the process to do so.
Because there are so many threads and there are so many applications to do it and I am not able to figure out the correct procedure.
Click to expand...
Click to collapse
Bootloop is a different term. It is because of bad ROM, once you unlock bootloader, nothing can relock it except you do it. So nothing to be scared of.
-------------------------------------------------------------------
HIT Thanks if you like my post
-------------------------------------------
My work:
[TOOL]Kernel/Boot.img (un)packer
[ZIP]Flashable zip to bypass lockscreen for LG E975
I tried everything Rom Manager, X-Parts, Recover-X, BusyBox but not able to boot into recovery.
Can anyone help me with this???
I got this working using below thread
http://forum.xda-developers.com/showthread.php?t=1364509
Thanks though...
it is possible to root with king root
or i need flashtool etc..?
also.. root always voids warranty ?
even with bootloader locked with stock kernel and ROM?
Superrman said:
it is possible to root with king root
or i need flashtool etc..?
also.. root always voids warranty ?
even with bootloader locked with stock kernel and ROM?
Click to expand...
Click to collapse
I suggest you read a bit more on rooting your device. I don't think you're ready yet.
civicsr2cool said:
I suggest you read a bit more on rooting your device. I don't think you're ready yet.
Click to expand...
Click to collapse
lol..
i rooted my previous phone with ADB via terminal
unlocked with imei with sony code 1st
and 2nd Push adb boot.img recovery
and install everything from there including root
(i've had cyanogenmod cm7-13 etc)
but i dont want lose warranty
my old phone was without warranty when i unlocked and rooted him
Superrman said:
lol..
i rooted my previous phone with ADB via terminal
unlocked with imei with sony code 1st
and 2nd Push adb boot.img recovery
and install everything from there including root
(i've had cyanogenmod cm7-13 etc)
but i dont want lose warranty
my old phone was without warranty when i unlocked and rooted him
Click to expand...
Click to collapse
then read, like everyone
So you guys know the new bootloader exploit that came out right, can't we use this to gain temp root and use dd to fix laf?
I'm talking about cve-2020-12753 btw, this was already done for the V20.
crimsonrommer said:
So you guys know the new bootloader exploit that came out right, can't we use this to gain temp root and use dd to fix laf?
I'm talking about cve-2020-12753 btw, this was already done for the V20.
Click to expand...
Click to collapse
Who has Download mode issues? Some people lose Download mode flashing to Pie in US998, but the fix is to flash TWRP flashable US998 20e zip.
I'm curious who you are talking about. There's no other Download issues being discussed. Except some random T-Mobile H932, but Bootloader exploit has nothing to do with that. They can already unlock their Bootloader from the Settings GUI.
I meant, being able to restore download mode since it's corrupt, and I only have stock and stock recovery with no root but a broken custom rom, so I was wondering if using that cve we can gain root to dd non broken laf, I have a h932 so fastboot is obviously not an option
crimsonrommer said:
I meant, being able to restore download mode since it's corrupt, and I only have stock and stock recovery with no root but a broken custom rom, so I was wondering if using that cve we can gain root to dd non broken laf, I have a h932 so fastboot is obviously not an option
Click to expand...
Click to collapse
Right. The T-mobile H932 guys have issues with losing Download mode here and there. The only problem is bootloader exploit assumes if you unlock bootloader or bypass bootloader, THEN you can use fastboot commands to gain root. Doesn't it? Because you have to flash something -- either Magisk or a kernel. Or is there something I'm missing?
I must admit I misspoke when I said bootloader exploit, it's a temp root exploit that can be used in a terminal emulator to gain root access until reboot
Here's what I mean:
https://forum.xda-developers.com/v2...perf-root-shell-lg-v20-variants-t3990145/amp/
And that is when I realized I'm mixing myself up a bit, but yeah that's what the exploit does,
Here: https://www.zdnet.com/article/new-cold-boot-attack-affects-seven-years-of-lg-android-smartphones/
It gives dl mode as an example but I'm pretty sure you can use anything like dl mode to do this, or am I wrong?