yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S7 Edge Questions and Answers] cvaloros:
Hi,

My main phone just bricked, and I have an S7 Edge from ATT (model 935A) on standby. However, my old phone was running 8.1 Oreo, so all my google backups require 8.1 or higher in order to restore. Alas, the highest the 935A upgrades go is 8.0, and from what I can tell they will not upgrade it to 8.1 or 9.0.

Thus, I started looking at rooting and installing 8.1 myself. Lineage or really anything that is stable and usefull. However, apparently using that 935A ATT model prevents a lot of my potential options.

Does anyone have an idea how I could do this? Seems like an option might be to flash a 935U firmware and try going from there? Or is there some different way to get my google info restored onto the 'new' phone?

Many thanks

Chris
[Xiaomi Mi A2 Lite Guides, News, & Discussion] underdoq:
"HMD Global has announced the rollout of Android 10 for the Nokia 8.1, making it the first Nokia smartphone to get a stable build of the latest version of Android."

https://m.gsmarena.com/nokia_8_1_android_10_update-news-39549.php

Is this good news for any Android One phone, or Android One project, or is it a matter of manufacturers that build the phones, maybe this could have good effect on development of Android 10 for A2 Lite ?
[Xiaomi Mi A2 Lite Guides, News, & Discussion] marstonpear:
Nokia always gave timely updates to their devices, this matter doesn't really have any effect on other androidone devices. Nokia also adds other features to their phones (they're all androidone afaik), like round ui, pixel blue accent color and cam2api. As far as updates go, xiaomi isn't that good with their androidone phones, so don't get your hopes up and get frustrated afterwards. I would love to have Android 10 soon but, I know it's not gonna happen. Cheers.
[Xiaomi Mi A2 Lite Guides, News, & Discussion] loop4444:
its strictly related to nokia, this. the fact that they will push it sooner then xiaomi means nothing to us. it all depends on Xiaomi when they will start working for it, and when will they release... nokia is known for being faster to update then xiaomi thats for sure. so just sit and wait :)

...or, you could install unofficial android 10, there is a good GSI version here on xda which works fairly well.
[Xiaomi Mi A2 Lite Guides, News, & Discussion] thorin0815:
My brother is using a Nokia 7 plus and I had Android 9 weeks before him and even with security updates Nokia isn't faster all the time compared to Xiaomi.
[Xiaomi Mi A2 Lite Guides, News, & Discussion] cadenarcher:
I've never managed to get any kind of custom rom working through TWRP because of the kinstalldeviceopenerror.
[Xiaomi Mi A2 Lite Guides, News, & Discussion] marstonpear:
Okay let me ask this, do you consider the Pie update we got as stable? Because I still think that we never got a stable build of Pie from Xiaomi. I can't even update to September update because it breaks the digitizer for me and I can't even use the screen properly. I have no idea how stable is Nokia's version of Pie but maybe you can enlighten us about that.
[Xiaomi Mi A2 Lite Guides, News, & Discussion] thorin0815:
In my eyes our Android Pie is very stable. I never had to reboot my device due to system instability bugs. The worst one I ever had was the screen rotate flash bug. My battery backup after one year of usage is still superb, usually I get 7 hours of screentime within 5-6 days of usage. Most reported bugs appear to be on devices which had installed custom firmware and messed up vendor partitions.

The only thing I dislike on this device is the low headphone sound volume while using a European Union display language. I'm just using U.S. English to fix that.

I don't know about bugs in Nokia phones, my brother never told me about anything special and I can't check his phone because he's in England and I'm in Germany.
[Xiaomi Mi A2 Lite Guides, News, & Discussion] thorin0815:
Nothing official, but I think q1/2020 would be a good guess.
[Xiaomi Mi A2 Lite Guides, News, & Discussion] xbs:
Last year Mi A1 got the Android 9 update on the 23rd of december.

My guess is Mi A2 Lite will get Android 10 in late december.
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] mrmazak:
Update for new year.

1-1-2020 Uploaded a version of twrp for Bold-N1 with working touchscreen.

thanks to the help of [MENTION=4182033]vineethrp[/MENTION] in This Post

Original thread hidden, since twrp build is fixed.

This initial version of TWRP, still has major issue. A second issue with the recovery is the screen will not turn on for about 30 seconds after boot. A time that lines up with the screen sleep timer. The touchscreen is not working. This has been a kernel issue on other devices that I am aware of.

The kernel source for th BOLD-N1 is released, and I have been reading through it. To no avail. I can't find the section that is checking for recovery mode.

For the time being, I have confirmed this version is working with the adb command line operations.

Partial list of functions found Here https://twrp.me/faq/openrecoveryscript.html

I have used the "install" and "sideload" operations.

In most cases (mods etc) sideload should be ok to try.

For the mod I was interested in (DM-Verity-No-Forceencrypt). The install does not support being done in sideload.

Because in the install script used, it checks the zip file name. Based on the file name it enables/disables options of the script.

Sideload changes the *.zip name, so more steps were necessary.

In the following steps, the device /data partition will be formatted. This will erase all your stored data, and more importantly,

it will remove the encryption.

The following steps require you to have already unlocked bootloader.

And,

As a reminder, whenever you modify your phone, you should

NEVER

relock the bootloader

INSTALL the attached TWRP img. Use Fastboot to install it.

fastboot flash recovery **insert-file-path-&name-here**
fastboot oem reboot-recovery

STEPS USED TO FLASH Disable_Dm-Verity_ForceEncrypt

Download zip file from developers XDA page HERE

adb shell twrp wipe data
adb shell reboot recovery
adb push Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip /sdcard/Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip
adb shell twrp install /sdcard/Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip

STEPS USED TO SIDELOAD MAGISK

Download from Developers GitHub repo HERE

I had trouble with the newest V20. Stay on tested version V19.2, unless you can troubleshoot problems on your own.

adb shell twrp sideload
adb sideload C:\Users\(your user name HERE)\Downloads\Magisk-v19.2.zip

Device tree used

https://github.com/mrmazakblu/Bold-N1_minimum_device

Kernel source

https://github.com/mrmazakblu/Bold-N1-Kernel.git

Released twrp folder on android file host HERE

Stock recovery image HERE

.
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] mrmazak:
Call for help

[MENTION=2472806]vampirefo[/MENTION] ,you had fixed touchscreen issue in recovery on other devices. You also helped me to do the same too. If you find some time , could you try point me in some direction.
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] greeneyez15o:
No luck with decrypting here :(

Tried to backup stock recovery with no luck. Do u have a copy ?
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] mrmazak:
How did you try to backup stock recovery?

Yes do have stock images loaded on filehost as well. I will add a link in the OP.

Let's try and figure out why you had trouble decrypt.

Start by flashing that twtp image to recovery. Boot I to the twrp then follow the steps I listed
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] greeneyez15o:
Not sure, but now Im bootlooping to twrp :/
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] mrmazak:
do you know if your phone had received the ota update. there was an update made on

Wednesday, 16-Oct-19 03:27:28 UTC not sure when it was released, though.

it is possible, but unconfirmed that this update may have made this bootloop happen. because others have said that the update made them loose there root. Unknown about the unlock status
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] mrmazak:
I am still trying to fix this twrp, as it is still only one I have seen.

I also have a different phone(umidigi F1) with same soc, mt6771.

A Dev made twrp for that device that even works decrypt. [MENTION=5351691]PeterCxy[/MENTION].

I have forked his build tree. And am trying to copy his success. Unfortunately even though devices have same soc, the encryption method is different enough that the files used to make decrypt work on F1 are not present on N1.

A made a full firmware dump of the N1 at

https://github.com/mrmazakblu/blu_n0030ww_dump
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] mrmazak:
working on porting , then building old Carliv touch recovery. since it can be used with the volume rocker as well as touch.

So far i have it ooting and adb works. Of course with device encrypted , the internal storage is not accessed. but once i get the fsab and vold correctly mapped, it will be ok.

am not posting the port till sdcard is fixed, and can be built from source.
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] ᐯerified Developer:
sounds great man i just oem unlocked the bold n1 how do i go far as rooting wise without the custom recovery. using magisk or do i gotta wait until the carliv recovery is available
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] mrmazak:
Well it's up to you. In this thread I have detailed how I used ADB with twrp to flash first decrypt install package, then magisk. Or you can patch boot.img with magisk manager then flash back to phone with fastboot or sp-flash tool.

Or if you are going to use gsi AOSP, you don't need any of these options.
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] ᐯerified Developer:
Any word on the touch twrp. Im rooted with magisk but need viper4android and cant seem to flash properly without twrp... I tryed all kinds of ways
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] mrmazak:
Did you try either of the 2 ways I explained how to use adb to install zips?

1- adb sideload

2- adb twrp install. Xzxsome-zip-name

But I thought viper4android has not worked on devices higher than marshmallow
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] ᐯerified Developer:
I gotten it to work on my galaxy tab a on Oreo and my galaxy s7 and different varieties of devices. And yes i tryed the command from abd in twrp to install zip.. no success yet. BUT i have a otg from a samsung devices. And am able to use twrp within the mouse and keyboard. So tryna see what my options are as far as installin zips
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] mrmazak:
That's good, lets us know how the otg mouse works out. I did not have one to try it.
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] ᐯerified Developer:
I got viper4android workin .. i downloaded a module called "Magisk SELInux permissive Script" this basically gave me the option to be permissive thats need for viper to work. And busybox but im pretty sure thats already installed from magisk but if not just install busybox. Should be good to go for audio mods?? bout to try dolby now.. let you kno how it goes
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] ᐯerified Developer:
Basically i have the device unencrypted and under magisk settings you wanna uncheck "magisk hide" you will fail safety thing but me personally idc. But anyway follow the above comment along with wat i just said you should have no issues installin viper and dolby. I also recommend a otg for custom recovery. Just easier in my opinion. I basically got device setup how i want and backed it up thru twrp. But any question feel free to ask. More then welcome to help anybody .
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] dml0211:
deleted.
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] mrmazak:
I think you posted in wrong stop. I see you deleted before I got reply. Oh well.

But if you need to know which type of gsi to use on your device. The best bet is to use this app, from play store.

https://play.google.com/store/apps/details?id=tk.hack5.treblecheck
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] vineethrp:
I got to fix the touch issue. After a bit of debugging I figured out that kernel is not able to find the firmware file for goodix:

[ 0.935177] (4)[222:goodix-parse_cf]goodix_i2c 0-005d: Direct firmware load for goodix_cfg_group.bin failed with error -2
[ 0.935177] (5)[1:swapper/0]BOOTPROF: 935.177078:probe: probe=i2c_device_probe drv=goodix_i2c(ffffff80097f7b08) 77.446154ms
[ 0.935191] (5)[1:swapper/0]i2c i2c-0: Failed to register i2c client cap_touch at 0x5d (-16)
[ 0.935191] (4)[222:goodix-parse_cf]goodix_i2c 0-005d: Falling back to user helper
[ 0.935204] (5)[1:swapper/0]i2c i2c-0: of_i2c: Failure registering /i2c@11007000/cap_touch@5d
...
...
[ 2.422885] (7)[222:goodix-parse_cf]goodix_i2c 0-005d: Direct firmware load for goodix_cfg_group.bin failed with error -2
[ 2.422892] (7)[222:goodix-parse_cf]goodix_i2c 0-005d: Falling back to user helper
[ 2.423524] (4)[321:ueventd]ueventd: firmware: loading 'goodix_cfg_group.bin' for '/devices/platform/11007000.i2c/i2c-0/0-005d/firmware/goodix_cfg_group.bin'
[ 2.423633] (4)[321:ueventd]ueventd: firmware: could not find firmware for goodix_cfg_group.bin
[ 2.423664] (4)[321:ueventd]ueventd: loading /devices/platform/11007000.i2c/i2c-0/0-005d/firmware/goodix_cfg_group.bin took 0ms
[ 2.423695] (7)[222:goodix-parse_cf][GTP-ERR][goodix_read_cfg_bin:493] Cfg_bin image [goodix_cfg_group.bin] not available,error:-11, try_times:2

I digged in deeper an figured out that the firmware files are in /vendor/firmware folder and and I extracted it out and put it in

recovery/root/etc/firmware

and touch works as a result.

adb pull /vendor/firmware/goodix_cfg_group.bin

BTW, I have not yet figured out the reason for delayed screen on. I am debugging that and will let you know if I get some leads. I am also not able to get the decrypt working as of now.

Please let me know if you need any more details about how to get the touch working.
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] mrmazak:
Thank you. I added the firmware to the recovery ramdisk and repacked. Just like you said. Now I have touch working. THis may have re-sparked my interest. I have more to work with now. Thanks.

Perhaps twrp is not properly mounting the /vendor and this is why we need to add that bin file to recovery/root. May also be same issue making the screen on time lag. Either way this seems like a big step forward.

I am working on adding the goodix firmware to the device tree I am building with, so will not need to do repacking. I have added the test build with working touch to the file host folder linked in OP
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] vineethrp:
So, I have figured out the issue with lag in screen on. Its a bug in TWRP. The fix is here:

https://github.com/vineethrp/androi...mmit/f15759671df8d389e40a0d378609cc99456a86e5

Issue is that, blanking logic is not pulled in because the required env variables are not exported.

You can make these changes locally and rebuild the recovery image. With the above change, you need to have the following in Boardconfig.mk

TW_NO_SCREEN_BLANK := true

This is required because N1 do not support a blanking ioctl.

Please try this and let me know
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] mrmazak:
I am trying now. But i am thinking i had that line before and didnt help. I will update after build and test. Thanks.

Update:

So when I followed all the instructions, the patch did work to remove the lag. New build is now in file host folder linked in Op
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] vineethrp:
TWRP had a bug. So that line along with the fix I quoted only will fix the issue. Thanks
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] Sergeantslaughter:
this is awesome! thanks so much...but how do i get pas the decrypt data password?

i dont have a screen lock/tried to set one also, either was it wont accept password, times out and denies.....
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] mrmazak:
For now, just press cancel. If you run the decrypt zip, you will have access to the internal. Otherwise only can use sdcard
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] vineethrp:
I've identified the cause for decrypt failing. The decrypt logic is looking for services like servicemanager, hwservicemanager, keymaster etc which is not running. My initial trials to get it running failed. Need more understanding of how these services interact. Learning phase now ;)
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] lobothefoots:
Thank you [MENTION=4182033]vineethrp[/MENTION] for contibuting to the development of this "niche" phone
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] ᐯerified Developer:
So the gsi for android 10 is the only one that works for this phone? Because i tryed countless times installin other gsi arm64bit a/b roms and cant boot into it.. so im anxious to get off this stock rom lol
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] mrmazak:
https://xdaforums.com/bold-n1/how-to/aosp-quack-gsi-t3994409

This only one I have used.
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] inaudible101:
Is this known to disable the finger print sensor? It lights up but when I try to register a fingerprint it doesn't respond to my touches. Sorry if this has been mentioned, but I didn't see it.
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] mrmazak:
I didn't notice. butp am using a gsi aosp room, that the fingerprint doesn't work anyway.
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] ofunrein1:
Hi is any way I can replace the original twrp w/out touchscreen after choosing to update my phone and being forced to boot in twrp. I cannot navigate twrp due to the lack of touch screen. I am trying to replace the twrp, but after selecting the update it force boots into twrp with the "unmodified system partition" message?
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] mrmazak:
Well, yes and no.

There is problem with the situation you describe. You cannot take stock OTA update with custom recovery on phone. It causes a recovery boot loop.

To recover the boot loop, you can follow the directions on the OP and use the adb command line to control twrp, and wipe the "misc" partition.

Or boot to fastboot and flash the working version of twrp. Then use screen to wipe "misc" to stop the boot loop.

My return question for you , is do you have details on the update? I have not been on the stock room, so have no idea what updates may have been released.

I asked around. And found out most recent update was Feb 13, 2020
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] ofunrein1:
Thanks for the guidance. Unfortunately, I wasn't able to see the details of the new update since I could not remove the boot loop. So I was able to install the working custom recovery using ADB commands but was unable to find the misc partition. Then, I assumed flashing the stock recovery would remove the boot loop, but now I'm stuck in another boot loop with the stock recovery. The phone continuously turns off and on w/ the screen flashing yellow, and I am unable to stop it. Is there a way I can get into fastboot mode on the device in order to reflash the working custom recovery? I have been trying different button combinations but none seem to work.
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] mrmazak:
well, cant be sure why it is looping. especially if it is update related. my best opinion is to use the full oem rom package and flash with sp-flash tool.

https://xdaforums.com/showpost.php?p=80876491&postcount=3
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] greeneyez15o:
Twrp is asking me for a password ??*♂️??*♂️??*♂️

Help please
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] mrmazak:
This twrp has no access to /data because encryption. But it asks for password to try and decrypt. It just fails .

Two options are remove force encryption from fstab on your phone. And format /data to clear current encryption.

Or

Just press cancel and only use external sdcard for flashing . Back up and restore of encrypted /data has not been tested.
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] ofunrein1:
Bold N1 Magisk Inquiry

Hey mrmazak,

I have three questions for you. The first one is what is the latest magisk version you've been able to run on the bold n1 device(in regard to the update that patches the boot image)? Secondly, I saw that you've been to get an android 10 GSI running on the n1, have you been able to get the fingerprint working? And if I were to install a GSI on my bold device which one should I use?

Best,

ofunrein1
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] Duantn:
TWRP Bold N1

How to flash TWRP on Bold N1?

I couldn't find anywhere the TWRP recovery file to install on my Blu Bold N1.

Are there any solutions to root this device?

Any help would be great appreciate
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] inaudible101:
Does anyone know how to get the finger print sensor working again? I already tried flashing a stock rom through sp.
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] jdg007:
It's not working on my Android 10 beta for the boat in one I've tried it it's boot looped every time
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] jdg007:
It don't work on Android 10 beta
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] greeneyez15o:
Blu updated to android 10 beta ???
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] jdg007:
I gave up on that I've been trying to get a OST Android chin DSi ROM or system image to work but I keep getting boot loop and I don't understand why I factory reset the phone I've used the splash to to back to stock and I will strike them file but I still get into a boot loop can you please help
[Blu Bold N1 ROMs, Kernels, Recoveries, & Other Dev] greeneyez15o:
https://xdaforums.com/t/restore-factory-package.3993305/

Hey left u a link ur gonna have to go back to complete stock and try flashing gsi again.
[Wing, P4350 ROM development] gabriel713281:
I want it to be kinda like ttran001's Open touch 4CN WWE i have that rom but it has a colorful vista look i dont really like but i want it to have the threaded textmessaging and most of the features on his rom.. I know i sound picky but im really not im just new to this and dont know how to find the right roms please help
[Wing, P4350 ROM development] CuteD34th:
For a supurb all black ROM, I'd suggest ItsPapaBlackDiamon by pappamopps. It doesn't have TFCube or a lot of other programs included in ttran001's ROMs, but just search the forums for the nessecary cabs and install them after you've flashed the ROM.

If you need any help, search the forums (or you can ask me if you like.)

One last thing, I don't think this thread should be in this forum, so a mod will probably move it.

Regards

CuteD34th
[Wing, P4350 ROM development] robpet2:
if u are using ttrans rom you can always change background or theme on it... and find out what today plugins it runs and download new themes for it that are black.
[Galaxy S6 Edge+ Q&A, Help & Troubleshooting] :
[redacted]
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] GedeonTaylor:
I'm asking it because on AliExpress the k20 has chinese rom originally, and the global rom is flashed after unlocked bootloader.

Te 9t has global rom officially.

Which is the better option? If I buy the k20, can I make it a full fledge 9t with working gpay, etc?

I'm asking it because there is a significant price difference between them.