Related
Here is the latest OTA. Verizon says it has security (*cough* Sunshine *cough*) patches. I can confirm that it does not re-lock an unlocked bootloader. It's so minor, they just decided to slap an extra -5 on it.
https://www.androidfilehost.com/?fid=745425885120733909
Do not take this if your bootloader is locked and you'd like to unlock it at some point. If you'd like to unlock it at some point, do it now! What are you waiting for?
You cannot flash this with TWRP.
TheSt33v said:
Do not take this if your bootloader is locked and you'd like to unlock it at some point.
Click to expand...
Click to collapse
There, fixed it for you.
Gotta bold the important stuff.
ChazzMatt said:
There, fixed it for you.
Gotta bold the important stuff.
Click to expand...
Click to collapse
You're inhibiting natural selection.
TheSt33v said:
Here is the latest OTA. Verizon says it has security (*cough* Sunshine *cough*) patches. I can confirm that it does not re-lock an unlocked bootloader. It's so minor, they just decided to slap an extra -5 on it.
https://mega.nz/#!70Zh1BbS!cC_mZ8xouLVwvMlOZLKW2UyC-JXDS7SdnCjxDoafXbI
Do not take this if your bootloader is locked and you'd like to unlock it at some point. If you'd like to unlock it at some point, do it now! What are you waiting for?
You cannot flash this with TWRP.
Click to expand...
Click to collapse
hweew ... new kernel ...
could you upload it?
3Dota said:
hweew ... new kernel ...
could you upload it?
Click to expand...
Click to collapse
TWRP flashable, including kernel, version will be up shortly.
TheSt33v said:
TWRP flashable, including kernel, version will be up shortly.
Click to expand...
Click to collapse
Any modem updates?
koftheworld said:
Any modem updates?
Click to expand...
Click to collapse
Yes. Will also be included in TWRP version.
Yee!
I'm already unlocked on Stock with Stock recovery, and tried taking the OTA, but got an error when it rebooted to install
Sent from my XT1254 using Tapatalk
mustafu said:
I'm already unlocked on Stock with Stock recovery, and tried taking the OTA, but got an error when it rebooted to install
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Have you done any modifications at all? Even in the past? For example, if you were rooted and then unrooted, if any files were left over from that process, the update will fail. If you had xposed and removed it, same deal. Even if you replaced your emoji file with an updated one, that will also cause it to fail. Did you modify build.prop? Fail.
The only way to be sure that it will pass is to reflash MCG24.251-5 with fastboot before taking the OTA. Or you could always do it the easy way and flash MCG24.251-5-5 with TWRP: https://forum.xda-developers.com/droid-turbo/general/rom-mcg24-251-5-5-100-stock-t3565795
I have a "system update paused, waiting for wi-fi" in the status bar. I don't want to take this update - can someone help me remove the notification, and block future updates? I have bl unlocked and rooted...
Tia
I'm running 24.81.5 and just received 24.91.5. Did not install. Unlocked and rooted. If I take this will it fail or cause issues?
Sent from my XT1254 using XDA-Developers Legacy app
g0ndor said:
I have a "system update paused, waiting for wi-fi" in the status bar. I don't want to take this update - can someone help me remove the notification, and block future updates? I have bl unlocked and rooted...
Tia
Click to expand...
Click to collapse
Install titanium backup and freeze the app called Motorola Update Services.
Shtiff1 said:
I'm running 24.81.5 and just received 24.91.5. Did not install. Unlocked and rooted. If I take this will it fail or cause issues?
Sent from my XT1254 using XDA-Developers Legacy app
Click to expand...
Click to collapse
It will fail. Any modifications at all (like root or TWRP, for example) will cause the update to fail.
So I'm guessing it's for "security" issues. So I really don't need to take this, because it involves to much crap... Unrooting, cleaning cache, reflashing, having to do the phone over again, etc.... If that is all true, then how can I get rid of the system update?
g0ndor said:
I have a "system update paused, waiting for wi-fi" in the status bar. I don't want to take this update - can someone help me remove the notification, and block future updates? I have bl unlocked and rooted...
Tia
Click to expand...
Click to collapse
Download "Disable Service" from the play store
TheSt33v said:
It will fail. Any modifications at all (like root or TWRP, for example) will cause the update to fail.
Click to expand...
Click to collapse
I'm not aware of any modifications, I thought I went back to all stock. Recovery says qe 1/1, is it supposed to be 0/1?
Sent from my XT1254 using Tapatalk
mustafu said:
I'm not aware of any modifications, I thought I went back to all stock. Recovery says qe 1/1, is it supposed to be 0/1?
Click to expand...
Click to collapse
If you look at the update script for the OTA, the first two thirds of it are dedicated to checking the system partition (and maybe other partitions. It's a pretty long read and I certainly haven't read all of it) for modifications. If the update is failing, that means it has detected something that does not match what it is checking for. I don't think the qe flag matters, because in the past I'm pretty sure that I've been at 1/1, and after a successful OTA it changes to 0/1.
trial TWRP or temp TWRP custom recovery
trial TWRP or temp TWRP custom recovery
TheSt33v said:
If you look at the update script for the OTA, the first two thirds of it are dedicated to checking the system partition (and maybe other partitions. It's a pretty long read and I certainly haven't read all of it) for modifications. If the update is failing, that means it has detected something that does not match what it is checking for. I don't think the qe flag matters, because in the past I'm pretty sure that I've been at 1/1, and after a successful OTA it changes to 0/1.
Click to expand...
Click to collapse
Don't know if this would help someone install an update like this, but let me throw this out there. There's a way to boot to TWRP custom recovery and use TWRP without installing TWRP. Think of it as "temporary" TWRP.
Thus, you should still be able to flash stuff, including any TWRP-flashable updates, boot logos (to replace the unlocked bootloader warning, SuperSu, etc -- and when you reboot you still have stock recovery.
Now, I don't know why anyone would want to keep stock recovery when TWRP recovery does so much more... But I just recently helped someone with the same suggestion. He wanted to install SuperSu, get root, but keep stock recovery -- for some reason.
Anyway, think of it as "trial TWRP" or "temp TWRP".
I remembered when I made factory images for my Quark, in a variety of states, I used this temporary TWRP trick. I'd almost forgotten about it!
So, seems like you could flash THIS TWRP-flashable version of this update while temporarily booting to TWRP (but not actually installing it), and it wouldn't matter if everything "checked" out or not.
Of course, if you like it, then you can always install it permanently.
For reference, here's the most recent version of TWRP for our phone. (use the one with the most recent post date. @bhb27 updates it fairly often.)
TWRP FOR QUARK
https://www.androidfilehost.com/?w=files&flid=39562
Here's my complete reply:
______
Rahuld107 said:
@ChazzMatt,
Hi, can i root xt1225 using temporary twrp ( one time method). I don't need twrp/custom recovery. Just want root with stock recovery. I am on stock marshmallow, bootloader is unlocked .
Click to expand...
Click to collapse
TEMPORARY TWRP
OK, here's another suggestion. There is a way to boot to TWRP to install SuperSu but NOT install TWRP. You will not be flashing TWRP over stock recovery. You will STILL have stock recovery when you reboot. Think of it as "temporary" TWRP.
Put the TWRP file in your ADB folder and use this command. Your phone will boot to TWRP, but it will not be permanently installed. You can then flash SuperSu while booted into the TWRP interface and then reboot back to your system.
fastboot boot file-name.img (whatever your file name of TWRP is.)
Whereas, the command to permanently install TWRP is this:
fastboot flash recovery file-name.img (whatever your file name of TWRP is.)
___
Back when I first got this phone -- now over two years ago -- I made a bunch of backups in TWRP and posted the images online in various stages -- pure stock, stock + root, stock + root + TWRP. I made the first two with the "temporary" TWRP. People could flash them and already have root without having TWRP installed.
Moto Maxx - Moto Turbo XT1225 factory images (Mexico | Puerto Rico | India | Brazil)
https://forum.xda-developers.com/moto-maxx/development/moto-maxx-moto-turbo-xt1225-factory-t3078274
1) TWRP BACKUPS which I made in various stages, such as
stock, unrooted
stock + rooted
stock + rooted + permanent TWRP
Click to expand...
Click to collapse
See? Even just stock + rooted but with no TWRP. I made that backup with a "temporary" TWRP which did not overwrite the stock recovery.
But they were only for 4.4.4 Kitkat, which came with this phone. After we went to Lollipop, I posted some more images, but just pure factory. Still, the "temporary" TWRP trick is useful.
Is it just me or the Gallery app in 6.0.1 scrolls really slow? Btw i didnt do a clean update from LP in case that could be the reason
Just popped up today. Will it bust my recovery and root?
pwag said:
Just popped up today. Will it bust my recovery and root?
Click to expand...
Click to collapse
Yes it will. Out of curiosity what version do you have?
I've attached a screenshot of my info page.
I tried to install it looks - it broke twrp. I was stuck in a recovery boot loop. It'd boot back up if I went to bootloader first. I flashed back to the stock recovery, then it booted fine. The update didn't stick, but that's okay.
I've not flashed twrp back yet. I'll do it later when I feel like running a new ROM.
It looks like you were getting the 67 update, since you are on 33 now
Karlinski said:
It looks like you were getting the 67 update, since you are on 33 now
Click to expand...
Click to collapse
He was likely getting the 33-5 update. The 67 update seems to be for India only.
I can also confirm that you should not take the OTA update with TWRP installed. It will put you into a recovery boot loop. Obviously nothing that can't be fixed, but don't waste your time trying it.
sic0048 said:
He was likely getting the 33-5 update. The 67 update seems to be for India only.
I can also confirm that you should not take the OTA update with TWRP installed. It will put you into a recovery boot loop. Obviously nothing that can't be fixed, but don't waste your time trying it.
Click to expand...
Click to collapse
How can you update if already rooted with TWRP?
carnivalrejectq said:
How can you update if already rooted with TWRP?
Click to expand...
Click to collapse
I'm not aware of any TWRP flashable zip. I think we are stuck with ADB sideloading the stock firmware. Here are insturctions on how to do that. You can find the 35-5 firmware here.. That site also has the other versions available too (just do a quick search to find them).
sic0048 said:
I'm not aware of any TWRP flashable zip. I think we are stuck with ADB sideloading the stock firmware. Here are insturctions on how to do that. You can find the 35-5 firmware here.. That site also has the other versions available too (just do a quick search to find them).
Click to expand...
Click to collapse
Will I lose root and or TWRP or does side loading keep TWRP? Also I wonder what's new or fixed or different in the update. I don't really care about security patches so I don't even know if it's worth it if I lose TWRP.
So I recently got the LG V20, H91810J specifically, I have a couple of questions:
Q1: If I see a rooting guide for H918, does that work for all H918 variants? (Like the H91810J ?)
Q2: Can I update the phone and still be able to root/install TWRP?
Q3: If I can't update the phone and root/install TWRP, can I update the phone after It's been rooted?
Q4: Anyone have a good guide for rooting/installing TWRP? (Did a search earlier and found mixed results, not sure which would be safest/easiest)
Thanks.
1. Rooting guide only works for firmware up through 10j. 10k can be rolled back to 10j using KDZ tools, but 10p can't because of the anti-rollback.
2. No. If you update to the latest 10p firmware, you're stuck and can't roll back.
3. Yes and no. If you update via OTA, it will wipe out root and custom recovery and you'll be stuck on 10p with no way to go back. Modified versions of the updates that will preserve custom recovery can be downloaded and flashed manually via twrp: https://forum.xda-developers.com/v20/development/rom-10p-debloated-rom-beta-flashable-zip-t3656616
4. https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594/
eric.clay42 said:
1. Rooting guide only works for firmware up through 10j. 10k can be rolled back to 10j using KDZ tools, but 10p can't because of the anti-rollback.
2. No. If you update to the latest 10p firmware, you're stuck and can't roll back.
3. Yes and no. If you update via OTA, it will wipe out root and custom recovery and you'll be stuck on 10p with no way to go back. Modified versions of the updates that will preserve custom recovery can be downloaded and flashed manually via twrp: https://forum.xda-developers.com/v20/development/rom-10p-debloated-rom-beta-flashable-zip-t3656616
4. https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594/
Click to expand...
Click to collapse
Thanks, sometimes I get impatient and I was really tempted to update lol, glad I didn't.
WheresTheDamnSignInButton said:
Thanks, sometimes I get impatient and I was really tempted to update lol, glad I didn't.
Click to expand...
Click to collapse
I'm thinking about rooting my V20 as well. Let me know how it goes for you.
Sent from my LG-H918 using Tapatalk
There is one more catch with updating after TWRP to 10p+. It is currently impossible to use an older firmware on the device. You wouldn't think that's a big deal, unless you end up having a problem that requires a stock restore. Now you have an un-rootable firmware you can't roll back to an older one to root with. If root/AOSP is important to you, don't install 10p.
To be clear, attempting to roll a 10p device back to an older bootloader hard bricks the device at present. The 10p bootloader will not boot older firmware.
Note that you must have root to flash anything other than signed stock firmware. It's not like a Nexus where you can use fastboot to write things without root.
Everything went smoothly, just a couple things to note:
I haven't rooted in a VERY long time (last was the Galaxy Note 3) so I completely forgot that USB debugging needs to be enabled for ADB (The guide didn't specify this, so I spent a good 2 hours trying to figure out the problem)
When I first booted into Recovery, it asked for a password to decrypt the data (Again, the guide didn't specify anything about this screen, so I just hit cancel, everything worked out)
When I went to make a backup, it failed near the end (Reason unknown, perhaps not enough space? Will try again later)
Also anyone know If it's possible to install xposed? I can live without it but It'd be nice to have it.
help me how to root+recovery Lg g5 H83020M
What is anti- roll back version in 20M?
nguyenvantuc said:
help me how to root+recovery Lg g5 H83020M
Click to expand...
Click to collapse
same here..i have tried lg up with uppercut but nothing. i have tried using 20a kdz but i get anti rollback error
i had my lg g3 rooted running fulmics and was hoping to get the dame for my g5 but no....help!!
That's bad news Refrain from updating to 20M and later without a custom recovery for now.
help me!
dksoni411 said:
What is anti- roll back version in 20M?
Click to expand...
Click to collapse
help me how to root + recovery h83020m
I just did it on mine the other day. I didn't realize that having an unlocked bootloader didn't automatically mean fastboot flashing would work, so I upgraded to 20m before I started the unlock and root process.
Starting from 20m, I:
1. Downgraded to 20l using LG UP + Uppercut from Autoprimes thread
2. Booted into android and let it do its thing.
3. I then used Uppercut to downgrade to 20a.
4. After I was on 20a, I had issues in android with items crashing, but no big deal... I was now able to use autorecowvery to install twrp.
5. Once I had twrp, I flashed the complete 20l zip from Autoprimes thread to get back to 20l, wiped data to get rid of the crashing issues, made sure I deleted the "recovery-fromboot.p" file, and then flashed magisk also.
6. Rebooted into a rooted 20l rom and continued on.
I will try then report back,thanks.
jobelaa said:
I will try then report back,thanks.
Click to expand...
Click to collapse
Have you had a chance to try it?
To be honest no, time is against me, but still i cant afford to brick my device right now.. if only he would provide us with a video and step by step.but when or if i do i will post
Deleted
Deleted
da_reeseboy said:
I just did it on mine the other day. I didn't realize that having an unlocked bootloader didn't automatically mean fastboot flashing would work, so I upgraded to 20m before I started the unlock and root process.
Starting from 20m, I:
1. Downgraded to 20l using LG UP + Uppercut from Autoprimes thread
2. Booted into android and let it do its thing.
3. I then used Uppercut to downgrade to 20a.
4. After I was on 20a, I had issues in android with items crashing, but no big deal... I was now able to use autorecowvery to install twrp.
5. Once I had twrp, I flashed the complete 20l zip from Autoprimes thread to get back to 20l, wiped data to get rid of the crashing issues, made sure I deleted the "recovery-fromboot.p" file, and then flashed magisk also.
6. Rebooted into a rooted 20l rom and continued on.
Click to expand...
Click to collapse
Those steps are right to perform the downgrade. If someone is interested in testing the new firmware from tmobile (h83020M), I have created a beta version of my Nimax Rom which has root, xposed and is compatible with asgard kernel.
cesarandres_8911 said:
Those steps are right to perform the downgrade. If someone is interested in testing the new firmware from tmobile (h83020M), I have created a beta version of my Nimax Rom which has root, xposed and is compatible with asgard kernel.
Click to expand...
Click to collapse
Where is your rom?
da_reeseboy said:
Where is your rom?
Click to expand...
Click to collapse
Hello, I'm correcting some details and I could create an independent thread the other week if I have some time.
da_reeseboy said:
I just did it on mine the other day. I didn't realize that having an unlocked bootloader didn't automatically mean fastboot flashing would work, so I upgraded to 20m before I started the unlock and root process.
Starting from 20m, I:
1. Downgraded to 20l using LG UP + Uppercut from Autoprimes thread
2. Booted into android and let it do its thing.
3. I then used Uppercut to downgrade to 20a.
4. After I was on 20a, I had issues in android with items crashing, but no big deal... I was now able to use autorecowvery to install twrp.
5. Once I had twrp, I flashed the complete 20l zip from Autoprimes thread to get back to 20l, wiped data to get rid of the crashing issues, made sure I deleted the "recovery-fromboot.p" file, and then flashed magisk also.
6. Rebooted into a rooted 20l rom and continued on.
Click to expand...
Click to collapse
this works pretty well, i rooted my tmobile g5 with no problems. after you follow the above quote just head to this link and follow as well, but dont use the latest twrp, use twrp 3.0.2..flawless https://forum.xda-developers.com/tmobile-lg-g5/how-to/guide-root-twrp-lg-g5-using-t3580264
da_reeseboy said:
Where is your rom?
Click to expand...
Click to collapse
As I mentioned earlier, a beta is already available:
https://forum.xda-developers.com/lg-g5/development/rom-nimax-rom-1-0-h830-h850-t3710841
I now have H830 20m update zips Here.
I have completely stock Tmobile LG G5 with H83020M. I've avoided letting H83020N install so I can preserve the possibility of rootingby rollling back to 20A.
It's been officially sim-unlocked by Tmobile and I use it with ATT, and that's my question, will I lose that during rollback ? Since the imei is in Tmobile's database now I hope it wouldn't ?
semifast said:
I have completely stock Tmobile LG G5 with H83020M. I've avoided letting H83020N install so I can preserve the possibility of rootingby rollling back to 20A.
It's been officially sim-unlocked by Tmobile and I use it with ATT, and that's my question, will I lose that during rollback ? Since the imei is in Tmobile's database now I hope it wouldn't ?
Click to expand...
Click to collapse
No,u wont lose sim-unlocked status.
The RS988 finally has a new OS update with Google patch level Dec 1st, and that means that we are finally good against blueborne and krack!
Sent from my RS988 using Tapatalk
I just installed it. It's about time. I was beginning to wonder if they had stopped support on the RS988. I hear the LG G5 is supposed to get Oreo, but I have a feeling that the RS988 will get left out based on how the updates have gone so far.
Hi! Has the modem changed?
I rooted my device with SuperSU and TRWP, is it advisable install this update? Won't it remove or disable the root access?
Nispero said:
I rooted my device with SuperSU and TRWP, is it advisable install this update? Won't it remove or disable the root access?
Click to expand...
Click to collapse
From what I know, in order to get the ota your bootloader needs to be the stock one, but I could not find it outside of full kdz packages.
I have not rooted yet waiting for this specific update (given the security fixes).
I would suggest you to backup all of your apps and settings with an app like Titanium Backup, flash stock, install the ota, reinstall TWRP, root and magisk and then restore apps and settings from the backup
Sent from my RS988 using Tapatalk
kattolo said:
From what I know, in order to get the ota your bootloader needs to be the stock one, but I could not find it outside of full kdz packages.
I have not rooted yet waiting for this specific update (given the security fixes).
I would suggest you to backup all of your apps and settings with an app like Titanium Backup, flash stock, install the ota, reinstall TWRP, root and magisk and then restore apps and settings from the backup
Sent from my RS988 using Tapatalk
Click to expand...
Click to collapse
Sorry for asking, but where do I get the flash stock? I loaded SuperSU-v2.82-SR5-20171001224502.zip and TWRP-3.0.2-1-RS988.img to root after unlocking the bootloader
spinoza_web said:
Hi! Has the modem changed?
Click to expand...
Click to collapse
I'm not completely sure (did not write down the previous baseband)
I'm attaching the current info
Nispero said:
Sorry for asking, but where do I get the flash stock? I loaded SuperSU-v2.82-SR5-20171001224502.zip and TWRP-3.0.2-1-RS988.img to root after unlocking the bootloader
Click to expand...
Click to collapse
the best source of full stock roms as well as info on the phone I could find so far is https://forum.xda-developers.com/lg-g5/how-to/info-autos-g5-thread-t3350648
The way I had to update was to flash 21a and then take OTA's up to 21d because when I flashed 21c back to stock using TWRP and tried to update it gave me an error and then rebooted and said I can't update because I had rooted the device.
kattolo said:
I'm not completely sure (did not write down the previous baseband)
I'm attaching the current info
Click to expand...
Click to collapse
Here's the baseband version with RS98821c: MPSS.TH.2.0.c1.4-00047-M8996FAAAANAZM-1.88674.1.101802.1
The numbers are slightly different at the end compared to RS98821d , but I'm not sure what if anything might have changed.
maybe, for getting OTA should we just get unroot? How to do it properly?
If recovery is not the stock one, it will not be possible to install the OTA.
Alternatively you might need to wait for someone to make a flashable zip you could flash with TWRP, but given the fact development on this phone is not too active you might need to wait for a while before is available
Sent from my RS988 using Tapatalk
Awkydee said:
The way I had to update was to flash 21a and then take OTA's up to 21d because when I flashed 21c back to stock using TWRP and tried to update it gave me an error and then rebooted and said I can't update because I had rooted the device.
Click to expand...
Click to collapse
I was also planning on flashing the complete 21c zip so that I could take the 21d OTA. Glad to know that might not work.
Anyone know if it would be possible to install just the stock 21c recovery image? It's my understanding that having a custom recovery installed is what makes the OTA installation fail. If TWRP is what's getting in the way of installing the OTA, wouldn't replacing TWRP with stock recovery solve the problem without touching the system? If anyone who knows more about this stuff than me could chime in, I'd appreciate it.
brewerywagon said:
I was also planning on flashing the complete 21c zip so that I could take the 21d OTA. Glad to know that might not work.
Anyone know if it would be possible to install just the stock 21c recovery image? It's my understanding that having a custom recovery installed is what makes the OTA installation fail. If TWRP is what's getting in the way of installing the OTA, wouldn't replacing TWRP with stock recovery solve the problem without touching the system? If anyone who knows more about this stuff than me could chime in, I'd appreciate it.
Click to expand...
Click to collapse
First I flashed the magisk uninstaller and rebooted back to recovery. Then I flashed the 21c COMPLETE ZIP and didn't flash magisk so it would replace TWRP with the stock recovery on reboot. Then I rebooted and when I tried to update it went to the stock and threw up an error then rebooted. Upon reboot it displayed a message saying that I couldn't update because my device had been rooted. So I rebooted back in to bootloader and flashed TWRP again. Then I flashed 21a COMPLETE ZIP and no magisk so that the stock recovery would replace TWRP. I rebooted and went through setup and took OTA updates until I was on 21d. Then rebooted back into bootloader and flashed TWRP. Then rooted and we've through setup. I tried every other way but this was the only way that worked for me. I hope it helps!
should be an easier way. Did u see some changes to the radio?
Some of you may remember that last year I had the misfortune of installing the Brightpoint ROM on my Unlocked G5, which completely messed the phone up by not allowing it to connect to AT&T's LTE. It was a process to re-flash the older ROMs/Bootloader and then rebuild it to a stable 21c. I had used it for a while like that, and the only problem I had was that when ending a voice call (HSPA) it would take a while to change back to LTE.
I ended up going with the S8 over the summer (Samsung discount + Note 2 trade in) which got it for $18/month. I've been using it ever since and the LTE to HSPA Voice to LTE change-off on the S8 is done within a second, unlike the G5.
My mom had been using an unlocked Samsung S5 for almost a year now, and it's constantly dropping calls, and this past week it froze on her and required a battery pull, so was thinking of having her try out my (unused) G5 to see if she liked it more. When I turned the G5 on today, I updated all the apps, and then installed the 21d OTA update. The hand-off from voice to LTE still is not as fast as my S8, but seems to be improved from the 21c firmware.
ROM Posted
Just to let you all know, I have posted the latest 21d stock ROM in my thread here: https://forum.xda-developers.com/lg-g5/development/stock-21c-roms-flashable-zips-imgs-t3679907
Hi. After 21d received my phone starts to rebbot when I try to play music on phone. No matter if this is stock player or google music. After self reboot music plays normally but if I click pause and wait until first stand by mode, the problem returns. Want to ask you guys to check if you have the same problem or I should download full version of 21d and check if the problem still exists. Thanks.
ingressor said:
Hi. After 21d received my phone starts to rebbot when I try to play music on phone. No matter if this is stock player or google music. After self reboot music plays normally but if I click pause and wait until first stand by mode, the problem returns. Want to ask you guys to check if you have the same problem or I should download full version of 21d and check if the problem still exists. Thanks.
Click to expand...
Click to collapse
I'm not having any reboot issues when playing music.