Develop Bugs

[UPDATE][ICS]Stock Android 4.0.4 IMM76L. (VERIZON STINGRAY 4G)

{
"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"
}
DOWNLOAD STRAIGHT FROM GOOGLE:
http://android.clients.google.com/packages/ota/verizon_trygon/2a903016f227.signed-trygon-IMM76L-from-HLK75H.2a903016.zip
Instructions:
* You will also need to be on Android build HLK75H
1. Download the file from above and drop it on a USB stick or SD card that can be put in a USB Stick.
2. Turn your XOOM off.
3. When you power it back on, tap Volume Down at the red M logo until it says:
–> Android Recovery
4. Tap Volume Up to enter recovery mode.
5. At the green Android logo, press Volume Up and Power.
6. Plug in your USB drive to a USB host cable and then into your XOOM.
7. Scroll down to “apply update via USB drive” and select it with Power.
8. Scroll down to the .zip update file from above and use Power to select it.
9. Your XOOM will now update.
Click to expand...
Click to collapse

Has anyone applied this update with success?

patrickhills said:
Has anyone applied this update with success?
Click to expand...
Click to collapse
I did, its legit. However I SBF'd back to HC before applying the update. ( I prefer to go the SBF route)
Hulu Plus STILL giving error 91
However, works fine. I see no reason to use any other rom.

Yup. Works. Thanks
Sent from my Xoom using XDA

Can someone pull their /system once the update's been installed, please? This will help the ROM community out quite a bit. Thanks!
---------- Post added at 08:56 PM ---------- Previous post was at 08:17 PM ----------
... and share the output of "fastboot getvar all" (while in "Fastboot Mode", of course), too (you can leave out your serial number if you wish)? Thanks!

I am on EOS 2.0.
I am assuming I will lose root,but that can be corrected.
Will I need to revert back to stock?
Or should I just stfu and be happy with EOS until we get a pre rooted rom?

tcbj said:
should I just stfu and be happy with EOS until we get a pre rooted rom?
Click to expand...
Click to collapse
Probably.

Can anyone confirm that there's a new radio? I've heard that there are 4G improvements.
Also, any general impressions? How does it stack up to something like Bugless Beast?

jm9843 said:
Can anyone confirm that there's a new radio?
Click to expand...
Click to collapse
Yes, for both the LTE and the original CDMA radios.
I NEED A SYSTEM DUMP!

kcrudup said:
Yes, for both the LTE and the original CDMA radios.
I NEED A SYSTEM DUMP!
Click to expand...
Click to collapse
I have one but unfortunately didnt pull it until after I had rooted and installed the latest busybox. If you want it I will upload it for you.
Edit: added build.prop for reference
Here is the link.
https://www.dropbox.com/s/lnlvkvc1zkp41ak/xoom_system_IMM76L.7z
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IMM76L
ro.build.display.id=IMM76L
ro.build.version.incremental=345519
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Wed May 2 19:56:06 UTC 2012
ro.build.date.utc=1335988566
ro.build.type=user
ro.build.user=android-build
ro.build.host=vpbs18.mtv.corp.google.com
ro.build.tags=release-keys
ro.product.model=Xoom
ro.product.brand=verizon
ro.product.name=trygon
ro.product.device=stingray
ro.product.board=
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Motorola
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=stingray
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=trygon-user 4.0.4 IMM76L 345519 release-keys
ro.build.fingerprint=verizon/trygon/stingray:4.0.4/IMM76L/345519:user/release-keys
ro.build.characteristics=tablet
# end build properties
# RIL and telephony related settings
rild.libargs=-d /dev/chnlat10
#Point to lte, CDMA, MM RILs
lte_ril.libpath=/system/lib/libmoto_lte_ril.so
cdma_ril.libpath=/system/lib/libmoto_cdma_ril.so
rild.libpath=/system/lib/libmoto_mm_ril.so
ril.rat=LTE
persist.ril.mux.ttydevice=/dev/usb/tty2-1:1.2
# Increase # channels to 10 to allow M2M communication
persist.ril.mux.noofchannels=10
persist.ril.modem.mode=1
# Enable ALWAYS_READ_IMSI_FROM_SIM
persist.ril.features=800
ro.cdma.home.operator.numeric=310004
ro.cdma.home.operator.alpha=Verizon
ro.cdma.homesystem=64,65,76,77,78,79,80,81,82,83
ro.cdma.data_retry_config=default_randomization=2000,0,0,120000,180000,540000,960000
persist.ril.modem.ttydevice=/dev/usb/tty2-1:1.4
persist.ril.tcmd.ttydevice=/dev/usb/tty2-1:1.3
persist.ril.diag.ttydevice=/dev/usb/tty2-1:1.0
ril.wrigley.modem.tty=/dev/usb/tty1-1:1.10
#Leave default mode to 4 (CDMA) but need it to be Global (7) for LTE/CDMA
ro.telephony.default_network=4
# Disable ims by setting imsapp.mode to all_dependency_met
#imsapp.mode=all_dependency_met
# The value of the kernel command line product_type variable for lte on cdma devices
telephony.lteOnCdmaProductType=clw
# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version = 131072
# Indicate carrier OTA SP number schema
# refer to frameworks/base/telephony/java/com/android/
# internal/telephony/cdma/CDMAPhone.java for the schema:
ro.cdma.otaspnumschema=SELC,1,80,99
# Give extra time for LTE bug dumps
ril.dumpstate.timeout=75
# Retry config when GSM DCT is used for EHRPD/LTE call
ro.gsm.data_retry_config=max_retries=infinite,default_randomization=2000,0,0,80000,125000,485000,905000
ro.gsm.2nd_data_retry_config=max_retries=infinite,default_randomization=2000,0,0,80000,125000,485000,905000
ro.ril.panic.reporter=apr
ro.ril.fccid=IHDP56LU2
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.google.clientidbase=android-verizon
ro.config.ringtone=Sceptrum.ogg
ro.config.notification_sound=Cobalt.ogg
ro.config.alarm_alert=Cesium.ogg
keyguard.no_require_sim=true
ro.setupwizard.mode=OPTIONAL
drm.service.enabled=true
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.com.android.wifi-watchlist=GoogleGuest
ro.error.receiver.system.apps=com.google.android.feedback
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

cellzealot said:
I have one but unfortunately didnt pull it until after I had rooted and installed the latest busybox. If you want it I will upload it for you.
Click to expand...
Click to collapse
Yes, that's fine- as long as the busybox files are only the ones you've changed.
The patch scripts in the update have the SHA1 of the result files listed in it, so I can verify the integrity of the ones we really need, which are mostly just the VZ and NVidia proprietary files. (Interestingly enough, none of the WiFi files changed, but the BT firmware did).

I have tried installing this update multiple times, but keep getting this error when trying to install:
Code:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:Failed to seek in /tmp/sideload/package.zip (Invalid argument)
E:Signature verification failed
Installation aborted.
I have tried multiple times with the same result. I am running stock HLK75H, unlocked bootloader but no root or custom recovery. Any help would be great! Thanks.

dawynkoop said:
I have tried installing this update multiple times, but keep getting this error when trying to install:
Code:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:Failed to seek in /tmp/sideload/package.zip (Invalid argument)
E:Signature verification failed
Installation aborted.
I have tried multiple times with the same result. I am running stock HLK75H, unlocked bootloader but no root or custom recovery. Any help would be great! Thanks.
Click to expand...
Click to collapse
Is your S-OFF or S-ON? I think you need to have signature verification ON in order to apply an OTA update.

[ROM][4.4.4][v3.00]Mi Xperia! - eXperience the Xperia UI {v3.00 Released]

