Develop Bugs

Nougat 7.1.1 is rolling out!

Hey everyone, been a little while, but 7.1.1 N is rolling out to you guys.

Awesome! Is this the same 108 build that went out to beta testers?

Does it include the battery optimization that was mentioned some time ago?

***

New update appears to be uncertified and Android Pay doesn't work.... any way to fix this?

ipowyourface said:
New update appears to be uncertified and Android Pay doesn't work.... any way to fix this?
Click to expand...
Click to collapse
Is your bootloader unlocked?

Nextbit_Khang said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
No, I relocked it after I flashed the image and turned off the oem unlocking option after. I was previously rooted though, but the script on the image should have taken care of that right?

ipowyourface said:
No, I relocked it after I flashed the image and turned off the oem unlocking option after. I was previously rooted though, but the script on the image should have taken care of that right?
Click to expand...
Click to collapse
Yeah that's kinda weird. It should work. I'll ask around.

Nextbit_Khang said:
Yeah that's kinda weird. It should work. I'll ask around.
Click to expand...
Click to collapse
Yeah, there was another person on the Razer forums who had the same problem as well.

Just got my Nextbit today updated few times before work on 7.0 present and update pending hopefully 7.1.1 , How's the update ? any issues fixed not had it long enough to find any
Sent from my Robin using Tapatalk

Nextbit_Khang said:
Yeah that's kinda weird. It should work. I'll ask around.
Click to expand...
Click to collapse
I figured it out, I had just came from Omni Rom. For some reason, I had to flash the 6.0 image then flash the 7.1.1 image and now everything passes, and AP works.

ipowyourface said:
I figured it out, I had just came from Omni Rom. For some reason, I had to flash the 6.0 image then flash the 7.1.1 image and now everything passes, and AP works.
Click to expand...
Click to collapse
You had to re-lock your bootloader also, correct?

Is anybody having issues with sending text messages (your standard text message) with WiFi on? Not over WiFi, but just with WiFi on. I tried the default messaging app and the Google one. They both work the same. For me to get a text message out, I have to turn off WiFi.

I flashed stock N88 and still have TWRP recovery installed I got a system update that updated now stock on nextbit logo on boot , is this coz I still have TWRP recovery or just bad update would factory reset in TWRP fix ? Thanks
Sent from my MotoG3 using Tapatalk

DoobyDroid said:
I flashed stock N88 and still have TWRP recovery installed I got a system update that updated now stock on nextbit logo on boot , is this coz I still have TWRP recovery or just bad update would factory reset in TWRP fix ? Thanks
Click to expand...
Click to collapse
Why don't you flash the latest factory image?
You can't flash an OTA update via custom recovery.

Loving this new update!
However, if you want to save resources and please your customers at the same time when doing the next update -
skip the nextbit bits.
Just make the next updates (if you plan on making any more of course) stock, for all intents and purposes, except perhaps for the backup/cloud feature.

revert back to 7.0 ?
since i updated to 7.1.1, my pebble 2 would constantly disconnect.
how to revert back to plan 7.0 ?
thanks!

Any word on android 8

Franzferdinan51 said:
Any word on android 8
Click to expand...
Click to collapse
Lmao very doubtful

hey there guys i'm having this weird trouble updating to 7.1.1, i'm currently on 7.0 (Robin_Nougat_88) and i have downloaded the 7.1.1 update (560 mb) and when i hit the "reboot and install" button it say restarting in 10 ... 9... 8 blah blah then rebooting now and never get to reboot... i can't install this update is there some solution? do i have to install the N108 image like new following the razer thread? thanks in advice guys have a good day!

Lineage OS on A2 lite?

Is it possibleto flash the Lineage treble rom to mi A2 lite?

I still didn't tried this (I must search for a spare phone to use while experimenting with daisy) but you can precede me, simply reset your phone and flash via fastboot with
Code:
fastboot flash system lineagetreblerom.img
You must use the A/B image type.
If something goes wrong you can flash the stock firmware.

