[Q] S-off (full root) on the X10 Mini Pro - Sony Ericsson XPERIA X10 Mini

I just updated my unlocked Mini Pro to Vodafone Spain's Android 2.1
Next step, rooting.
It's rooted, in that Superuser permissions can be granted (I get the # in the terminal), I've used Titanium backup to remove all the game trials/Voda stuff.
However, I want to use Font Changer to change the display density and hopefully get bigger characters on the screen.
When I start this app, I get the message that "Write access to the system partition was not established.... make sure your device has full root and try again".
I have tried mounting the system folder as rw (the fonts folder is in here), but that doesn't do the job.
I have tried a variety of rooting techniques, but it seems I need "S-off" on the system partition.
Any ideas to take rooting this one step further?

Dude
Tio, simplemente bajate el z4root del market y dale al gran boton que pone "Permanent root". Funciona 100%.
Dude, just download z4root from the market and hit the big button with the "Permanent root" tag on it. It works 100%.

gracias loger8, ¡funciona!
Thanks loger8, it worked like a dream.
I had tried a variety of rooting options, but this is the only one that goes all the way!

Related

[Q] First try at rooting - things to do after and in what order?

Hi.
I getting ready to root my X10 mini for the first time and I've been reading up on things. My plan for now is the following:
1) Factory reset and full official update
2) Root using this: LINK
But then what? At first I don't want to use custom roms, but I would love to get rid of all the crapware and a speed increase would also be highly appreciated
I’ve looked at some of the summaries, read about things like xRecovery, Apps2SD, themes and JIT but I’m not sure whether there’s a correct order in which to apply these, if some will conflict, if they're all "needed", how to partition my SD card (I know about partitioning – just unsure about when to do it and what partitions are needed) or……
Help is greatly appreciated - also suggestions on what else my phone would benifit from after rooting.
Thanks
/Henriette
Hi!
I used SuperOneClick, I think this is the best way for rooting. Don't need USB debug, just push the root button on your PC and the app makes everything.
I suggest you, don't use App2SD, JIT, and "other things" just for fun, if you can brick your phone and lose guarantie.
Rooting is useful, you can do a full backup from your device via xrecovery, and you can remove stock apps (be careful, if you will remove some system app, you can brick your device).
One more useful stuff: Download Samba Server from Market (requies root), it shares your SD card over a WIFI network, so you can forget the data cable...
I think this is enough for beginning, and when you will get more knowledge, you can do more things with your rooted phone.
TEmes
Well, isn't that why we do it - "just for fun"?
Thank you for your answer. I'll try apps2sd og links2sd since I keep running out of space on my mobile. Not enough room for apps.
Thank you for the tip about the samba server. Will try that one. Any more "must" apps after root?
Thanks again
/Henriette
HenrietteK said:
Well, isn't that why we do it - "just for fun"?
Thank you for your answer. I'll try apps2sd og links2sd since I keep running out of space on my mobile. Not enough room for apps.
Thank you for the tip about the samba server. Will try that one. Any more "must" apps after root?
Thanks again
/Henriette
Click to expand...
Click to collapse
CM6 (Floyo) and CM7 (Gigglebread) have app2sd support. I have no more must have app that requires root, but Titanium Backup is useful (for me it's enough the stock SE backup&restore).
Temes
Henriette, I would also recommend a root with SuperOneClick (Rooted my X10 Mini Pro with it) z4root did not work for me but maybe it will do it for you.
Other benefits are: use your phone as a Wi-Fi hotspots, and run newer versions of android (custom roms), xCyanogenPro / xCyanogenMini 7 comes with JIT, xRecovery is X10 mini pros method that back up (if you're not using Titanium Backup). To get xRecovery (which would be the first thing you would do if you need xCyanogenPro / Mini 7) are:
1. Finding a xRecovery zip file and unzip it on your sd card.
2. use something like Root Explorer to get xRecovery installed (Press Mount R / W when using Root Explorer)
3. Go into / sdcard and find where you extracted the files
4. Press "Menu " button and press the Multi-Select.
5. Select chargemon, busybox and xrecovery.tar files and press copy
6. Go into / System and tap on Mount R / W (if you have Root Explorer) to insert the files in / System Folder
7. Navigate to / system / bin
8. Put the files as you ealier had copied into this folder and Ding! xRecovery is installed (App2SD I do not know how to do yet)
(And if you liked it, press the "Thanks " button)
Hope It Helped you out
Thank you very much for your answer. Any help is welcome Love to hear more suggestions. Thanks
Sent from my E10i using XDA App

Huawei Mediapad / T-Mobile Springboard Discussion

It looks like we have to move our discussion here, so I went ahead and started a thread.
As of now, there is root for the mediapad, but the only way to root the springboard is by flashing it with a rooted mediapad cust.img - which gives you root but loses your 4g.
So for us Springboard users, we either need root or a way to get 4g back if flashing it as a mediapad. Anybody with thoughts or leads or any know-how?
Finally,
Special room for Huawei Media Pad created,
Thanks to TS
I'm very glad,
Now i'm waiting the master in here to modified this device
cause i still newbie
Actually I Prefer The 3G More THan The 4G For Some Reason I Felt 4G Wasnt Stable Enough....So Im Enjoiying My Mediapad In 3G More Than My Springboard In 4G......
from the other thread, Rumbi wrote:
Yap, only thing you have to do is install Superuser and Busybox from Market and copy "su" from /hwcust/oversea_hk/preload/fixed/bin/ to /system/xbin (e.g. with ES File Explorer with root and r/w enabled), and you are ready to go
I've installed SU & BusyBox. I cannot move the SU file over to /system/xbin. A message tells me that I am not root.
However, when I run Root Check Basic I am told I have root.
I ran Root Check before & after I installed S7-301u V100R001C232B012(Root_version) and Root Check said I did not have root.
So the real question is, How do I really know if I have root?
*****
Actually I installed BusyBox Installer. I'm asked to pick a version to install:
1.19.3
1.19.2
1.18.5
1.18.4
1.17.1
None of these will install.
I also have the option to install a "Custom Tune" is there one? I'd gladly pay for BusyBox pro to get BusyBox running
*******
I powered off the device. Put my sdCard back in (the rooted firmware was removed from it). Then installed the SuperUser update from the market.
Ran that - it said everything was OK. Then I forced it to update - it crashed - so I force closed it. I then realized I could not run the original SuperUser app anymore.
Next, I opened up Root Explorer and was able to move the su file over to the xbin. But now BusyBox is not acting right - It said that it was having problems installing, and I'd need to reflash (or reload - I can't recall) the rom.
I'm rebooting, and going to try to install BusyBox....to be clear on which BusyBox..it's this one:
https://market.android.com/details?...t=W251bGwsMSwyLDEsInN0ZXJpY3Nvbi5idXN5Ym94Il0.
*****
Just realized in Root Explorer, to tap the little gray box at the top. After you tap it it should read "Mount R/O"
Now you can long press a folder/file and change the read/write permission.
Rumbi,
You said to r/w enabled the su file....is that check ALL the boxes?...Read, Write, Execute Special?????
IIRC, i had some problems with busybox, too. Copy the file from the attachment to /system/xbin and try the installer again.
And i said to enable r/w support for the /system folder. There are two checkboxes in ES File Explorer. First checkbox is enable root permission for ES File Explorer and second checkbox is "Mount / and /system writable".
Now you should be able to copy whatever file you want to /system/xbin. That's how i have done it. If you have any further questions, feel free to ask. I'll try to explain.
PS. You don't ne to alter file permissions of the su-binary but mine are "rwx r-x r-x".
Rumbi, how do you feel about the High resloution mode, does it slow the tablet down? Have you had a chance to use any tegra 2 devices and if so how does the mediapad with the snapdragon compare when in standerd/high-res mode?
Nothing to complain about the Hi-Res-Mode but i don't have any Tegra2-Devices to compare, sorry.
Haven't tried any games in hi-res-mode but normal usage is just fine.
Thanks. Ill try this out. When i try to install busybox it hangs first, then i force close and run again. Then i get the message about reflashing Rom. But i know i have root. I installed connectbot and ran su and got #
Heres how i got root (im away from my pc right now so i try to be as accurate as possible) :
Installed Hauwei modified rom (its the one that says "(root) " in the file name.
Installed Root explorer
Installed Superuser
Install busybox
Install Connectbot
Put my microsd back in (with the firmware AKA dloa folder removed)
I could not get root explorer to allow rw permissions until i slid the sd card out and back in whil the device was on.
Then i ran connectbot as local and typed su hit enter then superuser popped up asking fo allow connectbot to access. Hit allow an type su hit enter an you should get # This took 3 reinstalls of the firmware to work wjthout errors. The first times resulted in superuser needing to be force closed.
I also ran superuser and went into settings and updated it eventhouh its not neede. There i got a read out saying that busybox is not installed, but it does say i have root.
Sent from my HUAWEI MediaPad using xda premium
Honestly i havent noticed a big difference between high resolution an standard.
The only issue with high res is the small icons and buttons are difficult to hit sometimes
Sent from my HUAWEI MediaPad using xda premium
Do i need to unzip this file first?....
.... Nevermind... I unzipped it and put the busybox file in th system/xbin folder.
I installed busybox installer by JRummy16. This time and it worked!!!!!!!
Now its on to figuring out 4G and tryiying to use it as a phone.
What is the xml file i need to edit?
Sent from my HUAWEI MediaPad using xda premium
Good, that you have worked it out now What exactly do you want to do? To get to the hidden menu, you have to open the calculator and type: ()()2846579()()=
To edit the XML-Files, you have to extract the cust.img... But now that you have root, yo can edit whatever is available via root explorer
€dit: To get 4G working again, maybe with someone with an original Springboard (not a flashed one) can copy the folder /system/lib/. This should be possible even without root. I think it has something to do with the ril-files...
after updating my mediapad to S301uV100R001C232B012, i have problem with 2x Client (RDP client) now, few second after conecting to rdp session, is app 2X client crashing, with error 2x Client has stopped unexpectedly (process com.tux.client), is here anybody with this problem? thanks...
Rumbi said:
€dit: To get 4G working again, maybe with someone with an original Springboard (not a flashed one) can copy the folder /system/lib/. This should be possible even without root. I think it has something to do with the ril-files...
Click to expand...
Click to collapse
How about this - link
I'll look at it, thank you And these are the libs from an unmodified Springboard, aren't they?
yes indeed. I broke the silly thing, so I haven't played with it much. guess I will have to call about how to get it fixed.
knoxjon said:
How about this - link
Click to expand...
Click to collapse
Even though I have no clue of what to do with this, THANKS! I tried to open an .so file in notepad, but no luck, but I'm assuming that the geniuses here know what to do.
On an off-root topic - How do you take a screen cap? I accidentally did it yesterday while my MediaPad was lagging, but don't know how I did it.
The Hi Suite that comes with the device can do this, but require a computer and usb hooked up. Useful, but not as practical as doing it from the tablet itself.
The *.so files are a bit like drivers for the internal components. I'll try to find differences between T-Mobile and Huawei so maybe we get 4G working again.
tedbone said:
Even though I have no clue of what to do with this, THANKS! I tried to open an .so file in notepad, but no luck, but I'm assuming that the geniuses here know what to do.
On an off-root topic - How do you take a screen cap? I accidentally did it yesterday while my MediaPad was lagging, but don't know how I did it.
The Hi Suite that comes with the device can do this, but require a computer and usb hooked up. Useful, but not as practical as doing it from the tablet itself.
Click to expand...
Click to collapse
I'm not sure how to screencap. It's so easy on CM that I've gotten lazy. Plus I rarely do it. I know there are a ton of apps for that, tho. But you could probably google "gingerbread screen capture" and find a better answer. But not with gingerbread. I'm blanking on the name for this version of android.
knoxjon said:
I'm not sure how to screencap. It's so easy on CM that I've gotten lazy. Plus I rarely do it. I know there are a ton of apps for that, tho. But you could probably google "gingerbread screen capture" and find a better answer. But not with gingerbread. I'm blanking on the name for this version of android.
Click to expand...
Click to collapse
Honeycomb
I've been Googling searches like that, and end up with actual screen shots of Honeycomb os..I'll keep looking...
Tried this (from here), but no luck:
Screen capture
Android natively supports the ability to capture a screenshot by method of pressing both the power and volume-down buttons at the same time on an Android device. This native support was first included within the Android 4.0 (Ice Cream Sandwich) update, which is first seen on the Galaxy Nexus smartphone.[86] Previously, Android did not feature native support for screen capturing which would have likely been due to security concerns. Furthermore, prior manufacturer and third-party customizations as well as using a PC connection (DDMS developer's tool) were the only known methods of capturing a screenshot on Android.
I've looked through the *.so files and many of them are exactly the same, but some are different. One file caught my interest. I've attached it here for anyone who wants to try. Please only use it, if you have a T-Mobile Springboard with flashed root Firmware. Copy the content of the zip-file to /system/lib and overwrite the existing file. But make a backup first! After copying you have to set the correct file permission (rw- r-- r--) and reboot the tab. Hopefully 4G works again with this little trick.

[Q] [XT920] Recover ROM from .img

Hey guys,
Recently I've tried to port CWM to my device following this tutorial and it bricked...
It did not boot in any mode (Recovery, Fastboot or Normal) after doing this (stuck on motorola logo/boot menu).
@diego-ch helped me and he managed to flash the XT920_2_290_2014 back on my device and unbrick it, but I want to install XT920_2_310_2014 back.
There are some Stock ROMs available on the internet, but these ROMs are outdated compared to my original ROM...
The ROMs available are: XT920_2_290_2014_A01_MP (Tim Brazil) and XT920_2_290_2009_A01_MP (Retail), and my original ROM was XT920_2_310_2014_A01_MP.
The backup script in this tutorial created a few files files: recovery.img, system.img, boot.img...
What I want to know is...
Is there any way to "reflash" these backups to my device?
Here is a printscreen from my original ROM:
https://dl.dropboxusercontent.com/u/82392755/OriginalROM.jpg
And a printscreen from the "new" ROM:
https://dl.dropboxusercontent.com/u/82392755/NewROM.png
Thank you!
In this link you can get the up-to-date firmware for the D3,
and for now you can't flash those img in the device.
Regardless it's a MTK6577 chipset (the same of some generic chinese devices), Motorola used some security measures that we couldn't avoid yet. In this thread you can follow the discussion about it.
My theory is that the ROM make some validation on each partition in every boot. If one doesn't pass, then the phone stuck in a bootloop, as happened to you. Also, we can't flash any partition as we do in similar devices because the phone requires an authorization file, a signature. The only way to generate it is with a private key, that we don't have.
Maybe you can recover some data from the data.img if you root your phone and use some specific software to extract the files and put it in the data partition, but you'll need to research about how to do it. Also... maybe there some apk in the Play Store that provides this options to you, idk... but I think the most important is to recover you system, the data you can just reinstall your apps.
About the root, you can find good tutorials researching in Google
@farenheith, thank you for your answer!
My device is already rooted, thanks for advice!
Can I help you with something right now?
I'm studying how Android works (ROMs, APPs, Drivers, etc), and I've downloaded the source code found on SourceForge (Razr D Files) and I'm studing it (applying to my Razr D3).
If I have something new, I'll post it here!
I have some driver conflict problem with the motorola drivers in my machine... I take hours to successfully flash the firmware again... it's very annoying...
And well, I want to do more tests right now, but I can't. If you want to help, you can do some tests too:
What I did:
* I got an image from the recovery and then I flashed it again without any changes. The phone boots successfully. This tests was to make sure that the writing operation was not screwing something
* I tried to edit myself the ramdisk of the image I got before and then I flashed it. I got a bootloop again...
What I need now:
FIRST TEST
* Get an Image from recovery with these adb commands
Code:
adb shell su -c "dd if=/dev/recovery of=/storage/sdcard1/recovery.img bs=6291456c count=1"
adb pull /storage/sdcard1/recovery.img
* Unpack and repack the image without any change and try to flash again (to do the repack you can use this app). Commands:
Code:
adb push new_image.img /storage/sdcard1/recovery2.img
adb shell su -c "dd if=/storage/sdcard1/recovery2.img of=/dev/recovery bs=6291456c count=1"
reboot
* Look if the phone will boot normally. If not, re install the firmware with RSD
The idea of this test is to check if the phone needs a padded recovery, ie, with exact 6291456 bytes, to boot properly.
SECOND TEST
Do exact as the test above, but, before repack the recovery, add the following parameters in the default.prop in the ramdisk:
Code:
ro.testtest=1
This test is to check if the phone will do a validation, like a checksum, in the partition to make sure it can boot. If the phone doesn't boot with this change, then we know that any recovery we put there will not work. If it boot, then the problem is something inside the recovery.
Update: I did the tests I talked about... I'm quite sure that we do have a checksum validation of some internal partitions (like bootimg and recovery) during the boot.
I'll start to analyse the source code to see if I find some clue. Maybe we can edit some partition manually or even recompile some and write it using adb, we just need to find where this supposed validation is happening and study the best workaround for it.
Can you help me with it? Do you have some programming knowledge?
farenheith said:
Update: I did the tests I talked about... I'm quite sure that we do have a checksum validation of some internal partitions (like bootimg and recovery) during the boot.
I'll start to analyse the source code to see if I find some clue. Maybe we can edit some partition manually or even recompile some and write it using adb, we just need to find where this supposed validation is happening and study the best workaround for it.
Can you help me with it? Do you have some programming knowledge?
Click to expand...
Click to collapse
I can help you @farenheith!
I know a bit of programming (I'm already conversant with some source codes)... I've downloaded the code and I'm studying it.
If I have some news, I'll post it here!
naroku said:
I can help you @farenheith!
I know a bit of programming (I'm already conversant with some source codes)... I've downloaded the code and I'm studying it.
If I have some news, I'll post it here!
Click to expand...
Click to collapse
Hello guys, I am from brazil also. Yesterday I was trying to convert my 32gb SD to exFat or NTFS and to do so I had to install Multi mount SD card and I believe it was this **** that brick it. One of the signal meters of the sim cards is gone, the other is normal, also I don't have the slide to disable one of the sims, they are gone... I've tested and both sims are still working, to make calls and receive. Also my Google Play Store is gone, every time I open it it forces closed with "unfortunately google play store has stopped". ja tentei de tudo, qnd faço clear dos dados do app ele ate abre, mas é so mandar iniciar o download de alguma coisa que ja ferra (I've tried everything including deleting app data, when I do that it does open, but after the first download start it forces closes with that error). And the worse of all is that i've been reading that if you hard reset or flash a rom you get the 2nd chip disabled forever. is that true?
one more info... my xt920 is being recognized as xt919! I believe this is what is causing all the problems... the strange thing is that there was no factory reset, hard reset, or firmware flash... just this **** app which might have caused this. How can an APP make your phone be recognized as another model? how could I fix it?
fscussel said:
Hello guys, I am from brazil also. Yesterday I was trying to convert my 32gb SD to exFat or NTFS and to do so I had to install Multi mount SD card and I believe it was this **** that brick it. One of the signal meters of the sim cards is gone, the other is normal, also I don't have the slide to disable one of the sims, they are gone... I've tested and both sims are still working, to make calls and receive. Also my Google Play Store is gone, every time I open it it forces closed with "unfortunately google play store has stopped". ja tentei de tudo, qnd faço clear dos dados do app ele ate abre, mas é so mandar iniciar o download de alguma coisa que ja ferra (I've tried everything including deleting app data, when I do that it does open, but after the first download start it forces closes with that error). And the worse of all is that i've been reading that if you hard reset or flash a rom you get the 2nd chip disabled forever. is that true?
one more info... my xt920 is being recognized as xt919! I believe this is what is causing all the problems... the strange thing is that there was no factory reset, hard reset, or firmware flash... just this **** app which might have caused this. How can an APP make your phone be recognized as another model? how could I fix it?
Click to expand...
Click to collapse
Hey man, don't panic!
When you run "getprop" command, what model you get on [ro.product.model]?
Run this tutorial and you get your XT920 back.
Don't use your SD in exFAT or NTFS, it may cause some trouble, use um FAT32 yet.
Cya!
ROM XT920 32D working!!! Follow this instructions:
Instalando a ROM v 2_32D_2009 no RAZR D3 (XT920).pdf (322 KB)
https://mega.co.nz/#!olhn2QQa!fU1KmU9Mp2rRp671bSpI0iB_Vo0_YsFMgZZf8CfnlnA
Is anyone needs it english translated please contact me. I believe it solves sim locked problems!
Unfortunately It don't solve the sim locked problem...
Just a good new... I did a question for Motorola in the razr d sourceforge about the HID support, and they answered me that is possible to implement it. HID is the common protocol for keyboards, gamepads, mouse, etc...
http://sourceforge.net/motorola/razrd/discussion/general/thread/0eaeef02/
Anyone discovered a solution for the locked SIM Slot problem?
I'm in panic here for not being able to use 2 sims on my phone...
And motorola doesn't give any answers about it..
Take it easy, you're not alone.
Motorola released a official update for D3, idk if it'll solve this problem. Last week a guy robbed me, so I don't have a D3 anymore. Look for this update and how to put it in your phone.
Good luck
farenheith said:
Unfortunately It don't solve the sim locked problem...
Click to expand...
Click to collapse
Late reply but... The SIM locked problem, is due to User Data files, when you restore a good one, the problems are gone....
farenheith said:
Unfortunately It don't solve the sim locked problem...
Just a good new... I did a question for Motorola in the razr d sourceforge about the HID support, and they answered me that is possible to implement it. HID is the common protocol for keyboards, gamepads, mouse, etc...
http://sourceforge.net/motorola/razrd/discussion/general/thread/0eaeef02/
Click to expand...
Click to collapse
Hello,
There's any news about the sim lock problem?
silverfoxbrazil said:
Hello,
There's any news about the sim lock problem?
Click to expand...
Click to collapse
Unfortunately a thief robbed my D3, so I'm not looking into this theme anymore, sorry :/
seems i'll have my phone fixed.
in contact with motorola they authorized send the phone to service, even without warranty.
they send me a code from "correios", to ship it without any charge
they called it "special warranty", i will send it today by "correios", let's see what's gonna happen

Phone root

I need help please, this day I root the phone SOLONE STYLUS, I did kingroo and check that estava well with the application root checker restart the phone and in doing so I appeared error, which was not rooted, so I went back to try but only appeared me a notice that it could not, in ccleaner appeared to me that if I was with root and check root no, not to do, I was checking the bin folders and xbin to delete root but I can not permits, if anyone knows or knows of this that can help tell me, thanks

[CLOSED]old android, edit update.zip to get root

Hello,
i need help, i have an old android system (2.3.4) that i would like root. (3months that I try)
the kingroot application (3.5) allows me to get root rights (which allows me to have adb shell su # OK, if I install it) but this app installs too much unpleasant things... i would like to do otherwise with your help.
I have an update file "update.zip" that can load automatically at startup.
is it possible to modify the update.zip to get root rights (supersu)?
and if so, can you help me?
for information, this is the android system of "recon live mod" (no touch, but I can use "asm java apps" to simulate the touch on laptop)
thank you!
Perhaps Yes?!
dededede said:
Hello,
i need help, i have an old android system (2.3.4) that i would like root. (3months that I try)
the kingroot application (3.5) allows me to get root rights (which allows me to have adb shell su # OK, if I install it) but this app installs too much unpleasant things... i would like to do otherwise with your help.
I have an update file "update.zip" that can load automatically at startup. >>>>file here<<<<
is it possible to modify the update.zip to get root rights (supersu)?
and if so, can you help me?
for information, this is the android system of "recon live mod" (no touch, but I can use "asm java apps" to simulate the touch on laptop)
thank you!
Click to expand...
Click to collapse
Kingroot is a Chinese App that pushed it's Function from Managing root To Advertising and Stuff.So,There is an app Called Kingroot to supersu that allows you to Gain root access.Alternatively you can Flash a Custom recovery and flash Supersu Throug it(After unrooting from kingroot ofcourse)Or try other oneclick root soloutions.But Out of Curiousity what are you doing with that Old Android.I thought they were Dead.What are You hiding bro?You gonna Hack CIA with that Lethal Programming.
Sent from my SM-N9005 using Tapatalk
lol
is the "recon mod live HUD" of "reconinstrument" bought and abandoned by "intel" .. ( thx intel )
the "fastboot" is unreachable, and I have only 150MB of disponnible (not enough for a custom recovery?)
kingroot is the only one to work but I do not want to use it ...
so I'm looking for another way to get root and supersu
dededede said:
lol
is the "recon mod live HUD" of "reconinstrument" bought and abandoned by "intel" .. ( thx intel )
the "fastboot" is unreachable, and I have only 150MB of disponnible (not enough for a custom recovery?)
kingroot is the only one to work but I do not want to use it ...
so I'm looking for another way to get root and supersu
Click to expand...
Click to collapse
So Use "Kingroot to SuperSu"Script zip or apk from xda.
Sent from my SM-N9005 using Tapatalk
I already tried but I had a lot of errors.
it was also impossible for me to update the binary (no internet connection on the device)
Last Resort.
dededede said:
j'ai déjà essayer mais j'avais beaucoup de remontées d'erreur.
il m'était également impossible de mettre a jour le binary (pas de connexion internet sur l'appareil)
Click to expand...
Click to collapse
Buddy Your Device is too old.Either Flash a Recovery.Generally it replaces your already present recovery and Doesn't Cause much pain.
Sent from my SM-N9005 using Tapatalk
there is no recovery at all .... yes it is really old
(go see on the web "recon mod live")
dededede said:
Hello,
i need help, i have an old android system (2.3.4) that i would like root. (3months that I try)
the kingroot application (3.5) allows me to get root rights (which allows me to have adb shell su # OK, if I install it) but this app installs too much unpleasant things... i would like to do otherwise with your help.
I have an update file "update.zip" that can load automatically at startup.>>>>file here<<<<
is it possible to modify the update.zip to get root rights (supersu)?
and if so, can you help me?
for information, this is the android system of "recon live mod" (no touch, but I can use "asm java apps" to simulate the touch on laptop)
thank you!
Click to expand...
Click to collapse
Hi. The easiest way to root your Android is through TWRP... I don't know if your device is supported but take a look. https://www.xda-developers.com/how-to-install-twrp/
agatgamez said:
Hi. The easiest way to root your Android is through TWRP... I don't know if your device is supported but take a look. https://www.xda-developers.com/how-to-install-twrp/
Click to expand...
Click to collapse
Hello,
thank you for your answer, but as I said above, I can not use fastboot because the terminal does not support fastboot.
no fastboot --> no TWRP
I found the solution, I used a tool "unlockroot23" which was no longer available on XDA (which I recovered with "web.archive.org")
it installs root 10x faster than kingroot and cleaner.
I re-share the links, if you can serve someone.
>>link unlockroot23<<
Thank you all for your help
dededede said:
I found the solution, I used a tool "unlockroot23" which was no longer available on XDA (which I recovered with "web.archive.org")
it installs root 10x faster than kingroot and cleaner.
I re-share the links, if you can serve someone.
>>link unlockroot23<<
Thank you all for your help
Click to expand...
Click to collapse
I did my best, always happy to help

Categories

Resources