Hello my friends
Good as recently know the Sony launched the lollipop firmware for d5803, and also know still do not have the recovery'm waiting anxiously for it haha. good'll do a mini tutorial to help them maintain the permissions so gives to delete some things like native apps. come on
# Install the firmware 23.0.A.2.106
# Make Root how giefroot
# Extract the file giefroot and within it there will be the files folder, you hold down shift and click the right mouse button and go to the option open command window here, Plans to open the cmd and type these commands below or copy and paste one by one. Well look at your mobile screen, will ask the permissions of adb.
adb push systemrw.sh /data/local/tmp
adb push modulecrcpatch /data/local/tmp
adb push wp_mod.ko /data/local/tmp
adb shell
chmod 777 /data/local/tmp/systemrw.sh
chmod 777 /data/local/tmp/modulecrcpatch
chmod 777 /data/local/tmp/wp_mod.ko
su
cd /data/local/tmp
./systemrw.sh
# Once you have done the above option you check with the root explorer to this with the permissions RW-RO
# download the firmware lollipop 23.1.A.0.690 also download the PRFCreator, UPDATE-SuperSU-v2.46, Z3c-lockeddualrecovery2.8.3-RELEASE.flashable. With these files you create a rom zip pre rooteada. place on your sd card, enter the recovery and give the following wipes
**system, data, cache** given wipes, install the rom preroot and the end of the installation you off the phone.
# Open FlashTool in flashmod select the option D5803_23.1.A.0.690_Baltic_Generic firmware on the right side has the option called Exclude: below have numerous options, you mark only the option SYSTEM and click flash, do the flash firmware.
# Turn on the phone and see how this the permissions with root explorer. End :victory:
The files mentioned above to download are all found right here on xda :good:
Thanks my friend >>Pedrooca <<
Do not forget to give me a thank you [:good:], it will be great for me because somehow will encourage me to keep my work and create new roms and mods! Thank you all
So far no bug was found. I ask you please file a bug found that I can fix. Thank you
Related
I just put cm7 on a sd and am running it on my NC. how do I get the market on it? I saw one link but don't understand how to do it.
If all you want is the market, you can download the newest market APK from my webserver. The link is:
http://www.r00tyou.com/android/tools/Vending(new).apk
To push it to the device simple connect the device to your computer using ADB and type the following in the console:
adb devices
adb install \path\to\the\downloaded\apk.apk
Click to expand...
Click to collapse
Wait for it to successfully transfer over and install.
The viola, you have the newest market APK.
However, I suggest that you download the newest GAPPS from the cyanogen website and push over the whole gapps.
To do this, simply download the latest GAPPS from here:
http://wiki.cyanogenmod.com/index.php?title=Latest_Version#Google_Apps
Again, using ADB type the following commands:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb push [the path to your SDK tools folder]\system system/
adb reboot
Click to expand...
Click to collapse
The console will show the progress of what apps are being transferred over and installed. Once it is done rebooting it will prompt you for logging in to your google account to setup your device. You can simply skip this (Tapping in each corner of the screen starting from the top left going clockwise) or you can proceed with the setup process.
Hope that helps
Thanks for the info. It took some doing because I haven't written code since DOS.
Thanx alot man i had the same problem and this worked perfecty
Not sure if it's important since /system/ is mounted ro anyway but all apps in /system/app/ have 644 permissions, pushing files with adb (whether in linux or windoz) will give them 755 permissions defaultly, so I usually do a:
chmod 644 [app-name].apk
after I transfer the file. Might be a good idea to do this if you are remounting it a lot.
Cheers,
Mike
PS. Themed Markets :-D
Ok now that we got Root on Arc thanks to our devs (Bin4ry...) it's time to move to the next step...recovery!
All the devs who want to discuss, brainstorm, work on and edit recovery for Arc are all invited here.
I don't consider myself a dev so I will let you begin...
Can you check which
/dev/input/eventX [X is a number]
is the Keys under the display?
On X10 it's
/dev/input/event2
f.e.:
You can try it with:
cat /dev/input/event2
now press the keys, do you see some output? If not just try the next one. Until you find the right one for the keys.
Regards
On mine (unbranded, unlocked, UK version) it's /dev/input/event1
Okay,
Flashtool is already prepared for this case!
So we can try it directly. Download latest!!!!! Flashtool (version 2.9.1) and download the chargemon.zip from my attachment.
Flashtool link:
http://forum.xda-developers.com/showthread.php?t=920746
Unzip the file and copy it into flashtool folder:
Flashtool/custom/xRecvery/
overwrite the original chargemon file!
Now open flashtool and and click "Ask Root Permissions", if that had worked you will see that the "xRecovery" Button on the right side gets activated.
Push it now!
When flashtool says -> Recovery installed.
You can reboot the device -> Now push the back button on the device during the booting process. If all works you will be in Recovery
Regards
Flashed the recovery, but it doesn't appear to be loading (tried rebooting while holding the back button, and 'adb reboot recovery')
adb reboot recovery won't work!
try opening flashtool ->Advanced -> Recovery -> Reboot in recovery.
Does this work?
Regards
Nope, didn't work!
ok, thanks for testing.
Can you check if the files are there correctly ?
use adb shell and type:
cat /system/bin/chargemon
do you get a readable text or some weird signs?
Regards
Strange symbols
As an update - I copied the correct version onto the phone (the script) and it still does the same thing
Okay thanks,
maybe this will help.Problem is that we cannot run anything from /data/.....
So Flashtool fails to install it :/
Just run the RunMe.bat
Regards
Bin4ry said:
Okay thanks,
maybe this will help.Problem is that we cannot run anything from /data/.....
So Flashtool fails to install it :/
Just run the RunMe.bat
Regards
Click to expand...
Click to collapse
File seems to be missing 'sh'. Also, getting permission denied when attempting to copy into /system/bin. (/system/bin permissions are root:shell, 755).
you're missing a file ("sh") and the adb push commands failed - I modified your batch file slightly, but it doesn't work, possibly due to the missing "sh" file
Code:
adb shell su -c "mount -o remount,rw /dev/block/mtdblock0 /system"
adb shell mkdir /system/recovery
adb push files\recoveryLT15.tar.bz2 /sdcard/arcrecovery/recovery/recovery.tar.bz2
adb push files\sh /sdcard/arcrecovery/recovery/sh
adb push files\chargerLT15 /sdcard/arcrecovery/bin/charger
adb push files\model /sdcard/arcrecovery/recovery/model
adb push files\chargemon /sdcard/arcrecovery/bin/chargemon
adb shell su -c "cp -rf sdcard/arcrecovery/* /system"
adb shell su -c "chmod 04755 /system/bin/chargemon"
adb shell su -c "chmod 04755 /system/bin/charger"
adb shell su -c "chmod 04755 /system/recovery/sh"
adb shell su -c "chmod 444 /system/recovery/recovery.tar.bz2"
Ups
Sorry i said before long day today!
Here is one with SH included.
Hope it works for you, if not i have to put it into system.img directly or you have to do all that on your own via shell directly!
Regards
Doesn't appear to be at the moment stuck on the Sony Ericsson screen when I choose reboot into recovery but it boots normally when I adb reboot it.
Powered off, then booted with back button held town, just bootloops
well this is quite good!
It seems the phone tries to start the recovery but for some reason it won't start!
It's designed the way that on next reboot it have to reboot normal, so no need to worry about this behaviour, it should be stick on the logo aswell if you push the key during boot now!
Let me think about this tomorrow, i have to think if the problem is the compiled file or the script! If it's the file we will have to wait for Z, he has the sources on the recovery and i'm just too lazy to reconstruct them for the ARC
But you can check if all files are in right place with right permissions and IF they are really the files ?
Regards
originlabs said:
Powered off, then booted with back button held town, just bootloops
Click to expand...
Click to collapse
But if you DONT press a button it boots okay or not ?
Regards
Bin4ry said:
But if you DONT press a button it boots okay or not ?
Regards
Click to expand...
Click to collapse
Yes, booting with no keys is fine.
Does the recovery mount and filesystems, and if so, does it write a log file?
Just look in the chargemon and extract the tar.bz2 to see how it works.
I think that the init from recovery (the recovery itself) is not working because of incompatible compilation.
So it cannot write anything into logs!
But it's good that the script itself is still working, we can create a working recovery now from this base
I go and get some sleep now! cu
Regards
Hi,
i played a lot with Zenonia on my SGS with Froyo 2.2.
Before upgrading/flashing to Gingerbread 2.3.4 i backed up Zenonia savefiles (\data\data\com.gamevil.zenonia\files\*.*) using Root Explorer.
Now i would like to restore the savefiles, but whenever i try to copy my backups in the same folder the game does not recognize them as valid savefiles.
I don't want to start again from scratch.
Any suggestion?
Mattia.
Did it!
0) Have at hands the backup of the following files: BGM.sav, option.sav, Save*.dat. You can find them in \data\data\com.gamevil.zenonia\files\
1) Start ZENONIA and save for the first time.
2) Quit ZENONIA and force stop it in Manage Application.
3) Goto \data\data\com.gamevil.zenonia\files\ and delete the newly generated files (BGM.sav, option.sav, Save*.dat)
4) Copy your backups in \data\data\com.gamevil.zenonia\files\
5) as root do the following:
Code:
chmod 777 BGM.sav
chmod 777 option.sav
chmod 777 Save*.dat
Now you can enjoy your old savegames!
Mattia.
aittam said:
5) as root do the following:
Code:
chmod 777 BGM.sav
chmod 777 option.sav
chmod 777 Save*.dat
Click to expand...
Click to collapse
Ok, I did everything up until the last step. I have temp root access but have no idea how to input the code above. Do I need some sort of terminal app? I get root access with with VISIONAary (which allows root until restart) - i have copied and replaced those files several times and tried creating new saves and replacing them ect with a file explore but I think this part is the key that I am missing. Thanks!
Use adb
You can use a terminal emulator app for executing the given commands from your device itself.
You can also use adb shell from a pc. I use adb and Android Commander to backup and push save files.
QtADB and Android Commander are graphical shells(gui) for adb. They're avialable for windows as well as linux.
aittam said:
Did it!
5) as root do the following:
Code:
chmod 777 BGM.sav
chmod 777 option.sav
chmod 777 Save*.dat
Now you can enjoy your old savegames!
Mattia.
Click to expand...
Click to collapse
No such file or directory
how to do it?
aittam said:
Did it!
0) Have at hands the backup of the following files: BGM.sav, option.sav, Save*.dat. You can find them in \data\data\com.gamevil.zenonia\files\
1) Start ZENONIA and save for the first time.
2) Quit ZENONIA and force stop it in Manage Application.
3) Goto \data\data\com.gamevil.zenonia\files\ and delete the newly generated files (BGM.sav, option.sav, Save*.dat)
4) Copy your backups in \data\data\com.gamevil.zenonia\files\
5) as root do the following:
Code:
chmod 777 BGM.sav
chmod 777 option.sav
chmod 777 Save*.dat
Now you can enjoy your old savegames!
Mattia.
Click to expand...
Click to collapse
It actually worked for me but i did'nt find any of these files, so i just C/P "Files" folder.
Thanks !
Thanks, very useful
Indeed root explorer save my ass. I really forgot how to work with this method, glad to found this again. Thank you still working 2021
Well I have Kindle Fire 7 at home and I wanted to install android on,so first I have to root it but I can not describe you how many times and solutions I have tried,Binary root,Qemu root, KF First Aide.So first two works like a charm and after "Root" is done I try to test it with ES file explorer and root is not applied.I really don't know what I can do more.
I am at version 11.3.2.5
What can I do?
duvnjak said:
Well I have Kindle Fire 7 at home and I wanted to install android on,so first I have to root it but I can not describe you how many times and solutions I have tried,Binary root,Qemu root, KF First Aide.So first two works like a charm and after "Root" is done I try to test it with ES file explorer and root is not applied.I really don't know what I can do more.
I am at version 11.3.2.5
What can I do?
Click to expand...
Click to collapse
My kindle is this model: kindle fire p48wvb4
duvnjak said:
My kindle is this model: kindle fire p48wvb4
Click to expand...
Click to collapse
BUMP Please help me
duvnjak said:
bump please help me
Click to expand...
Click to collapse
**** you everyone **** youuuuu!
mine just updated to 11.3.2.6 yesterday w/o my knowledge
ugh, I'll never get to root this guy
duvnjak said:
**** you everyone **** youuuuu!
Click to expand...
Click to collapse
No need to flame. We all saw your request.
Head over to kfsowi.com which will porbably redirect you to another site where you can find a rooting guide.
Root for "11.3.2.6_user_326002520"
It´s still possible to root 11.3.2.6 with KindleSuite with a small tweak:
1.) Get an actual version from KindleSuite: https://github.com/secretdevwork/KindleSuite/wiki
2.) Extract the archive and search in folder "/resources/tools" for the file "11325.bat" and make a backup of this file
3.) open "11325.bat" in a text editor
4.) search for the code line
Code:
adb shell chmod 755 /data/local/tmp/*
replace this line with the following code lines:
Code:
adb shell chmod 755 /data/local/tmp/su
adb shell chmod 755 /data/local/tmp/exploit
adb shell chmod 755 /data/local/tmp/rootme.sh
5.) save the edited file
6.) start KindleSuite, go to Root section and select the "11.3.2.5" entry (which leads to the edited Batch skript)
7.) start the rooting procedure as described by KindleSuite
8.) profit
This is just a small tweak to fix the chmod permission problems with the original script but I think KindleSuite will be updated in a few days.
P.S.: the KindleSuite root procedure does restore 11325-boot.img but nevermind it is binary the same as in the original 11.3.2.6_user_326002520 image included.
Calibaan said:
It´s still possible to root 11.3.2.6 with KindleSuite with a small tweak:
1.) Get an actual version from KindleSuite:
2.) Extract the archive and search in folder "/resources/tools" for the file "11325.bat" and make a backup of this file
3.) open "11325.bat" in a text editor
4.) search for the code line
Code:
adb shell chmod 755 /data/local/tmp/*
replace this line with the following code lines:
Code:
adb shell chmod 755 /data/local/tmp/su
adb shell chmod 755 /data/local/tmp/exploit
adb shell chmod 755 /data/local/tmp/rootme.sh
5.) save the edited file
6.) start KindleSuite, go to Root section and select the "11.3.2.5" entry (which leads to the edited Batch skript)
7.) start the rooting procedure as described by KindleSuite
8.) profit
This is just a small tweak to fix the chmod permission problems with the original script but I think KindleSuite will be updated in a few days.
P.S.: the KindleSuite root procedure does restore 11325-boot.img but nevermind it is binary the same as in the original 11.3.2.6_user_326002520 image included.
Click to expand...
Click to collapse
Just says waiting for device after i select 11.3.2.5
Of course you still need an ADB connection and a fastboot cable for rooting the 7" Kindle and according to the "Waiting for device..." ADB connection is not established.
Hello,
I have been bothered for some time that you don't have full RW access on a global level in the system, edit programs or cannot really edit the default. prop or build. prop or the fingerprints. Sure Magisk Module works somehow ... Only this gives you a real RW option and you are a real admin of your own phone.
So here are the instructions
Requirements:
1: Install TWRP, please take the decrypted version Mi11Ultra(Pro)-twrp3.5.1-recovery-21.5.9-decrypted.img
2: Root via Magisk (in my case Canary binary installed via TWRP
3: Download and install Minimal ADB and Fastboot
4: Download Superrepack-arm_64_pie and unzip it into the Minimal ADB and Fastboot folder
5: Start the file MAF32 executable from the Minimal ADB and Fastboot folder. Now enter what comes next in the input window:
adb
push superrepack.arm64_pie/data/local/tmp
adb shell
see below
cd/data/local/tmp
mv superrepack.arm64_pie superrepack
chmod 755 superrepack
stop
./superrepack/dev/block/bootdevice/by-name/super
sync
reboot
You have to repeat this process at least 5 times, and the system is already completely RW in the Root Explorer ect. Just klick on enter again 5 times....
Now you will be able to edit global and systemwide , you can switch RW on RootExplorer on. Edit on the fly is possible again.
There is also another possibility in which the system has to be flashed again manually via Fastboot. If necessary, I would be happy to provide instructions.
greetings
This Tool needs to be downloaded
https://forum.xda-developers.com/attachments/super_image_tools_v15-zip.5303007/
Credits:
@munjeni
[TOOL][WIN,LIN,AND,DARW] Super image tools | extract or make partitions RW in super partition
Disclaimer: Super image tools was made for testing and educational purposes, ME is not responsible for what you do on/with your device using our tools, you must agree that you using our tools on your own risk, I am not responsible for anything...
forum.xda-developers.com
Command doesn't work!
dxy180 said:
Command doesn't work!
Click to expand...
Click to collapse
adb
push superrepack.arm64_pie /data/local/tmp
adb shell
see below
cd /data/local/tmp
mv superrepack.arm64_pie superrepack
chmod 755 superrepack
stop
./superrepack/dev/block/bootdevice/by-name/super
sync
reboot
try now
What would you need this for?
xNAPx said:
What would you need this for?
Click to expand...
Click to collapse
for FULL Systemwide R+W Access .