Database Info

A2SD on Haykuro's 6.0r1

Morning all (in my part of the world)
Has anyone been able to get A2SD working on H's latest ROM yet?? I've tried afew things apps and adb wise and they seem to lock up the phone on the HTC screen with the (now annoying) chime, I've Reflashed on got everything running as normal so its just getting the A2SD bit working
Any Advice is much appreciated
Additionally im also experiencing issues with the drawer appearing at the bottom of the screen and the icons messing up when sliding the screen out

Thought i would throw up a screen shot for giggles
{
"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"
}

I came from dudes 1.1a, had apps and dalvik done with the "apps2sd2" app (on dudes).
after flashing new haykuro,i installed the old "apps2sd" app and got everything working again ;-)
maybe you should give it a try (formating sd by yourself, and the rest with "apps2sd" from maximus)

did you wipe for your ROM change or just Alt+S it??

Dantehman said:
Morning all (in my part of the world)
Has anyone been able to get A2SD working on H's latest ROM yet?? I've tried afew things apps and adb wise and they seem to lock up the phone on the HTC screen with the (now annoying) chime, I've Reflashed on got everything running as normal so its just getting the A2SD bit working
Any Advice is much appreciated
Additionally im also experiencing issues with the drawer appearing at the bottom of the screen and the icons messing up when sliding the screen out
Click to expand...
Click to collapse
It should work, it all depends how many apps. you have. you need to wait a while, since its installing all your all apps. that you had before........The home screen on landscape is not an issue, since the magic does not have a landscape mode on the home screen it does this. You can replace it with a alternative home so you won't have this issue, or use adb to push the launcher.apk that works right with screen home screen.

cholito said:
It should work, it all depends how many apps. you have. you need to wait a while, since its installing all your all apps. that you had before........The home screen on landscape is not an issue, since the magic does not have a landscape mode on the home screen it does this. You can replace it with a alternative home so you have this issue, or use adb to push the launcher.apk that works right with screen home screen.
Click to expand...
Click to collapse
Already taken care of the Launcher (2nd and 9th Posts) http://forum.xda-developers.com/showthread.php?t=518042
and I wiped my ex2 partition already so im looking at 0 appidge, but the issue is it getting sutck at the splash screen and looping with the (annoying) HTC chime, it wont budge
Im gonna get home from work later on and try formatting my card again by wiping everyhting off it and starting 100% fresh and ill first try
Haykuros A2SD via ADB
Then try..
The origional Apps2SD App
Failing that..
The new and improved Apps 2 SD Method
And ill report back with updates

Yeah, the old method works (the one where you have to use symlinks) but the newer, better method does not because Haykuro hasn't added unionfs into his kernel yet.
I tried flashing JF's boot.img from his ADP1.50 build through fastboot, but it caused half of the apps to force close so I had to wipe and reflash 6.0r1... apparently, Haykuro is working on it... he seems to be focusing more on Sapphire/Magic right now...

