Just dropping this here since I didn't see anything for an US version.
My thoughts on MM: fast, lots little Sony bugs were fixed (double tap for example), reception seems to be better and doze works very well. However, I feel that when the screen is on, it drains faster than LP.
Disclaimer: This worked for me. I provide no support for this. Do a TWRP backup.
FW info:
Device: Xperia Z3 (D6603)
CDA: 1288-7827
Market: USA
Operator: Customized US
Network: GLOBAL-LTE
Release: 23.5.A.0.570 / R4D
Link to my pre-rooted flashable zip: D6603_23.5.A.0.570_1288-7827_R4D_US_CUST_-RecRoot_v3-SuperSU_2.71
PRFC settings:
FW: D6603_23.5.A.0.570_1288-7827_R4D.ftf
SuperSU: BETA-SuperSU-v2.71-20160331103524.zip
Recovery: RecRootV3_combined.zip
Check: Kernel, Modem, LTALabel, Legacy Mode
Other zips and files:
Xposed: xposed-v81-sdk23-arm.zip, XposedInstaller_3.0_alpha4.apk, xposed-uninstaller-20150831-arm.zip (handy)
Modules: App Settings, GravityBox [MM]
Programs: TitaniumBackup 7.3.0.2 (restore data only)
Debloat by @frixed: Slimcore Debloat Script and I also deleted all the Google apps from the backup folder, saved additional 400mb.
Things that did not work:
- Xposed v82 kept getting deactivated on me. There is a v83 that came out over the weekend.
- Xposed modules: APM+ does not boot into recovery and @serajr modules don't work at all unfortunately
- Location Based Wifi port by @niaboc79
Things to test:
- Stereo sound mods, hopefully there's one out there that will allow louder output as well
- Gap Fix, messed up the phone
- Replacing the bootanimation, worked
Thanks for the pre-rooted file. Just wanted to know thougts from others that have tried this version and if it's safe to dirty flash over other region Lollipop.
chepeliyas said:
Thanks for the pre-rooted file. Just wanted to know thougts from others that have tried this version and if it's safe to dirty flash over other region Lollipop.
Click to expand...
Click to collapse
I'm going to say do a TWRP backup first and try a dirty. A few others in the MM Recovery thread had done that and worked out fine.
I would not personally do this though. I also highly advise against it if you have Xposed installed. You will bootloop for sure.
Cow07 said:
I'm going to say do a TWRP backup first and try a dirty. A few others in the MM Recovery thread had done that and worked out fine.
I would not personally do this though. I also highly advise against it if you have Xposed installed. You will bootloop for sure.
Click to expand...
Click to collapse
Perfect, thanks!
1) Thank you very much for putting together this pre-rooted ROM; you're the real MVP.
2) I am having issues getting NFC to work. When I first clean install this zip (wipe EVERYTHING -> install) and boot, NFC tries to update its firmware and then returns Failed (-1). I reboot, and I am then unable to toggle the NFC on switch it settings. Has this happened to anyone else? Any thoughts on what to do next in order to troubleshoot it? I've run into this issue with both this US rom and an AU version as well.
You need previous nfc firmware to make it work again. So follow this steps :
1. Flash 5.1.1 rom trough flashtool with any customization and be shure to tick all wipes in flashtool
2. After first boot you will see nfc update dialog but this time success (so you repaired the NFC)
3. Root the phone and install recovery (i am sure you know how)
4. Flash this prerooted firmware withouth wiping anything.
5. NFC update dialog will popup but should be success again.
6. Done!
Odoslané z D6603 pomocou Tapatalku
NetSkill said:
You need previous nfc firmware to make it work again. So follow this steps :
1. Flash 5.1.1 rom trough flashtool with any customization and be shure to tick all wipes in flashtool
2. After first boot you will see nfc update dialog but this time success (so you repaired the NFC)
3. Root the phone and install recovery (i am sure you know how)
4. Flash this prerooted firmware withouth wiping anything.
5. NFC update dialog will popup but should be success again.
6. Done!
Odoslané z D6603 pomocou Tapatalku
Click to expand...
Click to collapse
Thank you for your input!
I followed your steps but unfortunately at the first boot of 5.1.1 the NFC update failed (-1) once again, and flashing the pre-rooted firmware overtop did not fix it. I'm also having issues with NFC not being enabled on a 4.4.4 stock rom that I have tried. Could this be a sign of a bigger issue? I only just purchased this (new) phone the other day, but who knows what might have happened to it. I'm just not sure how else to diagnose it :-/
mishicki said:
Thank you for your input!
I followed your steps but unfortunately at the first boot of 5.1.1 the NFC update failed (-1) once again, and flashing the pre-rooted firmware overtop did not fix it. I'm also having issues with NFC not being enabled on a 4.4.4 stock rom that I have tried. Could this be a sign of a bigger issue? I only just purchased this (new) phone the other day, but who knows what might have happened to it. I'm just not sure how else to diagnose it :-/
Click to expand...
Click to collapse
I had my z3 that was from KK to LP to MM and never had issues with the NFC through the various boots. I'd try a stock KK firmware (no root, nothing) and see if it runs fine? and the go through the entire process of getting root then up to LP and then to MM?
Cow07 said:
I had my z3 that was from KK to LP to MM and never had issues with the NFC through the various boots. I'd try a stock KK firmware (no root, nothing) and see if it runs fine? and the go through the entire process of getting root then up to LP and then to MM?
Click to expand...
Click to collapse
I did just that cow07, and unfortunately I get a failure at all steps/stages/etc.
Upon performing a diagnostic NFC test from the Services menu, I get the error message "The NFC device cannot be used" (in all versions of the firmware, KK -> MM).
Sony support asked me to try and run their repair tool using the PC companion software, but that keeps failing as well. I think at this point I may just try to send it back for a replacement, as it is still under my seller's warranty.
Thank you for the help, I'll be coming back here soon enough! This wound up being a hardware issue; after contacting my seller and getting a refund, I purchased another and had no issues using the aforementioned procedure. Thank you for your work!
Related
Hi all!
I am writing some instructions for newbies like me that wish to root their Xperia Tablet Z. I spent a lot of hours trying to understand how things work and I try to fill this gap with this post. If anybody knows, I would like to have an answer on the DRM, and model type questions that I have colored red in the text.
I was a "proud" owner of Sony Xperia Tablet Z WIFI 32GB (SGP312) that I bought from northern Europe last September. It was my first Android device and I consider myself super newbie on this "sport". Since my last official Sony system upgrade ~1-2 months ago I had sound problems with skype. I could not make a call without a handset and also my sony speakers refused to reproduce any youtube video. Nonetheless, the alarm was working fine! I was disappointed and after a factory reset the sound problems persisted. Thus, I decided to delve into the rooting world.
So long story short, we can install whichever stock/original firmware we want if it is designed for our devices consulting the precious links in xda-developers.com forums. Then we can either stay with this or install custom "ROMs" having our tablet "rooted".
My first goal is to fix the sound problem so I tried following the stock firmware route.
I flashed the firmware(s) with the quite intuitive Flashtool. Beware that I had already installed the required Google's Android SDK/ADT kit in my windows machine, although I performed every task in my linux machine in order to have working fastboot and adb commands with the minimal fuss installation-wise. To flash the stock firmwares, or the so called FTF files, I was entering the flash mode holding/pressing down the Volume Down key while connecting the device with the USB to my PC. I note that holding down the Volume Up key, instead, connects the tablet in the fast boot mode
After/Before every firmware flashing I was trying not to forget to:
Enable the USB Debugging mode
Trust installation from unknown sources (this probably is redundant) and
Use massive storage instead of MTP in my USB connection options.
Then, I tried to unlock my bootloader (for experimenting purposes) following the official SONY instructions. I successfully did (fastboot was saying OK!), without keeping any DRM keys, since I guess I do not need them, right? However with some FTF stock firmwares my screen was freezing while booting and showing the "flying colors" and then it was eternally rebooting again and freezing again and so on. I tried this and verified it with a couple of FTF stock firmwares. The one was for sure the SGP312 Global Xperia Tablet Z WiFi 32 GB - 10.4.1.B.0.109, I do not remember the others. This 10.4.1.B.0.109 was working fine but not with the bootloader unlocked. I found out that I could break the boot/freeze loop by entering flash mode (Volume Down while connecting the USB) just after it was turned off after the "flying color" freeze.
So I tried with this stock firmware: SGP312 10.4.B.0.577 (UK version 32GB WIFI Unbranded) and after using my tablet for ~30mins I can say that I did not encounter any problems.
But I wanted to view the rooting world, so to do this I found out that installing a Recovery Software would help.
So I installed XZDualRecovery. I followed the instructions and downloaded TabZ-lockeddualrecovery2.7.123-BETA.installer.zip and also the *flashable.zip from the same site.
Before starting to implement the instructions, the same XZDualRecovery post was mentioning I should install a 10.3.1.C.0.136 firmware and so I did, getting the SGP312 10.3.1.C.0.136 VMo EU4 firmware. This 10.3.1.C.0.136 was also working quite well, and after unlocking the bootloader (I do not know if I have to do unlock the bootloader everytime I flash a stock FTF) it was botting properly and my speakers were working fine.
I runned the install.sh for linux (install.bat for windows). I noticed that the third option was "3/ Attempt installation on unrooted device" which I tried and was successful, since then, the "Root Checker" app was saying that my tablet was rooted. That was really cool!
I wanted to enter the recovery mode so I turned on my tablet and when the "SONY" letters appeared (or a bit earlier) I started pressing multiple times the Volume Up key and a nice purple screen (like this) with the recovery appeared. There, I chose Wipe Data/Factory Reset (it was quite fast) and then Install multiple Zip files from the SD card.
The Zips I had in my card were the Cyanogen Mod, the Google Apps and the XZDualRecovery:
I downloaded Cyanogen Mod, pollux_windy for our devices, from here. I chose the latest stable version, cm-10.2.1-pollux_windy.zip 2014-02-01 01:07:05, but I hope another one will see the light soon.
I also installed the latest google apps that for today are these and the latest versions can be found here.
The TabZ-lockeddualrecovery2.7.123-BETA.flashable.zip metnioned above. I am not sure if this is really needed but I think I read somewhere that I should included or else I would not be able to Reboot to Recovery after flashing.
The problem with the pollux_windy zip was that I panicked since the recovery zip installation stopped with the error: assert failed [...] status 7 and I was pretty sure I had an SGP312 device!!! So I deleted the first line in the cyanogen zip file:
Code:
/META-INF/com/google/android/updater-script
like it appears here or here. This forum post says I should not extract the zip, but I did and it worked.
After all the above steps I booted my tablet and everything seems almost ok so far. I say almost because:
I notice that my device, according to the settings is now the "SGP311" and not the SGP312 (how could I change that?), but in my free space I still see 25+GB (although I am still using only ~3GB).
Also, some times while I am scrolling e.g. in Play Store I see infinitesimal freezes in the movement of the webpage (AnTuTu benchmark returns a rating of ~19800-20118).
Moreover, I have installed ~30 apps, but the installing procedure seems somehow slow, and the last ~10 apps I tried to install have not been installed "due to an error 495". The above was "fixed" after a reboot, but I must say I never encountered this problem with my stock firmware.
To the first question in red: DRM keys are needed for Playstation Mobile, Video and Music Unlimited, I think something regarding Screen Mirroring and, until Android 4.3, no Bravia Engine 2. With 4.4, it works again.
About the 311 and 312 thing, it is because you flashed a firmware that wasn't specifically for your device. You can go into build.prop file, and change every SGP311 you find to SGP312.
Nevertheless, awesome guide
Sent from my LT26i using Tapatalk
Thanks for the time to share
Hi all,
I have the SGP312 but it's not the "global" version (I noticed one of the stock firmware used was the UK one). I have the US/Canadian/North American version.
Would I brick my device if I flashed with the UK firmware? I haven't for the life of me found any guides/threads for my device.
I know it's the "pollux windy" (wifi 32gb) but I'm...afraid.
Thanks!
UberBaumer said:
Would I brick my device if I flashed with the UK firmware? I haven't for the life of me found any guides/threads for my device.
Click to expand...
Click to collapse
no.
Hi everyone. I just flashed back to stock (Koodo official firmware) to sell my Note 3 and now my back hardware button isn't working. I have searched the web and to no avail. Could someone please give me an idea of what I can do to fix this? Thank you!!
Which note 3 is it?
SM n900W8
I have the same model. I haven't used it for a while. I powered it on a few days ago to take the update from doc4 to doh1. I just tried the back and menu buttons using the doh1 ROM and they seem to work fine.
A friend of mine has the same phone and he flashed the doh1 ROM from sammobile.com over a rooted doc4 RIM and he also has no problems.
Both of us were using custom ROMs with a 4.4.2 bootloader and we both flashed back to stock using sammobile.com's doc4 ROM before moving to doh1.
I ended up flashing a stock n9005 zip TW rom and it is fixed - but I had to install TWRP again etc. Thanks for the help though!
Glad you got it fixed but I'm not sure I was much help.
Partially solved..
Hi.
I have done everything trying to solve this and can confirm the next:
1st: If you go back to Kit Kat, the capacitive buttons start to work again. Then you are offered a couple of OTAs (one after the other to get you to DOH1). After the first OTA, the buttons stop working again.
So first solution: stay on Kit Kat (probably not what we want).
2nd: Flashing a custom Cyanogenmod based firmware works, I used latest temasek's build, I am testing it to see if I can keep it.
3rd: I tried erasing almost every single partition (system/cache/dalvik(art?) cache) and flashing from scratch DOH1... wont work.
According to what I have read all around there is a system file that controls the capacitive buttons, probably that file is getting weird with the upgrade, I still need to install a official rom, root it and try to edit such file.
It's strange that some phones have no problem while others do. My friend and I have no problems but we weren't running custom ROMs before the doc4 or doh1 updates.
audit13 said:
It's strange that some phones have no problem while others do. My friend and I have no problems but we weren't running custom ROMs before the doc4 or doh1 updates.
Click to expand...
Click to collapse
I wasn't running anything custom. I was on Official ROM (no root no anything, just Stock Samsung Software) as always with my Note 3. It was just that the DOH1 update make the damages.
Now I think I gotta stick to Cyanogenmod given this problem, unless Samsung says something and fix the thing.
Does this happen with TW-based custom ROMs too?
Dont know. As of now, I am trying to flash DOH1 again on top of KitKat 4.4.2
[/COLOR]http://www.askmefast.com/I_have_a_n...art_any_idea_what_can_be_done-qna1982335.html
They say clearing the Cache of the Samsung Keyboard fixes the thing. Wont be able to test by myself til tomorrow
Edited
I have N900W8 bell version, using it on Virgin network.
worked flawlessly with KitKat (either with Bell or Virgin version).
I've only experimented with Note-based custom roms (KitKat only), since I need the pen functionality.
First attempt:
I have experienced the same, not properly working menu button and not working back button.
I was on rooted stock KitKat 4.4.2 (N900W8VLUCNB7 Firmware Virgin mobile version), rooted with Chainfire CF-auto root (Build ID:KOT49H.N900W8VLUCNB7) using Odin. (all the buttons working properly)
Upgraded to Lollipop 5.0 (N900W8VLU2DOH1) with Odin, rooted same way with CF-auto root (Build ID:LRX21V.N900W8UBU2DOL1). (Buttons do not work)
Second Attempt (No rooting involved what-so-ever):
Reverted back to stock KitKat 4.4.2 (N900W8VLUCNB7 Firmware Virgin mobile version, clean flash), all the buttons working properly.
Did OTA update through Wifi to, assuming, N900W8VLU2DOC4. (Buttons do not work)
Another OTA update through Wifi to N900W8VLU2DOH1(confirmed). (Buttons do not work)
For both of above attempts, buttons are working properly with KitKat, whether it was rooted or not, and not with Lollipop, whether it was rooted or not. I'm thinking it's just the lollipop issue.
Third attempt (using N900W8VLUCNB7 Firmware Bell version):
Reverted back to stock KitKat 4.4.2 (N900W8VLUCNB7 Firmware Bell version, clean flash), all the buttons working properly.
Did OTA update through Wifi to N900W8VLU2DOC4. (Buttons do not work)
Another OTA update through Wifi to N900W8VLU2DOH1(confirmed). (Buttons do not work)
wy2sl0 said:
I ended up flashing a stock n9005 zip TW rom and it is fixed - but I had to install TWRP again etc. Thanks for the help though!
Click to expand...
Click to collapse
Do you have the link for the stock Tom zip?
Sent from my SM-N900W8 using XDA Free mobile app
Ok. Pretty much tried everything while staying on stock firmware.
However, everything else seems to work okay other than the touch button.
So now im gonna root the stock lollipop and use xposed and gravitybox to manually remap the 2 touch keys. Will update
Hell yeah(excuse my language, but I'm so happy), I got this working!
Before I start listing my steps, please thank wrench588 here for me to find a confirmed working solution, and
thank stew721 here for the original post!!
No root on a stock lollipop (N900W8VLU2DOH1) Virgin firmware on Bell phone
1. Clean flash with N900W8VLU2DOH1 Virgin firmware on odin. (I'm guessing you actually wouldn't even need to do this step, if you are already on lollipop (N900W8VLU2DOH1 or N900W8OYADOC4 firmware)4N900W8
- I got my stock firmware from here
2. Download idlekernel here
- For Odin flash: download idleKernel-hlte-can-6.6.5.tar.md5 (for Canadian galaxy note 3 SM-N900W8)
- For recovery flash (ie. twrp): download idleKernel-hlte-can-6.6.5.zip (for Canadian galaxy note 3 SM-N900W8)
3A. For Odin,
a. open Odin
b. load into download mode (by holding Power+Volume Down+Home key together when turning on the device)
c. Load the idleKernel-hlte-can-6.6.5.tar.md5 into the "AP" on Odin
d. "Start" on Odin
3B. For Recovery(TWRP or CWM),
a. Boot normally and copy idleKernel-hlte-can-6.6.5.zip into your phone
b. flash idleKernel-hlte-can-6.6.5.zip file in recovery
Done.
Thank you so much again, wrench588 and stew721. I could not be happier
Next step for me would be getting my stock rom to get deodexed so I can install "xposed". I need to replace the function of holding "menu" touch button to pop up google search instead of S finder.
rocked_out said:
Hell yeah(excuse my language, but I'm so happy), I got this working!
Before I start listing my steps, please thank wrench588 here for me to find a confirmed working solution, and
thank stew721 here for the original post!!
No root on a stock lollipop (N900W8VLU2DOH1) Virgin firmware on Bell phone
1. Clean flash with N900W8VLU2DOH1 Virgin firmware on odin. (I'm guessing you actually wouldn't even need to do this step, if you are already on lollipop (N900W8VLU2DOH1 or N900W8OYADOC4 firmware)4N900W8
- I got my stock firmware from here
2. Download idlekernel here
- For Odin flash: download idleKernel-hlte-can-6.6.5.tar.md5 (for Canadian galaxy note 3 SM-N900W8)
- For recovery flash (ie. twrp): download idleKernel-hlte-can-6.6.5.zip (for Canadian galaxy note 3 SM-N900W8)
3A. For Odin,
a. open Odin
b. load into download mode (by holding Power+Volume Down+Home key together when turning on the device)
c. Load the idleKernel-hlte-can-6.6.5.tar.md5 into the "AP" on Odin
d. "Start" on Odin
3B. For Recovery(TWRP or CWM),
a. Boot normally and copy idleKernel-hlte-can-6.6.5.zip into your phone
b. flash idleKernel-hlte-can-6.6.5.zip file in recovery
Done.
Thank you so much again, wrench588 and stew721. I could not be happier
Next step for me would be getting my stock rom to get deodexed so I can install "xposed". I need to replace the function of holding "menu" touch button to pop up google search instead of S finder.
Click to expand...
Click to collapse
THanks for this!!! note that some will get a "unfortunately knox has stopped working" upon bootup and nothing can be done about it to my knowledge.
SS604 said:
THanks for this!!! note that some will get a "unfortunately knox has stopped working" upon bootup and nothing can be done about it to my knowledge.
Click to expand...
Click to collapse
Hey , has anyone firgured out how to get rid of the "unfortunately Knox has stopped working" ? I had the same issue with the softkeys not working. This fix works but I get this message. I was also told to try flashing a PIT file with stock firmware to fix the softkey issue, but this did not work.
Maybe flashing supersu from TWRP will allow supersu to disable knox?
not to bring back a dead thread, but this is exactly what I needed. I needed to root to fix screen mirroring so I just used root uninstaller to delete knox.
This thread is to discuss KangVIP roms on our phones.
To Install just flash the zip over Marshmallow B522 or if you want a cleaner/leaner approach, feel free to follow my steps below:
https://userscloud.com/go/ys5uy5oacq05/ (mirror folder containing kangVip Roms and patches for MT7 only)
http://pan.baidu.com/wap/share/home?uk=1528889538&third=0&adapt=pc&fr=ftw (main - I guess - repository of ALL KangVip rom and patches)
https://cloud.mail.ru/public/JCbD/VgpT7f8dS/ (personal cloud mirror by XDA user Trankvilli)
http://www.opengapps.org OpenGapps download (I use ARM - 6.0 - Pico)
https://mega.nz/#!N4FTkIrA!-lMDZYqF2va1LSl5tU-npb_gQmDiSZQTQvP9RWOHyrs my chinese app removal script (removes all apps that are in chinese or that cannot be used outside of china)
https://mega.nz/#!RsUEFZZK!fKImZW0oFviNon4--RvZS4wsyKlB2XvawEUFO6vG7cY my stock app removal script (For that clean feelin' this backs up the apps to their respective folder inside bkp (eg a folder inside /system/app will be moved to /system/bkp/app) to restore, just move to the original location with a root explorer)
----Steps---
Flash (from custom recovery over B522)
1) Factory reset
2) Flash latest KangVIP zip
3) Flash debloat script
4) flash latest supersu zip
5) Flash Gapps
first boot will take a good 15-20min
Configure
1) Settings - K-Settings - Lockscreen and desktop - untick both lunar calendar options
2) Settings - K-Settings - Notification - untick lunar
3) Settings - K-Settings - Xposed - Install Xposed (For Xposed to work 100% you need to disable the theme engine, it's up to you)
untick "disable resource hooks" in xposed installer and, add or modify the following lines in the build.prop (they need to be 0) reboot
ro.config.hwtheme=0
ro.config.hw_theme=0
ro.config.themecolor=0
4)edit /data/cust/prop/local.prop and /system/build.prop. if the lines are there, modify, if they're not, create them. (needs root, this is to fix the Yellow pages + some other unidentified locale issues you might have)
Original:
ro.product.locale.language=zh
ro.product.locale.region=CN
change to:
ro.product.locale.language=en
ro.product.locale.region=US
PS: Thanks leonardus_magnus, Cloudcompute for helping out.
What want you discuss? We need a Thread same that.....
http://forum.xda-developers.com/mate-7/orig-development/rom-kangvip-rom-mate7-emui3-1-b351-t3228597
Skorpi58 said:
What want you discuss? We need a Thread same that.....
http://forum.xda-developers.com/mate-7/orig-development/rom-kangvip-rom-mate7-emui3-1-b351-t3228597
Click to expand...
Click to collapse
I'm confused.
weren't you the one who asked to open a new thread to discuss KangVIP.
regardless, Fooox1 has closed all his other KangVIP threads (unsure why) there is no reason to think he won't close this one either.
Yes, there I was, however, but not only to discuss....forget Fooox1
It must be same like that.....the first Page.....
http://forum.xda-developers.com/mate...-b351-t3228597
I tried Kangvip B553a on my L09 for couple of days. I loved the extra features and customization options that K setting provided, however I couldn't get fingerprint scanner to work. Additionally it lacked Swype for Huawei. The inbuilt keyboard and the lockscreen had some Chinese in it that I couldn't remove. I restored back to B511 for now, however I intend to downgrade to Chinese LP B354 over the weekend and work my way back to B553a and see if that fixes the fingerprint scanner.
CloudCompute said:
The inbuilt keyboard and the lockscreen had some Chinese in it that I couldn't remove.
Click to expand...
Click to collapse
I think you mean the Lunar calender. You can remove the Chinese characters by going to Settings -> K-settings -> Lockscreen & Desktop settings -> Lunar calender. I'm on B553-A, universally without any visible chinese language.
Hiemes said:
I think you mean the Lunar calender. You can remove the Chinese characters by going to Settings -> K-settings -> Lockscreen & Desktop settings -> Lunar calender. I'm on B553-A, universally without any visible chinese language.
Click to expand...
Click to collapse
I had removed the lunar calender, and also some Chinese captions on some pictures. That did take off most of the Chinese from the lockscreen, however I have a feeling some traces were still left out only for some pictures, not all. How about the keyboard? Were you able to remove Chinese letters from the Enter button, and another button on the bottom right corner? Is your fingerprint scanner working? What MT7 do you have, TL10 or L09?
What path did you take to get to KingVIP B553?
I tried downgrading from B511 to Chinese B354 yesterday using B500, the downgrade package from MM to LP, however the downgrade failed at 5%. I tried again after changing the vendor and country information to cnchannel and cn, however the downgrade continued to fail at 5%. I then downgraded to B326 instead. I want to get to B510 first, but I am not sure if an upgrade to B510 is going to be successful from B326.
A few links for new users...
https://userscloud.com/go/ys5uy5oacq05/ (mirror folder containing kangVip Roms and patches for MT7 only)
http://pan.baidu.com/wap/share/home?uk=1528889538&third=0&adapt=pc&fr=ftw (main - I guess - repository of ALL KangVip rom and patches)
https://cloud.mail.ru/public/JCbD/VgpT7f8dS/ (personal cloud mirror by XDA user Trankvilli - Thanks !!!)
This thread should be moved to correct section > Ascend Mate 7 Original Android Development
Ciao
leonardus_magnus said:
A few links for new users...
https://userscloud.com/go/ys5uy5oacq05/ (mirror folder containing kangVip Roms and patches for MT7 only)
http://pan.baidu.com/wap/share/home?uk=1528889538&third=0&adapt=pc&fr=ftw (main - I guess - repository of ALL KangVip rom and patches)
https://cloud.mail.ru/public/JCbD/VgpT7f8dS/ (personal cloud mirror by XDA user Trankvilli - Thanks !!!)
This thread should be moved to correct section > Ascend Mate 7 Original Android Development
Ciao
Click to expand...
Click to collapse
This wouldn't be original as it's based on stock. Android development thread is more suitable if the developer was here. But I'm not the developer. Thus general
I've made multiple failed attempts to install Chinese LP B354 on my L09.
I was on B511 to begin with. I used the MM to LP downgrade package to get to B500 and then tried to install LP B554, it failed at 5%. I replaced the "custom bin" file in the system(root) folder with one for CN. My vendor and country info changed to cnchannel and cn, however B354 continued to fail at 5%. I then installed B326 instead, and upgraded back to B511 again.
Then I flashed TWRP recovery and restored to B553 using a nandroid backup. Rooted and replaced "custom bin" file again to change my vendor and country info to cnchannel and cn. Flashed stock recovery, and tried to install a MM to LP downgrade package from Trankvilli's folder, but that one failed at 5%. Then I used the same downgrade package i'd used before to get to B500 again, and then tried to install B354, but that failed again at 5%.
Trankvilli in the earlier thread had indicated that his fingerprint scanner was working when he upgraded his L09 from B354 to Kangvip B553a passing through various other Chinese MM roms. B354 > B510 > B520 > B553 > Kangvip B553a.
Can anyone help me get to B354 first? I have a L09 from the Middle east region.
CloudCompute said:
I've made multiple failed attempts to install Chinese LP B354 on my L09.
I was on B511 to begin with. I used the MM to LP downgrade package to get to B500 and then tried to install LP B554, it failed at 5%. I replaced the "custom bin" file in the system(root) folder with one for CN. My vendor and country info changed to cnchannel and cn, however B354 continued to fail at 5%. I then installed B326 instead, and upgraded back to B511 again.
Then I flashed TWRP recovery and restored to B553 using a nandroid backup. Rooted and replaced "custom bin" file again to change my vendor and country info to cnchannel and cn. Flashed stock recovery, and tried to install a MM to LP downgrade package from Trankvilli's folder, but that one failed at 5%. Then I used the same downgrade package i'd used before to get to B500 again, and then tried to install B354, but that failed again at 5%.
Trankvilli in the earlier thread had indicated that his fingerprint scanner was working when he upgraded his L09 from B354 to Kangvip B553a passing through various other Chinese MM roms. B354 > B510 > B520 > B553 > Kangvip B553a.
Can anyone help me get to B354 first? I have a L09 from the Middle east region.
Click to expand...
Click to collapse
Hi Cloud, I also remember that post.
I experimented with changing the region too, in fact I made a tool, but I couldn't quite get a different region firmware to work, and ran out of time (needed my phone for work!)
I think the most important thing for changing the region is the oeminfo, the custom.bin can be empty, as long as it's there (maybe that's why I failed, because i didn't have any)
you can have a look at the script on how this is done.
xd4d3v said:
Hi Cloud, I also remember that post.
I experimented with changing the region too, in fact I made a tool, but I couldn't quite get a different region firmware to work, and ran out of time (needed my phone for work!)
I think the most important thing for changing the region is the oeminfo, the custom.bin can be empty, as long as it's there (maybe that's why I failed, because i didn't have any)
you can have a look at the script on how this is done.
Click to expand...
Click to collapse
Thank you xd4d3v, I'll check out the script tonight. This thread seems to be drawing very less attention though
CloudCompute said:
I've made multiple failed attempts to install Chinese LP B354 on my L09.
I was on B511 to begin with. I used the MM to LP downgrade package to get to B500 and then tried to install LP B554, it failed at 5%. I replaced the "custom bin" file in the system(root) folder with one for CN. My vendor and country info changed to cnchannel and cn, however B354 continued to fail at 5%. I then installed B326 instead, and upgraded back to B511 again.
Then I flashed TWRP recovery and restored to B553 using a nandroid backup. Rooted and replaced "custom bin" file again to change my vendor and country info to cnchannel and cn. Flashed stock recovery, and tried to install a MM to LP downgrade package from Trankvilli's folder, but that one failed at 5%. Then I used the same downgrade package i'd used before to get to B500 again, and then tried to install B354, but that failed again at 5%.
Trankvilli in the earlier thread had indicated that his fingerprint scanner was working when he upgraded his L09 from B354 to Kangvip B553a passing through various other Chinese MM roms. B354 > B510 > B520 > B553 > Kangvip B553a.
Can anyone help me get to B354 first? I have a L09 from the Middle east region.
Click to expand...
Click to collapse
Hi Cloud.
have a look at this thread, I've asked the poster to clarify the process.
http://forum.xda-developers.com/mat...il-software-update-fail-t3277242#post66284797
PS: I just checked in using the service code.. mine is switched to the cn region.. so what i did worked.
the problem we have could be that we're trying to flash tl10 stock roms on a tl09.. it's probably triggering something that refuses to budge.
I don't think that it will allow you to install a firmware from one phone on another, regardless of the region? (flashed on stock)
Again a brief explanation. I have the posts closed because I lack time or device. So I can not give assistance. I increasingly got the impression that the Rome is probably faulty, I saw this as a logical step.
And no, I'm not KangVIP. My Downloads I ordered directly from this page.
http://cn.club.vmall.com/forum.php?mod=forumdisplay&fid=468&page=1&filter=typeid&typeid=1368
What is hidden in the linked cloud I can not judge.
I am still convinced of the quality of Rome and it would use any time.
Looks like I am the only one experiencing this.
I recently updated to B513 and then to B553A KROM: in both cases notification icons in the status bar are static… only a fixed icon of the app pushing a notification …
Let me explain: the Meteo Wunderground app puts on the status bar an icon of the actual weather conditions (sun, clouds, rain…). Again… when downloading something with web browser or when updating an app in play store I used to see a little animated arrow… Now in all these cases I simply see in the notification bar the app icon.
This happens in both B513 and B553A, therefore in MM
Please have a look at the attached screenshot...
Is this happening to other users? Any ideas or suggestions to have animated notification icons back?
Thanks for your help...
Ciao
leonardus_magnus said:
Looks like I am the only one experiencing this.
I recently updated to B513 and then to B553A KROM: in both cases notification icons in the status bar are static… only a fixed icon of the app pushing a notification …
Let me explain: the Meteo Wunderground app puts on the status bar an icon of the actual weather conditions (sun, clouds, rain…). Again… when downloading something with web browser or when updating an app in play store I used to see a little animated arrow… Now in all these cases I simply see in the notification bar the app icon.
This happens in both B513 and B553A, therefore in MM
Please have a look at the attached screenshot...
Is this happening to other users? Any ideas or suggestions to have animated notification icons back?
Thanks for your help...
Ciao
Click to expand...
Click to collapse
Most of us have up with the fingerprint not working and uninstalled until it's solved. Do you have any problems with the fingerprint? Is yours a tl09 or tl10?
I've had similar problems before when flashing cm over previous installs. It sounds like the kind of problem that will go away with a factory reset (unfortunately) maybe you can take anandroid and see if resetting fixes the problem?
xd4d3v said:
Most of us have up with the fingerprint not working and uninstalled until it's solved. Do you have any problems with the fingerprint? Is yours a tl09 or tl10?
I've had similar problems before when flashing cm over previous installs. It sounds like the kind of problem that will go away with a factory reset (unfortunately) maybe you can take anandroid and see if resetting fixes the problem?
Click to expand...
Click to collapse
THanks for your suggestion... I'll try a factory reset... but not today, it'takes a lot to setup everything back and with MM it takes even more!!!
I am on TL09 and I cannot register fingerprint too... I noticed (with google translate so I guess I noticed ) on the chinese forum linked by Fooox1 that they are experiencing issues with fingerprint too... We can hope that a fix will come soon...
Ciao
leonardus_magnus said:
THanks for your suggestion... I'll try a factory reset... but not today, it'takes a lot to setup everything back and with MM it takes even more!!!
I am on TL09 and I cannot register fingerprint too... I noticed (with google translate so I guess I noticed ) on the chinese forum linked by Fooox1 that they are experiencing issues with fingerprint too... We can hope that a fix will come soon...
Ciao
Click to expand...
Click to collapse
thats great news for us actually.
means that more than likely there will be a fix in a newer version of KangVIP
ah.. before you do a factory reset, try to clear the cache.. it might do the trick.
anyone else try installing KangVIP553 and the sim card stopped working
I'm on tmobile ive tried clean reinstall a few times but nothings working
it was working fine with 551
hauntix said:
anyone else try installing KangVIP553 and the sim card stopped working
I'm on tmobile ive tried clean reinstall a few times but nothings working
it was working fine with 551
Click to expand...
Click to collapse
yeah, same thing happened to me.
I just got the US version of the Xperia XZ and I was attempting to get the fingerprint sensor to work by flashing with Flashtool and Xperiafirm. I managed to get it to work, but the process is slightly different from what we have here it other threads.
With the update to 7.0, all the customized versions of the firmware in Xperifirm have been updated to 7.0, which flashtool does not support atm. To get around this and enable the fingerprint sensor I used these steps: (at least until Flashtool is updated)
Process Steps:
backup your phone! You will lose everything on it with the flash
Find and download MM .ftf file for your phone. I used Centralized Europe, but you can use Italian or UK. These can be found using google, or PM and I'll send you a link
Make sure you install the flashtool drivers properly. This means Disable driver signature enforcement. Then do the install so they can install correctly.
Once installed power your phone off and while you hold down the down volume key, plug it into the computer.
Open Flashtool and click the lightning bolt and start the flash.
Once flash is complete, reboot phone and verify that the Fingerprint Sensor is actually working
Using built in software updater (OTA) update to 7.0
If you do this correctly everything should work smoothly.
Be Sure to use the latest version of Flashtool!
Flashtool began to support Nougat as of yesterday: http://forum.xda-developers.com/xperia-xz/how-to/flashtool-supports-nougat-t3523322
can someone upload stock usa rom that was shipped (marshmallow)
Announcement said:
can someone upload stock usa rom that was shipped (marshmallow)
Click to expand...
Click to collapse
Flashtool should work with the latest nougat .FTF. I believe the one it was shipped with is the customized US firmware on xperifirm. Just use that if you want to go back to stock.
Edit: I worked out my issues, I'll leave this here in case others have similar trouble:
I needed to manually add in the RAW F53XX files from the github (https://github.com/Androxyde/devices/tree/master/F53XX), this allowed Flashtool to correctly detect the type of phone and apply the fsc. I was then able to flash my desired firmware, I chose the 6.0.1 release for Journalists to begin with as a test. This confirmed my suspicion that it was a software update issue causing the proximity sensor to malfunction (stuck on) and also fixed up the FACTORY STARTUP SERVICE-POWER OFF bug and the Warrantytimeservice permanent notification. I can now look at updating to later versions of Android and find the latest version before I have issues again.
---
tl;dr - I need a guide that actually works on downgrading the F5321 to a specific stock Android version with a locked bootloader.
I recently received a new, old stock version of the X Compact (F5321) that appears to be a HK variant as it started up with the Chinese language selected.
It was initially stock Android 6.0.1 with no apparent problems. After OTA updating all the way through to 7.1.x and onward to the latest 8.0, I now receive the "FACTORY STARTUP SERVICE" problem. Even if I'm quick enough to disable the service for the service flag, the proximity sensor does not work as well after updating, making phone calls impossible. I believe the issue is all related to software, not hardware. I want to downgrade to 6.x and go from there before I have to send it back for another replacement.
I'm having trouble with getting Flashtool to correctly detect and identify the firmware files that I want to flash. I want a completely stock version of Android, so keeping the bootloader locked is fine for me.
After downloading the firmware that I want to try, XperiFirm will close and Flashtool will successfully build the FTF. After clicking the lightning bolt > flashmode > the firmware list is blank.
I'm using Flashtool 0.9.26 (I have tried older versions as well with the same problems) with driver signature enforcement disabled and correct drivers installed to detect the phone.
The last time I used Flashtool was to flash my older Z5 Compact, I didn't have any issues then and it was all done within 10 minutes. I've already spent more than 5 hours on this phone and would appreciate any help.
I seem to have the exact same problem with a Hong Kong-sourced X Compact. I am familiar with Flashtool, and have used it for basic flashing of firmware. This time, however, I am experiencing the dreaded "FACTORY STARTUP SERVICE" problem. Was wondering if Flashtool could be used to circumvent the problem. I simply want the USA Android 8.0 firmware on the phone. I am not familiar with the various options that Flashtool offers. I note that you mention a specific script(?) that can be installed. Do you have any advice? Thanks
pseudonym58 said:
I seem to have the exact same problem with a Hong Kong-sourced X Compact. I am familiar with Flashtool, and have used it for basic flashing of firmware. This time, however, I am experiencing the dreaded "FACTORY STARTUP SERVICE" problem. Was wondering if Flashtool could be used to circumvent the problem. I simply want the USA Android 8.0 firmware on the phone. I am not familiar with the various options that Flashtool offers. I note that you mention a specific script(?) that can be installed. Do you have any advice? Thanks
Click to expand...
Click to collapse
The "FACTORY STARTUP SERVICE" and to a lesser extent, "Warrantytimeservice" problems surface only in the later version of Android. The only way I could remove them was by staying on 6.0.x only. Anything higher, and the problems show up again. It seems to be a byproduct of upgrading the HK variant that wasn't designed to actually be software upgraded - you won't be able to have the US 8.x firmware on the phone.
Sorry to say, but you'll be stuck on 6.0.x if you want a usable phone. I should mention that I was never able to maintain a newer firmware on that particular phone.
I've since sent the Compact X back (it was meant to be a gift) and replaced it with a Samsung A20.
h
I'm using SO-O2J and a sim card not docomo. Use the "Repair" in Xperia Companion and it auto flash Android 7.0
..
PioneerSeeker said:
Try different region's roms on www.xperiablog.net and I hope you'll be successful to find nougat or oreo at last for your phone.
Remember xperia devices do not need to unlock bootloader for downgrade...
Click to expand...
Click to collapse
Thanks; I was able to obtain an X Compact originally for the UK market, and was able to successfully flash the US Oreo firmware. All seems to be in order.