Hello,
I flashed CM11 yesterday and everything went alright. This morning I noticed I had an update for it and proceed to do it.
After the instalation and optimizing all apps it asked me for my simcard PIN and after I unlocked the phone it just went back to the cyanogenmod logo over and over.
I tried to reboot phone but it didn't help.
I've tried to search for similar threads but since i'm a newbie (first time I ever flashed anything) to this I decided to create this thread.
What should I do?
Thank you!
try to use flashtool. google it on how to use flashtool or check other threads.
So I guess i have to flash a stock ROM with flashtool and do it all over again right?
And btw, any reason you guys might think It got stuck in bootloop after I updated CM11? I came from a fresh stock rom. I'm kinda scared it might happen again after the reinstall.
Can't you enter recovery to flash a nandroid backup? (If you have one)
If not, you have two options to choose from.
Fastboot or flash a kernel with CWM or TWRP.
ADB push a zip file of a ROM and flash that.
Flash an FTF file using flashtool and start all over again.
There are many reasons why you're stuck in bootloop at the moment.
With the info you provided, there's no way of telling what caused it for you.
Well, i flashed stock ROM with flashtool, installed CM11 and I had no problems.
Went to settings and OTA update was available. Downloaded it and installed it, stuck in loopboot again. I just can't figure out what's wrong. My phone has bootload unlocked.
Might just do it all over and not update, is that a problem?
Don't use OTA, just download and flash updates manually using recovery.
In the future, for your ease, if this happens again just wipe the phone very clean (cache, /system, /data etc except /boot) and then re-flash the CM zip that you have.
It is a good practise if you make a nandroid backup before flashing a newer version of zip, in case of breaks. Or, you can have Titanium Backup to backup your apps automatically (pro version) everyday, so that you can be ready if there will be something bad happen.
Related
Hello everybody!
I used to have a working stock firmware 2.67 Android 4.2.2, but I decided to unlock my bootloader.
I did the operation twice and then I encountered bootloop issue.
I downloaded a stock firmware and flashed it using Androxyde Flashtool.
Oh god! The firmware FTF file was corrupted.
I AM sure that it was corrupted.
Next up, I booted my device but it won't let me inside: Just the SONY screen and a black screen and afterwards and it goes off.
Then I flashed CWM Recovery as a boot.img file. After that I entered (luckily!) the CWM recovery, Cleaned Cache and performed Hard reset and installed the CyanogenMod 10.2 Yuga Nightly (or sth like that) as a zip. It said that it had been successful.
Despite that, when I rebooted device through CWM, I got the CyanogenMod boot screen( a blue orbit moving around) and it shows that forever!
What is wrong with my smartphone?
How can I fix this thing without a fresh installation of the stock firmware?
And if you flash cm again without wipe data?
Do you tryed to flash only an other kernel?
Tipp: always do Backups before flashing new CFWs.
i recently flashed the eXistenZ Ultra 2, and im sure i did everything fine, after flashing the rom in recovery and flashing suprsu and wifi fix, i powered off the phone, and powered on but sony logo has apeared until now , and welcoming`s sounding 999..times. i cant turn it off, or i should say i cant do anything.
please help,
After flashing ROM and the fixes you should flash the 12.1.A.0.266 Firmware with FlashTool!
If problem still persists:
http://xda-university.com/as-a-user/how-to-recover-from-a-bootloop
Take a look at this site A recovery would be quite useful, but I think the kernel of eXistenZ ROM has one. If not, you'll find one in the development section. Otherwise, use the ADB as solution.
Good luck
Thanx for the post!
I used force shut down and then flash the 254 rom, and did all those things, and the problem occured again.
does the recovery software have to be the touch recovery? I use CWM v6 that enables with volume +.
and i use SuperSU fix.zip rather than superUser.zip and generally i flash rom, supersu fix.zip and wifi fix.zip. i flashed those three, before first booting, do i have to boot first before flashing wifi fix.zip?
eefathi said:
Thanx for the post!
I used force shut down and then flash the 254 rom, and did all those things, and the problem occured again.
does the recovery software have to be the touch recovery? I use CWM v6 that enables with volume +.
and i use SuperSU fix.zip rather than superUser.zip and generally i flash rom, supersu fix.zip and wifi fix.zip. i flashed those three, before first booting, do i have to boot first before flashing wifi fix.zip?
Click to expand...
Click to collapse
I think you need to flash 12.1.A.0.266 instead of 12.0.A.2.254 after flashing ROM. You could also wipe data, cache and dalvik cache, reflash eXistenZ ROM and SuperSU fix (or SuperUser but SuperSU should be ok), shut down the phone with the option in recovery and then flash the 12.1.A.0.266 with FlashTool.
It doesn't matter which recovery you take. Use the one you like best. I'm not quite sure, but to go sure, please flash the wifi fiz.zip after first boot up!
Schokonuss said:
I think you need to flash 12.1.A.0.266 instead of 12.0.A.2.254 after flashing ROM. You could also wipe data, cache and dalvik cache, reflash eXistenZ ROM and SuperSU fix (or SuperUser but SuperSU should be ok), shut down the phone with the option in recovery and then flash the 12.1.A.0.266 with FlashTool.
It doesn't matter which recovery you take. Use the one you like best. I'm not quite sure, but to go sure, please flash the wifi fiz.zip after first boot up!
Click to expand...
Click to collapse
thanx again,
i flashed the 266 kernel before the first boot, and the rom runs correctly,
but ive got some new problems:
1. performance, when i click on performance, it closes unexpectedly and says it has stopped.
2. i used go backup for backing up from data in 4.1, but in this rom i restored my apps,the apps installed correctly but goBackup says the data restoring successfully finished , but the data didnt restored, by the way at the time i backed up from my apps&data, i swapped memories with that linux code that this forum did.
eefathi said:
thanx again,
i flashed the 266 kernel before the first boot, and the rom runs correctly,
but ive got some new problems:
1. performance, when i click on performance, it closes unexpectedly and says it has stopped.
2. i used go backup for backing up from data in 4.1, but in this rom i restored my apps,the apps installed correctly but goBackup says the data restoring successfully finished , but the data didnt restored, by the way at the time i backed up from my apps&data, i swapped memories with that linux code that this forum did.
Click to expand...
Click to collapse
You're welcome
1. Do you have SuperSU installed? On AOKP ROM I'm running it asked for superuser permission for ROM Control (the control center implemented in the settings of the ROM). Maybe it'll ask you if SuperSU is installed. Otherwise, because it is after the first boot it needs to rebuild cache and so on.. If problem persists after reboot, just use an other clock speed controler (No-frills CPU, SetCPU..)
2. If you did that at the same time, maybe Go Backup didn't really backup your data. Try again, if it doesn't work and if you have a nandroid backup (backup from recovery) you can go into recovery, then to advanced restore and restore data. Otherwise your data is unfortunately gone I think :/
PS: I prefer Titanium Backup
Hi, device is rooted, and clockworkmod recovery 6.0.4.5 installed.
ROM is JB, the official update from LG. Today device reported there is an update to the installed firmware.
I rebooted in CM recovery, took a nandroid backup, booted, and accepted to download the official update to my official JB rom. After downloading I was asked to reboot (in order to install), and the phone reboots to the CM recovery.
From there I don't know what to do. I have tried rebooting, but again find myself to the CM recovery. I have tried "reboot to bootloader" and get stuck at the LG boot screen logo with the message "Now Ready!" in tiny white letters on the upper left corner.
I would try "install zip" but I don't know where the downloaded update is (if it even is in an acceptable zip format)
Phone isn't bricked, I guess I can always restore from the recently taken backup, but I really would like to know if there is a way to install this update.
Thank you
http://forum.xda-developers.com/showthread.php?p=50645445
Could you please please please try to search the next time I've seen this question for probably 3-4 times
Sent from my LG-P880 using xda app-developers app
you can't ota over unlocked bl/cwm, you must flash update manually
moneyvirus said:
http://forum.xda-developers.com/showthread.php?p=50645445
Could you please please please try to search the next time I've seen this question for probably 3-4 times
Click to expand...
Click to collapse
You're right, but you know, sometimes you just can't nail the right keywords especially if its not your native language. I searched, but obviously not good enough.
Rudjgaard said:
you can't ota over unlocked bl/cwm, you must flash update manually
Click to expand...
Click to collapse
Sadly, this seems to be the case.. bummer.
Thanks everyone
Not even my nandroid backup can help me get to where I was before? So much for nandroid being the ultimate backup, a "snapshot image" of the device...
So, what if, I use CM recovery to install a custom rom, and then restore from my nandroid backup (being the official JB) ?
Flash with kdz flasher original ROM then flash cwm you can put back your backup. I think the problem starts that the update pushes something in the boot section that is expecting an other (read original) recovery . when you installed cwm it boots up cwm so that's why an nandroid backup doesn't work I think ( to be honest I'm not 100% sure this is correct)
Sent from my LG-P880 using xda app-developers app
I can't even flash cyanogenmod???
I downloaded latest stable build, copied it to sd card, selected it from the CM recovery ("install zip"), installed fine, reboot, still stuck at CM recovery!!!
What gives?
EPa said:
I can't even flash cyanogenmod???
I downloaded latest stable build, copied it to sd card, selected it from the CM recovery ("install zip"), installed fine, reboot, still stuck at CM recovery!!!
What gives?
Click to expand...
Click to collapse
Have you yet followed the advice and installed the KDZ?
Trying to avoid that, as it seems too much work for a phone that was working fine, and stuck to recovery due to some silly boot flag or something.
Saw it as a chance to try cyanogenmod. But it seems having CM recovery and the cyanogenmod rom on the sd card won't cut it! Talk about failure..
EPa said:
Trying to avoid that, as it seems too much work for a phone that was working fine, and stuck to recovery due to some silly boot flag or something.
Saw it as a chance to try cyanogenmod. But it seems having CM recovery and the cyanogenmod rom on the sd card won't cut it! Talk about failure..
Click to expand...
Click to collapse
I don't think you will have a choice. If you created the nandroid backup on your SD card then you aren't going to lose it, so just flash the KDZ, root again and install your backup, or accept the LG update and rebuild all your software again.
Yes, one thing is for sure. I had to install the KDZ to be able to proceed with anything..
It's just funny having a working CWM recovery and a cyanogen rom on the device and after flashing it, still not having a device that boots. A "recovery"/flash tool, should be able to "recover" from such a situation..
EPa said:
Yes, one thing is for sure. I had to install the KDZ to be able to proceed with anything..
It's just funny having a working CWM recovery and a cyanogen rom on the device and after flashing it, still not having a device that boots. A "recovery"/flash tool, should be able to "recover" from such a situation..
Click to expand...
Click to collapse
You can't blame the recovery. It is clearly stated many, many times that you should never attempt an official OTA update with a non-standard (rooted or recovery installed) device. On other devices you could even hard-brick AFAIK, so consider yourself lucky that you only had to reflash a KDZ and start again.
For restoring stock rom use this: http://forum.xda-developers.com/showthread.php?t=2682146 I can confirm it works and it is (very) easy.
Yes that's what I used and I also confirm it works and is very easy.
Edit: The flashable zip seemed to be a good workaround and got everything done in one go. Fingers crossed from here on in.
Hi guys, this is my first post here, so please go easy on me.
So recently my phone screen cracked and I had to send it off for recovery.
The company wiped and upgraded my firmware, but I did my data backup as a nandroid backup, so I have to get a recovery installed to restore it.
I have managed to unlock the bootloader and flash this version of the firmware : - D5803_23.4.A.1.264
I am simply trying to root the phone so I can get SuperSU onto it and the method I used last time uses CWM. However, when I try to install CWM I can access CWM, but otherwise, it goes into a boot loop and I have to reflash that firmware to restore it, which deletes the CWM. The CWM version I can flash does not seem to be able to restore nandroid, so it's fairly useless.
i have tried downgrading but then the phone crashes on startup. I noticed when I restored to the current firmware above, the phone had kept all my settings, so I don't know if there's extra I need to wipe, or if I'm not flashing correctly.
Now I have used PRF tool to create a flashable zip, that I thought might be able to do the job for me if I can get something to install it. It has the working firmware, SuperSU and dualrecovery in it.
I have done this all before without issues, but the new firmware version is making things more difficult.
So questions are;
1. Am I flashing incorrectly when downgrading? Or is there some other factor at play preventing me from doing so?
2. Is there a way I keep the CWM and flash the working firmware? Like it would go into boot-loop but then I could get the normal systems operating again and have the phone rooted, continuing the work. I figured there might be an option in flashtool, but I didn't want to press anything without confirmation from someone.
3. Is there an easier way to froot this? Last time I was able to use giefroot, but now it says my kernel isn't supported.
Any help would be greatly appreciated. I'm not new to modding my phones, but I'm not advanced either. Let me know if there are other details I can give that might help.
Thanks.
So I tried installing Xposed Framework by flashing it's ROM, but after I did it, I rebooted my phone, but every time I do it, it always boots into TWRP recovery. I tried fixing it by looking in the setting and I used a backup I made before doing all this crap and I restored, but my phone still boots only into TWRP recovery mode. I would really appreciate it if anyone could help me. Thanks.
PS. My phone is rooted and it has TWRP
TribalPaint said:
So I tried installing Xposed Framework by flashing it's ROM, but after I did it, I rebooted my phone, but every time I do it, it always boots into TWRP recovery. I tried fixing it by looking in the setting and I used a backup I made before doing all this crap and I restored, but my phone still boots only into TWRP recovery mode. I would really appreciate it if anyone could help me. Thanks.
PS. My phone is rooted and it has TWRP
Click to expand...
Click to collapse
Is it possible that you used the wrong Xposed for your device or SDK version? I can't imagine that restoring a backup didn't fix it. Did you try wiping system in TWRP first?
Things you can try:
- Flash the "Xposed Uninstaller" zip file in TWRP, which should always be on your device when you are flashing new versions of Xposed.
- Reflash TWRP in Odin. This should fix a recovery loop.
- Wipe system, data, dalvik, cache in TWRP, then try restoring your backup.
- As a last resort, you can download the latest stock firmware for your device from the sammobile site, flash it in Odin, let it boot once, reflash TWRP, wipe in TWRP and restore your backup (if you were running a custom rom you liked or something), then flash the correct Xposed for your device & android version.
Hope this helps!
Sent from my SM-N920T using Tapatalk
bogarty said:
Is it possible that you used the wrong Xposed for your device or SDK version? I can't imagine that restoring a backup didn't fix it. Did you try wiping system in TWRP first?
Things you can try:
- Flash the "Xposed Uninstaller" zip file in TWRP, which should always be on your device when you are flashing new versions of Xposed.
- Reflash TWRP in Odin. This should fix a recovery loop.
- Wipe system, data, dalvik, cache in TWRP, then try restoring your backup.
- As a last resort, you can download the latest stock firmware for your device from the sammobile site, flash it in Odin, let it boot once, reflash TWRP, wipe in TWRP and restore your backup (if you were running a custom rom you liked or something), then flash the correct Xposed for your device & android version.
Hope this helps!
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Hello. I already tried zipping the uninstaller for xposed but it did nothing, I also tried wiping dalvik cache and all, but no luck. I also think that my backups are just not functional. Now I'm left to just reflashing TWRP and if that doesn't work I'll have to flash the original stock firmware for my phone. I have spent already 2 days with constant searching for ways to fix my phone and not being able to do other things because this has been taking up my time and my patience, so I really appreciate every bit of fixing my phone that I get. Since I am new to all this I would be very grateful if you could send me the links to the correct files for my device and also give me a tutorial on what to do. As I appreciate any support, so I'm thankful for you helping me But until then my device is still not able to boot regulary but rather boots to TWRP
TribalPaint said:
Hello. I already tried zipping the uninstaller for xposed but it did nothing, I also tried wiping dalvik cache and all, but no luck. I also think that my backups are just not functional. Now I'm left to just reflashing TWRP and if that doesn't work I'll have to flash the original stock firmware for my phone. I have spent already 2 days with constant searching for ways to fix my phone and not being able to do other things because this has been taking up my time and my patience, so I really appreciate every bit of fixing my phone that I get. Since I am new to all this I would be very grateful if you could send me the links to the correct files for my device and also give me a tutorial on what to do. As I appreciate any support, so I'm thankful for you helping me But until then my device is still not able to boot regulary but rather boots to TWRP
Click to expand...
Click to collapse
Also, if I try to reflash TWRP, do I have to reflash the original firmware first, or I can just go straight ahead and just reflash TWRP?
TribalPaint said:
Also, if I try to reflash TWRP, do I have to reflash the original firmware first, or I can just go straight ahead and just reflash TWRP?
Click to expand...
Click to collapse
Update:
I fixed my phone, and here's what I did, so if anyone is new here with the same issue I had, I hope this can help you. So first of all as I said I kept booting to TWRP, later I tried reflashing TWRP, but I remembered that I missed something in ODIN, so I just pulled the cord and my screen after rebooting just said something along the lines of "An unexpected error occurred while updating software, please recover using Samsung Smart Switch." after that, I tried Samsung Smart Switch, but it was no luck for me, so then I used the last resort. I went on sammobile.com, I searched stock firmware for the exact model I had and then I checked the stock firmware that was available. Since I'm from Latvia, I picked the Baltic region, then I downloaded the latest stock firmware. After a long time, I downloaded the file, and I checked the instructions on how to flash it, I flashed the stock firmware, and then my problem was fixed, my phone was working again and now I have Android 7.1.1 as I used to have Android 6.0.1 and I had ZERO file loss However as you flash the stock firmware, TWRP get "flashed" out and same with root if you have it, and in that case if you want TWRP and root again, I highly suggest Meziani's YoutTube channel, because he gives simple and working tutorials on how to do it I'm glad if this helped anyone.