{
"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"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
We(I, HridayHS and TechExhibeo) present you our Xperia Themed ROM. The ROM is based on Cyanogenmod builds by jsevi83 and Kra1o5. The Cyanogenmod thread can be found here. Please thank them for their work. Changelog and Screenshots are in the second post and Download links and Instructions in the third.
​
Features:​
*Xperia Themed Framework
*Xperia Z2 Lockscreen
*Sony Smart Social Camera
*Xperia Themed Dialer & Messaging
*WALKAMN
*xLOUD
*ClearPhase
*ClearAudio+
*Surround Sound
*Xperia Album
*Xperia Movies
*Xperia Keyboard
*White Xperia Settings
*Motion Graph
*Motion Shot
*TrackID
*SOMC Sketch
*SOMC Notes
*STM10 Audio Recorder
*Sony CAR
*Notes
*SoundEnhancement
*Xperia Z3 Launcher
*Many More which I probably don't remember...
​
To do:
*Port Small-apps
*Optimise Z3 SystemUI for dual-sim Phones
*SONY Dialer and conversations
Credits:
*jsevi83 and Kra1o5 for Cyanogenmod 11 which we're using as base
*ashishdubey for always being available to help me out
*Sahaab for Z3 home
*ibanez7 for WALKMAN files
*Ben Ling for Z3 Bootanimation
*Vipul Verma for Sony Smart Social Camera PORT
If I missed out someone, I'm sorry. Please PM me.​
Support​
Want to support this project? It's simple! Just thank us and rate this thread 5 stars. That's it.
Thread rules:
*No asking for ETA's!
*If you're reporting a bug, attach a log with it. Logs or it didn't happen.
*Don't Post Thanks! Hit the button.
plus all XDA rules...
​
XDA:DevDB Information
Mi Xperia!, ROM for the Xiaomi Redmi 1S
Contributors
sud.vastav, Hridayhs, TechExhibeo
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: Cyanogenmod
Version Information
Status: Testing
Created 2014-11-27
Last Updated 2015-03-13

ScreenShots & Changelogs
1.Intial Build
2.Added Xperia Apps
3.Added Xperia Bootanimation
4.Highly Modded
5.Xperia Icons and Animations
LockScreen
Xperia Themed Dailer & Messaging APP
Apps
Sony Smart Social Camera
Motion Shot & Motiongraph for Xperia
Settings
ROOT
Launcher

Instructions & Downloads
# Instructions for V3.00
# Download ROM (Part 1 & Part 2 Both) & GAPPS
# Copy ROM & GAPPS to Internal or External SD Card
# Boot into Custom Recovery (TWRP or CWM)
# Wipe data,system,cache,dalvik/factory reset
# Flash Part 1 Zip
# Flash Part 2 Zip and Reboot to System
# Reboot again to Recovery
# Flash GAPPS and Reboot to System
# Voila DONE!
# Enjoy your Redmi 1S
# Instructions for V2.0
# Download ROM (Part 1 & Part 2 Both) & GAPPS
# Copy ROM & GAPPS to Internal or External SD Card
# Boot into Custom Recovery (TWRP or CWM)
# Wipe data,system,cache,dalvik/factory reset
# Flash Part 1 Zip
# Flash Part 2 Zip and Reboot to System
# Reboot again to Recovery
# Flash GAPPS and Reboot to System
# Voila DONE!
# Happy New Year 2k15
# Instructions for V1.1
# Download ROM & GAPPS
# Copy ROM & GAPPS to Internal or External SD Card
# Boot into Custom Recovery (TWRP or CWM)
# Wipe data/factory reset or Wipe /system, data, /cache & /dalvik
# Mount /system , /data
# Flash Mi_Xperia_v1.1.zip
# Reboot to System
# Set Xperia Live Wallpaper for Lockscreen Effects
# Reboot again to Recovery
# Flash GAPPS
# Reboot your phone
# Enjoy
# Instructions for V1.0
# Download ROM (Part 1 & Part 2 Both) & GAPPS
# Copy ROM & GAPPS to Internal or External SD Card
# Boot into Custom Recovery (TWRP or CWM)
# Wipe data,system,cache,dalvik/factory reset
# Mount System and Data ( Very IMPORTANT)
# Flash Part 1 Zip
# Mount System and Data Again( Very IMPORTANT)
# Flash Part 2 Zip and Reboot to System
# Reboot again to Recovery
# Flash GAPPS
# Mount System and Data Again ( Very IMPORTANT)//Step for Addon (Optional)
# Flash Z3 Lock-Screen//Step for Addon (Optional)
# Reboot your phone
# Enjoy
Sorry for these long instructions. We will shorten this instructions part in next update
Thank You!
# v1.0
ROM
# Part 1 ===> Google Drive | Mirror (Dev-Host)
# Part 2 ===> Dev-Host | Mirror (Mediafire)
# v1.1
----> Download<----
# v2.0
----> Download<----
# v3.00
----> Download<----
GAPPS
PA GAPPS
// Use any PACKAGE (I use PICO MODULAR PACKAGE)
Addons (Optional)
Xperia Z3 Lockscreen //Only for V1.0
Flash Through Custom Recovery And Set Xperia Live Wallpaper
----> Download <----
Fixes
Bluetooth Fix// For all Builds
Download BT FIX​

Code:
[B]*xLOUD
*ClearPhase[/B]
interesting!
If you don't mind, can you add screenshot both features works on CM11 ?

very nice work.......will try later.............

Links
where is the download links......btw Thumbs UP
---------- Post added at 06:20 AM ---------- Previous post was at 06:13 AM ----------
Got It Now.......
Thanks

u_know_me said:
Code:
[B]*xLOUD
*ClearPhase[/B]
interesting!
If you don't mind, can you add screenshot both features works on CM11 ?
Click to expand...
Click to collapse
yeah sure
will update ASAP!!
EDIT- xLOUD & ClearPhase are enabled by Default... So no option in settings
Stay Tuned!
saket2606 said:
where is the download links......btw Thumbs UP
---------- Post added at 06:20 AM ---------- Previous post was at 06:13 AM ----------
Got It Now.......
Thanks
Click to expand...
Click to collapse
Sorry for the Delay!

Nice and great works.
can you screenshot phone and messaging apps?

TechExhibeo said:
yeah sure
will update ASAP!!
EDIT- xLOUD & ClearPhase are enabled by Default... So no option in settings
Stay Tuned!
Sorry for the Delay!
Click to expand...
Click to collapse
Thanks for your efforts to bring Xperia xperience into Redmi, btw can you please check, I've not found Walkman/Movies apps, I believe I don't miss anything when flashing the ROM part1, part2 and gapps
pls check the screen attached.

Levered said:
Nice and great works.
can you screenshot phone and messaging apps?
Click to expand...
Click to collapse
As you know, SONY Dialer and conversations are hard coded so its very hard to port it. So dialer and conversations are still the CM stock ones. We're trying to theme CM stock dialer like SONY's one and hopefully we'll add it soon.
u_know_me said:
Thanks for your efforts to bring Xperia xperience into Redmi, btw can you please check, I've not found Walkman/Movies apps, I believe I don't miss anything when flashing the ROM part1, part2 and gapps
pls check the screen attached.
Click to expand...
Click to collapse
Are you using TWRP?
Please first mount system and data and then again flash part-2. This should bring all the apps.
And as per your request about xLOUD, it is already enabled. There's no option to enable/disable it. An option to enable/disable makes xLOUD very buggy. If you still want it, i'll upload it as an add on soon.

u_know_me said:
Thanks for your efforts to bring Xperia xperience into Redmi, btw can you please check, I've not found Walkman/Movies apps, I believe I don't miss anything when flashing the ROM part1, part2 and gapps
pls check the screen attached.
Click to expand...
Click to collapse
Sorry for the inconvenience caused
i forgot to mention in instructions to mount system and data
my bad
sorry

unfortunately setup wizard stopped............what to do now..,......flashed 3/4 times
but every time this msf comes.

saket2606 said:
unfortunately setup wizard stopped............what to do now..,......flashed 3/4 times
but every time this msf comes.
Click to expand...
Click to collapse
Wipe /data
Flash Part 1
Boot into system
Once booted, reboot to recovery and then flash GAPPS and part 2

sud.vastav said:
Wipe /data
Flash Part 1
Boot into system
Once booted, reboot to recovery and then flash GAPPS and part 2
Click to expand...
Click to collapse
Thanks buddy

after managed to flash the ROM, I only have 8 apps from xperia, finally walkman player installed perfect.
see attached picture

Thanks for this. i will try this rom, i'm waiting rom xperia.:good:

Glad to see the devs giving attention to Redmi 1S.
Thanks for this rom, will try it soon.

fanboy_android said:
Glad to see the devs giving attention to Redmi 1S.
Thanks for this rom, will try it soon.
Click to expand...
Click to collapse
Thnaks, For appreciate our work

TechExhibeo said:
# Download ROM (Part 1 & Part 2 Both) & GAPPS
# Copy ROM & GAPPS to Internal or External SD Card
# Boot into Custom Recovery (TWRP or CWM)
# Wipe data/factory reset
# Mount System and Data ( Very IMPORTANT)
# Flash Part 1 Zip
# Mount System and Data Again( Very IMPORTANT)
# Flash Part 2 Zip and Reboot to System
# Reboot again to Recovery
# Flash GAPPS
# Mount System and Data Again ( Very IMPORTANT)//Step for Addon (Optional)
# Flash Z3 Bootanimation//Step for Addon (Optional)
# Reboot your phone
# Enjoy
Sorry for these long instructions. We will shorten this instructions part in next update
Thank You!​
Click to expand...
Click to collapse
u_know_me said:
after managed to flash the ROM, I only have 8 apps from xperia, finally walkman player installed perfect.
see attached picture
Click to expand...
Click to collapse
try these instructions carefully
i tested it myself and i checked that its working
i got all sony apps in my app drawer

1. any call bug like CM ?
2. How's the ram management?
3. Can someone give me benchmark score for this rom?
4. How's the camera and music compared to stock MIUI? better?
5. How's the battery life?
Thank you

[ROM] SuperStock v2.9 Custom Rom COKC G928T S6 Edge+ (1//29/2016)

SuperStock v2.9 COKC Custom Rom for T-mobile
Samsung Galaxy S6 Edge Plus G928T​
The SuperStock Rom v2.9 is fully based on the latest Samsung G928T COKC firmware
but it's also fully compatible with the COJ5 baseband..​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
--
--
-
-
​
This rom is FAST!!!
The Air Command feature of the NOTE 5 is being worked on and will soon become​another additional feature in the SuperStock rom. (using your finger of course)​​​​
Version 2.9 - COKC Changelog:
SystemUI, Settings, and Keyboard were all themed dark (Samsung theme store still works fine)
Fixed a few memory tweaks and done some code cleaning
Fixed a couple Grammar errors (CustomSettings)
Removed Build Version (CustomSettings)
Fixed Listview Animations FC on clean install scroll
Re-added Data Icon Style (CustomSettings)
Version 2.8 - COKC Changelog:
Fully re-based using the latest G928T COKC firmware.
Enhanced SuperStock Rom Control features.
Rom Control re-located underneath Quicksettings.
Various database cleanup and optimizations.
Version 2.6 - COJ5 Changelog:
Fixed App Optimization
Added Tool access into settings
SuperStock Custom Settings
6thGear TWswipe
Toolbox settings
Multiwindow manager
App permissions
Autostart settings
Added in Custom Settings
NW Booster color
Data arrows
Wifi arrows
Battery % display
Show/Hide 3minit battery
Working on adding Stock Battery Show/Hide
Home, Menu, and Back hardware key mapping
Volume key mapping
Please Note:
All SuperStock Rom control options are now located under "Developers Options".
Version 2.5 - COJ5 Changelog:
Fully Re-Based to COJ5
Fixed All NIne Quicksettings
36 Scroll-able toggles
Added many features & options to Rom Control
Added extra options to hardware key mapping
Many performance enhancements
And more fixes + improvements... will add them later
Version 2.4 - COI5 Changelog:
Added Hardware keys remapping
Added Auto Start Management
Added App Ops Permission Manager
Status Bar tweaks
Bluetooth tweaks
Netflix Fix
Version 2.3 - COI5 Changelog:
Added Project Super Camera on Steriods
New Boot Animation in my style
CSC Feature Tweaks
Volume Boosting Sound Hack- Moderate
TouchWiz Smooth Scrolling
6thGear TWLauncher Swipe
Modified TouchWiz Launcher For Speed
No Safe Volume Warning Popup Message
Set TouchWiz Launcher Hotseat Dock From 5 To 6
Removed Samsung Keyboard Patent Block
Added Auto-Correct Back To Keyboard
CustomSettings changes
Signal and Wifi Colors
Network Signal Wifi Options
Notification Icon Options
Signal Bar and Network Option
Added Battery Bar Option
Added Reboot, Quick Recovery, Recovery & Download Options
Settings changes
Added 6thGear TWSwipe Options
Added Toolbox Settings
Version 2.2 - COI5 Changelog:
Based on the very latest Samsung S6 Edge+ COI5 firmware
Change Default Window Animation Scales and Build in New scales
Added over 900 fonts
Updated CustomSettings (AKA: Rom Control)
Added Rom Control Toggle (must enable extra toggles to view)
Set default toggle view to 6 (Option in Rom Control)
Added Launcher animations (Remove with flashable zip file)
Version 2.0 Changelog:
Added CustomSettings App
Added Enable Extra Toggles 34 (CustomSettings)
Added Viper4Android (CustomSettings)
SystemUI Pulldown Glitch Fixed (Gravity Setting)
Added Potato Clock, Gradients, CPU (CustomSettings)
Added Settings link to CustomSettings (also has launcher)
Added 3Minit to (CustomSettings)
Re-Added 3Minit Battery (zip file flash for removal)
Removed "host" (use AdAway)
Tweaks here and there...
Version 1.4 Changelog:
Added Device Status Official
Removed 3Minit Battery
3Minit Battery Flashable zip as a separate download
Change Default Window Animation Scales to 0.5x
Added dr.ketan's toggle expansion installer apk as a separate download
Fixerd S Voice issue
Version 1.3 Changelog:
Added 5 flashable zip file mods which you can download
Tweaked csc features
Tweaked floating window features
Added International Samsung boot animation - no more ugly white screen on boot
Added version in build.prop
Fixed keyboard issues
Here is a list of all the custom features in v1.0:
Based and built on the latest official Samsung G928T BOH6 firmware for Tmobile
SuperStock COI5 / BOH6 Custom rom version 1.0
Knox disabled
Rooted
Busybox
Deodexed
Zipalign
TMO bloat removed
5 way reboot menu
Private mode working
Camera during call
No boot up sound
Misc feature mods
3Minit Battery Mod
Center Clock Mod
Signature verification disabled
init.d support
Privacy mode fully working
Misc tweaks
Enabled copy to dialer
Recipient limit raised to 999
Disabled sms 2 mms conversion
No carrier iq
Added call button in call logs
Camcorder does not pause music
Samsung kb with auto correct
Camera during call
FW update removed
Added ATT radio icon removed LTE
Volume warning disabled
ime switcher in statusbar disabled
Private mode working
Netflix working
Call recording with enable/disable option on call screen
Option to revert back to stock keyboard with symbols using flashable zip
No kernel - The rom will use your existing kernel automatically
Installation:
======================================================
Following the step by step instruction will avoid many unforeseen issues.
======================================================
Prerequisites:
Must have a G928T device
Must have twrp or philz recovery installed
Must have a custom kernel flashed if coming from stock firmware
(this rom does not come with a kernel)
To avoid any type of issues please be sure you have already fully updated to COKC baseband
======================================================
Please Note:
1. If you are coming from another rom you already have the
custom kernel so there is no need to flash the kernel again.
2. Doing a full and complete wipe does NOT delete the kernel
3. Samsung Pay is not working in this or any other zip file rom
4. Flashing this zip file rom or any other zip file rom will trip knox
======================================================
Make sure to remove any fingerprints prior to flashing
Make a nandroid backup of your existing rom just in case
Copy the zip file rom into your internal sdcard
Boot into TWRP or Philz custom recovery
Do a full wipe including system, data, cache, dalvik cache & factory reset
Flash this rom
Have patience, let the phone boot it can take up to 10 minutes more or less
After it's done booting and you are at the setup wizard screen reboot the phone
Now you can start setting up your phone according to your personal needs
Don't drop the phone! LOL
========================================================
Here is a real FAST download link for the SuperStock v2.9 Custom Rom
based on the NEW COKC firmware:
https://www.androidfilehost.com/?fid=24399994186367057
========================================================
If you need help flashing the NEW COKC G928T odin flash firmware please go to
my other thread in the general forum for an easy and complete step by step guide
You will also find a FAST download link for the official G928T COKC firmware there
http://forum.xda-developers.com/tmo...rmware-g928t-complete-untouched-boh6-t3198387
=========================================================
SuperStock Custom Rom Extras - This is NOT a flashable zip file
Inside of this zip file you will find 4 flashable zip file mods
Blue Purple White Explosion Boot Animation
Stock Samsung Keyboard With Symbols
Stock Samsung Boot Animation
Stock Samsung Keyboard With Symbols and Stock Boot Animation
Flash each individual zip file mod using twrp or philz recovery
Here is the download link for the zip file package of 4 mods
https://www.androidfilehost.com/?fid=24052804347814995
=====================================================================
More Flashable Mods for The SuperStock Rom - All Versions
Install Samsung Stock keyboard with Symbols - Download here:
https://www.androidfilehost.com/?fid=24052804347815766
Revert Back to STOCK Screen Animation
https://www.androidfilehost.com/?fid=24052804347823689
Install BikiniGirl Boot Animation - Download here:
https://www.androidfilehost.com/?fid=24052804347818623
Install PACMAN Boot Animation with AUDIO
https://www.androidfilehost.com/?fid=24052804347822253
=====================================================================
Here is a little trick I just learned which might interest many of you:
If anyone has a problem going directly from "download mode" into "recovery mode" then here
is a way you can do it. I have never seen any posts about this procedure before but it works!
Press both of the volume keys, home key and the power button for about 15 seconds more or less
then as soon as the screen goes black let go of the volume down key and then as soon as you see
"seanroid is not enforcing" let go of all the keys and the phone will go directly into recovery mode
where you can power off the phone for a fresh power on or power down.
Give it a try a couple times, you have to be careful to look at the 4 buttons making sure that your
fingers are actually on all 4 buttons before pressing them.
This is very helpful and useful to know for people who are rooting and flashing custom recovery
for the first time or simply want to go directly from download to recovery mode for other reasons.
===========================================================
Please Note: You are fully responsible for what you do with your phone not me.
===========================================================
Here are the credits for the people who have made this rom possible:
@Mr Impossible for building this rom
@Chainfire for giving us root access (supersu)
@arter97 for building the rootable kernel for us
@bigbiff and @Dees_Troy for giving us twrp recovery
@dr.ketan for his excellent two way call recorder and his toggle extension app.
@KachowPow for his really excellent boot animations
@ficeto for creating the Custom Settings App
@kevinrocksman for his Super Camera
@pas2001 Bootanimation in my style
@mariozawa for the Potato Clock, Gradients, CPU
@gharrington 3Minit to (CustomSettings)
@samsung for making the best cellphones
@Misterjunky for creating this thread for everyone LOL
Have fun people...
I hope you enjoy this great rom...

Mine!
Mine!

Definitely will flash this rom if i get to root mine later today

Can someone just upload build.prop please

Sweet !!!
Sent from my SM-G928T using Tapatalk
---------- Post added at 04:06 PM ---------- Previous post was at 04:04 PM ----------
allenjthomsen said:
Can someone just upload build.prop please
Click to expand...
Click to collapse
Why do you need the build.prop? Its stock can pull it off any stock rom or odin flash
Sent from my SM-G928T using Tapatalk

I own a note 4 and my internet here is 3mbps thats why

Yess
Sent from my SM-G928T using Tapatalk

allenjthomsen said:
I own a note 4 and my internet here is 3mbps thats why
Click to expand...
Click to collapse
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=LMY47X
ro.build.display.id=LMY47X.G928TUVU1BOH6
ro.build.version.incremental=G928TUVU1BOH6
ro.build.version.sdk=22
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.1.1
ro.build.date=Mon Aug 31 10:31:25 KST 2015
ro.build.date.utc=1440984685
ro.build.type=user
ro.build.user=dpi
ro.build.host=SWHD4011
ro.build.tags=release-keys
ro.build.flavor=zenltetmo-user
ro.product.model=SM-G928T
ro.product.brand=samsung
ro.product.name=zenltetmo
ro.product.device=zenltetmo
ro.product.board=universal7420
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=exynos5
# ro.build.product is obsolete; use ro.product.device
ro.build.product=zenltetmo
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=zenltetmo-user 5.1.1 LMY47X G928TUVU1BOH6 release-keys
ro.build.fingerprint=samsung/zenltetmo/zenltetmo:5.1.1/LMY47X/G928TUVU1BOH6:user/release-keys
ro.build.characteristics=tmo
# Samsung Specific Properties
ro.build.PDA=G928TUVU1BOH6
ro.build.hidden_ver=G928TUVU1BOH6
ro.config.rm_preload_enabled=0
ro.build.changelist=5556672
ro.product_ship=true
ro.chipname=exynos7420
# end build properties
#
# HWUI_BUILD_PROPERTIES
#
ro.hwui.texture_cache_size=88
ro.hwui.layer_cache_size=58
ro.hwui.path_cache_size=16
ro.hwui.shape_cache_size=4
ro.hwui.gradient_cache_size=2
ro.hwui.drop_shadow_cache_size=8
ro.hwui.r_buffer_cache_size=4
ro.hwui.text_small_cache_width=2048
ro.hwui.text_small_cache_height=2048
ro.hwui.text_large_cache_width=4096
ro.hwui.text_large_cache_height=4096
ro.hwui.fbo_cache_size=16
#
# from device/samsung/zenltetmo/system.prop
#
#
# system.prop for universal7420
#
ro.sf.lcd_density=560
ro.arch=exynos7420
persist.demo.hdmirotationlock=false
ro.zygote.disable_gl_preload=1
ro.sf.lcd_density=560
# Multimedia property for Smart View
media.enable-commonsource=true
# Multimedia property for Camcorder Recording
media.sfrec.adj_frames=2
# System property for storage_preload
persist.sys.storage_preload=1
# VQG - User Agent Header for Video-Streaming Client
net.streaming.rtsp.uaprof=http://wap.samsungmobile.com/uaprof/
# slook
ro.slook.ver=1
# AFW
ro.config.afw=NONE
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.astcenc.astcsupport=0
ro.config.tima=1
ro.config.timaversion=3.0
ro.config.dmverity=true
ro.config.rkp=true
ro.config.kap_default_on=true
ro.config.ringtone=CLEAN_Tmo_Jingle.ogg
ro.config.notification_sound=Whisper.ogg
ro.config.alarm_alert=Morning_Flower.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
ro.config.ringtone_2=Basic_Bell.ogg
ro.config.notification_sound_2=S_Charming_Bell.ogg
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=256m
dalvik.vm.heapsize=512m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
ro.opengles.version=196609
ro.sf.lcd_density=480
debug.hwc.force_gpu=0
debug.hwc.nodirtyregion=0
debug.hwc.winupdate=1
drm.service.enabled=true
ro.hdcp2.rx=tz
ro.secwvk=220
ro.securestorage.support=false
ro.build.scafe=capuccino
ro.build.scafe.size=short
ro.build.scafe.shot=single
ro.build.scafe.cream=white
ro.sec.fle.encryption=false
ro.im.param.offset=7341648
ro.me.param.offset=7341728
ro.sn.param.offset=7341808
ro.pr.param.offset=7341888
ro.sku.param.offset=7341968
security.mdpp=None
ro.security.mdpp.ver=2.0
ro.security.mdpp.release=4
ro.security.vpnpp.ver=1.4
ro.security.vpnpp.release=5.2
security.mdpp.result=None
ro.frp.pst=/dev/block/persistent
ro.error.receiver.default=com.samsung.receiver.error
ro.config.dha_cached_min=4
ro.config.dha_empty_min=8
ro.config.dha_lmk_scale=2.363
ro.config.dha_pwhitelist_enable=1
config.disable_atlas=true
ro.security.mdpp.ux=Enabled
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.com.google.clientidbase=android-samsung
ro.security.icd.flagmode=multi
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.release.iss=false
ro.setupwizard.mode=DISABLED
ro.com.google.clientidbase.ms=android-hms-tmobile-us
ro.com.google.clientidbase.am=android-tmobile-us
ro.com.google.clientidbase.yt=android-samsung
ro.com.google.clientidbase.gmm=android-samsung
ro.com.google.gmsversion=5.1_r2
persist.sys.dalvik.vm.lib.2=libart.so
ro.build.selinux=1
dalvik.vm.isa.arm64.features=default
dalvik.vm.isa.arm.features=div
ro.config.knox=v30
ro.kernel.qemu=0
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.build.aapt.config.prefer=xxxhdpi
ro.build.version.sdl=2101

I installed twrp it came on but when I hit restart system it doesn't go in my phone keeps rebooting any ideas
Sent from my SM-G928T using Tapatalk
---------- Post added at 08:10 PM ---------- Previous post was at 08:08 PM ----------
Misterjunky said:
Mine!
Click to expand...
Click to collapse
Where do I get a custom kernel to install this rom.I tried the one that says 928 T-ODIN and it gets to my screen then keeps rebooting any other ones?
Sent from my SM-G928T using Tapatalk

raw2000j said:
I installed twrp it came on but when I hit restart system it doesn't go in my phone keeps rebooting any ideas
Sent from my SM-G928T using Tapatalk
---------- Post added at 08:10 PM ---------- Previous post was at 08:08 PM ----------
Where do I get a custom kernel to install this rom.I tried the one that says 928 T-Pain and it gets to my screen then keeps rebooting any other ones?
Sent from my SM-G928T using Tapatalk
Click to expand...
Click to collapse
You need to go directly from Download mode to recovery mode after the ODIN flash
you cannot allow the phone to bootup or reboot before entering recovery mode.
Here is the way to do it:
If anyone has a problem going directly from "download mode" into "recovery mode" then here
is a way you can do it. I have never seen any posts about this procedure before but it works!
Press both of the volume keys, home key and the power button for about 20 seconds more or less
and the phone will go into recovery mode where you can power off the phone for a fresh power on.
This is very helpful and useful to know for people who are rooting and flashing custom recovery
for the first time or simply want to go directly from download to recovery mode for other reasons.
Good luck!

SOOOOOOOOOOO Wanna flash this. Im still stuck on trying to flash a custom recovery LOL Got the whole ODIN procedure to go through, pass, successful, reboot, etc .... But when I go to use the recovery, its the stock recovery. I'm stumped

Can you please post actual build.prop file

re: flashing
ssmr2t said:
SOOOOOOOOOOO Wanna flash this. Im still stuck on trying to flash a custom recovery LOL Got the whole ODIN procedure to go through, pass, successful, reboot, etc .... But when I go to use the recovery, its the stock recovery. I'm stumped
Click to expand...
Click to collapse
Thats because you let the phone reboot or boot normally after you odin flashed.
Before odin flashing you must go to odin's options and select "auto reboot off" so
after the successful odin flash you will be on the "downloading" screen.
Once there then use the method I described in my previous post.

Make sure you are using odin 3.10.7 i think it is . Also when you finish flashing recovery with Odin dont let the phone reboot into the system by unticking reboot in odin. Instead hold power and volume down to have power down and immediately after hold volume up home and power button to reboot into recovery
Sent from my SM-G928T using XDA Free mobile app

re: build-prop
allenjthomsen said:
Can you please post actual build.prop file
Click to expand...
Click to collapse
Here is the build-prop file:
https://www.dropbox.com/s/i67anks6npjn12t/build.prop?dl=0
Good luck with it!

Help!
I did as you stated then after I got to twrp i powered down in twrp then pressed power and keeps on rebooting cant get into system.

Misterjunky said:
Here is the build-prop file:
https://www.dropbox.com/s/i67anks6npjn12t/build.prop?dl=0
Good luck with it!
Click to expand...
Click to collapse
Thankx for the help

re: step by step
raw2000j said:
I did as you stated then after I got to twrp i powered down in twrp then pressed power and keeps on rebooting cant get into system.
Click to expand...
Click to collapse
Here is what you need to do:
1: setup odin in it's options so it will not reboot the phone
2: odin flash the twrp recovery TAR file using odin
3: when it's done flashing disconnect usb cable.
4: use the method I described to boot directly from the download screen into recovery.
5: in recovery you MUST flash @arter97;s custom kernel
6: after flashing the custom kernel POWER DOWN the phone.
7: after powerdown reboot into recovery mode, it will be twrp
unless you are doing something wrong. (users fault).

Guess I cant root or twrp taking this crap back

SuperStock Rom MAJOR Update
SuperStock Custom Rom Major Update v2.0 - Many features added.
Check it out!

Frp unlock bypass updated expoits online and offline application win32

Advanced Box
​Mostly this tool contains
AABox Specialification No need root for all adb options. Need Root Only for Send Files to system and build.prop editor Pattern unlock
Update File New 20/11/2017 17.09v Direct from server official no Serial No Passwords​
# Features #
Frp Unlock tool
Adb Toolkit
Flashing and Recovery
Boot loop and boot repairs
FRP Unlock Qual, SPD, SPRD, MTK,
Aboot and boot img adb enable
Fastboot toolkit
First Time Oneclick and frp add gmail for 6.0.1 +​
SNAPSHOT​
{
"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"
}
​
Supported Vendor and ID
Acer 0502, ASUS 0b05, Dell 413c, Foxconn 0489, Fujitsu 04c5, Fujitsu, Toshib 04c5 ,Garmin , Asus 091e, Google 18d1, Haier201E,
Hisense109b, HTC 0bb4, Huawei 12d1,Intel 8087,K-Touch 24e3,KT Tech 2116,Kyocera 0482,Lenovo 17ef,LG 1004,Motorola 22b8,
MTK 0e8d,NEC 0409,Nook 2080,Nvidia 0955,OTGV 257,Pantech 10a9,Pegatron 1d4d,Philips 0471,PMC-Sierra 04da,
Qualcomm 05c6,SK Telesys 1f53,Samsung 04e8,Sharp 04dd,Sony 054c,Sony Ericsson 0fce,Sony Mobile Communications 0fce,Teleepoch 2340,Toshiba 0930,ZTE 19d2,​
Version Log List in order​
1. Artiven Box 1.148.0 Alpha [ 01-08-2014 ]
# First Release
# Fixed fastboot codes for lg
# Fixed bootloader unlock
# New tusk
2. Artiven Box 1.149.6 Beta [ 06-09-2014 ]
# Fixed Auto close
# Fixed backup options
# Fixed outfixed apps
# Root for mtk updated and update zip
# data wipe
# pattern unlock
# flash img, cwm flashing, reboot mode all.
3. Aabox 2 stable (CMD) Commander [ 05-05-2015 ]
How to install..!
1) a) You must install aabox alpha or suite pack 1.148 or 149
b) download aabox 2c updater 2.157
2) unrar or unzip file you will get only 1 exe file.
2) b) copy it to c:\artiven\aabox\ = replace it with old file or paste just and open it to use...
3) when open it as adminstrator .. use get full access to aabox.
# Update Pack for 1.149.6
# 5 features Added
4. AABOX ( 2 16.1 ) ( Dardbread ) [ 2016.11.11 ]
After a big Gap and nearly 8 months from CMD Screen-shots at fb page Screen Shots of Repaired and added
# Fastboot Flash added
# Sony Unlock Bootloader Tested and Success
# Sony feature added
# Dir Style Changed (because making a windows UI - bt dont know when)
4. AABOX ( 2017 - 17.1v ) ( Exyno ) [ 2017.1.10]
After along Push- ViT Team Build a GUI based Tool Screen Shots of Repaired and added
# New Unlocks and Repair Tools
# Lenovo Features Added
# MT6592 Added
# Dir Search in Mtk for unbooting to boot)
# Auto Repair
# IP Connect Adb
# adb full Controls
# Easy for Mobile Repairs
# ADB Installers-Reboot-Boot files-Find Phone
# AABOx Flasher v2
# Fastboot recovery Fixed
Download link will be at 2017-01-10
5. AABOX ( 2017 - 17.6v ) ( Froyo ) [ 2017.6.15]
All in 1 adb and frp tool Screen Shots of Repaired and added
# MTK chipsets added
# Lenovo A319 Features Added
# FRP unlock Knox 2.6 Added
# Com port added)
# mtk frp unlock
# Frp 6.0.1 for samsung
# adb full Control Spreadrum
# Fixed adb bugs and hanging
# ADB Installers
# AABOx Frp
# Fastboot boot.bin
AABox2 ( 2017 - 17.7v ) ( GoD ) [ 2017.8.20]
All in 1 adb and frp tool Screen Shots of Repaired and added
#SPD Surported
#MTK Wipe ADDED
#More Android devices scripts
#UI Changes with High powerfull expoits
#Adb.exe bug fix
#Android Direct kernel inject expoits
#Power to com ports SAM and LG QUALCOMM
#UNLOCK via Bootloader and FrP
#MTK Module alpha version with pack
AABox2 ( 2017 - 17.7.1v ) ( GoD ) [ 2017.8.30] Only Update
All in 1 adb and frp tool Screen Shots
#Etel i210 FRP removal ADDED
#re connect adb bug fixed
#all gui overlap fixed
#Radio-button stay fixed
#CMD pop up freeze fixed
#error 016 at frp lenovo fixed
AABox2 ( 2017 - 17.8v ) ( HotFire ) [ 2017.9.21] Full StandaloneVersion
#Box Detect Bug Fixed
#Base board detector added
#FRP KNOX 2.7 bypass added
#FRP gmail Browser bypass added
#adb disconnect bug fixed
#Added new dll files for expoit
#Script errors fixed
#.Net updated for 4.X +
#Com Port dial helper for FRP bug fixed
#Stability application improved
#New Testing coding added for trace KNOX
#System hack for gmail bypass apk added
AABOX2 17.8.1v Hotfire Standalone
---------------------------------
#Expoit 2.3v for KNOX 2.6 updated
#Expoit Andoid 6.0.1 Fixed errors
#ADB net framework error fixed
#Browser Gmail added new scripts
#Fixed error 0x023 and 0x024
#Refreshed File Builds
AABox2 ( 2017 - 17.09v ) ( HotFire 2 ) [ 2017.11.20] Full StandaloneVersionScreenshot and Comments
#New UI Updated
#fresh Full version Files added
#MTK Module 0.3v added 1711v Build
#brom updated for boot.img repack
#AndroidCtrl.dll updated
#Welcome Screen added with online
#Keyboard for android adb
#Hard and soft keys added via adb
#Update.exe added for online
#Online Script fixed
#Needed Internet
#2017 Frp Scripts added online
​
17.09v TODAY
Update File New 20/11/2017 17.09v Direct from server official no Serial No Passwords​
Next VerSion :
Release [2017-xx] | Codename [ --- ] | Build [17xxx] | ViT [xxx]
​
17.8 RELEASE TODAY UPDATED TO XDA AND DOWNLOAD LINKS WILL BE AVAILABLE ON 20-11-17 ONWARDS​READ POST 2nd before install or downloading for Help​
Official Site Official Facebook Page
All Downloads And Version Here at Download Page AABox
This tool/box/software build for helping a dev or repairer for more experience and shorted for cmd long commands. If you use this tool u will never use a software box for frp or system repairs, most of features added for easy tasking. Reading and knowing it would help to repair as said and must read 2nd Post for any details
This tool is also being continued in Win32 GUI tool As a DEVPROJECT
IN XDA Forum - Click here to Link in xda --------- AABOX New Page download​
Wait:: Note Before Download
Read 2nd post before download... always download latest download available below AAbox2 17.09v is a stable all in one installer for now!​Dear Friends i would like see my thanks been pressed.. If you like to have more versions with more features Please give me a thank

