[RECOVERY+LOKI][CWM][MDK][VZW] SCH-I545 CWM v1.0 - Verizon Samsung Galaxy S 4

DISCLAIMER:
Your device, your responsibility. I am not liable for anything you flash, including this.
As a result you'll probably want to read the rest of the thread and at least be aware of what you're flashing.
You've been warned.
CM: CWM Based Recovery for SCH-I545 (jfltevzw)​
Features:
This is comes from CM as it is provided in the source repos. I will be keeping it as such at this time.
If modifications deviate from CM source we will set up a new repo.
The recovery image has already been patched using the Loki method.
This also means it is tied to MDK signature and should only be flashed on MDK.
Screenshots: None
Latest Build: v1.1
Tar/ZIP Mirror: [CWM][RECOVERY]Team SXTP CWM for Galaxy S4 (Team SXTP Site)
Flash Instructions - READ THESE CAREFULLY!!!
1) Download Zip
2) Unpack Zip and place items on your phone. Assumes you're doing commands from folder where files were extracted to.
For the sake of testing let's say /data/local/tmp like djrbliss used. (ADB push was used in that example)
Code:
adb push recovery.lok /data/local/tmp/
adb push loki_flash /data/local/tmp/
3) Go to ADB shell, su and flash using following commands: (assumes path is /data/local/tmp for Step 2)
Code:
adb shell
su
chmod 755 /data/local/tmp/loki_flash
/data/local/tmp/loki_flash recovery /data/local/tmp/recovery.lok
If successful you should see something similar to:
Code:
[+] Loki validation passed, flashing image.
2253+1 records in
2253+1 records out
9230848 bytes transferred in 0.656 secs (14071414 bytes/sec)
[+] Loki flashing complete!
Assuming you see the above, you should be ready to boot to recovery.
If you do not see this you should immediately flash the stock recovery by dd.
If you don't know how to do that, stop, ask for help. Let's try not to brick a phone doing this, okay?
Summary Changelog:
Code:
v1.1 - Correct typo on device name (in CM device tree). Repo was still okay.
v1.0 - Initial based on Sprint progress (jf series shares same fstab)
Source:
CyanogenMod Official Repositories
Device Dependencies:
android_device_samsung_jf-common
android_device_samsung_msm8960-common
android_device_samsung_qcom-common
Verizon GS4 Device Repository
NOTE: Due to potential copyright issues I do not include a vendor repo.
You can extract the files from the phone or ROM as needed - should you decide to build on your own.
Credits:
Early Bringup Advice: Entropy512, Shabbypenguin, Cordell12
Current Advisors/Collaborators: Noobnl (CM CDMA Maintainer)
Testers: Mohogalore, robbyamor, crawj and others
Steve Kondik (Cyanogen) for CM development and jf common work
The CM maintainters who continue to improve CM along with Mr. Kondik
The crew that is Paranoid Android - Pure Hybrid!
Djrbliss for the Loki Method. (and for permission to include loki_flash in the zip!)
...and of course! You, the community, for your support as well! Thank you!

OP has been updated with a Loki patched recovery image and flash instructions.
If you run into problems, STOP and post here with the issue.
Let's do this as safely as possible until we confirm some safe flashes.

Again, asking that anyone who flashes this post their results. Obviously a lot of folks watching and although it shouldn't be an issue everyone likes to wait for first outside validation before flashing.

If it helps at all, I used the same process for the most part. It does indeed work.
1|[email protected]:/ # /data/local/tmp/loki_flash recovery /data/local/tmp/twrp.lok
covery /data/local/tmp/twrp.lok <
[+] Loki validation passed, flashing image.
2559+1 records in
2559+1 records out
10484224 bytes transferred in 0.713 secs (14704381 bytes/sec)
[+] Loki flashing complete!
only difference is I used TWRP

NxtGenCowboy said:
If it helps at all, I used the same process for the most part. It does indeed work.
1|[email protected]:/ # /data/local/tmp/loki_flash recovery /data/local/tmp/twrp.lok
covery /data/local/tmp/twrp.lok <
[+] Loki validation passed, flashing image.
2559+1 records in
2559+1 records out
10484224 bytes transferred in 0.713 secs (14704381 bytes/sec)
[+] Loki flashing complete!
only difference is I used TWRP
Click to expand...
Click to collapse
where'd you get the twrp.lok file? following djrbliss' instructions?

t3project said:
where'd you get the twrp.lok file? following djrbliss' instructions?
Click to expand...
Click to collapse
No.
thats what I renamed it to since I used a twrp img

im losing my damn mind. someone care to explain this?
Code:
[email protected]:/sdcard # /sdcard/loki_flash recovery /sdcard/twrp.lok
/sdcard/loki_flash recovery /sdcard/twrp.lok
sh: /adcard/loki_flash: not found
127|[email protected]:/sdcard #
i get this after a chmod of loki_flash. if i dont do chmod on it it says it cannot find the file loki_flash.....wtf?
Code:
[email protected]:/sdcard # /sdcard/loki_flash recovery /sdcard/twrp.lok
/sdcard/loki_flash recovery /sdcard/twrp.lok
sh: /sdcard/loki_flash: can't execute: Permission denied
126|[email protected]:/sdcard #

t3project said:
im losing my damn mind. someone care to explain this?
Code:
[email protected]:/sdcard # /sdcard/loki_flash recovery /sdcard/twrp.lok
/sdcard/loki_flash recovery /sdcard/twrp.lok
sh: /adcard/loki_flash: not found
127|[email protected]:/sdcard #
i get this after a chmod of loki_flash. if i dont do chmod on it it says it cannot find the file loki_flash.....wtf?
Code:
[email protected]:/sdcard # /sdcard/loki_flash recovery /sdcard/twrp.lok
/sdcard/loki_flash recovery /sdcard/twrp.lok
sh: /sdcard/loki_flash: can't execute: Permission denied
126|[email protected]:/sdcard #
Click to expand...
Click to collapse
Derp. What permissions are you giving it?

NxtGenCowboy said:
No.
thats what I renamed it to since I used a twrp img
Click to expand...
Click to collapse
I tried just renaming the .img file to .lok, but it gave me a few errors. So using djrbliss's Loki tool (much thanks!) I generated a file for the TWRP recovery.
Here is the link: twrp.lok - 10.00 MB
---------- Post added at 02:52 PM ---------- Previous post was at 02:50 PM ----------
t3project said:
im losing my damn mind. someone care to explain this?
Code:
[email protected]:/sdcard # /sdcard/loki_flash recovery /sdcard/twrp.lok
/sdcard/loki_flash recovery /sdcard/twrp.lok
sh: /adcard/loki_flash: not found
127|[email protected]:/sdcard #
i get this after a chmod of loki_flash. if i dont do chmod on it it says it cannot find the file loki_flash.....wtf?
Code:
[email protected]:/sdcard # /sdcard/loki_flash recovery /sdcard/twrp.lok
/sdcard/loki_flash recovery /sdcard/twrp.lok
sh: /sdcard/loki_flash: can't execute: Permission denied
126|[email protected]:/sdcard #
Click to expand...
Click to collapse
You have to put the files in a folder like /data/local/tmp since the sdcard folder does not allow executables contrary to the instructions provided. (At least that was my understanding when trying to debug the same issue!)