BubuXP said:
I still didn't tried this (I must search for a spare phone to use while experimenting with daisy) but you can precede me, simply reset your phone and flash via fastboot with
Code:
fastboot flash system lineagetreblerom.img
You must use the A/B image type.
If something goes wrong you can flash the stock firmware.
Click to expand...
Click to collapse
As far as i understood treble, it is only the vendor partition which is not flashed. So you would still need a LOS compatible kernel to flash (or you are lucky and the original kernel works). Also, LOS needs to be adjusted for specific things on this phone (like resolution, dpi, options to show up in settings, avaiable ram/storage, etc).
So we have to wait until xiaomi or a proper dev releases a kernel source. It would probably also be possible to adjust the build environment to fit the original kernel.
Or did i understand sth wrong here?
edit:
Flashing GSI's should work, it is a nice way to have another rom with more features on the device, but it is not a homebuilt n optimized rom (probably similar perf/battery to stock).

treble gsi rom don't need the vendor partition that's what makes treble great . you just flash the gsi rom into system on a treble compatible device

Hi
sgi ab images works (does not handle well rounded corners as icons are a bit near corners) but works

lineage booted. I will test and report
Both Lineage and RR boots but they are laggy. Camera quality is quite bad.
Both can be used as daily drivers
*can not handle well rounded corners as max-232 said

BubuXP said:
I still didn't tried this (I must search for a spare phone to use while experimenting with daisy) but you can precede me, simply reset your phone and flash via fastboot with
Code:
fastboot flash system lineagetreblerom.img
You must use the A/B image type.
If something goes wrong you can flash the stock firmware.
Click to expand...
Click to collapse
fastboot erase system
fastboot -u flash system name_of_system.img

The Xiaomi MI A2 Lite stock comes compatible with treble, has it been tested with an image of Androoid 9?

menphis said:
The Xiaomi MI A2 Lite stock comes compatible with treble, has it been tested with an image of Androoid 9?
Click to expand...
Click to collapse
yes, I did before.
it booted, but the sgi I used needs a lot of work, many things didn't work.
but, yes, I confirm, it booted

max-232 said:
yes, I did before.
it booted, but the sgi I used needs a lot of work, many things didn't work.
but, yes, I confirm, it booted
Click to expand...
Click to collapse
What SGI you use?

forum.xda-developers.com/project-treble/trebleenabled-device-development/aosp-9-0-phh-treble-t3831915
This above

max-232 said:
yes, I did before.
it booted, but the sgi I used needs a lot of work, many things didn't work.
but, yes, I confirm, it booted
Click to expand...
Click to collapse
max-232 said:
forum.xda-developers.com/project-treble/trebleenabled-device-development/aosp-9-0-phh-treble-t3831915
This above
Click to expand...
Click to collapse
I recently received my A2 Lite, because you do not test the next one that is more stable, as everything works: https://androidfilehost.com/?fid=5862345805528067642
All the files:
https://androidfilehost.com/?w=files&flid=280192

How can flash these post zips with out twrp?

I really hope we get more going ons here it's dead and i cant stand android one if nothing happens soon im going to sell this phone.

mortmaru said:
I really hope we get more going ons here it's dead and i cant stand android one if nothing happens soon im going to sell this phone.
Click to expand...
Click to collapse
I don't think what happening right now is dead, it is still very active and you can flash Lineage or RR if you want
For a few weeks old phone, i consider this as reasonable

mortmaru said:
I really hope we get more going ons here it's dead and i cant stand android one if nothing happens soon im going to sell this phone.
Click to expand...
Click to collapse
This device is new, barely has a month that went on the market, also comes with factory Oreo, also Android 9 came out a few days ago official ...
What development do you need urgently?

menphis said:
This device is new, barely has a month that went on the market, also comes with factory Oreo, also Android 9 came out a few days ago official ...
What development do you need urgently?
Click to expand...
Click to collapse
Some custom roms the base version is awful it is missing so much you cant even backup all stuff from miui to this even app data doesn't transfer over using googles so called backup
With it being month old i expected modded versions even if it was based on the current andriod one loaded with new look bunch of extra options

Can anyone confirm if on AOSP/LOS systems notification LED od still single color (white only)?

Doman said:
Can anyone confirm if on AOSP/LOS systems notification LED od still single color (white only)?
Click to expand...
Click to collapse
It's impossible to have other colors on mi a2, as the phisical LED is only white, not rgb

Another month passes and still nothing.
Hopefully some one will come up with something soon even the official updates for this phone are really slow

Question anti rollback error flash fastboot stock miui tool global latestest fastboot V13.0.7.0.SKHMIXM | 12.0 (SOLVED)

getting rollback check error tried the Munchy method of deleting the lines in the bat file but it is not working any help would be great

You could try this:
k40 bricked
Guys, I have redmi k40 while moving from chinese rom to global in mi flash tool I locked my bootloader and lost my android and now only fastboot mode. it givinng me Erading not allowed in lock state every time I try to flash any rom and when I...
forum.xda-developers.com

