Database Develop

[Q] Help: Galaxy Mini/Pop won't boot.

I haven't rooted my phone whatsoever or installed a rom or something. One day, it just won't boot. I don't use it all the time, so the battery died. I charged it so I could use it and download an app. When I try to power it on, it will only reach the flashing Samsung logo with the black background and won't go any further so I result to opening the back cover the remove the battery and try turning it on again. Still won't boot. I tried draining the battery, but it still won't boot. Would booting it without the SD card solve this problem? I heard that if I did that, I would have to factory reset it using the hardware keys. I don't want to erase everything in the phone since I'm not able to back it up. Please help. Thanks!

ZAYNlienware said:
I haven't rooted my phone whatsoever or installed a rom or something. One day, it just won't boot. I don't use it all the time, so the battery died. I charged it so I could use it and download an app. When I try to power it on, it will only reach the flashing Samsung logo with the black background and won't go any further so I result to opening the back cover the remove the battery and try turning it on again. Still won't boot. I tried draining the battery, but it still won't boot. Would booting it without the SD card solve this problem? I heard that if I did that, I would have to factory reset it using the hardware keys. I don't want to erase everything in the phone since I'm not able to back it up. Please help. Thanks!
Click to expand...
Click to collapse
You can try to boot it without SD card, but i don't think that's the problem.
I think your only possible solution is to try doing a factory reset. Try to press HOME button and POWER button together until you get to the recovery. Than, depending on the recovery you have, search for a "wipe cache/data" or "data reset".
Another solution might be using Odin, but that's the last one...

frazar said:
You can try to boot it without SD card, but i don't think that's the problem.
I think your only possible solution is to try doing a factory reset. Try to press HOME button and POWER button together until you get to the recovery. Than, depending on the recovery you have, search for a "wipe cache/data" or "data reset".
Another solution might be using Odin, but that's the last one...
Click to expand...
Click to collapse
It did work. I thought of doing that but I waited for my friend so I could consult for another way, but I resorted to a hard reset. Thanks!

sorry for you, you can't get your data back
but to solve this
you can try to wipe everything through recovery mode
(while turn of, home button + power)
if you still can't access recovery mode or still the same after wiping
you must flash your mini
[TUT]Official Gingerbread 2.3.6 09.02.2012 GalaxyMini s5570~ODIN~UPDATED
for later, backup your data app by using Titanium Backup
must root

[Q] [CM10] [Brick] After CM10 stable Update: Bricked device(?) / HW issues

Hi all,
seems like my OB is broken. But just in case this is still a repairable issue and since I would of course love to keep my good ol' OB, I'm posting my issue. Maybe there is still hope
It all started after OTA-Update from CM10 nightly to the stable release. I noticed that from time to time the power button did not work after charging the device over night. So for example, the device woultn't wake up when pressing the power button, but reconnecting to the charger did the trick. But then again, I often coudn't turn it back to sleep with the button.
Every time that issue appeared, the OB acted normally after removing the battery for a moment.
But not today.
Again, I couldn't get it to lock when it was active because the power button did not work. So I decided to wait until the screen turned off after the timeout which it actually did. But then again, I couldn't wake it up.
So, starting with the "normal" procedure, I removed the battery for a moment and tried to turn it back on, thinking that it'll be just fine again. But not this time. It didn't react at all. Even after connecting it to the charger - the display turned on and showed the charging animation, but I couldn't get the device to boot.
Next step: Common unbrick procedure. Since it was the only thing I could still do with the OB, I reflashed the good old patched v20n using SmartFlash. I used the exact same program and bin files that I used long ago when I initially rooted the device. So that should have worked like a charm. It didn't.
First try: Flashed with SmartFlash and restored an old nandroid with Zeus ROM on it. Rebooted and... oh great it's stuck already on the LG logo.
Okay, 2nd try: Flashed again but this time just selected the reboot option in CWM. Device boots, plays the animated LG bootlogo and reboots into bootlooop....
So far about my poor OB
Now does anybody have any idea what could have gone wrong with the device?
Of course it could just be a coincidence that these issues started right after the update and the cause may be an ancual failure of the HW button.
But really, how likely is that keeping in mind that my OB worked like a charm all the time before the update?
Any ideas, comments or even suggestions what else I could try?