fallingup said:
Derp. What permissions are you giving it?
Click to expand...
Click to collapse
all the good ones. haha 755
trvrlol said:
I tried just renaming the .img file to .lok, but it gave me a few errors. So using djrbliss's Loki tool (much thanks!) I generated a file for the TWRP recovery.
Here is the link: twrp.lok - 10.00 MB
---------- Post added at 02:52 PM ---------- Previous post was at 02:50 PM ----------
You have to put the files in a folder like /data/local/tmp since the sdcard folder does not allow executables contrary to the instructions provided.
Click to expand...
Click to collapse
lol.....see told you i was losing it

I get a successful flash but still only get stock android recovery. I think it is because I can't find the install reovery.sh to delete it

mikebuck69 said:
I get a successful flash but still only get stock android recovery. I think it is because I can't find the install reovery.sh to delete it
Click to expand...
Click to collapse
It's in /system/etc.

I think I read in the other thread, they had success doing this on the pre-release kernal.
Sent from my SCH-I545 using Xparent Green Tapatalk 2

garwynn said:
It's in /system/etc.
Click to expand...
Click to collapse
not on my S4 it isn't lol. I get the successful flash, reboot to recovery, get stock recovery, reboot system from there and I then get the Samsung logo with the unlocked padlocked telling me SOMEthing unnoficiall got installed. Phone boots up and I boot back into recovery, still stock recovery, reboot system again and I get normal boot up, no padlock screen. I'm still on the mdk kernel so I will try flashing the pre-release kernel a little later and trying again.

I see a recovery-resource.dat in /system/etc but not recovery.sh.
Sent from my SCH-I545 using Xparent Green Tapatalk 2

You can use GooManager and install Twrp... Just have root first.

NxtGenCowboy said:
You can use GooManager and install Twrp... Just have root first.
Click to expand...
Click to collapse
Have you done this? I tried it on a (locked bootloader) Note 2 and got the screen that I needed to take the phone to a Verizon store. It took me an hour or more to fix it.
Sent from my SCH-I545 using Xparent Green Tapatalk 2

NxtGenCowboy said:
You can use GooManager and install Twrp... Just have root first.
Click to expand...
Click to collapse
I tried that and got the "You have installed unofficial blah blah contact Verizon" message. I had to generate a TWRP loki image and flash using the OP's instructions.

It works fine. Make sure you are rooted.

NxtGenCowboy said:
It works fine. Make sure you are rooted.
Click to expand...
Click to collapse
Yea they posted an updated release already that is Loki modified, so you are actually correct!

Related

Snowball Mod

