Database Info

[Help] Wifi connects but doesn't work

It started when I tried to install a CM11 update. I did not see that was only for KK BL, then I tried to revert to stock rom(using RSD lite) and install the old version for the JB BL again, but my wifi still not working(or working only when it wants lol).
Anyone could help me?
I tried to flash a lot of different roms, even reset with RSD, but the issue stills. I don't know what more I can do
Thx for the att and sorry for my horrible english...

Carcass.br said:
It started when I tried to install a CM11 update. I did not see that was only for KK BL, then I tried to revert to stock rom(using RSD lite) and install the old version for the JB BL again, but my wifi still not working(or working only when it wants lol).
Anyone could help me?
I tried to flash a lot of different roms, even reset with RSD, but the issue stills. I don't know what more I can do
Thx for the att and sorry for my horrible english...
Click to expand...
Click to collapse
im having the same issue... my step dad said there was a patch somewhere but i think its a patch from verizon thats going to be an ota so... we will lose root

derpyherp said:
im having the same issue... my step dad said there was a patch somewhere but i think its a patch from verizon thats going to be an ota so... we will lose root
Click to expand...
Click to collapse
lose root? your bootloader is not unlocked?

ncsuwolfs said:
lose root? your bootloader is not unlocked?
Click to expand...
Click to collapse
I thought you loose root when you take ota's??

derpyherp said:
I thought you loose root when you take ota's??
Click to expand...
Click to collapse
If you are rooted, the OTA will fail, so you have to flash back to stock before taking OTAs.
If you are locked and you take an OTA, you will lose access to whatever exploit was patched. In the case of going from JB to KK, the original root (Saferoot I believe) won't work. However, Towelroot will work for those that have locked bootloaders.
However, if you are rooted and on the latest official KK, then you can unlock your bootloader and then, no matter what OTA comes out after that, you will still be able to root your phone without the use of an exploit like Towelroot. Instead, you take .zip image of the SU app you are using and flash it in TWRP or CWM recovery. No exploit needed.
Towelroot is only for those that don't have an unlocked bootloader and it's an exploit (a security issue) within the specific version of the Android OS. OTAs patch these as they are released, which means another exploit has to be discovered in order to achieve root for locked bootloaders.
So, right now, if you are not unlocked, you better unlock on the initial KK release because the latest soak test does patch Towelroot and the bootloader exploit. You've been warned.

Unable to update from 5.0 to 5.0.1 on stock

I am on stock lollipop 5.0 but flashed 4.4.2 radio on it using fastboot few weeks ago and locked the boot loader back.
I got 5.0.1 update and it downloads ,reboots and starts to install and hangs with a red icon halfway through the install.
Anybody know what I will need to do to update without losing any data or unlocking boot loader?

stivelio said:
I am on stock lollipop 5.0 but flashed 4.4.2 radio on it using fastboot few weeks ago and locked the boot loader back.
I got 5.0.1 update and it downloads ,reboots and starts to install and hangs with a red icon halfway through the install.
Anybody know what I will need to do to update without losing any data or unlocking boot loader?
Click to expand...
Click to collapse
You can`t do anything if you don`t unlock the bootloader and flash the 5.0 radio or flash the 5.0.1 factory image, you can backup your apps and data with Helium.

gee2012 said:
You can`t do anything if you don`t unlock the bootloader and flash the 5.0 radio or flash the 5.0.1 factory image, you can backup your apps and data with Helium.
Click to expand...
Click to collapse
That will be last resort but I was just trying to find out why the update doesn't work for me even though I'm on stock 5.0

stivelio said:
That will be last resort but I was just trying to find out why the update doesn't work for me even though I'm on stock 5.0
Click to expand...
Click to collapse
Your radio is not 5.0 compatible (stock), everythinhg has to be 100% stock and not rooted to be able to install the OTA

And if I unlock bootloader I will lose my data. Right?

stivelio said:
And if I unlock bootloader I will lose my data. Right?
Click to expand...
Click to collapse
Yup, there is no other way though. Backup everything you can before you unlock.
-Edit- You could try to root the device with CF Auto Root, install Bootunlocker from PLay and unlock the Bootloader without loosing data. Then unroot from the superSU app and flash the 5.0. radio, wipe caches in recovery or fastboot erase cache and see if the OTA can be installed
by sideloading it in stock recovery, link to the OTA http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217

gee2012 said:
Yup, there is no other way though. Backup everything you can before you unlock.
Click to expand...
Click to collapse
Ah ok. I guess I will wait until 5.1 or something to do this when there are major updates