What do you mean it's not working ? What does it say?

Doesn't flash right off the start error anti rollback check failed

jefffrom said:
Doesn't flash right off the start error anti rollback check failed
Click to expand...
Click to collapse
You must've edited the wrong file. Try removing the Anti-Rollback Script from all scripts there.
And check that you use your desired script (clean / clean all lock / update) in Mi Flash, and whatever you use.

jefffrom said:
getting rollback check error tried the Munchy method of deleting the lines in the bat file but it is not working any help would be great
Click to expand...
Click to collapse
weirdly enough, this rollback problem doesnt occur because of 'rollback'
it occurs because of two reasons:
• long path name
• spaces in folder names

3zozHashim said:
weirdly enough, this rollback problem doesnt occur because of 'rollback'
it occurs because of two reasons:
• long path name
• spaces in folder names
Click to expand...
Click to collapse
For real !?

laid1995 said:
For real !?
Click to expand...
Click to collapse
yeah, i fastboot flashed with mi flash tool like a 100 times, im almost confident about that

3zozHashim said:
yeah, i fastboot flashed with mi flash tool like a 100 times, im almost confident about that
Click to expand...
Click to collapse
Going back and forth between different android versions (rollback) ?

laid1995 said:
Going back and forth between different android versions (rollback) ?
Click to expand...
Click to collapse
yeah
i went back and forth a couple of times between miui versions 12.5 and 13
i also went back and forth a couple of times between miui versions 13
i also went back and forth a couple of times between Mi, EEA & Indonesia

3zozHashim said:
yeah
i went back and forth a couple of times between miui versions 12.5 and 13
i also went back and forth a couple of times between miui versions 13
i also went back and forth a couple of times between Mi, EEA & Indonesia
Click to expand...
Click to collapse
That's awesome.
Thanks for the info. Buddy.

cyanGalaxy said:
You must've edited the wrong file. Try removing the Anti-Rollback Script from all scripts there.
And check that you use your desired script (clean / clean all lock / update) in Mi Flash, and whatever you use.
Click to expand...
Click to collapse
Odd I never had this problem with the 1306 never had to edit nothing but what the other guy said about the folder name being to long very well my be it, right now I'm in no desperate need to flash on previous version of Arrow and all is good, just want to have it ready for the next time I get. Board

3zozHashim said:
weirdly enough, this rollback problem doesnt occur because of 'rollback'
it occurs because of two reasons:
• long path name
• spaces in folder names
Click to expand...
Click to collapse
you are correct worked like a charm !

Question The new update made the cellular issue come back again

i accidentally updated to the new android 13 firmware (5.1) its actually the smoothest version of all time.
i have knox tripped but locked bootloader even in this situation it broke the cellular and it stops randomly and it isnt downgradable im just starting to hate this phone

musatbz said:
i accidentally updated to the new android 13 firmware (5.1) its actually the smoothest version of all time.
i have knox tripped but locked bootloader even in this situation it broke the cellular and it stops randomly and it isnt downgradable im just starting to hate this phone
Click to expand...
Click to collapse
uh oh.. i didnt notice that. I switched to crdroid 9.2 immidiately after installing the update. i'll extract system.img from the firmware and see if it is an actual issue here too. i faced it on one ui 4.1 before. Otherwise since downgrade isnt an option, consider switching to a gsi?

Captain_cookie_200 said:
uh oh.. i didnt notice that. I switched to crdroid 9.2 immidiately after installing the update. i'll extract system.img from the firmware and see if it is an actual issue here too. i faced it on one ui 4.1 before. Otherwise since downgrade isnt an option, consider switching to a gsi?
Click to expand...
Click to collapse
just flashed one ui with dsu. tried speedtest on data 4 times. seemed fine. try a fw reflash maybe?

Captain_cookie_200 said:
just flashed one ui with dsu. tried speedtest on data 4 times. seemed fine. try a fw reflash maybe?
Click to expand...
Click to collapse
yeah actually maybe it was because i upgraded from android 12 but im not sure

musatbz said:
i accidentally updated to the new android 13 firmware (5.1) its actually the smoothest version of all time.
i have knox tripped but locked bootloader even in this situation it broke the cellular and it stops randomly and it isnt downgradable im just starting to hate this phone
Click to expand...
Click to collapse
just make a full wipe and done, but make a full backup first

