http://www.ztemobile.de/forums/topic/zte-sucht-axon-7-android-nougat-beta-tester/
A couple of days ago i had contact with ZTE Germany for this N update. (my previous post)
They stated clearly that this update was scheduled for end of january.
Now, today as i read, they are looking for 20 testers...isn't this not a little bit too late when a release would be scheduled by the end of this month ?
In general how quick can a beta Nougat be tested to release a full working N?
Didnt they sey end of february mid march? not really sure but i think i read something like that on a screenshot from zte germany
MrPepperino said:
Didnt they sey end of february mid march? not really sure but i think i read something like that on a screenshot from zte germany
Click to expand...
Click to collapse
That was for the mini version
Maybe someone would ask in the thread. Really sad if they change the release
Well, the A2017U and A2017G are pretty similiar, so I guess they already have most of the features in.
A sprint is about 2 weeks and you can go from a public beta to release in one or two sprints.
Sent from my ZTE A2017G using Tapatalk
razorsbk said:
A sprint is about 2 weeks and you can go from a public beta to release in one or two sprints.
Sent from my ZTE A2017G using Tapatalk
Click to expand...
Click to collapse
How do you know they are working with sprints? How do you know they have 2 week sprints? Still, big issues can come from the public beta test which will delay the release.
razorsbk said:
A sprint is about 2 weeks and you can go from a public beta to release in one or two sprints.
Sent from my ZTE A2017G using Tapatalk
Click to expand...
Click to collapse
Had some further discussion this morning with ZTE.
They keep holding the date of the end of January even with this test...let's wait and see.
ZTE remarked also that the update to Nougat would imply that it would be difficult and not be recommandable to downgrade to 6 again (if you would/want/needed to).
Can someone confirm this that downgrading to 6 would be very tricky and risky?
Hmm I think that with ADB method it shouldn't be tricky - but I might be wrong. May the update will change recovery / bootloader idk.
PS. I'm from Poland and I do not speak Germany but I will be willing to help as beta tester.
MrMD69 said:
Hmm I think that with ADB method it shouldn't be tricky
Click to expand...
Click to collapse
I would think ADB would make this easy as usual, but i have never downgraded (if i and other users are needed to for some reason) before.
Perhaps someone, who has allready performed a OS-downgrade before or does know exactly how this should be done, could give us some insight in this ( even to prevent some possible issues in the future)
raystef66 said:
I would think ADB would make this easy as usual, but i have never downgraded (if i and other users are needed to for some reason) before.
Perhaps someone, who has allready performed a OS-downgrade before or does know exactly how this should be done, could give us some insight in this ( even to prevent some possible issues in the future)
Click to expand...
Click to collapse
It's usually very easy (done it with a Nexus 5, Xperia Ray, Xperia Z1 Compact, Oneplus X). You just have to flash the previous OS's zip in recovery - or, in the Galaxy and Xperia's cases, with a PC tool (Odin, Flashtool). The Oneplus was the most complicated but even that was simple - I had to flash the older bootloader as well. Although ZTE may have something up their sleeve... I'm not sure.
Here's hoping Nougat will be so good we won't want to downgrade!
As long as ZTE doesn't do nasty things in the bootloader downgrading on unlocked devices will be trivial and very likely possible on locked ones too.
If they install more restrictive bootloader you can probably avoid that by keeping the old one but that means blindly flashing the OTA won't be an option.
Personally I feel like nougat would have to be exceptional for me to live with stock and to renounce xposed, otherwise I will stick with lineage for the time being.
NadavCE said:
It's usually very easy (done it with a Nexus 5, Xperia Ray, Xperia Z1 Compact, Oneplus X). You just have to flash the previous OS's zip in recovery - or, in the Galaxy and Xperia's cases, with a PC tool (Odin, Flashtool). The Oneplus was the most complicated but even that was simple - I had to flash the older bootloader as well. Although ZTE may have something up their sleeve... I'm not sure.
Here's hoping Nougat will be so good we won't want to downgrade!
Click to expand...
Click to collapse
Indeed let's hope the N update is that good we dont need to downgrade afterall
I saw some reflashing of a nexus from Lollipop to Kitkat and it was really simple. Just flash in ADB the 'flash-all' with an unlocked BL and you're good to go.(+wipe data/factory data reset in recovery)
If there is no flash-all file which files have to be flashed in fastboot and in what order ? Is there some guide to do this properly for all type of phones using ADB?
raystef66 said:
Indeed let's hope the N update is that good we dont need to downgrade afterall
I saw some reflashing of a nexus from Lollipop to Kitkat and it was really simple. Just flash in ADB the 'flash-all' with an unlocked BL and you're good to go.(+wipe data/factory data reset in recovery)
If there is no flash-all file which files have to be flashed in fastboot and in what order ? Is there some guide to do this properly for all type of phones using ADB?
Click to expand...
Click to collapse
IIRC the order is: bootloader, recovery, system. But there are a ton of guides online, and here on XDA, that you can use to verify :good:
raystef66 said:
I would think ADB would make this easy as usual, but i have never downgraded (if i and other users are needed to for some reason) before.
Perhaps someone, who has allready performed a OS-downgrade before or does know exactly how this should be done, could give us some insight in this ( even to prevent some possible issues in the future)
Click to expand...
Click to collapse
I downgraded Moto g xt1039 from 7.1.1 to original 4.0.2 (or 5.x I can not remember) via service menu recovery. That was super easy - sotck OTA image (flashable with all things eg. Bootloader, recovery etc), then fews pushing , wipe, reboot and done
You can find step by step guide in Moto g 4g development submenu on XDA
As mentioned above, sometimes changes are made in the bootloader which deny a downgrade. Same with the modem/baseband. I've seen older moto g's (xt1031) refuse to work with a downgraded baseband.
As enthusiasts, we'll have to take apart the update and flash only what needs to be flashed to obtain a working nougat.
There is a possibility of partitions changing when going to nougat. There was some added partitions that if you went to roll on one of the phones that I have owned that would brick your phone if it wasn't done correctly. I wish that I could remember the phone but the update added something like 10 more partitions that dealt with bootloader security and what not. This could possibly be an issue but I do not know much about ZTE phones.
IIRC, htc did this on the evo 4g lte during one of the 4.x upgrades.. I believe it was on 4.3. The emmc was completely restructured.
Related
I usually would not do this but because of the cleaver way of putting it from a ZTE mod i figured I would share it as is
https://community.zteusa.com/commun...ming-soon-to-a-device-near-you?comment-26024=
peramikic said:
I usually would not do this but because of the cleaver way of putting it from a ZTE mod i figured I would share it as is
https://community.zteusa.com/commun...ming-soon-to-a-device-near-you?comment-26024=
Click to expand...
Click to collapse
They're finally releasing factory images, yay!
xxBrun0xx said:
They're finally releasing factory images, yay!
Click to expand...
Click to collapse
They are going to give us something that they consider to be "stock"
Worst case scenario it's factory images
Best case scenario it's AOSP
nsane said:
They are going to give us something that they consider to be "stock"
Worst case scenario it's factory images
Best case scenario it's AOSP
Click to expand...
Click to collapse
It's almost guaranteed we will get a stock B27 recovery image. I do not see them dumping MiFavor, not even with N.
Question is what kind of recovery method will they use (DFU/EDL flasher or just full zip) and can we generated custom "MiFavor" from them
nsane said:
They are going to give us something that they consider to be "stock"
Worst case scenario it's factory images
Best case scenario it's AOSP
Click to expand...
Click to collapse
Best case scenario it's both
**** just when I gave up on the phone and send it back to Newegg ?
Sent from my Pixel using XDA-Developers mobile app
So please let's go
I am so ready. I have been holding off on unlocking, installing recovery and root until something worth while shook loose. Let's do this!
UnBrick tool will be good. I'm waiting for it. I hope that they release soon.
Would be great if it's something with bootloader unlock
Hopefully it's stock images so I can finally root my phone free of worry.
System images all but confirmed! Great news!
https://community.zteusa.com/community/blogging/blog/2016/10/21/weekly-roundup-october-21-2016
Factory images and new bootloader unlock process coming next week. Update #3 to come in the following weeks.
Fingers crossed update #3 is the nearly stock nougat build we saw running on a Chinese axon 7 last week!
xxBrun0xx said:
https://community.zteusa.com/community/blogging/blog/2016/10/21/weekly-roundup-october-21-2016
Factory images and new bootloader unlock process coming next week. Update #3 to come in the following weeks.
Fingers crossed update #3 is the nearly stock nougat build we saw running on a Chinese axon 7 last week!
Click to expand...
Click to collapse
as long as they don't make you sign away our warranty for the bootloader unlock and stock image use, else I'll have to do it the old way and keep my warranty under US law.
Nothing for EU still. Looks like EU won't get an official unlock...
Sadly this has nothing to do with the EU model whatsoever.
Very sad to see the EU model just 'ignored' and forgotten in terms of bootloader unlock and updates.
peramikic said:
It's almost guaranteed we will get a stock B27 recovery image. I do not see them dumping MiFavor, not even with N.
Question is what kind of recovery method will they use (DFU/EDL flasher or just full zip) and can we generated custom "MiFavor" from them
Click to expand...
Click to collapse
I'm guessing since they say that's in final testing and next update is almost ready to roll out, I'd more guess it will be with whatever that build is. But it will definitely just be a stock image, not AOSP.
---------- Post added at 02:31 PM ---------- Previous post was at 02:29 PM ----------
keessonnema said:
Sadly this has nothing to do with the EU model whatsoever.
Very sad to see the EU model just 'ignored' and forgotten in terms of bootloader unlock and updates.
Click to expand...
Click to collapse
The EU model has had just as many updates as the US one at this point. US got B18->B20->B27. EU has gotten B02->B03->B05.
Bootloader is slightly different, but the US model currently doesn't have support for that either, as they pulled it to rework it.
Where the US is definitely better is in communication from the respective ZTE branch.
TeutonJon78 said:
I'm guessing since they say that's in final testing and next update is almost ready to roll out, I'd more guess it will be with whatever that build is. But it will definitely just be a stock image, not AOSP.
---------- Post added at 02:31 PM ---------- Previous post was at 02:29 PM ----------
The EU model has had just as many updates as the US one at this point. US got B18->B20->B27. EU has gotten B02->B03->B05.
Bootloader is slightly different, but the US model currently doesn't have support for that either, as they pulled it to rework it.
Where the US is definitely better is in communication from the respective ZTE branch.
Click to expand...
Click to collapse
Uhm the EU Version is still on Android sec Patches from 1. Juli for example. And b05 is somewhat unofficial, No ota yet.
Gesendet von meinem ZTE A2017G mit Tapatalk
keessonnema said:
Sadly this has nothing to do with the EU model whatsoever.
Very sad to see the EU model just 'ignored' and forgotten in terms of bootloader unlock and updates.
Click to expand...
Click to collapse
Total unacceptable and ridicules that kind of discrimination of ZTE part.
Seems European are B class customers to them.
WTF ZTE!
Sent from my iPad using Tapatalk
Hi, got this phone for 1 month now used MM for 2 weeks then updated to Nougat but I didnt like it. Now I want to downgrade to MM is it possible with RSD Lite? If yes how? If no will factory reset solve battery drain, awfull notifications, over heating problems?
How did you upgrade? If you updated the bootloader to the N version, I'm not sure if you can revert back to MM.
OTAs are the Evil. :silly:
Updated via OTA. I could downgrade Samsung S4 isnt it possible with Moto Z? I did hard reset, downloaded my apps then closed my phone and charged it. I don't know what happened while phone was booting but it wasn't %100 battery charge btw. This battery life is killing me..
I'm sure you are not able to get back to Marshmallow because the OTA installs a new bootloader that is incompatible with the original Marshmallow
lollyjay said:
I'm sure you are not able to get back to Marshmallow because the OTA installs a new bootloader that is incompatible with the original Marshmallow
Click to expand...
Click to collapse
So I have to wait for fix eh
Which version did you apply?
If you updated to Nougat via OTA, there is currently no safe and simple way to downgrade back to Marshmallow as the OTA also updates the bootloader, meaning that Nougat is the oldest OS that is supported on that bootloader.
That's why I unlocked the bootloader on mine and used the technique outlined in the following thread. Not only do you get a perfectly working Nougat OS but also allows you to keep the old bootloader should you decide to downgrade to Marshmallow.
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
D13H4RD2L1V3 said:
If you updated to Nougat via OTA, there is currently no safe and simple way to downgrade back to Marshmallow as the OTA also updates the bootloader, meaning that Nougat is the oldest OS that is supported on that bootloader.
That's why I unlocked the bootloader on mine and used the technique outlined in the following thread. Not only do you get a perfectly working Nougat OS but also allows you to keep the old bootloader should you decide to downgrade to Marshmallow.
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
Click to expand...
Click to collapse
If I do this method to upgrade to nougat, will I still be able to use android pay?
wilder_mason said:
If I do this method to upgrade to nougat, will I still be able to use android pay?
Click to expand...
Click to collapse
Android Pay detects not only root but also unlocked bootloader.
So in other words, no android pay guys
D13H4RD2L1V3 said:
If you updated to Nougat via OTA, there is currently no safe and simple way to downgrade back to Marshmallow as the OTA also updates the bootloader, meaning that Nougat is the oldest OS that is supported on that bootloader.
That's why I unlocked the bootloader on mine and used the technique outlined in the following thread. Not only do you get a perfectly working Nougat OS but also allows you to keep the old bootloader should you decide to downgrade to Marshmallow.
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
Click to expand...
Click to collapse
It seemed too hard for me.. This is my first "almost" stock android experience I'm confused with fastboot commands etc.. I think i'll stay with stock android for a while..
tjk639 said:
Which version did you apply?
Click to expand...
Click to collapse
This is it. Hope you can find what you asked mate
Orangley said:
This is it. Hope you can find what you asked mate
Click to expand...
Click to collapse
Ah, I was hoping you had the first release of N. But it looks like you have the current one.
If someone reveals easy and safe way to downgrade please tag me I don't have much time to check forums
Nougat upgrade OTA leaves you in a tough position
My new Moto Z took an update from stock MM to Nougat 3 days after I got it. Stupid me, I should not have accepted the OTA update. But I did. And you cannot go back to MM because the update contains a new bootloader that makes it a one way trip.
Search my other posts in the last few days to see that you are not totally prevented from unlocking and rooting. But unlocking the bootloader leaves a trail forever because a solid state fuse gets tripped forever.
tjk639 said:
Ah, I was hoping you had the first release of N. But it looks like you have the current one.
Click to expand...
Click to collapse
What version is the first release of nougat that allows downgrading? :victory:
Did not downgrade
i23u8 said:
What version is the first release of nougat that allows downgrading? :victory:
Click to expand...
Click to collapse
I did not downgrade from 7.0.
I unlocked the bootloader and rooted the phone with twrp 3.xx and then used phh's Superuser.
But I must admit that I have not loaded a third party ROM yet. I want to load stock 7.1.1 when Motorola releases it in February or March.
Question would it be possible to use RDS light or the program at the beginning of this form to unlock set bootloader and then proceed to route
Hello All
I would really appreciate the help on my situation.
I have bought a new motherboard from aliexpress. and it turns out the board is a VS990 with H901 5.1 installed on it.
Its working like a charm now I received the OTA update to android 6 but I am very scared to go ahead with the update as it will most probably brick the phone. Has anyone experienced same situation? Do i go ahead and let it do the OTA update? If not is there anyway I can install Nugget on my (Half / Half) setup ?
I will very much appreciate the help please.
Thanks
ramyboy said:
Hello All
I would really appreciate the help on my situation.
I have bought a new motherboard from aliexpress. and it turns out the board is a VS990 with H901 5.1 installed on it.
Its working like a charm now I received the OTA update to android 6 but I am very scared to go ahead with the update as it will most probably brick the phone. Has anyone experienced same situation? Do i go ahead and let it do the OTA update? If not is there anyway I can install Nugget on my (Half / Half) setup ?
I will very much appreciate the help please
Thanks
Click to expand...
Click to collapse
hi
before you install the update, check weather is rooted or not, if rooted update will stop, otherwise it will update the phone, i'm having att phone i updated manually, update was messed up my phone, now phone its 6.0 but errors on my phone, if you are not sure what you doing, please don't updated.
jurneybegin said:
hi
before you install the update, check weather is rooted or not, if rooted update will stop, otherwise it will update the phone, i'm having att phone i updated manually, update was messed up my phone, now phone its 6.0 but errors on my phone, if you are not sure what you doing, please don't updated.
Click to expand...
Click to collapse
Thank you but my issue is not work root. My phone it's not rooted. My board is a VS900 verizon board but the FW is t mobile. That is why i am worried to accept the OTA.
ramyboy said:
Hello All
I would really appreciate the help on my situation.
I have bought a new motherboard from aliexpress. and it turns out the board is a VS990 with H901 5.1 installed on it.
Its working like a charm now I received the OTA update to android 6 but I am very scared to go ahead with the update as it will most probably brick the phone. Has anyone experienced same situation? Do i go ahead and let it do the OTA update? If not is there anyway I can install Nugget on my (Half / Half) setup ?
I will very much appreciate the help please.
Thanks
Click to expand...
Click to collapse
These posts should help you, I also thought I was in your boat until I searched my whole motherboard.
https://forum.xda-developers.com/tm...k-h901-f600l-board-2017-t3635697/post75788253
https://forum.xda-developers.com/tm...k-h901-f600l-board-2017-t3635697/post75799801
My motherboard also had vs990 printed on it but the "t" link is soldered. So my v10 is a h901, which makes sense since I bought mine from my local T-Mobile store right after release.
If you plan on rooting do not take the ota. It is much easier to root on 5.1 (10c), the fastboot commands are still intact. All updates after 5.1 get more difficult to root. Once rooted there is twrp flashable .zip in the development forum to safely bring you to the latest 7.0 update (30c) and is also a full firmware update.
Sent from my Moto Z (2) using XDA Labs
skywalker-live said:
These posts should help you, I also thought I was in your boat until I searched my whole motherboard.
https://forum.xda-developers.com/tm...k-h901-f600l-board-2017-t3635697/post75788253
https://forum.xda-developers.com/tm...k-h901-f600l-board-2017-t3635697/post75799801
My motherboard also had vs990 printed on it but the "t" link is soldered. So my v10 is a h901, which makes sense since I bought mine from my local T-Mobile store right after release.
If you plan on rooting do not take the ota. It is much easier to root on 5.1 (10c), the fastboot commands are still intact. All updates after 5.1 get more difficult to root. Once rooted there is twrp flashable .zip in the development forum to safely bring you to the latest 7.0 update (30c) and is also a full firmware update.
Sent from my Moto Z (2) using XDA Labs
Click to expand...
Click to collapse
Man you are a life saver.. I have just unlocked my bootloader. Now where is that forum with the TWRP Nugget Please???
ramyboy said:
Man you are a life saver.. I have just unlocked my bootloader. Now where is that forum with the TWRP Nugget Please???
Click to expand...
Click to collapse
Did you take apart your phone and verify your soldered link?
Do you have twrp 3.2.1 installed?
All the info you need can be found https://forum.xda-developers.com/tmobile-lg-v10/development
Reading about anything you plan to do will help prevent a brick.
To install twrp
'fasboot flash recovery <twrp.img>' (extract .img from .zip) https://androidfilehost.com/?fid=818070582850501883
Linked from https://forum.xda-developers.com/tmobile-lg-v10/development/twrp-3-2-1-h901-t3765971
'reboot recovery'
From twrp flash this .zip (firmware)
https://drive.google.com/file/d/0Bz7RQirmMu9MZHNSc3hjRTF3X0U
Linked from
https://forum.xda-developers.com/tmobile-lg-v10/development/h901-t-mobile-nougat-v30b-twrp-t3639203
Then flash this .zip (30c update)
https://androidfilehost.com/?fid=673956719939821713
Linked from
https://forum.xda-developers.com/tm.../h901-t-mobile-nougat-v30c-flashable-t3744648
Then flash magisk 16.0 (current stable version) for root. Done.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Read all threads I linked, some parts of them are old and have been superseded but will still provide valuable info that should prevent a brick.
Sent from my Moto Z (2) using XDA Labs
skywalker-live said:
Did you take apart your phone and verify your soldered link?
Do you have twrp 3.2.1 installed?
All the info you need can be found https://forum.xda-developers.com/tmobile-lg-v10/development
Reading about anything you plan to do will help prevent a brick.
To install twrp
'fasboot flash recovery <twrp.img>' (extract .img from .zip) https://androidfilehost.com/?fid=818070582850501883
Linked from https://forum.xda-developers.com/tmobile-lg-v10/development/twrp-3-2-1-h901-t3765971
'reboot recovery'
From twrp flash this .zip (firmware)
https://drive.google.com/file/d/0Bz7RQirmMu9MZHNSc3hjRTF3X0U
Linked from
https://forum.xda-developers.com/tmobile-lg-v10/development/h901-t-mobile-nougat-v30b-twrp-t3639203
Then flash this .zip (30c update)
https://androidfilehost.com/?fid=673956719939821713
Linked from
https://forum.xda-developers.com/tm.../h901-t-mobile-nougat-v30c-flashable-t3744648
Then flash magisk 16.0 (current stable version) for root. Done.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Read all threads I linked, some parts of them are old and have been superseded but will still provide valuable info that should prevent a brick.
Sent from my Moto Z (2) using XDA Labs
Click to expand...
Click to collapse
That is great.. I will read them all very carefully and I will try to do it tommorrow.
2 points :
First I have already installed TWRP recovery for LG V10 H901 (File: twrp-2.8.7.1-h901.img & SuperSU v2.56 and now i am rooted.
Second I am sure now even without looking at the Link that my board is a H901 else I think the boot loader would have never been simply unlocked. Dont you agree?
ramyboy said:
That is great.. I will read them all very carefully and I will try to do it tommorrow.
2 points :
First I have already installed TWRP recovery for LG V10 H901 (File: twrp-2.8.7.1-h901.img & SuperSU v2.56 and now i am rooted.
Second I am sure now even without looking at the Link that my board is a H901 else I think the boot loader would have never been simply unlocked. Dont you agree?
Click to expand...
Click to collapse
SuperSU is abandoned. TWRP 2.8.7.1 can't flash nougat, you'll need to upgrade to the 3.2.1 I linked but will only have to flash the .zip from TWRP. SuperSU will get removed when you flash the system updates so then you should have no problem installing magisk, just do a factory reset in TWRP after you do the updates before magisk to remove and data from SuperSU that my be left.
Your 2nd point is dead on, the h901 is the only US carrier branded v10 that can be bootloader unlocked. True vs990's were locked down tight in true Verizon fashion.
Sent from my Moto Z (2) using XDA Labs
Looking the posts you shared i understand that i cant upgrade 5.1 directly to nugget.. Corrent me if i am wrong. If not then which 6.0 should i flash using rtwp? And can i upgrade instead of wiping over the rooted 5.1? I would love to keep my apps and setting.
ramyboy said:
Looking the posts you shared i understand that i cant upgrade 5.1 directly to nugget.. Corrent me if i am wrong. If not then which 6.0 should i flash using rtwp? And can i upgrade instead of wiping over the rooted 5.1? I would love to keep my apps and setting.
Click to expand...
Click to collapse
That's the point of these twrp flashable updates, to update without wipeing . For the Android 6.0 updates use the part 1 (firmware) and part 2 (system, boot) 20L files in this thread.
https://forum.xda-developers.com/tmobile-lg-v10/development/rom-v10h901v20estock-customized-t3360240
It is still heavily suggested to wipe when changing major Android versions. Minor updates within the same version don't cause too much trouble, but data structure varies between major version updates. All this being said some people don't have problems with dirty (no wipe) flashes.
Sent from my Moto Z (2) using XDA Labs
skywalker-live said:
That's the point of these twrp flashable updates, to update without wipeing . For the Android 6.0 updates use the part 1 (firmware) and part 2 (system, boot) 20L files in this thread.
https://forum.xda-developers.com/tmobile-lg-v10/development/rom-v10h901v20estock-customized-t3360240
It is still heavily suggested to wipe when changing major Android versions. Minor updates within the same version don't cause too much trouble, but data structure varies between major version updates. All this being said some people don't have problems with dirty (no wipe) flashes.
Sent from my Moto Z (2) using XDA Labs
Click to expand...
Click to collapse
I dont understand why this happened . I followed the exact steps .. Downloaded Part 1 L and Part 2 L
Flashed part 1 with TWRP and did not reboot. Then flashed Part 2.. Then rebooted.. Now my phone doesnt even turn on.
This must be a hard brick.. I cant even go into TWRP any more .. and no logo appears.. the phone is detected on PC as QSUSB_BULK
ramyboy said:
I dont understand why this happened . I followed the exact steps .. Downloaded Part 1 L and Part 2 L
Flashed part 1 with TWRP and did not reboot. Then flashed Part 2.. Then rebooted.. Now my phone doesnt even turn on.
This must be a hard brick.. I cant even go into TWRP any more .. and no logo appears.. the phone is detected on PC as QSUSB_BULK
Click to expand...
Click to collapse
There are a few threads that discuss recovering from bricked 20J software that you could try. (20L is said to be the only software that can downgrade, but only to 20J) Most people had LG do warranty exchange. This is the frustrating part of LG phones, how easy LG made it to brick if you didn't fully read up on what you were doing.
Sent from my Moto Z (2) using XDA Labs
hi. can anyone help me to fix my phone after update to MM 6.0, having errors LG vpn has stopped, finger print not working n and can't uninstall any program its reboot itself, I'm using ATT phone had 5.1 LP, motherboard is board is a VS990
im looking correct firmware to correct these errors on MM or upgrade to 7.0?
Please help me
skywalker-live said:
There are a few threads that discuss recovering from bricked 20J software that you could try. (20L is said to be the only software that can downgrade, but only to 20J) Most people had LG do warranty exchange. This is the frustrating part of LG phones, how easy LG made it to brick if you didn't fully read up on what you were doing.
Sent from my Moto Z (2) using XDA Labs
Click to expand...
Click to collapse
Hi Skywalker
I tried the image sd card method provided by tungkick and i could go to download mode. I uses 20j tot and flashed succesfully but phone keeps looping lg logo and verdication fail message in red.. you think this the wrong firmware? Whats the next step?
ramyboy said:
Hi Skywalker
I tried the image sd card method provided by tungkick and i could go to download mode. I uses 20j tot and flashed succesfully but phone keeps looping lg logo and verdication fail message in red.. you think this the wrong firmware? Whats the next step?
Click to expand...
Click to collapse
The unbricking thread should have some input on that problem, just search for it.
Sent from my Moto Z (2) using XDA Labs
Hi new user here. I checked the website and I see I have the latest Android version but in the website it shows android 9 but I have android 8. I am wondering if android 9 is released in Canada. Thanksh
https://xpericheck.com/device/G8341
A lot regions skipped November/Pie (probably due to time constraints or ignorance) and are being pushed out now as we speak.
Techamazon said:
https://xpericheck.com/device/G8341
A lot regions skipped November/Pie (probably due to time constraints or ignorance) and are being pushed out now as we speak.
Click to expand...
Click to collapse
Ya but even there there is no mention of G8343 variant. You can't search it lol.
https://xpericheck.com/device/G8343
Not sure why Canadians have a different version since the US is the same as ROW (except JP). Oh well... Anyhow, expect updates to start being pushed from the 6th all the way to the 14th. After that, nothing will happen till January. But judging from the average time it seems you belong to the week 2 category (10-14th).
I couldn't wait for it so I flashed the US firmware since I don't care for the fingerprint reader
Phat-T said:
I couldn't wait for it so I flashed the US firmware since I don't care for the fingerprint reader
Click to expand...
Click to collapse
Why not flash a European firmware?
Umm from what I remembered, European firmwares uses the 4G symbol instead of LTE. That's the only reason I chose the US firmware haha
Phat-T said:
Umm from what I remembered, European firmwares uses the 4G symbol instead of LTE. That's the only reason I chose the US firmware haha
Click to expand...
Click to collapse
Lol hahaha. Anyways can you help me flash the firmware? I am not so sure how to flash 2 different variants
PM'd you
I want to flash aslwell and have rooted my Samsung device but never a sony
So I have no Idea how to get the roms or apks to flash my phone with and what applications are used to flash Sony phones
Addy1993 said:
So I have no Idea how to get the roms or apks to flash my phone with and what applications are used to flash Sony phones
Click to expand...
Click to collapse
flashing a sony phone is different to that of samsung. You have to backup drm key(ta partition) before you even unlock your bootloader, because without that you camera will become useless. I cant give you links but I am sure if you look around you will find them. After unlocking your bootloader it is very simple. Just flash a kernel and the rom that you want to.
The application we use for flashing kernels for sony phones is flashtool. Just make sure you have the right kernels and files before flashing.
Goodluck.
My bootloader is unlocked already I just can't find a rom that will work for an xz1 can you give me a hint on what exactly to search. There is no support for the xz1 and as for backing up the drm key where is that found?
Addy1993 said:
My bootloader is unlocked already I just can't find a rom that will work for an xz1 can you give me a hint on what exactly to search. There is no support for the xz1 and as for backing up the drm key where is that found?
Click to expand...
Click to collapse
Yup there isn't really much or any support at all for Sony phones nowadays. I didn't find any good custom ROMs so sorry I wouldn't be the right person to advice you. And as for DRM keys. Once you unlock it. It's gone. I heard they have introduced some fixes or something. I don't know.
Need help
Can you give me guidance on how to with out braking my phone
As soon as you said you had 8.1 on your phone I knew this would be an interesting read.. Not sure how long ago you. unlocked your BL but once you did it you lost your DRM keys, though if you had read a bit you would have realized that.. there is a DRM fix for oreo (8.0), Pie is debatable as the camera appears to work without one but a few other thing appears to be missing related to video and sound enhancements without a DRM fix.. Now as far as flashing go it's time for you to do your homework as there are a few guidelines for using Flashtool and Newsflasher.. no disrespect here but hunt them down and read through them before you do anything else to your phone..
Currently using firmware 47.1.A.12.270 with root+drm fix. I'm considering to upgrade my phone to Pie but i'm unsure about its stability. I wanna hear how stable is Pie and is it good to upgrade?
evildog1 said:
Currently using firmware 47.1.A.12.270 with root+drm fix. I'm considering to upgrade my phone to Pie but i'm unsure about its stability. I wanna hear how stable is Pie and is it good to upgrade?
Click to expand...
Click to collapse
Since you are already rooted - you could (probably) downgrade... although I am not able to find official firmware for OREO.
My device is 0FCE:01F3 (seems that there is a different version of Sony Xperia XZ1 with id 0FCE:B00B).
I guess that you have nothing against unlocking the bootloader
So in other words: you could try upgrading and see (although way back might be difficult).
As for me... I have accepted the upgrade and I regret that.
Android 9 Pie blocks one feature that is mandatory for me: call recording is no longer possible.
There should be some gesture navigation - it is not present in pie on xz1.
Except that... you should be going into a better direction. I am not sure about root availability for xz1... shouldn't be a problem I guess?
P.S.
I bought this phone only because my previous (it was gt-n910c) had some HW issues with calls. I wanted a phone with NFC and my assumption was I won't root it (to use banking apps without magisk). Now it seems that my calls are flawed and I might need to use magisk+root... and I am not able to physically remove bloatware (especially spyware called fatbook or something like that). Shame on google, Shame on sony.
As your bl is already unlocked download Xperia firm and see if Pie is available in your region, if so download Newflasher (read how to use it), there is a root guide posted here for Pie.
It's in the guide section
evildog1 said:
Currently using firmware 47.1.A.12.270 with root+drm fix.
Click to expand...
Click to collapse
By any chance - do you have stock FW for Oreo ? I am no longer able to get it from xperia servers so downgrading is not possible for me...
lilbrat said:
As your bl is already unlocked download Xperia firm and see if Pie is available in your region, if so download Newflasher (read how to use it), there is a root guide posted here for Pie.
It's in the guide section
Click to expand...
Click to collapse
I was asking if should upgrade and how stable it was but I will try upgrade anyway lol
Root is easy on unlocked BL phones.
adderek said:
By any chance - do you have stock FW for Oreo ? I am no longer able to get it from xperia servers so downgrading is not possible for me...
Click to expand...
Click to collapse
I have downloaded G8341_Customized NOBA_1310-7488_47.1.A.16.20_R24B from XperiFirm which is last version of Oero but never got time to flash.
As I don't use call recording, i'm good to upgrade to Pie.
evildog1 said:
I was asking if should upgrade and how stable it was but I will try upgrade anyway lol
Root is easy on unlocked BL phones.
For me as I have been one of the few that have had the updates since they first started and It has been very stable...
Click to expand...
Click to collapse