Database Develop

Booting problem

Hi
I'm having problems when turning on my galaxy note. I was using Paranoid Android J.B. and was playing Death Trigger happily when suddenly the screen started acting like an old T.V. I got scared so I exited the game and rebooted the phone and got stuck so I re restarted the phone by long pressing the power button but this time it didn't boot but only appeared quickly the galaxy note N-7000 screen and turned off.
At first I charged the phone thinking maybe it was low on battery but happened the same. Then I entered to recovery mode after pressing the buttons a longer than usual time and installed P.A. CM9. Everything was ok but 15 minutes later I ran off of battery and the phone turned off. I charged again the phone and after a few minutes I tried to turn on the phone but I couldn't because again all I got was a quick flash of the galaxy note screen.
I entered again on the recovery mode but this time I only selected the reboot phone option and it turned on as always.
Does someone knows what could it be or how to fix it?
Would you recommend me to install stock rom and unroot the phone just in case?
Thanks four your help

Hello perri.etb, you could first try another custom firmware and see if the exact problem persists. You could then try a stock firmware just to double-check.

YLNdroid said:
Hello perri.etb, you could first try another custom firmware and see if the exact problem persists. You could then try a stock firmware just to double-check.
Click to expand...
Click to collapse
That's why I installed Paranoid Android CM9. I have used it some time and know that it works perfectly but yeah, maybe installing a TW rom could work. I'll try.
Edit
I installed another rom and everything worked fine. Now I installed again P.A. CM9 and everything is fine.
Thanks.

perri.etb said:
Edit
I installed another rom and everything worked fine. Now I installed again P.A. CM9 and everything is fine.
Thanks.
Click to expand...
Click to collapse
Hello perri.etb, I am glad you have resolved the issue.

[Q] S3 Mini Does Not Turn On, Cannot Boot Into Recovery or Download Modes

I have seen a lot of threads on similar problems, but none of them seem to have a fix for me. So, here I am!
A few weeks back, I flashed a custom CM11 ROM to my phone, and it went through without a hitch. The phone did have a few problems, but the dev had mentioned that the ROM had a few bugs, so I didnt think much of it. The phone screen would turn off at random, and if i plugged in the phone while it was not turned on, it would get stuck at the loading screen that precede the battery animation. Like I said, I didn't make much of these.
The dev released the newest update yesterday, so I downloaded it, and when I tried to boot my phone into recovery, the s3 mini splash screen came up for a few seconds, then the phone turned off. This happened several times, even when I tried to turn it on in download mode.
I decided to use Terminal Emulator to turn on recovery, but when I tried to turn my phone on normally, the same thing happened (s3 mini splash screen, then turned off).
I saw other threads on the same matter, but they were mostly due to a pressed-in power button, or were solved with steps that didnt work out for me. Please advise!!!

polski691 said:
I have seen a lot of threads on similar problems, but none of them seem to have a fix for me. So, here I am!
A few weeks back, I flashed a custom CM11 ROM to my phone, and it went through without a hitch. The phone did have a few problems, but the dev had mentioned that the ROM had a few bugs, so I didnt think much of it. The phone screen would turn off at random, and if i plugged in the phone while it was not turned on, it would get stuck at the loading screen that precede the battery animation. Like I said, I didn't make much of these.
The dev released the newest update yesterday, so I downloaded it, and when I tried to boot my phone into recovery, the s3 mini splash screen came up for a few seconds, then the phone turned off. This happened several times, even when I tried to turn it on in download mode.
I decided to use Terminal Emulator to turn on recovery, but when I tried to turn my phone on normally, the same thing happened (s3 mini splash screen, then turned off).
I saw other threads on the same matter, but they were mostly due to a pressed-in power button, or were solved with steps that didnt work out for me. Please advise!!!
Click to expand...
Click to collapse
is it turnoff and keep restart or turnoff and never turn on ?

