Related
Hello, this is my second post here though I visit this forum quite frequently.
I have a p990, and I have encountered a very strange problem with my phone:
Until yesterday, everything was normal, and every couple of weeks or so I installed a new/updated rom via CWM without any problem (usually).
Yesterday I installed the CM7 Kang from Ricardo, and this also worked well. However, when I tried to install my previous rom again (Gueste 3.1, after 3 wipes of course. The reason I didn't go back to a nandroid backup was because of problem in making the last backup) it got stuck on the 2ng LG screen. the buttons are lighted when I touch the screen, but even waiting 30 minutes doesn't change anything.
Since then, I tried to install many different roms (the latest CM7 nightly and some others), and all gave me the same problem. The only things that I've been able to do in order to boot successfully was to revert to an old backup that I had, or to install MIUI, which did work for some reason.
When I tried to install the same version of CM9 again, I always got a boot loop.
Any idea as to what could cause such a strange behavior and how can it be fixed?
Sorry for the long post, I just wanted to give as many details as possible, and I'll be happy to give more details if I can if there are things that I forgot.
Thanks,
Beorn
Beorn1 said:
Hello, this is my second post here though I visit this forum quite frequently.
I have a p990, and I have encountered a very strange problem with my phone:
Until yesterday, everything was normal, and every couple of weeks or so I installed a new/updated rom via CWM without any problem (usually).
Yesterday I installed the CM7 Kang from Ricardo, and this also worked well. However, when I tried to install my previous rom again (Gueste 3.1, after 3 wipes of course. The reason I didn't go back to a nandroid backup was because of problem in making the last backup) it got stuck on the 2ng LG screen. the buttons are lighted when I touch the screen, but even waiting 30 minutes doesn't change anything.
Since then, I tried to install many different roms (the latest CM7 nightly and some others), and all gave me the same problem. The only things that I've been able to do in order to boot successfully was to revert to an old backup that I had, or to install MIUI, which did work for some reason.
When I tried to install the same version of CM9 again, I always got a boot loop.
Any idea as to what could cause such a strange behavior and how can it be fixed?
Sorry for the long post, I just wanted to give as many details as possible, and I'll be happy to give more details if I can if there are things that I forgot.
Thanks,
Beorn
Click to expand...
Click to collapse
Try this: go to recovery > mounts and storage and wipe system, data and cache, and flash your rom.
If wiping system doesn't work neither, catch a logcat when the phone bootloops
markop90 said:
Try this: go to recovery > mounts and storage and wipe system, data and cache, and flash your rom.
If wiping system doesn't work neither, catch a logcat when the phone bootloops
Click to expand...
Click to collapse
This fixed the same issue for me.
Wiped everything and flashed CM9. Works great (but battery drain is incredible!!!)
Solved!
markop90 said:
Try this: go to recovery > mounts and storage and wipe system, data and cache, and flash your rom.
If wiping system doesn't work neither, catch a logcat when the phone bootloops
Click to expand...
Click to collapse
Thanks, I did this, and now I was able to boot again with Gueste 3.1 (I'd rather wait for a bit more stable and mature version of CM9).
Actually, I did this thing twice, and it still didn't help, and in the third time I tried to make a logcat (I'm rather new to this logcat thing), and while trying to boot and make a logcat at the same time it suddenly started workind
I just hope that it will stay good now, and that I won't have this problem again in future flashes...
Thanks!
[SOLVED]
Sorry I keep posting things to myself and solving it on my own after hours -__-.. I already struggled hours beforehand and was frustrated..
Anyways, I went to CMW recovery mod, deleted the back up that I backed earlier. And then format/reset to factory mod / wipe partition / cache / Dalv. Then I went to boot my device but after 10 minutes, it'd still be loading cyanogen.... so I reinstalled the CyanogenMod9. Wiped all the things I mentioned above again and when it loaded to OS, it worked..
I have no idea what was causing it.. probably the back up file interfering somehow? Because that's the only thing I got rid of and everything went back to normal.
_________________
Hey guys, I successfully installed CyanogenMod 9 on my Gingerbread 2.3.5.
Everything is great and slick. I used to use CyanogenMod 7.
Funny thing is, I enabled the lock screen (pattern) and it seems to be not working? I don't know if I'm missing something but after leaving my phone for good 20 minutes, I came back to turn on (from sleep) and it wasn't asking for lock screen pattern. I tried slide too, same.
Also, from my previous versions, whenever I was in setting or any app, if I were to press on Home Button it would bring my back to main screen. My Home button no longer does this. I have no idea what it does now, I press it and the phone vibrates (indicates that its been pressed) but no effect. I have to literately press Back like 5 times just to return to Main menu.
Is there something I'm suppose to enable or something?
Let me know, thank you
-Dan
danroh said:
[SOLVED]
Sorry I keep posting things to myself and solving it on my own after hours -__-..
Click to expand...
Click to collapse
lol, hate when that happens
Hey danroh,
I had same issue with home button and lockscreen and this steps fixed problem:
1) I accidentally downloaded Jelly Bean gapps instead of ICS version
2) Reinstalled CM9
3) Downloaded experimental build and flashed that over stable one
4) Flashed with proper ICS gapps
5) Factory reset/Data wipe, Clear Dalvik cache
6) Reboot
-----
Hit thanks if that worked for you
HElp ME
hard2play said:
Hey danroh,
I had same issue with home button and lockscreen and this steps fixed problem:
1) I accidentally downloaded Jelly Bean gapps instead of ICS version
2) Reinstalled CM9
3) Downloaded experimental build and flashed that over stable one
4) Flashed with proper ICS gapps
5) Factory reset/Data wipe, Clear Dalvik cache
6) Reboot
-----
Hit thanks if that worked for you
Click to expand...
Click to collapse
IT didnt wok, maybe because i dont have the needed gapps. Do you have a link?
danroh said:
[SOLVED]
Sorry I keep posting things to myself and solving it on my own after hours -__-.. I already struggled hours beforehand and was frustrated..
Anyways, I went to CMW recovery mod, deleted the back up that I backed earlier. And then format/reset to factory mod / wipe partition / cache / Dalv. Then I went to boot my device but after 10 minutes, it'd still be loading cyanogen.... so I reinstalled the CyanogenMod9. Wiped all the things I mentioned above again and when it loaded to OS, it worked..
I have no idea what was causing it.. probably the back up file interfering somehow? Because that's the only thing I got rid of and everything went back to normal.
Click to expand...
Click to collapse
Weirdly, my brother's Galaxy S had the same thing. Home button just would not work after installing CM9. Tried a few things, failed.
Then, I found this thread and I remembered that I'd backed up his old CM7 a while before. Deleted that backup in CWM Recovery, factory wiped/cache wipe, reinstalled CM9 and Gapps for 9 and boom, everything was fine.
EDIT:
Another thing to note is that when the home button wouldn't work, there was no Lockscreen either, just like you had. On first boot it didn't prompt me for a google account either, which it did do after I deleted the backup.
hard2play said:
Hey danroh,
I had same issue with home button and lockscreen and this steps fixed problem:
1) I accidentally downloaded Jelly Bean gapps instead of ICS version
2) Reinstalled CM9
3) Downloaded experimental build and flashed that over stable one
4) Flashed with proper ICS gapps
5) Factory reset/Data wipe, Clear Dalvik cache
6) Reboot
-----
Hit thanks if that worked for you
Click to expand...
Click to collapse
hey man!!..thnx for your guide...i w as actually in great trouble coz of this error..nd now its fixed!!...thnx a lot!!...
Hello,
I am a noob trying to install a rom with aroma installer. But now it has been stuck at the page where it says: The installation wizard has successfully installed *********. Press next to exit.
What do i do? Power off?
Is it definitely stuck? Aroma doesn't always recognise touch events very accurately, and I usually have to tap the "next" button a few times before it registers. Failing that, if it's finished installing whatever you flashed, you should be fine to reboot manually anyway.
Yes,i have tried to push the next button many times but nothing happens. It has been like this for 30 minutes now. The successfully installed text appeared very fast, a second or two maybe after the previous screen. So if it has installed the rom, it was def a fast install.
Anyway, is it safe to try to reboot, even if it was in the middle of the install? Rebot to recovery and try again?
Well, there certainly isn't anything else to be done besides rebooting. I don't know what you were trying to install - if it was a several-hundred-MB ROM, as most things that use Aroma are, you would expect it to take a while. Smaller things can be flashed very quickly. If it _did_ go wrong somewhere, there are a few things:
1. What recovery, and what version thereof, are you using?
2. Did you wipe data before using the installer?
3. Most of all, what were you trying to install? There might be some known issue with certain configurations.
I wouldn't necessarily expect a working OS when you reboot, depending on what you were trying to install and how badly things went wrong, but you should be able to get back into recovery easily enough.
Thank you for your quick reply.
1. I use the CWM recovery in this http://forum.xda-developers.com/showthread.php?t=1914394 thread, not the newest, but 5.5 something i believe.
2. Yes, wiped all data + dalvik.
3. I was trying to install rXTREME on my SGS III lte i9305.
I've rebooted now, and everything works perfect as the phone was before i tried to do the install. No brick. I also tried to flash it one more time, but stuck at the same place again. Rebooted fine at stock rom again. Maybe i should take this as a hint that someone else should be put at the steering wheel.. :laugh:
EDIT: forgot link above
Found out what the problem was.
In Aroma Installer i selected EFS backup both times. The third time i tried i did not do this. And everything went fine. Runs smooth.
my galaxy s3 international version got stuck at 30% of formatting\data partition while trying to flash s4 revolution 4.1 rom
what should i do?
jehad.drarjeh said:
my galaxy s3 international version got stuck at 30% of formatting\data partition while trying to flash s4 revolution 4.1 rom
what should i do?
Click to expand...
Click to collapse
This is I9305 forum is this your phone ??
This thread is about Aroma installer is that your problem ???
Suggest you read the basic faqs and guides first looks like from your post you are either flashing wrong rom to your phone or have hijacked a thread in the wrong forum ./
jje
Hi. I'm unexperienced with this in general, so please bear with me. I treid to search similar threads but didn't find anything about my problem exactly.
I've a rooted European (Exynos, Polish or German distribution) version of Note 4. I don't run any custom OS nor did I make any changes to my phone in the last few months. As of now, it's running Lollipop.
A few weeks ago, my phone started randomly rebooting. I blamed it on old apps, did a check with antivirus and uninstalled some apps I wasn't sure about. But the problem grew worse (reboot every few minutes). I've erased all apps that had something to do with my root (Lucky Patcher was constantly popping up in my SU logs in the same minute my phone rebooted, so I uninstalled all patched app and then Lucky Patcher), deleted almost everything, checked that system apps were all the newest version. Nothing helped so I thought a factory reset seems like the best option now. I went to the Settings and did a factory reset.
But now I'M STUCK. There is this picture of the Android with the blue web that should be turning (but isn't) the screen says "Systemupdate wird installiert" (system update is installing), the picture disappears (black screen) and comes back every few seconds. There is no blue line signalising progress or anything. All this for some two hours now.
I don't want to try anything myself because I don't want to make my phone a brick. Does any of you know what my problem could be? Thanks.
I'm not too sure why your device is stuck in an update loop. But are you positive you havent tried flashing anything to your device??
---------- Post added at 05:28 PM ---------- Previous post was at 05:23 PM ----------
Wait a second, you're saying you arent running a custom rom, yet your device has root with superuser.. Therefore you should also have a custom firmware flashed to your device.. Twrp or cwm. Irecommend twrp. If you have a custom recovery. Then boot in to recovery mode and clear cache/dalvik wipe/ factory reset etc.
TheTecXpert said:
I'm not too sure why your device is stuck in an update loop. But are you positive you havent tried flashing anything to your device??
---------- Post added at 05:28 PM ---------- Previous post was at 05:23 PM ----------
Wait a second, you're saying you arent running a custom rom, yet your device has root with superuser.. Therefore you should also have a custom firmware flashed to your device.. Twrp or cwm. Irecommend twrp. If you have a custom recovery. Then boot in to recovery mode and clear cache/dalvik wipe/ factory reset etc.
Click to expand...
Click to collapse
Positive I haven't flashed anything. I didn't even connect it to a computer.
I think that my device has cwm but it's long since I've used it. I tried getting into recovery mode and the only thing I can see is the android figure with the blue ball, no menu, no anything.
UPDATE: I flashed twrp with ODIN, phone rebooted like after a factory reset.
keinalu said:
Hi. I'm unexperienced with this in general, so please bear with me. I treid to search similar threads but didn't find anything about my problem exactly.
I've a rooted European (Exynos, Polish or German distribution) version of Note 4. I don't run any custom OS nor did I make any changes to my phone in the last few months. As of now, it's running Lollipop.
A few weeks ago, my phone started randomly rebooting. I blamed it on old apps, did a check with antivirus and uninstalled some apps I wasn't sure about. But the problem grew worse (reboot every few minutes). I've erased all apps that had something to do with my root (Lucky Patcher was constantly popping up in my SU logs in the same minute my phone rebooted, so I uninstalled all patched app and then Lucky Patcher), deleted almost everything, checked that system apps were all the newest version. Nothing helped so I thought a factory reset seems like the best option now. I went to the Settings and did a factory reset.
But now I'M STUCK. There is this picture of the Android with the blue web that should be turning (but isn't) the screen says "Systemupdate wird installiert" (system update is installing), the picture disappears (black screen) and comes back every few seconds. There is no blue line signalising progress or anything. All this for some two hours now.
I don't want to try anything myself because I don't want to make my phone a brick. Does any of you know what my problem could be? Thanks.
Click to expand...
Click to collapse
There is a chance that you put your phone in odin download mode instead doing factory reset
keinalu said:
UPDATE: I flashed twrp with ODIN, phone rebooted like after a factory reset.
Click to expand...
Click to collapse
So you got it working now? Or?? You mean rebooted successfully? Or rebooted back in to download mode?
TheTecXpert said:
So you got it working now? Or?? You mean rebooted successfully? Or rebooted back in to download mode?
Click to expand...
Click to collapse
There seems to be no problem now, my phone went back from 5.1 to 5.0.1 though. Maybe the whole thing started because of the last update. I tested and I can get to recovery mode normally, so I did a back-up just in case somethin goes wrong again.
If you managed to flash twrp and successfully booted back in to your device, then i recommend rebooting back into twrp recovery, and doing a cache and dalvik cache from within the recovery menu. And if you want root access, download the latest superSU (itll be a zip file), copy the file to the download folder of your internal storage, reboot in to your recovery, install the superSU zip file you downloaded, once its indtalled, wipe both caches again. And reboot.
Let me know how you go, and if you get stuck somewhere, dont be afraid to ask. Im happy to help
Hello! My Galaxy note 5 (SM-920G) has been stuck on a boot loop for a week now, I've tried everything. I've used "wipe cache partition", "Wipe data/factory reset", even flashed stock firmware from sammobile using odin. I'm still stuck on a bootloop. I am gonna proceed to explain the events that occurred before and after the bootloop in a level of detail that I'm capable of, also one that I think should be sufficient.
Events before the bootloop:
So here's what happened. I was using my phone as usual when I noticed that I couldn't play any music. Spotify, which I was using at the time, refused to play any song. So, I checked out Phonograph(music app that uses local library) and I couldn't seem to play anything from my local library either. I then proceeded to go ahead and open YouTube only to realize that I couldn't play a video on YouTube either. After much fiddling (I don't remember what exactly I did that caused it) but a YouTube video played, but I heard no sound. From here on out, I could PLAY/VIEW any media related file and such but I heard no sound. I searched it up and apparently a cache partition wipe seemed to do the trick (I should have dug deeper into this but this is what I found). I proceeded to the recovery menu and selected "Wipe Cache Partition" (Forgive me, memories a little fuzzy from here on), If I recall correctly, I got into a bootloop and I wiped the cache partition again and it booted up fine. However, there was still no sound, since it was late at night I decided to give up and go ahead and sleep for now.
The next day, when I woke up, everything was working perfectly. I had no idea why.. but hey, I wasn't about to complain. Fast forward a few days, the sound issue popped up again, so I proceeded to wipe the cache partition again. I repeated this a few times but it didn't work, so I gave up. My phone was booting perfectly fine then. During the course of a week or so (maybe less) I had done quite a few cache partition wipes hoping that it would fix the sound issue. I also tried calling someone, only to figure out that person on the other end couldn't hear me and I couldn't hear them. So, one of these days when I did the whole cache partition wipe, my phone wouldn't boot up. This is where it got stuck in a bootloop.
Events before the bootloop:
So yeah, my phone was stuck in a bootloop. If I remember correctly I used the "cache partition wipe" a lot and even opted for the factory reset option. Which didn't work out either. I finally opted to flash stock rom today but over the course of some days I have been trying a combination of "cache partition" wipe and factory resets. Of course, my attempts were in vain. SO, I decided to flash stock rom today. I found the firmware I needed and used Odin to flash it on my phone and that didn't work either, still stuck on the bootloop. I tried a factory reset and cache wipe after the flash as well.
Relevant images:
1- Screen I'm stuck on
2- When I go to recovery mode, first screen that pops up.
3- The so called update fails, second screen that pops up
4- and finally the recovery menu pops up
So yeah, that's it. I'm currently in the midst of my A level's, so my days are pretty hectic and stressful. I apologize for the long post, first time making a thread on XDA. Please help ;-;
maskimmortalsucks said:
Hello! My Galaxy note 5 (SM-920G) has been stuck on a boot loop for a week now, I've tried everything. I've used "wipe cache partition", "Wipe data/factory reset", even flashed stock firmware from sammobile using odin. I'm still stuck on a bootloop. I am gonna proceed to explain the events that occurred before and after the bootloop in a level of detail that I'm capable of, also one that I think should be sufficient.
Events before the bootloop:
So here's what happened. I was using my phone as usual when I noticed that I couldn't play any music. Spotify, which I was using at the time, refused to play any song. So, I checked out Phonograph(music app that uses local library) and I couldn't seem to play anything from my local library either. I then proceeded to go ahead and open YouTube only to realize that I couldn't play a video on YouTube either. After much fiddling (I don't remember what exactly I did that caused it) but a YouTube video played, but I heard no sound. From here on out, I could PLAY/VIEW any media related file and such but I heard no sound. I searched it up and apparently a cache partition wipe seemed to do the trick (I should have dug deeper into this but this is what I found). I proceeded to the recovery menu and selected "Wipe Cache Partition" (Forgive me, memories a little fuzzy from here on), If I recall correctly, I got into a bootloop and I wiped the cache partition again and it booted up fine. However, there was still no sound, since it was late at night I decided to give up and go ahead and sleep for now.
The next day, when I woke up, everything was working perfectly. I had no idea why.. but hey, I wasn't about to complain. Fast forward a few days, the sound issue popped up again, so I proceeded to wipe the cache partition again. I repeated this a few times but it didn't work, so I gave up. My phone was booting perfectly fine then. During the course of a week or so (maybe less) I had done quite a few cache partition wipes hoping that it would fix the sound issue. I also tried calling someone, only to figure out that person on the other end couldn't hear me and I couldn't hear them. So, one of these days when I did the whole cache partition wipe, my phone wouldn't boot up. This is where it got stuck in a bootloop.
Events before the bootloop:
So yeah, my phone was stuck in a bootloop. If I remember correctly I used the "cache partition wipe" a lot and even opted for the factory reset option. Which didn't work out either. I finally opted to flash stock rom today but over the course of some days I have been trying a combination of "cache partition" wipe and factory resets. Of course, my attempts were in vain. SO, I decided to flash stock rom today. I found the firmware I needed and used Odin to flash it on my phone and that didn't work either, still stuck on the bootloop. I tried a factory reset and cache wipe after the flash as well.
Relevant images:
1- Screen I'm stuck on
2- When I go to recovery mode, first screen that pops up.
3- The so called update fails, second screen that pops up
4- and finally the recovery menu pops up
So yeah, that's it. I'm currently in the midst of my A level's, so my days are pretty hectic and stressful. I apologize for the long post, first time making a thread on XDA. Please help ;-;
Click to expand...
Click to collapse
Was that Lollipop or MM 6 that you were on? In Download mode what does it say on that screen? Is FRP enabled?
P.S what country are you in?
Before flashing in odin do the format in recovery.
Sent from my SM-N9208 using XDA-Developers mobile app
MrMike2182 said:
Was that Lollipop or MM 6 that you were on? In Download mode what does it say on that screen? Is FRP enabled?
P.S what country are you in?
Click to expand...
Click to collapse
I could have sworn I replied to this... I can't seem to post any links here. I pm-ed the images to you! Frp was on, yeah. I was on Marshmallow. I live in the Maldives.
maskimmortalsucks said:
I could have sworn I replied to this... I can't seem to post any links here. I pm-ed the images to you! Frp was on, yeah. I was on Marshmallow. I live in the Maldives.
Click to expand...
Click to collapse
I'm pretty sure I replied to your private message already. On the picture you showed me it said the CSC was SLK and I gave you the link to the correct firmware for the device
You can also download the firmware to flash through odin here too.
https://samsung-firmware.org/download/Galaxy Note 5/9hs6/INS/N920GDDS2BPD2/N920GODD2BPC3/
You can't post any links because you don't have enough "posts" on here yet to prove you're not just coming on here to post some crazy links lol.
MrMike2182 said:
I'm pretty sure I replied to your private message already. On the picture you showed me it said the CSC was SLK and I gave you the link to the correct firmware for the device
You can't post any links because you don't have enough "posts" on here yet to prove you're not just coming on here to post some crazy links lol.
Click to expand...
Click to collapse
Alright so, my cousin somehow managed to get rid of the bootloop with some fiddling and the audio issues still remained. So, he tried to downgrade to 5.1.1 by downloading the firmware for it and the phone got stuck in another bootloop. Tried to flash 6.0.1 again and it didn't work, still stuck on bootloop.
I tried what you have suggested but I can't seem to get into the recovery menu.
maskimmortalsucks said:
Alright so, my cousin somehow managed to get rid of the bootloop with some fiddling and the audio issues still remained. So, he tried to downgrade to 5.1.1 by downloading the firmware for it and the phone got stuck in another bootloop. Tried to flash 6.0.1 again and it didn't work, still stuck on bootloop.
I tried what you have suggested but I can't seem to get into the recovery menu.
Click to expand...
Click to collapse
Already replied to your private message.
Can you not select this directly after odin...
Flush twrp for yours model go to recovery then wape os and every think then flush firmware by odin
Sent from my SM-N920C using XDA-Developers mobile app