C6916 14.4.B.0.56 Kernel Only FTF - Xperia Z1 General

PLEASE DELETE,
the best way is to root 14.4.B.0.37 install recovery but don't deodex then apply this update(14.4.B.0.56) via ota then deodex and do your thing. few things changed in /system
Use flashtool and flash via flashmode
Original 4.4.4 build number but notice the kernel date
Note: Root is kept, System Still Writable Etc Etc Etc
+ I've noticed instant screen wakeup and faster camera initialization
- after a day of use the camera isnt as fast but it hasnt lagged to the point where it freezes at a black screen
- upon further investigation, libs and firmware has been replaced also i believe , try to work things in, might just flash the whole system partition from recovery, should still have root at least i believe
#Edit
after reading around it looks like this is the 14.4.A.0.157 update but for the Z1S, they report the same fixes, still need to find out if system was changed
{
"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"
}
can anyone else confirm and anyone know if system files or framework was changed?
iffy about just changing the build number, doesn't feel clean xD

Related

Strange thing happens when trying to flash kernels to my arc s

{
"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"
}
Just as the picture above shows, when flashing kernels made by devs, it says 1bad blocks encountered in the fastboot window, and when flashing finished and try to start up the phone, the phone just vibrate once and lose response. The screen even doesn't turn on.
I have unlocked the bootloader.
The only way to fix the phone after flashing a kernel is using the flashtool to flash a ftf file.
Do you guys know why this thing gonna happen?
you flashing kernel that arent compatible maybe?
from my ARC using I.See.Ass
rashid.fairus said:
you flashing kernel that arent compatible maybe?
from my ARC using I.See.Ass
Click to expand...
Click to collapse
Nope, I have flashed kernels made by Doomlord, Jasonstein, FXP, non of the worked.
you have broken nand
send phone to service for nand replacement (of board replacement)
dun know the non-unicode language will affect the DOS code or not , cause u using the chinese non-unicode .... need ask those pro to conform

[Q] Unfortunately, LGSetupWizard has stopped

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I always get this message when installing a ROM on my D805 (except the AOSP).
this message comes right back to the start of the initial configuration, and not leave it!
someone has gone through this?
OBS: can I install any ROM D802 I have this same message!
sorry for the google translator: (
how do you go to stock rom, is it purely stock or custom?
try factory reset lol. will lose all data.
wipe the app that fc data\caches.
in recovery fix permisions, only if you have a recovery on phone. if you do have update it
on aosp its not there.
Do you do clean installs
The only one that actually helped me out is deleting the lg setup*.apk from the flashable zip.
Yes I always got this when installing a new rom on d802. was really annoying and i had to uninstall the setupwizard.apk and odex from system/app. i returned my phone to stock original then rerooted and installed blackpearl and this has gone away however.
Thank you, excluding LGStartupwizard.apk had worked to install the ROM.

TMO D801 V20E Update

Hello all,
I have tried to make a flashable zip to where I do not have to flash the KDZ but also make it deodex'd, zipaligned, etc, etc...all that good stuff...but I have failed...
So now I'm reaching out for assistance...kernels are my forte...not so much ROM stuffs...
Here is a dump of the ROM from the KDZ...
https://mega.co.nz/#!JExxEKCZ!0-w1xfwB8TaOgo0S_43L6i2g03KmH3U2nJVr4TWd-TU
And here is a flashable zip for the baseband...It works with Cloudy G3...as that's what I'm currently using...
https://mega.co.nz/#!sEgnEQ6J!h1HzF8hELUJUwr0nxbuzCryPf-sURA2wpIF7KvvRORY
Any suggestions and help are welcomed!...there was a thread with a template but we do not have cust.bin...i tried some of those rom kitchens...but it doesn't account for lokifying boot.img...i've tried to update the updater-script...the furthest I've gotten was to the tmobile boot screen and then it stops there...I'm thinking it's the kernel...I've tried using my personal kernel from V20E source but i get the blinking lights but nothing else...
I'm stumped... *sigh*
It was easier to flash the KDZ > ran TowelRoot > installed SU > ran Autorec > rebooted...I did get the white lines...so I switched to my custom stock kernel...with the stock ramdisk...pushed that to my phone while in TWRP...time to freeze/remove the bloat...and set up xposed...
Cheers...
{
"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"
}
Sent from my LG-D801 using Tapatalk

Keyboard Glitch/Broken after Rooting/Flashfyre

Hi guys,
I have a fresh S7 SM-G930V(Android 6.0.1). Which i logged in via google and it downloaded all my previous apps on my old phone(i assume it automatically does)
I was following https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039.
And now my keyboard is now starting to look weird
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I completed all the steps and rooted to the following image "Samsung_G930x_QC_Rooted_BOOT.TAR (any Samsung Galaxy S7) (MD5 hash 948A01ECCF280828DFD13AC366F6FE85)"
and used Odin3_v3.12_PrinceComsy.zip as opposed to the other odin.
Any ideas besides using another keyboard app?
EDIT: Just flashed back to G930VVRU4API3, which i thought was my stock rom but has a purpleish first time start up which i thought should be blueish?
Going to try and re-flash a root after work again.
UPDATE2: I Follow the rooting/xposed steps again and now i got my normal keyboard back. The difference is that the verizon startup is white/red while when i first ever used the phone it was a blueish/purple verizon start up. But i feel that it was definitely 6.0.1 with PI3.
Accessing the phone via cable seems extremely slow but thats for another thread...
I am now rooted with a working keyboard, now time to work on the other issues....

need help installing custom rom

im trying to install a custom rom on my mi 9t. its not the first time that ive done this, but now its all gone wrong. I have unlocked the device, flashed twrp, and got the rom/gapps ready to go, but when i go to install it i get 2 errors, "E:unhandled flag: wrappedkey" and "E:unable to decrypt fbe device". and just to make things worse, i came to the brilliant conclusion that the errors were from the old rom interferring with the new one that i was trying to install, so i deleted the system partition and wiped my os.
feel free to call me as many names as you like, so long as you also provide some help aswell haha.
thanks guys
{
"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"
}
If you have twrp I stalled, then you just need to factory reset in recovery, format partition, flash dmverity, flash ROM and optionally root. There is nothing you could do wrong if you choose proper ROM for your device - each ROM has instruction what you need for it to work properly

Categories

Resources