Hello i wrongly installed aosp s4 google edition 5.0 ,because i flashed gapps with it also which i shouldnt,and when it boots it says unfortunately,the process com.android.phone has stopped and im thinking that i should enter recovery mode and wipe and flash again without gapps but it wont go into recovery mode...i tried cmw recovery and twrp recovery but when i press the volume up and power buttons it says recovery booting but then it restarts,it did the same before but i entered recovery from an app,someone help me
No one ??
kidudub said:
No one ??
Click to expand...
Click to collapse
Hi mate ,
That is related to google syncing the contacs
go to
Go to
settings ->application manger -> all-> and clear data on contact and contact storage
or do a factory reset and flash rom again
kidudub said:
Hello i wrongly installed aosp s4 google edition 5.0 ,because i flashed gapps with it also which i shouldnt,and when it boots it says unfortunately,the process com.android.phone has stopped and im thinking that i should enter recovery mode and wipe and flash again without gapps but it wont go into recovery mode...i tried cmw recovery and twrp recovery but when i press the volume up and power buttons it says recovery booting but then it restarts,it did the same before but i entered recovery from an app,someone help me
Click to expand...
Click to collapse
Press the three button , when you see the first samsung logo , stop pressing the power button but keep pressing the up volume with the home button .
If this doesn't work , install rom manager from the play store , install from it the last CWM and boot in recovery from the app
guys,i cant acces my phone,after it boots it goes into that error
kidudub said:
guys,i cant acces my phone,after it boots it goes into that error
Click to expand...
Click to collapse
Okay , we will try the hard way then .
Download the last stock firmware , boot into download mode , open odin , plug your device , flash the firmware with odin .
Choose the file in odin from " PDA" .
Soufiansky said:
Press the three button , when you see the first samsung logo , stop pressing the power button but keep pressing the up volume with the home button .
If this doesn't work , install rom manager from the play store , install from it the last CWM and boot in recovery from the app
Click to expand...
Click to collapse
Dude thank you so much,thats why it didnt go into recovery mode... thank you so much
No problem men , glad i could help
lost my twrp after installing bootloader changer and then installing kk bootloader(for cloudy 3.3). (accidently marked install twrp inside the bootloader installation after already having the latest twrp installed)
phone restarts right after logo appears and seems to be unable to boot at all.
no download mode. no recovery. not even hardware factory reset is accessible.
im really lost here ! read all xda posts nothing works because i cant connect to
the phone from any pc. please help! i cant flash anything because i have no adb or any connection from the phone to the pc.
wont show up in device manager in any way(with the latest drivers installed) and wont show up on linux on /dev/sd*.
before the bootloader i had access to twrp and showed up just fine on my win 7.
problem solved!
was able to enter recovery mode by pressing pwr + vol-up release when logo appears and press vol-up + vol-down.
My phone just went by its own into a bootloop form stock 5.02 , i tried to flash the stock using odin and the problem continued . I then tried to root my device usrin TWRP but i didnt notice that USB debugging must be set from OS it self which i dont have any access to .
So now i cant exit the boot logo no matter what i do from Key combos like Power + Vol down to restart , not matter power + vol up/down + home button , nothing just works , any ideas please ?
Hello Friends,
I am new to this area and please help me learn out everything.
Today I have just installed TWRP on my Samsung Galaxy s5 using Odin v3.12.3 .
I removed my battery and tried to enter recovery mode to install SuperSU.
For recvery booting , i pressed volume up, home, and the power key.
But my phone still boots normally.
Please help
Hello All
I have problem with my Axon7 G. I had 8.00 version installed and tried to make a system write option with using a method mentioned in
Official (Beta) Android 8.0.0 V1.30B01 EU Version by NFound thread. I flashed zip mentioned in this tread -ZTE_A7_UniversalBootStack.
Then restart devices and...whats happened....soft (or hard) bricked my phone!!!!!
1. After restart i had a standard warning about unlocked bootloader with yellow fonts . After 5 sec yellow fonts changed into red and wrote my device is corrupt...
2 using vol down i can enter into bootloader mode - then i can choose option like fastboot, recovery,restart and power off.
- pressing recovery and restrt , phone restart and again boot into bootloader mode with option above (cant get into twrp or stock recovery mode)
-pressing fastboot i can enter into this mode .
3 . Use fastboot mode to flash recovery and boot ( fastboot flash recovery recovery.img and fastboot flash boot boot.img)
everything seems ok but...nothing changed , i cant boot into recovery -twrp or stock. Still go back after restart to bootloader menu
4. edl mode.....i can`t enter . Use vol + and vol- and power button then after 3 sec phone went black screen with red light upper left. Applications cant recognize phone in this mode...
somene can help me ???
I also get the warning but I can just continue with the boot. I can't access recovery however. Don't know hot to fix that.
Ok I did this. A7 is working )
I flashed this via fastboot flash file: A2017G_B06_NOUGAT_STOCK_FASTBOOT_EDL.zip then i went into twrp and everything works
Antistar said:
Ok I did this. A7 is working )
I flashed this via fastboot flash file: A2017G_B06_NOUGAT_STOCK_FASTBOOT_EDL.zip then i went into twrp and everything works
Click to expand...
Click to collapse
did you manage to get the error message away?
I got it recently after installing LOS 15.1, but for me everything works fine .
I'm just afraid if the device randomly reboots at night my alarm won't go off in the morning since it's the device is shutting itself down after the 30 second warning.
If you've fixed this can you please detail me through the steps.