Thread closed as duplicated with https://forum.xda-developers.com/android/software/frp-unlock-bypass-tools-online-updated-t3709593

[DEV][Discontinued] WAS-Lxx [EU] Toolkit [0.0.0.5] All-in-One

INFO
I sold my P10 Lite, based on Huawei's decision to no longer provide bootloader unlock codes.
For a generic version of this project (ADB-Overlay) have a look at this thread.
The latest build of this project is still available.
---
Hello together,
here is a toolkit for the P10 Lite, it's designed to work primary with root (THE MOST TIME) so be careful what u are doing, specially if u are using the "Explorer". (Deleting the wrong file/folder on root lvl, could bring u in bad trouble!)
-
To all who used already my P9 Lite toolkit, there is currently not all available which u know from the old version, but i'll extend this toolkit in the next days. So, no worries about missing functions, they'll appear in some of the next builds.
-
About the usage,
- For a basic UI-Help just press F1
- If ur device is not detected u can switch off the "Device check" on the "Disclaimer" view (If u own a P10 which is not detected pls share a screenshot of the "adb devices -l" (l = lowercase L) command)
- U can also switch the (su -c) usage off (in the explorer view), BUT! after u performed any action which requires root, the trigger will be automatically switched on. (There is no other option, because my dll know only, use root or don't do so... There is no use root part-wise)
But anyways, i'm NOT responsible for any damage to your device!
Little preview of what u get
{
"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"
}
Tested Devices
Huawei P10 Lite [WAS-LX1A] [SINGLE-SIM]
Requirements
Platform: x86/x64 (Windows)
Frameworks: min. .NET 4
(Installed ADB/Fastboot driver)
Download
Mirror: See attachments
Mirror #1: GoogleDrive
XDA:DevDB Information
WAS-Lxx [EU] Toolkit, Tool/Utility for the Huawei P10 Lite
Contributors
k1ll3r8e
Version Information
Status: Stable
Current Stable Version: 0.0.0.5
Stable Release Date: 2018-08-01
Created 2018-03-30
Last Updated 2018-08-15

How-To
[Q:01] My device is not recognized by the toolkit?
1. Make sure NO adb-server is running!
2. U need to start ur device in android with enabled USB-Debugging (see the screenshot)
(Only in adb mode my toolkit can detect ur device)
3. Make sure that u granted adb access on ur device
(A popup will appear on the device and asks u to grant access.)
Try also to restart the toolkit after u granted access on ur device.
U can also check the device state by opening a cmd/terminal prompt and typing:
Code:
cd path\to\the\toolkit\adb
adb devices -l
check if ur device is listed as follows:
XXXXXXXXXXXXXXX device product:WAS-Lxx model:WAS-Lxx device:XXXXXXX
If ur device can't boot into Android or still didn't get detected, well, just deactivate the "Device Check" on the "Disclaimer" tab. And follow the description.
[Q:02] What does the Lxx Cxxx Bxxx mean?
The Lxx is the device model, the Cxxx is the region/operator identifier and the Bxxx is the build number.
Here is a short list about the regions/operators
ID (Cxxx) = Region/Operator | custom.bin (content)
----------------------------------------------------------------------------------------------------------------------------------------------------
C02 = Vodafone
C10 = Russia
C21 = Telefonica / O2
C40 = Czech Republic Telefonica / O2
C55 = Italia TIM
C66 = VIPmobile | vip/rs
C86 = Spain Yoigo
C109 = Amena/Orange
C112 = Latin America
C113 = Wind/Italy | wind/it
C121 = Türkei
C123 = Switzerland
C150 = T-Com | dt/de
C151 = India
C185 = North-Africa/Middle-East | hw/meafnaf
C209 = Asia (Pacific)
C212 = Iusacell/Nextel
C249 = Serbia Telekom
C432 = Nordic-European | hw/eu
C470 = Asia (Pacific)
C605 = Colombia
C637 = Spain
C636 = Asia-Pacific | hw/spcseas
C675 = India
C706 = New Zealand
C900 = GLOBAL
More comming soon...
Big THX for some of those "identifier" goes to:
@lost3
@baduncle
[Q:03] I want share my custom.bin & oeminfo, what i need to do?
U can get the files via the "Dual-/Single-SIM -> Export" or u can do the following steps (root required).
Open an terminal/cmd prompt and navigate to ur adb installation or the toolkit directory (path/to/the/toolkit/adb) and type the following commands.
Code:
adb shell
su
cat /data/custom.bin > /storage/emulated/0/custom.bin.bak
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/storage/emulated/0/oeminfo.img.bak
exit
exit
adb pull /storage/emulated/0/custom.bin.bak custom.bin.bak
adb pull /storage/emulated/0/oeminfo.img.bak oeminfo.img.bak
Now u have 2 files, the custom.bin.bak and the oeminfo.img.bak just zip them and upload them to GoogleDrive or DropBox, etc. and share the link in this thread.
[Q:04] How can i manually boot into a specific mode?
Bootloader:
[device] = Turn the device off - Connect it to the PC - Press and hold: [Vol-]
[adb] = adb reboot bootloader
[fastboot] = fastboot reboot bootloader
E-Recovery:
[device] = Turn the device off - Connect it to the PC - Press and hold: [Vol+]
[adb] = N/A
[fastboot] = N/A
Recovery:
[device] = Turn the device off - Disconnect it from the PC - Press and hold: [Vol+ Power]
[adb] = adb reboot recovery
[fastboot] = N/A
Normal Boot:
[device] = Power button / Power button menu
[adb] = adb reboot
[fastboot] = fastboot reboot
Update Mode:
[device] = Turn the device off - Disconnect it from the PC - Press and hold [Vol+ Vol- Power]
[adb] = N/A
[fastboot] = N/A
[Q:05] Does the Dual-Sim upgrade survive an OTA?
Yes, the Dual-Sim modification will stay until u flash another oeminfo.
[Q:06] I upgraded to Dual-SIM and there is only one IMEI shown?
That's absolute normal... Because, u had a single-sim device before, so the device hold only one IMEI and the 2cd sim will use the same IMEI as the 1st sim or as shown the "0000000000000000".

Changelog
2018-08-01 - 0.0.0.5
* Added a Remote-Desktop
* Added a "partition selector" (recovery [Nougat], recovery_ramdisk [Oreo])
* Added a rooting option for Oreo
* Fixed a few bugs
* Realigned a few container
2018-04-21 - 0.0.0.4
* Added on the Device-Info view the BusyBox check
* Added the Phone control
* Added the Root menu (just waiting for permissions to include a zip)
* Added some features to the Explorer "View" menu (e.g. Sync with Treeview, Layout, Sort)
* Added a Display-Trigger to the "Power-Button" menu
2018-04-10 - 0.0.0.3
* Fixed a crash which appeared during device connection on the Explorer view
* Switched the whole window stuff to my new GlassWindow
* Added a AlphaChannelSlider (left beside the [--] button) for those which don't like transparent windows
* Added a Device-Info view
2018-04-01 - 0.0.0.2
* Fixed the icon bug (Big Icons, List)
* Re-positioned the "View" menu and made 2 of them, one for each view
* Refactored the "Button" layout, that they match now with the rest of the dark theme
* Added a fallback color "#2C2C2C" for those who got maybe the error message that the Glass-Effect couldn't be applied
* Added the "Shell-Tools" menu
* Added the 1st tweak (Pro-Mode)

Bug-Tracker
*FIXED in 0.0.0.2
- Noticed already the missing icons in the "Explorer" (Big Icons + List)
(Bug is already solved and will be fixed in the next version)
Known-Issues
- The "Explorer" "Big Icons" looking a bit ugly, that's because the p/invokes won't give me the "Extra Large" icons... I still work on it, so maybe it's fixed in the next version.
--
Drag 'n' Drop on any Explorer view, from outside the Application won't work until u run everything as Admin... That's a Windows UAC restriction and based on the fact, that we need the right's to create/delete/modify files/folders under Win8++ on the system HDD. (Like ADB pull for export of the oeminfo and custom.bin)
Missing Tweaks from the P9 Lite Toolkit
- As the screenshot shows, i managed to activate the "Double-Tap" menu, but that's all... The Double-Tap it self doesn't work... So there will be no "tweak" for this. - (Additional Info: The Double-Tap works^^ But ONLY on the lock-screen... And ONLY to turn the screen off... What a joke...)
- USB-OTG, is not available because, so far i know, u need a special kernel for it. (Which i can't provide, atm)
- AppTwin, because it should be enabled on any P10 Lite by default
Little - Update (1+2+3+4)
- I added a screenshot of the upcoming release, with integrated "Phone" control. (Currently only Call/Dial works)
- Added another screeny, now (Call/Dial/Add) is possible. Add, needs still interaction on the device side, like which "provider" (Device, Google, etc.) u want to choose. Dial, will insert the number in the default dialer, or it gets captured by any USSD protection. Call, will immediately start a call to the provided number.
- Just tested to send USSD-Codes like "*#06#", but it seems that u really have to type them... Even sending "*#06" and manually type the "#" doesn't work... U have to delete and re-type the whole USSD-Code...
- Added the final look of the "Phone". (At least, Add, Call, Dial, Hang-Up) is now possible.
For those which also use XAML, here are the control-button-geometries i created:
Menu-Button
Code:
<Path Fill="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}">
<Path.Data>
<GeometryGroup>
<EllipseGeometry Center="2,2" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="7,2" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="12,2" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="2,6" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="7,6" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="12,6" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="2,10" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="7,10" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="12,10" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="7,14" RadiusX="1.5" RadiusY="1.5"/>
</GeometryGroup>
</Path.Data>
</Path>
Call-Button
Code:
<Path Data="M 1.25,5.55 A 8.5,8.5 0 1 1 0.75,7 Z M 5,9 8,13 13,5" Stroke="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}" StrokeThickness="1"/>
Hang-Up-Button
Code:
<Path Data="M 1.25,5.55 A 8.5,8.5 0 1 1 0.75,7 Z M 5,13 13,5 M 5,5 13,13" Stroke="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}" StrokeThickness="1"/>
Dial-Button
Code:
<Path Stroke="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}" StrokeThickness="1">
<Path.Data>
<GeometryGroup>
<EllipseGeometry Center="9,9" RadiusX="8.5" RadiusY="8.5"/>
<EllipseGeometry Center="6,5" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="9,5" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="12,5" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="6,8" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="9,8" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="12,8" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="6,11" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="9,11" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="12,11" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="9,14" RadiusX="0.5" RadiusY="0.5"/>
</GeometryGroup>
</Path.Data>
</Path>
Delete-Button
Code:
<Path Data="M 0,7.7 5,2 16,3 16,12 5,13 Z M 8,5 13,10 M 8,10 13,5" Stroke="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}" StrokeThickness="1"/>

WAS-LX1AC432B204dual
oeminfo

WAS-LX1AC432B206dual
oeminfo

I tested it on my WAS-LX1 C10 DS/ It works.

Perfect
Thank you !

rom issue
Dear Developer!
I suffering with a strange problem, i also opened a question thread about:
https://forum.xda-developers.com/p10-lite/help/please-help-fix-issue-t3805333
I'm not tried your toolkit yet, but i guess it maybe could help me... First: I would like to ask you what do you think about my issue(?). Probably you are much more technical than me, if you were able to create a toolkit for p10 lite... Should i try to fix my phone with your toolkit or can you suggest me any method? Do you have any idea what I could do?
Thanks you in advance!
Greets, NSX

nsx82 said:
Dear Developer!
I suffering with a strange problem, i also opened a question thread about:
https://forum.xda-developers.com/p10-lite/help/please-help-fix-issue-t3805333
I'm not tried your toolkit yet, but i guess it maybe could help me... First: I would like to ask you what do you think about my issue(?). Probably you are much more technical than me, if you were able to create a toolkit for p10 lite... Should i try to fix my phone with your toolkit or can you suggest me any method? Do you have any idea what I could do?
Thanks you in advance!
Greets, NSX
Click to expand...
Click to collapse
Use only stock ROMs for now, cuz there's no daily driver Customs for P10 Lite yet. Stock Oreo is really good. You can use HwOTA to flash stock ROMs.

nsx82 said:
Dear Developer!
I suffering with a strange problem, i also opened a question thread about:
https://forum.xda-developers.com/p10-lite/help/please-help-fix-issue-t3805333
I'm not tried your toolkit yet, but i guess it maybe could help me... First: I would like to ask you what do you think about my issue(?). Probably you are much more technical than me, if you were able to create a toolkit for p10 lite... Should i try to fix my phone with your toolkit or can you suggest me any method? Do you have any idea what I could do?
Thanks you in advance!
Greets, NSX
Click to expand...
Click to collapse
Heyho,
the "NRD-testkeys" are normally an issue with the "cust" partition. That means that ur oeminfo doesn't match with ur "cust" version. Let me explain... If u switch from SS to DS u change the device model (ID - Lx1 -> L21) this causes some problems on the "cust", because there is only one folder existent. The folder matching to the device u had before the switch. So all settings like "phone/umts" etc. are now invalid and can't be found under this model (ID). Because the folder simply doesn't exists.
How to fix it?!
U have to install/flash a complete stock rom via dload. - Get u FOR EXAMPLE an oeminfo like "L21AC432B183" and the rom "L21AC432B183", now u have to flash the oeminfo and straight after it, via dload, the FW upgrade.
-
During the flash of the "L21AC432B183" the system will check that u have "now" a L21 and will align the "cust" to that device.
Hope i could help u to understand how things work
Regards,
Sebastian

k1ll3r8e said:
Heyho,
the "NRD-testkeys" are normally an issue with the "cust" partition. That means that ur oeminfo doesn't match with ur "cust" version. Let me explain... If u switch from SS to DS u change the device model (ID - Lx1 -> L21) this causes some problems on the "cust", because there is only one folder existent. The folder matching to the device u had before the switch. So all settings like "phone/umts" etc. are now invalid and can't be found under this model (ID). Because the folder simply doesn't exists.
How to fix it?!
U have to install/flash a complete stock rom via dload. - Get u FOR EXAMPLE an oeminfo like "L21AC432B183" and the rom "L21AC432B183", now u have to flash the oeminfo and straight after it, via dload, the FW upgrade.
-
During the flash of the "L21AC432B183" the system will check that u have "now" a L21 and will align the "cust" to that device.
Hope i could help u to understand how things work
Regards,
Sebastian
Click to expand...
Click to collapse
Thank you very much for your help. im going to try all of this on next weekend, because workdays i have to use my phone.
greets, NSX
---------- Post added at 12:18 PM ---------- Previous post was at 11:59 AM ----------
k1ll3r8e said:
If u switch from SS to DS u change the device model (ID - Lx1 -> L21) this causes some problems on the "cust", because there is only one folder existent.
Click to expand...
Click to collapse
just a quick question: lx1 is single sim and l21 for dual sim?
Because i had a dual sim model but my sw version was lx1
did i misunderstood something?
btw, i having a very strange problem with the phone, out of the box. seems like a sw render problem. for example in nova launcher i have strange animation distortion and diatorted masking. i was hoping it will be fixed too with changing the rom but this problem still exist.. do you thing it can be because of some wrong factory software inatallation?
thanks, NSX

nsx82 said:
Thank you very much for your help. im going to try all of this on next weekend, because workdays i have to use my phone.
greets, NSX
---
just a quick question: lx1 is single sim and l21 for dual sim?
Because i had a dual sim model but my sw version was lx1
did i misunderstood something?
btw, i having a very strange problem with the phone, out of the box. seems like a sw render problem. for example in nova launcher i have strange animation distortion and diatorted masking. i was hoping it will be fixed too with changing the rom but this problem still exist.. do you thing it can be because of some wrong factory software inatallation?
thanks, NSX
Click to expand...
Click to collapse
Heyho,
np
-
Yes, the "Lx1" are always the SS and the "L[1-9]1" are the DS variants. - Btw. u can't see the "real ID" under "Settings -> Info" to see the "real ID" u have to look in the "current" oeminfo.
-
I wrote a tool for this kind of tweaking/exploring, have a look at it, u can get it here
EDIT:
About the issue with the display/animations, it could also be a problem with the HW... I have seen a few forum posts about "factory delivered" broken chips etc.... Maybe there is something else wrong, if it was really from the 1st day u got it.
Regards,
Sebastian

Little Update
Heyho together
-
Here is a little preview of the upcoming update.
* Added a Remote-Desktop (touch, swipe and keyboard are working so far)
* Improved the speed
* Fixed a few minor bugs
Release should be in 2-3 days
Version 0.0.0.5 is online!
Regards,
Sebastian

k1ll3r8e said:
[Q:03] I want share my custom.bin & oeminfo, what i need to do?
U can get the files via the "Dual-/Single-SIM -> Export" or u can do the following steps (root required).
Open an terminal/cmd prompt and navigate to ur adb installation or the toolkit directory (path/to/the/toolkit/adb) and type the following commands.
Code:
adb shell
su
cat /data/custom.bin > /storage/emulated/0/custom.bin.bak
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/storage/emulated/0/oeminfo.img.bak
exit
exit
adb pull /storage/emulated/0/custom.bin.bak custom.bin.bak
adb pull /storage/emulated/0/oeminfo.img.bak oeminfo.img.bak
Now u have 2 files, the custom.bin.bak and the oeminfo.img.bak just zip them and upload them to GoogleDrive or DropBox, etc. and share the link in this thread.
Click to expand...
Click to collapse
I guess your Q&A kind of answers my question, though I want to be absolutely sure:
Sharing your oeminfo (and/or custom.bin) file(s) with others, does not give away any personal/unique info. I checked my oeminfo with a HexEditor and it seems to include my Firmware upgrade history (at least the last two updates), IMSI (only SIM/Network Operator - unless I overlooked something), and those hmac/&token values. With these infos nobody should be able to "do bad stuff" - am I right?
Please correct me if I'm wrong. Thanks in advance for any input, cheers!

callmeWhiskers said:
I guess your Q&A kind of answers my question, though I want to be absolutely sure:
Sharing your oeminfo (and/or custom.bin) file(s) with others, does not give away any personal/unique info. I checked my oeminfo with a HexEditor and it seems to include my Firmware upgrade history (at least the last two updates), IMSI (only SIM/Network Operator - unless I overlooked something), and those hmac/&token values. With these infos nobody should be able to "do bad stuff" - am I right?
Please correct me if I'm wrong. Thanks in advance for any input, cheers!
Click to expand...
Click to collapse
Heyho,
if you would have used my OEMInfo Tools, you would have seen that those values are no secret.
-
For example, the FW builds are needed to determine the current OS and if needed, the fallback/restore versions. Also the HMAC is needed for the OTA (the HMAC is used in conjunction with your IMEI, so the HMAC alone, is worth nothing). There is also a "Tamper-State" when and how often you unlocked/rooted your device.
But so far i saw, there are no "personal" data, like the IMEI or the SIM-Card Number. Maybe they are stored as one of those checksums (md5/sha1).
Regards,
Sebastian

k1ll3r8e said:
if you would have used my OEMInfo Tools, you would have seen that those values are no secret.
-
For example, the FW builds are needed to determine the current OS and if needed, the fallback/restore versions. Also the HMAC is needed for the OTA (the HMAC is used in conjunction with your IMEI, so the HMAC alone, is worth nothing). There is also a "Tamper-State" when and how often you unlocked/rooted your device.
But so far i saw, there are no "personal" data, like the IMEI or the SIM-Card Number. Maybe they are stored as one of those checksums (md5/sha1).
Click to expand...
Click to collapse
Thank you very much for clarifying and shedding some light on this, Sebastian!
From what I've read, reconstructing (files) from checksums doesn't (really/easily) work - though in theory (if enough additional parameters are given, and IMEI/IMSI are kind of short strings) it could be reverse engineered - unless I interpreted my research findings wrong :victory:
I assume it's safe though
Liebe Grüße nach Delmenhorst!

Hi world(first post since android(previous windows mobile member of xda)),
I have P10 lite for almost a year(not rooted for warranty issues).
I wanted to perform a stock firmware backup before I endulge in rooting/custom ROM.
Is that possible with TWRP(with or without rooting), and are there any how-to's?
Sorry for being such a newbie, just like to upgrade to 8.0 and revert back to stock in case of a problem or warranty issues.
Thank you.

Recovery