Related
Hi guys,
Yesterday I got sweaty hand palms.
My EU 815 G4 is unlocked, the official way, and I had rooted it.
Then I tried to install xposed from twrp and I did something wrong, and ended up in bootloop...
I have just updated to v20b before, and forgot to connect the phone to the PC, and allow the PC debug access before installing xposed, so i could see the phone in ADB mode, but couldn't access it.
Of course I hadn't made a backup before this - I like to cry
Just as a desperate try, when everything else had failed, i thought about using the new tool provided by shakeyabooti LG UP to flash the factory KDZ all over
I put the phone in SW. update mode by:
1. Turning off the phone
2. connecting USB cable to the PC
3. Press and hold vol. up while connecting the USB cable to the phone
Then i downloaded the v20b KDZ file, provided by Autoprime (since this was what i where allready running)
Opened LG UP, loaded the H81520B_00.kdz, marked REFURBISH
Lastly i pressed "Start" and waited for about 15-20 minutes and "TADAAAA"
The phone where up and running again... only things lost where root and TWRP
- Sharing since I'm properly not the only one ending up in this kind of mess :laugh:
Just tried it no luck :/
So just to confirm...unlocking bootloader official way does void warranty and we can not send it in for repairs?
rakinisbat said:
Just tried it no luck :/
So just to confirm...unlocking bootloader official way does void warranty and we can not send it in for repairs?
Click to expand...
Click to collapse
Indeed. Maybe you'll find a cool employee at your vendor who will still do it, but your warranty is definately void and they don't need to do anything. Depends on how acommodating the employee is. If you're stuck in a bootloop @rakinisbat just follow the steps in this thread.
And please keep in mind that there's a way to get out of bootloops 99% of the time (in fact 100% if it's a software related problem), you just have to do a good search on xda. Furthermore there's an uninstaller app for xposed in the official rovo89 thread, which you can flash via recovery and it which undos the xposed installation and your phone will boot fine (if you can access TWRP - just flash it). If you have further questions you can PM me, always happy to help
Follow_and_Feel said:
Indeed. Maybe you'll find a cool employee at your vendor who will still do it, but your warranty is definately void and they don't need to do anything. Depends on how acommodating the employee is. If you're stuck in a bootloop @rakinisbat just follow the steps in this thread.
And please keep in mind that there's a way to get out of bootloops 99% of the time (in fact 100% if it's a software related problem), you just have to do a good search on xda. Furthermore there's an uninstaller app for xposed in the official rovo89 thread, which you can flash via recovery and it which undos the xposed installation and your phone will boot fine (if you can access TWRP - just flash it). If you have further questions you can PM me, always happy to help
Click to expand...
Click to collapse
Thanks Mate, I guess ill have to try my luck with LG,
I have that batch of H815 with the faulty motherboard, unfortunately I'm in that 1% *Sigh* :crying:
Tried literally everything i could with the software, pretty much confirmed it is the motherboard.
It looks like the KDZ is flashing properly, as LGUP shows whichever kdz i put on, but the actual hardware is not capable of booting into the OS.
rakinisbat said:
Thanks Mate, I guess ill have to try my luck with LG,
I have that batch of H815 with the faulty motherboard, unfortunately I'm in that 1% *Sigh* :crying:
Tried literally everything i could with the software, pretty much confirmed it is the motherboard.
It looks like the KDZ is flashing properly, as LGUP shows whichever kdz i put on, but the actual hardware is not capable of booting into the OS.
Click to expand...
Click to collapse
Ugh, okay that's bad luck. Sorry to hear. If it's a motherboard problem I can't help you unfortunately Sorry for that. What is exactly happening when you try to flash via LGUP? Just curious
Follow_and_Feel said:
Ugh, okay that's bad luck. Sorry to hear. If it's a motherboard problem I can't help you unfortunately Sorry for that. What is exactly happening when you try to flash via LGUP? Just curious
Click to expand...
Click to collapse
It flashed perfectly fine, once completed it reboots and just literally sits on the LG logo.....FOREVER or till the battery dies.
So much disappointment in LG
rakinisbat said:
It flashed perfectly fine, once completed it reboots and just literally sits on the LG logo.....FOREVER or till the battery dies.
So much disappointment in LG
Click to expand...
Click to collapse
Oh yeah that really sounds like a hardware problem. Damn it LG! But is your bootloader still locked? You might have a chance to get a new one if it is And if it's a hardware prob you still have your warranty, haven't you?
Follow_and_Feel said:
Oh yeah that really sounds like a hardware problem. Damn it LG! But is your bootloader still locked? You might have a chance to get a new one if it is And if it's a hardware prob you still have your warranty, haven't you?
Click to expand...
Click to collapse
Nope, my bootloader is unlocked, im a flash-a-holic, longest i have lasted without rooting or unlocking a bootloader is about 2 weeks. I would have never imagined such a massive hardware issue with a flagship phone. I'll probably get a nexus 6P atleast it has better support than a LG. I'm in Australia, I imported this phone when it was released, so i have to send this phone overseas if i want it repaired, which they will most likely deny.
Sooooo over LG now! There are like hundreds if not thousands that are effected they are not even acknowledging it or providing a viable solution.
rakinisbat said:
Nope, my bootloader is unlocked, im a flash-a-holic, longest i have lasted without rooting or unlocking a bootloader is about 2 weeks. I would have never imagined such a massive hardware issue with a flagship phone. I'll probably get a nexus 6P atleast it has better support than a LG. I'm in Australia, I imported this phone when it was released, so i have to send this phone overseas if i want it repaired, which they will most likely deny.
Sooooo over LG now! There are like hundreds if not thousands that are effected they are not even acknowledging it or providing a viable solution.
Click to expand...
Click to collapse
Haha! I can completely subscribe to the flash-a-holic :laugh: Well ok. So it's even worse than i thought Sorry for ya. At least you live on a continent everyone here desires to go to :laugh: Going to Australia is very popular in germany But sorry that you're experiencing trouble with your LG. Good luck with that nexus - it's an awesome phone, too. Bye bye
I've got the bootloop issue. Phone was turning on or not, just vibrating etc. I've dissassembled it, assembled again and it started working don't know why...Now I've flashed CM I was on Genisis ROM earlier maybe that was the issue
zwodziarz said:
I've got the bootloop issue. Phone was turning on or not, just vibrating etc. I've dissassembled it, assembled again and it started working don't know why...Now I've flashed CM I was on Genisis ROM earlier maybe that was the issue
Click to expand...
Click to collapse
Hi sir
I decide to buy lg g4.
If i flash cm ,bootloop not happend again?
Thank you
It doesn't matter what firmware you have got. Bootloop is happening because of hardware failure.
Odesláno z mého LG-H815 pomocí Tapatalk
Just need to know if this is possible and if so what steps to take
Sent from my Pixel XL using Tapatalk
FUZER384 said:
Just need to know if this is possible and if so what steps to take
Click to expand...
Click to collapse
On beta O? I was rooted on beta but I had supersu so Android pay didn't work, but the steps were the same as any other firmware
sakumaxp said:
On beta O? I was rooted on beta but I had supersu so Android pay didn't work, but the steps were the same as any other firmware
Click to expand...
Click to collapse
Yeah Android Pay is a must for me, from researching it it seems like it's possible with Magisk and having 7.1.2 on another slot. I just can't put the right steps together for some reason
Sent from my Pixel XL using Tapatalk
FUZER384 said:
Yeah Android Pay is a must for me, from researching it it seems like it's possible with Magisk and having 7.1.2 on another slot. I just can't put the right steps together for some reason
Click to expand...
Click to collapse
I highly doubt that is possible since you need rc2 to flash magisk and it won't flash if one of your slots has an Android O boot.IMG.
pcriz said:
I highly doubt that is possible since you need rc2 to flash magisk and it won't flash if one of your slots has an Android O boot.IMG.
Click to expand...
Click to collapse
I have RC2 TWRP working fine on mine, problem is I locked my BL as a troubleshooting step and now VZW disabled the OEM unlocking toggle. This is balsy since I have a Google Play Pixel that I'm using on their network. Oh well I might end up just finding a way to buy another GP Pixel since VZW will never loosen their grip on our bootloaders
FUZER384 said:
I have RC2 TWRP working fine on mine, problem is I locked my BL as a troubleshooting step and now VZW disabled the OEM unlocking toggle. This is balsy since I have a Google Play Pixel that I'm using on their network. Oh well I might end up just finding a way to buy another GP Pixel since VZW will never loosen their grip on our bootloaders
Click to expand...
Click to collapse
Could be worse. You couldve bricked it locking your boot loader with modifications...
pcriz said:
Could be worse. You couldve bricked it locking your boot loader with modifications...
Click to expand...
Click to collapse
True
Sent from my Pixel XL using Tapatalk
FUZER384 said:
True
Click to expand...
Click to collapse
Whatever else you might say about the Pixel and how much harder it is to flash on this phone than others it seems to be virtual impossible to hard brick this phone. Any other phone I've ever used you would be screwed now. It sucks that Verizon locked your bootloader even though you have a Google Phone but if you have any flashing experience at all you should have known not to lock your bootloader when you weren't running full stock because on any other phone I know of that would result in an automatic bootloop. You might want to report to Pixel Support that you are having a problem with your phone--overheating and poor battery life are the two most common ones. They will RMA your phone and send you another Google version if that was what you originally bought--you just need to enable OEM unlocking before you accept any updates from Verizon. If you did a factory reset before returning the phone you might end up back on full stock or boot looping the phone--neither of which would really be bad in your case.
jhs39 said:
Whatever else you might say about the Pixel and how much harder it is to flash on this phone than others it seems to be virtual impossible to hard brick this phone. Any other phone I've ever used you would be screwed now. It sucks that Verizon locked your bootloader even though you have a Google Phone but if you have any flashing experience at all you should have known not to lock your bootloader when you weren't running full stock because on any other phone I know of that would result in an automatic bootloop. You might want to report to Pixel Support that you are having a problem with your phone--overheating and poor battery life are the two most common ones. They will RMA your phone and send you another Google version if that was what you originally bought--you just need to enable OEM unlocking before you accept any updates from Verizon. If you did a factory reset before returning the phone you might end up back on full stock or boot looping the phone--neither of which would really be bad in your case.
Click to expand...
Click to collapse
I locked my bootloader ON stock dp3 thinking because I have a GPE it wouldn't matter. For God's sake I got the package from the Google preview site, had nothing to do with Verizon. Big red must've worked something out with Google to allow them to lock the toggle by IMEI. I had not read this in all my research trying to root on dp3
Sent from my Pixel XL using Tapatalk
jhs39 said:
Whatever else you might say about the Pixel and how much harder it is to flash on this phone than others it seems to be virtual impossible to hard brick this phone. Any other phone I've ever used you would be screwed now. It sucks that Verizon locked your bootloader even though you have a Google Phone but if you have any flashing experience at all you should have known not to lock your bootloader when you weren't running full stock because on any other phone I know of that would result in an automatic bootloop. You might want to report to Pixel Support that you are having a problem with your phone--overheating and poor battery life are the two most common ones. They will RMA your phone and send you another Google version if that was what you originally bought--you just need to enable OEM unlocking before you accept any updates from Verizon. If you did a factory reset before returning the phone you might end up back on full stock or boot looping the phone--neither of which would really be bad in your case.
Click to expand...
Click to collapse
Isn't kind of against the rules to suggest users make false reports to return device?
Not to mention what it makes the user look like if they boot up the device and see what is running on it.
Smart thing to do first would be to side load an ota, or attempt to.
Inform them you purchased the one you purchased because you could unlock and youre not happy with the condition of the device.
This narrative may be helpful because it puts op down a path that may get him a true GPE device.
Seems that I have just the opposite with you. I deadly want my XL 8.0 OPP3 to be UNLOCKED......
Has anyone released a modified stock kernel for O Preview that bypasses unlocked bootloader checks? I don't care about root but I like my bootloader unlocked, still want Netflix and Android Pay though.
I have a brand new sealed Samsung S9 SM-G960F/DS which is most probably Exynos variant however I couldn't find OEM Unlock after activating the developer tools. I've googled that and was surprised that this is a recent Samsung policy and as mentioned by most users they've waited more than 7 days to see OEM Unlock so they can root the device. Any one was able to find an alternative or workaround solution instead of waiting 7 days since I don't have that much time to wait I need to root urgently before a birthday.
Your help much appreciated.
Nope, wait the 7 days
My G960F had OEM unlock available on day 1, check in download mode it is the model you think
Flashing Firmware
*Detection* said:
Nope, wait the 7 days
My G960F had OEM unlock available on day 1, check in download mode it is the model you think
Click to expand...
Click to collapse
Do you think flashing a new firmware will show the OEM lock?
c05338 said:
Do you think flashing a new firmware will show the OEM lock?
Click to expand...
Click to collapse
Factory resetting resets the 7 day timer, switching CSCs requires a reset, you'll have to wait it out
*Detection* said:
Factory resetting resets the 7 day timer, switching CSCs requires a reset, you'll have to wait it out
Click to expand...
Click to collapse
I'll wait but actually I don't have much time I should finish it before Monday and today is Saturday so far it's 25 hours up so I'm yet searching for a solution. Anyway to root the device without OEM unlock?
c05338 said:
I'll wait but actually I don't have much time I should finish it before Monday and today is Saturday so far it's 25 hours up so I'm yet searching for a solution. Anyway to root the device without OEM unlock?
Click to expand...
Click to collapse
No solution, read the forums, you cannot root without it, you have to wait no matter how many times you ask
c05338 said:
I have a brand new sealed Samsung S9 SM-G960F/DS which is most probably Exynos variant however I couldn't find OEM Unlock after activating the developer tools. I've googled that and was surprised that this is a recent Samsung policy and as mentioned by most users they've waited more than 7 days to see OEM Unlock so they can root the device. Any one was able to find an alternative or workaround solution instead of waiting 7 days since I don't have that much time to wait I need to root urgently before a birthday.
Your help much appreciated.
Click to expand...
Click to collapse
flash a combination ROM and oem unlock shows since first moment, unlock and flash the normal firmware that you want.
acabreram said:
flash a combination ROM and oem unlock shows since first moment, unlock and flash the normal firmware that you want.
Click to expand...
Click to collapse
Are you sure man? Any wrong stop will cause me issues to reset the time and wait another 7 days and I'm in an urgent time.
c05338 said:
Are you sure man? Any wrong stop will cause me issues to reset the time and wait another 7 days and I'm in an urgent time.
Click to expand...
Click to collapse
http://www.techzai.com/combination-rom-galaxy-devices/
I found this link to download Combination ROM does it fit?
c05338 said:
http://www.techzai.com/combination-rom-galaxy-devices/
I found this link to download Combination ROM does it fit?
Click to expand...
Click to collapse
A member tested the combination ROM theory yesterday for the same purpose and it bootlooped their phone
The combination ROM will allow you to "OEM unlock" your device, but the RMM prenormal state will prevent you from flashing anything custom. I tried this when I first got my S9.
You need to wait the 7 days on stock in order to be able to actually bootloader unlock your device. Make sure to keep a SIM card in, connect a Samsung and Google account, and don't power it off. There is no workaround for this.
*Detection* said:
A member tested the combination ROM theory yesterday for the same purpose and it bootlooped their phone
Click to expand...
Click to collapse
that's me LOL
if we can get it to boot up on s9/ plus
then the oem lock thing wouldn't be an issue
TheUndertaker21 said:
that's me LOL
if we can get it to boot up on s9/ plus
then the oem lock thing wouldn't be an issue
Click to expand...
Click to collapse
Wonder if it was because the combination ROM firmware is older than the current on the device
Did it factory reset after the flash? If not that might be causing the bootloop, or if the bootloader version is older on combination
*Detection* said:
Wonder if it was because the combination ROM firmware is older than the current on the device
Did it factory reset after the flash? If not that might be causing the bootloop, or if the bootloader version is older on combination
Click to expand...
Click to collapse
i mean i'm on ARD6 and i don't think there's any combination for this firmware
i flashed the latest combination i found on many times
TheUndertaker21 said:
i mean i'm on ARD6 and i don't think there's any combination for this firmware
i flashed the latest combination i found on many times
Click to expand...
Click to collapse
The way to check the bootloader is here
G960FXXU1BRE5
Version 1
If you boot into Download mode it should say at the bottom BL:1 or whatever version you are currently running, downgrading the BL is usually not possible from what I see lately
*Detection* said:
The way to check the bootloader is here
G960FXXU1BRE5
Version 1
If you boot into Download mode it should say at the bottom BL:1 or whatever version you are currently running, downgrading the BL is usually not possible from what I see lately
Click to expand...
Click to collapse
this is my version
but i flashed this one
COMBINATION_OXM_FA80_G965FXXU1ARB4_OXMFAC
and
COMBINATION_OXM_FA80_G965FXXU1ARB7_OXMFAC_CL13084894_QB17151834
COMBINATION_OXM_FA80_G965FXXU1ARC3
Bootloader version 1 for both yours and the comb'n firmware so doesn't seem to be that
Did you factory reset after flashing combination? That's the only thing I can think of that would cause the loop if you didn't
*Detection* said:
Bootloader version 1 for both yours and the comb'n firmware so doesn't seem to be that
Did you factory reset after flashing combination? That's the only thing I can think of that would cause the loop if you didn't
Click to expand...
Click to collapse
yeah i factory reset it after still nada
weird though
i can wait since i have youtube vanced, everything i always used besides titanium
TheUndertaker21 said:
yeah i factory reset it after still nada
weird though
i can wait since i have youtube vanced, everything i always used besides titanium
Click to expand...
Click to collapse
Yea I used Vanced too, much better than the original YT app
I always did full TWRP nandroid backups rather than TiBu, but it's a good app
Not really impressed with the lengths Samsung are going to to prevent us (the phone OWNERS) from doing what we want with OUR own phones tbh
There was a workaround to update system apps with Nougat, literally no harm done to Samsung with us doing that but they still patched it in Oreo
Starting to feel more like an iPhone than an Android, wasn't the whole point of Android that it was basically open and unlocked for us to play with?
Thing is though, Samsung make one of the best android devices available and they know locking it down isn't going to hurt their sales
*Detection* said:
A member tested the combination ROM theory yesterday for the same purpose and it bootlooped their phone
Click to expand...
Click to collapse
I appreciate if you can share his thread maybe he got the wrong ROM that bricked the phone.
This is my question. I'm currently on ATTMX channel, but, my carrier has being saying in lot of forums AT&T México, that we are not being updated to Android Pie, due to end of cycle. I already found that:
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
Is where you can find the update already in Stock format. My Albus is under OPSS27.76-12-25-15-2-4. But that's my question if not, I'm just leaving already the phone, wasn't all that worth it after all, but if I can update it, would be awesome for a second hand move.
Any kind of help, or comment, would be awesome. Thanks.
Vesaniaheim said:
This is my question. I'm currently on ATTMX channel, but, my carrier has being saying in lot of forums AT&T México, that we are not being updated to Android Pie, due to end of cycle. I already found that:
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
Is where you can find the update already in Stock format. My Albus is under OPSS27.76-12-25-15-2-4. But that's my question if not, I'm just leaving already the phone, wasn't all that worth it after all, but if I can update it, would be awesome for a second hand move.
Any kind of help, or comment, would be awesome. Thanks.
Click to expand...
Click to collapse
In theory, it is possible to update.
My device is RETAR channel. And I updated using this file from the RETAIL channel.
Sorry if my English is not good: D
I also have a xt1706 from att mx, i used the method in this post https://forum.xda-developers.com/z2-play/how-to/download-z2-play-pie-ota-t3977367 but i had to install first the stock rom for retail moddel, exactly the ALBUS_RETAIL_8.0.0_OPSS27.76-12-25-23_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip, after that i copied the ota file from the post above to internal storage, searched on my system apps for motorola update services, give it storage permissions, reboot phone and when it booted the OTA appeared, so i just installed the OTA and rebooted, everything is working fine, a lot better than oreo stock or other pie based roms. the only issue i had was with Netflix, i can't install from play store due the phone showing on search for updates that system integrity is at risk.
What i'm trying to do now to solve that is to install the retail version of pie from this https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/ In the past i've installed some retail version from this web and everything worked fine so i hope installing the retail pie stock everything will work fine, speacially with netflix xD maybe i'll root because i need to record calls and none of the record callers are working fine because of the compatibility with pie, the only working method is with root.
I will update this if my attempt to install the retail version of pie and/or rooting is successful
Vesaniaheim said:
This is my question. I'm currently on ATTMX channel, but, my carrier has being saying in lot of forums AT&T México, that we are not being updated to Android Pie, due to end of cycle. I already found that:
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
Is where you can find the update already in Stock format. My Albus is under OPSS27.76-12-25-15-2-4. But that's my question if not, I'm just leaving already the phone, wasn't all that worth it after all, but if I can update it, would be awesome for a second hand move.
Any kind of help, or comment, would be awesome. Thanks.
Click to expand...
Click to collapse
I have the XT1710-06 AMXMX Channel (not the ATTMX) with bootloader unlocked and rooted with Magisk. I upgraded to Pie using the retail version firmware from the page you mention.
1.- First I was on this stock Oreo version for my phone: XT1710-06_ALBUS_AMXMX_8.0.0_OPSS27.76-12-25-15-2-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
2.- Then I installed the retail Oreo ALBUS_RETAIL_8.0.0_OPSS27.76-12-25-23_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip to check if everything was working fine
3.- And finally I installed Pie with this firmware: ALBUS_RETAIL_9.0_PPS29.133-30_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Maybe I could skiped the step 2, I'm not sure.
I had an issue with my SD Card because system said it was damaged and I had to format it like 2 or 3 times. This happened randomly when I restarted the phone. Now all is working fine.
irvingagm said:
What i'm trying to do now to solve that is to install the retail version of pie from this https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/ In the past i've installed some retail version from this web and everything worked fine so i hope installing the retail pie stock everything will work fine, speacially with netflix xD maybe i'll root because i need to record calls and none of the record callers are working fine because of the compatibility with pie, the only working method is with root.
I will update this if my attempt to install the retail version of pie and/or rooting is successful
Click to expand...
Click to collapse
The thing with Netflix will be solved once you rooted your phone with Magisk.
̶Y̶e̶s̶ ̶y̶o̶u̶ ̶c̶a̶n̶,̶ ̶b̶u̶t̶ ̶a̶t̶ ̶l̶e̶a̶s̶t̶ ̶m̶y̶ ̶X̶T̶1̶7̶1̶0̶-̶0̶6̶ ̶h̶a̶s̶ ̶i̶s̶s̶u̶e̶s̶ ̶r̶e̶c̶o̶g̶n̶i̶z̶i̶n̶g̶ ̶t̶h̶e̶ ̶U̶S̶B̶ ̶c̶o̶n̶n̶e̶c̶t̶i̶o̶n̶ ̶o̶n̶ ̶P̶C̶.̶ ̶I̶ ̶h̶a̶v̶e̶ ̶t̶e̶s̶t̶e̶d̶ ̶m̶a̶n̶y̶ ̶c̶u̶s̶t̶o̶m̶ ̶R̶O̶M̶'̶s̶,̶ ̶A̶O̶S̶P̶,̶ ̶A̶E̶X̶,̶ ̶L̶i̶n̶e̶a̶g̶e̶ ̶O̶S̶ ̶f̶o̶r̶ ̶8̶.̶1̶,̶ ̶9̶ ̶a̶n̶d̶ ̶1̶0̶ ̶a̶n̶d̶ ̶e̶v̶e̶r̶y̶ ̶s̶i̶n̶g̶l̶e̶ ̶o̶n̶e̶ ̶o̶f̶ ̶t̶h̶e̶m̶ ̶g̶e̶t̶s̶ ̶t̶h̶e̶ ̶U̶S̶B̶ ̶c̶o̶n̶n̶e̶c̶t̶i̶o̶n̶ ̶w̶o̶r̶k̶i̶n̶g̶ ̶p̶r̶o̶p̶e̶r̶l̶y̶,̶ ̶h̶o̶w̶e̶v̶e̶r̶,̶ ̶a̶l̶s̶o̶ ̶e̶v̶e̶r̶y̶ ̶s̶i̶n̶g̶l̶e̶ ̶o̶n̶e̶ ̶o̶f̶ ̶t̶h̶o̶s̶e̶ ̶c̶u̶s̶t̶o̶m̶ ̶R̶O̶M̶s̶ ̶h̶a̶s̶ ̶i̶s̶s̶u̶e̶s̶ ̶w̶i̶t̶h̶ ̶t̶h̶e̶ ̶S̶p̶e̶a̶k̶e̶r̶s̶,̶ ̶s̶p̶e̶c̶i̶a̶l̶l̶y̶ ̶w̶h̶e̶n̶ ̶t̶h̶e̶r̶e̶ ̶i̶s̶ ̶a̶n̶ ̶o̶n̶g̶o̶i̶n̶g̶ ̶c̶a̶l̶l̶ ̶i̶t̶ ̶d̶i̶s̶t̶o̶r̶t̶s̶ ̶t̶h̶e̶ ̶a̶u̶d̶i̶o̶ ̶s̶o̶ ̶m̶u̶c̶h̶ ̶i̶t̶ ̶i̶s̶ ̶i̶m̶p̶o̶s̶s̶i̶b̶l̶e̶ ̶t̶o̶ ̶u̶s̶e̶ ̶t̶h̶e̶ ̶p̶h̶o̶n̶e̶ ̶d̶a̶i̶l̶y̶ ̶f̶o̶r̶ ̶c̶a̶l̶l̶s̶,̶ ̶w̶h̶i̶c̶h̶ ̶i̶n̶t̶e̶r̶e̶s̶t̶i̶n̶g̶l̶y̶ ̶t̶h̶i̶s̶ ̶i̶s̶s̶u̶e̶ ̶d̶o̶e̶s̶ ̶n̶o̶t̶ ̶h̶a̶p̶p̶e̶n̶ ̶o̶n̶ ̶S̶t̶o̶c̶k̶ ̶R̶O̶M̶.̶ ̶H̶a̶s̶ ̶a̶n̶y̶o̶n̶e̶ ̶h̶a̶d̶ ̶t̶h̶i̶s̶ ̶p̶r̶o̶b̶l̶e̶m̶?̶
EDIT: Actually the USB connection issue is caused by a bad guide that lacks some commands. This guide gets everything right without any issues.
https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-flash-update-stock-rom-t3838213
EDIT2: The audio issue only affects users who have upgraded to Stock Pie. This ROM's modem file causes distortion on audio during calls and must be avoided during the upgrading process. To fix the audio issue simply flash the modem file from Stock Android Oreo.
I'm currently on OPSS27.76-12-25-15-2-4
Can i upgrade directly to PPS29.133-30
Or do i need to flash them one by one (That would be annoying and nonsensical).
Please confirm.
Yes, you can.
AndroidManager said:
I'm currently on OPSS27.76-12-25-15-2-4
Can i upgrade directly to PPS29.133-30
Or do i need to flash them one by one (That would be annoying and nonsensical).
Please confirm.
Click to expand...
Click to collapse
I actually fixed the USB connection issue, it was actually caused by a bad installation (one of those flashing adb guides has missing commands needed for proper USB mode to function properly), this is NOT ROM issue as the missing commands will cause the USB connection to fail whether it is Nougat, Oreo or Pie.
Follow this guide. https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-flash-update-stock-rom-t3838213
But keep in mind one thing.
Avoid flashing the modem file NON-HLOS.bin because it is known the modem file from Stock Pie causes audio issues on Custom ROMs. This will be helpful later if you decide to flash Custom ROMs into it.
Ok. One more thing. My phone model is xt1710-06. That ROM is compatible with it right? Please reply soon, as I'm about to flash it.
leodexe said:
I actually fixed the USB connection issue, it was actually caused by a bad installation (one of those flashing adb guides has missing commands needed for proper USB mode to function properly), this is NOT ROM issue as the missing commands will cause the USB connection to fail whether it is Nougat, Oreo or Pie.
Follow this guide. https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-flash-update-stock-rom-t3838213
But keep in mind one thing.
Avoid flashing the modem file NON-HLOS.bin because it is known the modem file from Stock Pie causes audio issues on Custom ROMs. This will be helpful later if you decide to flash Custom ROMs into it.
Click to expand...
Click to collapse
yes
AndroidManager said:
Ok. One more thing. My phone model is xt1710-06. That ROM is compatible with it right? Please reply soon, as I'm about to flash it.
Click to expand...
Click to collapse
Do you speak spanish by any chance? I also have that model and that one comes from Spanish Providers for Latin America. I had some issues earlier because of some inaccuracies and other stuff I wasn't aware like the modem thing from Stock Android 9 distorting audio during calls. Now I got everything working properly and flashed Custom ROM AEX (you need Treble TWRP to flash custom ROMs) with working audio without problems.
I tried the internal storage method, but nothing happened. Then i tried the ADB method, which also failed (invalid signature). I'm gonna try to update to OPSS27.76-12-25-23 first, if that works, then I'll attempt to upgrade to PPS29.133-30 again.
In any case, it's very annoying. Let's hope it works though.
Once I'm done with that, I have to waste more time on rooting it, then enabling Camera2 API & Wireless display...
I tried the internal storage method, but nothing happened. Then i tried the ADB method, which also failed (invalid signature). I'm gonna try to update to OPSS27.76-12-25-23 first, if that works, then I'll attempt to upgrade to PPS29.133-30 again.
In any case, it's very annoying. Let's hope it works though.
Once I'm done with that, I have to waste more time on rooting it, then enabling Camera2 API & Wireless display...
Are you using fastboot or mfastboot? And you are using up to date adb?
Didn't work. Invalid signature again. :/
Screw this. I'm gonna unlock bootloader, then root the phone, then flash Pie ROM through RSDlite. If even that fails, then screw Pie. I'll stay on Oreo.
AndroidManager said:
I tried the internal storage method, but nothing happened.
Click to expand...
Click to collapse
Sometimes this method works, sometimes may not work.
AndroidManager said:
Then i tried the ADB method, which also failed (invalid signature). I'm gonna try to update to OPSS27.76-12-25-23 first, if that works, then I'll attempt to upgrade to PPS29.133-30 again.
Click to expand...
Click to collapse
You need bootloader unlocked for this process.
felipecassiors said:
Your bootloader must be unlocked.
Click to expand...
Click to collapse
JulioCeesarC said:
I recomend bootloader unlocked for this process
Click to expand...
Click to collapse
HTCDevil said:
Bootloader unlocked but without root
Click to expand...
Click to collapse
RSDLite didn't work either. It was not able to detect my device at all, so i couldn't proceed flashing this way.
Then i followed this video: https://www.youtube.com/watch?v=n57v9r2jysw
It's basically the same as the ADB method, except he extracts the ZIP file & uses individual commands to flash all items. I tried his method, and it worked wonders. I'm on Pie ROM now, it's all good.
AndroidManager said:
RSDLite didn't work either. It was not able to detect my device at all, so i couldn't proceed flashing this way.
Click to expand...
Click to collapse
RSD Lite isn't recommended as it can screw up your basebands getting a phone with no signal whatsoever. The standard ADB fastboot is recommended over everything else.
AndroidManager said:
Then i followed this video: https://www.youtube.com/watch?v=n57v9r2jysw
Click to expand...
Click to collapse
In 1:30 of the video, the following commands are missing:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
Without these commands, the USB and MTP Mode of the phone will never work. This is true for the XT-1710-06, and probably true for all other variants. Besides, it will do a heavier installation, meaning it will install all the OEM stuff that will eat space, resources and you will not probably use anyways.
AndroidManager said:
It's basically the same as the ADB method, except he extracts the ZIP file & uses individual commands to flash all items. I tried his method, and it worked wonders. I'm on Pie ROM now, it's all good.
Click to expand...
Click to collapse
Yes, it is, in fact, it is the exact same method as the standard ADB fastboot flash, because you need to extract the zip file anyways. But this video is mostly based on @JulioCeesarC's guide, which specifically lacks these three commands which are needed for a proper correct installation.
A better guide for flashing/updating Z2P to Pie 9.0 is this one: https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-flash-update-stock-rom-t3838213
The first statement in this guide is that YOUR BOOTLOADER must be unlocked for this process. This will become useful later if something goes wrong. As a locked bootloader can render the phone completely bricked if something goes wrong during the process. You were so LUCKY because your locked bootloader refused to flash the update. Otherwise you could end with a dead unrecoverable phone.
However, all of these guides in XDA forgets another important REQUIRED step:
If you upgrade to Stock Pie, and you decide to flash a Custom ROM later, you will have audio issues during calls. This is caused by the Stock Pie's faulty modem file (NON-HLOS.bin), the good thing is that the Stock Oreo's modem file works flawlessly and must be skipped during the upgrading/flashing process.
If you wanted a Spanish guide, then all you had to do is just ask for one. There might be more spanish users that don't quite understand english very well and might mess up with this trivial process. I will make a Spanish guide to help them and avoid more conflicts and unwanted bricks. I know all this through proper testing with trial and error.
Hey. I just tried plugging USB, and it is working fine. Even File transfer mode is working fine... I have not noticed any issues so far. So I'm gonna keep it as is without reflashing the ROM with those additional commands. If i encounter an issue later, i will consider your suggestion.
BTW, Now i am running Pie & have an unlocked bootloader. Please tell me the proper way to root the phone. I tried rooting before with TWRP & Magisk, but the phone went to bootloop. I then had to reflash the Pie ROM with ADB method to get it working again. I think the problem has to do with DM-Integrity & Encryption, but I've already wasted hours getting Pie to run on it, and don't want to waste more hours trying to root it. So a quick and easy working guide would be useful.
Also, i don't intend to install any custom ROMs on it. I just have to root it so i can enable Camera2 API (disabled on my variant), and enable wifi display (disabled by default on most AOSP based ROMs, including mine).
BTW, I don't understand spanish. I was looking for guides and found that video. I enabled english subtitles & understood enough to give it a shot. I have some experience with flashing & rooting in the past, so i can understand these concepts and methods.
Well, i followed this thread: https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
And was able to root my phone without bootlooping. All is well for now. Now i will enable Wifi Display & Camera2 API. Once those are done. I'll have peace at last.
---------- Post added at 01:47 AM ---------- Previous post was at 01:27 AM ----------
Just successfully enabled wireless display (persist.debug.wfd.enable=1) & camera2 API (persist.camera.HAL3.enabled=1) within build.prop
Both are working as intended. I have succeeded in doing everything i desired to do. It only took a bunch of hours & a headache...
But thanks a lot to "leodexe" for helping me out. You're cool, friend!
AndroidManager said:
Hey. I just tried plugging USB, and it is working fine. Even File transfer mode is working fine... I have not noticed any issues so far. So I'm gonna keep it as is without reflashing the ROM with those additional commands. If i encounter an issue later, i will consider your suggestion.
Click to expand...
Click to collapse
Oh, mine is XT1710-06 and it had issues with the USB mode, I figured out it was because of the missing OEM commands, I tested several times flashing without these and the USB connection would never work, after a simple flash with all the commands it started to work again, so if yours worked without these then maybe it's a thing of luck. But keep in mind that without the OEM commands there will be more installed stuff, I prefer to include the OEM commands to remove all the bloatware, so the user can decide which thing to install later.
AndroidManager said:
BTW, I don't understand spanish. I was looking for guides and found that video. I enabled english subtitles & understood enough to give it a shot. I have some experience with flashing & rooting in the past, so i can understand these concepts and methods.
Click to expand...
Click to collapse
I am doing a spanish guide anyways, so spanish users can properly do the upgrade process without messing everything.
AndroidManager said:
I have succeeded in doing everything i desired to do. It only took a bunch of hours & a headache...
Click to expand...
Click to collapse
Same feeling bro, it took me a few nights and lots of headaches to get things working after upgrading.
AndroidManager said:
But thanks a lot to "leodexe" for helping me out. You're cool, friend!
Click to expand...
Click to collapse
Hey, thanks, no problem, the first time I arrived at this forum I had no clue how to do most things, so I'm here to help anyone whenever I can. Keep up the good work!
I rooted my a325m by patching the stock AP file with magisk, had to use FRP hijacker by hagard to be able to flash the patched file. I root uninstalled several apps for debloating. The phone worked fine for like a couple of weeks, and now, suddenly I find there's the no SIM indication, and in settings -> about phone it says IMEI: unknown, and in software information it says bandbase version: unknown.
The firmware version I used was exactly the same as when I bought it, A325MUBU2AUJ4, with the right csc (ARO in my case).
EDIT: after a couple reboots, the bandbase version now shows, but still no IMEI or SIM detected.
Can anyone help me? What happened? What can I do? Thanks in advance!
flash all the with odin the correct rom. the twrp unstable and more like shell and who knows what bugs have magisk. until why have a good recovery i would no root my phone reallly if you want to unisstall the software from samsung and google i would say to use the universal debload https://github.com/0x192/universal-android-debloater.
UPDATE: it got unknown baseband againI
I relocked the bootloader and now in download mode I have an option to "show barcodes" pressing the side button. The barcodes show the right IMEI and serial number. Maybe stuff wasn't erased, just inaccesible by the rom?
I was told by a technician to flash the original ROM (already did) then root again. Tried several versions but not an older bandbase because downgrade is forbidden by the bootloader, apparently, to no avail. Would try a newer baseband but i'm afraid it will not work and will be unable to go back to the origial baseband version.
Weird thing is, there is the EFS directory but no /data/nvram or /dev/nvram
Same happened to me.
I tried everything I could think of to get the IMEI back and couldn't.
It was still under warranty and I took it to Samsung.
Before taking it I unrooted it and locked it again.
They fixed it for me with no problem.
edukardo said:
Same happened to me.
I tried everything I could think of to get the IMEI back and couldn't.
It was still under warranty and I took it to Samsung.
Before taking it I unrooted it and locked it again.
They fixed it for me with no problem.
Click to expand...
Click to collapse
How did you root it?
as I understand, after rooting, warranty is void since it implies flashing a magisk patched boot image or AP tar. In my case I was indeed able to relock the bootloader and flash the original firmware but upon entering download mode, it shows "warranty void 0x01".
was it the same in your case?
Flashed original firmware, relocked phone, and then went to Samsung Office. I had no problem with it
edukardo said:
Flashed original firmware, relocked phone, and then went to Samsung Office. I had no problem with it
Click to expand...
Click to collapse
most likely the warranty vod bit was on (you can check it yoursef by entering odin mode) and they didn't notice
so you got it fixed for free?
did they mention what did the fix consist in? I heard they say they change the motherboard, which is a lie, they just write the nvram or efs with the right stuff
ah sos de argentina? lol where did you take it? to a samsung store? I'm from neuquen and got it at musimundo, but here's a samgung store too
myself i was thinking of waiting for an update which should be soon, lock bootloader, flash some official rom and pull off the cable so it gives an upgrade error and doesn't enter download mode, then take it to the store
Unroot before update and unlock
wipe the cache partition . then reset the phone using recovery mode . this is at you own risk .
did you fix it?
applesucksLmao said:
did you fix it?
Click to expand...
Click to collapse
nope, went to samsung, got rejected cause warranty bit on, no choice but take it to a service and I suppose they could do something with Chimera Tool, Z3X or something like that, which, as I've seen, claims to fix it in minutes (and the client gets charged handsomely, like 100 USD)
From Samsung I got the same bullsh*t I read in some threads: "this phone has been tampered with and it's a hardware problem, the board must be replaced"
For the technically savvy, I got a strange Magisk log which kind of looks like it may be the problem. It seems to try to "unlock"* some devices on bootup but gets "permission denied". One of them may be the nvram or something like that. I have an EFS directory but no NVRAM directory anywhere or /dev/nvram.
very strange, i guess we gotta not use magisk until its bug fixed.. i have seen other people have the same problem too, but anyways, i sent my phone to get probably JTagged for 54 us dollars, if they fix it well, great right, but if they dont i guess ill have to buy another motherboard from samsung or go to another city... and the best part is that while my phone is there, im using an S4 mini from 2013 with custom android 11 rom hehe
i saw that auh firmware causes empty imei in another thread and to flash aug, maybe you could try this? https://forum.xda-developers.com/t/has-anyone-successfully-rooted-this-a32-4g.4326193/post-85788523
applesucksLmao said:
very strange, i guess we gotta not use magisk until its bug fixed.. i have seen other people have the same problem too, but anyways, i sent my phone to get probably JTagged for 54 us dollars, if they fix it well, great right, but if they dont i guess ill have to buy another motherboard from samsung or go to another city... and the best part is that while my phone is there, im using an S4 mini from 2013 with custom android 11 rom hehe
Click to expand...
Click to collapse
or atleast use magisk with aug or even older firmware if you can... is your a32 A325M or A325F?
well, your firmware is A325MUB"U2"AUJ4 and that means u cant downgrade to older versions that have binary1 so maybe you could try using samsung's new version which was released past month
applesucksLmao said:
very strange, i guess we gotta not use magisk until its bug fixed.. i have seen other people have the same problem too, but anyways, i sent my phone to get probably JTagged for 54 us dollars, if they fix it well, great right, but if they dont i guess ill have to buy another motherboard from samsung or go to another city... and the best part is that while my phone is there, im using an S4 mini from 2013 with custom android 11 rom hehe
Click to expand...
Click to collapse
what's JTagged?
applesucksLmao said:
i saw that auh firmware causes empty imei in another thread and to flash aug, maybe you could try this? https://forum.xda-developers.com/t/has-anyone-successfully-rooted-this-a32-4g.4326193/post-85788523
Click to expand...
Click to collapse
I found it impossible to downgrade, download mode doesn't allow it. Couldn't find a tutorial to do it either.
applesucksLmao said:
well, your firmware is A325MUB"U2"AUJ4 and that means u cant downgrade to older versions that have binary1 so maybe you could try using samsung's new version which was released past month
Click to expand...
Click to collapse
I did, I tried all combinations rooting/unrooting with the new magisk 24.1 the new version, A325MUBS2AVA1
It's a 325m btw