Database Users

After Flashing android 4.3 ERROR com.andorid.phone stopped

the problem is with Pepephone spanish carrier, i found a fix
http://www.elgrupoinformatico.com/s...droid-phone-android-con-pepephone-t16852.html
[SOLVED]
hi all, i flash latest paranoid android rom, andorid 4.3 , first thing i notices is the first boot, i stuck on boot logo, and i need to reboot, when phone start , i put sim card pin, and errror appear , com.android.phone stopped, i asking for advice in PA page on g+ , all people say reflash... wipe... i do all thing posible, so i tried to flash other rom, stock rom, and i have one more time the first boot problem, (stuck in boot logo) and then com.andorid.phone ERROR
please i need help what can i do??

orti13 said:
hi all, i flash latest paranoid android rom, andorid 4.3 , first thing i notices is the first boot, i stuck on boot logo, and i need to reboot, when phone start , i put sim card pin, and errror appear , com.android.phone stopped, i asking for advice in PA page on g+ , all people say reflash... wipe... i do all thing posible, so i tried to flash other rom, stock rom, and i have one more time the first boot problem, (stuck in boot logo) and then com.andorid.phone ERROR
please i need help what can i do??
Click to expand...
Click to collapse
Ok i had similar issue with stuck on boot logo. Here is fix. ITS SUPER SIMPLE
1. Go download newest SDK developer dot android dot com/sdk/index.html (New on forums so i can't post links)
2. Unzip sdk and naviagte to sdk/platform-tools
3. Use the fastboot and adb program in this folder to fastboot over your new rom.
For me I was rooted on 4.2.2 AOKP and everytime i flashed rom it would succeded but then fail to boot. Read somewhere on google that using old version of fastboot/adb can cause the issue. Updated and eveything worked flawlessly.

dhruvb14 said:
Ok i had similar issue with stuck on boot logo. Here is fix. ITS SUPER SIMPLE
1. Go download newest SDK developer dot android dot com/sdk/index.html (New on forums so i can't post links)
2. Unzip sdk and naviagte to sdk/platform-tools
3. Use the fastboot and adb program in this folder to fastboot over your new rom.
For me I was rooted on 4.2.2 AOKP and everytime i flashed rom it would succeded but then fail to boot. Read somewhere on google that using old version of fastboot/adb can cause the issue. Updated and eveything worked flawlessly.
Click to expand...
Click to collapse
Thanks i will try , bit my principal problema now is when i flash stock ROM i lost CMW recovery so now i have android 4.3 without root without recovery and with android.phone error ... And i dont know exatcly what to do????
I really need help

orti13 said:
Thanks i will try , bit my principal problema now is when i flash stock ROM i lost CMW recovery so now i have android 4.3 without root without recovery and with android.phone error ... And i dont know exatcly what to do????
I really need help
Click to expand...
Click to collapse
This is easy. Turn on phone with power and vol down buttom pressed. When on the bootloader screen plugin to computer and use fastboot to sideload custom recover.
(./fastboot sideload ziptosideload.zip)

Huawei Bricked

Hi every body.
I have a big problèm with my Nova.
Impossible to install à firmware ota because i have a huawei root.
My device is in bootloop.
I cant relock because i said : root type is risk
And when install lineage os bootloop too.
And i have a error message with cust in twrp
Help me please...

i think you have to try this
1 you get official fireware (https://boycracked.com/2017/05/18/official-huawei-nova-cannes-l11-stock-rom-firmware/)
2 put update.app to folder[dload] on SDcard
3 you use Huawei Update Extractor(https://forum.xda-developers.com/showthread.php?t=2433454) and you get recovery.img
4 flash recovery.img
5 enter recovery mode(not e) and automatic start update.app
6 but you see failed and reboot
7 But strange things to be adle to boot official fireware
8 flash twrp
9 Probably , you can mount /cust
sorry , my bad english

AlexandreVideos said:
Hi every body.
I have a big problèm with my Nova.
Impossible to install à firmware ota because i have a huawei root.
My device is in bootloop.
I cant relock because i said : root type is risk
And when install lineage os bootloop too.
And i have a error message with cust in twrp
Help me please...
Click to expand...
Click to collapse
I am guessing you use TWRP, so what is the error. You are lacking in details which makes it very hard to say any more.

[SOLVED] [Loop] Your device is corrupt it cannot be trusted and will not boot

Hello,
I have an issue with my brand new G6.
It is in a loop "Your device is corrupt it cannot be trusted and will not boot" , no more recovery available.
What i did:
I unlocked the bootloader and flashed Magisk via TWRP the device displayed that the partition was corrupt and need to be erased.
After that the device was in a loop to twrp, whatever the wipe or ... no system boot.
I read that i had to format the data partition so i adapted a what i found here to my available partitions
https://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386
the device is now in a constant loop.
Does someone can help me please ?
is there any way to recover it ? download mode ? how ?
Update : I succeed to boot into download mode but LGUP gives me an error while trying to flash
error 0x2000 ... ... cefs::initialize()

docizoc said:
Hello,
I have an issue with my brand new G6.
It is in a loop "Your device is corrupt it cannot be trusted and will not boot" , no more recovery available.
What i did:
I unlocked the bootloader and flashed Magisk via TWRP the device displayed that the partition was corrupt and need to be erased.
After that the device was in a loop to twrp, whatever the wipe or ... no system boot.
I read that i had to format the data partition so i adapted a what i found here to my available partitions
https://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386
the device is now in a constant loop.
Does someone can help me please ?
is there any way to recover it ? download mode ? how ?
Update : I succeed to boot into download mode but LGUP gives me an error while trying to flash
error 0x2000 ... ... cefs::initialize()
Click to expand...
Click to collapse
Can you boot to TWRP?
Did you make a backup and have access to it? Especially the EFS partition? If you do, restore the EFS partition.
If you can boot to TWRP, try the following:
- wipe everything (the option where you have to type 'yes').
- download lineageOS and flash it. If this is working fine, install whatever ROM you want to install.

no access to twrp anymore , no backup , only access to download mode now
is there a way to flash back twrp or stock recovery from download mode ? boot into fastboot ?
(i know... i have no excuses , but made that so many times without issues ...)
thank you in advance

Maybe you should go in download mode and flash stock Rom with LGUP.

LGUP gives me an error while trying to flash the rom error 0x2000 ... ... cefs::initialize()

Can you flash twrp through lgup or fastboot?

For those that could be in the same situation i finally succeed to flash with LGUP last version but without the 8894DLL
the error was probably coming from the dll.
Cheers and thanks all for the answers

docizoc said:
LGUP gives me an error while trying to flash the rom error 0x2000 ... ... cefs::initialize()
Click to expand...
Click to collapse
It's probably a problem with the DLL, try to extract it from the kdz and input it in Lgup folder (I don't remember where and I'm not home, check the main thread for that) and after that retry flashing
EDIT : well you were faster than my phone glad it worked for you.

Lenovo Tablet 2 1050L boot failure after attempted root

hi - I hope someone can help me. I have a LTE enabled Lenovo Tablet 2 1050L which I attempted to root using the instructions given here ... https://forum.xda-developers.com/thinkpad-tablet/general/how-to-root-yoga-tablet-2-t3251571 ... but I have managed to brick my device. I successfully installed SuperSU but then read that Magisk was better and tried the same procedure with that but it didn't work. Now when the tablet starts up, I get a message which says ... "EFILINUX ERROR [android_image_start_buffer:737] boot image digital signature verification failed : 0000001A" which appears over the initial Lenovo splash screen. I then get to the Android system recovery menu but I can't get the table any further than this. I have tried wiping data / factory resetting but this does not work.
I can boot the tablet into recovery mode using CWM or TWRP but I have no idea what to do now. I guess I shouldn't have messed. I hope someone can help - I've tried the official Lenovo forums but no one has answered in a week.
Kind regards

I've downloaded this ROM ... lenovo-forums.ru/files/file/1074-yoga-tablet-2-10-yt2-1050l_s100192_151119_row_los-50 ... and flashed this onto my tablet using the Intel flash tool and everything seems to be back up and running.
Can someone confirm that this is safe to do? Can I trust this ROM as it's not from an official source?
Thanks

/e/ OS (8.1.0) Bullhead - Oreo dev (beta) -Degoogled ROM

Posting this link as I couldn't find a link to this Project anywhere else.
The main page is here https://doc.e.foundation/
and the Bullhead download information and links are here
https://doc.e.foundation/devices/bullhead/install
Unfortunately it is now classed as a legacy device so no longer receives updates.
However that wouldn't stop a developer from doing an unofficial build etc. I was thinking of it in order to update
it to Android 10 or 11, but you apparently need 16GB RAM and 400GB free space to install 'Docker' on a Linux system,
which I don't have at the moment.
An interesting Project though.

The installation runs completely through, but then booting stops at the "Google" sign.

Next try: Install a stock android (using Nexus Root Toolkit), then install the recovery anew, boot recovery, format Data, Cache and Dalvik, and install /e/ OS as described.
This time the e with the bouncing dot appears and then I get to read
Android System: A vendor image mismatch has been detected. Typically this means your vendor image is out of date. Please ensure your vendor image matches. OPM7.181205.001
Click to expand...
Click to collapse
And when I touch the "OK", "System UI has stopped". Any idea how to fix this?
Followed THIS instruction. The same error...

Do you have the latest (ie last) Factory Image? In fastboot mode you should have Bootloader version BHZ32c and Baseband M8994F-2.6.42.5.03. These should correspond to the factory image 8.1.0 (OPM7.181205.001, Dec 2018) which you can download at https://developers.google.com/android/image.
You need to have this factory image installed before installing TWRP and then e/OS.
Once you get into e/OS you might find an error message about eSpeak TTS when you click on camera or Maps. You can resolve this by going to Settings-System-Language&Input-Advanced-Text to Speech output and changing it to 'Pico TTS'.

You might find this list useful. Had to convert it to a .txt file as I couldn't upload spreadsheet file.

FYI, I installed Ubuntu and Docker on a spare hard drive and followed the e /OS instructions to try and build an Android Pie version for bullhead, but the process failed. Meantime trying to read the log to see why it failed.

OK, next try: I managed to install the stock rom that you mentioned. The bootloader version is now BHZ32c and the baseband is M8994F-2.6.42.5.03. The download link changed to https://developers.google.com/android/ota?hl=de#bullhead from which I downloaded the latest OTA version 8.1.0 (OPM7.181205.001 from December 2018. And after 32 bounces of the dot it booted! Now I have something to play with again.
Thank you!

That is great. That should be your de facto Stock ROM to flash everytime you need to restore your phone. The other thing to note/check next time is in the stock Android Recovery screen (before you install TWRP). It should say at the top google/bullhead/bullhead and then 8.1.0/OPM7.181205.001/xxxxxxx. This again confirms the version you have installed in your phone.
If you are not sure how to get into stock Android Recovery, first boot into Fastboot Mode.
Use Vol up and Vol Down to scroll through menu and the Power button to select an option:
Start
Restart bootloader
Recovery Mode
Power Off
Select Recovery Mode then wait until you see the 'Robot lying down' and "No command" text appear on screen. Now hold Power button and briefly press the Vol-up button.
Android Recovery screen should now appear.