Smartflash must unbrick the device if the problem is not a hardware problem, if you have tried it and it didn´t work, i am pretty sure that you have to take the phone to warranty.
Anyway, you can try to flash a patched bin/fls with root and recovery, after flash phone will go to recovery, then do a full wipe (Data, cache and dalvik) and reboot.

Reflashed with SmartFlash (to get into CWM), wiped all, booted v20n; no power button, all other HW-Buttons work :/

Hardware problem.

That's what I thought as well, but:
Just managed to restore my Zeus ROM Nandroid image, cleared cache and it booted without problems. Aaand: Power button is working again! Locking/unlocking as well as turning on/off the device entirely works normal!
Now seriously, this issue keeps buggin me - how can something like that happen at all??
I mean, if I would mess with the key mapping and remove the mappings of the power button, it might not work anymore for locking and unlocking the phone. But what could possibly cause that button to not even work for powering on the device? I always thought that must be a hard-wired functionality??

cm12 wont enter recovery

hey guys... this morining suddently my z1 turned off... and now it wont boot. The cm face shows up but after 2min it freezes. I tried to enter recovery but it wont happen. The LED turns purple.. i press the vol up button but nothin happen.. the phones starts booting normaly :/
i flashed twrp via fastboot but this was not a solution..
i'm on cm12-2015-01-30... any ideas?

same situation here bro

hmm.. maybe its possible to install cm only via fastboot? special files need?

Read this:
http://forum.xda-developers.com/showthread.php?t=3000822
http://forum.xda-developers.com/showthread.php?t=3002887
Sent with C6903 using Tapatalk 2

thanks.. but this wont wort for me. The volume up button doesnt bring me into recovery

same here! Cm12 update 31.01. installed, reboot at bootanimation stuck and can´t enter recovery ... will go fastboot

had the same problem....it was a hit and miss for me.....after a lot of tries recovery started rendomly at one.....but i was dumb enough to flash 30/01 nightly again ...then today morning after the hit and miss session when the recovery started....i took my sd card....replaced 30/01 nightly with 28/01 nightly....popped the card back and flashed it....voila...its working now.......hope you find a fix too..

dont know why... yesterday i flashed twrp via fastboot and it didnt work.. today i tried again and it worked! In recovery i wiped dalvik and cache, hit reboot and the system started! yay !
maybe the solution was twrp... philz touch didnt worked.. hope it will work for you guys

When you on Cm12 there is no TWRP it's the new Cyanogenmod Recovery. You can enter it by pressing the volume down and up button after the Sony logo pops up.

Got the same problem, have been trying many different recoveries, no success. Does anyone have a definite fix?

Also the same for me. Cyanogen logo freeze (or sometimes restart phone) and this for the nightly buids of 201500130, 20150131 and lastest 20150202.
I had to do a fresh wipe with an AOSP rom to install again CM12. The first boot was ok after fresh install but on reboot, the problem was getting back.
I'm going to revert to the 20150128 nightly and look out the next changelog to see if a fix will be available.

Okay. Look at the Cyanogenmod page. In the faq they say. "when the light is purple press volume up button" it works every time http://wiki.cyanogenmod.org/w/Honami_Info

Z1 wont boot proplerly - cant get into recovery
-Happy Feet- said:
Okay. Look at the Cyanogenmod page. In the faq they say. "when the light is purple press volume up button" it works every time
Click to expand...
Click to collapse
I've been trying that for days, and it very rearely works (mayvbe 2 or 3 rimes in as many days). My phone is in a real bad way - about 99.99% of the time its just stuck on the CM boot logo. Very occasionally I can get into recovery, but in order to get into my OS, I actually have to reflash CM. Simple boot from recovery never works.
I've tried installing fotaZ1_2.8.4.img (as suggested by a user on another thread) from fastboot, but can only get into that very rarely too.
I've also tried flashing the boot.img from the last few CM nightlies, but once again no joy.
This is getting real bad, as I've spent days reading threads on here and reflashing / resetting the phone! In fact my fingers are aching from stabbing at those damn power and volume buttons!
If anyone could please help or suggest a solution, I'd be eternally grateful. CM 12 is freaking great...when . if it works... ;-p
cheers
[edit]
Managed to get into TWRP, so decided to just wipe the phone completely, including int SD card. Thankfully TWRP has a file manager, so I could copy my stuff to my ext SD beforehand. Reflashed cm12-20150202 and it seems to be ok now. Done 3 or 4 test shutdowns, as well as reboots and its been booting ok so far. Getting into recovery still seems to be a bit touch and go though, but I can live with that for the time being I guess.

