Database Info

[Q] There is error with batteryStats.computeBatteryRealtime on Androi

There is error when we obtain time with batteryStats.computeBatteryRealtime on Android platform.
In our code, we want to get the time with the method batteryStats.computeBatteryRealtime , shown as following:
import android.os.BatteryStats;
void update() {
int statsType = BatteryStats.STATS_SINCE_CHARGED;
...
long realTime = SystemClock.elapsedRealtime();
long uSecTime = batteryStats.computeBatteryRealtime(realTime * 1000, statsType);
...
}
the update method will be invoked every 20 seconds, but, the uSecTime never changed while realTime changing, Why, who can help me ?
thank you very much!
our platform:
--------------------------------------------------------------------
1) Android 2.3
2) Juno Service Release 2
3) Windows 8 64 bit

batteryStats.getBatteryRealtime(realTime) has the same problem
the method batteryStats.getBatteryRealtime(realTime) has the same problem, why?

[G386F] Dual booting from SD card and concept of bypassing secure boot for Core LTE

Dual booting - the idea:
Use of recovery partition to boot second rom ( stock recovery isn't very useful anyway)
How to on post:
http://forum.xda-developers.com/showpost.php?p=63735205&postcount=10
Already tested:
Boot from SD card possible.
Video:
http://www.dailymotion.com/video/x3d8xq1_g386f-dual-boot-from-sd-card_tech
Cons:
lack of recovery makes flashing roms rather complicated (but we can't use stock recovery for that anyways)
second rom must be compatible with kernel
I know there's nothing interesting to be booted from sd card for now. But I hope that it'll be useful to test any compiled or ported rom, yet still have a fully usable phone.
Bypassing secure boot - kexec idea:
Kexec
is a mechanism of the Linux kernel that allows "live" booting of a new kernel "over" the currently running one
Click to expand...
Click to collapse
In short words it runs "stock" kernel and then it runs any other kernel.
As we know that stock kernel can be modified and repacked in boot.img.
The difficult is to implement kexec hardboot to kernel.
I already tried twice with no succes.
More detailed description:
http://forum.xda-developers.com/showthread.php?t=2104706
TO DO LIST:
boot from /recovery
- add hard kexec to Samsung kernel - most important
- repartition phone with 'parted' to dualboot from internal memory - low priority, but everyone may try
Already done:
- boot from /recovery with custom Samsung kernel (should be easy)
- boot from sd card possible
- boot from /recovery with changed initramfs - is it possible or will secure boot react?

--------------------------------------------------------------------------------------------------------------
Version Anglaise - English Version
--------------------------------------------------------------------------------------------------------------
Hello,
I'm very thankful that you're there to lead this project.
Such as you, I want to pass this problem of secure boot to create a custom ROM (cyanogenmod in fact).
However I'm just a web developer (PHP, Javascript...) and I know just a little (very little ) the Java (but no oriented-object).
I want to be useful... So have you some tasks to assign me ?
While I'm waiting your answer, I will read some docs !
(Sorry for my english, if you don't understand me I could try to explain in other words )
--------------------------------------------------------------------------------------------------------------
Version Française - French Version
--------------------------------------------------------------------------------------------------------------
Bonjour,
Je suis vraiment content que tu sois là pour gérer ce projet.
Comme toi, je voudrai passer ce problème de sécurité au démarrage pour créer une ROM custom (Cyanogenmod en fait).
Cependant je suis juste un développeur Web (PHP, Javascript) et je connais un petit peu (vraiment un petit peu) le Java (mais pas la programmation orientée objet).
Je souhaiterai être utile... As-tu quelques tâches à me confier ?
En attendant ta réponse, je vais lire quelques documentations !

Hello ! In the past, i already managed to compile a CWM and TWRP for our phone. But well, sadly i ran into the secure boot issue.
Now i can't even work anymore on that, since my pc is broken, and i lost almost everything. But if we understand how to bypass it i'll be glad to restart my work on it anyway, as soon as i got a new computer ^^
BTW i'm french too

Thanks for awesome job, @Agasharr.
After seeing many questions how to help you with development, I thought it would be nice to have a TODO list in first post so anyone could try to "do the magic" with their devices.
Example goals:
boot from /recovery
☐ boot from /recovery with custom Samsung kernel (should be easy)
☐ boot from /recovery with changed initramfs - is it possible or will secure boot react?
☐ add hard kexec to Samsung kernel - most important
☐ repartition phone with 'parted' to dualboot from internal memory - low priority, but everyone may try
☐ fix power off problem
Please write your own list and add to main post.
Could you answer me a question in 3rd goal - can we change initramfs when secure boot is enabled?
Sorry about my English and a bit low quality of this post but I think we have to make the thread alive and every help count. I don't have Core LTE atm but it is sad how few ppl are working with it.

Hi.
Firstly:
Your english is perfectly understandable. It's not a native language for most of us, mistakes are naturally so we shouldn't care that much about it. It's not a english philology.
Second:
To do list is a great idea, I'll update the first post, hope You don't mind if I just copy yours
As for initramfs I'll check and let You know next week.
Third:
I know some c++ and php basis, but never consider myself as a dev. I'm just and user who can't wait any longer for someone to do the job I spend almost all my free time "playing" with this phone. The problem is that I've full time job, wife, 2 kids, i'm helping my wife run her business, and i'm selling modules on prestashop addons so my all free time is in fact very little.
PS. broken PC is not an excuse ;P I currently run on old netbook with amd e450 cpu as graphic card in my PC breaks up almost 2 months ago.

Great idea for the todo list !
Firstly, I tried to extract my boot.img however the tuto which I read wasn't very adapted...
Have you some websites to advise me ?

bobo159951 said:
Great idea for the todo list !
Firstly, I tried to extract my boot.img however the tuto which I read wasn't very adapted...
Have you some websites to advise me ?
Click to expand...
Click to collapse
hi, if You insist to dump boot.img from a phone this is a good guide:
http://forum.xda-developers.com/showthread.php?t=2450045
But the easiest way is to unpack it from downloaded firmware:
http://www.sammobile.com/firmwares/database/SM-G386F/

We may decide on which firmware of this phone we will work together in order to haven't any sort of compatibily problems, no ?
I download this firmware personally : G386FXWUAOI2
-- On devrait peut-être décider sur quel firmware de ce téléphone nous devrions travailler pour ne pas avoir de problème de compatibilité, non ?
J'ai téléchargé ce firmware personnellement : G386FXWUAOI2

I was using boot and system img from latest polish and french firmware and mixed them without any problems. But we can stick with french.

Post updated:
How to dual boot from sd card:
What You need:
sd card - kinda obvious
micro sd card reader - can be useful
linux (or other way to unpack and copy system.img to sd card)
Terminal Emulator installed on phone.
How to:
With gparted on linux (or on windows with any program capable of creating ext4 partition)
Create partitions on sd card:
1. it not necessary but I advice to create some fat32 partition of size You wont, it will be available as sd card on base rom, without this partition base rom will constantly notify that sd card is damaged and You need to format it.
2. cache partition - ext4 format - stock size is 200 MB
3. system partition - ext4 format - stock size is 1475 MB
4. data partition - ext4 format - size You want
Copy system.img to system partition:
On linux:
unpack system.img to some folder
copy simg2img to that folder and create in the same place folder sys (it's an example)
open terminal and paste:
Code:
simg2img system.img sys.raw
then:
Code:
sudo mount -t ext4 -o loop,rw sys.raw sys/
sys.raw will be mounted in sys folder and You can copy files from there
if You need a root for that, open terminal in sys folder and paste:
Code:
sudo cp -r * /patch/to/your/system/partition/on/sd/card
On windows:
unknown
When You all done with sd card it's time to place it in phone and make sure how partitions are mounted.
Run terminal emulator and type:
Code:
cat /proc/partitions
It'll show all partitions on a phone, check your partitions names if You are not sure check size. You need some math to do so, as You have to divide blocks by 1024, for example 204800 / 1024 it's 200 MB.
It's time to mod fstab.u2evm from boot.img . It defines mount points so You have to change mount points for system, cache and data partitions.
It looks like "/dev/block/mmcblk0p18" (stock cache) and after change: "/dev/block/mmcblk1p6" (cache on sd card) in my case.
On windows:
Repack boot.img, rename new file to "recovery.img" and make flashable tar with
"tar-Tool_Odin3-v3.07_by_mkh.mourad"
http://forum.xda-developers.com/showthread.php?t=2446269
Flash with Odin and boot to recovery.
First boot take about 15 minutes.

Great works ! doesn't it slow down ?
I'm sorry I didn't have so much time to work on it but also I have a problem with the Java JDK on linux :-/

bobo159951 said:
Great works ! doesn't it slow down ?
I'm sorry I didn't have so much time to work on it but also I have a problem with the Java JDK on linux :-/
Click to expand...
Click to collapse
Well, phone boots like 3 times slower than normal and lags at the beginning, but after a while it runs almost like normal (at least with less demanding tasks). Performance drop is strictly related to sd card quality. Better the card better the performance will be. I have old 8 GB card class 10.
I'll update the first post with a short video.
As for your problems with java, You can use builduntu:
is a custom branch of the Ubuntu operating system for compiling Android ROMs from source. It includes everything you need to sync with the repo of your choice (Cyanogenmod, AOSP, etc) and start building.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2585828

I'm sorry but finally I decided to sell my phone..

It's interesting that you can boot on sdcard. But can you do the same with recovery ? Booting a recovery in a micro sd ? y the way i'm still searching for hints to bypass the secure boot.
I made some tests :
--Booting Stock recovery with stock kernel (but reflashed) - OK
--Stock Recovery extracted, Edited (config text files) and repacked - OK, Boot after showing the red exclamation mark
-- Custom recovery with stock kernel - won't skip the red exclamation mark
--Stock Recovery Extracted and repacked with custom kernel - Not Yet Tested
--Custom Recovery with custom kernel : Not Yet Tested
wondering if a custom kernel would change something, since the G386W needed a custom kernel to boot into custom recovery

AmineIzumi said:
It's interesting that you can boot on sdcard. But can you do the same with recovery ? Booting a recovery in a micro sd ?
Click to expand...
Click to collapse
No, I'm not booting "boot" partition from sd card, just replace recovery with another boot that points to system on sd instead of internal memory.
AmineIzumi said:
Stock Recovery Extracted and repacked with custom kernel - Not Yet Tested
Click to expand...
Click to collapse
If stock boot partition can be repacked with custom kernel and it works well, I presume that recovery will work in similar way.
AmineIzumi said:
wondering if a custom kernel would change something, since the G386W needed a custom kernel to boot into custom recovery
Click to expand...
Click to collapse
Not sure if it'll help but I already removed SECURE_BOOT_ENABLE verification from drivers/char/rtapi/rtboot/rtboot and rt_boot_sub
changing in rt_boot_sub from:
Code:
#ifdef SECURE_BOOT_ENABLE
data_addr = ioremap(PRIMARY_COPY_ADDR, info.image_size);
#else
data_addr = ioremap(info.boot_addr, info.image_size);
#endif
to:
Code:
data_addr = ioremap(info.boot_addr, info.image_size);
and in rtboot from:
Code:
#ifdef SECURE_BOOT_ENABLE
phys_cert_addr = (PRIMARY_COPY_ADDR + g_rtboot_info.image_size + 0x00001000) & (0xFFFFF000);
cert_size = read_rt_cert(phys_cert_addr);
if (cert_size == 0) {
MSG_ERROR("[RTBOOTK] |read_rt_cert failed\n");
do_iounmap_register();
ret = misc_deregister(&g_device);
if (0 != ret)
MSG_ERROR("[RTBOOTK] |misc_deregister failed ret[%d]\n", ret);
MSG_HIGH("[RTBOOTK]OUT|[%s] ret = 1\n", __func__);
return 1;
}
ret = sec_hal_memcpy((uint32_t)g_rtboot_info.boot_addr, (uint32_t)PRIMARY_COPY_ADDR, (uint32_t)g_rtboot_info.image_size);
if (ret == SEC_HAL_CMN_RES_OK) {
ret = sec_hal_authenticate(phys_cert_addr, cert_size, NULL);
if (ret != SEC_HAL_CMN_RES_OK)
MSG_ERROR("[RTBOOTK] |sec_hal_authenticate ret[%d], phys_cert_addr[0x%08x], cert_size[%d]\n",
ret, phys_cert_addr, cert_size);
}
if (SEC_HAL_CMN_RES_OK != ret) {
MSG_ERROR("[RTBOOTK] |RT boot secure error\n");
MSG_ERROR("[RTBOOTK] |boot_addr[0x%08x], image_size[%d]\n", g_rtboot_info.boot_addr, g_rtboot_info.image_size);
do_iounmap_register();
ret = misc_deregister(&g_device);
if (0 != ret)
MSG_ERROR("[RTBOOTK] |misc_deregister failed ret[%d]\n", ret);
MSG_HIGH("[RTBOOTK]OUT|[%s] ret = 1\n", __func__);
return 1;
}
MSG_ERROR("[RTBOOTK] |secure boot on\n");
#else
MSG_LOW("[RTBOOTK] |write_rt_imageaddr bootaddr[%x]\n", bootaddr);
MSG_LOW("[RTBOOTK] |write_rt_imageaddr start\n");
write_rt_imageaddr(bootaddr);
#endif
to:
Code:
MSG_LOW("[RTBOOTK] |write_rt_imageaddr bootaddr[%x]\n", bootaddr);
MSG_LOW("[RTBOOTK] |write_rt_imageaddr start\n");
write_rt_imageaddr(bootaddr);

Alcatel OneTouch Pixi 3 (8) WIfi [Model 8070 mt8127] - Custom Recovery [TWRP 3.0.2.0]

After some effort, I present you TWRP 3.0.2.0 custom recovery for Alcatel OneTouch pixi 3 (8) Wifi, model 8070.
The specific recovery is currently under some progress, but this build is working really well except from touch input.
CREDITS :
@yuweng for providing a convenient and automated way to build a twrp recovery -> twrp-build script.
Changelog:
- v2.2: Changes in partition scheme. Also the "wipe with rm -rf" instead of formating is now the default setting, for compatibility in restoring a backup.
- v2.1: Some minor changes in recovery.fstab. Thanks to @yuweng for mention it out!
- v2.0: Now the graphics are displayed in better resolution. Cpu temp is now working. Still touch is not fixed though
Things that work:
- Battery Percentage
- CPU Temp
- Installing superSU
- Installing xposed-framework
- full backup/restore process (explained at the end of the post)
Things that don't work:
- Touch (You'll have to connect a mouse through OTG cable in order to use the recovery)
DISCLAIMER:
Rooting your phone and using custom Recoveries and ROM's have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledge about the phone and phone utilities also.
Make sure that whatever you do, you are doing it at your own responsibility.
In order to install it, you'll have to unlock the bootloader of the device first. Read the steps before procedure. Take a backup of your files before proceeding!
How to unlock bootloader:
- Power on device and boot into Android.
- Connect the device to PC through cable
- Go to settings -> storage and press the 3-dot menu and select "USB computer connection". Next, select connect as Built-in CD-ROM option.
- Now, go to My Computer and install the driver of the virtual disc that is mounted from device.
- Supposing that the driver is installed correctly, we activate adb for our device.
- Go to settings -> about tablet -> hit 7-8 times on "build number", congrats, you're now a developer!
- Go to settings -> developer options -> hit USB debugging and press OK on the popup window. If the connection is working, one more popup is going to appear asking you to allow the connection, Tick the box "always allow from this computer" and press OK.
- Open an adb terminal and check if the device is working properly typing "adb devices". The serial number of your device should appear, so everything is OK!
- Now, boot into fastboot typing "adb reboot-bootloader". The device is going to reboot and boot into fastboot mode, waiting for command.
- For the bootloader to be unlocked, you have to type "fastboot oem unlock". A warning message regarding bootloader unlocking should appear on the device, waiting for an answer. Press the volume+ key and the bootloader is now unlocked! WARNING! ALL DATA ON THE DEVICE IS GONNA BE WIPED, so backup your files before.
- Wait for the wiping of the device to be finished and then you're ready to install the twrp custom recovery!
How to install TWRP:
- We must be in fastboot mode once again. You can either boot holding power button & vol+ while the device is powered off, or type the command in the adb terminal "adb reboot-bootloader" while the device is connected to PC and is booted into Android.
- Assuming that you are in fastboot mode and the device is connected to the PC, you open an adb terminal and type "fastboot flash recovery /path/to/twrp-recovery".
Replace the path reflecting your path's downloaded twrp.
- Congrats! You now have your twrp custom recovery installed!
In order to operate the twrp, due to lacking of touch input, you'll have to connect a mouse using an OTG cable.
You can now install whatever you want, from supersu to xposed-framework, you can take full backups with restore capabilites, and many more interesting stuff!
I'll try to fix the bugs, but because I'm not a developer, I'm just a power user with some advanced linux knowledge, if any dev knows and willing to help me fix the touch screen issue, he's more than welcome!
Info about backup/restore process:
The specific device has one ubnormality. It stores some of the data in a separate partition called "custom". What I found out was that if you format this partition, even if you restore a backup image, the device doesn't boot, or it boots in boot loops.
So, after some testing, I found out that the process for a reliable and working backup image, is to do the next steps:
For creating a backup:
- Go to twrp settings and select use -rm instead of formatting
- You should only choose Data, Custom & System. No need for anything else, but if you want, you can backup the rest of the dirs, just in case.
For restoring a backup:
- Wipe the Dalvik Cache, Cache, System, Data, Custom partitions. You don't need to wipe the Internal Storage or/and External SDcard, if you don't want to lose your personal data like, photos, music, etc. But, you should always take a backup of these files at any case!
- Choose Data, System, Custom partitions from twrp backup dir
- Reboot

Can we get some screenshots?

kirito9 said:
Can we get some screenshots?
Click to expand...
Click to collapse
It's planned but I have to install a screenshot script first. But if you want to see, I'll take some shots in analogue way.

dam85 said:
It's planned but I have to install a screenshot script first. But if you want to see, I'll take some shots in analogue way.
Click to expand...
Click to collapse
Nicee .

@kirito9 You can see the images on the first post

dam85 said:
@kirito9 You can see the images on the first post
Click to expand...
Click to collapse
Good, you'll get your thanks tomorrow (ran out)

Can I use it on Pixi 3 (8) WiFi I220 model?

zakk87 said:
Can I use it on Pixi 3 (8) WiFi I220 model?
Click to expand...
Click to collapse
I'm not sure. Probably not. This build is for mt8127 cpu and the most important thing, is the partition scheme of your device. The recovery partition has to be in the same position with pixi 3 8 in order to not cause brick.
But I can help you. If you could post your dumchar_info (/dev/proc/dumchar_info), I can tell you if it's the same. Maybe you must to be rooted in order to view this file. Try with kingroot.

Unfortunlately i have a bootloop and I don't know how to recover this device. Alcatel upgrade tool say it's up to date.

zakk87 said:
Unfortunlately i have a bootloop and I don't know how to recover this device. Alcatel upgrade tool say it's up to date.
Click to expand...
Click to collapse
If it's already bricked, you could try it (won't get worse afterall). But you'll have to unlock the bootloader first, follow my guide to do this.
Mobile Upgrade tool doesn't work? Can you tell me the full model name, to have a look please?

Did you try with this one? I've just checked that it has your model in the list.

My device is i220 model. No 3G, wifi only. I think its mt8127 CPU and I'm wondering how can I recover software.

zakk87 said:
My device is i220 model. No 3G, wifi only. I think its mt8127 CPU and I'm wondering how can I recover software.
Click to expand...
Click to collapse
First of all, how did you get into bootloop? Did you try to install xposed framework? In order to restore your tablet, you have to get the stock rom, through a rom readback or through a custom recovery backup. For alcatel devices, through mobile upgrade tool. Try the one I posted and give me a feedback.

I have this update tool but doesn't work.
Now I'm trying backup but it's very slow.
This device is from Orange, my friend hit factory data reset button by menu and it's all. Device bricked.

zakk87 said:
I have this update tool but doesn't work.
Now I'm trying backup but it's very slow
This device is from Orange, my friend hit factory data reset button by menu and it's all. Device bricked.
Click to expand...
Click to collapse
Try with mobile upgrade 4.4.5 version. Uninstall the other one first.
I don't think that a read back of your already bricked rom is gonna make any good. You need a working rom
Basically, your device is not bricked. Your friend just wiped your rom from device, so there isn't any os to boot, that's why the boot loops.
Try to restore it through mobile upgrade tool 4.4.5 (uninstall all other versions), and give me a shot of the fail screen.

the fail screen and log:
The phone's cu is I220-2DRGPL1
The phone's IMEI is 94D85xxxxxxxxxxxx
The phone's version is D33EO30
The version in the server is NULL
Click to expand...
Click to collapse
2015/06/16 10:53:40 [DEBUG] Thread #0xe08 has been successfully started.
2015/06/16 10:53:40 [INFO] ############################################################
2015/06/16 10:53:40 [INFO] OTU DLL Version 3.1.8, Build Id=2015031600, Protocol Id=20130822.
2015/06/16 10:53:44 [INFO] Shutting down O.T.U. Library ...
2015/06/16 10:53:44 [DEBUG] Thread #0xe08 received shutdown request.
2015/06/16 10:53:44 [DEBUG] Thread #0xe08 terminated.
2015/06/16 10:53:44 [INFO] O.T.U. Library: Succeeded to join AM!
2015/06/16 10:53:44 [INFO] O.T.U. Library: Succeeded to join MD!
2015/06/16 10:53:44 [DEBUG] Request Executor Thread #0xde4 has been terminated.
2015/06/16 10:53:44 [INFO] O.T.U. Library: Succeeded to join ReqExecutor!
2015/06/16 10:53:44 [INFO] O.T.U. Library: Great! No timer exists in scheduler after shut down all threads.
2015/06/16 10:53:44 [INFO] O.T.U. Library has been shutdown!
2016/05/17 18:55:45 [INFO] ############################################################
2016/05/17 18:55:45 [INFO] OTU DLL Version 3.2.8, Build Id=2015052611, Protocol Id=20130822 SessionBackupFile path=downloaded/session_backup.txt.
2016/05/17 18:55:45 [ERROR] Failed to open file 'downloaded\E1\FE\E1FE54CF356003567A2579519EFE0582F6A1DA0A.bin' due to non existing path.
2016/05/17 18:55:45 [ERROR] Failed to open session file.
2016/05/17 18:55:45 [ERROR] load session from disk failed!
2016/05/17 18:55:45 [ERROR] Failed to open file 'downloaded\65\A2\65A22D35BB44A8D51AE2ECF8936A5B25C9763242.bin' due to non existing path.
2016/05/17 18:55:45 [ERROR] Failed to open session file.
2016/05/17 18:55:45 [INFO] O.T.U. Library has been successfully initialized!
2016/05/17 18:55:45 [DEBUG] Thread #0x4d4 has been successfully started.
2016/05/17 18:55:45 [DEBUG] Request Executor Thread #0x4f8 has been successfully started.
2016/05/17 18:55:45 [INFO] ############################################################
2016/05/17 18:55:45 [INFO] OTU DLL Version 3.2.8, Build Id=2015052611, Protocol Id=20130822.
2016/05/17 18:55:56 [DEBUG] GisusDllImpl::create_device_info...
2016/05/17 18:55:56 [DEBUG] Thread #0x4d4: Request Processing is Starting ...
2016/05/17 18:55:56 [DEBUG] Thread #0x4d4: We have to connect first to 184.73.174.232 ...
2016/05/17 18:55:56 [DEBUG] Thread #0x4d4: Successfully connected to 184.73.174.232!
2016/05/17 18:55:57 [DEBUG] AMConnection::TickVersionReq: Connection #0x4d4: to check report info !
2016/05/17 18:55:57 [INFO] Thread #0x4d4: Upgrade for current software is not available.
2016/05/17 18:57:27 [INFO] Shutting down O.T.U. Library ...
2016/05/17 18:57:27 [DEBUG] Thread #0x4d4 received shutdown request.
2016/05/17 18:57:27 [DEBUG] Thread #0x4d4 terminated.
2016/05/17 18:57:27 [INFO] O.T.U. Library: Succeeded to join AM!
2016/05/17 18:57:27 [INFO] O.T.U. Library: Succeeded to join MD!
2016/05/17 18:57:27 [DEBUG] Request Executor Thread #0x4f8 has been terminated.
2016/05/17 18:57:27 [INFO] O.T.U. Library: Succeeded to join ReqExecutor!
2016/05/17 18:57:27 [INFO] O.T.U. Library: Great! No timer exists in scheduler after shut down all threads.
2016/05/17 18:57:27 [INFO] O.T.U. Library has been shutdown!
Click to expand...
Click to collapse
I found i213 model ROM but i don't know is it fit -
Code:
[url]http://chomikuj.pl/marcin.l19/Alcatel+pixi+7+i213+MT8127[/url]

So, you have to get a working rom from another same, working device through read back. I suggest to mail alcatel support asking for an image, or for a working method of mobile upgrade tool, they should reply to you within 24-48 hours.
I'll have a look too. When you get a reply, post again on the thread.

zakk87 said:
the fail screen and log:
I found i213 model ROM but i don't know is it fit -
Code:
[url]http://chomikuj.pl/marcin.l19/Alcatel+pixi+7+i213+MT8127[/url]
Click to expand...
Click to collapse
Maybe it will. The cpu is the same. Try to flash only system partition to see if it works.

I flashed android but memory test gives me:
============ Memory Detection Report ===========
Internal RAM:
External RAM:
Type = DRAM
Size = 0x20000000 (512MB/4096Mb)
NAND Flash:
ERROR: NAND Flash was not detected!
EMMC:
EMMC_PART_BOOT1 Size = 0x0000000000400000(4MB)
EMMC_PART_BOOT2 Size = 0x0000000000400000(4MB)
EMMC_PART_RPMB Size = 0x0000000000080000(0MB)
EMMC_PART_GP1 Size = 0x0000000000000000(0MB)
EMMC_PART_GP2 Size = 0x0000000000000000(0MB)
EMMC_PART_GP3 Size = 0x0000000000000000(0MB)
EMMC_PART_GP4 Size = 0x0000000000000000(0MB)
EMMC_PART_USER Size = 0x00000000e9000000(3728MB)
UFS:
ERROR: UFS was not detected!
Click to expand...
Click to collapse

zakk87 said:
I flashed android but memory test gives me:
Click to expand...
Click to collapse
How did you try to flash it? Through sp flash tool? This tool isn't working properly on alcatel tablets. You should try through twrp, maybe it works.

[help and advice][Google Pixel 3]: Installing su binary to gain termux access to /dev

I have a program that must be run on android as root. After installing opencv and other dependencies from itspointless repo.... this program creates a dual cam image, video in two side by side 720 x 720, one 1440 x 720....anyway...i need to run it as root on my pixel 3. 3.....any help or advice greatly appreciated....
import cgitb
cgitb.enable()
import cv2
import numpy as np
cap = cv2.VideoCapture(0)
cap1 = cv2.VideoCapture(1)
out = cv2.VideoWriter('output.avi',cv2.VideoWriter_fourcc(*'XVID'), cap.get(cv2.CAP_PROP_FPS), (1440,720))
while(cap.isOpened()):
ret, frame = cap.read()
ret1, frame1 = cap1.read()
if ret == True:
print (frame)
reframe = cv2.resize(frame,(720, 720), interpolation = cv2.INTER_AREA)
reframe1 = cv2.resize(frame1,(720, 720), interpolation = cv2.INTER_AREA)
both = np.column_stack((reframe, reframe1))
out.write(both)
if cv2.waitKey(1) & 0xFF == ord('q'):
break
else:
break
cap.release()
cap1.release()
out.release()
cv2.waitKey(0)
if you install the correct dependencies MP4 is possible too.

What part do you need help with? Rooting the Pixel 3? You'll need an unlockable bootloader, and some carrier specific models cannot be unlocked. Also, be aware unlocking the bootloader will wipe your phone.
See this article for bootloader unlocking instructions, but ignore the TWRP and Magisk parts. TWRP hasn't worked on the Pixel 3 for a couple of years, and the Magisk part is out of date. https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
You'll need the latest Platform Tools from https://developer.android.com/studio/releases/platform-tools
Once the bootloader is unlocked, download Magisk from https://github.com/topjohnwu/Magisk. See Downloads section.
Magisk installation instructions are at https://topjohnwu.github.io/Magisk/install.html. See the "Patching images" section. You'll be patching a boot image, not a recovery image.
Make sure the boot image you use is the correct one for the Android version on your phone. You can get that from https://developers.google.com/android/images. Unzip the file from that site, then unzip the zip within that file. There will be a boot.img file.
Once Magisk is installed, open Termux and run "su -". That puts you at a root prompt.

[ALL DEVICES] Private DNS broken with Let's Encrypt even on new devices

So today's been a big day, Let's Encrypt original CA expired at around 15:15 UK which is precisely when private DNS on my phone decided it wasn't going to play anymore.
DST Root CA X3 Expiration (September 2021) - Let's Encrypt
Update September 30, 2021 As planned, the DST Root CA X3 cross-sign has expired, and we’re now using our own ISRG Root X1 for trust on almost all devices. For more details about the plan, keep reading! We have also updated our Production Chain Changes thread on our community forum - our team and...
letsencrypt.org
The interesting thing is that Android trusts the new Let's Encrypt CA. Sure enough, browsing to the private DNS server in a web browser works fine. DavDroid/etc also work fine (same certificate used on that endpoint).
It appears that private DNS uses its very own CA certificate trust and this IS affected by the Let's Encrypt change.
So if your private DNS server stopped working with Android at around 15:15 today then check the server is using a Let's Encrypt certificate. This will be your problem.
Anyone know where I should file this bug with AOSP please do let me know. I have searched long and hard and really want this fixed!

I'm having the same issue, my tls dns server stopped to work on android, any solution?

Same problem with stock device Android 9. And /e/ ROM Android 10 on Gigaset GS290...

Oh dear, I spent the whole day debugging my DoT adguard instance today. Following while hoping there's a solution to this

guitphreak said:
Oh dear, I spent the whole day debugging my DoT adguard instance today. Following while hoping there's a solution to this
Click to expand...
Click to collapse
Also wasted the whole last day. So sad. This was a really great feature.

Same issue, right after launching the service. Tricky timing!
I'm wondering how to solve this in a different manner than having to replace the cert with non-letsencrypt

I'm already missing this feature very much. Can we try to install/configure our Android devices to trust ' ISRG Root X1 ' ?
edit: I just downloaded and trusted x1 on my android (https://letsencrypt.org/certificates/), no succes
topic on letsencrypt.org: https://community.letsencrypt.org/t/r3-intermediate-certificate-has-expired/160797/108

I'll have a look at alternative certificates for that VM. Google comes up with ZeroSSL. Seams like it'll be tonight's project

Problem solved for me.
I am using the acme.sh client (3.0.0) and regenerated (delete and recreate) my certificates with this settings :
--server letsencrypt --preferred-chain "ISRG Root X1"
More information here : https://github.com/acmesh-official/acme.sh/issues/3723#issuecomment-932143360
And here: https://github.com/acmesh-official/acme.sh/wiki/Preferred-Chain
PS: with certbot client:
certbot renew --preferred-chain "ISRG Root X1" --force-renewal

I have exactly the same problem. I have rented several vServers on which I have installed Pi-Hole and since yesterday ~8:00 (UTC) DNS over TLS no longer works. Have used nginx as proxy. My SSL certificates are all up to date and valid. With the tool Stubby (tested on Windows) I can connect and send DNS queries, but Android does not want.
Unfortunately, this does not seem to work. The parameter
Code:
--preferred-chain="ISRG Root X1"
does not work for certbot.
Code:
certbot: error: unrecognized arguments: --preferred-chain ISRG Root X1
But if I add the parameter
Code:
preferred_chain = ISRG Root X1
in
Code:
/etc/letsencrypt/renewal/domain.conf
, the certificate will be issued via ISRG Root X1.
After creating, the entry disappeared from the configuration.
However, Android 10 and 11 still can't connect.
Firefox says that everything is fine with the certificate.

Hoerli said:
I have exactly the same problem. I have rented several vServers on which I have installed Pi-Hole and since yesterday ~8:00 (UTC) DNS over TLS no longer works. Have used nginx as proxy. My SSL certificates are all up to date and valid. With the tool Stubby (tested on Windows) I can connect and send DNS queries, but Android does not want.
Unfortunately, this does not seem to work. The parameter
Code:
--preferred-chain="ISRG Root X1"
does not work for certbot.
Code:
certbot: error: unrecognized arguments: --preferred-chain ISRG Root X1
But if I add the parameter
Code:
preferred_chain = ISRG Root X1
in
Code:
/etc/letsencrypt/renewal/domain.conf
, the certificate will be issued via ISRG Root X1.
After creating, the entry disappeared from the configuration.
However, Android 10 and 11 still can't connect.
Firefox says that everything is fine with the certificate.
Click to expand...
Click to collapse
Which version of certbot client ?
Require 1.6.0 and more.
Better if 1.12.0 and more.
Latest is 1.19.0 now.
Check Certificate chain with: openssl s_client -connect yourdomain.tld:853
For me:
---
Certificate chain
0 s:CN = mydomain.tld
i:C = US, O = Let's Encrypt, CN = R3
1 s:C = US, O = Let's Encrypt, CN = R3
i:C = US, O = Internet Security Research Group, CN = ISRG Root X1
---

Tetsumaki said:
Which version of certbot client ?
Require 1.6.0 and more.
Better if 1.12.0 and more.
Latest is 1.19.0 now.
Check Certificate chain with: openssl s_client -connect yourdomain.tld:853
For me:
---
Certificate chain
0 s:CN = mydomain.tld
i:C = US, O = Let's Encrypt, CN = R3
1 s:C = US, O = Let's Encrypt, CN = R3
i:C = US, O = Internet Security Research Group, CN = ISRG Root X1
---
Click to expand...
Click to collapse
Oh now it seems to work ....
I have only ever used the official package source version.
For Debian 10:
Code:
[email protected]:~# apt-cache policy certbot | grep -i Installed
Installed: 0.31.0-1+deb10u1
I have now installed the latest version via snap (which I never use).
Code:
name: certbot
summary: Automatically configure HTTPS using Let's Encrypt
publisher: Certbot Project (certbot-eff✓)
store-url: https://snapcraft.io/certbot
contact: https://github.com/certbot/certbot/issues
license: unset
description: |
The objective of Certbot, Let's Encrypt, and the ACME (Automated
Certificate Management Environment) protocol is to make it possible
to set up an HTTPS server and have it automatically obtain a
browser-trusted certificate, without any human intervention. This is
accomplished by running a certificate management agent on the web
server.
This agent is used to:
- Automatically prove to the Let's Encrypt CA that you control the website
- Obtain a browser-trusted certificate and set it up on your web server
- Keep track of when your certificate is going to expire, and renew it
- Help you revoke the certificate if that ever becomes necessary.
commands:
- certbot
services:
certbot.renew: oneshot, enabled, inactive
snap-id: wy7i66qPx4neXr6m9rTh7Y40h8EhtZFh
tracking: latest/stable
refresh-date: today at 20:31 CEST
channels:
latest/stable: 1.19.0 2021-09-07 (1434) 44MB classic
latest/candidate: ↑
latest/beta: 1.19.0 2021-09-07 (1434) 44MB classic
latest/edge: 1.20.0.dev0 2021-10-01 (1498) 44MB classic
installed: 1.19.0 (1434) 44MB classic
The result with the certbot from the package sources:
Code:
Certificate chain
0 s:CN = mydomain.tld
i:C = US, O = Let's Encrypt, CN = R3
1 s:C = US, O = Let's Encrypt, CN = R3
i:C = US, O = Internet Security Research Group, CN = ISRG Root X1
2 s:C = US, O = Internet Security Research Group, CN = ISRG Root X1
i:O = Digital Signature Trust Co., CN = DST Root CA X3
With snap-version:
Code:
Certificate chain
0 s:CN = mydomain.tld
i:C = US, O = Let's Encrypt, CN = R3
1 s:C = US, O = Let's Encrypt, CN = R3
i:C = US, O = Internet Security Research Group, CN = ISRG Root X1
2 s:C = US, O = Internet Security Research Group, CN = ISRG Root X1
i:O = Digital Signature Trust Co., CN = DST Root CA X3
Ok, now I ran the command with --preferred-chain="ISRG Root X1" again for all certificates already issued.
Now it works after all
... and .... it works!
The old version of Certbot, has here in 2. place still made entries, which are now gone!
Code:
Certificate chain
0 s:CN = mydomain.tld
i:C = US, O = Let's Encrypt, CN = R3
1 s:C = US, O = Let's Encrypt, CN = R3
i:C = US, O = Internet Security Research Group, CN = ISRG Root X1

Thanks! it worked... the only think is that i had to remvoe certbot from apt on my 18.04 and add the one from snap
My pihole is up and running again