update with a rooted Mate 8

I am on rooted stock B331 and I just received an update to B356 (492 MB). If I acceot the OTA will the bootloader get locked? I know I will most likely loose root and twrp. I'd like to updated but not get locked again. Any advice?
Or should I flash the image file in TWRP along with insecure boot?
If anybody has gone this route please advice. Thanks

huh? thats new! here i thought that once u unlock bootloader and root u dont receive ota updates anymore! how is that possible?!
in any case, whats the big deal about bootloader getting locked? u just unlock it again using your code via fastboot, no problem then flash twrp and supersu, done!
Sent from my Huawei Mate 8 NXT-AL10

jbmc83 said:
huh? thats new! here i thought that once u unlock bootloader and root u dont receive ota updates anymore! how is that possible?!
in any case, whats the big deal about bootloader getting locked? u just unlock it again using your code via fastboot, no problem then flash twrp and supersu, done!
Sent from my Huawei Mate 8 NXT-AL10
Click to expand...
Click to collapse
Yeah, I know it is wierd. My bootloader is unlocked, I'm rooted and have twrp installed and received the B356 OTA this morning.
I was hopping to dirty flash so I don't have to go through all the setup process again

true, unlocking BL again would mean that your phone would be reset...
Sent from my Huawei Mate 8 NXT-AL10

You can still do OTA'S with an unlocked bootloader. You should be able to OTA but it may remove root or fail in the process because of root. I always recommend backing up the stock rom in TWRP so you can always go back to it to take an OTA. Fastboot flash the stock rom you're on and the stock recovery then boot up and take the OTA then fastboot flash twrp again.

I have also received the notification for b357 and I am on stock rooted b356...sounds fishy, I am not updating

malekowsky said:
I have also received the notification for b357 and I am on stock rooted b356...sounds fishy, I am not updating
Click to expand...
Click to collapse
I'd love it if anybody could make a flashable zip rooted B356 or 357 rom to be safe.

A9 Back to stock -> question about returning to Android Pay and eventually Nougat

I've a device that is S-ON , TWRP 3.0.2-0 recovery installed , unlocked USA. Was running CM13 and later a lineage build...i just wiped/ reflashed the stock boot and system image so i've got things more or less back to original. All's good. However my bootloader remains unlocked. Do i need to relock it to get Android Pay working again? I was able to add a card, but have not tested it in the real world yet. My understanding is locking the bootloader will erase my data. Given I'd like to try that Nougat flavor and I don't think that will come OTA with an unlocked bootloader, maybe now's the time sense I think i'll have to flash that manually
Sorry, still new to joy of working with these devices. Fun tho

mlecho said:
I've a device that is S-ON , TWRP 3.0.2-0 recovery installed , unlocked USA. Was running CM13 and later a lineage build...i just wiped/ reflashed the stock boot and system image so i've got things more or less back to original. All's good. However my bootloader remains unlocked. Do i need to relock it to get Android Pay working again? I was able to add a card, but have not tested it in the real world yet. My understanding is locking the bootloader will erase my data. Given I'd like to try that Nougat flavor and I don't think that will come OTA with an unlocked bootloader, maybe now's the time sense I think i'll have to flash that manually
Sorry, still new to joy of working with these devices. Fun tho
Click to expand...
Click to collapse
No, if Android pay has a problem, it will reject you DURING the process of adding a card, if you add a card sucussfully, your good to go.
If you want to try nougat, please note that that change is irreversible. The firmware is non-downgradeable. I don't think locking the bootloader will erase data, but if it does it PROBABLY will warn you.

The_scam said:
No, if Android pay has a problem, it will reject you DURING the process of adding a card, if you add a card sucussfully, your good to go.
If you want to try nougat, please note that that change is irreversible. The firmware is non-downgradeable. I don't think locking the bootloader will erase data, but if it does it PROBABLY will warn you.
Click to expand...
Click to collapse
Thanks for all that...just to be clear, the only way to get Nougat is to flash it ? or is it also OTA?

mlecho said:
Thanks for all that...just to be clear, the only way to get Nougat is to flash it ? or is it also OTA?
Click to expand...
Click to collapse
It is an OTA, you can have s-on, but you can't have an unlocked bootloader, root, or system modifications if any kind.