musatbz said:
yeah actually maybe it was because i upgraded from android 12 but im not sure
Click to expand...
Click to collapse
try a fw reflash and lmk how it goes

im wiping rn

Question Touchscreen not working

Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?

persifele said:
Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?
Click to expand...
Click to collapse
Did you contacted the assistance? Seems a bad driver or kernel problem.

zSyntex said:
Did you contacted the assistance? Seems a bad driver or kernel problem.
Click to expand...
Click to collapse
no because i dont know how much it would cost and the phone isnt mine either so if possible i dont want to spend money

persifele said:
no because i dont know how much it would cost and the phone isnt mine either so if possible i dont want to spend money
Click to expand...
Click to collapse
We couldn't provide support for the hardware, mostly because you said that you've tried to reset the device and flash the stock ROM again.
If this doesn't fix the hardware issue, the assistance is the only way.
Probably a failure batch etc.

to be completely honest i flashed the stock rom by a backup i did before flashing lineage os, so if there's a guide on how to flash one ui 5.1 in order to have a clean installation it would be rlly helpful

persifele said:
to be completely honest i flashed the stock rom by a backup i did before flashing lineage os, so if there's a guide on how to flash one ui 5.1 in order to have a clean installation it would be rlly helpful
Click to expand...
Click to collapse
Simply download the latest firmware from SamLoader (Bifrost) and use Odin in order to flash it.
Tell me if you couldn't flash

I tried installing the latest firmware with odin, everything went fine but nothing, touch still doesn't work, i think tomorrow i'll take it to someone to fix it.

persifele said:
Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?
Click to expand...
Click to collapse
what model of a32 is it? SM-A325F or??
One ui 5.1 firmware cannot be downgraded. I currently daily drive crdroid from nazim on one ui 5.1 firmware. my touch has never had issues. May be a hardware issue. Maybe a custom kernel would solve it. I built one for A325F that works on one ui 5.1 firmware. Give it a try from here. Its permissive btw. Just flash it in twrp. Although take a backup of boot before flashing incase something goes wrong

Captain_cookie_200 said:
what model of a32 is it? SM-A325F or??
One ui 5.1 firmware cannot be downgraded. I currently daily drive crdroid from nazim on one ui 5.1 firmware. my touch has never had issues. May be a hardware issue. Maybe a custom kernel would solve it. I built one for A325F that works on one ui 5.1 firmware. Give it a try from here. Its permissive btw. Just flash it in twrp. Although take a backup of boot before flashing incase something goes wrong
Click to expand...
Click to collapse
Hi, I tried to flash from twrp but it just gives me a series of "unable to unlock /dev/block/mmcblk0p14" and so on, btw yes its a A325F.

persifele said:
Hi, I tried to flash from twrp but it just gives me a series of "unable to unlock /dev/block/mmcblk0p14" and so on, btw yes its a A325F.
Click to expand...
Click to collapse
its fine. those are normal. if the flash suceeds at last that is all that matters

Captain_cookie_200 said:
its fine. those are normal. if the flash suceeds at last that is all that matters
Click to expand...
Click to collapse
The problem is that after flashing it goes in a bootloop where it says that "this phone's bootloader is unlocked, press power button" i do it and it starts the galaxy logo with above the writing "the software you are using isnt official, you may have problems with security and features" and it gets stuck there, rn i flashed the original firmware with odin and the phone is working but touch still isn't.
EDIT: i forgot to add that when i flashed with odin everything was going fine until the phone's screen went from green to red, i've never seen this so idk if i should be worried or not (phone is still running normally).

persifele said:
The problem is that after flashing it goes in a bootloop where it says that "this phone's bootloader is unlocked, press power button" i do it and it starts the galaxy logo with above the writing "the software you are using isnt official, you may have problems with security and features" and it gets stuck there, rn i flashed the original firmware with odin and the phone is working but touch still isn't.
EDIT: i forgot to add that when i flashed with odin everything was going fine until the phone's screen went from green to red, i've never seen this so idk if i should be worried or not (phone is still running normally).
Click to expand...
Click to collapse
oh weird . you are using one ui 5.1 right? whats the firmware name or version. Also those things def look like hardware issue. you should get it checked.