Any news here? I can't get into recovery mode, and my phone is now effectively "bricked".
-Happy Feet- said:
When you on Cm12 there is no TWRP it's the new Cyanogenmod Recovery. You can enter it by pressing the volume down and up button after the Sony logo pops up.
Click to expand...
Click to collapse
I upgraded from CM11 to a CM12 nightly (the one with the broken boot animation that hangs). Before upgrading I had TWRP, and could boot into recovery by holding volume down while turning on the phone. This is not working any more. Have tried a lot of different combinations, but nothing seems to work.
Please, if anyone can help, give me a tip.
Btw: my led never lights up, only after a few seconds, the Sony logo shows, then the broken boot animations starts.

What worked for me was to only press volume-up after the Sony logo had appeared and the LED shows purple briefly. I then cleared cache and dalvik and was able to boot.
I already had fotaZ1_2.8.4.img installed, and had rebooted one of the affected CM12 nightlies.

idle1 said:
Any news here? I can't get into recovery mode, and my phone is now effectively "bricked".
I upgraded from CM11 to a CM12 nightly (the one with the broken boot animation that hangs). Before upgrading I had TWRP, and could boot into recovery by holding volume down while turning on the phone. This is not working any more. Have tried a lot of different combinations, but nothing seems to work.
Please, if anyone can help, give me a tip.
Btw: my led never lights up, only after a few seconds, the Sony logo shows, then the broken boot animations starts.
Click to expand...
Click to collapse
you can enter recovery when you boot the Phone, plugin USB Cable and when the LED shows purple then hold the volume up button, that worked for me.
btw. Bootloop: flash the rom.zip again then it boots. after that install from playstore this Bootanimation: https://play.google.com/store/apps/details?id=de.appublic.cyanogenboot and install this animation. After that boot work fine and you can flash new updates without issue

Thank you very much, both of you. I could not get any of your tips to work, though this morning the strangest thing happened. When i got up, I suddenly heard the alarm ringing from my Z1. It was booted and seemed ok. I have no idea how it booted...
Anyway, now it's working again with todays nightly. Thanks again.
btw: I can now enter the new recovery (twrp is replaced by a CM one) by tapping vol-up while the Sony logo is showing. Rebooting directly into recovery from the OS does not work.

bootloop (starting, charging mode and also, with pc) z3c how to solve?

Hi guys, first of all sorry for my bad english
anyway, when I tryed to restart my phone, it was going to infinite bootloop... so, I tryed to lauch twrp and swipe all data also reinstalling the rom with adb/pc.. but in this moment happened the inaspected.. it go, to bootloop even if it was off, (changer screenshot, bootloop)
How Can I lauch adb, if my pc doesnt finds my z3c , because it goes to bootloop even if is off?

Xalein said:
Hi guys, first of all sorry for my bad english
anyway, when I tryed to restart my phone, it was going to infinite bootloop... so, I tryed to lauch twrp and swipe all data also reinstalling the rom with adb/pc.. but in this moment happened the inaspected.. it go, to bootloop even if it was off, (changer screenshot, bootloop)
How Can I lauch adb, if my pc doesnt finds my z3c , because it goes to bootloop even if is off?
Click to expand...
Click to collapse
So it won't stay off, even if you press power and volume up together for a few seconds? Which rom were you using, what did you do before it bootlooped, bootloader unlocked, etc...?

levone1 said:
So it won't stay off, even if you press power and volume up together for a few seconds? Which rom were you using, what did you do before it bootlooped, bootloader unlocked, etc...?
Click to expand...
Click to collapse
even it wont stay off, always bootloop;
If I remember well, first I unlock the phone with the code from sony; after launch the twrp with adp on pc (for a strange motive it (the phone) doesnt load the twrp without pc) , clean cache and co, like 2/3 times, after installing the new rom
it seems to me the omni rom 7.1.2