The_scam said:
It is an OTA, you can have s-on, but you can't have an unlocked bootloader, root, or system modifications if any kind.
Click to expand...
Click to collapse
Sorry I have a question, I have an A9 (European model) S-ON with CM 14.1 and I would like to get S-OFF in order to back to stock. The problem is that I have read that Sunshine only works with stock ROM and, out of the box, my phone came with vodafone uk ROM and I can't find, on the internet, the exact same ROM as mine ( I have found an older version but because I have S-ON I can't downgrade ). There is another way to make Sunshine works? Thanks in advance

Lolli26 said:
Sorry I have a question, I have an A9 (European model) S-ON with CM 14.1 and I would like to get S-OFF in order to back to stock. The problem is that I have read that Sunshine only works with stock ROM and, out of the box, my phone came with vodafone uk ROM and I can't find, on the internet, the exact same ROM as mine ( I have found an older version but because I have S-ON I can't downgrade ). There is another way to make Sunshine works? Thanks in advance
Click to expand...
Click to collapse
what is your rom version number/firmware version 1.57?

The_scam said:
what is your rom version number/firmware version 1.57?
Click to expand...
Click to collapse
No my firmware version is 1.62.161.2

Lolli26 said:
No my firmware version is 1.62.161.2
Click to expand...
Click to collapse
i cant find anything either, i guess you'll have to wait until the rom is released.

The_scam said:
It is an OTA, you can have s-on, but you can't have an unlocked bootloader, root, or system modifications if any kind.
Click to expand...
Click to collapse
ahh, so i will need to re-lock if i want this OTA.
And btw, Android Pay worked, just as you said it would!

mlecho said:
ahh, so i will need to re-lock if i want this OTA.
And btw, Android Pay worked, just as you said it would!
Click to expand...
Click to collapse
Good, I think you can download the ota and sideload it, should be in one of the general threads. Think it's called any news on 7.0

So, after all this, i had Android Pay (AP) working great w/ 1.57.617.60 flashed back to my phone. I never re-locked my bootloader. This a.m. i flashed nougat, both boot and system (RUU_HIA_AERO_UL_N70_SENSE80GP_ATT_MR_NA_Gen_Unlock_2.18.617.1) - All's great. However while shopping i was rejected by AP with the message in the attached screen shot. Is this because i never re-locked the bootloader? What are the consequences by doing so? Can I eventually re-unlock for future flashing?
NOTE - my device is not rooted, despite the accusations from the modal!

mlecho said:
So, after all this, i had Android Pay (AP) working great w/ 1.57.617.60 flashed back to my phone. I never re-locked my bootloader. This a.m. i flashed nougat, both boot and system (RUU_HIA_AERO_UL_N70_SENSE80GP_ATT_MR_NA_Gen_Unlock_2.18.617.1) - All's great. However while shopping i was rejected by AP with the message in the attached screen shot. Is this because i never re-locked the bootloader? What are the consequences by doing so? Can I eventually re-unlock for future flashing?
NOTE - my device is not rooted, despite the accusations from the modal!
Click to expand...
Click to collapse
In nougat, it checks for unlocked bootloaders sadly you can't relock bootloader in nougat.

The_scam said:
In nougat, it checks for unlocked bootloaders sadly you can't relock bootloader in nougat.
Click to expand...
Click to collapse
oh no...really? no 'fastboot oem lock'? crap. Perhaps the "upgrade" was a mistake. So i'm without?

mlecho said:
oh no...really? no 'fastboot oem lock'? crap. Perhaps the "upgrade" was a mistake. So i'm without?
Click to expand...
Click to collapse
Yep, looks like it unless you downgrade and relock bootloader, then upgrade back to nougat

MGfusion said:
Yep, looks like it unless you downgrade and relock bootloader, then upgrade back to nougat
Click to expand...
Click to collapse
My goal was keep su and also get nougat. A9 has the bug about OEM unlocking just like all other 7.0 devices. It will most likely get fixed at 7.1.1, the nexuses and all other devices running 7.0 seem to have this "bug"

The_scam said:
My goal was keep su and also get nougat. A9 has the bug about OEM unlocking just like all other 7.0 devices. It will most likely get fixed at 7.1.1, the nexuses and all other devices running 7.0 seem to have this "bug"
Click to expand...
Click to collapse
ahh, so that means, as i understand it, if all goes to plan, we should one day expect a 7.1.1 update that will allow me to finally get back to AP?

mlecho said:
ahh, so that means, as i understand it, if all goes to plan, we should one day expect a 7.1.1 update that will allow me to finally get back to AP?
Click to expand...
Click to collapse
As long as you don't care about root. You can always downgrade to mm, lock, and OTA back to nougat