Captain_cookie_200 said:
oh weird . you are using one ui 5.1 right? whats the firmware name or version. Also those things def look like hardware issue. you should get it checked.
Click to expand...
Click to collapse
yes i'm on android 13 one ui 5.1, the firmware is A325FXXU3DWB8_A325FOXM3DWB8_ITV. I got it checked and they said that it cant be fixed because i cant downgrade from android 13 to another one, i could try installing crdroid like you and if you could send me a guide it would be amazing, thanks again.

persifele said:
yes i'm on android 13 one ui 5.1, the firmware is A325FXXU3DWB8_A325FOXM3DWB8_ITV. I got it checked and they said that it cant be fixed because i cant downgrade from android 13 to another one, i could try installing crdroid like you and if you could send me a guide it would be amazing, thanks again.
Click to expand...
Click to collapse
Just flash twrp for this thing from here. Follow steps on that thread to decrypt your storage and stuff. Then download crdroid gsi. Extract it. flash img file to system partition in twrp. Afterwards wipe dalvik, cache, internal storage
(internal storage is not necessary). You should be able to boot into twrp sucessfully.
I also have some workarounds and the stuff i use for my daily driving in this thread here.
If you need any further help i'll be here to assist.

Captain_cookie_200 said:
Just flash twrp for this thing from here. Follow steps on that thread to decrypt your storage and stuff. Then download crdroid gsi. Extract it. flash img file to system partition in twrp. Afterwards wipe dalvik, cache, internal storage
(internal storage is not necessary). You should be able to boot into twrp sucessfully.
I also have some workarounds and the stuff i use for my daily driving in this thread here.
If you need any further help i'll be here to assist.
Click to expand...
Click to collapse
Oh um i am sorry looks like thread doesnt contain instructions to that. I'll write em here myself
When you boot into twrp after flashing go to advanced and go to terminal
type
multidisabler
run it two times. Then go to format. Then press format data and type yes. Once its done reboot back into twrp again. Then flash crdroid as i said in my post above. and format the things i said. you should be able to boot into crdroid normally.

Captain_cookie_200 said:
Oh um i am sorry looks like thread doesnt contain instructions to that. I'll write em here myself
When you boot into twrp after flashing go to advanced and go to terminal
type
multidisabler
run it two times. Then go to format. Then press format data and type yes. Once its done reboot back into twrp again. Then flash crdroid as i said in my post above. and format the things i said. you should be able to boot into crdroid normally.
Click to expand...
Click to collapse
I followed everything you said, flashed crdroid but nothing, touch still doesnt work if not for when im twrp, i tried to flash kernel again and it still didn't so i don't know what to do anymore.

persifele said:
I followed everything you said, flashed crdroid but nothing, touch still doesnt work if not for when im twrp, i tried to flash kernel again and it still didn't so i don't know what to do anymore.
Click to expand...
Click to collapse
So uh looks like you have no options left. I just want to make sure. could you list the exact methods you used to flash the fw. Along with where u got the fw from? Lets see if the fw itself is broken or something.
Also this is very unrelated and time wasting. but you could try download one ui 5 firmware. Then extract super.img from ap. unsparse it and extract vendor.img and flash it to vendor partition using twrp. Then decrypt by typing
multidisabler twice in terminal as said in my previous post. Check if maybe an older version one ui 5 firmware has this issue fixed. one ui 5's kernel boots so one ui 5 vendor should work on 5.1 as well. It may not work but worth a try. you could also try doing this with android 12 firmware if that fixes it. if you do not have a linux machine availible i'll do it for you and upload the files for both firmwares here. Otherwise if its a hardware issue get your phone replaced or try getting the screen replaced. if still nothing happens ig switching to a new phone would be the only optiion.

So, to flash the firmware I used odin, the fw was from sammobile.
For trying to extract super.img and so on idk how to actually do it so if you could explain it would be really helpful. Btw trying to flash android 12 firmware is impossible because samsung made it so,
thank you again for the help.

persifele said:
So, to flash the firmware I used odin, the fw was from sammobile.
For trying to extract super.img and so on idk how to actually do it so if you could explain it would be really helpful. Btw trying to flash android 12 firmware is impossible because samsung made it so,
thank you again for the help.
Click to expand...
Click to collapse
i use samfw mostly for my firmwares. anyways. You need a linux machine nearby. ubuntu or arch. any distro based on them would work.
first you need to unsparse the super.img
for that we use
simg2img super.img super-raw.img
then we can use lpunpack or mount it to get our vendor.
we flash it using twrp and then we run multidisabler twice like we did when we first flashed gsi.

As you said above if you could do it for me it'd be awesome because i don't have a pc with linux rn.