Xalein said:
even it wont stay off, always bootloop;
If I remember well, first I unlock the phone with the code from sony; after launch the twrp with adp on pc (for a strange motive it (the phone) doesnt load the twrp without pc) , clean cache and co, like 2/3 times, after installing the new rom
it seems to me the omni rom 7.1.2
Click to expand...
Click to collapse
Sorry to repeat, but just to be clear - when you press and hold power and volume up, what happens? Are you saying it turns off, and then automatically turns back on, and bootloops?

levone1 said:
Sorry to repeat, but just to be clear - when you press and hold power and volume up, what happens? Are you saying it turns off, and then automatically turns back on, and bootloops?
Click to expand...
Click to collapse
strangely this time go, it go on twrp..
but since I have encrypted, twrp request me the pass.. but, inserting the right pass, it always failed.. there is a way, to bipass this process (even with formatting the phone) to acess to twrp?

Xalein said:
strangely this time go, it go on twrp..
but since I have encrypted, twrp request me the pass.. but, inserting the right pass, it always failed.. there is a way, to bipass this process (even with formatting the phone) to acess to twrp?
Click to expand...
Click to collapse
Try fastboot flash, (different kernel or different recovery...), or flash stock rom with FT.

levone1 said:
Try fastboot flash, (different kernel or different recovery...), or flash stock rom with FT.
Click to expand...
Click to collapse
I solved with format data.. thanks
I have to re-installed the rom.. but I just to have wait to understand if it is still a bootloop or the classic installation phase..

Xalein said:
I solved with format data.. thanks
I have to re-installed the rom.. but I just to have wait to understand if it is still a bootloop or the classic installation phase..
Click to expand...
Click to collapse
10+ minutes is not unusual for first boot for stock rom.