Ahmed.ragab said:
is it turnoff and keep restart or turnoff and never turn on ?
Click to expand...
Click to collapse
I have the same problem, since two weeks the phone was stuck on the pre-charging logo loading.
This morning the phone showed the same problem of polski, but i can boot in recovery and in download mode.
Every time i try to change something, the phone's situation worsens.
First the phone reboots 5 seconds after the system completely boots.
After a nandroid restore the phone was stuck in S3 mini logo
After that i tried another nandroid restore and it failed.
The phone keep restart, anyway.

Sorry for double-posting, anyway i tried a way to resolve and it had been successful.
I downloaded original firmware from samsung site (obiouvsly the correct one) and i flashed it with odin.
After that i re-flashed Maclaw's CM11 by odin and now the phone work well

HylianHero said:
I have the same problem, since two weeks the phone was stuck on the pre-charging logo loading.
This morning the phone showed the same problem of polski, but i can boot in recovery and in download mode.
Every time i try to change something, the phone's situation worsens.
First the phone reboots 5 seconds after the system completely boots.
After a nandroid restore the phone was stuck in S3 mini logo
After that i tried another nandroid restore and it failed.
The phone keep restart, anyway.
Click to expand...
Click to collapse
HylianHero said:
Sorry for double-posting, anyway i tried a way to resolve and it had been successful.
I downloaded original firmware from samsung site (obiouvsly the correct one) and i flashed it with odin.
After that i re-flashed Maclaw's CM11 by odin and now the phone work well
Click to expand...
Click to collapse
As u can go.to download.mode.. flashing full stock.firmware via odin will solve it

As i said
There's another problem now... the phone works well but there's no more the Samsung Splash screen but a crashed image (like static of TVs)

HylianHero said:
As i said
There's another problem now... the phone works well but there's no more the Samsung Splash screen but a crashed image (like static of TVs)
Click to expand...
Click to collapse
Flash param and image will be alright again.

tys0n said:
Flash param and image will be alright again.
Click to expand...
Click to collapse
The problem started with the GT-i8190N_param.tar flash

Ahmed.ragab said:
is it turnoff and keep restart or turnoff and never turn on ?
Click to expand...
Click to collapse
It turns off and never turns on. :\
I bought a new battery today to see if it fixes the problem, but it didnt. :\

polski691 said:
It turns off and never turns on. :\
I bought a new battery today to see if it fixes the problem, but it didnt. :\
Click to expand...
Click to collapse
if it didn't respond at all so it is a hard brick for sorry

Ahmed.ragab said:
if it didn't respond at all so it is a hard brick for sorry
Click to expand...
Click to collapse
I dont think I made myself clear.
The splash screen does show up, but then the phone turns off immediately afterwards.