Dantehman said:
did you wipe for your ROM change or just Alt+S it??
Click to expand...
Click to collapse
i flashed haykuro, then (before starting) did a wipe, don`t know if necessary?
then i installed appstosd (the old one), removed the "first time" and made apps to sd.
after reboot it took a while, then all apps appeared ;-)
again appstosd, made dalvik cache to sd.
after reboot again it took a while (5 minutes or so), then 90 apps free space 75MB ;-)
i think formating sd by yourself and the old appstosd app should work ;-)

If thats the case im going to totally erase my card + partitions,
then try the Apps 2 SD app and see what happens
if not, amgupt01 do you have a linky for the old method?? (or im i being noobish and its the Haykuro's A2SD 5.0.x onwards i need to follow)

Dantehman said:
If thats the case im going to totally erase my card + partitions,
then try the Apps 2 SD app and see what happens
if not, amgupt01 do you have a linky for the old method?? (or im i being noobish and its the Haykuro's A2SD 5.0.x onwards i need to follow)
Click to expand...
Click to collapse
lol, it's the one for 5.0.x onwards.

amgupt01 said:
lol, it's the one for 5.0.x onwards.
Click to expand...
Click to collapse
Followed and Failed, looping on the splash screen with the chime,,,, as didnt put into silent,,, aargh its killing my ears lmao
anyone have any ideas???

pulling battery now!
====== UPDATE ======
Alt+S (just for fun, to see if it does anything)

Dantehman said:
pulling battery now!
====== UPDATE ======
Alt+S (just for fun, to see if it does anything)
Click to expand...
Click to collapse
if you came into recovery, there should be no real problem?
still your apps on sd?
try the "appstosd" app (old one)?

EPIC FAIL
Alt+W
Alt+S
Keyboard Back up and running
Stuck where i was,
seems the Origional A2SD theory has left me high and dry
(all this wiping and reflashing, maybe i should learn how to use nandroid and make a backup lmao!)

Haykuros Apps to SD tutorial worked fine for me.
I formatted my ext2 partition first after coming from jf1.5 just to start clean.
Setup in 5.0.1 onward
http://android-dls.com/wiki/index.php?title=Haykuro_Apps_to_SD
hope it helps.

Success!!!!!!
The Origional A2SD APP works!!!!!
Wahoo
-Those who are keen eyed will notice that this is my old picture,,, the reason ive put this up is because i have 86mb FREE AGAIN on this ROM

here's what i did :
1. nandroid backup
2. alt+w, alt+s, reboot
3. open terminal emu, rm all folders in /system/sd from H1.5r3, reboot
4. busybox cp -a /data/app /system/sd/
busybox cp -a /data/app-private /system/sd/
busybox cp -a /data/dalvik-cache /system/sd/
busybox cp -a /data/data /system/sd/
5. rm -r /data/app
ln -s /system/sd/app /data/app
rm -r /data/app-private
ln -s /system/sd/app-private /data/app-private
rm -r /data/data
ln -s /system/sd/data /data/data
rm -r /data/dalvik-cache
ln -s /system/sd/dalvik-cache /data/dalvik-cache
6. reboot
7. enjoy
Been running smooth ever since, 1gb ext2 partition w/ 150ish apps installed, 88mb internal mem free.

If you had Klaxon installed before you went to the H build, thats probably the culprit. It will put your phone in a continuos loop at boot screen.

kchino said:
If you had Klaxon installed before you went to the H build, thats probably the culprit. It will put your phone in a continuos loop at boot screen.
Click to expand...
Click to collapse
that and " owner" and a few other programs.
on a side note, after thinking about it last night after looping mine about 10 times...
i think it prob is necessary to reformat the sd, so back it all up jic , then the old a2sd prog seems to work for most folks. the only guys that seem to get it to work are ether coming from a clean sheet, or an H build...
also, i think if your coming from a non H build and you use backup for root it seems to loop.

ichibanpnoy said:
here's what i did :
1. nandroid backup
2. alt+w, alt+s, reboot
3. open terminal emu, rm all folders in /system/sd from H1.5r3, reboot
4. busybox cp -a /data/app /system/sd/
busybox cp -a /data/app-private /system/sd/
busybox cp -a /data/dalvik-cache /system/sd/
busybox cp -a /data/data /system/sd/
5. rm -r /data/app
ln -s /system/sd/app /data/app
rm -r /data/app-private
ln -s /system/sd/app-private /data/app-private
rm -r /data/data
ln -s /system/sd/data /data/data
rm -r /data/dalvik-cache
ln -s /system/sd/dalvik-cache /data/dalvik-cache
6. reboot
7. enjoy
Been running smooth ever since, 1gb ext2 partition w/ 150ish apps installed, 88mb internal mem free.
Click to expand...
Click to collapse
APPRECIATED!! i almost gave up on the build and went back to JF's.. 88meg free

[Tutorial]Deodexing + Zipaligning Galaxy Gio GT-S5660

Advantages or disadvantages
- Odexed ROMs are slightly faster, deodexed ROMs are slightly slower
+ You can make custom themes for your ROM
+ Performance los is negligible.
Requirements
xUltimate - http://www.droidforums.net/forum/xeudoxus/47283-release-xultimate.html
Busybox installed
Root
Automatic deodexing - Method 1, by r33p
1. Connect phone to computer
2. Start xUltimate, we will now get the required files from our phone to deodex and zipalign it which we will describe in the 3rd step.
3. Select option #15 then "do it all".
Deodexing (little harder, but contains useful information for your future Galaxy Gio modding experience)- Method 2, by me
1. Connect phone to computer
2. Start xUltimate, we will now get the required files from our phone to deodex and zipalign it which we will describe in the 3rd step.
3. On the main menu of xUltimate, choose option 5 (Pull and deodex all). Everything will be done for you here. Don't worry. You will see all your finished files in the folders 'done_app' and 'done_frame' which are located in the installation directory of xUltimate.
4. move folders 'done_app' and 'done_frame' folders to your sdcard, you can find these folders in the directory of xUltimate as described in the previous step.
5. Make sure the sdcard is not mounted to pc anymore
6. Open Windows Command Prompt and type the following commands.
adb shell
su
stop
mount -o remount,rw /dev/block/stl12 /system
rm /system/app/*.odex
rm /system/framework/*.odex
busybox cp /sdcard/done_app/* /system/app/
busybox cp /sdcard/done_frame/* /system/framework/
chmod 644 /system/app/*
chmod 644 /system/framework/*
mount -o remount,ro /dev/block/stl12 /system
sync
reboot recovery
Click to expand...
Click to collapse
7. Now data and cache reset in the recovery menu...
8. reboot
If one of the commands, for example 'cp' is not found, try putting busybox in front of the command:
eg: busybox cp /sdcard/done_frame/* /system/framework/
How to odex again
This may put you in the right direction. You may need to edit some steps.
http://forum.xda-developers.com/showthread.php?t=1124034
If you like my work please donate
Paypal:
Bankaccount: in private message

Updated my tutorial. Now everything works.

What does this do to my gio?
// Thanks from the noob

why the hassle? just let xultimate do it all automatic -> select option #15 then "do it all"
yep

Thanks.. ;-)
Would it work with others samsung devices?
Gonna try with 5510
Sent from my GT-I9100 using Tapatalk

dann3_86 said:
What does this do to my gio?
// Thanks from the noob
Click to expand...
Click to collapse
I am curious to

I suggest you google deodexing and zipaligning.
Deodexing in short means that it will allow you to have custom themes.
Zipaligning improves performance of the apk/jar files when reading
There is a lot of information you might want to look up!
I just added r33p's suggestion. Thanks!

Dhuu, just google it.............
I did, but it gives no answers.
I thought it was about the holy grail, or the fountain of youth..............
But no..........
But comes close
So tell me, does it works on the fly or must you reboot to aply changes?

I tiedy this metod and it works. Tank you

I'm having a problem..
I'm on xUltimate, I go to the advanced menu (15) and I type 1 (Do everything) and then it says that I don't have files in done_app folder.
Please help
Edit: I have rooted my phone, it's on Gingerbread.xxkpo. Do I have to Un-Root my phone and then do this ? Also can I root it back when the ROM is on ?
Please reply fast :S

I'm having this issue,,, what does it mean? i pulled out all the files with the automatic process and went fine. But then in the deoxed process:
How can i solve it? Thanks :3

Deodex ur jb rom {not for at&t}

FINALLY MY WIFI CAME BACK !!!
SO I THINK U SHOULD DEODEX UR ROM FOR MORE SPACE AND FLUIDITY
{I COULD NOT CREATE BATCH FILE AS OUR BOOT IMAGE DOES NOT SUPPORT TRUE ADB ROOT AS ITS DEV EDITION}(ANY IDEAS FROM DEVS IS WELCOME)
AGAIN SAYING NOT FOR ATT
OKAY FIRST THANX TO dsixda/Android-Kitchen FOR HELPING TO DEODEX THE ROM
NOW STEPS ::::::
-1.install a third party launcher (like apex for safety purpose)
0.MAKE A BACKUP OF UR SYSTEM (I HOPE U R USING BMM !!!)
1.DOWNLOAD THE APP AND FRAMEWORK FOLDER FROM LINK GIVEN BELOW
2.PUT BOTH THE FOLDERS ON SDCARD AS WELL AS INTERNAL MEMORY (DONNO WHICH IS USED !!)
3.OPEN THE """4.0.4ROOT BY CRC""" FOLDER U DOWNLOADED WHILE ROOTING OR ANY FOLDER WHICH CONTAINS ADB
3.5}NOW HOLDING SHIFT CLICK OPEN COMMAND WINDOW HERE
4.NOW CONNECT PHONE IN MTP MODE WITH DEBUGGING ON
5.TYPE THE FOLLOWING CODE AND U R DONE (WELL IT WILL SLIGHTLY MAKE U FEEL LIKE A TEMPORARY DEV HAAHAH)
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/deodexedapp/* /system/app/
rm /system/app/*.odex
cp /sdcard/deodexedframe/* /system/framework/
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot
note ::
1.its o not zero
2.when u enter su the $ sign will change to # it means u gained root access
3.i dont remember but after pressing su look at ur phone if supersu notification for root access comes allow it if it is there
4.i am not sure or the stock launcher it may fc so firs install a third party launcher for safety purpose
*links ::::
apps::
https://app.sugarsync.com/iris/wf/D8443834_63525726_687588
framework::::
https://www.sugarsync.com/pf/D8443834_63525726_688199
pls hit thanx bros it motivates me !!!!!!!
make an acc on sugarsync the next famous storage systemm it will help u as well as me

What is MTP mode?

brianmoyano said:
What is MTP mode?
Click to expand...
Click to collapse
When ya connect the phone to PC, it will show 3 different modes. Like USB mass storage and stuff. One of em is MTP. pull down the notification bar, you will get those options (when connected of course)
Sent from my muffin LIFE! Under maintenance.!

Good. Thanks for sharing this!
I already Deodexed and zipaligined my rom using this tutorial to achieve the same.
brianmoyano said:
What is MTP mode?
Click to expand...
Click to collapse
Media Transfer Protocol. Gives you access to your SD Card and phone storage without unmounting them from phone so your SD Card is also available through phone as well as on PC. If you access any file on your phone, it will first copy it to PC and then open it which makes it slower. But its good enough for transferring pics and music and basically MEDIA TRANSFER as the name says..

answersamir said:
Code:
adb shell
su
stop
mount -o rw, remount /system/ /system/
cp /sdcard/deodexedapp/* /system/app/
rm /system/app/*.odex
cp /sdcard/deodexedframe/* /system/framework/
rm /system/framework/*.odex
mount -o ro, remount /system/ /system/
reboot
Click to expand...
Click to collapse
This one is wrong...
The right one is
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
rm /system/app/*.odex
rm /system/framework/*.odex
cp /sdcard/deodexedapp/* /system/app/
cp /sdcard/deodexedframe/* /system/framework/
mount -o ro,remount /system/ /system/
reboot
Sent from my jb atrix 2

shubham412302 said:
This one is wrong...
The right one is
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
rm /system/app/*.odex
rm /system/framework/*.odex
cp /sdcard/deodexedapp/* /system/app/
cp /sdcard/deodexedframe/* /system/framework/
mount -o ro,remount /system/ /system/
reboot
Sent from my jb atrix 2
Click to expand...
Click to collapse
On extremely close observations I found out that both are same :sly:
Buddy order doesn't matter
Sent from my ME865 using xda app-developers app

can you upload an alternate link for 'apps' ...download is not completing...it is stopping after 140mb....

poorna said:
can you upload an alternate link for 'apps' ...download is not completing...it is stopping after 140mb....
Click to expand...
Click to collapse
Thats the full size of zipped apps...
But it has all apps
Sent from my jb atrix 2

shubham412302 said:
Thats the full size of zipped apps...
But it has all apps
Sent from my jb atrix 2
Click to expand...
Click to collapse
when i try to extract it ,i get a message invalid file ...the actual size is 185mb ...twice i downloaded. in the 1st attempt i was able to download 146mb...in the 2nd attempt i was able to download 140mb....

poorna said:
when i try to extract it ,i get a message invalid file ...the actual size is 185mb ...twice i downloaded. in the 1st attempt i was able to download 146mb...in the 2nd attempt i was able to download 140mb....
Click to expand...
Click to collapse
Match this with your d/l file.
146 MB (153,457,466 bytes)
CRC: 7FC9D73F

shubham412302 said:
This one is wrong...
The right one is
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
rm /system/app/*.odex
rm /system/framework/*.odex
cp /sdcard/deodexedapp/* /system/app/
cp /sdcard/deodexedframe/* /system/framework/
mount -o ro,remount /system/ /system/
reboot
Sent from my jb atrix 2
Click to expand...
Click to collapse
the phone is not booting... after i type stop and press enter ,the screen turns off,then when i type mount -o rw,remount /system/ /system/ and press enter i get the same line and then i get the # symbol again..then when type rm /system/app/*.odex and press enter i get the same line and then i get the # symbol again ,same thing for the next rm line...but when i type cp /sdcard/deodexedapp/* /system/app/ and press enter i get the same line again and there is no # symbol,the same thing happens to the following lines ....when i typed reboot and press enter the same line(reboot) appears and the phone is not rebooting...i removed the battery and tried to boot the phone is not booting...i downloaded both the links (apps and framework) and extracted them and copied both(deodexedapp and deodexedframe) to internal phone storage and sd card ....what might be the problem here?

poorna said:
the phone is not booting... after i type stop and press enter ,the screen turns off,then when i type mount -o rw,remount /system/ /system/ and press enter i get the same line and then i get the # symbol again..then when type rm /system/app/*.odex and press enter i get the same line and then i get the # symbol again ,same thing for the next rm line...but when i type cp /sdcard/deodexedapp/* /system/app/ and press enter i get the same line again and there is no # symbol,the same thing happens to the following lines ....when i typed reboot and press enter the same line(reboot) appears and the phone is not rebooting...i removed the battery and tried to boot the phone is not booting...i downloaded both the links (apps and framework) and extracted them and copied both(deodexedapp and deodexedframe) to internal phone storage and sd card ....what might be the problem here?
Click to expand...
Click to collapse
Wait for a while....
Until you get the [email protected] again you must not do any thing because the previous step is not done.....
Be patient.
The step copy system apps take 5 minutes...
And there is a space here before remount
mount -o rw, remount /system/ /system/
Sent from my jb atrix 2

What are the advantages of deodexing the stock rom?
I came across this thread and it gave me curiosity to find-out the stuff which I wanted to read for long time. Odex and deodex..
The only advantage I came across of deodexing was posibility of theme modifications.
Some thread on XDA and google said that with odex rom (1) boot will be faster.
With deodexing, they said (1) it will take up more data space (2) theoritically deodexing will slow some performance and (3) longer boot times because of big dalvik cache...
Please can you tell me exactly where I am wrong?
Sent from my jb atrix 2

Download unsuccessful
Download is not starting...it says it has started but nothing is getting downloaded have tried a lot.... any alternate link pls:silly:

hello , it´s only for jelly bean?

Native tether for VZW DE 4.4

Now works on non-DE phones too.
Installation instructions, with ro.boot.write_protect=0:
Code:
adb push VzwEntitlementService.apk /sdcard/VzwEntitlementService.apk
adb shell
su
mount -o remount,rw /system
mv /system/priv-app/VzwEntitlementService.apk /system/priv-app/VzwEntitlementService.apk.bak
mv /system/priv-app/VzwEntitlementService.odex /system/priv-app/VzwEntitlementService.odex.bak
cp /sdcard/VzwEntitlementService.apk /system/app/VzwEntitlementService.apk
chmod 644 /system/app/VzwEntitlementService.apk
Now tap "Portable Wi-Fi hotspot". You will experience a force close, this is expected.
Code:
mv /system/app/VzwEntitlementService.apk /system/priv-app/VzwEntitlementService.apk
mount -o remount,ro /system
exit
exit
Now you will be able to tether.

For the geeks:
Code:
.method public startEntitleCheck()V
.locals 2
.prologue
const/4 v0, 0x1
iput-boolean v0, p0, Lcom/motorola/service/vzw/entitlement/EntitlementDialogActivity;->mEntitlementCheckState:Z
const-string v1, "1"
iput-object v1, p0, Lcom/motorola/service/vzw/entitlement/EntitlementDialogActivity;->mStatusCode:Ljava/lang/String;
return-void
.end method

cj64 said:
Installation instructions:
Code:
adb push VzwEntitlementService.apk /sdcard/VzwEntitlementService.apk
adb shell
su
mount -o remount,rw /system
mv /system/app/VzwEntitlementService.apk /system/app/VzwEntitlementService.apk.bak
mv /system/app/VzwEntitlementService.odex /system/app/VzwEntitlementService.odex.bak
cp /sdcard/VzwEntitlementService.apk /system/app/VzwEntitlementService.apk
chmod 644 /system/app/VzwEntitlementService.apk
Now tap "Portable Wi-Fi hotspot". You will experience a force close, this is expected.
Code:
mv /system/app/VzwEntitlementService.apk /system/priv-app/VzwEntitlementService.apk
mount -o remount,ro /system
exit
exit
Now you will be able to tether.
Click to expand...
Click to collapse
Hi there! I'm definitely not in the "geek" category. But, I'm extremely interested in this. I'm curious, are all of the above items individual adb commands. Do each? (I've not done anything with ADB since Droid X days and then just followed very precise directions).
Any possibility this could be put into some kind of flashable zip (through recovery)...that might have scripts that take care of the "grunt" work?
If I only had the time and knowledge to get further into these things, I wouldn't even make the suggestion.
Still yet, GREATLY APPRECIATED!!

cj64 said:
Installation instructions:
Code:
adb push VzwEntitlementService.apk /sdcard/VzwEntitlementService.apk
adb shell
su
mount -o remount,rw /system
mv /system/app/VzwEntitlementService.apk /system/app/VzwEntitlementService.apk.bak
mv /system/app/VzwEntitlementService.odex /system/app/VzwEntitlementService.odex.bak
cp /sdcard/VzwEntitlementService.apk /system/app/VzwEntitlementService.apk
chmod 644 /system/app/VzwEntitlementService.apk
Now tap "Portable Wi-Fi hotspot". You will experience a force close, this is expected.
Code:
mv /system/app/VzwEntitlementService.apk /system/priv-app/VzwEntitlementService.apk
mount -o remount,ro /system
exit
exit
Now you will be able to tether.
Click to expand...
Click to collapse
Thx, works great for me!

cj64 said:
Installation instructions:
Code:
...
[STRIKE]mv /system/app/VzwEntitlementService.apk /system/app/VzwEntitlementService.apk.bak
mv /system/app/VzwEntitlementService.odex /system/app/VzwEntitlementService.odex.bak[/STRIKE]
mv /system/priv-app/VzwEntitlementService.apk /system/priv-app/VzwEntitlementService.apk.bak
mv /system/priv-app/VzwEntitlementService.odex /system/priv-app/VzwEntitlementService.odex.bak
...
Click to expand...
Click to collapse
Made a correction to the paths in the installation instructions.

will this work on non DE vz moto x after 4.4 root is achieved?

Yes.

cj64 said:
Yes.
Click to expand...
Click to collapse
VERY cool, thank you

cj64 said:
Installation instructions:
Code:
adb push VzwEntitlementService.apk /sdcard/VzwEntitlementService.apk
adb shell
su
mount -o remount,rw /system
mv /system/priv-app/VzwEntitlementService.apk /system/priv-app/VzwEntitlementService.apk.bak
mv /system/priv-app/VzwEntitlementService.odex /system/priv-app/VzwEntitlementService.odex.bak
cp /sdcard/VzwEntitlementService.apk /system/app/VzwEntitlementService.apk
chmod 644 /system/app/VzwEntitlementService.apk
Now tap "Portable Wi-Fi hotspot". You will experience a force close, this is expected.
Code:
mv /system/app/VzwEntitlementService.apk /system/priv-app/VzwEntitlementService.apk
mount -o remount,ro /system
exit
exit
Now you will be able to tether.
Click to expand...
Click to collapse
What does that chmod 644 do? Is this required to be done on the system or could you use root explorer to put the .zip file into the priv-app file on they system.

TheDonXR said:
What does that chmod 644 do? Is this required to be done on the system or could you use root explorer to put the .zip file into the priv-app file on they system.
Click to expand...
Click to collapse
Sets the permissions to be the same as the original entitlement files.
http://www.draac.com/chmodchart.html
Do the equivalent with root explorer if that is what you are going to use.

cj64 said:
Yes.
Click to expand...
Click to collapse
Assuming you can get writable /system, which isn't a sure thing. Didn't the first 4.2.2 root not achieve that and you still had to boot into a faux recovery to write to /system in any sticky way?

SQFreak said:
Didn't the first 4.2.2 root not achieve that and you still had to boot into a faux recovery to write to /system in any sticky way?
Click to expand...
Click to collapse
Yes. The same technique works on 4.4.

this worked great. Thanks!

Hi there! Any way this can be made into a flashable zip through TWRP? I've not had much luck lately with ADB, etc. I am sitting on 4.4 DE, unlocked, rooted, with the new TWRP. I was hoping to do this all on the phone if it were possible and not too difficult.
And, just so you know, I am always extremely appreciated for all the mods and development on these devices. You guys who have learned these skills just rock! (getting older here with less time on my hands to always dig in and figure it out on my own, unfortunately)
I'm travelling in 2 wks and just want to make sure my Moto X is up and fully functional (as was my gNex).
Thanks!

Dburgessme2 said:
Hi there! Any way this can be made into a flashable zip through TWRP? I've not had much luck lately with ADB, etc. I am sitting on 4.4 DE, unlocked, rooted, with the new TWRP. I was hoping to do this all on the phone if it were possible and not too difficult.
And, just so you know, I am always extremely appreciated for all the mods and development on these devices. You guys who have learned these skills just rock! (getting older here with less time on my hands to always dig in and figure it out on my own, unfortunately)
I'm travelling in 2 wks and just want to make sure my Moto X is up and fully functional (as was my gNex).
Thanks!
Click to expand...
Click to collapse
I did most of the work on my phone using root explorer, I didn't know how to set the permissions when I did it and used ADB for that. I found out later how to do that and here's what the process should be without using ADB:
1. Download Root Explorer by Jrummy in the Play store.
2. Download VZWEntitlementServices.apk from OP on your moto x.
3. Go into Root Explorer and find System folder, find priv-app, inside priv-app long press VZWEntitlementServices.apk and VZWEntitlementServices.odex rename to VZWEntitlementServices.apk.bak and VZWEntitlementServices.odex.bak and back out to first folder.
4. Go to sdcard folder, download and find VZWEntitlementServices.apk that you downloaded from step 2 copy it and back out to the home folder enter the system folder and paste it.
5. Long press on the file and hit permissions in the menu. change permissions to look like screenshot.
{
"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"
}
(should show rw-r--r--)
6. Exit out of root explorer and try to enable your tether it will FC.
7. Go back to root explorer and move the VZWEntitlementServices.apk that you put in the system folder to the priv-app folder.
8. Check the tether it should work.
9. PROFIT!
Let me know if it works!

I will definitely give that a shot in the next day or so. Thanks!

This is great, thanks so much!
I noticed that unlike the native tether solution for 4.2.2 this one still shows the "Checking subscription status" toast notification when activating tether - does this mean that Verizon is being notified everytime I am activating tether even though the check is ultimately being bypassed? Even if not I'd prefer not to see this.

TheDonXR said:
I did most of the work on my phone using root explorer, I didn't know how to set the permissions when I did it and used ADB for that. I found out later how to do that and here's what the process should be without using ADB:
1. Download Root Explorer by Jrummy in the Play store.
2. Download VZWEntitlementServices.zip from OP on your moto x.
3. Go into Root Explorer and find System folder, find priv-app, inside priv-app long press VZWEntitlementServices.zip and VZWEntitlementServices.odex rename to VZWEntitlementServices.zip.bak and VZWEntitlementServices.odex.bak and back out to first folder.
4. Go to sdcard folder, download and find VZWEntitlementServices.zip that you downloaded from step 2 copy it and back out to the home folder enter the system folder and paste it.
5. Long press on the file and hit permissions in the menu. change permissions to look like screenshot.
(should show rw-r--r--)
6. Exit out of root explorer and try to enable your tether it will FC.
7. Go back to root explorer and move the VZWEntitlementServices.zip that you put in the system folder to the priv-app folder.
8. Check the tether it should work.
9. PROFIT!
Let me know if it works!
Click to expand...
Click to collapse
Well, this is just awesome! Evidently it worked. I'm making this post with my Nexus 7 tethered to my DE 4.4 Moto X on my unlimited data plan.
Sent from my Nexus 7 using Tapatalk 4

did it on my non DE and it works lovely. goodjob

publicanimal said:
does this mean that Verizon is being notified everytime I am activating tether even though the check is ultimately being bypassed?
Click to expand...
Click to collapse
No, it's just cosmetic. There is a useful internet connection check which was left alone.

[COMPLETE GUIDE]Root HD7/8/10(6th Gen 2016) and replace with SuperSU

FOR 2016(6th GEN) ON 5.3.1 AND 5.3.1.1 ONLY: Works on HD7, HD8 and HD10
You can downgrade from 5.3.2 by adb sideload the 5.3.1.1 bin file.
DO NOT downgrade from 5.3.2.1!! Hard-brick attention!!
This guide requires some ADB skills, read more from the forum, install it from here
Enable ADB and install apps from other sources in Developer Options
Download Kingoroot PC version at www.kingoapp.com or google mirror
Root your Kindle using Kingoroot, then reboot your device
Download a file explorer apk (ie. ES File Explorer) and sideload install the apk to your kindle
Download SuperSU apk at APKPure, but DON'T install it first
Download the attachment "Kingo.to.SuperSU" below then unzip and paste into your kindle, ie /sdcard/Kingo.to.SuperSU
Run ADB Shell and type
Code:
su
mount -w -o remount /system
Keep the root-accessed ADB shell open, then remove root by using Kingoroot
(If your kindle reboot at this step, you need to re-root it and try the above steps again)
In the ADB shell type
Code:
cd /sdcard/Kingo.to.SuperSU
cp ./su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &
Still keep that root-accessed ADB shell opened, copy the SuperSU apk into your kindle and install it using the file explorer, DO NOT OPEN IT.
In the ADB shell type
Code:
cp ./su /system/xbin/su
chmod 0755 /system/xbin/su
rm /system/xbin/supolicy
rm /system/bin/install-recovery.sh
rm -rf /system/usr/iku
rm -rf /sdcard/Kingroot
(1 error with "No such file or directory" is okay I think)
Run SuperSU and update binary, choose the "normal" one, then it should ask you to reboot your kindle
Open up SuperSU and go to setting
Set the "Default Access" as [Grant]
{
"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"
}
Due to unknown reason, kindle cannot prompt the "Asking for root access", this step is to allow all access for all apps.
Install Root Checker and confirm you have root, run ADB shell to confirm you can su
Remove Kingolink and that Kingo battery app from kindle
Uninstall Kingo from PC via manual unins000.exe inside install directory in programs(x86)
ALL DONE! You may then want to install google play, do all the pm disable for OTA, firelauncher, and other amazon services you don't want.
References:
[Index] Amazon Fire HD 8 and HD 10 (5th Gen/2015)
[Working]Root Kindle Fire HD8 6th Gen
Tips, Tricks, and the Root!
[HOW-TO] Install Google Play Store (Fire OS 5.3.1.1) (No Root/ADB)
[Script] Replace KingoRoot with SuperSU
Credits:
@coltxL2717
@chemie99
@2ig2ag
@smokejumper76
@phpbb88 ME

phpbb88 said:
Code:
cp ./su /system/xbin/su
chmod 0755 /system/xbin/su
rm /system/xbin/supolicy
rm /system/bin/install-recovery.sh
rm -rf /system/usr/iku
rm -rf /sdcard/Kingroot
[*]Run SuperSU and update binary then it should ask you to reboot your kindle
[*]Open up SuperSU and go to setting
Click to expand...
Click to collapse
Getting error at Step 11:
After entering
rm /system/bin/install-recovery.sh
getting
No such file or directory
Then when updating binaries, SuperSU says "Installation successful! Reboot your device." On reboot, says that binaries are not installed and the app closes itself. Also, when initially updating SuperSU binaries, which option is to be chosen? The first "Normal" or the second "Custom/TWRP."
Here is my full log:
[email protected]:/ $ su
[email protected]:/ # mount -w -o remount /system
[email protected]:/ # cd /sdcard/Kingo.to.SuperSU
[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/daemonsu
[email protected]:/sdcard/Kingo.to.SuperSU # chmod 0755 /system/xbin/daemonsu
[email protected]:/sdcard/Kingo.to.SuperSU # daemonsu -d &
[1] 5542
[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/su
[1] + Done daemonsu -d
[email protected]:/sdcard/Kingo.to.SuperSU # chmod 0755 /system/xbin/su
[email protected]:/sdcard/Kingo.to.SuperSU # rm /system/xbin/supolicy
[email protected]:/sdcard/Kingo.to.SuperSU # rm /system/bin/install-recovery.sh
rm: /system/bin/install-recovery.sh: No such file or directory
1|[email protected]:/sdcard/Kingo.to.SuperSU # rm -rf /system/usr/iku
[email protected]:/sdcard/Kingo.to.SuperSU # rm -rf /sdcard/Kingroot
[email protected]:/sdcard/Kingo.to.SuperSU # reboot

imadiamond said:
Getting error at Step 11:
After entering
rm /system/bin/install-recovery.sh
getting
No such file or directory
Then when updating binaries, SuperSU says "Installation successful! Reboot your device." On reboot, says that binaries are not installed and the app closes itself. Also, when initially updating SuperSU binaries, which option is to be chosen? The first "Normal" or the second "Custom/TWRP."
Here is my full log:
[email protected]:/ $ su
[email protected]:/ # mount -w -o remount /system
[email protected]:/ # cd /sdcard/Kingo.to.SuperSU
[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/daemonsu
[email protected]:/sdcard/Kingo.to.SuperSU # chmod 0755 /system/xbin/daemonsu
[email protected]:/sdcard/Kingo.to.SuperSU # daemonsu -d &
[1] 5542
[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/su
[1] + Done daemonsu -d
[email protected]:/sdcard/Kingo.to.SuperSU # chmod 0755 /system/xbin/su
[email protected]:/sdcard/Kingo.to.SuperSU # rm /system/xbin/supolicy
[email protected]:/sdcard/Kingo.to.SuperSU # rm /system/bin/install-recovery.sh
rm: /system/bin/install-recovery.sh: No such file or directory
1|[email protected]:/sdcard/Kingo.to.SuperSU # rm -rf /system/usr/iku
[email protected]:/sdcard/Kingo.to.SuperSU # rm -rf /sdcard/Kingroot
[email protected]:/sdcard/Kingo.to.SuperSU # reboot
Click to expand...
Click to collapse
in step 10, install SuperSU but do not open it.
your log should have no problem, maybe try again from clean state? (clean 5.3.1./5.3.1.1 state)
PS. you should choose "normal" when update binary

Thanks for making this clear and concise guide! Well done.

phpbb88 said:
in step 10, install SuperSU but do not open it.
your log should have no problem, maybe try again from clean state? (clean 5.3.1./5.3.1.1 state)
PS. you should choose "normal" when update binary
Click to expand...
Click to collapse
Did cache wipe/format and reset to factory settings via device recovery (powering on and holding volume button.)
Went through the process again, and THOUGHT it worked, even though I got the same "No such file or directory" error. I didn't reboot on Step 12 and went into SuperSU setings to "Grant." Got Root Checker. Had root. Rebooted and opened Root Checker and had no root. So--
1) still getting same "No such file" error: how can I reset the device "clean" without that new .bin? Isn't there a way to "clean" the OS already on the device? On 5.3.1.1 On device did "wipe data/factory reset" then "wipe cache partition" and have also done them in the opposite order to make sure.
2) On step 12 do you reboot the device like SuperSu says, or do you just go straight into the settings. I was rebooting the device at this point for 3 or 4 tries. The last two times I did not and went straight into settings. Still same error of "No such file or directory." The file IS in the Kingo.to.SuperSU folder though, even downloaded and unzipped the attachment a few times.

Could I also install a customrom after root? with one?

meikschlenther said:
Could I also install a customrom after root? with one?
Click to expand...
Click to collapse
Not at this time... There are no ROMs as of yet, and if I'm not mistaken we would need a custom recovery and our bootloader is still locked.

imadiamond said:
Did cache wipe/format and reset to factory settings via device recovery (powering on and holding volume button.)
Went through the process again, and THOUGHT it worked, even though I got the same "No such file or directory" error. I didn't reboot on Step 12 and went into SuperSU setings to "Grant." Got Root Checker. Had root. Rebooted and opened Root Checker and had no root. So--
1) still getting same "No such file" error: how can I reset the device "clean" without that new .bin? Isn't there a way to "clean" the OS already on the device? On 5.3.1.1 On device did "wipe data/factory reset" then "wipe cache partition" and have also done them in the opposite order to make sure.
2) On step 12 do you reboot the device like SuperSu says, or do you just go straight into the settings. I was rebooting the device at this point for 3 or 4 tries. The last two times I did not and went straight into settings. Still same error of "No such file or directory." The file IS in the Kingo.to.SuperSU folder though, even downloaded and unzipped the attachment a few times.
Click to expand...
Click to collapse
Please download the official 5.3.1.1 bin, wipe cache, factory reset, then sideload the bin through recovery mode and follow the guide step by step strictly.
edited: please have a look at here, I somehow worked with 1 error, which is likely the "rm /system/bin/install-recovery.sh" command.

phpbb88 said:
Please download the official 5.3.1.1 bin, wipe cache, factory reset, then sideload the bin through recovery mode and follow the guide step by step strictly.
edited: please have a look at here, I somehow worked with 1 error, which is likely the "rm /system/bin/install-recovery.sh" command.
Click to expand...
Click to collapse
First problem was even though previously all drivers loaded and I was able to root/re-root and navigate adb.... when booting the device into recovery mode? Tablet not recognized by computer. Extremely frustrating. Read and read and read.... and finally came across something from @smokejumper76 -----answer was in Device Manager, tablet was showing up as KFGIWI with the error that drivers were not installed. Did "manually install drivers" "Search online" does not work) and chose ADB Composite Device, and now tablet is recognized in recovery mode.
Issue NOW is the process gets halfway through installation and then force closes with
E: failed to verify whole-file signature
E: signature verification failed
Man, I am ticked. What now? Been reading for the past hour++. People elsewhere are saying to change the .bin extension to .zip, but I haven't seen that here on the XDA forum.
---------- Post added at 01:48 AM ---------- Previous post was at 01:11 AM ----------
Install from ADB complete: went through. After multiple tries, did 2 things at once so not sure which one it was
1) ran cmd prompt as Administrator
2) deleted all 5.3.1.1 bin files from computer, just in case what was gotten previously was corrupt, and redownloaded fresh file onto the ADB computer, instead of the copy and paste version from another computer

Thanks for making this guide! Worked perfect 1st time on my hd8 2016. Used rootjunky supertool to disable ota, install nova, disable ads Lockscreen, install Google play.
Just a thought, in the guide, you state, you could get es file Explorer from Amazon appstore, which would imply you have wifi on...which could get you updated to 5.3.2.1 without you knowing? Should prolly stick to sideloading ES only until ota is disabled.
Thanks again
From the time I turned the hd8 on for 1st time, I kept wifi off until I was rooted and able to disable ota.

I hope all you guys are also donating some bux to Kingoroot (I did).
We want to keep those geniuses happy and cranking out rooting updates for the v5.3.2.x builds!

Thanks so much for the guide. It was pretty easy to get through!
I have Nova Launcher running now and it is way better.
However, Auto Rotate screen isn't working quite right. If it is in Portrait, it will flip to landscape if I turn the tablet, but then it gets stuck in landscape which is the wrong landscape that I need for my Fire cover/stand.
Anyone else experiencing this?

Dumbest question:
the root is supposed to stay after turning the tablet off and on again, right?
I say this because went through the whole process successfully. New .bin. No errors on any commands. SuperSU installed binaries and then downloaded Root Checker and verified. Then verified su in adb shell. Then did pm disable of amazon apps and services,
and then turned tablet off and back on and Root Checker says NO ROOT. Root is supposed to stay, correct??? Or is it to just get all of the Amazon items off and customize tablet. Have rooted at least 8 or 9 devices, LG, Samsung, HTC etc, and this one has been the absolute _____ .

el7145 said:
Thanks for making this guide! Worked perfect 1st time on my hd8 2016. Used rootjunky supertool to disable ota, install nova, disable ads Lockscreen, install Google play.
Just a thought, in the guide, you state, you could get es file Explorer from Amazon appstore, which would imply you have wifi on...which could get you updated to 5.3.2.1 without you knowing? Should prolly stick to sideloading ES only until ota is disabled.
Thanks again
From the time I turned the hd8 on for 1st time, I kept wifi off until I was rooted and able to disable ota.
Click to expand...
Click to collapse
Thanks for pointing out the mistake, cause I had disable ota update by OpenDNS method before, so I was not aware of this.

imadiamond said:
Dumbest question:
the root is supposed to stay after turning the tablet off and on again, right?
I say this because went through the whole process successfully. New .bin. No errors on any commands. SuperSU installed binaries and then downloaded Root Checker and verified. Then verified su in adb shell. Then did pm disable of amazon apps and services,
and then turned tablet off and back on and Root Checker says NO ROOT. Root is supposed to stay, correct??? Or is it to just get all of the Amazon items off and customize tablet. Have rooted at least 8 or 9 devices, LG, Samsung, HTC etc, and this one has been the absolute _____ .
Click to expand...
Click to collapse
did you change the default access in SuperSU from prompt to grant? or have you disabled the OTA service?
in normal case, root will not lose till the OS updated.

Need to type exit, exit in shell to save settings?
phpbb88 said:
did you change the default access in SuperSU from prompt to grant? or have you disabled the OTA service?
in normal case, root will not lose till the OS updated.
Click to expand...
Click to collapse
Good question. Thanks for asking phpbb88! Definitely changed the default access. Rebooting here was one of the problems earlier since SuperSU says to reboot, then you must hit "Ok"-- and then logically, you would reboot. But instructions don't say to *ignore* and stay in SuperSU. Previously was rebooting, since Step 13 says "Open up SuperSU"... but SuperSU is already open in Step 12, so no need to open it up.
Only connected to the internet with it once, in December. Saw that everything needed an Amazon account, so have had wireless off/airplane mode ever since. Bought it with sole purpose to root.
The only thing I can think of would be not typing "exit" twice to get out of the shell. First read that instruction at the end of the pm disabling tutorial. If that's important than it needs to be added to the instructions also. Otherwise, when finished people will just power down the device or pull the USB plug. It's got to be written so that someone not knowing anything- first-time Kindle buyer like me , can do it. Here is the log.
[email protected]:/ $ su
[email protected]:/ # mount -w -o remount /system
[email protected]:/ # cd /sdcard/Kingo.to.SuperSU
[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/daemonsu
[email protected]:/sdcard/Kingo.to.SuperSU # chmod 0755 /system/xbin/daemonsu
[email protected]:/sdcard/Kingo.to.SuperSU # daemonsu -d &
[1] 7590
[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/su
[1] + Done daemonsu -d
[email protected]:/sdcard/Kingo.to.SuperSU # chmod 0755 /system/xbin/su
[email protected]:/sdcard/Kingo.to.SuperSU # rm /system/xbin/supolicy
[email protected]:/sdcard/Kingo.to.SuperSU # rm /system/bin/install-recovery.sh
[email protected]:/sdcard/Kingo.to.SuperSU # rm -rf /system/usr/iku
[email protected]:/sdcard/Kingo.to.SuperSU # rm -rf /sdcard/Kingroot
[email protected]:/sdcard/Kingo.to.SuperSU #
C:\Users\COMPUTER\AppData\Local\Android\Sdk\platform-tools>

smokejumper76 said:
I used eu.chainfire.supersu_2.79-SR3-279_minAPI7(nodpi)_apkmirror.com.apk for superSU...that would be another thing to check
Click to expand...
Click to collapse
ROOOOOOOOOOOOOOOOOTEEEDDDDDDDDDDDDDDD.
Final piece of puzzle I think it was the SuperSU I had. Didn't do any other changes. Got it from appsapk.com . FOLKS, do not use any SuperSU you get from there (or anywhere else) at least for this process. You'll end up chasing squirrels. It *might* have gone through even with the other errors etc (like phpbb88 mentioned it did for him), but the wrong SuperSU probably killed everything in the end. Go to https://apkdot.com/apk/chainfire/sup...ersu-2-79-sr3/ and get your SuperSU there: thank you for the suggestion smokejumper76. For one, immediately noticed the app logo was different. Also took longer to load the binaries. Whatever the other SuperSU apk is I'm deleting it now: don't even want to know the version.
phpbb88, I see you added the answer to my question about which option to pick in SuperSU (Normal) to the instructions. Thanks! Would also suggest 1) to add a note NOT to reboot even though SuperSU asks to, since in the next line you say "Open SuperSU" but it's already open and 2) the link for the proper SuperSU in the credits at the end, or the file even.
This was Christmas gift for my gf... now she can use it. Was planning on getting a HD10 for myself, but it's been so long that unfortunately now it might ship with newer software. Might buy one from a retail store as they will have older stock, and the return will be a quick walk-in if it's got 5.3.+.+ .

imadiamond said:
ROOOOOOOOOOOOOOOOOTEEEDDDDDDDDDDDDDDD.
Final piece of puzzle I think it was the SuperSU I had. Didn't do any other changes. Got it from appsapk.com . FOLKS, do not use any SuperSU you get from there (or anywhere else) at least for this process. You'll end up chasing squirrels. It *might* have gone through even with the other errors etc (like phpbb88 mentioned it did for him), but the wrong SuperSU probably killed everything in the end. Go to https://apkdot.com/apk/chainfire/sup...ersu-2-79-sr3/ and get your SuperSU there: thank you for the suggestion smokejumper76. For one, immediately noticed the app logo was different. Also took longer to load the binaries. Whatever the other SuperSU apk is I'm deleting it now: don't even want to know the version.
phpbb88, I see you added the answer to my question about which option to pick in SuperSU (Normal) to the instructions. Thanks! Would also suggest 1) to add a note NOT to reboot even though SuperSU asks to, since in the next line you say "Open SuperSU" but it's already open and 2) the link for the proper SuperSU in the credits at the end, or the file even.
This was Christmas gift for my gf... now she can use it. Was planning on getting a HD10 for myself, but it's been so long that unfortunately now it might ship with newer software. Might buy one from a retail store as they will have older stock, and the return will be a quick walk-in if it's got 5.3.+.+ .
Click to expand...
Click to collapse
Glad to hear that you can finally root your fire.
In fact, I never typed exit twice in adb shell, I just close it...lol
1) After SuperSU updates its binary, I followed the reboot, still success to root my device.
2) I am using the SuperSU apk download from apkpure linked above, why don't you download it in the first try...?
I went to appsapk.com and have a look of the SuperSU, it is totally a different app.

Thanks for the Guide finally got root!

phpbb88 said:
in step 10, install SuperSU but do not open it.
your log should have no problem, maybe try again from clean state? (clean 5.3.1./5.3.1.1 state)
PS. you should choose "normal" when update binary
Click to expand...
Click to collapse
I had the exact same problem over and over finally tried this:
change this: rm /system/bin/install-recovery.sh
To this: rm install-recovery.sh