The_scam said:
As long as you don't care about root. You can always downgrade to mm, lock, and OTA back to nougat
Click to expand...
Click to collapse
ok, but just so i am clear , if i lock while in nougat, there's no going back ? i can not then unlock and downgrade?

mlecho said:
ok, but just so i am clear , if i lock while in nougat, there's no going back ? i can not then unlock and downgrade?
Click to expand...
Click to collapse
No, you can only UNLOCK in nougat. If you want to relock the bootloader, you will have to downgrade to marshmallow and loose your root, or wait for Android 7.1.1

downgrade means i have to wipe data, right? The upgrade that was not the case. I am only assuming

my maxx xt1225 br is hard brick help please!!!

hi guys i'm brasilian and my english is pretty poor but lets try. i was flash 4.4.4 rom br retail. and i update via ota for lollipop.. and brick .. i search in forums here ... and i go it to put in boot loader without robot.. already try many ways to recovery my boot loader but always get error remote failure.. and already used 6.0.1 stock .. maybe i need to files atualy for this? i'm very sad my maxx is dead .. someone give me light .. help me fix this ... thank you guys

Is your bootloader locked or unlocked?

ChazzMatt said:
Is your bootloader locked or unlocked?
Click to expand...
Click to collapse
unlocked

kenedi jr said:
unlocked
Click to expand...
Click to collapse
Good.
What version Android was your phone on before the problem?
Were you on stock (factory) or on custom ROM?
Surely you weren't on Kitkat for almost 3 years?

ChazzMatt said:
Good.
What version Android was your phone on before the problem?
Were you on stock (factory) or on custom ROM?
Surely you weren't on Kitkat for almost 3 years?
Click to expand...
Click to collapse
I was in a custom rom and went to 4.4.4 and tried to upgrade via ota .. and brinck so I was able to make boot loader appear more without the robot

kenedi jr said:
I was in a custom rom and went to 4.4.4 and tried to upgrade via ota .. and brinck so I was able to make boot loader appear more without the robot
Click to expand...
Click to collapse
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?

ChazzMatt said:
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
Click to expand...
Click to collapse
So I'm stuck on the bootloader. If I connect charger or pc it will already pro boot loader without the robot. I have already tried to pass stock 4.4.4 and 6.0 and more etc always from the failure remote failure in bootloader appears in the log something with gt bin downgrade

ChazzMatt said:
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
Click to expand...
Click to collapse
My question is if I crashed from 4.4.4 trying to upgrade to 5.1 which version files do I need to adapt to my bootloader that seems to be corrupted?

kenedi jr said:
My question is if I crashed from 4.4.4 trying to upgrade to 5.1 which version files do I need to adapt to my bootloader that seems to be corrupted?
Click to expand...
Click to collapse
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?

ChazzMatt said:
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
Click to expand...
Click to collapse
Yes before this problem I was in the latest 6.0.1 and the stock I have here when I installed had a security update

ChazzMatt said:
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
Click to expand...
Click to collapse
I do not have twrp backup and I can not even install the recovery stock

kenedi jr said:
Yes before this problem I was in the latest 6.0.1 and the stock I have here when I installed had a security update
Click to expand...
Click to collapse
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.

ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that version to repair. Just reflash the entire full firmware.
Click to expand...
Click to collapse
This is the most likely because all the methods say so old and not one was and when I try to pass any old stock also will not always get that error in the bootloader in the gptbin downgrade logs

ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
Click to expand...
Click to collapse
thanks bro you saved me

kenedi jr said:
This is the most likely because all the methods say so old and not one was and when I try to pass any old stock also will not always get that error in the bootloader in the gptbin downgrade logs
Click to expand...
Click to collapse
You can not flash any older gpt.bin files. You have to omit (leave out) that flash command.
Your gpt.bin file is 6.0.1, and you cannot downgrade. Even on 4.4.4, trying to accept the 5.0.2 OTA update is still older gpt.bin file in that OTA than your 6.0.1.

ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
Click to expand...
Click to collapse
i don't have link .. i will wanting you so

kenedi jr said:
i don't have link .. i will wanting you so
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?p=72846593

ChazzMatt said:
https://forum.xda-developers.com/showthread.php?p=72846593
Click to expand...
Click to collapse
I was a bit confused with this link which is the last one? I discovered because I am Brazilian and my English was developed only by playing

http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/

ChazzMatt said:
http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/
Click to expand...
Click to collapse
Face first you're a myth. I just passed gpt.bin and got the bootloader ... I'm very happy. Do I need to pass the entire rom ??
:good::laugh: