• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

which & how custom android OS rom version (7.1 to 12.1) virtually pre load/test adoptable storage

@Hadron bro I mean to ask that the twrp recovery image should be installed on mobile device permanently or it can work by loading virtually through fastboot recovery twrprecoveey.img . I have already took the backup from twrp backup menu after loading it through fastboot recovery twrprecovery.img and backup is done successfully I think hopefully the bootloader is not locked but still as backup is reading from rom and copying writing to a image file hopefully it don't need write permission but the recovery menu is a process of writing flashing to the rom and need writing permission privillages .. so for unlocking bootloader which command should be u
Fastboot OEM unlock
Fastboot flashing unlock

So the main question is can I recover write back to ROM back from the backup images taken by twrp backup menu through virtually loading (fastboot recovery twrprecvery.img) not installing or I would have to install the recovery image on to device itself permanentally
I don't know a "fastboot recovery" command myself. There is "fastboot flash recovery <recovery image>" to flash the recovery image to the recovery partition, i.e. permanently install it, and "fastboot boot recovery <recovery image>" to boot the phone once into the recovery without installing it.

Anyway if you've managed to take the backup by just booting into recovery without installing it permanently there's no reason you can't restore it the same way. In fact not all phones allow you to boot into a recovery that hasn't been installed - I even once owned a phone where you could do that on the original firmware but a later update removed the option - but if that works then it should make no difference whether the recovery is permanently installed or not (other than needing a computer if it is not installed).

Bootloader unlocking is separate from recovery. If you can fastboot boot into a custom recovery then as long as you are using the recovery I don't think it will matter whether the bootloader is unlocked or not. But if you want to install a custom recovery via fastboot, or use fastboot to flash anything other than the manufacturer's signed firmware images, then you do need to unlock the bootloader.

Whether you use "fastboot oem unlock" or "fastboot flashing unlock" depends on what device you have. "fastboot flashing unlock" is newer, so if this device is on 5.1 my guess would be "oem unlock". Either way beware, as that will probably factory reset the phone, so make sure you have backups first (and files on the device do not count as backups).

How to turn off 'service provder ntwk not available. Emergency calls only'

So my work area there is no internet connection. We installed wifi so internet is good but my phone keeps popping up 'service provider ntwk not available. Emergency calls only' notification like every 10 seconds and its really annoying me. I tried bunch of times messing with network settings to turn it off but none of them worked. Anyone know how to fix this? Please and thank you.
sooooo your work has internet or not? i'm confused by your first sentence. if you have wifi, you should have internet. do you mean that your work has bad cellular coverage?

like @Unforgiven has said, have you tried setting up wifi calling? i would also talk to your carrier as well and see what they say.

Software update after new malware

It's usually called 'Responsible disclosure' The discoverer of the flaw/bug/security weakness tells the company, with the caveat that they'll make it public if the problem is not fixed within a given time-frame (usually 90 days, but may be shorter if the problem is known to be currently exploited 'in the wild'). If you kn ow the problems CVE number, you can check on it at https://www.cvedetails.com/

Please can you help JavaDoc generation failed error only on Bitrise

Hello Devs!
I'm calling for help all Android build experts as this issue on bitrise with gradle-runner step is not letting me sleep well since Monday.

The issue seems to be with react-native-screens which is used by react-navigation v2.18.3 (the newest from 2.x.x). I have added a screenshot as well as an attached file. screenshot. Please can give me some ideas what to try next. Here's what I've tried:

  • upgrading gradle-runner step in bitrise from currently used 1.8.5 to 2.0.0
  • upgrading react-native-screens to the most recent ver
  • deleting react-native-screens lib
  • downgrading current react-native-screens ver (2.0.0-alpha.11) to the one specified in package-lock.json for react-navigation dependencies to 1.0.0-alpha.11
When running react-native run-android, it all works fine locally. Also, ./gradlew assembleRelease is successful. iOS builds fine

Attachments

  • error.png
    error.png
    1.9 MB · Views: 171

Filter

Back
Top Bottom