Hi i have rooted my galaxy tab 10.1 wifi only, after i have installed the ClockworkMod Recovery'
and after the rom [ROM][ICS] JellyBeanRom ICS v5 [P7500][P7510][13.08.2012] - xda-developers.
All seems ok i have superuser and superSu .
I have tried to use some apps for root but dont work any such as Titanium backup root explorer etc
I have update superuser and superSu by play and by flash not resolved .
Root Checker done me this:
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - version 0.96 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Standard Location
Check Command: ls -l /system/bin/su:
Result: lrwxrwxrwx root root 2019-08-31 03:30 su -> ../xbin/su
Analysis: File: su is a symbolic link pointing to another file: ../xbin/su
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: root user - ro.secure=0
Results provided on your GT-P7510 device
please can you help me?
Try uninstalling one of the two SU apps...you should only need one to my understanding. Then reboot right after.
If that doesn't work you may have to unroot completely and start over.
Hi dear friend...
I had the same problem(likely) with some APPs in ICS...please do the following:
First if you are running ICS,disable(or uninstall) superuser(supersu is sufficient),then open supersu and look at your list of APPs in the first page,if the # mark in front of some APPs are green,then they have root access.if not, tap on them,in the window that appears,in the root access drop down list choose "Grant"...if even this didn't solve the issue please tell us to send you a working root package...
djmatt604 said:
Try uninstalling one of the two SU apps...you should only need one to my understanding. Then reboot right after.
If that doesn't work you may have to unroot completely and start over.
Click to expand...
Click to collapse
I have tried this but is the same!
arashtarafar said:
Hi dear friend...
I had the same problem(likely) with some APPs in ICS...please do the following:
First if you are running ICS,disable(or uninstall) superuser(supersu is sufficient),then open supersu and look at your list of APPs in the first page,if the # mark in front of some APPs are green,then they have root access.if not, tap on them,in the window that appears,in the root access drop down list choose "Grant"...if even this didn't solve the issue please tell us to send you a working root package...
Click to expand...
Click to collapse
Hi tank you for help me i tried this but superSu dont work : exe SU not present and uperSu cant instal this is a problem!
pls any idea?
skyone75 said:
i tried this but superSu dont work : exe SU not present and uperSu cant instal this is a problem!
pls any idea?
Click to expand...
Click to collapse
Yes...you must get su and supersu.I've put it for you in the attachment...
Note that installing superuser or supersu only doesn't mean rooting...
All the credits of this package go to Max Lee from Zedomax...
arashtarafar said:
Yes...you must get su and supersu.I've put it for you in the attachment...
Note that installing superuser or supersu only doesn't mean rooting...
All the credits of this package go to Max Lee from Zedomax...
Click to expand...
Click to collapse
Tank you i tried to install this file now i have Clocworkmod recovery v 5.8.3.1 and result is :
Installing: /sdcard/GalaxytabHacks.com_superuser.zip
Finding update package...
Opening update package...
Installing update....
Install from sdcard complete
but i have the same problem!
You think is better unroot?
It sounds like you've tried everything else. I would back up stuff you need, unroot with stock firmware and start over with just one option. You may choose to skip manually rooting altogether and just flash a rooted ROM. Good luck!
The first time you flash this you must open supersu,a message says that the su binary is outdated,press OK,after some seconds connected to the internet,you see success message,reboot(just optional) znd execute the app you want to gain root access,if it fails(no prompt appeared)don't get disappointed,close the APP,launch supersu,see the # mark in front of the APP's name,tap on it,from the "root access" select "Grant"...
Edit:if you want to flash a ROM then have a look at Jelly Bean ICS in the dev forum...it's ICS and comes with root+many other goodies...
arashtarafar said:
Yes...you must get su and supersu.I've put it for you in the attachment...
Note that installing superuser or supersu only doesn't mean rooting...
All the credits of this package go to Max Lee from Zedomax...
Click to expand...
Click to collapse
arashtarafar said:
The first time you flash this you must open supersu,a message says that the su binary is outdated,press OK,after some seconds connected to the internet,you see success message,reboot(just optional) znd execute the app you want to gain root access,if it fails(no prompt appeared)don't get disappointed,close the APP,launch supersu,see the # mark in front of the APP's name,tap on it,from the "root access" select "Grant"...
Edit:if you want to flash a ROM then have a look at Jelly Bean ICS in the dev forum...it's ICS and comes with root+many other goodies...
Click to expand...
Click to collapse
Ok i try to unroot , need only flash a firmware samsung in download mode with odin?
wich firmware ? hc 3.2 or ics i have tab 7510 wifi only buy in switzerland with italian language
Is there not an Italian ICS? If not try the UK firmware with IT support.
djmatt604 said:
Is there not an Italian ICS? If not try the UK firmware with IT support.
Click to expand...
Click to collapse
But is better honey com 3.2 or ics for unroot?
Tanks
ICS is faster but lacks flash player...but it doesn't harm too much...
arashtarafar said:
ICS is faster but lacks flash player...but it doesn't harm too much...
Click to expand...
Click to collapse
i have unrooted and now i have installed ROM][ICS] JellyBeanRom ICS v5 [P7500][P7510][03.09.2012] v6
Itink the problem was then i caming by Honeycomb:
Instructions (IMPORTANT!):
1. Coming from stock ICS.
If you don't have any recovery then flash it (for example TWRP). Then boot into recovery, make a full wipe and flash my rom.
2. Coming from Honeycomb or any other custom like CM9/CM10/AOKP etc.
First you have to flash stock ICS, regarding which version of the Tab you have (3G/non 3G). Then you have to flash a custom recovery (for example TWRP), boot into it and make a full wipe. Finally flash my rom.
tanks for help bye .
That makes sense. You can run into problems with some ROMs depending on where you're coming from. I ran into problems with ICS ROMs in the beginning because of a bootloader issue...I flashed stock firmware to change my base and built ROMs from there as you're describing in Step 2.
Enjoy!
I have similar problem...
I own a T-Mobile 10.1 Tab, stock ICS... After flashing the stock ICS (i came from CM9) with odin, i flashed the CWM, and the applyed the "root.zip" file...
Booted and I saw that Superuser has been installed.
But I have no root access... The applications return that the root requisitation timed-out...
Anyone knows why? It shoud be quite simple....
Another thread has just been opened in the General area with someone asking the same question. The answers are there, friend...you just have to look for them Here it is again (assuming you are having the same problem and it sounds like you are) - it's because the version of Superuser the root.zip you're using drops into the system is not friends with ICS. Simply update Superuser to 3.1.3. Go Here , download Super 3.1.3-ARM-Signed.zip, drop it on your tablet's root, flash it from recovery and reboot. You should be good after that.
Tab 10.1 ICS flash player 11
arashtarafar said:
ICS is faster but lacks flash player...but it doesn't harm too much...
Click to expand...
Click to collapse
Since the adobe flash player 11 work for tab 10.1 HC 3.2 P7510, and some ICS early device.
adobe system no more certificate and support for ICS 4.0.x device.
So it SHOULD work for my Tab 10.1 P7510 ICS 4.0.4 too. and Yes. It is.
You no longer fine Flash player in Tablet PLAY store once you upgrade to ICS.
but you can find it in PC version PLAY store, then PUSH install from PC to Tablet P7510.
and YES, it work fine for my P7510 with ICS!
https://play.google.com/store/apps/details?id=com.adobe.flashplayer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
or try download this APK to your tablet to install:
View attachment adobe.flashplayer11.apk
After install , open Flash player setting in your APPs, and setup options, then yoi are ready for any FLAH web object.
even web flash online games.
Related
Hello,
i wish to create an update.zip to copy fonts from the zip into the system/fonts/ folder because i delete them and kept one font but it seems android doesn't boot with one font only need other fonts to be there (or atleast matching the names) to be able to boot.
adb push doesn't work giving me permission denied because /system is not mounted R/W (which i do using Super Manager for example)
i read other update.zip files and it seems i need to create CERT.SF and MANIFEST.MF files in META-INF , but it seems there are some SHA1-Digest: below each file (is this a md5checksum?) so i can't just replace file names and apply it
any ideas how can i do it without Wipe data/factory reset ? (and if factory reset is my last option would fonts be returned or factory reset doesn't get fonts back? i feel not)
Thanks
The app below will sign the zip and allow you to flash it. You just need to put the zip inside the folder and call it 'update.zip'
l0st.prophet said:
The app below will sign the zip and allow you to flash it. You just need to put the zip inside the folder and call it 'update.zip'
Click to expand...
Click to collapse
Thank you , any chance there i a Linux version out there? i'm using adb on ubuntu
and for CERT.SF and MANIFEST.MF i just create them manually based on any update.zip file i download earlier?
I'm on windows now and i've signed the file, when i try to apply it from recovery i get
E:signature verification filed
Installation aborted
what i'm missing?
attached my signed update.zip
it seems i had a folder update inside the zip
i have re-created one and signed it and still same error
attached the file
btw as i'm rooted and i used to su from adb shell and terminal emulator earier, any idea why su not working now?
$ su
[1] + Stopped (signal) su
$
[1] Segmentation fault su
$
is it because i'm on the HeRO logo boot screen ? it didnt get in yet?
btw for linux/ubuntu users who want to sign on linux you can use this:
Code:
java -jar signapk.jar testkey.x509.pem testkey.pk8 update.zip update_signed.zip
inside the Auto Sign folder
after signing on linux i get the following:
E: failed to read footer from / sdcard/update.zip (I/O error)
E:signature verification failed.
Installation aborted
First of all, please use the edit button, posting 6 times in a row is very hard to read, and is considered bumping your own thread which is a quick way to lose friends.
Secondly, the autoSign program creates a file called update_signed.zip which is the file you need to flash, the cert and manifest files are created by the process, you don't need to touch them. I have attached a signed version of your zip
I resigned it for you, see attachment. I use "androsign" I found here somewhere on XDA, maybe go look for it. It is a very easy tool edit: Too late
When you are in "adb shell" you should have SU rights already.
Otherwise there is an option in adb to switch to SU rights, just type in "adb help" of a howto.
First of all , sorry for the multiple posts
second i've tried both update-signed.zip and update_signed.zip and both of them gave me the same error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*P.S: sorry if i'm not allowed to put an image ill delete it
EDIT:
riemervdzee said:
When you are in "adb shell" you should have SU rights already.
Otherwise there is an option in adb to switch to SU rights, just type in "adb help" of a howto.
Click to expand...
Click to collapse
i tried to the help i didn't find how to set su in the right roots?
Have you flashed an alternative recovery at all? This one looks like the default one.
And look at the first error, it asks for a path in /cache/... Just get amon_ra recovery This way you can select which zip you want to flash (as long as they are in the root of the sd-card).
And from "adb help":
"adb root - restarts the adbd daemon with root permissions".
However seen you still have the original recovery, that probably won't work in recovery.
You said you rooted the device already right? maybe you can move the files with adb then when the ROM is trying to start, and after everything works get a real recovery where you can do something.
riemervdzee said:
Have you flashed an alternative recovery at all? This one looks like the default one.
And look at the first error, it asks for a path in /cache/... Just get amon_ra recovery This way you can select which zip you want to flash (as long as they are in the root of the sd-card).
And from "adb help":
"adb root - restarts the adbd daemon with root permissions".
However seen you still have the original recovery, that probably won't work in recovery.
You said you rooted the device already right? maybe you can move the files with adb then when the ROM is trying to start, and after everything works get a real recovery where you can do something.
Click to expand...
Click to collapse
yeah i tried the adb root already but getting "adbd cannot run as root in production builds"
yes i'm rooted and everything is fine
btw why deleting fonts prevents the phone from booting although there is one font there "not the default one"
what i want is to push the font files into the phone but getting the error i mentioned earlier that its not mounted as as R/W:
[email protected]:~/linux_adb_fastboot/hero_fonts$ for i in `cat list`; do adb push $i /system/fonts/$i ; done
failed to copy 'DroidSerif-Bold.ttf' to '/system/fonts/DroidSerif-Bold.ttf': Read-only file system
failed to copy 'DroidSerif-Regular.ttf' to '/system/fonts/DroidSerif-Regular.ttf': Read-only file system
failed to copy 'DroidSerif-Italic.ttf' to '/system/fonts/DroidSerif-Italic.ttf': Read-only file system
failed to copy 'DroidSansMono.ttf' to '/system/fonts/DroidSansMono.ttf': Read-only file system
failed to copy 'DroidSansFallback.ttf' to '/system/fonts/DroidSansFallback.ttf': Read-only file system
failed to copy 'DroidSerif-BoldItalic.ttf' to '/system/fonts/DroidSerif-BoldItalic.ttf': Read-only file system
failed to copy 'DroidSans-Bold.ttf' to '/system/fonts/DroidSans-Bold.ttf': Read-only file system
failed to copy 'Clockopia.ttf' to '/system/fonts/Clockopia.ttf': Read-only file system
failed to copy 'DroidSans.ttf' to '/system/fonts/DroidSans.ttf': Read-only file system
and yes adb remount doesn't work
[email protected]:~/linux_adb_fastboot/hero_fonts$ adb remount
remount failed: Operation not permitted
You have "rooted" your phone but you can't get adb root? That is contradictory
But since I'm in a good mood. Try to boot up the phone on your ROM, so not in recovery or bootloader. Then try to remount.
If remount is still failing, you don't have root.
Maybe you should also read your stuff a bit in before attempting anything. You are kinda screwing up your phone here.
Yes i'm sure i'm rooted i had universal root which i can root and unroot, and before deleting the fonts i used to do su and get root
also to confirm im rooted i used to use Market Access to access US and other markets to buy (since my country only has free apps not paid yet)
i didn't get the part of botting up the phone using my ROM ?
also a side question when booting the phone normally (i think this is what you meant about booting into the ROM?) and it stays on the HeRO logo as you can see i can access the adb shell etc.. so the phone is actually responding but not booting because of the fonts not there? or something else could be broken ?
Bashar . said:
Yes i'm sure i'm rooted i had universal root which i can root and unroot, and before deleting the fonts i used to do su and get root
also to confirm im rooted i used to use Market Access to access US and other markets to buy (since my country only has free apps not paid yet)
i didn't get the part of botting up the phone using my ROM ?
also a side question when booting the phone normally (i think this is what you meant about booting into the ROM?) and it stays on the HeRO logo as you can see i can access the adb shell etc.. so the phone is actually responding but not booting because of the fonts not there? or something else could be broken ?
Click to expand...
Click to collapse
Read "adb logcat" or in adb shell, use the linux command "dmesg" to see what is wrong.
And yes, with booting your ROM I mean the normal boot process. But probably android won't start as it can't find the fonts (they are essential).
And really... Read your stuff. You deleted fonts but didn't put any new there yet? You are asking for problems, while you ask us to solve it.
Then you come up with the plan to flash the new fonts, but you don't have a customized recovery.
riemervdzee said:
Read "adb logcat" or in adb shell, use the linux command "dmesg" to see what is wrong.
And yes, with booting your ROM I mean the normal boot process. But probably android won't start as it can't find the fonts (they are essential).
And really... Read your stuff. You deleted fonts but didn't put any new there yet? You are asking for problems, while you ask us to solve it.
Then you come up with the plan to flash the new fonts, but you don't have a customized recovery.
Click to expand...
Click to collapse
I did put one font there, but my mistake is not renaming it as the default font names that was there, i thought it would scan the fonts folder and use ANY font listed there
but seems not...
catlog shows im missing the fonts: http://dpaste.org/ADyJ/
dmesg output: http://dpaste.org/8IGw/
i never thought the recover it had won't let met flash the fonts
EDIT: i tried the mv command as linux user but my main problem is that its a read only system
[email protected]:~$ adb shell
$ cd system
$ cd fonts
$ ls
DroidSansArabic.ttf
$ mv
USAGE: mv <source...> <destination>
$ mv DroidSansArabic.ttf DroidSans.ttf
failed on 'DroidSansArabic.ttf' - Read-only file system
$
You can't do "adb remount" when starting normally? You have rooted the ROM, not the recovery (which refuses root access, as it is still the default one).
If everything fails, you can always do a RUU. (google "hero RUU"), this will reset everything as HTC wants it. Then you start from scratch again.
riemervdzee said:
You can't do "adb remount" when starting normally? You have rooted the ROM, not the recovery (which refuses root access, as it is still the default one).
If everything fails, you can always do a RUU. (google "hero RUU"), this will reset everything as HTC wants it. Then you start from scratch again.
Click to expand...
Click to collapse
yeah it seems thats my only option
I was hoping to learn by fixing, i'll flash it tomorrow then
now back to the question, why the update.zip that we were trying to sign is not flashable or signable ? what might be the reason? is it because i didn't root the recovery ?
i tried an stock Hero rom and still gives me invalid signature, i can't apply any rom at all now or what?
I have create rooting method based on DooMLoRD method [ROOT] Rooting Toolkit for Xperia 2011 ICS [FW:.562]{LOCKED & UNLOCKED BOOTLOADERS} but have different approach.
special thanks to DooMLoRD
REQUIRED ROOTED DEVICE prior to update
How this method work?
1. create file /data/local.prop contain "ro.kernel.qemu=1" to enable root shell (this step must be done on ROOTED DEVICE)
2. update using Update Service/PC Companion/Flashtool without Factory Reset
3. after device updated,we should gained root shell that we use to push su binary and superuser.apk
Download : Xperia-ROOT.rev3.zip
Download : Xperia-ROOT.rev4.zip
Including autoinstall Stericson Busybox 1.20.1 and nAa CWM Recovery 5.0.2.7
extract Xperia-ROOT.rev3.zip to any folder,so you got something like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Another great tutorial made by DragonClawsAreSharp can be found at
[Tutorial]Root.Xperia 4.0.4 ROM | 4.1.B.0.431
STEP :
1. run 01-local-prop.cmd to create /data/local.prop (enable android emulator hack)
2. power off device and update your device WITHOUT FACTORY RESET
Update Service
select Update (recommended)
Flashtool
UNMARK WIPE DATA
after your device updated
on 1st boot your device will reboot once
on 2nd boot it will boot normally
if you got bootloop run 02-push-root-files.cmd right away
until it finished wait for 1 or 2 reboot
if you still got bootloop you need to reflash rootable firmware(zergrush method) then try again
3. run 02-push-root-files.cmd to push su binary and superuser.apk
4. your device will automatically reboot
5. enjoy your new rooted firmware
this method tested on :
1. Arc S ROOTED GB 4.0.2.A.0.42 updated to ICS 4.0.4
2. Ray ROOTED ICS 4.0.3 updated to ICS 4.0.4
3. Active ROOTED GB 4.0.2.A.0.42 updated to GB 4.0.2.A.0.62
tested by user:
1. SK17i ROOTED GB 4.0.2.A.0.58 updated to GB 4.0.2.A.0.62 by Bolussimo
2. Rooted SK17i FW 4.1.B.0.431 by draco_ag
3. LWW WT19i Rooted GB 4.0.2.A.0.58 updated to ICS 4.0.4 by alness1213
4. SK17i ROOTED GB 4.0.2.A.0.42 updated to ICS 4.0.4 by DragonClawsAreSharp
Dis method can only work on non-latest firmware.... lets say am using .62 firmware which is not rooted, dat means i need to downgrade to lower version & ROOT it to use dis!!!
Nice piece of work brov...
whalesplaho said:
Dis method can only work on non-latest firmware.... lets say am using .62 firmware which is not rooted, dat means i need to downgrade to lower version & ROOT it to use dis!!!
Nice piece of work brov...
Click to expand...
Click to collapse
Yup,that's it bro.
As we know zergrush exploit doesn't works on FW starting .62 and above.
we just need any firmware that can be rooted using zergrush method then use this tool before and after upgrade to gain updated and rooted firmware.
I have tested this method on my Xperia Active running on ROOTED FW .42(rooted using zergrush method) use this tool before and after update to gain rooted FW .62
When doing update you MUST NOT do factory reset.
Wipe Data will deleted any add file & make tha phone return to factory reset right....?
whalesplaho said:
Wipe Data will deleted any add file & make tha phone return to factory reset right....?
Click to expand...
Click to collapse
it will clean all data from your phone,all user installed app and setting will gone.
in rooting process DO NOT factory reset.if you wish to factory reset you can do it after running the tool after 1st boot (step 3 - 5 )
And you really did it, bro! I will use your method, root my .62 fw and get ready for my rooted ICS. Thank you again!
Sent from my SK17a using xda premium
A little question...
Just add these line " ro.kernel.qemu=1" to already exist /data/local.prop right???
Or make another /data/local.prop???
Till-Kruspe said:
A little question...
Just add these line " ro.kernel.qemu=1" to already exist /data/local.prop right???
Or make another /data/local.prop???
Click to expand...
Click to collapse
when running 01-local-prop.cmd
it will overwrite /data/local.prop
so /data/local.prop only contain "ro.kernel.qemu=1"
you need to run 01-local-prop.cmd just before you update your device.
puppet13th said:
when running 01-local-prop.cmd
it will overwrite /data/local.prop
so /data/local.prop only contain "ro.kernel.qemu=1"
you need to run 01-local-prop.cmd just before you update your device.
Click to expand...
Click to collapse
I got bootloop...
Till-Kruspe said:
I got bootloop...
Click to expand...
Click to collapse
did you read this?
puppet13th said:
you need to run 01-local-prop.cmd just before you update your device.
Click to expand...
Click to collapse
puppet13th said:
did you read this?
Click to expand...
Click to collapse
yes...I have done all the step...but got bootloop...
Till-Kruspe said:
yes...I have done all the step...but got bootloop...
Click to expand...
Click to collapse
can you tell me what have you done step by step?
edit :
if you have updated your device and run "02-push-root-files.cmd"
it's look like the script failed to remove /data/local.prop
from 02-push-root-files.sh :
Code:
adb shell rm [COLOR="Red"]-f[/COLOR] /data/local.prop
builtin rm command syntax on GB build :
Code:
rm [-rR] <target>
workaround :
open env.cmd
type these command
Code:
adb shell rm /data/local.prop
puppet13th said:
can you tell me what have you done step by step?
edit :
if you have updated your device and run "02-push-root-files.cmd"
it's look like the script failed to remove /data/local.prop
from 02-push-root-files.sh :
Code:
adb shell rm [COLOR="Red"]-f[/COLOR] /data/local.prop
builtin rm command syntax on GB build :
Code:
rm [-rR] <target>
workaround :
open env.cmd
type these command
Code:
adb shell rm /data/local.prop
Click to expand...
Click to collapse
my phone is rooted 2.3.4 with cwm, FW .58, lock bootloader...
First I run 01-local-prop...but on my phone it doesn't ask for superuser permission...in the 01-local-prop it say complete (done replacing new local.prop)...I have checked /data/local.prop (open with text editor) it has this "ro.kernel.qemu=1"
Then I open up PCC and update my phone to FW .62...Bla bla bla...finished...restart phone.....then bootloop...
what to do now...this is my only phone...please help me...
Till-Kruspe said:
my phone is rooted 2.3.4 with cwm, FW .58, lock bootloader...
First I run 01-local-prop...but on my phone it doesn't ask for superuser permission...in the 01-local-prop it say complete (done replacing new local.prop)...I have checked /data/local.prop (open with text editor) it has this "ro.kernel.qemu=1"
Then I open up PCC and update my phone to FW .62...Bla bla bla...finished...restart phone.....then bootloop...
what to do now...this is my only phone...please help me...
Click to expand...
Click to collapse
if you have FW. 58 or erlier ftf flash it with flashtool DO NOT UNMARK wipe data.
then root it using zergrush method.
try again from step 1
edit :
it's look like you got bootloop because your data partition was full.
now i got bootloop downgraded to fw. 42 without factory reset.i only got 50mb free before flashing.
my rom was odexed before,so 50mb was not enought to hold dalvik-cache from framework and system app
updated 1st post
puppet13th said:
updated 1st post
Click to expand...
Click to collapse
Hi puppet,
How come he was not asked by Superuser for root permission?
Is it because he had allowed adb with root rights earlier and had checked "always allow"? (may be).
Or there can be some other reasons?
Thanks,
Rick
Sent from my SK17i using XDA
Till-Kruspe said:
my phone is rooted 2.3.4 with cwm, FW .58, lock bootloader...
First I run 01-local-prop...but on my phone it doesn't ask for superuser permission...in the 01-local-prop it say complete (done replacing new local.prop)...I have checked /data/local.prop (open with text editor) it has this "ro.kernel.qemu=1"
Then I open up PCC and update my phone to FW .62...Bla bla bla...finished...restart phone.....then bootloop...
what to do now...this is my only phone...please help me...
Click to expand...
Click to collapse
now i hit the bull eye
/data/local.prop : ro.kernel.qemu=1 --> cause system instability that cause bootloop if data partition was full
download Xperia-ROOT.rev3.zip from 1st post and run 02-push-root-files.cmd it will wait for device before reboot(bootloop).after /data/local.prop(ro.kernel.qemu=1) gone,it will boot normally
when it reach home screen you need to make more free space on /data partition
DragonClawsAreSharp said:
Hi puppet,
How come he was not asked by Superuser for root permission?
Is it because he had allowed adb with root rights earlier and had checked "always allow"? (may be).
Or there can be some other reasons?
Thanks,
Rick
Sent from my SK17i using XDA
Click to expand...
Click to collapse
it's look like superuser automatically allow su access from adb shell
i just check from superuser app,there is no shell in apps list.
if i remember correctly old superuser doesn't automatically allow su access from adb shell,it will prompt su access and if allowed or denied it will be added to app list as unknown
puppet13th said:
it's look like superuser automatically allow su access from adb shell
i just check from superuser app,there is no shell in apps list.
if i remember correctly old superuser doesn't automatically allow su access from adb shell,it will prompt su access and if allowed or denied it will be added to app list as unknown
Click to expand...
Click to collapse
Okay. Got it.
So if he had connected his dead cell to the pc and run the 2nd bathc file, things would become alright for him right?
Sent from my SK17i using XDA
DragonClawsAreSharp said:
Okay. Got it.
So if he had connected his dead cell to the pc and run the 2nd bathc file, things would become alright for him right?
Sent from my SK17i using XDA
Click to expand...
Click to collapse
02-push-root-files.cmd doesn't run on su access because of /data/local.prop (ro.kernel.qemu=1)
when ro.kernel.qemu=1 in effect we automatically got root shell
so when we start adb shell we got # instead of $
# = root user
$ = normal user
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a tutorial explaining how to install and modify Adobe Flash Player
to view Hulu Free content on a compatible Android browser.The modification script was made by user NoSudo, whose official thread can be found here.
Root is required for this to work
KitKat 4.4 users see this post for instructions.
Step 1: Install & Configure BusyBox
• Install JRummy's Busybox Installer app from the PlayStore: link
• Open BusyBox Installer and select version 1.20 (not the latest) & install location: /system/xbin
• Click Install
Step 2: Install Script Manager - SManager
• Install Script Manager (free) from PlayStore: link
Step 3: Install Adobe Flash Player 11.1.115.36
• http://download.macromedia.com/pub/...roid/11.1.115.36/install_flash_player_ics.apk
Step 4: Download & Extract FLASHEX 2.05
• Download Flashex205.zip from the attachment below
• Extract the zip using a file manager app & copy Flashex2 folder to root of sdcard (IMPORTANT)
Step 5: Execute FLASHEX script
• Open ScriptManager app & navigate to Flashex2 folder
• Click the flashex205.sh file
• Select "Su" (skull and crossbones icon) & Run
• (Optional) If you want this script to run automatically at each boot, click the Boot option next to the Su from the previous line.
If all went well you should have a patched Adobe Flash Player!
To view Hulu Free flash content you need a compatible browser (I use Boat Browser) and in settings change the "User Agent" to Desktop.
P.S. Getting it to work is one achievement, but getting it to play fluidly is another. I have noticed that different ROMs, Kernels, and even Browsers have an effect on the smoothness of the video playback. I've also found that on my Nexus 10, the audio and video begins out of sync. I've figured out that changing the quality setting on the video after it has begun to play reloads and resyncs it again. More tweaking and testing may eventually improve this but if you're having any of these issues with playback, you're not alone.
---------------------------------------------------------------------------------------------------------------------
thx for the guide,will it only work in the US?
Tripledrop said:
thx for the guide,will it only work in the US?
Click to expand...
Click to collapse
No problem. Yes, unfortunetly the same international restrictions would apply.
Thank you
Working great and smoothly with no sync issue on my htc sensation 4g with Elegancia rom and using proxydroid for us proxy server.
I love Android.
Cannot run script.
I have it stored in the SDcard but when I run the script I get the following message.
/storage/emulated/0/flashex205.sh cannot write to or /.
This message means the scropt can't create any files in teh intended location(s)
try just installing the script in the /mnt/sdcard/Flashex2 and make sure you have read/write permissions in it.
I then changed the directory to /sdcard and reran it and got the same error.
I am running AOKP Buttered 4.2.2 ROM
Hatman41 said:
I have it stored in the SDcard but when I run the script I get the following message.
/storage/emulated/0/flashex205.sh cannot write to or /.
This message means the scropt can't create any files in teh intended location(s)
try just installing the script in the /mnt/sdcard/Flashex2 and make sure you have read/write permissions in it.
I then changed the directory to /sdcard and reran it and got the same error.
I am running AOKP Buttered 4.2.2 ROM
Click to expand...
Click to collapse
Just to be sure, do you have the "Flashex2" folder with all its containing files copied to the root of the sdcard before you ran the flashex205.sh script? The flashex205.sh script has to be executed inside the Flashex2 folder...which has to be on the root of your sdcard.
Example: /sdcard/Flashex2/flashex205.sh
• Extract the zip using a file manager app & copy Flashex2 folder to root of sdcard (IMPORTANT)
Click to expand...
Click to collapse
Ahhh ok so I cannot read very well It installed now thanks. I did not have the folder there just the script. I tried Hulu after I did everything. I am using Boat I set the user agent to desktop and I get the error that Hulu requires Flash player 10.1.53.64 or higher. I have the patched 11.1 installed.
Thanks so much for this! As an added bonus, this mod allows Amazon Instant Video to work. Woo hoo!
Hatman41 said:
Ahhh ok so I cannot read very well It installed now thanks. I did not have the folder there just the script. I tried Hulu after I did everything. I am using Boat I set the user agent to desktop and I get the error that Hulu requires Flash player 10.1.53.64 or higher. I have the patched 11.1 installed.
Click to expand...
Click to collapse
Hmm, make sure in boat browser settings under Page Content Settings you have enabled flash plugin.
That fixed it thanks.
Sent from my Nexus 10 using Tapatalk 4 Beta
ugh....what am I doing wrong?!
I followed the steps and I keep getting Sorry Unfortunately Hulu isn't supported by your device
i'm sure i'm doing something wrong...any idea?
For people that have init.d support I have added a CWM zip that will enable everything for you.
Instead of the working folder being on the SD it is now in data/Flashex2
If you already have flash installed, uninstall it before flashing the zip. Also wipe the dalvik cache and cache partition after flashing the zip.
What it installs:
Flash 11.1.115.36
Busybox 1.20
Flashex 2.05
May take a couple of reboots to set everything up.
problems
I am on Verizon Galaxy Note 3 and follow this step by step and it doesn't work for me. I give SU permission and go to run scripts and it either hangs there or gives me an error each time. I even tried a different app to run scripts and it gives me an error. I have the folder unzipped in the root of my sdcard0. Please help as I can watch flash videos, but still no hulu
"Hulu requires Flash player 10.1.53.64 or higher" Error
I am also getting the Hulu requires Flash player 10.1.53.64 or higher. Script was copied to /mnt/sdcard/Flashex2, directory has r/w, and script executed properly as root and showed no errors. I'm running the latest version of Boat, have Flash set to "Always On", and user agent set to "Desktop". Any ideas?
What version of Android are you guys running? Since KitKat 4.4, Adobe Flash Player doesn't work with the standard apk.
brGabriel said:
What version of Android are you guys running? Since KitKat 4.4, Adobe Flash Player doesn't work with the standard apk.
Click to expand...
Click to collapse
Yep, running KitKat 4.4.
I am on stock rooted 4.3
brGabriel said:
What version of Android are you guys running? Since KitKat 4.4, Adobe Flash Player doesn't work with the standard apk.
Click to expand...
Click to collapse
datawrhsdoc said:
Yep, running KitKat 4.4.
Click to expand...
Click to collapse
I have an idea on how to get it working on KitKat. When I do I'll let you know, and add the instructions to my OP. Stay tuned...
archaleus said:
I am on stock rooted 4.3
Click to expand...
Click to collapse
Try flashing the zip from http://forum.xda-developers.com/showpost.php?p=46165947&postcount=13 ...Then open up Script Manager and run the flashex205.sh script from sdcard/data/Flashex2
For KitKat 4.4.X Users
-Uninstall previous version of Adobe Flash Player
-Install the attached Adobe Flash Player apk
-Follow all of the steps from the OP (obviously, with the exception of the "Install Flash Player" step since we are using the one from this post).
-Now Adobe Flash content will work but you must use Dolphin Jetpack browser for any flash content (including Hulu)
P.S. You may have to go into Dolphin Jetpack settings and enable Flash before viewing...also change "User Agent" to "Desktop". :good:
Anyone can use this ROM as his base for Custom ROMs without asking for permission as long as they include credits wherever it is posted
DEODEXED Stock Jelly Bean with Sense 4+ build 2.20.401.6 for Desire X
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
neXus PRIME for the JB TWRP Recovery
Chainfire for the SuperSU
doiutzu for testing the updater-script and other tests
And anyone directly / indirectly contribute for this ROM
DEODEXED stock ROM
hTC update build 2.20.401.6 (with Heartbleed fix)
Android Jelly Bean 4.1.1 (JRO03C)
Sense 4+
Kernel: 3.4.0-g2b619a5
rooted with SuperSU
Pre-installed Busybox
init.d support
Unlocked bootloader & Custom Recovery fixed for Jelly Bean
Recommended TWRP Recovery by neXus PRIME (http://forum.xda-developers.com/showpost.php?p=36714573&postcount=2)
For hboot 1.25.0002 (JB hboot)
Put the 2.20.401.6_Dodexed.zip on your sdcard
Make sure you already have the TWRP for JB hboot installed (NOT the stock recovery)
fastboot flash the attached boot.img for S-On DX (which comes with init.d feature)
Reboot to recovery
Make a full wipe is recommended but you can always try a dirty flash if your current ROM is stock (odex or deodexed)
Install the 2.20.401.6_Deodexed.zip as how you normally install a custom ROM
Reboot once completed and you are done
Old version 2.20.401.5_Deodexed.zip
http://sourceforge.net/projects/others/files/DX/2.20.401.5_Deodexed.zip/download
*DELETED*
*DELETED*
I still can't remove apps from system.I think something's wrong with my phone.
CrysiZ said:
I still can't remove apps from system.I think something's wrong with my phone.
Click to expand...
Click to collapse
Use Aroma File Manager. I've removed almost all google aps successfully. Rebooted several times and they do not appear again
CrysiZ said:
I still can't remove apps from system.I think something's wrong with my phone.
Click to expand...
Click to collapse
Which ROM ?
As mentioned before, you need a ROM with a properly installed busybox, root and init.d support.
See Part 1 : http://forum.xda-developers.com/showpost.php?p=40359126&postcount=250
See Part 2 & 3 : http://forum.xda-developers.com/showpost.php?p=40359148&postcount=251
And still can't edit build.prop
secthdaemon said:
And still can't edit build.prop
Click to expand...
Click to collapse
On my Deodexed ROM ?
ckpv5 said:
On my Deodexed ROM ?
Click to expand...
Click to collapse
Yes. Made changes via Build Prop Editor app, allowed changes via SuperSU, rebooted and no changes been applied
secthdaemon said:
Yes. Made changes via Build Prop Editor app, allowed changes via SuperSU, rebooted and no changes been applied
Click to expand...
Click to collapse
Here are the screenshots of build.prop editing that I made on a fresh installed deodexed ROM
I made changes to "ro.config.htc.enableCOTA=1" to "ro.config.htc.enableCOTA=0" with Root Explorer (you can see build.prop.bak is created after saving the changes.
And make a reboot, after reboot the "ro.config.htc.enableCOTA" still show 0 and the build.prop.bak is still there
Init.d seems not to be working
C:\Android>adb reboot recovery
C:\Android>adb push 12_test /system/etc/init.d/12_test
27 KB/s (57 bytes in 0.002s)
C:\Android>adb shell chmod 0755 /system/etc/init.d/12_test
C:\Android>adb reboot
C:\Android>adb shell cat /data/local/tmp/test.log
/system/bin/sh: cat: /data/local/tmp/test.log: No such file or directory
You can try this one.
hm...tried to to make changes with root explorer, rebooted, and all changes are gone and no bak file
secthdaemon said:
Init.d seems not to be working
C:\Android>adb reboot recovery
C:\Android>adb push 12_test /system/etc/init.d/12_test
27 KB/s (57 bytes in 0.002s)
C:\Android>adb shell chmod 0755 /system/etc/init.d/12_test
C:\Android>adb reboot
C:\Android>adb shell cat /data/local/tmp/test.log
/system/bin/sh: cat: /data/local/tmp/test.log: No such file or directory
You can try this one.
Click to expand...
Click to collapse
init.d is working fine... you can find zipalign.log in /data
BTW.. which boot.img that you are using ? the one that you posted ?
I gotta go now... will check later and update post #3 when I'm home.
ckpv5 said:
init.d is working fine... you can find zipalign.log in /data
BTW.. which boot.img that you are using ? the one that you posted ?
I gotta go now... will check later and update post #3 when I'm home.
Click to expand...
Click to collapse
Nope, I'm using your boot.img
secthdaemon said:
Nope, I'm using your boot.img
Click to expand...
Click to collapse
It works for me and others too that helped me.... so no idea why it is not working for you
So.. you don't have zipalign.log in /data folder ?
I'm gonna reflash your rom and boot.img just in case, I'll write about results.
secthdaemon said:
Use Aroma File Manager. I've removed almost all google aps successfully. Rebooted several times and they do not appear again
Click to expand...
Click to collapse
I can remove system apps and edit build.prop with aroma without disabled wp. So what? Why do i need this boot.img?
Sent from my HTC Desire X using xda premium
micu13 said:
I can remove system apps and edit build.prop with aroma without disabled wp. So what? Why do i need this boot.img?
Sent from my HTC Desire X using xda premium
Click to expand...
Click to collapse
You don't have to and you don't need the boot.img when you are comfortable doing all these stuff in recovery
Most people prefer to do things not in recovery as most people use recovery just to do nandroid backup/restore and flashing zips. That is why flar2 comes out with a workaround not only for DX but also on other devices such as
HTC One - http://forum.xda-developers.com/showthread.php?t=2235085 & http://forum.xda-developers.com/showthread.php?t=2233665
secthdaemon said:
I'm gonna reflash your rom and boot.img just in case, I'll write about results.
Click to expand...
Click to collapse
Let us know the result... as I'm afraid it is the JB hboot thing as I can't test it as I'm on ICS hboot.
If yes.. then we may need the kernel source then only Dev like neXusPRIME and atis112 can do their magic.
Ahh... how I wish I am on JB hboot then I can test a lot of things
ckpv5 said:
Which ROM ?
As mentioned before, you need a ROM with a properly installed busybox, root and init.d support.
See Part 1 : http://forum.xda-developers.com/showpost.php?p=40359126&postcount=250
See Part 2 & 3 : http://forum.xda-developers.com/showpost.php?p=40359148&postcount=251
Click to expand...
Click to collapse
Yes,on your deodex rom
I`ve updated the complete guide by changing the way you have to do these things and making a Video out of it. Thanks [NUT] .
Files:
http://forum.xda-developers.com/showthread.php?t=1538053...
http://nut.xperia-files.com/
Steps:
Enable DEV. Options and USB-Debugging, PC Companion must be installed AND CLOSED.
Download SuperSU and place it into your internal storage
Download ZU-lockeddualrecovery2.7.154 INSTALLER here, extract it and run Installer.bat.
Use option 3 and follow the instructions
Device will reboot, make shure your device goes into Recovery by pressing vol. up.
In recovery flash SuperSU.zip
Reboot and you're done
Enjoy root
IMPORTANT INFORMATION:
Busybox is already preinstalled, don`t override it! The APK from the Play Store is useable but don''t tap on install or uninstall, this can result in trouble.
Point 1. You write about downloading TabZ-lockdualrec - why? You have been tested on C6833, it is ZU. Why not to download ZU-lockdualrec and use it? Recovery for ZU is broken or som? Version for TabZ and ZU are the same, have the same build number… confused
FRM300 said:
Point 1. You write about downloading TabZ-lockdualrec - why? You have been tested on C6833, it is ZU. Why not to download ZU-lockdualrec and use it? Recovery for ZU is broken or som? Version for TabZ and ZU are the same, have the same build number… confused
Click to expand...
Click to collapse
this should also work on non C6833 Z Ultras. The. point is i only have the C6833 to test it and the tabz one doesnt need root to work while phils recovery also works for the Z Ultra.
so the TabZ Recovery Installer gives you only a temporary root on 4.4.4 and installs the recovery, which means after reboot the Root is gone (enugh for installing Recovery). so you need to Root it again permamently via the easy Root tool after rebooting and install SuperSU directly after it via Recovery, so that not every app can have root Acess whithout asking you.
using this order all works perfectly.
update to 4.4.4
enable usb debugging
run easyroot bat
reboot
install supersu from play (and update binary when prompted)
run ZU Dual recovery installer bat (from same @[NUT] dl page)
done.. easyroot and supersu (via play) before recovery is a neater option and then no supersu flash is required (plus you have supersu so can grant adb shell access when asked during the recovery flash). You then choose method 1 instead of 3 when flashing recovery ("already rooted with supersu" option instead of the "about to root with towelroot" option).
cheers..
iBuzman said:
using this order all works perfectly.
update to 4.4.4
enable usb debugging
run easyroot bat
reboot
install supersu from play (and update binary when prompted)
run ZU Dual recovery installer bat (from same @[NUT] dl page)
done.. easyroot and supersu (via play) before recovery is a neater option and then no supersu flash is required (plus you have supersu so can grant adb shell access when asked during the recovery flash). You then choose method 1 instead of 3 when flashing recovery ("already rooted with supersu" option instead of the "about to root with towelroot" option).
cheers..
Click to expand...
Click to collapse
Or you install XZDR with option 3 in the installer menu and have @Chainfire's latest SuperSU flashable ready on your sdcard/internal storage before you do. Then you can flash it the instant you enter recovery for the first time and be done with it
[NUT] said:
Or you install XZDR with option 3 in the installer menu and have @Chainfire's latest SuperSU flashable ready on your sdcard/internal storage before you do. Then you can flash it the instant you enter recovery for the first time and be done with it
Click to expand...
Click to collapse
agreed, tested it right now. i`ll change my post, ty.
changes done:
-removed old guide
-completly changed the steps for rooting (old one was working, but this one includes recoverys that are made for ZU)
-new steps are now described in a Video
Supersu 2.01 from market don't update su binary, after dual recovery I prefer flash the supersu update zip from recovery
@Lightbird I see there is a ZU-lockeddualrecovery2.7.141-BETA.installer.zip. Is this newer and should I use it instead of 2.7.128 ?
adfurgerson said:
@Lightbird I see there is a ZU-lockeddualrecovery2.7.141-BETA.installer.zip. Is this newer and should I use it instead of 2.7.128 ?
Click to expand...
Click to collapse
you can try it, the .132 stucked in Towelroot, thats why you should use .128 instead. However if this one stucks in Towelroot, too and you want to have the newest Version you simply can flash the flashable.zip version after rooting whith the .128.
Lightbird said:
you can try it, the .132 stucked in Towelroot, thats why you should use .128 instead. However if this one stucks in Towelroot, too and you want to have the newest Version you simply can flash the flashable.zip version
Click to expand...
Click to collapse
@Lightbird just an update, I have a c6806 and on .128 it said unsupported when selecting make it rain. It worked fine with .141 though.
adfurgerson said:
@Lightbird just an update, I have a c6806 and on .128 it said unsupported when selecting make it rain. It worked fine with .141 though.
Click to expand...
Click to collapse
thanks for the reply
@[NUT] is working on a new dual recovery version, 141 is missing philz. 132 is currently my preferred version https://docs.google.com/file/d/0B0uD0ZLDjONjZ0dKck00OUdBdWM/edit?usp=docslist_api
Please help me
Hello, I tryed to root my xperia z ultra with the tutorial maked by lightbird and towelroot tells me : your device is not already supported.
Please help me really want to root my ZU!:crying:
Salutations
dual recovery updated to 142 http://forum.xda-developers.com/showthread.php?p=53935287
Lightbird said:
I`ve updated the complete guide by changing the way you have to do these things and making a Video out of it. Thanks [NUT] .
Files:
http://forum.xda-developers.com/showthread.php?t=1538053...
http://nut.xperia-files.com/
Steps:
Enable DEV. Options and USB-Debugging
Download SuperSU and place it into your internal storage
Download ZU-lockeddualrecovery2.7.128 INSTALLER, extract it and run Installer.bat
Use option 3 and follow the instructions
Device will reboot, make shure your device goes into Recovery by pressing vol. up.
In recovery flash SuperSU.zip
Reboot and you're done
Enjoy root
Click to expand...
Click to collapse
spent 10days to root and flash recovey ,your illustration helped ,cheers
I cant run install bat file. Please see below error message. Did i.missed something?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks in advance!
zaxharu said:
I cant run install bat file. Please see below error message. Did i.missed something?
Thanks in advance!
Click to expand...
Click to collapse
This message appears if you didn`t extract the files bevore using the .bat file ^^. Try again after extracting the Files in a seperate folder :good:.
If this doesn`t work try to run this as an Administrator (rightklick - run as Admin) (maybe your permission settings block the script loading other files). If you cant run it directly run cmd as admin and navigate to it:
Cd.. = directory up
Cd (folder) = navigate into (folder)
Dir = shows the folders and files
ZU-lockeddualrecovery2.7.145-BETA.installer.zip
successed
Confirmed that .145 is working, no bugs detected.
Changes to Guide done:
Upgraded Version to .145