levone1 said:
10+ minutes is not unusual for first boot for stock rom.
Click to expand...
Click to collapse
solved
but futhermore, another problem (hardware problem, I don't want to open another post):
today I open my cell phone because the screen had stuck, discovering that the connector had disconnected.. ok solved.. but the cellphone seems electrically charged, I mean more than 5 (I think) time I got the shock
any solution?/possible causes? (isnt the first time that I open the phone)

Updated to Xiaomi.eu 10.1.2.0, can't unlock screen.

I was very excited to install this update that released today, but after installing it, I can't sign in to my phone. When it boots up, it flashes the homescreen wallpaper, not the lockscreen wallpaper for a second or two then the screen turns black. If I hold the power button I can view the power settings (reboot, silent, airplane mode, shut down) and also if I double press the power button, which my camera shortcut, it opens the camera. Aside from these actions, I can't do anything.
My method to installing this rom was this:
Download the rom from xiaomi.eu website
use the built in updater where I select a rom on my phone and it automatically boots to recovery for me (I'm using TWRP)
Let it do its thing, and boot up, then when it boots the errors occur.
I tried wiping cache and dalvik, but no change.
Did I miss something? Is there something I should have done differently when updating my phone? Is there a special procedure in upgrading Android versions? (1.1.2.0 is first Android Pie version on my phone)
Thank you very much.
Edit 1: I have flashed a second time, this time flashing cache, dalvik, and data. I was able to get into MIUI and set up my device, but after I rebooted the phone for a separate reason, I am experiencing the same errors as before.
Edit 2: Not 100% sure because I switched ROMs, but I probably could have gotten it working by wiping /system as well.

Hello, same thing here.
Clean install and same problem... very sad

DaniloFerracini said:
Hello, same thing here.
Clean install and same problem... very sad
Click to expand...
Click to collapse
Yep same here. I tried it again, wiping data partition and same issue. Can't downgrade because rollback protection too. I guess I'll try out Pixel Experience??

DaniloFerracini said:
Hello, same thing here.
Clean install and same problem... very sad
Click to expand...
Click to collapse
Hey, by the way, what launcher are you using? This seems to be a problem with just the lock screen so maybe there is a weird interaction happening between the launcher and the lock screen. I was using Rootless Pixel Launcher.
Edit: one more question: did you do the same thing as me where I first flashed without formatting data, then you flashed a second time, that time formatting the data? I'm thinking it could also be just because we flashed it incorrectly the first time, future flashes are gonna be messed up.

Where's the download I can find only 10.1.1.0

AquaticPossum said:
Hey, by the way, what launcher are you using? This seems to be a problem with just the lock screen so maybe there is a weird interaction happening between the launcher and the lock screen. I was using Rootless Pixel Launcher.
Edit: one more question: did you do the same thing as me where I first flashed without formatting data, then you flashed a second time, that time formatting the data? I'm thinking it could also be just because we flashed it incorrectly the first time, future flashes are gonna be messed up.
Click to expand...
Click to collapse
I make a dirty flash and clean flash, nova launcher and stock launcher, both dont work

kekkojoker90 said:
Where's the download I can find only 10.1.1.0
Click to expand...
Click to collapse
https://sourceforge.net/projects/xi...ulti_MI8_V10.1.2.0.PEACNFI_v10-9.zip/download
DaniloFerracini said:
Hello, same thing here.
Clean install and same problem... very sad
Click to expand...
Click to collapse
Try this : https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008
You must have a valid custom recovery
Edit : the recovery method won't work... It's a problem with the rom. Just switch to another version....
https://xiaomi.eu/community/threads/miui-10-0-10-1-stable-release.47170/page-23 see the last posts about that

my phone also dead after install the last pie my phone stuck on a black screen
tried downgrading the miui to oreo and the phone did not work well the phone reboot after 30 sec
and after that happened I backed to pie version again but the same problem stuck on a black screen I don't want to lose my data what can I do?
there is possible to back the oreo version and restore that data from twrp backup? the apps work well or not?

almog250 said:
my phone also dead after install the last pie my phone stuck on a black screen
tried downgrading the miui to oreo and the phone did not work well the phone reboot after 30 sec
and after that happened I backed to pie version again but the same problem stuck on a black screen I don't want to lose my data what can I do?
there is possible to back the oreo version and restore that data from twrp backup? the apps work well or not?
Click to expand...
Click to collapse
You shouldn't downgrade :/

kekkojoker90 said:
You shouldn't downgrade :/
Click to expand...
Click to collapse
Even with xiaomi.eu rom ?

Otarie004 said:
Even with xiaomi.eu rom ?
Click to expand...
Click to collapse
You can downgrade from Pie to Oreo with EU rom and TWRP, the phone boot up normaly but some processes say stop working.
I had same problem yesterday. I recommend wipe system before reinstalling Oreo rom and waiting a fixed Pie rom

kekkojoker90 said:
Where's the download I can find only 10.1.1.0
Click to expand...
Click to collapse
This is the Xiaomi.eu ROM which is based on China Stable.

AquaticPossum said:
I was very excited to install this update that released today, but after installing it, I can't sign in to my phone. When it boots up, it flashes the homescreen wallpaper, not the lockscreen wallpaper for a second or two then the screen turns black. If I hold the power button I can view the power settings (reboot, silent, airplane mode, shut down) and also if I double press the power button, which my camera shortcut, it opens the camera. Aside from these actions, I can't do anything.
My method to installing this rom was this:
Download the rom from xiaomi.eu website
use the built in updater where I select a rom on my phone and it automatically boots to recovery for me (I'm using TWRP)
Let it do its thing, and boot up, then when it boots the errors occur.
I tried wiping cache and dalvik, but no change.
Did I miss something? Is there something I should have done differently when updating my phone? Is there a special procedure in upgrading Android versions? (1.1.2.0 is first Android Pie version on my phone)
Thank you very much.
Edit 1: I have flashed a second time, this time flashing cache, dalvik, and data. I was able to get into MIUI and set up my device, but after I rebooted the phone for a separate reason, I am experiencing the same errors as before.
Click to expand...
Click to collapse
This stable ver has many problems. It's hasnt stable yet. Even when you could turn the screen on, if you use the 3 buttons as default, everything is normal, but if you use fullscreen gestures and reboot your phone, you will stuck in black screen again. Many friends and me have the same black screen problems. So my advice is you should stay where you are waiting for a real "stable" ver.

For all who want to use FSG in version 10.1.2.0 I would recommend the following workaround:
a) Startup freshly installed system
b) Select navigation bar as preferred method and finish setting up the phone
c) Download Magisk v18.0
d) Reboot into TWRP and flash Magisk v18.0 zip
e) Reboot to system
f) Download the free application "Fluid Navigation Gestures" and setup the same Gestures as in Stock mi8
g)Optional: In Fluid NG, choose "Hide Navigation Bar"
It doesn't have the exact same feeling as stock but is pretty close and I think it's valid as a meantime workaround.