• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root getting multitasking for sense 5 help

maybe a good idea to move this all out to a separate thread.
Yes, I agree.

I'm out and about right now. Do your thing.
Stuff happens and I think we agree that what happened wasn't caused by the rom itself or anything like that
I am not quite sure what caused it, so for now... I am happy, again.
 
Yep and ask away if his instructions for moving it give any grief.

Btw - two things to put on your list.

First, make sure that you've got Fastboot off in main settings, power.

Second, as soon as conveniently possible, test a simple "adb reboot" command (just that will be fine while running).

If you can get to it with adb, you can get to with fastboot and that's a must for extreme error recovery.

If not, fix your sdk tools or drivers or whatever right away so you can have fastboot and adb at your fingertips.

Hmmmm.

Also maybe a good idea to move this all out to a separate thread.

Stuff happens and I think we agree that what happened wasn't caused by the rom itself or anything like that.

If you agree and you're at a pc, please go for it. :)
Daemon starts successfully. ;)
I also noticed after running daemon, all the apps inside my folders are now duplicate.


Now I need an easy less complicated steps to get sense 5 multitasking working on this here ROM. All the above steps I've tried, and nothing seems to work for me...why, maybe because I'm not able to understand certain terminology being used.

Today is my birthday and I'm spending the day with you guys ... But don't expect me to be here all night.
 
Ok, do this exactly. Commands that you copy/paste are in red.

Stop at any step that fails or is confusing. Please don't tinker. ;) :)

Read the steps as you go along, don't just copy/paste. You'll see why.

It's really best to copy/paste rather than try to type the commands.

1. Get the new SystemUI.apk into the same folder that adb is in, your sdk tools. We're going for the easy way here.

2. Plug in your phone, running normally, and confirm that adb is connecting.

adb devices

3. Confirm that it returns a response, something like - HT25FS409294

4. Let's get to recovery the easy way.

adb reboot recovery

5. The command will return and rather than using cool adb tricks, just wait patiently until your TWRP main screen appears.

6. Tap mount button on your phone.

7. Checkbox - System

8. Back key, let's get out of there.

9. On PC:

adb shell

10. You are now inside the phone in its command window.

11. Check that your prompt ends with the # character. If it does not and ends with the $ character instead then do this -

su

12. Check that your prompt ends with the # character. It should look something like this.

~ # _

13. Go to /system/app folder.

cd /system/app

14. Preserve existing SystemUI.apk

mv SystemUI.apk SystemUI.apk.bak

15. Go back to your pc.

exit

16. Now copy the new SystemUI by pushing it through the usb cable.

adb push SystemUI.apk /system/app

17. Almost done, let's spruce it up. Go back into the phone, do the following:

adb shell

(^ you already know to make sure that you see the # prompt make sure right now)

cd /system/app

chmod 644 SystemUI.apk

exit

18. All done, let's go!

adb reboot

19. Profit!

20. Happy birthday!

 
I can't find the Sprint Zone application anywhere ....

I guess we were posting at the same time, EM. ;)
 
After you grow comfortable with those adb basics - getting in, moving around, doing stuff, getting out - we'll show the fancy shortcuts if you want to learn them.

Because you're copy/pasting today, I wanted to show the operations and no time is lost because - copy/paste.

Personally, I just do everything the long way.
 
I appreciate everything you do here... :)

Nope! No Sprint Zone application was found in app search. So I went ahead and installed the posted .APK I found over XDA.

Okay, back to schooling schedule ... ;)


I copy/paste 'adb devices' inside command prompt -- "List of devices attached FA33YS400867 Device".

I'm about to enter "adb reboot recovery' -- I won't be able to use my phone it seems with this process.

Will post when I can.
Simple steps works great for me. ;)

After you grow comfortable with those adb basics - getting in, moving around, doing stuff, getting out - we'll show the fancy shortcuts if you want to learn them.
I'm game with this...:)
 
Okay ... I got the ~ # _ character.

Do i copy/paste the below in command window as the ones before? I'm just asking, because you said.. go back to your PC.

13. Go to /system/app folder.

cd /system/app

14. Preserve existing SystemUI.apk

mv SystemUI.apk SystemUI.apk.bak
 
Did you copy/paste through step 14 where it shows the #?

If not, go ahead.

Then exit in 15 to return to pc.
Yes... I did.

I'm at #16. I already have the .apk installed.

