Related
So, I've gotten my SGS2 today and went ahead to root it. Flashed CF-Root matching my current version (KE7 PDA/KE4 baseband). I used the S2Root app posted here on the forum to get root and flashed a stock kernel back.
In either of these stages, I couldn't get ADB to run as root, needed for a modification i'm trying to do (can't write to /system/framework otherwise).
Is there a known way to get ADB to run as root?
(The issue at hand - /default.prop contains ro.secure=1 and ro.debuggable=0 - And i can't edit this file in order for it to persist after reboot)
even in CWM i can't get ADB to run as root and thus cannot copy files to /system/framework even though /system is mounted as r/w.
Thanks for the help.
ransagy said:
So, I've gotten my SGS2 today and went ahead to root it. Flashed CF-Root matching my current version (KE7 PDA/KE4 baseband). I used the S2Root app posted here on the forum to get root and flashed a stock kernel back.
In either of these stages, I couldn't get ADB to run as root, needed for a modification i'm trying to do (can't write to /system/framework otherwise).
Is there a known way to get ADB to run as root?
(The issue at hand - /default.prop contains ro.secure=1 and ro.debuggable=0 - And i can't edit this file in order for it to persist after reboot)
even in CWM i can't get ADB to run as root and thus cannot copy files to /system/framework even though /system is mounted as r/w.
Thanks for the help.
Click to expand...
Click to collapse
Try this:
adb shell mkdir /sdcard/temp/
adb push fileToPush /sdcard/temp/
adb shell
$ su
# cp /sdcard/temp/ /system/path/to/push/to/
ADB doesn't run as root, as it's not safe to, as you can bypass superuser security in a rogue app otherwise
I'll try it ASAP, Thanks.
Isn't there a way to edit /default.prop though?
I'd prefer to have adb run in root at the very least while running this mod, and then restore it.
the mod currently patches framework.jar/libwebcore.so for RTL issues, and relays on scripted access to adb and r/w access to /system.
I ended up discovering that i need a different ROM either way since stock is odexed.
I'll try making my own ROM based on stock with deodexed files and make the fix before hand.
can someone explain how to use bypasslkm in further detail. i looked through multiple threads but im stilll not getting the handle on it,
Open your terminal emulator on your phone (download one from Google play if you don't have one) open the terminal and type the following commands (Pressing enter to execute each one)
su (sands for switch user, used alone will switch you to the "root" user. Equilivent to Admin in windows)
cd /data/local/temp (cd - change directory, followed by the complete folder path you want to navigate to)
chmod 755 bypasslkm (not going to get too in depth with this one because I could go on for a while with it but "chmod 755" changes the permissions to read, write, execute for the root user and read/execute for everyone else)
. /bypasslkm (. / tells the system to look in the current directory and, in this case, execute bypasslkm)
Hope this helps clear some things up for you!
Sent from my SCH-I545 using XDA Premium HD app
sfgrimes said:
Open your terminal emulator on your phone (download one from Google play if you don't have one) open the terminal and type the following commands (Pressing enter to execute each one)
su (sands for switch user, used alone will switch you to the "root" user. Equilivent to Admin in windows)
cd /data/local/temp (cd - change directory, followed by the complete folder path you want to navigate to)
chmod 755 bypasslkm (not going to get too in depth with this one because I could go on for a while with it but "chmod 755" changes the permissions to read, write, execute for the root user and read/execute for everyone else)
. /bypasslkm (. / tells the system to look in the current directory and, in this case, execute bypasslkm)
Hope this helps clear some things up for you!
Sent from my SCH-I545 using XDA Premium HD
I keep getting a message saying that there is no such directory after trying to execute "chmod 755 bypasslkm"
Click to expand...
Click to collapse
Deleted
Sent from my SCH-I545 using Tapatalk
JTSDeveloper said:
I keep getting a message saying that there is no such directory after trying to execute "chmod 755 bypasslkm"
Click to expand...
Click to collapse
I had the same issue. Here is the binary from Surges dropbox https://www.dropbox.com/s/9rdz9ff6x5foech/bypasslkm
Make sure you copy it to the right directory and follow all the commands.
Sent from my SCH-I545 using XDA Premium HD app
To add to the above post, after downloading that just execute this in terminal
Code:
su
mount -o remount,rw /system
find . -name "bypasslkm" -exec cp {} /data/local/tmp \;
find /data/local/tmp -name "bypasslkm" -type f -exec chmod 755 {} \;
./data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
exit
Surge1223 said:
To add to the above post, after downloading that just execute this in terminal
Code:
su
mount -o remount,rw /system
find . -name "bypasslkm" -exec cp {} /data/local/tmp \;
find /data/local/tmp -name "bypasslkm" -type f -exec chmod 755 {} \;
./data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
exit
Click to expand...
Click to collapse
I got the following error trying to execute after downloading the bypasslkm file and doing what you said
JTSDeveloper said:
I got the following error trying to execute after downloading the bypasslkm file and doing what you said
Click to expand...
Click to collapse
Thats not an error. If you had bypasslkm anywhere on your phone, it should now be in /data/local/tmp with the right permissions and should have executed. Make sure you downloaded the bypasslkm binary linked above
Edit: Also just copy and paste the whole script to make things easier
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
Thats not an error. If you had bypasslkm anywhere on your phone, it should now be in /data/local/tmp with the right permissions and should have executed. Make sure you downloaded the bypasslkm binary linked above
Edit: Also just copy and paste the whole script to make things easier
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's still not working. Any ideas? Should I move it directly into /data/local/tmp
Surge1223 said:
Thats not an error. If you had bypasslkm anywhere on your phone, it should now be in /data/local/tmp with the right permissions and should have executed. Make sure you downloaded the bypasslkm binary linked above
Edit: Also just copy and paste the whole script to make things easier
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I downloaded the binary from above and pasted it directly in data/local/tmp then tried it and it still didn't work :/ what should the permissions on the file be? I'm a noob at this stuff
JTSDeveloper said:
I downloaded the binary from above and pasted it directly in data/local/tmp then tried it and it still didn't work :/ what should the permissions on the file be? I'm a noob at this stuff
Click to expand...
Click to collapse
The permissions should be 755, as Surge said.
If you KNOW it's in /data/local/tmp, then do this in a terminal emulator window:
Code:
su
mount -o remount,rw /system
chmod 755 /data/local/tmp/bypasslkm
/data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
mount -o remount,ro /system
exit
If this doesn't work, DO NOT post just "it didn't work". Say what you did, why you think it failed. Capture the output and reply here with it.
Solution to the 755 bypasslkm issue!!!!!
k1mu said:
The permissions should be 755, as Surge said.
If you KNOW it's in /data/local/tmp, then do this in a terminal emulator window:
Code:
su
mount -o remount,rw /system
chmod 755 /data/local/tmp/bypasslkm
/data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
mount -o remount,ro /system
exit
If this doesn't work, DO NOT post just "it didn't work". Say what you did, why you think it failed. Capture the output and reply here with it.
Click to expand...
Click to collapse
I figured it out! Here is exactly what I did:
after downloading the bypasslkm.bin from the dropbox link, I used ES File Explorer (WITH ROOT ENABLED) to move the bypasslkm file to directly to the data/local/tmp location. NOTE: there are a few places marked "data" and "local" on the phone, so when you open a "data" folder, make sure you find the path in the right order [ i.e. first data, then local, and then tmp]
Using a ROOT FILE EXPLORER app (because ES doesn't have what you will need) go to the bypasslkm file, long press, and select permissions. It will display with permissions are currently set. At the bottom, it SHOULD display the total sum of the permissions selected. Basically, that means by selecting the right boxes, you can change the permissions to 755 !
7 5 5
user group world
r+w+x r+x r+x
4+2+1 4+0+1 4+0+1 = 755
These setting will give you the 755 that you need to pull this off .
When you have the permissions changed to 755, the last step was actually very easy. But if you want to play it safe, then I will tell you the root file browser I specifically used to do the last step.
I used the app Root Browser version 2.2.3 ( i literally googled for any generic root file explorer and this came up )
ok, so when you have the permissions changed, long press on the bypasslkm file.
select "Open With" and then select the option "Open As.."
At the bottom of the options is "script file" select it.
after doing so, select the option "Execute" and... Voila! I immediately regained my WIFI !!!!! \>w</
I hope this guide helped everyone out. I tried to be as specific as possible.
EinGlo said:
I figured it out! Here is exactly what I did:
after downloading the bypasslkm.bin from the dropbox link, I used ES File Explorer (WITH ROOT ENABLED) to move the bypasslkm file to directly to the data/local/tmp location. NOTE: there are a few places marked "data" and "local" on the phone, so when you open a "data" folder, make sure you find the path in the right order [ i.e. first data, then local, and then tmp]
Using a ROOT FILE EXPLORER app (because ES doesn't have what you will need) go to the bypasslkm file, long press, and select permissions. It will display with permissions are currently set. At the bottom, it SHOULD display the total sum of the permissions selected. Basically, that means by selecting the right boxes, you can change the permissions to 755 !
7 5 5
user group world
r+w+x r+x r+x
4+2+1 4+0+1 4+0+1 = 755
These setting will give you the 755 that you need to pull this off .
When you have the permissions changed to 755, the last step was actually very easy. But if you want to play it safe, then I will tell you the root file browser I specifically used to do the last step.
I used the app Root Browser version 2.2.3 ( i literally googled for any generic root file explorer and this came up )
ok, so when you have the permissions changed, long press on the bypasslkm file.
select "Open With" and then select the option "Open As.."
At the bottom of the options is "script file" select it.
after doing so, select the option "Execute" and... Voila! I immediately regained my WIFI !!!!! \>w</
I hope this guide helped everyone out. I tried to be as specific as possible.
Click to expand...
Click to collapse
worked perfectly and all my confusion is now gone thank you.
Fix works but new issue
JTSDeveloper said:
worked perfectly and all my confusion is now gone thank you.
Click to expand...
Click to collapse
Thanks for the support. Glad I could help. Has your WIFI remained on, though? The solution I posted works, but only for a short amount of time. rebooting the system undoes the work I did and I have to go back into the root browser and execute the file all over again to get wifi.
Can Surge or someone else offer any expertise?
with the permissions changed properly, I tried executing the code, and still not working.
I have safestrap enabled, and I have sound restored. I am currently on android 4.3 from the downgrade provided by Surge. Its rooted.
If I were to upgrade to the rooted version of NC5, would that help fix the wifi issue, or would it carry over?
Any input going forward is appreciated!
EinGlo said:
Thanks for the support. Glad I could help. Has your WIFI remained on, though? The solution I posted works, but only for a short amount of time. rebooting the system undoes the work I did and I have to go back into the root browser and execute the file all over again to get wifi.
Can Surge or someone else offer any expertise?
with the permissions changed properly, I tried executing the code, and still not working.
I have safestrap enabled, and I have sound restored. I am currently on android 4.3 from the downgrade provided by Surge. Its rooted.
If I were to upgrade to the rooted version of NC5, would that help fix the wifi issue, or would it carry over?
Any input going forward is appreciated!
Click to expand...
Click to collapse
It is possible to automate this.
Create a file with the following contents:
Code:
#!/system/bin/sh
/data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
exit
Save this file as /system/etc/install-recovery-2.sh.
Make sure that the bypasslkm file is in /data/local/tmp.
Reboot, and you should now have WiFi again.
[Note: this assumes SuperSU has it's custom copy of /system/etc/install-recovery.sh in place. If that's not there, it's still possible to edit /init.rc to add a stanza to run this command.]
Issue with auto-running my solution
k1mu said:
It is possible to automate this.
Create a file with the following contents:
Code:
#!/system/bin/sh
/data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
exit
Save this file as /system/etc/install-recovery-2.sh.
Make sure that the bypasslkm file is in /data/local/tmp.
Reboot, and you should now have WiFi again.
[Note: this assumes SuperSU has it's custom copy of /system/etc/install-recovery.sh in place. If that's not there, it's still possible to edit /init.rc to add a stanza to run this command.]
Click to expand...
Click to collapse
I do NOT have supersu's install recovery 2 file in the location you said. I only have the regular install recovery file.
What I should I do? Could I create the file in laptops termial?
The first line of code gave me the error "file not found"
update
EinGlo said:
I do NOT have supersu's install recovery 2 file in the location you said. I only have the regular install recovery file.
What I should I do? Could I create the file in laptops termial?
The first line of code gave me the error "file not found"
Click to expand...
Click to collapse
I tried again.
Ok, so I figured out the coding a little bit. Im not used to this, so forgive my ignorance.
I did the code as u typed it. BUT I made a change. Because I kept getting the "file not found " error. I added ".bin" to the end of the bypasslkm code line. It generated a real response. I felt relieved. I went ahead and typed the last line of code.
THEN I was told the file already exists... I have attached a picture of what I got in android Terminal
EinGlo said:
I do NOT have supersu's install recovery 2 file in the location you said. I only have the regular install recovery file.
What I should I do? Could I create the file in laptops termial?
The first line of code gave me the error "file not found"
Click to expand...
Click to collapse
You should have /system/etc/install-recovery.sh
It will run /system/etc/install-recovery-2.sh if it exists. What I would do is to create the file on your PC, put it onto your SDcard on the PC, then use Root Explorer to put it into place.
The "file exists" error is because you already have the WiFi module installed. That won't happen when this script runs at boot.
Question
k1mu said:
You should have /system/etc/install-recovery.sh
It will run /system/etc/install-recovery-2.sh if it exists. What I would do is to create the file on your PC, put it onto your SDcard on the PC, then use Root Explorer to put it into place.
The "file exists" error is because you already have the WiFi module installed. That won't happen when this script runs at boot.
Click to expand...
Click to collapse
Ok. I'll try that tonight.
But I have a few questions
Im basically trying to autostart the wifi module when the phone boots up right? Are there any apps that can accomplish this specific task?
Also about the downgrade in general. Did anyone get their SD card permissions restored after downgrading? I donwgraded to 4.3, rooted the phone, and somehow I STILL cant move apps to the sd card! Im beginning to suspect that thr issue may be with the card itself, which can be fixed with formatting the sd card. But has anyone had any problems with moving apps to the sd card?
Finally, the bug question concerning the wifi issue.
Is this probkem specific only to those with the downgrade? If so, should upgrading to Surge's rooted kitkat (with sd card permissions and tethered enabled) resolve the wifi issue?
I also noticed that I had wifi access when the phone had no sound. Only when I flashed the Non-HLOS bin file did I encounter this wifi issue.
Thanks for the feedback so far, I just need to understand whrre to go from here
EinGlo said:
Ok. I'll try that tonight.
But I have a few questions
Im basically trying to autostart the wifi module when the phone boots up right? Are there any apps that can accomplish this specific task?
Click to expand...
Click to collapse
I'm sure there are programs that can be set up to run scripts as root during boot; However, that's complicated since you want this to run while the phone is booting, before there's any opportunity to allow SuperSU to ask for permission.
EinGlo said:
Also about the downgrade in general. Did anyone get their SD card permissions restored after downgrading? I donwgraded to 4.3, rooted the phone, and somehow I STILL cant move apps to the sd card! Im beginning to suspect that thr issue may be with the card itself, which can be fixed with formatting the sd card. But has anyone had any problems with moving apps to the sd card?
Click to expand...
Click to collapse
That's a problem that's fixed by an edit to /system/etc/permissions/platform.xml, adding a stanza that permits external storage write access.
EinGlo said:
Finally, the bug question concerning the wifi issue.
Is this probkem specific only to those with the downgrade? If so, should upgrading to Surge's rooted kitkat (with sd card permissions and tethered enabled) resolve the wifi issue?
I also noticed that I had wifi access when the phone had no sound. Only when I flashed the Non-HLOS bin file did I encounter this wifi issue.
Thanks for the feedback so far, I just need to understand whrre to go from here
Click to expand...
Click to collapse
The need to run the "bypasslkm" program is because of the downgrade. If you go to a clean rooted Kit Kat ROM, it shouldn't have any issues with WiFi being enabled. That may be the easiest way to fix this.
Since this information was buried in the other thread I am posting it here for visibility:
This will work only on CWM flashable zip stock (because you need CWM to flash the zip, obviously):
- Flash this first:
http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip
- Then flash this:
http://d-h.st/X1A
Click to expand...
Click to collapse
Now, people are wondering if it's possible to root from OTA/kdz update (like we originally rooted stock JB). In theory it should be. Basically what I did with this root fix is I've added one line to one of init scripts (which all run with root permissions). This line is starting the install-recovery.sh script (which is provided with SuperSU zip package). With KK it's not enough to just drop su binary to /system/xbin - you also have to start daemon (as root). Whatever rooting method you are trying to use has to add a line to one of startup scripts which starts the SuperSU script. If one such method is found please post here, I will also update the OP.
Varcain said:
Since this information was buried in the other thread I am posting it here for visibility:
Now, people are wondering if it's possible to root from OTA/kdz update (like we originally rooted stock JB). In theory it should be. Basically what I did with this root fix is I've added one line to one of init scripts (which all run with root permissions). This line is starting the install-recovery.sh script (which is provided with SuperSU zip package). With KK it's not enough to just drop su binary to /system/xbin - you also have to start daemon (as root). Whatever rooting method you are trying to use has to add a line to one of startup scripts which starts the SuperSU script. If one such method is found please post here, I will also update the OP.
Click to expand...
Click to collapse
Is there any way I can root the phone if i already upgraded to KitKat, but I don't have CWM ?
I'm guessing that RootKeeper does not work?
help
dSERiES said:
I'm guessing that RootKeeper does not work?
Click to expand...
Click to collapse
:cyclops:
whether we should try this guide with other sd card
[GUIDE] [ROOT] Root your LG Mini L40/L70/L90/G2
"update.zip"
looks positive
or try a Varcain "kk_root.zip"
consider and report
or for us, and there are many of us, the OTA upgrade, no root and CWM
pozz
I want to know if this method will work to me( I am using 4.4.2 OpenEu v20b.)
Изпратено от моят LG-D605 използвайки XDA-FORUM, благодарение на appyet.com
hepy
or loss from the root 4.4.2.sa ota update
working with this method, at least for me
I just installed TowelRoot V 2
and without a reboot got root
Then I installed the Super 1.9.4 (any little problems)
and got root .....
very happy
http://forum.xda-developers.com/showthread.php?t=2784416
[ROOT][EXPLOIT][APK]Root Your Phone[LG and other supported]
Originally Posted by giperborey View Post
So. I got it Thanks to all!
1) Download and install TowelRoot.
2) Varcain's patch
Add string "/system/etc/install-recovery.sh &" to the end of /system/etc/init.engdo.post_boot.sh
or just simply replace it by Varcain edited version
this file.
It's neccessary to get root after each boot.
NOTE!!! YOU MUST SAVE ORIGINAL PERMISSIONS TO THAT FILE (rw-, r--, r--)
3) Delete last string "/system/etc/install-recovery-2.sh" from the /system/etc/install-recovery.sh
NOTE!!! YOU MUST SAVE ORIGINAL PERMISSIONS TO THAT FILE (rwx, r-x, r-x)
Congratulation! You get rooted phone
IMPORTANT NOTE:
When I did it the first time, I tried to install SuperSU 2.0 from the Market. He did not want to upgrade properly. Finally I got a soft-broken phone and repaired it by kdz firmware flasher. I'm not sure that the reason of soft-brick was SuperSU, but without it root works fine.
since I'm not a programmer, I would ask Varcain and opportunity that we end up CWM,
so that we enjoy the OTA UPDATE CM11, PA Rom 4.4.3 .......
Get the conversation
skakavac65 said:
or loss from the root 4.4.2.sa ota update
working with this method, at least for me
I just installed TowelRoot V 2
and without a reboot got root
Then I installed the Super 1.9.4 (any little problems)
and got root .....
very happy
http://forum.xda-developers.com/showthread.php?t=2784416
[ROOT][EXPLOIT][APK]Root Your Phone[LG and other supported]
Originally Posted by giperborey View Post
So. I got it Thanks to all!
1) Download and install TowelRoot.
2) Varcain's patch
Add string "/system/etc/install-recovery.sh &" to the end of /system/etc/init.engdo.post_boot.sh
or just simply replace it by Varcain edited version
this file.
It's neccessary to get root after each boot.
NOTE!!! YOU MUST SAVE ORIGINAL PERMISSIONS TO THAT FILE (rw-, r--, r--)
3) Delete last string "/system/etc/install-recovery-2.sh" from the /system/etc/install-recovery.sh
NOTE!!! YOU MUST SAVE ORIGINAL PERMISSIONS TO THAT FILE (rwx, r-x, r-x)
Congratulation! You get rooted phone
IMPORTANT NOTE:
When I did it the first time, I tried to install SuperSU 2.0 from the Market. He did not want to upgrade properly. Finally I got a soft-broken phone and repaired it by kdz firmware flasher. I'm not sure that the reason of soft-brick was SuperSU, but without it root works fine.
since I'm not a programmer, I would ask Varcain and opportunity that we end up CWM,
so that we enjoy the OTA UPDATE CM11, PA Rom 4.4.3 .......
Get the conversation
Click to expand...
Click to collapse
But this is only temporary root. After restart of phone you must run this root again
help
Varcain said:
Since this information was buried in the other thread I am posting it here for visibility:
Now, people are wondering if it's possible to root from OTA/kdz update (like we originally rooted stock JB). In theory it should be. Basically what I did with this root fix is I've added one line to one of init scripts (which all run with root permissions). This line is starting the install-recovery.sh script (which is provided with SuperSU zip package). With KK it's not enough to just drop su binary to /system/xbin - you also have to start daemon (as root). Whatever rooting method you are trying to use has to add a line to one of startup scripts which starts the SuperSU script. If one such method is found please post here, I will also update the OP.
Click to expand...
Click to collapse
Hello.Thanks for the tutorial.I cant put the recovery mode as i dont know how to do it exactly.I know that i have to press the power button and volume up.If you help me i will be grateful.Thanks
Hi Varcain
Please could you update "varcain_rootfix.zip" for SuperSU v 2.01?
With the current "rootfix" does not work, and still wants to install SU binary.
Thanks for your work.
Sorry bad English.
Root Stock Recovery 4.4.2
Hello people,
After many attempts,
it seems that these instructions
definitely the easiest to root lg d 605, the OTA upgrade to 4.4.2.
A big thank you lioko27
Android.com.pl
Root Stock Recovery 4.4.2
Welcome.
Modification is used to zrotowania v20 firmware preloaded or OTA update for the PC (KDZ, Software LG)
This method does not allow upload custom recowery Cwm-fault is either with the powers or the installation file Cwm-work in progress
needs
* soft v20
* stock recovery
installation
charge applications:
- Towelroot (gives you temporary root)
https://towelroot.com/
Rom Toolbox Lite (or other manager with root privileges)
https://play.google.com/store/apps/d....toolbox&hl=pl
w / the apps you install on your phone, run Towelroot and click on the banner "make it ra 1 n"
charge pack zip
https://drive.google.com/file/d/0B1t...it?usp=sharing
move it through the USB cable or a memory card reader
run rom toolbox, click the root browser and copy the root file location v2.zip dp "cache" on your phone,
we leave the rot browser to the main menu click "scripter"-reboot recovery-run script-do
the phone will start in recovery, select apply update from the cache and select the copied package,
after the installation is completed, restart the phone and look forward to root.
The procedure is simple and Root after restart everything is OK
Now is already high time for CWM ....
Help Varcain....
and other developers ....
When I see what kind of support are second LG devices,
I was angry a lot.
Just look at what support has LG 9 and all will be clear.
The other devices that do not speak ....: (
Sorry for my english, going over translater,
greeting
I hope CWM soon ...: Kiklop:
hey I updated to v2.01 supersu
link
http://forum.android.com.pl/f1211/root-stock-recovery-4-4-2-a-439890/
I have seen a way for cwm to kitkat in a polish forum.
Instructions:
You must have adb.
1 Extract the zip on PC
2 Connect your phone to a PC with USB debugging enabled
3 Open the folder and press "shift" and the right mouse button
4 Select "Open command window here"
Follow the commands now:1 adb push aboot.img / data / local / tmp
2 adb shell
3 su
4 dd if = / data / local / tmp / aboot.img of = / dev / block / platform / msm_sdcc.1 / by-name / aboot
5 exit
6 exit
7 adb push loki_flash / data / local / tmp
8 adb push recovery.img / data / local / tmp
9 adb shell
10 su
11 cd / data / local / tmp
12 chmod 777 loki_flash
13 ./loki_flash recovery recovery.img
14 reboot recovery
After your phone will reboot in cwm mode.When i did it rebooted automatically with an error:HW reset was detected.Dont worry just press the turn on button for 20 sec and the phone will reboot without giving that error again.
Big thanks to szymel00 a user of a polish android forum.
The link for the zip: (http://d-h.st/2kk)
Tested without any virus.
I didn't have to flash anything
I used the app KingRoot(not in appstore). It just rooted and it was just done. Later that day it rooted jelly bean version as well.
PS! You have to allow unknown sources when running apk-s from outside play store.
Well, I "had" an HDX at 14.3.2.6. I had the hdxposed module and I renamed the otacerts.zip to otacerts.bak. When the downgrade method came out, I named the otacerts.bak to otacerts.zip and I removed and uninstalled the HDXposed module. Then I changed the build prop to match the guides, and tried to update. I keep on getting an update fail, despite multiple reboots. I have checked to make sure that the .bin is in the root of storage, but nothing is happening. Please help me.
I put a pause in the batch, and manually copied the files to the right location, and I believe what happened is I did the build.prop and one more thing, then I accidently rebooted and its a brick.
XxD34THxX said:
Well, I "had" an HDX at 14.3.2.6. I had the hdxposed module and I renamed the otacerts.zip to otacerts.bak. When the downgrade method came out, I named the otacerts.bak to otacerts.zip and I removed and uninstalled the HDXposed module. Then I changed the build prop to match the guides, and tried to update. I keep on getting an update fail, despite multiple reboots. I have checked to make sure that the .bin is in the root of storage, but nothing is happening. Please help me.
Click to expand...
Click to collapse
Please clarify what did you plan to achieve with this and with what you need help exactly?
Is your kindle still usable (rom booting, but freeze at some point and is unusable or rom booting correctly, only update is failing)?
What recovery are you using (stock, safestrap or TWRP 2.8.x.x) and can you access it?
Your firmware was stock + rooted or some custom rom?
Please link the "guides" you worked with and if possible mark the point in which guide recommend something, but your kindle refuse(d) to continue?
XxD34THxX said:
Well, I "had" an HDX at 14.3.2.6. I had the hdxposed module and I renamed the otacerts.zip to otacerts.bak. When the downgrade method came out, I named the otacerts.bak to otacerts.zip and I removed and uninstalled the HDXposed module. Then I changed the build prop to match the guides, and tried to update. I keep on getting an update fail, despite multiple reboots. I have checked to make sure that the .bin is in the root of storage, but nothing is happening. Please help me.
Click to expand...
Click to collapse
Not sure why you needed to mess with build prop when starting from 3.2.6. According to this guide (which I have successfully used several times) it's simply a matter of dropping the renamed image in root, rebooting and allowing the 'update' to be processed naturally. What am I missing?
You're following the wrong guide...Those instructions are only for x.3.2.4 and below.
See http://forum.xda-developers.com/showpost.php?p=55759790&postcount=204.
Well.. If this is not the case..
Did you set the permissions on the build.prob? I forgot it last time and my kindle was bricked. And Warrenty was out of time. But I got a new With 4.5.2 -.-'
@Davey126 I used that guide and it says to edit build.prop
@EncryptedCurse Uhmm, chrome and firefox both don't like the rollback for my HDX... Also, do I run the bat on the kindle or on my PC? And what folder exactly...
@oOFrAnzOo Permissions were all r/w
@jeryll Only update is failing. Everything works fine. Firmware and everything is stock + towelroot and Xposed. No safestrap
you need to read carefully...
edit build.prop is only up to 3.2.4...
you way to do is the mentioned post from encryptedcurse...
before that, edit the build.prop back to what it was before...
you need to extract it first on pc, and copy the update 3.1.0bin to that folder, and run the .bat from there....
after that copy the 3.1.0 to kindle (mentioned in the how to)
if you can't get the rollback.zip, disable your antivirus for a minute and use internet explorer...
(if remeber right, there are two download buttons, the blue one was the right one...)
XxD34THxX said:
@Davey126 I used that guide and it says to edit build.prop
Click to expand...
Click to collapse
I am afraid not. You need to read more carefully. The first section (where it mentions modifying build.prop) is for versions up to 3.2.4. The section further down is for 3.2.5-3.2.6. Look for the bold red highlighted text delineating sections.
(yes, it could be more clear. Maybe blinking red. That said, volunteers post this information; I am grateful for their contributions even if it takes a couple readings to fully digest)
Now if I can start IE...
The HDX has to be in fastboot mode correct?
wait, The kindle DOES NOT need to be connected to the PC when running the batch right? Also, is the reboot for the HDX or PC?
XxD34THxX said:
wait, The kindle DOES NOT need to be connected to the PC when running the batch right? Also, is the reboot for the HDX or PC?
Click to expand...
Click to collapse
The batch file simply issues a bunch of adb commands on your behalf. So yeah, it needs to be connected. Reboot is for HDX. Make sure you understand what you are doing; you can easily 'damage' or permanently brick your device with a simple mistake.
---------- Post added at 11:35 AM ---------- Previous post was at 11:33 AM ----------
XxD34THxX said:
The HDX has to be in fastboot mode correct?
Click to expand...
Click to collapse
No...where does it say that?
Davey126 said:
The batch file simply issues a bunch of adb commands on your behalf. So yeah, it needs to be connected. Reboot is for HDX. Make sure you understand what you are doing; you can easily 'damage' or permanently brick your device with a simple mistake.
---------- Post added at 11:35 AM ---------- Previous post was at 11:33 AM ----------
No...where does it say that?
Click to expand...
Click to collapse
OK, so I installed ADB drivers... going to try this now. I'm still used to safestrap, which needed little work
Alright, I ran the batch, the .bin was in the same folder, Kindle was connected, ADB enabled in settings. I rebooted, moved .bin to the root of storage, and I get the same "Last Update Failed" Error again...
XxD34THxX said:
OK, so I installed ADB drivers... going to try this now. I'm still used to safestrap, which needed little work
Alright, I ran the batch, the .bin was in the same folder, Kindle was connected, ADB enabled in settings. I rebooted, moved .bin to the root of storage, and I get the same "Last Update Failed" Error again...
Click to expand...
Click to collapse
Did you mess with the otaupdate apk's from amazon to previously blick ota updates? That is the error you get when you try to update & it can't launch the updater app. The same error you get when disabling the OTA's & then trying to search for updates.
You may need to rename the OTA apk's ***AFTER DISABLING WIFI*** & then trying to start the process again. I think it will require a reboot to bring those services on line again, as well.
Ermmm.. The OTAcerts is a .zip... Is it supposed to be a .apk?
XxD34THxX said:
Ermmm.. The OTAcerts is a .zip... Is it supposed to be a .apk?
Click to expand...
Click to collapse
otacerts.zip is correct.
Davey126 said:
otacerts.zip is correct.
Click to expand...
Click to collapse
well, it's a .zip and located in /System/etc/Security. HDXposed is off, and I did several reboots to make sure. Then I did the batch...
XxD34THxX said:
well, it's a .zip and located in /System/etc/Security. HDXposed is off, and I did several reboots to make sure. Then I did the batch...
Click to expand...
Click to collapse
Not sure what to say. Seems something is still amiss and needs to be tracked down. Suggest you go through previous posts and validate everything. I am sure you have already done this but something must be off. Frustrating for sure...we've all been through it at some point.
Perhaps someone else has a better idea.
XxD34THxX said:
well, it's a .zip and located in /System/etc/Security. HDXposed is off, and I did several reboots to make sure. Then I did the batch...
Click to expand...
Click to collapse
Try a factory reset from within the settings.
Code:
* USE IT AT YOUR OWN RESPONSIBILITY because rewrite recovery partition.
*
* This batch file works "kindle fire hdx 8.9" ONLY
* This is not tested.
*
* If do not want rollback, Close this window.
*
* IF you want to rollback,
* Put "update-kindle-14.3.1.0_user_310079820.bin" in SAME folder,
* Push Enter key 5 times
*
* If it is requested from super su, please allow superuser.
*
Press any key to continue . . .
Press any key to continue . . .
Press any key to continue . . .
Press any key to continue . . .
Press any key to continue . . .
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>7z.exe e update-kindle-14.3.1.0_user_310079820.bin "boot.img" "recovery/recovery-from-boot.p" "system/etc/recovery-resource.dat" "system/etc/security/otacerts.zip"
7-Zip 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Processing archive: update-kindle-14.3.1.0_user_310079820.bin
file boot.img
already exists. Overwrite with
boot.img?
(Y)es / (N)o / (A)lways / (S)kip all / A(u)to rename all / (Q)uit? a
Extracting boot.img
Extracting recovery\recovery-from-boot.p
Extracting system\etc\recovery-resource.dat
Extracting system\etc\security\otacerts.zip
Everything is Ok
Files: 4
Size: 8875856
Compressed: 833418977
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>adb shell mkdir /sdcard/recovery
mkdir failed for /sdcard/recovery, Permission denied
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>adb push build.prop /sdcard/recovery/build.prop
failed to copy 'build.prop' to '/sdcard/recovery/build.prop': Permission denied
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>adb push otacerts.zip /sdcard/recovery/otacerts.zip
failed to copy 'otacerts.zip' to '/sdcard/recovery/otacerts.zip': Permission denied
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>adb push boot.img /sdcard/recovery/boot.img
failed to copy 'boot.img' to '/sdcard/recovery/boot.img': Permission denied
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>adb push recovery-from-boot.p /sdcard/recovery/recovery-from-boot.p
failed to copy 'recovery-from-boot.p' to '/sdcard/recovery/recovery-from-boot.p': Permission denied
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>adb push recovery-resource.dat /sdcard/recovery/recovery-resource.dat
failed to copy 'recovery-resource.dat' to '/sdcard/recovery/recovery-resource.dat': Permission denied
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>adb push install.sh /sdcard/recovery/install.sh
failed to copy 'install.sh' to '/sdcard/recovery/install.sh': Permission denied
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>adb shell sh -v /sdcard/recovery/install.sh
sh: /sdcard/recovery/install.sh: Permission denied
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>pause
Press any key to continue . . .
That's the log for the batch... I added a pause at the end and a check for this. a crap ton of errors... Oh yes, I did a factory reset...
Hi,
what started as an Idea seems to be working now. For once i wanted a phone that has warranty for more than two weeks (or at least a chance for warranty).
DISCLAIMER:
Do all of this at your own risk. Even though we will not be flashing a custom recovery, technically the warranty is lost the moment you root your phone.
None of the Tools is actually written by me, i just tinkered a bit and came up with this tutorial.
1. You will need
- Galaxy A3 (mine was an A300FU but i guess every one that can be rooted without flashing should do) on Lollipop (5.0.2).
- Minimal ADB or some other software that brings debugging drivers and adb.
- KingRoot 4.60+
- SuperSu-ME (from play Store or an older version is also fine) or any other way to go from the Kinguser Root Management to SuperSU
- Deodexed apks matching you phone model
- Flashfire Beta
- Xposed Installer, I used 3.0alpha4
- Xposed bridge for Samsung lollipop I used xposed-v75-sdk21-arm-arter97-snapdragon_requestConcurrentGC
2. If something goes wrong:
- Odin and a stock LOLLIPOP ROM for your device!
This is Important: Since we dont have a custom recovery, whenever something goes wrong the only rescue is going back to a stock rom and thereby wiping. If everything works in the first go there will be no wipe.
3. Rooting
First we need to root. Thanks to KingRoot thats very easy and just a matter of waiting. Install KingRoot (has to be 4.60+ for Lollipop), Click try to Root, wait for it, done. Know we need to get rid of the KingRoot stuff again and install SuperSU (FlashFire does not support KingUser but SuperSU) thats what we need SuperSU-ME for. There Will be some Left overs since KingRoot converts itself to a system app, you can remove this with Titanium Backup or a ROM Toolbox of you choice.
4. Deodexing
Next step is gonna be Deodexing. This one is a little Tricky without a Custom Recovery. Flashing the Deodex using FlashFire will leave you stuck at the Boot Logo.
Unpack the Flashable Deodex zip. you#ll find a META-INF and a system folder. Copy the system folder (or rename it, doesnt matter) to your SDcard or the phone memory using USB. At this point you can also copy the two Xposed files (zip+apk). Next we need USB Debugging. Install the minimal ADB, browse to the install location and start "adb devices" once (this will start the daemon). Now take your phone, browse to settings / phone info and tap the build number like 10 times (this gives you developers options) now go to settings / developers options and enable USB debugging.
Connect you phone via USB. This hould bring up a dialog granting your PC permission to connect. Click Yes.
Connect to the phone and request root using
Code:
adb shell
su
Now turn on the phones screen there should be a root request, allow it.
Next is the following commands, assuming the location of the extracted system folder is /storage/extSdCard/deodex_system
Code:
mount -o rw,remount /system
rm -Rf /system/app
rm -Rf /system/priv-app
rm -Rf /system/framework
cp -R /storage/extSdCard/deodex_system/* /system
chown -R root:root /system/app
chown -R root:root /system/priv-app
chown -R root:root /system/framework
chmod -R 755 /system/app
chmod -R 755 /system/priv-app
chmod -R 755 /system/framework
rm -Rf /data/dalvik-cache/*
reboot
This will replace all system apks with the deodexed ones, sets the right owner and permissions, clears the dalvik cache and reboots. Booting is gonna take a while and then you're enjoying you're rooted, deodexed stock ROM without flashing anything so far. So now about installing Xposed.
Don't be to slow with thus step. Deleting the three folders will make the phone go crazy and at some point reboot, you should be done by then.
Edit: I did this on a second device now, for some reason the remount did not work. In this case try disabling SElinux (http://forum.xda-developers.com/devdb/project/dl/?id=12178) and then remount.
5. Xposed
Install the XposedInstaller apk file like any other app, no need to start it yet. Next install FlashFire and launch it (granting root access) now select the Option "OTA or ZIP" in Flashfire and select the flashable Xposed zip you downloaded earlier. No further settings needed just hit Flash! The next reboot is again gonna take a while, but after that you can launch the Xposed Installer and start Installing Modules. We're done.
Whenever you do a factory reset (from the recovery), You need to root again using Kingroot, replace it with SuperSU and install Xposed again.
Once more, I did not develop any of the tools mentioned, all credits to their respective authors.
Cheers,
prometh
Edit: I did not try too many modules yet but Wanam for lollipop works just fine and that useless S Whatever bar is a thing of the past
Hi.
I already have a rooted Galaxy A3 (A300FU) and I have TWRP as my recovery so my warranty is already gone and I'm not too worried about that. However I have had no success at trying to deodex my rom to be able to install xposed.
Would it be possible to just flash the deodexed and the xposed zip from TWRP? And with regards to the deodexed zip would it matter if I flash it over the top of my current rom when I'm using a carrier rom rather than the BTU unlocked rom?
Squall88uk said:
Hi.
I already have a rooted Galaxy A3 (A300FU) and I have TWRP as my recovery so my warranty is already gone and I'm not too worried about that. However I have had no success at trying to deodex my rom to be able to install xposed.
Would it be possible to just flash the deodexed and the xposed zip from TWRP? And with regards to the deodexed zip would it matter if I flash it over the top of my current rom when I'm using a carrier rom rather than the BTU unlocked rom?
Click to expand...
Click to collapse
I think this would be a question for the deodex thread I linked but heres my 5 cents: The procedure in your case should be Flashing Deodex (eventually also gapps_replacement from that thread if you get Google Apps FCs) flashing Xposed, booting, installing the xposed installer. The Deodexed zip is meant to be flashed on top of your system. What I described is basically doing manually what the deodex zip file would do (deleting copying...). Since you have twrp already, I guess a system backup wouldn't hurt.
Many thanks for the help. I'll make a nandroid backup of system first just in case and then give it a go.
Thanks again.
Impossible with my SG A3 A300FU
Hello, I already have the root and TWRP installed, but if I try to type the command line with ADB it doesn't work and if I flash the zip, it doesn't work too. Any Idee ? With the first or the second method boot loop with the samsung logo !!
darwin345 said:
Hello, I already have the root and TWRP installed, but if I try to type the command line with ADB it doesn't work and if I flash the zip, it doesn't work too. Any Idee ? With the first or the second method boot loop with the samsung logo !!
Click to expand...
Click to collapse
If you try the adb commands whats the exact error? Permission Problems? Anyway the Command line should do nothing else than flashing the zip file (I dont know what the zip file wipes after flashing but I assume its dalvik and cache).
Great work prometh696 !!! I managed to get xposed on my A5 with knox 0x0 !!!
Some other steps I followed to get it for my A500FU; first I extracted my own system folders system/app/, system/framework/ & system/priv-app/ with root explorer to my ext SD card and then copied it to my computer.
On the computer I batch deodexed those folders with joeldroid's batch deodexer:
http://forum.xda-developers.com/and.../script-app-joeldroid-lollipop-batch-t2980857
Had some issues there as not every Java version seems to deliver the deodexed folders without errors; more details in that topic.
Then I followed your adb commands and installed xposed, and as you said, knox didn't change and is still 0x0 !!!
Thanks again !!!
---------- Post added at 01:30 PM ---------- Previous post was at 01:06 PM ----------
prometh696 said:
If you try the adb commands whats the exact error? Permission Problems? Anyway the Command line should do nothing else than flashing the zip file (I dont know what the zip file wipes after flashing but I assume its dalvik and cache).
Click to expand...
Click to collapse
The command lines are for copying the deodexed apks (so not in a zip). The zip is for xposed and is flashed by flashfire.
But as he already got TWRP (and thus knox 0x1) I see no use for him to use your method anyway
prometh696 said:
If you try the adb commands whats the exact error? Permission Problems? Anyway the Command line should do nothing else than flashing the zip file (I dont know what the zip file wipes after flashing but I assume its dalvik and cache).
Click to expand...
Click to collapse
When I type the first command line after this one "rm -Rf /system/priv-app" or this one "rm -Rf /system/framework" I don't know when exactly my phone reboot and bootloop on samsung logo (dynamic one) ???
My mobile restart before end of commands line
Hi,
your solution seems really good but my mobile (A300FU) is retarting before I typed all commands line.
Do you know a solution ?
Maybe cause I've no ExtSDcard and use the internal card ?
Thank you for your help !!
Regards
Virtua
update : I tried with trwp and made the necessary but the mobile does not boot.
This phone is a mess
It's the first time I can't do what I want with a phone. All posts seems to be a hoax. ;( ;(
Whenever you do a factory reset (from the recovery), You need to root again using Kingroot, replace it with SuperSU and install Xposed again.
Click to expand...
Click to collapse
This is actually incorrect unless root is systemless.
Root remains in system, and so does xposed. A factory reset does not touch the system partition.
You lose root after a reset because you need to reinstall superuser. If you make it a system app you won't lose root even after a reset.
The same with xposed just reinstall the apk.