I ran the Snowball Mod without a hitch. I then tried to run the update but it won't run for some reason. The window flashes some text quickly but then closes so I'm not even really sure why it's not working. Anyone run into this or have any ideas. Thanks in advance!
I haven't had the time to try out the snowball mod, yet -- so I can't offer any advice. But, I would post the issue in the development thread, that's where the most help will be.
Swyped from my B&N Nook Tablet.
Try running it from a command line to keep it up and be able to read any text.
Also, there is a log.txt, if you post that, it can be more helpful.
Yeah I was goin to but I don't have enough posts. I was hoping someone would see it here.
Well... if you post your log.txt and start it from a command-line window rather than double clicking the update.bat, then we can take a look at what's up.
Log file says:
Snowball is reporting: v2.0.2
NO PACKAGE AVAILABLE
Command line:
Snowball is reporting: v2.0.2
There does not appear to be a package for the version snowball is reporting.
Are you sure you're not reapplying an update?
Perhaps you are accidentally trying to apply an "outdate"?
Thanks a lot!
There is no v2.0.2 update package in the zip folder. I renamed v2.0.1 to v2.0.2 and ran. Not sure if this was a good thing to do or not. Any help or direction would be appreciated. Thanks.
No write permissions
Tried to install snowball mod from a macbook pro by just running the snowball.sh. Started up and the B&N stuff was all there, although it looked like it ran without a hitch.
Looked at the log file in the snowball-mod folder and saw a lot of "Read-only file system" business. The first few lines being:
unzip: can't open nook-update-package.zip, nook-update-package.zip.zip, nook-update-package.zip.ZIP^M
rm failed for nook-update-package.zip, Read-only file system^M
Installing nook-update-package...
cd: can't cd to /mnt/media/nook-update-package^M
sh: Can't open install^M
rm failed for /mnt/media/nook-update-package, No such file or directory^M
Click to expand...
Click to collapse
How do you suggest I get around that?
conundrum768 said:
I haven't had the time to try out the snowball mod, yet -- so I can't offer any advice. But, I would post the issue in the development thread, that's where the most help will be.
Swyped from my B&N Nook Tablet.
Click to expand...
Click to collapse
We need 10 legit posts before we are allowed to post in the dev forum
Robotronik said:
Tried to install snowball mod from a macbook pro by just running the snowball.sh. Started up and the B&N stuff was all there, although it looked like it ran without a hitch.
Looked at the log file in the snowball-mod folder and saw a lot of "Read-only file system" business. The first few lines being:
How do you suggest I get around that?
Click to expand...
Click to collapse
Huh... this is weird... /mnt/media should not be read-only... although, I suppose, perhaps if you had it USB mounted, it might end up read-only.
Ensure that you have Automatic USB mounting turned off before you run the script.
You can actually push this update via wifi if you mod the update.bat (or update.sh for linux users) file.
Just turn on ADB Wifi (I prefer adbWireless app) and add the following to your bat file:
Code:
echo Waiting for device...
[B]adb connect XXX.XXX.XXX.XXX:XXXX[/B]
adb wait-for-device
...
adb shell "chmod 755 /data/local/tmp/update-package.sh ; su -c /data/local/tmp/update-package.sh" >> log.txt
if exist reboot adb reboot
[B]adb connect XXX.XXX.XXX.XXX:XXXX[/B]
echo INSTALLATION SUCCESSFUL
Use your IPort given to you by your ADB Wifi app in place of XXXs. Then just run the .bat!
Run from cmd if you don't want the output to vanish right away.
cfoesch said:
Ensure that you have Automatic USB mounting turned off before you run the script.
Click to expand...
Click to collapse
Okay, that got me a little further. Now:
Extracting nook-update-package...
Archive: nook-update-package.zip
creating: nook-update-package/data/
unzip: can't set permissions of directory 'nook-update-package': Operation not permitted
unzip: exiting
Installing nook-update-package...
sh: Can't open install
Click to expand...
Click to collapse
More permissions issues...
Still posting here because I don't have the 10 total posts to go in the Dev forum...
Anyway, I did the factory reinstall, and reran the snowballmod update. It said the root was still there, so I commented out that check from the snowball.sh, reran the package and everything went swimmingly.
Now, for the update:
The terminal spits out this:
Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
7 KB/s (46 bytes in 0.006s)
Snowball is reporting: v2.0.2
.zipte-package-v2.0.2
There does not appear to be a package for the version snowball is reporting.
Are you sure you're not reapplying an update?
Perhaps you are accidentally trying to apply an 'outdate'?
Click to expand...
Click to collapse
Where the log file gives me:
Snowball is reporting: v2.0.2
NO PACKAGE AVAILABLE
Click to expand...
Click to collapse
The file "update-package-v2.0.2.zip" is in the directory. In the "update.sh" file replaced all instances of "${VERSION}" with "v2.0.2" and it seemed to work fine.
same
Robotronik said:
Still posting here because I don't have the 10 total posts to go in the Dev forum...
Anyway, I did the factory reinstall, and reran the snowballmod update. It said the root was still there, so I commented out that check from the snowball.sh, reran the package and everything went swimmingly.
Now, for the update:
The terminal spits out this:
Where the log file gives me:
The file "update-package-v2.0.2.zip" is in the directory. In the "update.sh" file replaced all instances of "${VERSION}" with "v2.0.2" and it seemed to work fine.
Click to expand...
Click to collapse
I AM HAVING THE SAME PROBLEM.MYBE..I need help some plz make a better howtos for dummies m
The first thing you need to do, if you have no clue what you're doing, is post the contents of the log file in the snowballmod folder.
The ".zipte-package-v2.0.2" seems to be related to adb shell "snowball-ver" returning DOS formatted text, even though you're in a *nix. I really did not expect this to happen with the linux and osx versions of adb, but apparently, they perform the same as cygwin... (cygwin I expected, after all, the adb.exe is a windows program). I will fix the update scripts to take that into account.
Code:
unzip: can't set permissions of directory 'nook-update-package': Operation not permitted
This message is reported by unzip when it is run by a non-root user on the /mnt/media partition.
You do _NOT_ have to run snowball-update though if you've installed snowball-mod fresh with the most recent version.
robtlebel said:
I AM HAVING THE SAME PROBLEM.MYBE..I need help some plz make a better howtos for dummies m
Click to expand...
Click to collapse
The changes made to the script were posted here:
Robotronik said:
Now, for the update:
The terminal spits out this:
Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
7 KB/s (46 bytes in 0.006s)
Snowball is reporting: v2.0.2
.zipte-package-v2.0.2
There does not appear to be a package for the version snowball is reporting.
Are you sure you're not reapplying an update?
Perhaps you are accidentally trying to apply an 'outdate'?
Where the log file gives me:
Snowball is reporting: v2.0.2
NO PACKAGE AVAILABLE
The file "update-package-v2.0.2.zip" is in the directory. In the "update.sh" file replaced all instances of "${VERSION}" with "v2.0.2" and it seemed to work fine.
Click to expand...
Click to collapse
I had the same issue with the name of the update file being called incorrectly: ".zipte-package-v2.0.2". With that output the script is looking for a file of that name and it's not finding it. I just changed the value of the variable ${VERSION} to v2.0.2 (since that was what was being reported by Snowball as my current version) and all worked after that.
Easy to fix temporarily:
-open "update.sh" in a text editor
-go to line 66 and change
VERSION=`awk '//{ print $2 }' snowball.version`
Click to expand...
Click to collapse
to
VERSION=v2.0.2
Click to expand...
Click to collapse
or whatever version yours shows to be running (v2.0.1, etc). Something tells me it might be important to input the correct current version number in
-save and close the file and rerun it.
EDIT: or wait until cfoesch fixes the scripts
Scripts should be updated. I changed the awk program from just "//{ print $2 }" to "//{ sub('\r', '', $2); print $2 }" ... this means that it works both ways... *insert your favorite "both ways" joke here*
It should also detect if you haven't turned off automount, and warn you about it. If the nook ends up rebooting, then it would tear the USB mount and could cause file corruption. I got around it by putting things in /data rather than /mnt/media, but then realized, if it has to reboot, then it could cause trouble. So better, to just warn them that automount was on, and quit out.
It also detects better if something went wrong in the installation process, and should report that installation has failed, rather than successful under all cases.
Things may have gotten broken in the process, so keep up the bug reports.
I just can't stop Nookin' Around.........god i need to sleep
I decided to check out the update.sh script (can only go so far currently since I have the latest update).
At least for me, (Ubuntu Linux 11.10) I figured something out about the $OSTYPE call to set the $adb variable. I could echo $OSTYPE in the terminal and got a response, but could not echo it in any scripts. Ended up finding the "uname -o" call and that seems to have gotten it to work, although the printout is different.
snowball-update# echo $OSTYPE
linux-gnu
snowball-update# uname -o
GNU/Linux
Changed lines 7 & 8 and seems to have worked:
case `uname -o` in
GNU*|linux*|Linux*)
Now this last part is probably something on my end but: update.sh: 62: ./adblinux: Permission denied
Thanks again for the work (and everyone else involved in rooting/hacking these things )
Indeed. $OSTYPE seems to be specific to bash, and not all sh implementations.
If you don't mind could you do this command and give me the output? "ls -l /bin/sh" and "sh --version" Those two commands should explain exactly which implementation of sh you have. (For instance, on the NT with snowball-mod, the sh is a minimal implementation, and does not support $OSTYPE. But on most OSes I've seen sh is actually a statically linked bash, as it is the most widely used shell scripting language.)
The case on that you provided though could be a poor choice, as GNU*) would match GNU/freebsd, or GNU/openbsd, or GNU/anykernel. Sure it is unlikely, but it is possible.
The permissions issue is not entirely your end, but it is an expected artifact of extracting from a zip file. Although, is suppose performing a chmod 755 on it prior to use would be a good idea in general.

[Q] Rooting the Fusion 2