I rebooted the phone in order to installed the .apk. The screen is black, shows the clock and everything, but i can't open the lock or nothing.
 
I'm getting an error with the following ... cd /system/app

chmod 644 SystemUI.apk

exit

18. All done, let's go!

adb reboot

19. Profit!

After each one... I should press enter, right?
 
Those need to be entered while phone is in TWRP, system mounted, inside adb shell with # prompt.

Yes, enter after each one.

If not in # but still in Windows, please show me the output of

adb shell ls -l /system/app/SystemUI*
 
C:\sdk-tools\sdk-tools>adb devices
List of devices attached
FA33YS400867 device


C:\sdk-tools\sdk-tools>adb reboot recovery

C:\sdk-tools\sdk-tools>adb shell
~ # ←[6ncd /system/app
cd /system/app
/system/app # ←[6nmv SystemUI.apk SystemUI.apk.bak
mv SystemUI.apk SystemUI.apk.bak
/system/app # ←[6nexit
exit

C:\sdk-tools\sdk-tools>adb shell
sh-3.2# cd /system/app
cd /system/app
sh-3.2# chmod 644 SystemUI.apkexit
chmod 644 SystemUI.apkexit
Unable to chmod SystemUI.apkexit: No such file or directory
sh-3.2# chmod 644 SystemUI.apk
chmod 644 SystemUI.apk
Unable to chmod SystemUI.apk: No such file or directory
sh-3.2#
C:\sdk-tools\sdk-tools>adb shell ls -l /system/app/SystemUI*
-rw-r--r-- 1 root root 2631358 Aug 1 2008 /system/app/SystemUI.ap
k.bak

C:\sdk-tools\sdk-tools>
 
OK, it didn't copy over.

Confirm that SystemUI.apk is in your sdk tools folder.

dir SystemUI*

If it is, then do -

adb push SystemUI.apk /system/app

adb shell chmod 644 /system/app/SystemUI.apk

adb shell ls -l /system/app/SystemUI*
 
C:\sdk-tools\sdk-tools>adb devices
List of devices attached
FA33YS400867 device


C:\sdk-tools\sdk-tools>adb reboot recovery

C:\sdk-tools\sdk-tools>adb shell
~ # ←[6ncd /system/app
cd /system/app
/system/app # ←[6nmv SystemUI.apk SystemUI.apk.bak
mv SystemUI.apk SystemUI.apk.bak
/system/app # ←[6nexit
exit

C:\sdk-tools\sdk-tools>adb shell
sh-3.2# cd /system/app
cd /system/app
sh-3.2# chmod 644 SystemUI.apkexit
chmod 644 SystemUI.apkexit
Unable to chmod SystemUI.apkexit: No such file or directory
sh-3.2# chmod 644 SystemUI.apk
chmod 644 SystemUI.apk
Unable to chmod SystemUI.apk: No such file or directory
sh-3.2#
C:\sdk-tools\sdk-tools>adb shell ls -l /system/app/SystemUI*
-rw-r--r-- 1 root root 2631358 Aug 1 2008 /system/app/SystemUI.ap
k.bak

C:\sdk-tools\sdk-tools>dir SystemUI*
Volume in drive C has no label.
Volume Serial Number is 62D5-9A89

Directory of C:\sdk-tools\sdk-tools

11/10/2013 03:19 PM 4,434,563 SystemUI (1).apk
1 File(s) 4,434,563 bytes
0 Dir(s) 64,548,040,704 bytes free

C:\sdk-tools\sdk-tools>adb push SystemUI.apk /system/app
cannot stat 'SystemUI.apk': No such file or directory

C:\sdk-tools\sdk-tools>adb shell chmod 644 /system/app

C:\sdk-tools\sdk-tools>adb shell ls -l /system/app/SystemUI*
-rw-r--r-- 1 root root 2631358 Aug 1 2008 /system/app/SystemUI.ap
k.bak

C:\sdk-tools\sdk-tools>
 
Please don't repeat all of the steps.

Please see my previous two posts.

Do the TWRP post first, then the steps just above it.


Your output says that you don't have the SystemUI.apk in your sdk tools folder.
 
Please don't repeat all of the steps.

Please see my previous two posts.

Do the TWRP post first, then the steps just above it.


Your output says that you don't have the SystemUI.apk in your sdk tools folder.
I didn't .... I copy the results after following the steps you provided.

Post #46 is the result.
 
Back
Top Bottom