polski691 said:
I dont think I made myself clear.
The splash screen does show up, but then the phone turns off immediately afterwards.
Click to expand...
Click to collapse
(can u access download mode if yes so try complete stock firmware via odin

polski691 said:
The splash screen does show up, but then the phone turns off immediately afterwards.
Click to expand...
Click to collapse
First of all do you have a Custom Recovery installed??
If you don't this won't work.
(This happened to me on my S3.
I was using pimp my ROM and upon reboot, turned of after splash screen)
My way to fix this was:
•Download another ROM (for your device) (using a PC or another Android Phone) move downloaded ROM to External SD Card
•Insert External SD card back into Galaxy S3 Android Phone (or you can move ROM file to Internal SD Card if your using a PC)
•Boot into recovery mode.
Turn phone off
Press & hold Power Button, Volume Up & Home Button.
•Factory Reset
•Flash ROM from External or Internal depending on way used.
•Reboot
•Profit
Sent from S3 Mini
Using XDA App

polski691 said:
I dont think I made myself clear.
The splash screen does show up, but then the phone turns off immediately afterwards.
Click to expand...
Click to collapse
Discharge battery using download mode and return to seller for refund or replacement!

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.

Bootlooping Stuck in Maintenance Boot Mode can't access TWRP recovery or Download Mode at times

No matter what 9 out of 10 times I can no longer access TWRP recovery and Odin Download mode.
I'm currently on GA Lineage 7.1.2, rooted G900V. I have magisk 20.3 installed.
I've been having to change roms android 7.1-10 constantantly over the past couple years due to instability. Today the rom I was on I could not close the screen manually with power button otherwise the advanced power options would show. It's a bug!
Now all of a sudden after doing a full wipe and installing another rom I went to back it up and got the maintence boot mode rather than TWRP. I have already done factory resets, flashed other roms, re-flashed TWRP and my firmware. All of this several times over!
When I do mange to get TWRP I do wipe everything and restore backups of roms. Sometimes in download mode it wont stay and within a few seconds it bootloops into maintence mode.
I have no idea why this is happening again but now it seems it might be permeanent? Ive seen this maintence boot mode thing before but switching to another rom and or getting rid of bad modules stopped it. But not anymore.
Any ideas what is causing this and what can I do? Is my S5 done for? I guess at this moment I should stay on the buggy rom I was trying to get rid of until I can do regular backups again.

Droid9684 said:
No matter what 9 out of 10 times I can no longer access TWRP recovery and Odin Download mode...
...Today the rom I was on I could not close the screen manually with power button otherwise the advanced power options would show. It's a bug!
Click to expand...
Click to collapse
Well a bad power button could explain all 3 problems.
Or are you saying that even when using the advanced Power menu it will not reboot in Recovery or Download mode?
Droid9684 said:
Now all of a sudden after doing a full wipe and installing another rom I went to back it up and got the maintence boot mode rather than TWRP. I have already done factory resets, flashed other roms, re-flashed TWRP and my firmware. All of this several times over!
Click to expand...
Click to collapse
That never happened on my S5 G900M. I'm curious: could take a photo of it using an other device and post it here please?
Using this XDA site search: site:forum.xda-developers.com/ sm-g900v maintenance mode you can find other G900V users with a similar problem.
One user posted this:
I ONLY
GET "Maintenance Mode Recovery Menu" Which has 3 options
1 Normal Boot
2 Factory Reset
3 Safe mode Boot
But Sadly and STRANGELY I CANNOT GET THEM TO WORK EITHER!!!
Click to expand...
Click to collapse
A troubleshooting step could be to flash the most recent stock Samsung for your G900V which will re-lock the bootloader, test thoroughly to make sure it works properly then unlock the bootloader following one the numerous threads on XDA about it.
FWIW my Galaxy S5 G900M LineageOS 17.1 build 2020-11-29 + Open GApps Pico build 2020-11-05 + Magisk 21.0 + Magisk Manager 8.0.3 + TWRP 3.4.0 recovery is running smoothly without any major bugs.
See [OFFICIAL] LineageOS 17.1 for Galaxy S5 klte + Variants
***

Sorry for late reply I been busy. So the problems are happening again off and on. I'm going to have to switch roms again because mine keeps soft rebooting itself and dropping SIM card at times.
Next time I get maintenance boot screen i'll try to take a picture of it. The thing is from the restart menu I have the option to boot into recovery. When I do it only sometimes goes into TWRP otherwise goes into the maintenance boot mode and I have seconds to make a choice Boot normal, safe mode and factory reset. None of which options work. Within seconds my phone boots itself. I have the same issue in download mode if i'm able to get into it within seconds reboots itself. So it's very hard to do anything with ODIN. I've re-flashed twrp and my firmware a few times but it takes hours sometimes to be able to due to the self rebooting phone. There is also the problem of when I power off the phone in menu options it shuts off then powers itself back on again. I may have a bad power button its been a couple years that I can remember changing it. But it broke to where I couldnt power off my phone. When trying to lock the phone the reset menu pops up sometimes other times it locks phone as it should. It would be a ton of work for me to switch to a stock rom and do all that crap over again. I mean I wasnt having this problem this constant until recently.
I'm staying on 7.1.2 because bluetooth and music are working. I was on 8.1+ bluetooth would always drop and music would stop working in background due to how background foreground processes changed after 7.1.2. Also the camera file location is messed up and not in DCIM it's located in a lineage file. Whenever I take pictures they are auto uploaded into my dropbox. It doesnt work on newer android versions after 8.1. I have the G900V Verizon maybe thats why i'm having all these problems. I know for sure the No sim is one of them on this device.
I dont plan to buy a new phone until next year and it will be a 5G one. It's too early to invest in one at this time since 5G is just slowly rolling out.

@curiousrom here are two photos of the S5 booting into recovery / maintence boot mode.

Droid9684 said:
@curiousrom here are two photos of the S5 booting into recovery / maintence boot mode.
Click to expand...
Click to collapse
Thanks for the photos.
So it seems it's a Bootloader Maintenance Mode, not recovery.
The first splash screen is the bootloader's which is named Aboot in the S5. See the attachments.
You installed a custom bootloader to unlock your S5 G900V & that's probably why it's acting up.
Ask in S5 G900V unlocking threads & includes those photos.
***

curiousrom said:
Thanks for the photos.
So it seems it's a Bootloader Maintenance Mode, not recovery.
The first splash screen is the bootloader's which is named Aboot in the S5. See the attachments.
You installed a custom bootloader to unlock your S5 G900V & that's probably why it's acting up.
Ask in S5 G900V unlocking threads & includes those photos.
***
Click to expand...
Click to collapse
Odd because I really dont have this problem often and yes that was the only way to unlock the bootloader on 6.0.1. Anyhow I ordered a new power button should arrive soon. That might help with it being sensitive it does look a bit pushed in. I noticed it seems to not boot into TWRP if I choose to go to advanced restart menu and choose to boot into recovery. When I manually do it after powering off i'm not having the problem. So maybe it's a bug with all the ROMs out there when choosing recovery from advanced restart menu options.

[HELP] Bootloop after trying to boot to recovery. Can't go anywhere

Hey!
I was using my phone as normal, and installed an update for PixelPlusUI, it was working fine and all, until earlier today, i tried going into recovery to fix an app issue. After that, the phone just bootlooped. I figured that going into Fastboot would fix that, but the problem is, i can't reach any of those modes. It just goes to the Redmi logo, reboots, and repeats that infinitely.
I heard about EDL mode, but that seems atleast so far, unreacheable.
Is there any way for me to reach it? Maybe by letting the battery dry out and then plug the powered off phone with Volume -, or am i out of luck here? Im pretty sure this is caused by the stupid VBMeta checks XIAOMI phones has.

Matsilagi said:
Hey!
I was using my phone as normal, and installed an update for PixelPlusUI, it was working fine and all, until earlier today, i tried going into recovery to fix an app issue. After that, the phone just bootlooped. I figured that going into Fastboot would fix that, but the problem is, i can't reach any of those modes. It just goes to the Redmi logo, reboots, and repeats that infinitely.
I heard about EDL mode, but that seems atleast so far, unreacheable.
Is there any way for me to reach it? Maybe by letting the battery dry out and then plug the powered off phone with Volume -, or am i out of luck here? Im pretty sure this is caused by the stupid VBMeta checks XIAOMI phones has.
Click to expand...
Click to collapse
Vbmeta means Android Verified Boot.
Vbmeta is default for all android devices and it was made by Google.
It is not specific made by Xiaomi.
Android Verified Boot 2.0
https://source.android.com/security/verifiedboot/avb
What changes did you do when you fixed the app issue?

Couldn't do any, just tried to boot into recovery, then got into that bootlooop cycle, couldn't reach anything.
Managed to get into EDL and SP Flash Tool mode, however, im a bit confused on what i need to flash to get it back to life with stock MIUI or atleast boot to main system to use ADB.
My IMEI is fixed on the phone stickers so i can reasily recover that aswell, any help is appreciated.
EDIT: Now i just need help flashing as it seems, what do i need to do to properly re-flash / re-boot the phone without losing IMEI and that sorta stuff? I plan on switching back to Pixel Plus UI again so, it isn't an issue.
EDIT2: Completely fixed, followed VD's guide on EDL/Mediatek Bypass method and flashed a normal GLOBAL rom, all was fixed, no IMEI lost.