I update my phone when it asked me to update it, no problems right?
But I ended up having problems like other people were having recently, a Bootloop. I was able to fix that(but I ended up losing all my data), but now that I made it back to OS11, it is now showing an update named: HD1901_11_F.17 . Did Oneplus accidentally push the wrong update to some people phones, causing them to get stuck? It seems like this might be the case to me. Can anyone else check it out?
Is it possible that the 1901 software is supposed to be compatible with 1905?(though that does not make sense to me) I have seen other people saying that they have seen it instead be 1901 instead of 1905.
apepi41 said:
I update my phone when it asked me to update it, no problems right?
But I ended up having problems like other people were having recently, a Bootloop. I was able to fix that(but I ended up losing all my data), but now that I made it back to OS11, it is now showing an update named: HD1901_11_F.17 . Did Oneplus accidentally push the wrong update to some people phones, causing them to get stuck? It seems like this might be the case to me. Can anyone else check it out?
Is it possible that the 1901 software is supposed to be compatible with 1905?(though that does not make sense to me) I have seen other people saying that they have seen it instead be 1901 instead of 1905.
Click to expand...
Click to collapse
Nope, OnePlus was too lazy to make one for Global so they used hd1901 update for hd1905. Most people have no prob with this but some have issues like you
nope i got that update and its working on my device.but mine was a 1907 when updated went to 1901 as well. i dont mind as i plan to eventually flash a custom rom to it.
Related
Hey guys,
Does anyone know how we can get the rollback number on our devices? I was reading this thread here:
http://forum.xda-developers.com/g4/...wngrade-g4-t3197675/post62748057#post62748057
I guess you need to know your rollback number to do a KDZ becasue there is a chance of a hard brick. I tried the numbers highlighted below but it didn't work for Verizon. Anyone know how we could get this information?
waylo said:
This was not written anywhere specifically on the LG G4 forums that I could find. But every flash-addict needs to be warned. It is something you want to know before you continue tinkering.
Several users (myself included) have made the unfortunate mistake of attempting to downgrade their bootstack (for various reasons) to a former version.
DO NOT DO THIS (at least for the USA T-Mobile H811 version, and possibly other USA versions, per @autoprime)! It will result in a hard brick! Specifically, this results in the "Qualcomm QDLoader HS-USB port ( 9008 )" error. Connecting your phone to a PC will pop up with this active connection, but nothing else. There is no download mode. There is no publicly available fix as of yet.
This WILL happen both through KDZ restore as well as flashing bootstack .zips.
Yes, an official KDZ image can BRICK your USA phone, if you try to rollback.
This is in stark contrast to other manufacturers (i.e. Samsung), where the attempt to flash an older bootloader/modem/radio will simply fail, but your phone is not bricked.
I have conferred with @autoprime, who confirmed that with each OTA firmware release (on T-Mobile it was 10H, and now 10N), the version # increments. Flashing a lower version # will result in brick.
I have searched far and wide for a DIY fix. Without the proper firmwares in the right format, as well as the right flashing software, your phone is done and must be sent in for LG repair.
To check what antiroll-back version you are on, input this sequence in the dialer (T-Mobile and ATT) and scroll down:
*#*#244773825625#*#*
Flashing a bootstack version less than this # (through KDZ or zip) will brick the phone. You are free to flash anything equal or higher than the version listed.
Click to expand...
Click to collapse
sefirosu0522 said:
Hey guys,
Does anyone know how we can get the rollback number on our devices? I was reading this thread here:
http://forum.xda-developers.com/g4/...wngrade-g4-t3197675/post62748057#post62748057
I guess you need to know your rollback number to do a KDZ becasue there is a chance of a hard brick. I tried the numbers highlighted below but it didn't work for Verizon. Anyone know how we could get this information?
Click to expand...
Click to collapse
If you are still on the original software version 10b, then you have v0. If you took the OTA (or flashed the KDZ) to 11a, then you have v1.
We have a new OTA out now, 12a. I'm not sure what version that one is, but I'm willing to bet it is v2, and you will not be able to rollback if you install it.
laurasaurisrex said:
If you are still on the original software version 10b, then you have v0. If you took the OTA (or flashed the KDZ) to 11a, then you have v1.
We have a new OTA out now, 12a. I'm not sure what version that one is, but I'm willing to bet it is v2, and you will not be able to rollback if you install it.
Click to expand...
Click to collapse
Yeah right now I'm stuck with 11A and I'm not sure what I should do. Even though my phone sucks the way it runs, I'm gonna hang in there and wait a couple weeks. See what comes out of 12A.
Well I don't believe there is a way to check or there is a known way of finding it yet. Apparently there is an APK app that reads it. Perhaps we can rip it from another rom and access the APK via the same method we do for accessing the Themes (using a launcher to do custom shortcuts).
The inability to KDZ back to original software is ridiculous. Just like 12A and the broken notifications. How stupid is it to force broken updates yet make it impossible to go back to previous backup/software. I am half tempted to just take the 12A update and force Verizon to give me another phone just to emphasize my dislike for their method of locking the system down.
Two family members got this phone to start off their contract a couple of years ago. Recently they started having issues with sending and receiving text messages. After going into AT&T stores for help and calling support, they've been told the following...
The problems are being caused by an update from AT&T (the phones are running Android 5.0)
The issue is being caused by an HTC hardware failure and these are problem phones.
These comments from AT&T reps tell me that either they don't know for sure what the actual cause is, or that AT&T's recent update doesn't interact with some hardware on this device. I suspect the latter. Is anyone else with stock device having problems like this? (I know there might not be many with a stock device here but... thought I'd ask)
Did anyone try a factory reset?
Or try re-installing the ROM by getting the RUU from the HTC website. 4.28.502.2 is the latest for AT&T I think, since they haven't released MM yet.
murtaza02 said:
Did anyone try a factory reset?
Or try re-installing the ROM by getting the RUU from the HTC website. 4.28.502.2 is the latest for AT&T I think, since they haven't released MM yet.
Click to expand...
Click to collapse
I agree with both of the above suggestions. OTA updates will sometimes cause random issue related to migrating user data, which may be solved by factory reset.
Otherwise, RUU to full stock image will likely fix the problem.
If the problem started immediately after the update, I highly doubt its a hardware problem.
Hi there Guys. GoodDay. I just wanna ask. I recently bought Nexus 5x. And i see nougat is ready for update. But before that Ive found out on internet that some users that updated from MM to Nougat got stuck on bootloop and seems they cant figured it out i dont know if its model related(h791/h798). Google Employee says hardware. Here 's a qoute of a report. from androidauthority website.
"We’ve been hearing an increasing number of reports from Nexus 5X owners about bootloop issues after upgrading to Android 7.0 Nougat.
Many folks have been claiming that, after installing the Android 7.0 Nougat OTA, their Nexus 5X devices would unexpectedly crash and begin to randomly reboot after a few hours, or even days, of use. Some users say downgrading to Android 6.0 Marshmallow does the trick, while others say reflashing the Android 7.0 Nougat September update fixes the problem. Most people, unfortunately, have yet to find a good fix for the problem.
So if you run into this issue, what should you do?
Orrin, a Google employee, had this to say in the Nexus Help Forums:
We understand that a very small number of users are experiencing a bootloop issue on the Nexus 5X. We are continuing to investigate the situation, but can confirm that this is strictly a hardware related issue. For those of you that are currently experiencing this, please contact your place of purchase for warranty or repair options.
We’re sorry for the inconvenience and appreciate your continued patience."
Im afraid that if i update via OTA just like them. chances it might or might not happen to me. and if did, can a tool like Wugfresh' NRT save it? or should i root and manually update to nougat via some toolkit or manually, is it safer? Thank You very much for your suggestions.
BtW: im on
LG H791 Android 6.0
Build MDA89E
Security Patch Oct.1,2015
ryuhagaming said:
Hi there Guys. GoodDay. I just wanna ask. I recently bought Nexus 5x. And i see nougat is ready for update. But before that Ive found out on internet that some users that updated from MM to Nougat got stuck on bootloop and seems they cant figured it out i dont know if its model related(h791/h798). Google Employee says hardware. Here 's a qoute of a report. from androidauthority website.
"We’ve been hearing an increasing number of reports from Nexus 5X owners about bootloop issues after upgrading to Android 7.0 Nougat.
Many folks have been claiming that, after installing the Android 7.0 Nougat OTA, their Nexus 5X devices would unexpectedly crash and begin to randomly reboot after a few hours, or even days, of use. Some users say downgrading to Android 6.0 Marshmallow does the trick, while others say reflashing the Android 7.0 Nougat September update fixes the problem. Most people, unfortunately, have yet to find a good fix for the problem.
So if you run into this issue, what should you do?
Orrin, a Google employee, had this to say in the Nexus Help Forums:
We understand that a very small number of users are experiencing a bootloop issue on the Nexus 5X. We are continuing to investigate the situation, but can confirm that this is strictly a hardware related issue. For those of you that are currently experiencing this, please contact your place of purchase for warranty or repair options.
We’re sorry for the inconvenience and appreciate your continued patience."
Im afraid that if i update via OTA just like them. chances it might or might not happen to me. and if did, can a tool like Wugfresh' NRT save it? or should i root and manually update to nougat via some toolkit or manually, is it safer? Thank You very much for your suggestions.
BtW: im on
LG H791 Android 6.0
Build MDA89E
Security Patch Oct.1,2015
Click to expand...
Click to collapse
Wouldn't you rather it boot loop now then later when it's no longer covered under warranty?
Boot loop is a hardware issue that becomes exposed during the install process. You gain nothing by waiting and the same thing could be triggered every time the device is rebooted.
Sent from my Nexus 5X using XDA-Developers mobile app
Did you update? I'm in the exact same situation, afraid to update because I just got my phone from amazon and it's running Marshmallow...same model as yours. H791 I don't know if I even have a warranty for it
I suggest you update because it is possible that you might not have that hardware issue, I bought mine a month back and hadn't read any forums or anywhere online about the bootloop. I updated right when I got the phone to android 7.0 xD and my phone has been fine since.
sickofusernames said:
Did you update? I'm in the exact same situation, afraid to update because I just got my phone from amazon and it's running Marshmallow...same model as yours. H791 I don't know if I even have a warranty for it
Click to expand...
Click to collapse
Yeah, ive managed to successfully update it to nougat including the latest build 7.0.1. i think there is just some certain phone that are affected. just see to it that your bootloader is unlock before you update. just in case, you can still go to your recovery.
X3NOM said:
I suggest you update because it is possible that you might not have that hardware issue, I bought mine a month back and hadn't read any forums or anywhere online about the bootloop. I updated right when I got the phone to android 7.0 xD and my phone has been fine since.
Click to expand...
Click to collapse
wow. that's nice :good:
ryuhagaming said:
Yeah, ive managed to successfully update it to nougat including the latest build 7.0.1. i think there is just some certain phone that are affected. just see to it that your bootloader is unlock before you update. just in case, you can still go to your recovery.
Click to expand...
Click to collapse
Thanks for the reply, it gave me the courage to just do it! So far so good, no issues
Please,Don't upgrade you device firmware
Similar problem arose like before with initial global releases of Samsung ..
After suspending the update roll out but still some devices are receiving the update with a small code error and unable to communicate properly with PCB results in
Bootloop unable to fix this issue
Though this issue is resulting to a small niche of users
Developer recommend those few users can wait till some official notification is released
Or Users can try manually downgrading SYSTEM
(Keep nand backup since HOME CSC won't work due to encryption except you can restore data later after device is successfully reset)
Direct Link to Stock SM-705G (official only for units manufactured in India)
https://dl2018.sammobile.com/NV9ZRi...ERdVg../A705GMDDU5ATA1_A705GMODM5ATA1_INS.zip
Instruction to Odin Flash (in case)
https://www.sammobile.com/samsung/galaxy-a70/firmware/SM-A705GM/INS/download/A705GMDDU5ATA1/312540/
We already know this
Bugz1 said:
We already know this
Click to expand...
Click to collapse
I knew about this since previous update and this April security patch really f**ked bad
Fair Warning ...
P.S data lost
Abish4i said:
Please,Don't upgrade you device firmware
Similar problem arose like before with initial global releases of Samsung ..
After suspending the update roll out but still some devices are receiving the update with a small code error and unable to communicate properly with PCB results in
Bootloop unable to fix this issue
Though this issue is resulting to a small niche of users
Developer recommend those few users can wait till some official notification is released
Or Users can try manually downgrading SYSTEM
(Keep nand backup since HOME CSC won't work due to encryption except you can restore data later after device is successfully reset)
Direct Link to Stock SM-705G (official only for units manufactured in India)
https://dl2018.sammobile.com/NV9ZRi...ERdVg../A705GMDDU5ATA1_A705GMODM5ATA1_INS.zip
Instruction to Odin Flash (in case)
https://www.sammobile.com/samsung/galaxy-a70/firmware/SM-A705GM/INS/download/A705GMDDU5ATA1/312540/
Click to expand...
Click to collapse
This has already been fixed, updating to stock Android 10. The first release had the battery issue and was hard bricking the a70, samsung suspended the update and rolled out a new fixed android 10 update. Alls good now.
MarvinMod said:
This has already been fixed, updating to stock Android 10, samsung suspended.
Click to expand...
Click to collapse
I am talking abt the update one somewhere around 26-04
it was supposed to be the one with patch but that update corrupted itself ...:good:
[/COLOR]
Abish4i said:
I am talking abt the update one somewhere around 26-04
it was supposed to be the one with patch but that update corrupted itself ...:good:
Click to expand...
Click to collapse
Im saying, the issue with pcb is fixed. Try downloading the update now and flash. Fyi, you cant downgrade from 10 to 9 once you have updated to 10. Samsungs efuse will be triggered. It's been said that a device affected with the PCB bug is hardbricked, however, that is not entirely true.
MarvinMod said:
[/COLOR]
Im saying, the issue with pcb is fixed. however, that is not entirely true.
Click to expand...
Click to collapse
This was for people who might have bricked their devices and are looking for a workaround to successfully fix bootloop boot (same happened to me)
Since due to lookdown a lot of us can't visit customer support for same.
FYI officially you can downgrade without breaking efuse
Abish4i said:
This was for people who might have bricked their devices and are looking for a workaround to successfully fix bootloop boot (same happened to me)
Since due to lookdown a lot of us can't visit customer support for same.
FYI officially you can downloadgrade without breaking efuse
Click to expand...
Click to collapse
Efuse is popped during an update not a downgrade. Idk if ota pops it but i know updating with odin sure does and no, once the efuse is provisioned, there is no going back. If you or anyone else has found a way besides opening the device and making jumpers, please explain or provide links.
Device never went to 10 since the update with 10 has this error to ppl can still switch back to 9 hassle-free.
Thx for heads up!
Overall, Android 10 upgrade was a big disappointment for me, and pushed towards rooting it first, and then to installing LineageOS 17.1.
So, after rooting I disabled auto updates as I knew things can go bad.
But now I'm lucky LOS user!
I flashed my A705MN using Odin to get around the bootloop and it worked but now my wifi and bluetooth doesn't turn on. -_- I'm kinda new at this flashing business. How can I activate them both again?
MarvinMod said:
This has already been fixed, updating to stock Android 10. Alls good now.
Click to expand...
Click to collapse
Not good yet ;
I did some research with certified service centres this problem can't be fixed with software though it can be fixed with as a manual upgradation of PCB board is required
Ultrachamo said:
I flashed my A705MN using Odin to get around kinda new at this flashing business. How can I activate them both again?
Click to expand...
Click to collapse
If still error do following
Are you sure abt manufacturing unit place of origin is India it's fine ... Still if you used HOMECSC and it worked
you need to format it first thing in
If not manufactured in India Search for country origin specific file ... for odin flash
Why does this count as "development"?
DroidGTV said:
Why does this count as "development"?
Click to expand...
Click to collapse
Idk maybe it cuz the bug is related to PCB bridge code error in software which might be fixed with either downgrading FW ver or Hardware upgradation...
Hi all, I notice that the global variant (AA) does not get full flashable updates, this could pose a problem for those of us who mess around with kernels root etc, I know of the update to inactive and keep root through OTA, but if something were to go wrong having the fallback to flash the latest full ROM seems like a good plan. Is it safe to switch to say, the indian version or EU version?
(This came about as I was on bluspark kernel which modifies the vendor_boot, and I needed to flash the vendor_boot from the .4.4 build)
Sorry if this is a dumb question, I'm coming back into the world of ROM flashing and modification after having used a Note 20 and then an iphone for the last few years.
You can switch from AA to BA (and back) without any issues. Mine was originally on AA/Global and I've been using BA/EU the last couple of versions for exactly the same reason. I read somewhere that there are a couple of minor differences due to GDPL, but otherwise they're identical. Not sure about DA/India version.
Thank you! That's excellent information. Might swap over to BA. I was able to push the vendor_boot without any effects right now, but who knows when the OTA comes for it lol
The EU version works on the Global AA version.
I switched because I want to be able to have a full download since I run Magisk and Gravity Box.
I also did this on my 7 Pro with no bad effects. There is some licensing and defaults that might need to be set but, I can't tell any functional difference between AA and BA firmware.
terlynn4 said:
You can switch from AA to BA (and back) without any issues. Mine was originally on AA/Global and I've been using BA/EU the last couple of versions for exactly the same reason. I read somewhere that there are a couple of minor differences due to GDPL, but otherwise they're identical. Not sure about DA/India version.
Click to expand...
Click to collapse
so I can simply flash 11.2.6.6 EU while on 11.2.4.4 AA and have no issues? (it should be noted that I did apply 11.2.6.6 incremental update following the standard guide but for some reason my system still reports 11.2.4.4)
it's so frustrating waiting for a full update on AA that I'm thinking of doing this. I'm on Verizon and wanted to make sure it would not cause problems first.
thirtythr33 said:
so I can simply flash 11.2.6.6 EU while on 11.2.4.4 AA and have no issues? (it should be noted that I did apply 11.2.6.6 incremental update following the standard guide but for some reason my system still reports 11.2.4.4)
it's so frustrating waiting for a full update on AA that I'm thinking of doing this. I'm on Verizon and wanted to make sure it would not cause problems first.
Click to expand...
Click to collapse
I haven't had any issues. I actually was on 11.2.7.7AA and used twrp to flash the zip for 11.2.6.6BA in both slots and regain my custom kernel and root. Been running for 2 days without issues. There's some weird anomalies that occur like it asking for a default search engine, but that was a one pop up kind of thing (Normally it should let you pick but when I clicked mine it just kinda went away)
thirtythr33 said:
so I can simply flash 11.2.6.6 EU while on 11.2.4.4 AA and have no issues? (it should be noted that I did apply 11.2.6.6 incremental update following the standard guide but for some reason my system still reports 11.2.4.4)
it's so frustrating waiting for a full update on AA that I'm thinking of doing this. I'm on Verizon and wanted to make sure it would not cause problems first.
Click to expand...
Click to collapse
Yes, that's exactly what I did except one version earlier. I was on 11.2.4.4 AA and got tired of waiting for a full update, so I downloaded 11.2.5.5 BA and installed via settings/local update. Now that twrp is out you could use that if you prefer.
Haunt3r said:
There's some weird anomalies that occur like it asking for a default search engine, but that was a one pop up kind of thing (Normally it should let you pick but when I clicked mine it just kinda went away)
Click to expand...
Click to collapse
Weird, I don't remember encountering that.