I recently broke my phone and went out and purchased a cheap AT&T phone, after poking around a bit i discovered oem unlock was in the developer settings
I hop on my pc ran adb reboot bootloader, and it boots to fastboot mode just fine
I run fastboot oem unlock, and to my surprise that worked aswell. I rebooted and saw a 'unlocked bootloader' message from AT&T telling me my device wasen't official
but it booted up fine a few seconds later. My question is, is there some form of root for this device? Any help is appreciated !
Just to clarify i have already tried a multitude of '1click root apps' and pc tools and none of those worked, I'm more interested in finding the stock firmware or atleast boot.img so i can install magisk
Specs :
LG Phoneix 4 (LM-X210 )
Android Version : 7.1.2
Kernal Version : 3.18.31
Build Number : N2G47H
Software Number : X210APM10d
(sorry if this is messy or posted in the wrong place i've been a long time lurker but this is my first post lol)
kinghangry said:
I recently broke my phone and went out and purchased a cheap AT&T phone, after poking around a bit i discovered oem unlock was in the developer settings
I hop on my pc ran adb reboot bootloader, and it boots to fastboot mode just fine
I run fastboot oem unlock, and to my surprise that worked aswell. I rebooted and saw a 'unlocked bootloader' message from AT&T telling me my device wasen't official
but it booted up fine a few seconds later. My question is, is there some form of root for this device? Any help is appreciated !
Just to clarify i have already tried a multitude of '1click root apps' and pc tools and none of those worked, I'm more interested in finding the stock firmware or atleast boot.img so i can install magisk
Specs :
LG Phoneix 4 (LM-X210 )
Android Version : 7.1.2
Kernal Version : 3.18.31
Build Number : N2G47H
Software Number : X210APM10d
(sorry if this is messy or posted in the wrong place i've been a long time lurker but this is my first post lol)
Click to expand...
Click to collapse
Hey for anyone else with this question there is a root method. Head over to Tec's Aristo 2 Tutorial's. Someone with this device confirmed that it works. Also an upgrade from the LG Pheonix 4, to LG Aristo 2+ with Oreo Firmware to escape nougat.
Also... This phone is the exact same phone as the Aristo 2, 2+, and K8+ so I think you guys should flash some Aristo 2 stuff. It will work wonders!
NonStickAtom785 said:
Hey for anyone else with this question there is a root method. Head over to Tec's Aristo 2 Tutorial's. Someone with this device confirmed that it works. Also an upgrade from the LG Pheonix 4, to LG Aristo 2+ with Oreo Firmware to escape nougat.
Click to expand...
Click to collapse
I can confirm this root method for the Aristro 2 will also work for the Phoenix 4 on 7.1.2
link to tutorial, please?
Stop!! The method for Aristro 2 does not work for other variant like the LG Phoenix 4 or the LG rebel 4. You will end up with no touch screen. Again, this method is only for Aristro 2 variant
If you have any other variant do not try this.
---------- Post added at 04:15 PM ---------- Previous post was at 04:12 PM ----------
NonStickAtom785 said:
Hey for anyone else with this question there is a root method. Head over to Tec's Aristo 2 Tutorial's. Someone with this device confirmed that it works. Also an upgrade from the LG Pheonix 4, to LG Aristo 2+ with Oreo Firmware to escape nougat.
Also... This phone is the exact same phone as the Aristo 2, 2+, and K8+ so I think you guys should flash some Aristo 2 stuff. It will work wonders!
Click to expand...
Click to collapse
Stop!! The method for Aristro 2 does not work for other variant like the LG Phoenix 4 or the LG rebel 4. You will end up with no touch screen. Again, this method is only for Aristro 2 variant
If you have any other variant do not try this.
jbird1978 said:
Stop!! The method for Aristro 2 does not work for other variant like the LG Phoenix 4 or the LG rebel 4. You will end up with no touch screen. Again, this method is only for Aristro 2 variant
If you have any other variant do not try this.
---------- Post added at 04:15 PM ---------- Previous post was at 04:12 PM ----------
Stop!! The method for Aristro 2 does not work for other variant like the LG Phoenix 4 or the LG rebel 4. You will end up with no touch screen. Again, this method is only for Aristro 2 variant
If you have any other variant do not try this.
Click to expand...
Click to collapse
I can confirm as well. The method for Aristro 2 does not work for Phoenix 4. I found out the hard way
ox64 said:
I can confirm as well. The method for Aristro 2 does not work for Phoenix 4. I found out the hard way
Click to expand...
Click to collapse
What did you do? What varient of the phone are you on? You don't need to install the firmware. Your bootloader is unlockable. I need someone to send me a backup of there boot image so I can patch it for device specific usage. Then I can use meld to merge the Aristo 2 boot and Phoenix 4 boot images. If there are still sceptics so be it. The phone is the exact same as the Aristo 2 and probably the only other cv1 device compatible with the root method.
Link to Tecknight's Aristo 2 Tutorials:
https://forum.xda-developers.com/android/general/tecknights-aristo-2-tutorials-t3805141
NonStickAtom785 said:
What did you do? What varient of the phone are you on? You don't need to install the firmware. Your bootloader is unlockable. I need someone to send me a backup of there boot image so I can patch it for device specific usage. Then I can use meld to merge the Aristo 2 boot and Phoenix 4 boot images. If there are still sceptics so be it. The phone is the exact same as the Aristo 2 and probably the only other cv1 device compatible with the root method.
Link to Tecknight's Aristo 2 Tutorials:
https://forum.xda-developers.com/android/general/tecknights-aristo-2-tutorials-t3805141
Click to expand...
Click to collapse
Listen, everything went well, the unlock, twrp, even lineage os but if you touch the screen, it does nothing. Restoring stock didnt even work. Ended up taking the phone back and exchanging it for an Alcatel beings no more lg Phoenix 4 was in. My wife has a lg rebel 4 but im not trying it with hers. I should add though, touch did work in twrp, but twrp only.
WOO WOO!
Hello everyone, can anyone confirm that bootloader is unlockable after oreo update? I am thinking about working with this phone!
Thanks
Wild-Owl
Updating LG Phoenix 4 to Oreo re locks bootloader and disables fastboot!
jbird1978 said:
Listen, everything went well, the unlock, twrp, even lineage os but if you touch the screen, it does nothing. Restoring stock didnt even work. Ended up taking the phone back and exchanging it for an Alcatel beings no more lg Phoenix 4 was in. My wife has a lg rebel 4 but im not trying it with hers. I should add though, touch did work in twrp, but twrp only.
Click to expand...
Click to collapse
Okay then you should just use twrp. Lineage. I need to make device specific roms.
NonStickAtom785 said:
Okay then you should just use twrp. Lineage. I need to make device specific roms.
Click to expand...
Click to collapse
No what im saying is that once you go through this process, no matter what you put on there, custom or stock, the touch screen does not work. Only in twrp does it work but not in any rom, not even reverting to stock or applying backups work. Im saying, once this phone has twrp on it, touch screen only work in twrp, nowhere else, no matter what.
Android 8???
I have the phoenix 4 lm x210apm with android 7.1.2
and I do not have android 8.1, it does not update
jbird1978 said:
No what im saying is that once you go through this process, no matter what you put on there, custom or stock, the touch screen does not work. Only in twrp does it work but not in any rom, not even reverting to stock or applying backups work. Im saying, once this phone has twrp on it, touch screen only work in twrp, nowhere else, no matter what.
Click to expand...
Click to collapse
Ok, do you mind making a backup of your OP partition. Also I need to know your stock firmware version. I'm going to consult technight with that firmware version to make a new 7.1.2/1 and possibly an 8.1 ROM for you. It will take a bit but now that you guys have TWRP we can work on getting everything else to work. Honestly I think the touchscreen isn't working because the OP partitions are different. Did you install TWRP 3.1.2.0 and one of the Aristo 2 ROMs?
Try this method. If it none of it works let me know.
https://forum.xda-developers.com/showpost.php?p=78218056&postcount=130
NonStickAtom785 said:
Ok, do you mind making a backup of your OP partition. Also I need to know your stock firmware version. I'm going to consult technight with that firmware version to make a new 7.1.2/1 and possibly an 8.1 ROM for you. It will take a bit but now that you guys have TWRP we can work on getting everything else to work. Honestly I think the touchscreen isn't working because the OP partitions are different. Did you install TWRP 3.1.2.0 and one of the Aristo 2 ROMs?
Try this method. If it none of it works let me know.
https://forum.xda-developers.com/showpost.php?p=78218056&postcount=130
Click to expand...
Click to collapse
I no longer have this device, i had to get a new because the method made the Phoenix a paper weight.
jbird1978 said:
I no longer have this device, i had to get a new because the method made the Phoenix a paper weight.
Click to expand...
Click to collapse
But it should have a firehose available. I'm sorry for your loss if not.
Does anyone know if magisk works on the Phoenix 4? Or will there be a bootloop issue ?
NonStickAtom785 said:
Ok, do you mind making a backup of your OP partition. Also I need to know your stock firmware version. I'm going to consult technight with that firmware version to make a new 7.1.2/1 and possibly an 8.1 ROM for you. It will take a bit but now that you guys have TWRP we can work on getting everything else to work. Honestly I think the touchscreen isn't working because the OP partitions are different. Did you install TWRP 3.1.2.0 and one of the Aristo 2 ROMs?
Try this method. If it none of it works let me know.
https://forum.xda-developers.com/showpost.php?p=78218056&postcount=130
Click to expand...
Click to collapse
I've got one of these AT&T LG Phoenix 4 phones, but it's stuck on 7.12 since I gave away the AT&T SIM and AT&T will only update when on their network. Anyway, I'm interested in at least getting it updated to stock Oreo or perhaps a custom ROM. Let me know if there's something I can do to help (not sure how to backup OP partition). I see in the forums that there a few people with the AT&T version of this phone who can't update so hopefully this could help a few people out.
PsychoMcSatan said:
I've got one of these AT&T LG Phoenix 4 phones, but it's stuck on 7.12 since I gave away the AT&T SIM and AT&T will only update when on their network. Anyway, I'm interested in at least getting it updated to stock Oreo or perhaps a custom ROM. Let me know if there's something I can do to help (not sure how to backup OP partition). I see in the forums that there a few people with the AT&T version of this phone who can't update so hopefully this could help a few people out.
Click to expand...
Click to collapse
So right now you need to follow the steps on the Aristo 2 forums to get TWRP Recovery. After that I can start working on getting a base for the LG Phoenix 4 version of the Oreo ROM.
NonStickAtom785 said:
So right now you need to follow the steps on the Aristo 2 forums to get TWRP Recovery. After that I can start working on getting a base for the LG Phoenix 4 version of the Oreo ROM.
Click to expand...
Click to collapse
I'm a little wary about flashing that TWRP recovery since it sounds like the few people that have successfully done that end up with the touchscreen not working, and even re-flashing stock does not recover it.
Is there anyone here that has flashed TWRP without adverse effects?
Related
Has anyone tried using send_command to flash the LAF partition to BOOT (for backup sakes.. Need to be able to revert), after backing up to sdcard obviously, then flashing TMOBILE LAF to LAF partition. Rebooting the device again to download, now fastboot and oem unlocking? I was able to get this working on my old G3, I just got stuck in fastboot due to lg not having an official unlock tool (now available). From there TWRP could be flashed, and then root! After flashing the stock boot of course!!
Seriously!? Nobody responded!???? Maybe post this in the G5 Q&A????
jjj551280jjj said:
Has anyone tried using send_command to flash the LAF partition to BOOT (for backup sakes.. Need to be able to revert), after backing up to sdcard obviously, then flashing TMOBILE LAF to LAF partition. Rebooting the device again to download, now fastboot and oem unlocking? I was able to get this working on my old G3, I just got stuck in fastboot due to lg not having an official unlock tool (now available). From there TWRP could be flashed, and then root! After flashing the stock boot of course!!
Click to expand...
Click to collapse
Sounds like, and I could be wrong...an idea! Anyone else know about the odds of this working!????
jreed3786 said:
Sounds like, and I could be wrong...an idea! Anyone else know about the odds of this working!????
Click to expand...
Click to collapse
Not as of yet.. I've been doing research and testing
I will totally try this- as soon as the factory images are released, I'm all for expirementation, but I can't take one that big for the team!
Still no root for the LG G5 H820 (AT&T) Marshmallow 6.0.1?
Jim Mitchell said:
Still no root for the LG G5 H820 (AT&T) Marshmallow 6.0.1?
Click to expand...
Click to collapse
No, and honestly I don't think there will be. AT&T has locked this device down, and I mean locked it down HARD. If AT&T will release a tot or kdz then maybe we could get root, as someone could just make a pre-rooted system of the tot or kdz (right, guys?) but until (or if) they release it, I don't think there will be root. I would be willing to test for some things if I knew I could just flash back to stock if things go wrong but right now I can't, so I'm not willing to test for anything as I don't have the money to just go purchase another device if this one bricks.
Root for G5 h820?
If this is usefull at all to find root for the at&t g5 h820 i have the system zip file directly from LG? And ill help in anyway i do some android hacking and exploiting...
Quinnshank said:
If this is usefull at all to find root for the at&t g5 h820 i have the system zip file directly from LG? And ill help in anyway i do some android hacking and exploiting...
Click to expand...
Click to collapse
Is the system zip file for the AT&T variant? Can you upload it to Mega or Google Drive or something, please?
thatkindaguy said:
Is the system zip file for the AT&T variant? Can you upload it to Mega or Google Drive or something, please?
Click to expand...
Click to collapse
Yeah i will do that asap and the device i used was registered at&t h820
Quinnshank said:
Yeah i will do that asap and the device i used was registered at&t h820
Click to expand...
Click to collapse
Cool thanks man hopefully this should help, once uploaded I'll look through the system zip as well and do some research and possibly some testing.
posting
so it says before i upload a file i have to post a couple times so im just gonna ramble...
Quinnshank said:
so it says before i upload a file i have to post a couple times so im just gonna ramble...
Click to expand...
Click to collapse
You can always send a private message
Quinnshank said:
so it says before i upload a file i have to post a couple times so im just gonna ramble...
Click to expand...
Click to collapse
Yeah man you can private message me the link if you want, I can post it here and give you credits
post
[/COLOR]finally here is the H820 zip file direct from LG let me know what i can do to help::: https://drive.google.com/open?id=0BxbSBlcTY8vfSkE4dnZ6U0E1Wnc
Quinnshank said:
[/COLOR]finally here is the H820 zip file direct from LG let me know what i can do to help::: https://drive.google.com/open?id=0BxbSBlcTY8vfSkE4dnZ6U0E1Wnc
Click to expand...
Click to collapse
ok, so what you have is the source code. it will come in handy if you wanna look at the way it's built.
---------- Post added at 12:11 PM ---------- Previous post was at 12:06 PM ----------
jjj551280jjj said:
Has anyone tried using send_command to flash the LAF partition to BOOT (for backup sakes.. Need to be able to revert), after backing up to sdcard obviously, then flashing TMOBILE LAF to LAF partition. Rebooting the device again to download, now fastboot and oem unlocking? I was able to get this working on my old G3, I just got stuck in fastboot due to lg not having an official unlock tool (now available). From there TWRP could be flashed, and then root! After flashing the stock boot of course!!
Click to expand...
Click to collapse
You are kind of on the right path, but there is no way to just "flash" the t-mobile LAF partition. There are too many security variables that you need to find a work-around for, along with trying to find a way to get it onto your device.
Another thing is that THE SEND_COMMAND DOES NOT WORK ON THE G5. This has been talked about on many other threads, and it doesn't work.
Why is the AT&T getting so little love compared to all other models !? We need root too
boksquare said:
Why is the AT&T getting so little love compared to all other models !? We need root too
Click to expand...
Click to collapse
Well the biggest issue is on top of AT&T locking the device down, they aren't releasing a kdz or tot file.
I've been out of the game for awhile, but aren't they obligated to due to open source?
Sent from my LG-H820 using Tapatalk
kyuubi08 said:
I've been out of the game for awhile, but aren't they obligated to due to open source?
Sent from my LG-H820 using Tapatalk
Click to expand...
Click to collapse
Yea that's what I was thinking. How can they be the only carrier that doesn't have to release the FW? They do the same thing on the AT&T S7 and S7E. Can they be sued for that?
Sent from my VK815 using XDA-Developers mobile app
Just wondering what roms have worked successfully on the RS988, as well as Kernels. I've not seen any evidence of any compatibility, but I'm not sure I want to risk it without confirming that first. Thanks for any and all replies.
To the best of my knowledge... none.
alex03man said:
Just wondering what roms have worked successfully on the RS988, as well as Kernels. I've not seen any evidence of any compatibility, but I'm not sure I want to risk it without confirming that first. Thanks for any and all replies.
Click to expand...
Click to collapse
ED2O9 said:
To the best of my knowledge... none.
Click to expand...
Click to collapse
Yeah currently there ate no ROMs or kennels for any other devices except h830 (t mobile) and h850 (unlocked European version). This is due to the fact that those were the only devices that could be boot loader unlocked. Now if this new method is working for you guys on other devices and you have working twrp for your devices that actually flash files then the devs building ROMs for the two currently supported should be able to include the other devices but do NOT flash any roms for any other device to yours. Kindly ask the devs (like @King_lilrowrow or @gwolfu) if they could support your devices. I don't currently fully know if this is possible as I'm not sure you guys can flash files via twrp successfully yet, you would have to ask a dev. If unable to flash files you may need twrp updated for each device (kernel specific stuff), but again not sure as I'm not a developer. Hopefully this heels and hopefully you guys get a chance to enjoy custom ROMs like I have. I know I couldn't deal without, I'm a flashaholic. I actually returned my RS988 for a h830.
jeffsga88 said:
Yeah currently there ate no ROMs or kennels for any other devices except h830 (t mobile) and h850 (unlocked European version). This is due to the fact that those were the only devices that could be boot loader unlocked. Now if this new method is working for you guys on other devices and you have working twrp for your devices that actually flash files then the devs building ROMs for the two currently supported should be able to include the other devices but do NOT flash any roms for any other device to yours. Kindly ask the devs (like @King_lilrowrow or @gwolfu) if they could support your devices. I don't currently fully know if this is possible as I'm not sure you guys can flash files via twrp successfully yet, you would have to ask a dev. If unable to flash files you may need twrp updated for each device (kernel specific stuff), but again not sure as I'm not a developer. Hopefully this heels and hopefully you guys get a chance to enjoy custom ROMs like I have. I know I couldn't deal without, I'm a flashaholic. I actually returned my RS988 for a h830.
Click to expand...
Click to collapse
If other G5's have BL unlocked and a working build of TWRP then it will be easy for me to add support to my CM14.1 (LineageOS) builds.
The TWRP version targeting 20a/b isn't 100% needed but avoids issues with TZ assertion.
The only device I'm aware of thats close to an unlock method (via someone I know) is the H840 (LG G5 SE)
When any other G5 model is supported you'll see it on our GitHub site: https://www.github.com/ConquestTeam/
King_lilrowrow said:
If other G5's have BL unlocked and a working build of TWRP then it will be easy for me to add support to my CM14.1 (LineageOS) builds.
The TWRP version targeting 20a/b isn't 100% needed but avoids issues with TZ assertion.
The only device I'm aware of thats close to an unlock method (via someone I know) is the H840 (LG G5 SE)
When any other G5 model is supported you'll see it on our GitHub site: https://www.github.com/ConquestTeam/
Click to expand...
Click to collapse
Yeah from what I read in this thread http://forum.xda-developers.com/lg-g5/how-to/guide-adb-root-rw-dm-verity-off-sprint-t3523499 it appears that this method allowed them to flash twrp, although not sure if it's working 100% (I know they're having issues flashing SuperSU). Not sure if it's also unlocking the boot loader or not or of it simply bypasses the boot loader unlocking issues like old exploits on g2, g3 and g4. But as I said before I'm on h830 so not sure about this method and what exactly it's doing. But it appears to replace recovery with twrp. Also it appears to only be disabling DM verity and mounting system as rw via adb, not sure if it's allowing you to do this via twrp or not. Again if not, I'm assuming that you may need a new twrp built based on the modified kernel and boot image this method flashes. If that's they case maybe someone can goto twrp thread and ask support to be added specifically for these other versions, don't know.
King_lilrowrow said:
When any other G5 model is supported you'll see it on our GitHub site: https://www.github.com/ConquestTeam/
Click to expand...
Click to collapse
Getting a 404.
fallenturtle said:
Getting a 404.
Click to expand...
Click to collapse
github.com/kinglilrowrow
The team I was in parted ways, I work alone now
King_lilrowrow said:
github.com/kinglilrowrow
The team I was in parted ways, I work alone now
Click to expand...
Click to collapse
Since RS988 is now bootloader unlockable, do you have any plans to support this device?
I appreciate your work!!
lentm said:
Since RS988 is now bootloader unlockable, do you have any plans to support this device?
I appreciate your work!!
Click to expand...
Click to collapse
At this time my focus is bringing up the G6 as well as a few other projects I'm working on.
I may look into supporting the RS988 and H840 shortly.
King_lilrowrow said:
At this time my focus is bringing up the G6 as well as a few other projects I'm working on.
I may look into supporting the RS988 and H840 shortly.
Click to expand...
Click to collapse
Sorry to bug, but did you ever get the chance to look into RS988 support?
Thanks.
King_lilrowrow said:
At this time my focus is bringing up the G6 as well as a few other projects I'm working on.
I may look into supporting the RS988 and H840 shortly.
Click to expand...
Click to collapse
Any update? I'd really appreciate rs988 support!
RS988 Porting
So now that we have full bootloader and root capability w/custom recovery. Does anyone know what it would take to port any AOSP ROMS or stock ROM's like Fulmics to this device?
jmgamer12 said:
So now that we have full bootloader and root capability w/custom recovery. Does anyone know what it would take to port any AOSP ROMS or stock ROM's like Fulmics to this device?
Click to expand...
Click to collapse
Not sure but I do know it would make many of us very happy to see it. I've not stumbled upon the root procedure yet but anxious to get started.
LGtMgG2t said:
Not sure but I do know it would make many of us very happy to see it. I've not stumbled upon the root procedure yet but anxious to get started.
Click to expand...
Click to collapse
If you look it up in XDA, there Are already threads with bootloader unlock + root + TWRP threads to get you started. I'm running stock rooted and it's pretty solid. Just wanna see if this device can get into the ROM game
Sent from my RS988 using Tapatalk
Hey, did you use TWRP? Thx
jmgamer12 said:
So now that we have full bootloader and root capability w/custom recovery. Does anyone know what it would take to port any AOSP ROMS or stock ROM's like Fulmics to this device?
Click to expand...
Click to collapse
Yes
-lukin- said:
Hey, did you use TWRP? Thx
Click to expand...
Click to collapse
Yes. It's currently the only custom recovery for this device.
Cool I see h830 and h850 on the TWRP devices page. So rs988 works too? :good:
jmgamer12 said:
Yes. It's currently the only custom recovery for this device.
Click to expand...
Click to collapse
-lukin- said:
Cool I see h830 and h850 on the TWRP devices page. So rs988 works too? :good:
Click to expand...
Click to collapse
If you poke around LG G6 ROM Development forums you'll find a thread on unlocking bootloader's for this device and there is a download for the RS988 specific TWRP. It's not on the TWRP site
Sent from my RS988 using Tapatalk
"LG G5 ROM Development forums" - Good tip!
jmgamer12 said:
If you poke around LG G6 ROM Development forums you'll find a thread on unlocking bootloader's for this device and there is a download for the RS988 specific TWRP. It's not on the TWRP site
Sent from my RS988 using Tapatalk
Click to expand...
Click to collapse
-lukin- said:
"LG G6 ROM Development forums" - Good tip!
Click to expand...
Click to collapse
Whoops slight error. I meant LG G5
Sent from my RS988 using Tapatalk
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.
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
I am looking for someone who has a Xiaomi Black Shark (SKR-A0) that HAS NEVER ROOTED THEIR PHONE!
OTA is currently fixed for Global (SKR-H0) users, but not yet for CN (SKR-A0) users. I am looking for someone who:
Has a locked/unlocked bootloader
Has NEVER rooted their Black Shark Device
MUST be CN version (SKR-A0)
Thanks!
JengaMasterG said:
I am looking for someone who has a Xiaomi Black Shark (SKR-A0) that HAS NEVER ROOTED THEIR PHONE!
OTA is currently fixed for Global (SKR-H0) users, but not yet for CN (SKR-A0) users
Click to expand...
Click to collapse
Install factory firmware from this post and you will have OTA
hed1n said:
Install factory firmware from this post and you will have OTA
Click to expand...
Click to collapse
Thanks. I did see that, but I wasn't sure where the files came from or what the other 2 files are..
JengaMasterG said:
Thanks. I did see that, but I wasn't sure where the files came from or what the other 2 files are..
Click to expand...
Click to collapse
i tried this method last night, and it was perfect succesfully get my black shark CN ver into original G66X1903040CN00MPX android 8.1 version. Then i success update to G66X1906251CN00MPP which is the latest stable updated in android pie. :good:
Can you teach me on how to flash my Chinese SKR-AO to factory 8.1 because I have a problem in 9.0. whenever i try to go to clear data/clear cache screen for any apps, it always crashed to home screen. Thank you.
jaygan93 said:
i tried this method last night, and it was perfect succesfully get my black shark CN ver into original G66X1903040CN00MPX android 8.1 version. Then i success update to G66X1906251CN00MPP which is the latest stable updated in android pie. :good:
Click to expand...
Click to collapse
aqoerama said:
Can you teach me on how to flash my Chinese SKR-AO to factory 8.1 because I have a problem in 9.0. whenever i try to go to clear data/clear cache screen for any apps, it always crashed to home screen. Thank you.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=ywC_9Hrpb_I
cn bs unrooted
hi good day. i think i might have what you need. a cn bs unrooted but recently updated ota though. what do i do?
btw, bs is my first android phone i bought last october, 2018, so go easy on me. i came here in hopes to root it, but wanted to help before i do.
wendellmaru said:
hi good day. i think i might have what you need. a cn bs unrooted but recently updated ota though. what do i do?
btw, bs is my first android phone i bought last october, 2018, so go easy on me. i came here in hopes to root it, but wanted to help before i do.
Click to expand...
Click to collapse
Hey thanks for replying! You can go ahead and root since I was able to restore mine back to stock and get OTA working again ?
JengaMasterG said:
Hey thanks for replying! You can go ahead and root since I was able to restore mine back to stock and get OTA working again ?
Click to expand...
Click to collapse
Can you share a full backup of chinese partitions?
JengaMasterG said:
Hey thanks for replying! You can go ahead and root since I was able to restore mine back to stock and get OTA working again
Click to expand...
Click to collapse
i messed up. im stuck on fastboot (bootloader) mode. everytime i choose recovery mode or start, it vibrates and restarts 4 or 5 times only upto the S logo, before going back to fastboot mode again.
"fastboot boot twrp-3.2.3-0-blackshark.img" didnt work for me. it just starts my phone normally. so i tried "fastboot flash recovery twrp-3.2.3-0-blackshark.img" and got error.
need help pls.
edit: im still reading the whole thread and learning of flashing my bs from skr-a0 to skr-h0. i hope ill succeed from the files and procedures im getting at this link: youtube.com/watch?v=ywC_9Hrpb_I
edit2: was successful in flashing to skr-h0 using flash_all.bat (not brick anymore yay! it gave me the chills really.) sending "fastboot boot twrp-3.2.3-0-blackshark.img" command also now loads me to twrp (thank heavens) but i need to system update OTA first before trying to root again. will update soon.
edit3: now enjoying root on android 8.1... found the hard way that twrp-3.2.3-0-blackshark.img is not for android 9 and wont boot to twrp. probably flashed back to 8.1 for like 5 times more or less. hope maurino or someone else will make and release twrp-3.2.3-1-blackshark.img soon. thanks again for this wonderful thread.
btw: i originally wanted skr-a0 but i cant seem to download the link in the youtube video. file is corrupted. is it just me? i tried on 3 different workstations to no avail.
gilbert32 said:
Can you share a full backup of chinese partitions?
Click to expand...
Click to collapse
I've already updated the support megathread and other links with the image files I made...
Is pie version stable enough to use now? Im still on 8.1 because ppl said it was rebooting non stop and overheating.
Also is it possible to root android pie? Twrp working?
shteren said:
Is pie version stable enough to use now? Im still on 8.1 because ppl said it was rebooting non stop and overheating.
Also is it possible to root android pie? Twrp working?
Click to expand...
Click to collapse
I haven't had any issues with the pie update. TWRP currently doesn't work, but the source files on GitHub have been updated I believe. TWRP needs to be available for rooting.
I have DLT-A0
JengaMasterG said:
I am looking for someone who has a Xiaomi Black Shark (SKR-A0) that HAS NEVER ROOTED THEIR PHONE!
OTA is currently fixed for Global (SKR-H0) users, but not yet for CN (SKR-A0) users. I am looking for someone who:
Has a locked/unlocked bootloader
Has NEVER rooted their Black Shark Device
MUST be CN version (SKR-A0)
Thanks!
Click to expand...
Click to collapse
I have the new BS2 pro DLT-A0
Not rooted yet
I do
BS1 Android 9 never rooted or anything
I have a global ROM, but is from the beta program.
I'm sorry I'm new to this forum. I would like to ask if anybody had problems with their blackshark 3.
When i open camera app inside other app, like capturing instagram stories, the flash doesn't work.
Thank you all.