Hi guys, I've recently installed MIUI 1.11.11, and this friday there was an 1.11.18 update listed in the updater app which was already included.. I opened it, did a backup with the app and after that I downloaded the latest release and pushed UPDATE after that, and it went into reboot, then phone rebooted, I got into GALAXY S GT-I9000 screen, shortly after I got GALAXY S Cyanogen(mod) screen and shortly after that it went loading something for a quick second, then just rebooted, and then the phone started normally, I thought that was it, but when it loaded to the lockscreen I checked the version and it was still 1.11.11, so clearly something went wrong.. I did that several times after, but I get the same result everytime..
Looks to me like bootloops.. Bootloops gave me some problems while installing 1.11.11 in the first place, was stuck in bootloops in the middle of the installation of the rom until I pressed the three buttons to go into recovery mode and selected install .zip once again.. then it went through without a problem. Also I had no other problems with this rom so far..
So if anyone knows what could be wrong here, or what I could be doing wrong, so I can update I would really appreciate your help..
I recorded my screen. Recording has everything I did, nothing more nothing less, only after I stopped recording I pushed UPDATE in the updater as it clearly can't record screen while phone is rebooting.. Check it, I hope it helps with the problem.
The video is on youtube under -> watch?v=J01LpijBJ7c
Lumix357 said:
Hi guys, I've recently installed MIUI 1.11.11, and this friday there was an 1.11.18 update listed in the updater app which was already included.. I opened it, did a backup with the app and after that I downloaded the latest release and pushed UPDATE after that, and it went into reboot, then phone rebooted, I got into GALAXY S GT-I9000 screen, shortly after I got GALAXY S Cyanogen(mod) screen and shortly after that it went loading something for a quick second, then just rebooted, and then the phone started normally, I thought that was it, but when it loaded to the lockscreen I checked the version and it was still 1.11.11, so clearly something went wrong.. I did that several times after, but I get the same result everytime..
Looks to me like bootloops.. Bootloops gave me some problems while installing 1.11.11 in the first place, was stuck in bootloops in the middle of the installation of the rom until I pressed the three buttons to go into recovery mode and selected install .zip once again.. then it went through without a problem. Also I had no other problems with this rom so far..
So if anyone knows what could be wrong here, or what I could be doing wrong, so I can update I would really appreciate your help..
I recorded my screen. Recording has everything I did, nothing more nothing less, only after I stopped recording I pushed UPDATE in the updater as it clearly can't record screen while phone is rebooting.. Check it, I hope it helps with the problem.
The video is on youtube under -> watch?v=J01LpijBJ7c
Click to expand...
Click to collapse
I'm finding the same issue. Help please!
Related
Hi, I'm quite upset and I don't really know what to do. You see, I bought I Nexus One and since I'm a computer tech (Network is my strong point and I also got a Professional diploma of informatics support)I thought I could go and mod my thing out. Thing is everything worked fine until I downloaded Cyanogen with Rom Manager Premium (Crack3d)and tried to install it. At first it simply shut down the screen, rebooted a few times and restarted normally, then I retried downloading and it brought me to the reboot in recovery mode to install cyanogen popup. Clicked ok and then it rebooted another 3-4 times and when it came back, it was cyanogen splash screen bugging and rebooting in the middle of the loading. I have Android SDK if that changes anything, I just really don't even know how to bring any sort of menu from my pc or my phone.
P.S. I didn't cleared cache and didnt do any backup[thats no that important].
Thanks
-Ed
Hey xda.
Recently I flashed my GS with this rom (http://forum.xda-developers.com/showthread.php?t=1449156&page=), but just in a older version(pre-alpha) and after probably a month of use I began to experienced at lot og bugs and suddenly crashes in apps and programs. I decided to do a reboot,battery pull or wipe cache to see if that clould do it, but nothing help. On the contrary, my phone would not start. The Galaxy S logo showed u, but when the miui xiaomi.com logo showed it bootlooped. Several reboots did not work, so i decided to mount usb from recovery and download the newest version of the rom and then try to flash. I did not wipe, but i worked just fine and i thought i had my phone back, but after little over a day of use the screen began to flicker and blink, and no programs nor apps worked, just crashed. I flashed again again but nothing worked, and now i'm stuck with the same problem as before. bootloop..
So have anyone experienced the same or does anyone have a solution for this problem?
Hi guys,
Really sorry to ask about this but tearing my hair out!
I have a P6200 UK model. I installed CWM v6.0.1.0 and it worked fine. The intention was to install Galaxy ROM HD (build #06), so I downloaded it, put it on my SD card, and installed from CWM recovery. The install got stuck on "Flashing boot" - so after around 15 mins I reset it.
It went into a boot loop on the initial Samsung logo. Luckily I'd previously re-flashed stock HC with Odin (to cure a dead Wifi problem caused by, I think, an errant install of Busybox) so I did this again, rebooted, and the system came up, text started scrolling up the screen, followed by a red error message (see picture) and a reboot. I was then once again stuck on the initial Samsung Tab 7.0 Plus log. I repeated the process and it didn't even get past the Samsung logo.
So I thought I'd try the newly released ICS Rom (GT-P6200_ATO_P6200XXLQ1_P6200OXALQ1) - this seemed to install OK, then half booted, did some text type installation stuff with the blue Android, then rebooted again, finally getting stuck on the Samsung logo with blue pulsating behind it. It never gets any further than that.
I tried flashing HC back - same result as earlier. I can also reflash CWM and sometimes it works, sometimes it doesn't. It seems I've run out of options.
So - question is - where (if anywhere!) can I go from here?
Help greatly appreciated, many thanks!
have you tried a system wipe in cwm? if not do a system wipe and reflash HC using odin.. same thing happen to me 2 days ago.. I think something is up with HD rom
Hello. I Was wondering if someone can help me with a dilemma......... i recently got my mega a month ago. I then decided to root my mega (As i do with all my android devices)The rooting process worked out great. The phone booted.....Everything's all peachy! root was successful! After about 3 weeks i wanted to record my screen. By the way i was running kitkat on my mega. So i installed a screen recording program. i wanted to record the screen so i started the recording..... but it wasnt recording. it kept saying an error message i think it when like gpu is not supported and change to cpu something like that! i thought nothing of it... so i changed the settings to gpu then to cpu (Not knowing what i was doing) after it failed to record again i threw the towel in and quit. i then played one of my mobile games(FNAF2) after i lost the game i went back to the homescreen and the homescreen was acting up... it was in landscape mode when i had the phone upright. it was bugging me to the point where i just rebooted my device. i tried rebooting my device BUT IT WAS IN A BOOTLOOP! i had no idea what was going on. So i tried to restore the backup and it was restored but it was still in a bootloop. at this point i was freaking out! when i went home that day i put the device in download mode and flashed the stock firmware but it failed and didnt work. but when the phone rebooted it booted up and my phone was on activation screen and it was in a different language. then i soon found out that my touchscreen wasnt responding! neither was the home button or back button. i really dont know whats going on. kies does not work i tried emergency firmware initializing and kies didnt read it i tried reinstalling kies and my phones drivers 4 times and it was a no go...... but i finally found a english firmware and i flashed it but it failed and said something like dev_not supported or something so that didnt work either..... i booted up my phone and the language was back to english and my touchscreen wasnt working neither was my home buttons or anything. i also tried installing custom roms but everytime i try to install them it says it completed installing but when i boot up my phone its the same activation screen. i really need help anything that can help will be greatly appreciated. also everytime i boot up it always says set warranty bit:Kernal
Hi everyone,
Someone asked me to fix his phone and i'm stuck. The S7 is crashing randomly (black screen) and after a crash, it cannot be booted until the battery is dead (even by pressing power +home or power + vol-) and charged again. I don't know how to fix it and i'm stuck at this point.
Here is the story behind it :
The phone wrote the famous "moisture" message and then won't boot up. He never put it in water. So he put it in rice but it didn't work. The owner of the phone took it to a fixing store in Thailand where they changed the battery. After a day, the phone crashed and we send it to Samsung Thailand who told us a high cost without explanations so they didn't fix it and we got it back.
Hopping someone can help me about this problem :angel:
Update :
A deep-clean flash () got me stuck into "no command" and pushing vol+/vol-/home didn't change anything, it just bootlooped.
So then i tried installing TWRP 3.1.1, it's a success but after installing LineageOS 14.1 and booting the phone crashed at bootlogo and won't boot up again...
Another Update :
I finally managed to get it working saturday, but it crashed just today and it's the same. It crashed in a lightweight app with no app running in the background. I'm thinking of a material problem :/
New update, still hoping someone know how to fix this:
I tried to flash stock firmware over and over but it keeps crashing at the end of the boot animation... I'll try an oreo firmware, hope it'll fix it