Can anyone advise if the Huawei-U8665 (At&T Fusion 2) can be rooted? It has Android version 2.3.6. I tried with the easy OneSuperClick approach but didn't work-wouldn't recognize device. Thanks.
ptbear said:
Can anyone advise if the Huawei-U8665 (At&T Fusion 2) can be rooted? It has Android version 2.3.6. I tried with the easy OneSuperClick approach but didn't work-wouldn't recognize device. Thanks.
Click to expand...
Click to collapse
Did you ever figure out how to root?
Why don't you Google search other huawei devices and look for root kit running Gingerbread
Sent from my LGL35G using xda premium
903tex said:
Why don't you Google search other huawei devices and look for root kit running Gingerbread
Sent from my LGL35G using xda premium
Click to expand...
Click to collapse
I have, and I haven't been able to find anything. Superoneclick, z4root and unlock root only work for 2.3 and the Fusion 2 is running 2.3.6 and while trying to use those tools to root, it always hangs when trying to gain shell root.
Have to wait til somebody with skills makes a exploit for the fusion.
Sent from my LGL35G using xda premium
Patience is a virtue I supposed. I should've just bought a galaxy player I guess.
I seem to have acquired root, but I had to use fastboot to restore the rom. Sry i cant be more specific because tthis touchscreen took a hard fall..... post later thx -RFE
RFE said:
I seem to have acquired root, but I had to use fastboot to restore the rom. Sry i cant be more specific because tthis touchscreen took a hard fall..... post later thx -RFE
Click to expand...
Click to collapse
i keep posting to the wrong threas. sry
hint hint....... u need the diag drivers which are not posted but i should have a recovery img ready soon (one that re-installs SU on each boot
RFE said:
i keep posting to the wrong threas. sry
hint hint....... u need the diag drivers which are not posted but i should have a recovery img ready soon (one that re-installs SU on each boot
Click to expand...
Click to collapse
these are the right drivers for adb
RFE said:
these are the right drivers for adb
Click to expand...
Click to collapse
hi guys, here is a copy of the latest and greatest adb driver sets. with this driver set (folder called 'Driver' if you don't need adb).
I now HAVE ROOT on the phone by using fastboot and modifying the recovery image. I will post these once I strip it of all my personal info. Please try your own methods as well. I have attached a screenshot of what your (x86) device manager should look like once you correctly installed the drivers.
Best wishes & happy rooting
RFE said:
hi guys, here is a copy of the latest and greatest adb driver sets. with this driver set (folder called 'Driver' if you don't need adb).
I now HAVE ROOT on the phone by using fastboot and modifying the recovery image. I will post these once I strip it of all my personal info. Please try your own methods as well. I have attached a screenshot of what your (x86) device manager should look like once you correctly installed the drivers.
Best wishes & happy rooting
Click to expand...
Click to collapse
Here is a clip of adb working. I am trying to get clockworkmod working, but it is difficult because of all this new 2.3.6 securiy (my last phone was a 2.3.4)
D:\android-sdk-windows\platform-tools>adb tcpip 8888
restarting in TCP mode port: 8888
D:\android-sdk-windows\platform-tools>adb root
error: device not found
D:\android-sdk-windows\platform-tools>adb usb
error: device not found
D:\android-sdk-windows\platform-tools>adb get-state
unknown
D:\android-sdk-windows\platform-tools>adb shell
$ exit
exit
D:\android-sdk-windows\platform-tools>adb reboot-bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
D:\android-sdk-windows\platform-tools>adb root
adbd cannot run as root in production builds
(you must copy certain files to the device via adb push/pull & you can have root too)
---------- Post added at 04:14 PM ---------- Previous post was at 03:46 PM ----------
I dumped the entire phone in user mode and this is what you get:
(let me know if you need anything)
Device connected.
Default pull path saved.
Detailed phone info: RECOVERY ACTIVE
Pulling file or directory from data/app/... successful.
Pulling file or directory from data/app_private/... failed.
Pulling file or directory from data/data/... successful.
Pulling file or directory from data/local/... successful.
Pulling file or directory from data/nv/... failed.
Pulling file or directory from data/system/... successful.
Pulling file or directory from system/app/... failed.
Pulling file or directory from system/bin/... successful.
Pulling file or directory from system/etc/init.d/... failed.
Pulling file or directory from system/fonts/... successful.
Pulling file or directory from system/framework/... successful.
Pulling file or directory from system/media/... successful.
Pulling file or directory from system/usr/keylayout/... successful.
\android-sdk-windows\f2pull1
05 <DIR> .
05 <DIR> ..
56 1,697 7k_handset.kl
56 3,894 7x27a_kp.kl
43,652 abtfilt
51 0 accounts.db-journal
55,168 akmd8962
55,168 akmd8975
191 am
313 am.jar
27,864 am.odex
5,520 amploader
313 android.policy.jar
248,448 android.policy.odex
313 android.test.runner.jar
193,944 android.test.runner.odex
58,132 applypatch
5,720 app_process
71,736 ast-mm-vdec-omx-test7k
17,076 ATFWD-daemon
24,064 athtestcmd
631,588 ath_supplicant
<DIR> audio
56 245 AVRCP.kl
5,504 battery_charging
5,292 bluetoothd
199 bmgr
313 bmgr.jar
13,784 bmgr.odex
23,208 bootanimation
23,192 bootanimationex
313 bouncycastle.jar
778,624 bouncycastle.odex
10,196 brcm_patchram_plus
33,428 bridgemgrd
380,435 btld
5,556 bugreport
5,360 callife
145,156 charge
14,404 CKPD-daemon
6,880 Clockopia.ttf
22,788 cnd
313 com.android.location.provider.jar
7,352 com.android.location.provider.odex
1,671 com.cequint.platform.jar
1,984 com.cequint.platform.odex
313 com.google.android.maps.jar
388,168 com.google.android.maps.odex
313 com.qualcomm.location.vzw_library.jar
46,000 com.qualcomm.location.vzw_library.odex
120,332 compassd
313 core-junit.jar
23,952 core-junit.odex
22,926 core.jar
4,801,784 core.odex
5,520 dalvikvm
109,504 dbus-daemon
18,112 debuggerd
9,796 dexopt
44,612 dhcpcd
102,056 dhd
5,648 diag_klog
5,568 diag_mdlog
108,820 dnsmasq
194,488 DroidSans-Bold.ttf
190,776 DroidSans.ttf
35,880 DroidSansArabic.ttf
3,725,920 DroidSansFallback.ttf
23,076 DroidSansHebrew.ttf
119,380 DroidSansMono.ttf
36,028 DroidSansThai.ttf
185,228 DroidSerif-Bold.ttf
190,304 DroidSerif-BoldItalic.ttf
177,560 DroidSerif-Italic.ttf
172,916 DroidSerif-Regular.ttf
56,468 ds_fmc_appd
34,544 dumpstate
9,812 dumpsys
5,548 dvz
204,900 e2fsck
313 ext.jar
1,393,000 ext.odex
06 60,920,794 fastboot-tools-full-copy-HUAWEI-U8665-EN-NONIG
rar
9,968 filebackup
14,084 fmconfig
360,282 framework-res-hwext.apk
10,368,022 framework-res.apk
12,413 framework.jar
9,007,376 framework.odex
22,640 fsck_msdos
35,028 ftmdaemon
5,604 gzip
27,652 hciattach
5,684 hci_dev_state
277,652 hostapd
22,420 hostapd_cli
5,440 hostapd_wps
9,920 hwvefs
194 ime
313 ime.jar
6,720 ime.odex
201 input
313 input.jar
4,408 input.odex
18,324 installd
133,556 ip
36,052 iperf
216,188 ipth_dua
313 javax.obex.jar
60,848 javax.obex.odex
10,112 keystore
9,692 kmsgcat
39,416 linker
13,952 load_oemlogo
44,484 loc_api_app
14,052 logcat
9,760 logwrapper
5,504 mediaserver
17,408 mm-abl-daemon
13,184 mm-abl-test
18,092 mm-adec-omxaac-test
22,156 mm-adec-omxadpcm-test
22,172 mm-adec-omxamr-test
22,288 mm-adec-omxamrwb-test
22,236 mm-adec-omxevrc-hw-test
26,172 mm-adec-omxmp3-test
22,236 mm-adec-omxQcelpHw-test
22,268 mm-adec-omxvam-test
22,204 mm-adec-omxwma-test
5,532 mm-adspsvc-test
18,108 mm-aenc-omxaac-test
13,852 mm-aenc-omxamr-test
18,252 mm-aenc-omxevrc-test
18,252 mm-aenc-omxqcelp13-test
5,408 mm-audio-alsa-test
15,996 mm-audio-ctrl-test
5,552 mm-audio-mvs-test
88,820 mm-audio-native-test
22,188 mm-jpeg-dec-test
18,096 mm-jpeg-enc-test
5,456 mm-qcamera-daemon
62,308 mm-qcamera-test
10,652 mm-qcamera-testsuite-client
26,464 mm-vdec-omx-test
63,620 mm-venc-omx-test
9,800 modempre
205 monkey
313 monkey.jar
89,864 monkey.odex
18,308 mtpd
5,552 ndc
5,660 netcfg
47,764 netd
76,324 netmgrd
5,520 nl_listener
5,376 oeminfo_test
5,584 oem_rpc_svc
32,616 omx_tests
51 6,374 packages.list
51 111,973 packages.xml
18,692 pand
18,112 pcm-bridge
67,860 pcscd
524,288 Phonesky.apk
2,870,672 Phonesky.odex
11,032 PicoTts.apk
12,640 PicoTts.odex
26,720 ping
5,540 PktRspTest
6,916,572 PlusOne.apk
5,932,352 PlusOne.odex
191 pm
313 pm.jar
28,392 pm.odex
3,757,662 pops_atnt.apk
1,511,304 pops_atnt.odex
18,096 port-bridge
700,557 PotterUnlock.apk
77,128 PotterUnlock.odex
139,540 pppd
56,764 ProjectMenuAct.apk
94,408 ProjectMenuAct.odex
313 qcnvitems.jar
125,648 qcnvitems.odex
313 qcrilhook.jar
12,544 qcrilhook.odex
86,836 qmiproxy
33,652 qmuxd
9,760 qrngd
5,564 qrngtest
56 1,950 qwerty.kl
56 2,601 qwerty_m660.kl
142,516 racoon
26,252 radish
57,140 recEvent
9,856 rild
5,588 rmt_oeminfo
10,220 rmt_storage
59,832 run-as
5,392 schedtest
9,748 sdcard
42,404 sdptool
9,860 service
9,956 servicemanager
313 services.jar
1,732,544 services.odex
6,792,432 Settings.apk
883,048 Settings.odex
33,309 SettingsProvider.apk
65,176 SettingsProvider.odex
974,859 SetupWizard.apk
92,928 SetupWizard.odex
82,840 sh
15,014 ShopMusic.apk
3,264 ShopMusic.odex
23,176 shutdownanima
9,828 sleeplogcat
3,858 SmartcardService.apk
28,064 SmartcardService.odex
1,704,489 SoundRecorder.apk
54,480 SoundRecorder.odex
313 sqlite-jdbc.jar
147,632 sqlite-jdbc.odex
81,284 Stk.apk
67,312 Stk.odex
153,434 Street.apk
323,656 Street.odex
5,456 surfaceflinger
56 1,999 surf_keypad.kl
192 svc
313 svc.jar
8,400 svc.odex
10,239,938 Swype.apk
647,512 Swype.odex
609,667 SystemUI.apk
191,344 SystemUI.odex
5,472 system_server
811,688 Talk.apk
514,136 Talk.odex
35,024 TaskManager.apk
20,472 TaskManager.odex
19,817 TelephonyProvider.apk
165,968 TelephonyProvider.odex
30,452 testpcsc
35,268 test_diag
3,444,531 tn70-android-att-7121044.apk
2,756,552 tn70-android-att-7121044.odex
81,544 toolbox
559,282 ToolBox.apk
24,400 ToolBox.odex
15,030 TtsService.apk
37,544 TtsService.odex
51 58 uiderrors.txt
1,580,748 UNO_DEMO_HUAWEI_U8665_EN_NONIGP_ATT_TS_102.apk
552,136 UNO_DEMO_HUAWEI_U8665_EN_NONIGP_ATT_TS_102.ode
5,440 usbhub
5,520 usbhub_init
13,689 UserDictionaryProvider.apk
16,504 UserDictionaryProvider.odex
27,284 v4l2-qcamera-app
5,552 vdc
1,125,753 Videos.apk
1,392,992 Videos.odex
3,171,658 vlingo.apk
2,772,800 vlingo.odex
91,893 VoiceDialer.apk
87,256 VoiceDialer.odex
1,485,636 VoiceSearch.apk
2,391,016 VoiceSearch.odex
64,100 vold
19,377 VpnServices.apk
32,648 VpnServices.odex
9,792 wiperiface_v01
109,465 WISPr_57_Android22_prepaid.apk
66,824 WISPr_57_Android22_prepaid.odex
9,732 wlan_detect
10,416 wlan_tool
408,520 wl_4330
92,564 wmiconfig
31,284 wpa_cli
372,356 wpa_supplicant
1,937,546 YouTube.apk
1,660,664 YouTube.odex
1,973,436 YPMAndroid-release_preload3_6_2990.apk
1,531,032 YPMAndroid-release_preload3_6_2990.odex
282 File(s) 178,328,187 bytes
Click to expand...
Click to collapse
GOT ROOT? Fusion 2 finally rooted!
RFE said:
hi guys, here is a copy of the latest and greatest adb driver sets. with this driver set (folder called 'Driver' if you don't need adb).
I now HAVE ROOT on the phone by using fastboot and modifying the recovery image. I will post these once I strip it of all my personal info. Please try your own methods as well. I have attached a screenshot of what your (x86) device manager should look like once you correctly installed the drivers.
Best wishes & happy rooting
Click to expand...
Click to collapse
Here is the superuser binary along with a working adb packaged together. Just push the apk to the phone once you have the drivers installed.
I shouldn't have to spell it out for you how to apply this root kit.
Enjoy and don't abuse!
>adb wait-for-device
adb server is out of date. killing...
* daemon started successfully *
>adb shell mount -o rw,remount rootfs /
>adb shell busybox --install -s /vendor/bin
>adb install ./Lib/Superuser.apk
2458 KB/s (196640 bytes in 0.078s)
pkg: /data/local/tmp/Superuser.apk
Success
Looking for the rar password
Thanks for posting, however its asking for a password.
RFE said:
Here is the superuser binary along with a working adb packaged together. Just push the apk to the phone once you have the drivers installed.
I shouldn't have to spell it out for you how to apply this root kit.
Enjoy and don't abuse!
>adb wait-for-device
adb server is out of date. killing...
* daemon started successfully *
>adb shell mount -o rw,remount rootfs /
>adb shell busybox --install -s /vendor/bin
>adb install ./Lib/Superuser.apk
2458 KB/s (196640 bytes in 0.078s)
pkg: /data/local/tmp/Superuser.apk
Success
Click to expand...
Click to collapse
Rar Password?
Will you either release the rar password or post and non encrypted link please?
I thought I mentioned the password is xda-developers.com ... something easy to overlook if you are skimming the forums.
EDIT: attached recovery image
RFE said:
I thought I mentioned the password is xda-developers.com ... something easy to overlook if you are skimming the forums.
EDIT: attached recovery image
Click to expand...
Click to collapse
I got this phone for my daughter and wanted to root to make it seem like an ordinary phone to AT&T. That way they won't charge me for having a smart phone. Anyway, it doesn't seem a lot of folks are rooting the Fusion 2. How has yours behaved since you've rooted? Any problems?
Spurs_Redskins said:
I got this phone for my daughter and wanted to root to make it seem like an ordinary phone to AT&T. That way they won't charge me for having a smart phone. Anyway, it doesn't seem a lot of folks are rooting the Fusion 2. How has yours behaved since you've rooted? Any problems?
Click to expand...
Click to collapse
Even if out root it that won't stop att from seeing it as a smart phone
Batcom2
Whenever I try to push the Superuser.apk into the Fusion 2, it keeps saying that
Code:
"failed to copy 'superuser.apk' : read-only file system
Okay, so I've obtained root, but I bricked my phone using Rom Toolbox Pro. Can someone please backup their /system folder, so I may try to unbrick my device?
Sent from my NookColor using xda app-developers app
yup im a friggin moron flashed that recovery.img to my system out of habit ended up bricking mine too. can someone please upload a stock system.img as well as the original recovery so i can attempt to unbrick this beast I was trying to root for a friend. all I get to is first white at&t screen and it freezes almost like stuck in fastboot mode
can someone help and rip/upload or do I have ne other options?

[how to] reset your lock status flag

first and formost special thanks CastleBravo,without whos testing and help in this thread,for DNA. he asked all the right questions,and gave others all the right answers while i was at work and couldnt respond. also to treadwayj,who dumped mmcblk0p3 from his still locked phone for comparison,providing valuable confirmation.
with m7,this is just one way to skin the cat. you can also use the revone tool to change back to *locked*
use clockwork recovery it did not work for me using twrp. agaion, if you want to flash these zips,do now use twrp.
i happened across this thread inthe gsm evo 3d forum: http://forum.xda-developers.com/showthread.php?t=1970252 and found it to work on the rezound,inc 4g,sensation 4g,cdma evo 3d,MT4GS,Amaze 4g,one s,droid DNA,m7,and prolly several others.
this does NOT mean you can unlock your bootloader without going thru htcdev. all this means,is that if your bootloader is unlocked after s-off,you can get rid of the relocked watermark and get back to 100% locked prior to s-on for legitimate warranty purposes.
ive always been unlocked. for S&Gs,i dumped mmcblk0p3 and found the described "HTCU" at 0x8404. changed it to 0x00000000 and voila! back to locked
afterward,relfashed my origianl mmcblk0p3,wich brought me back to unlocked with no getting or flashing tokens.
this is NOT a patched or hex edited hboot.again,this is ONLY to get back your original ***locked*** status.
*this is for s-off phones only
2 ways to do it:
1)old school
this assumes you to have drivers,adb/fastboot,a hex editor,a fair understanding about what youre doing,and the ability to follow directions on the linked thread
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]
c:\mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HTxxxxxxxxxx device
c:\mini-adb_vigor>[COLOR="Red"]adb shell[/COLOR]
[email protected]:/ $ [COLOR="red"]su[/COLOR]
su
[email protected]:/ # [COLOR="red"]dd if=/dev/block/mmcblk0p3 of=/sdcard2/mmcblk0p3[/COLOR]
dd if=/dev/block/mmcblk0p3 of=/sdcard2/mmcblk0p3
64734+0 records in
64734+0 records out
33143808 bytes transferred in 9.519 secs (3481858 bytes/sec)
[email protected]:/ # [COLOR="red"]exit[/COLOR]
exit
[email protected]:/ $ [COLOR="red"]exit[/COLOR]
exit
c:\mini-adb_vigor>[COLOR="red"]adb pull /sdcard2/mmcblk0p3[/COLOR]
2292 KB/s (33143808 bytes in 14.116s)
[COLOR="Blue"]*modify mmcblk0p3 with a hex editor[/COLOR]
c:\mini-adb_vigor>[COLOR="Red"]adb push mmcblk0p3mod /sdcard2/mmcblk0p3mod[/COLOR]
2478 KB/s (33143808 bytes in 13.059s)
c:\mini-adb_vigor>[COLOR="red"]adb shell[/COLOR]
[email protected]:/ $ [COLOR="red"]su[/COLOR]
su
[email protected]:/ # [COLOR="red"]dd if=/sdcard2/mmcblk0p3mod of=/dev/block/mmcblk0p3[/COLOR]
dd if=/sdcard2/mmcblk0p3mod of=/dev/block/mmcblk0p3
64734+0 records in
64734+0 records out
33143808 bytes transferred in 18.937 secs (1750214 bytes/sec)
[email protected]:/ #[COLOR="red"] exit[/COLOR]
exit
[email protected]:/ $ [COLOR="red"]exit[/COLOR]
exit
c:\mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\mini-adb_vigor>
2)noob friendly
-download the appropriate zips,place on sd card.
-boot to recoverywipe cache/dalvik
-flash in recovery. i recomend to run query first,to make sure its working. tested on my personal m7_u,and m7_ul, one s,amaze,jetstream,rezound,inc) 4g,sensation,MT4GS,and gsm evo 3d. tested by castlebravo on DNA.
query:query_bootloader.zip
query_bootloader.zip f335f78f9f46469c823da0c671026de5
unlock:unlock_bootloader.zip
unlock_bootloader.zip f335f78f9f46469c823da0c671026de5
lock:lock_bootloader.zip
lock_bootloader.zip f335f78f9f46469c823da0c671026de5
a little bit of explanation. yes,the md5s are all the same. its the same file,just named differently. the script behaves based on the name of the zip. i knew if i only included 1 download and instructed folks to change the name there would be confusion,so this is my attempt to keep it simple. feel free to download one file and just change the name to make the other zips.
it also works to make your phone relocked if for some reason you want it that way(rename relock_bootloader.zip). i didnt include a zip for that because i figued there would be no demand.
before:
after:
sure,i could have easily faked the above photos,but i dint.
again,all credit goes to s trace on the above thread,be sure to click the thanks button on his post. all i did was remove the device check per his instruction. DO NOT flash on other devices without checking for the proper location of the lock flag first.
DISCLAIMER:this is not my work. i have tested it on my own device,but use it at your own risk. if it melts your phone into a lil pile of goo,its not my fault.
enjoy
special thanks
-BC for originally dumping mmcblk0p3 for me to know this was worth exploring for dna
-CastleBravo for testing and suport on the original test thread,as well as the pics you see here
-treadwayj for dumping mmcblk0p3 from his still locked phone.
-brian for unlocking his bootloader,then dumping mmcblock0p3 to make sure it would work for cdma evo3d phones too
-brian and donb for fearless testing of the zip files on evo3d cdma
This is only for the flags, correct? It won't turn S-ON, will it? I'm not sure how thorough the T-mobile folks check to see if you've rooted your phone or not. Mine says locked but I have S-OFF so i can still do as I please with the phone. NINJA!
silentcovenant said:
This is only for the flags, correct? It won't turn S-ON, will it? I'm not sure how thorough the T-mobile folks check to see if you've rooted your phone or not. Mine says locked but I have S-OFF so i can still do as I please with the phone. NINJA!
Click to expand...
Click to collapse
It will lock the bootloader again, but that doesn't matter now that we have S-OFF.
I just used revone's guide for resetting the flag from "Relocked" to "Locked".
Lafenear said:
It will lock the bootloader again, but that doesn't matter now that we have S-OFF.
I just used revone's guide for resetting the flag from "Relocked" to "Locked".
Click to expand...
Click to collapse
Okay, yeah, me too.. I'm having a lot of issues with getting AOSP ROMs to work with my phone, I'm starting to think the phone is defective. I can't imagine what would be going wrong, though. What would I tell T-Mobile if/when I take the phone to them, I just want another HTC One that works with my flashing habit.
Also, anyone know how to reflash the stock recovery? I notice someone posted the .img file of it
silentcovenant said:
Okay, yeah, me too.. I'm having a lot of issues with getting AOSP ROMs to work with my phone, I'm starting to think the phone is defective. I can't imagine what would be going wrong, though. What would I tell T-Mobile if/when I take the phone to them, I just want another HTC One that works with my flashing habit.
Also, anyone know how to reflash the stock recovery? I notice someone posted the .img file of it
Click to expand...
Click to collapse
you should be able to just flash it in fastboot
Sent from my HTC One using xda premium
Can you actually S-ON again? Don't need to but just curious!
meleelord said:
Can you actually S-ON again? Don't need to but just curious!
Click to expand...
Click to collapse
http://androidforums.com/showthread.php?p=5918438
Sent from my ADR6425LVW using Tapatalk 2

Tablet Z SGP311 - 10.7.A.0.222 Trouble trying to install CyanogenMod and TWRP

Hi, I have a stock Tablet Z on 10.7.A.0.222
I have successfully unlocked the bootloader via instructions on xperia firmware. However I have been unable to root it or install twrp.
I am a complete noob at this but the tablet is running incredibly laggy as stock so want to refresh it. I was using this guide:
https://www.cyanogenmods.org/forums/topic/xperia-tablet-z-cm14-cyanogenmod-14-nougat-7-0-rom/
In that guide I got to 1b which led me to this guide for installing recovery:
https://www.cyanogenmods.org/forums/topic/install-twrp-recovery-android-using-fastboot/
When i try to do step 6 the tablet shuts off and does not go into bootloader mode where I can flash twrp.
Can someone provide direction on what I need to do differently? I have done various searches on this site and I believe there is not a recovery installed in this firmware version or something and that is preventing me from being able to do this step but I am not sure how I get around that.
cward0625 said:
Can someone provide direction on what I need to do differently? I have done various searches on this site and I believe there is not a recovery installed in this firmware version or something and that is preventing me from being able to do this step but I am not sure how I get around that.
Click to expand...
Click to collapse
Hello!
Look at this thread.
Rootk1t said:
Hello!
Look at this thread.
Click to expand...
Click to collapse
Thanks for the response, I had referred to this guide too but was unable to get this step to work for me->
- Root. Follow Bin4ry root : http://forum.xda-developers.com/show....php?t=1886460
Download : http://forum.xda-developers.com/show....php?t=1886460
Below is what I get in the command prompt when doing the steps. When I tried option 4 for new xperia root it did not work...it just hangs here:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry =
= (15.06.2014) v36 =
======================================================================
Device type:
0) New Z2 Root Method by cubeandcube (thanks man!)
1) 2014 root (thx jcase for nice pwn binary and xsacha for the exploit)
2) Xperia Root by cubeundcube
3) New Standard-Root (thx Ariel Berkman)
4) New Xperia Root by Goroh_kun (Xperia Z, Xperia V [JellyBean] ...)
5) Old
6) Old-Special (for example: Sony Tablet S, Medion Lifetab)
G) Google Glass Mode (thx Saurik for the ab file)
x) Unroot
Make a choice: 4
Please connect Xperia device with enabled USB-Debugging now to your Computer
Going to copy over some files ...
33 KB/s (442 bytes in 0.012s)
33 KB/s (170 bytes in 0.004s)
13 KB/s (57 bytes in 0.003s)
Starting restore operation, please look on your device and confirm restore!
after that press anykey here in the console
Now unlock your device and confirm the restore operation.
Press any key to continue . . .
After restore is confirmed please look on your device and choose "Service Tests -> Display" in Service menu and WAIT THERE!"
Starting: Intent { act=android.intent.action.MAIN cmp=com.sonyericsson.android.servicemenu/.ServiceMainMenu }
/data/local/tmp/onload.sh ...
Then if I try option 1 instead I get this (although I do not think this is the correct option anyways:
Device type:
0) New Z2 Root Method by cubeandcube (thanks man!)
1) 2014 root (thx jcase for nice pwn binary and xsacha for the exploit)
2) Xperia Root by cubeundcube
3) New Standard-Root (thx Ariel Berkman)
4) New Xperia Root by Goroh_kun (Xperia Z, Xperia V [JellyBean] ...)
5) Old
6) Old-Special (for example: Sony Tablet S, Medion Lifetab)
G) Google Glass Mode (thx Saurik for the ab file)
x) Unroot
Make a choice: 1
Exploit type:
0) xsacha Z2 Tablet Root
1) jcase Z1S Root (make sure to download the pwn binary first from XDA thread!)
Make a choice: 1
Please connect your device with enabled USB-Debugging ...
Copy needed files ...
4106 KB/s (574722 bytes in 0.136s)
6023 KB/s (104576 bytes in 0.016s)
5317 KB/s (2139595 bytes in 0.392s)
72 KB/s (148 bytes in 0.001s)
1024 KB/s (2092 bytes in 0.001s)
4525 KB/s (1109128 bytes in 0.239s)
Beaups and jcase were here
donations may go here, pleaes say what it was for -> [email protected]
Rebooting device, please wait ...
mount: Permission denied
dd: /system/xbin/su: Read-only file system
chown: /system/xbin/su: No such file or directory
Unable to open /system/xbin/su: No such file or directory
ln: /system/bin/su: Read-only file system
dd: /system/app/Superuser.apk: Read-only file system
chown: /system/app/Superuser.apk: No such file or directory
Unable to open /system/app/Superuser.apk: No such file or directory
dd: /system/xbin/busybox: Read-only file system
chown: /system/xbin/busybox: No such file or directory
Unable to open /system/xbin/busybox: No such file or directory
/data/local/tmp/install_tool.sh[39]: /system/xbin/busybox: not found
mount: Permission denied
"If this helped you please consider donating to the original author jcase: http://forum.xda-developers.com/showpost.php?p=53407127&postcount=1004"
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press any key to continue . . .
Any ideas on what I am doing wrong or what I need to do differently?
I have rooted my phones before and installed different ROMs but something seems to be off here.
cward0625 said:
Thanks for the response, I had referred to this guide too but was unable to get this step to work for me->
Any ideas on what I am doing wrong or what I need to do differently?
I have rooted my phones before and installed different ROMs but something seems to be off here.
Click to expand...
Click to collapse
forget about root. To install TWRP to FOTA or custom ROM, you don't need it.
Proceed with step 7.
Rootk1t said:
forget about root. To install TWRP to FOTA or custom ROM, you don't need it.
Proceed with step 7.
Click to expand...
Click to collapse
thanks a lot, I did that, got lineage installed, worked fine, then when I followed the directions to install gapps and rebooted it just keeps loading twrp and not to lineage. I tried wiping and starting over and getting the same thing. Is there something I need to do differently? I used gapps arm 7.1 neon 20181118
thanks again
cward0625 said:
thanks a lot, I did that, got lineage installed, worked fine, then when I followed the directions to install gapps and rebooted it just keeps loading twrp and not to lineage. I tried wiping and starting over and getting the same thing. Is there something I need to do differently? I used gapps arm 7.1 neon 20181118
thanks again
Click to expand...
Click to collapse
wiping and installing 14.1 did not work, but when i did 15.1 it did. I think I should be set now.
Thanks

