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)

Bricked Zuk Z1

Hello,
Ok, here is the situation
I have a Zuk Z1 with last COS update 12.1 with locked bootloader, no root etc ... (I didn't touch anything).
Yesterday, it reboot by itself but I got bootloop (starting apps then again lenovo boot image ...)
I try to factory reset by using the recovery metohd, it's start normally (optimizing apps ...) but then reboot and again bootloop ...
So I try to sideload the official COS ROM from Cyanogen Support (cm-12.1-YOG4PAS9IG-ham-signed-d4fc2c5394.zip), but the sideload stuck at 47% and saying total xfer: 1.00x and the phone go back to recovery but still have boot loop ...
I try to boot in fastboot and use the All In One tool to flash official ROM but didn't work (Its say that the bootloader is lock)
I find without knowing this menu a debugging hardware tool test, and then I run the test, its say SD : Fail and in another I got SD : Fail and no sd fuse in dir
I saw many thread here and on google, and some say that we have to use qfil/qpst method, and find this which seems complete : http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/
But as I don't know if its hardware issue or soft brick ...
Could someone help me to recover my phone to COS or CM by using the right method ?
Thank you !

wackou said:
Hello,
Ok, here is the situation
I have a Zuk Z1 with last COS update 12.1 with locked bootloader, no root etc ... (I didn't touch anything).
Yesterday, it reboot by itself but I got bootloop (starting apps then again lenovo boot image ...)
I try to factory reset by using the recovery metohd, it's start normally (optimizing apps ...) but then reboot and again bootloop ...
So I try to sideload the official COS ROM from Cyanogen Support (cm-12.1-YOG4PAS9IG-ham-signed-d4fc2c5394.zip), but the sideload stuck at 47% and saying total xfer: 1.00x and the phone go back to recovery but still have boot loop ...
I try to boot in fastboot and use the All In One tool to flash official ROM but didn't work (Its say that the bootloader is lock)
I find without knowing this menu a debugging hardware tool test, and then I run the test, its say SD : Fail and in another I got SD : Fail and no sd fuse in dir
I saw many thread here and on google, and some say that we have to use qfil/qpst method, and find this which seems complete : http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/
But as I don't know if its hardware issue or soft brick ...
Could someone help me to recover my phone to COS or CM by using the right method ?
Thank you !
Click to expand...
Click to collapse
Go with qpst/qfil method to recover your phone
And did you tried changing the USB port or cable while side loading cos ROM .. Cause most of issues are solved by the changing USB port or cable.. So try this.. Or else qfil is the option

shubhambhise said:
Go with qpst/qfil method to recover your phone
And did you tried changing the USB port or cable while side loading cos ROM .. Cause most of issues are solved by the changing USB port or cable.. So try this.. Or else qfil is the option
Click to expand...
Click to collapse
Hello,
I got help on the telegram group, we try many thing, the result is that I can only get ZUI working, if flashing COS via QFIL, I get the same result, if I flash ZUI, unlock bootloader, flash TWRP, wipe everything, then sideload CM13, TWRP say that no os is installed and I get a bootloop at the bootloader ...
ZUI is good, but I get some error regarding notification.
If you have any other idea ?

wackou said:
Hello,
Ok, here is the situation
I have a Zuk Z1 with last COS update 12.1 with locked bootloader, no root etc ... (I didn't touch anything).
Yesterday, it reboot by itself but I got bootloop (starting apps then again lenovo boot image ...)
I try to factory reset by using the recovery metohd, it's start normally (optimizing apps ...) but then reboot and again bootloop ...
So I try to sideload the official COS ROM from Cyanogen Support (cm-12.1-YOG4PAS9IG-ham-signed-d4fc2c5394.zip), but the sideload stuck at 47% and saying total xfer: 1.00x and the phone go back to recovery but still have boot loop ...
I try to boot in fastboot and use the All In One tool to flash official ROM but didn't work (Its say that the bootloader is lock)
I find without knowing this menu a debugging hardware tool test, and then I run the test, its say SD : Fail and in another I got SD : Fail and no sd fuse in dir
I saw many thread here and on google, and some say that we have to use qfil/qpst method, and find this which seems complete : http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/
But as I don't know if its hardware issue or soft brick ...
Could someone help me to recover my phone to COS or CM by using the right method ?
Thank you !
Click to expand...
Click to collapse
Hope this will help you
Check this out
http://forum.xda-developers.com/zuk-z1/help/helpppp-t3505990

http://forum.xda-developers.com/zuk-z1/general/guide-how-to-unlock-root-install-twrp-t3394037
This will help you

Bootlooping to Factory reset status

Hello,
I'll try to detail as much as I can to explain how i ended up Bootlooping :
I tried today to root my LG H870. (imported from Germany, according to the seller).
I followed the tutorial on xda to unlock the Bootloader on the device.
After flashing it, it launched Android the 1st time without difficulties.
I rebooted into TWRP, flashed supersu, then rebooted into Android. Problems started there, the system told me my partition was encrypted, and asked if i wanted to reinitialize it. After doing so, it's been stuck, bootlooping to TWRP, the internal partition empty.
I followed numerous tutorial on how to flash a stock ROM through TWRP, Fastboot, ADB Sideload, without any success.
With TWRP, it was always ending up saying the flash wasdone, without writing a single file in the partition.
I also tried installing stock ROM with LGUP, but once again, didn't seem to work. While in download mode, it was either telling me the phone was an unknown model, on port COM3, or that there was no handset connected.
I then followed another guide, using LG Firmware Extract and LG Flash Tool. It didn't work as expected, but, I don't really know how, it made LGUP seeing my phone correctly. I was then able to flash a stock ROM (H87010f). No error during the process.
After the LG Logo, i get now a blue screen, saying for some seconds "Encryption Progress", and after that "Factory Reset Status", with a big red "2", and it gets stucks there.
Once again, if I get into download mode and into LGUP, i get now the "no handset connected" message.
Is someone on here able to help me?
If more infos are needed, tell me, i'll try to answer!
Thank you all!

Need help unbricking my Axon 7

So I'm quite a noob when it comes to flashing/recoveries/bootloaders and things like that, and that's most likely the reason why I got myself into this situation. Anyways my axon 7 (which I bought in China a year ago) was running fine yesterday, just a little bit slow. I had installed TWRP on it, and flashed the US rom along with SuperSU root. However last night was when things all went wrong.
I tried to flash the xposed installer from twrp which caused me to not get stuck on the AXON boot screen when I tried to restart.
Seeing that my phone was now softbricked, I thought since my phone was already running so slow, maybe I should take this opportunity to install lineage os and at the same time unbrick my phone. Win win right?
But when I tried to flash lineage os, I got the red error 7 message and problems with mounting /system. I went into the zip and changed the updated script and tried reflashing the new lineage os zip. That didn't worked and I still got error 7 messages.
So I this point I was quite desperate to get my phone back so I tried to reinstall the stock axon 7 rom which didn't work as I ended up with unable to mount /system errors.
I tried to reinstall twrp but my pc wouldn't recognize my phone while it was in fastboot mode.
I tried this tutorial IGNORETHISTEXTCASUEICANTPOSTLINKSYETJUSTCOPYTHELINKTHATCOMESAFTERhttps://m.youtube.com/watch?v=T-7neHzSIvc but got stuck on the step where I needed to reformat my data partition as exfat (the progress bar just kept going). After waiting 3 hours for it to format, I thought it was frozen or something because the guy in the video was able to format it instantly.
So I force restarted my axon 7 and now I'm here:
1. Most of the time when I restart my phone, it gets stuck on the zte logo
2. occasionally it gives me the option menu (with power off, fastboot, recover, etc.)
3. If try to use fastboot, my pc won't recognize my phone
4. If I use recovery, I get stuck on the teamwin screen, but my computer seems to recognize my phones presence, in the fastboot command prompt the "adb devices" command displays my phone as "10109dd offline", if I run any other command such as reinstalling TWRP, the command gets stuck at "waiting for device"
5. Obviously can't boot into android cause my whole system partition is wiped
Anyways that's the state I'm currently in (all because I wanted to install xposed installer ) and I would appreciate any suggestions!

Make sure all your phone drivers and adb are up to date.
Also try the Zadig drivers these might help too.
In Windows device manager it should show as,
Qualcomm HS-USB QDLoader 9008"
If you get stuck you can always try using an Edl package.
I have and Edl help page here>
https://forum.xda-developers.com/axon-7/help/bad-flash-help-page-axon-7-t3839700

Syberclone said:
Make sure all your phone drivers and adb are up to date.
Also try the Zadig drivers these might help too.
In Windows device manager it should show as,
Qualcomm HS-USB QDLoader 9008"
If you get stuck you can always try using an Edl package.
I have and Edl help page here>
https://forum.xda-developers.com/axon-7/help/bad-flash-help-page-axon-7-t3839700
Click to expand...
Click to collapse
Holy moly, you saved my life Syberclone! I was able to flash back my rom through EDL mode and my A7 is saved! :angel: Thanks a million!:good:

Unable to boot - Oneplus8 pro

Hi Everyone,
I have an issue with my Oneplus8 pro and below are the details
1. The device was working perfectly. I was interested to root the device and install a custom ROM.
2. The method used was to try and flash a patched boot image for the device but I think i landed up using a wrong boot image file.
3. The OS was on 10.5.10 if I remember correctly. I used a patched image file I suppose of an older firmware. Now restarts and goes to "QUALCOMM Crashdump mode". The only options are
a. reboot to fastboot mode
b. flash the TWRP for Oneplus 8 pro but that doesnt mount by storage so cant really transfer anything to flash again.
Requesting some help to fix the issue and apologies if i have not explained correctly.

Tried booting a stock boot image?

neverborn said:
Tried booting a stock boot image?
Click to expand...
Click to collapse
Hey,
Thank you for a quick repsonse. Yes, i had tried doing that and still the same error however while we speak, i just downloaded the msmDownloadtool and tried using it to flash a stock firmware and finally, i am so happy to see the device boot sucessfully
Thank you once again for tryin to help
Regards

Hello.
Clarify exactly how the procedure took place