Replacing the McLaren Boot Animation

Note: This appears to be relevant ONLY for the 7T Pro McLaren 4G Global Variant. For other variants, use the normal boot animation replacement method.
*** You have to be root in order to perform the following actions! ***
*** Perform at your own risk! ***
Hi!
So, I decided that I got a bit sick of the McLaren Boot Animation, and that the default OxygenOS is much cleaner.
I tried using the normal methods of replacing the bootanimation.zip inside /system/media, but it didn't seem to affect the McLaren boot animation at all.
After a bit of digging, I found that /op1/bootanimation/bootanimation.zip was the McLaren boot animation path!
I also noticed the /op1/filelist.md5 file, which has an md5 hash for each file inside the op1 partition.
After understanding the structure, here are the changes I took to replace my McLaren boot animation:
Code:
adb pull /system/media/bootanimation.zip
Code:
adb pull /op1/filelist.md5
Code:
md5sum bootanimation.zip
Open up the filelist.md5 and replace the md5 hash for bootanimation.zip with the one from step 3, save the file.
Code:
adb shell
Code:
su
Code:
mount -o rw,remount /op1
Code:
exit
Code:
adb push filelist.md5 /op1/filelist.md5
Code:
adb push /op1/bootanimation/bootanimation.zip
Code:
adb reboot
Done! your device will reboot & you should see the default OxygenOS Boot Animation
You can probably replace the default bootanimation.zip with any custom boot animation you like, just make sure you replace the md5 hash accordingly.
Anyone who wants to take this and compile it to a Magisk module, feel free to do so. I currently don't have time time...
Enjoy!
Armageda said:
*** You have to be root in order to perform the following actions! ***
*** Perform at your own risk! ***
Hi!
So, I decided that I got a bit sick of the McLaren Boot Animation, and that the default OxygenOS is much cleaner.
I tried using the normal methods of replacing the bootanimation.zip inside /system/media, but it didn't seem to affect the McLaren boot animation at all.
After a bit of digging, I found that /op1/bootanimation/bootanimation.zip was the McLaren boot animation path!
I also noticed the /op1/filelist.md5 file, which has an md5 hash for each file inside the op1 partition.
After understanding the structure, here are the changes I took to replace my McLaren boot animation:
Open up the filelist.md5 and replace the md5 hash for bootanimation.zip with the one from step 3, save the file.
Done! your device will reboot & you should see the default OxygenOS Boot Animation
You can probably replace the default bootanimation.zip with any custom boot animation you like, just make sure you replace the md5 hash accordingly.
Anyone who wants to take this and compile it to a Magisk module, feel free to do so. I currently don't have time time...
Enjoy!
Click to expand...
Click to collapse
There's already a magisk module McLaren boot animation its supposed to restore the original McLaren one but it doesn't, but you can throw any bootanimation.zip and shutdownanimation.zip with rwrr permissions (and I would assume correct resolution) and it will stick.
Joe199799 said:
There's already a magisk module McLaren boot animation its supposed to restore the original McLaren one but it doesn't, but you can throw any bootanimation.zip and shutdownanimation.zip with rwrr permissions (and I would assume correct resolution) and it will stick.
Click to expand...
Click to collapse
The existing magisk module only works for non-mclaren modules, since on these versions, the bootanimation.zip that is being loaded is at /system/media
Armageda said:
The existing magisk module only works for non-mclaren modules, since on these versions, the bootanimation.zip that is being loaded is at /system/media
Click to expand...
Click to collapse
I'm using a McLaren edition 7t pro it's what I used and it works perfectly fine. Granted I'm still on .19 for some reason
Joe199799 said:
I'm using a McLaren edition 7t pro it's what I used and it works perfectly fine. Granted I'm still on .19 for some reason
Click to expand...
Click to collapse
So you're using the 5G variant.
I'm using the 4G global variant on v10.0.8.
There might be a difference between the two in terms of how bootanimation is handled.
Armageda said:
So you're using the 5G variant.
I'm using the 4G global variant on v10.0.8.
There might be a difference between the two in terms of how bootanimation is handled.
Click to expand...
Click to collapse
Ahhh ok my bad forgot about the 4g global variant my bad
Joe199799 said:
Ahhh ok my bad forgot about the 4g global variant my bad
Click to expand...
Click to collapse
No worries, thanks for bringing that up
I edited my post accordingly.
Armageda said:
No worries, thanks for bringing that up
I edited my post accordingly.
Click to expand...
Click to collapse
No problem I apologise if I came off snarky in the first comment
Armageda said:
For other variants, use the normal boot animation replacement method.
Click to expand...
Click to collapse
What is the normal replacement method for the 5G McLaren variant?
I wanna remove that stupid warning about being rooted and change the tmobile logo to the mclaren one
RypeDub said:
What is the normal replacement method for the 5G McLaren variant?
I wanna remove that stupid warning about being rooted and change the tmobile logo to the mclaren one
Click to expand...
Click to collapse
You can't make the unlocked bootloader warning go away, if that's what you mean.
Look in the normal 7t pro forum, there is a bootanimation replacement method.
any updates i get isssues
PS C:\Program Files\platform-tools> adb pull /system/media/bootanimation.zip
/system/media/bootanimation.zip: 1 file pulled, 0 skipped. 28.4 MB/s (2050274 bytes in 0.069s)
PS C:\Program Files\platform-tools> adb pull /op1/filelist.md5
adb: error: failed to stat remote object '/op1/filelist.md5': Permission denied
PS C:\Program Files\platform-tools> mount -o rw,remount /op1
New-PSDrive : Parameter cannot be processed because the parameter name 'o' is ambiguous. Possible matches include:
-OutVariable -OutBuffer.
At line:1 char:7
+ mount -o rw,remount /op1
+ ~~
+ CategoryInfo : InvalidArgument: ) [New-PSDrive], ParameterBindingException
+ FullyQualifiedErrorId : AmbiguousParameter,Microsoft.PowerShell.Commands.NewPSDriveCommand
does the phone have to be off or something.
cbomb1337 said:
any updates i get isssues
PS C:\Program Files\platform-tools> adb pull /system/media/bootanimation.zip
/system/media/bootanimation.zip: 1 file pulled, 0 skipped. 28.4 MB/s (2050274 bytes in 0.069s)
PS C:\Program Files\platform-tools> adb pull /op1/filelist.md5
adb: error: failed to stat remote object '/op1/filelist.md5': Permission denied
PS C:\Program Files\platform-tools> mount -o rw,remount /op1
New-PSDrive : Parameter cannot be processed because the parameter name 'o' is ambiguous. Possible matches include:
-OutVariable -OutBuffer.
At line:1 char:7
+ mount -o rw,remount /op1
+ ~~
+ CategoryInfo : InvalidArgument: ) [New-PSDrive], ParameterBindingException
+ FullyQualifiedErrorId : AmbiguousParameter,Microsoft.PowerShell.Commands.NewPSDriveCommand
does the phone have to be off or something.
Click to expand...
Click to collapse
Looks like you ran this in PowerShell.
Please run the commands in the normal Windows command prompt.
Also, it seems like you can the "mount -o rw,remount /op1" while not being inside the device's ADB shell.
It's all good It's abit more confusing then my old phone I would just go to twrp file manager I think it was and swap files over and reboot lol.
cbomb1337 said:
It's all good It's abit more confusing then my old phone I would just go to twrp file manager I think it was and swap files over and reboot lol.
Click to expand...
Click to collapse
Since we can't access the partitions in TWRP (due to encryption), this is the current way to bypass it...
It's not too hard, just make sure you follow the steps carefully.

Categories

Resources