I'm having a rather weird issue right now. I've been running Victorator's Unofficial CM10.1 builds for a while and a couple of days ago I switched to the Official CM10.1 build for the I9505 (nightly of June 10th). Yesterday I updated manually to the June 11th nightly build (meaning I downloaded the zip file and installed it from Philz Touch Recovery). Today however, I tried updating to the nightly build of June 12th through the phone itself instead of manually downloading it and installing through the recovery.
The problem I have now is this:
- I updated to the new nightly build (June 12th) through Settings -> About -> CyanogenMod Updates
- The phone rebooted into Philz Touch Recovery and completed the update as far I know.
- It rebooted again but it was stuck on the boot logo (Samsung SIV GT-I9505).
- I pulled the battery and booted into the Recovery again
- The recovery is in an update loop, I can't wipe anything or do a factory reset.
- Pulled the battery again and booted into the recovery, it still wants to update (I tried multiple reboots from that point on).
So basicly, I can't boot into Android since the update probably failed, booting into the recovery gives me that update process every time. I can't access the functions of the recovery at all, I only get the update screen again and again. I'm at work now so I can't really do anything about it I guess, unless somebody has some tips? If not I'll try to install the Stock ROM again at home through Odin, since that's the only solution in my head right now. Hopefully it'll work after that, but to be honest, I'm not updating on the phone itself anymore, I'm just gonna do it manually on the PC from now on.
thisisfraa said:
I'm having a rather weird issue right now. I've been running Victorator's Unofficial CM10.1 builds for a while and a couple of days ago I switched to the Official CM10.1 build for the I9505 (nightly of June 10th). Yesterday I updated manually to the June 11th nightly build (meaning I downloaded the zip file and installed it from Philz Touch Recovery). Today however, I tried updating to the nightly build of June 12th through the phone itself instead of manually downloading it and installing through the recovery.
The problem I have now is this:
- I updated to the new nightly build (June 12th) through Settings -> About -> CyanogenMod Updates
- The phone rebooted into Philz Touch Recovery and completed the update as far I know.
- It rebooted again but it was stuck on the boot logo (Samsung SIV GT-I9505).
- I pulled the battery and booted into the Recovery again
- The recovery is in an update loop, I can't wipe anything or do a factory reset.
- Pulled the battery again and booted into the recovery, it still wants to update (I tried multiple reboots from that point on).
So basicly, I can't boot into Android since the update probably failed, booting into the recovery gives me that update process every time. I can't access the functions of the recovery at all, I only get the update screen again and again. I'm at work now so I can't really do anything about it I guess, unless somebody has some tips? If not I'll try to install the Stock ROM again at home through Odin, since that's the only solution in my head right now. Hopefully it'll work after that, but to be honest, I'm not updating on the phone itself anymore, I'm just gonna do it manually on the PC from now on.
Click to expand...
Click to collapse
Since its not going to recovery properly i also see one option which is flash a stock firmware using ODIN
123hiten said:
Since its not going to recovery properly i also see one option which is flash a stock firmware using ODIN
Click to expand...
Click to collapse
I just got home and I immediately booted into download mode to flash the stock firmware through Odin, but it keeps failing on me.
On the other hand, when I boot into the recovery it now says that the firmware upgrade encountered an error and that I need to recover the phone through Kies. I'm now trying to flash a custom recovery again, but Odin freezes up in the middle of the process
Ok, another USB-port, USB-cable, some battery pulls and driver re-installs later I managed to flash the stock rom again. It didn't boot into the stock rom though, it was stuck in a boot loop. Then I flashed a custom recovery again (this one) and I'm not getting the update loop anymore. I restored a backup I made yesterday (thank God I made one) and the phone is working again.
Instead of updating to the latest nightly build of CM10.1 on the phone itself, I'm now gonna try doing it manually.
So happy right now :laugh:
thisisfraa said:
Ok, another USB-port, USB-cable, some battery pulls and driver re-installs later I managed to flash the stock rom again. It didn't boot into the stock rom though, it was stuck in a boot loop. Then I flashed a custom recovery again (this one) and I'm not getting the update loop anymore. I restored a backup I made yesterday (thank God I made one) and the phone is working again.
Instead of updating to the latest nightly build of CM10.1 on the phone itself, I'm now gonna try doing it manually.
So happy right now :laugh:
Click to expand...
Click to collapse
Finally happy to hear that :thumbup:
Sent from my GT-I9500 using xda premium
From other comments I've seen, the cm update feature causes problems. You are best off manually flashing updates.
Trick: you can create an Odin flashable recovery by:
- unzip the recovery installation zip file
- create a tar file of the recovery.img using 7zip.
Sent from my GT-I9505
Related
hey guys, It seems that i cant get my phone out of boot loop. This ocurred last night while i was switching roms. I went from PA jan11 build downgrading to the beta 8 build. I was able to downgrade successfully, but when i tried to upgrade to the latest experimental feb1 build I then got bootloops. Now when i tried to flash back to the older build it still wouldnt work.. My phone was at very low battery at the time(under 10%) through the whole process. I charged my phone over night and when i tried flashing PA again it still doesnt work. I am still able to enter recovery and fastboot. I tried to go complete stock through fastboot(and erased all data through fastboot) and now im able to see the Nexus X logo. This is where im stuck. I also upgraded twrp to latest 2.4.1.0 and it told me my data was encrypted. I fixed this by wiping the entire system through twrp. Then I went back into fastboot reflashed the rom again and im still stuck here with a Nexus logo. Any help?
EDIT: NVM I fixed it, installing cfx through twrp seemed to work. please close this
Hi,
I'm currently running CyanogenMod KitKat version with ClockWorkMod. Since the rom has several bugs and for the past few months they haven't published any updates to my Galaxy s4 I9505, I've decided to switch to WanamLite.
There I found out I need TWRP recovery so I went ahead and downloaded GooManager which installed an outdated version, as I've found out.
I tried wiping my internal storage as recommended but the recovery couldn't mount any of my partitions.
So now CyanogenMod won't boot. I know this issue is fixed in the updated version of TWRP but I'm not sure how to update it without the phone booting (Odin perhaps? It doesn't recognize it currently... Should I move to download mode for it to be detected?)
Anyways, I'm kind of stuck as of now. Any help would be very much appreciated!
Btw I have a question, what's the difference between using Odin 1.85 and 3.09? Why do people still use the old version?
Thanks in advance!!
Neta
Edit:
Alright, now I can't get into recovery either. When I try, I can see the Samsung logo and there's "recovery" written in the top left but then it just restarts again into the same logo without "recovery". I'm starting to lose my cool now. Anyone have any ideas?
Try flashing latest stock through download mode and see if it boots.
Sent from my GT-I9506 using Tapatalk
Flash this recovery through odin. It's TWRP 2.6.3.1. Worked alwys for me.:fingers-crossed:
https://db.tt/SwLvOrZl
Uncheck auto-reboot in Odin.
Thank guys
I got freaked out and just did everything I could to make the phone working again.
I found a thread on XDA explaining how to return your phone to stock version, so I followed it, rooted with auto root, (btw Odin didn't recognize my phone because I used the front usb... how annoying!), then flashed the latest TWRP (2.7.0.1, not 2.6.x.x as GooManager downloaded for me), then booted to recovery and flashed WanamLite.
Everything is working now!
Except one thing - I'm still not able to access recovery mode through physical buttons, only using boot apps. Is this a kernel issue?
Could be some incompatibility since CyanogenMod uses it's own kernel and CWM recovery.
The recovery itself is working fine, but when I try to access it using buttons it shows the Samsung logo with the recovery on the top left, and then reboots again to normal boot.
What do you think?
Thanks!
I was trying to upgrade from CM11 to CM12, which went smooth except for GAPPS closing constantly. I read online that this was caused by an old version of the recovery, so I tried to update TWRP to 2.8.4.0. I first tried using the TWRP app from the Play Store (after recovering my Nandroid backup), which locked the phone where it would only try booting into recovery, but couldn't get there. Holding the power button to turn it off would result in a reboot right back into recovery, which of course never went anywhere. Now I am trying to re-install TWRP using ODIN but It fails every time [Complete(Write) operation failed.] I have an early S4 from AT&T and it has never had an official update. I can't remember which firmware it is using, but it is the original so I shouldn't have any problems there. Can anybody help me get this thing up and running with either TWRP or CWM and CM12 please?!
Update: I have been able to get the phone to boot by first booting into Download mode, then hitting the Volume Down button to cancel. This has twice booted it back into the OS. Still no recovery though.
Solved
I was able to install TWRP 2.8.4.0 from the app after getting the device to boot. It worked correctly this time and all appears to be well. Odd that ODIN didn't work though.
Hi guys, the times has come for me to open up my own account - I screwed up. I hope this is the right sub forum and apologize if it is not.
LG G2 Germany, formerly: TWRP recovery, Paranoid Android 5.1.1
Loved the rom but there were some issues like the screen turning off and on randomly, wouldn't accept pin right away, so I decided to go for CM 12.1.
Booted into recovery, factory wiped, tried to flash the .zip, but neither the rom nor the gapps would even begin to flash. It just said error.
Went crazy, tried some other CM versions, none of them worked. I've never had this issue before, when I flashed PA it all went just peachy.
Went even crazier and I can't really remember what I did in my panic spiral, but I somehow ended up with a soft-bricked phone. Managed to re-install the LG firmware .kdz, however, only the 4.2 one worked (4.4 gave me a bootloop.)
Now, getting this bad boy rooted and ready to flash custom roms is somewhat of a problem. I managed to get it into recovery though (after some issues with the recovery image), but flashing CM still won't work. Same error as before. I think there may be something wrong with the recovery image. I still had the image .apk from the first time I rooted my phone (also with 4.2) and it worked just fine so I figured I'd just use it again and do it like I did it last time. However, I am able to get into recovery mode. I've tried ClockworkMod and TWRP, but as a result of my panicking, it's just really a big ol' mess right now. I hope I've included all the info needed.
Please help, I'm actually lost.
Are you flashing the latest TWRP which is 2.8.7.1?
http://blastagator.ddns.net/twrp.html
Hey, thanks for replying. At the moment it only boots into recovery, unfortunately. ADB does not work, even after re-installing the usb drivers. My computer recognizes the device now though, but I can't get any files onto that thing at the moment.
Edit: It's not the latest TWRP
If you install the latest TWRP, you may be able to boot into TWRP and copy over a ROM to flash.
I got bored today and decided to pull out the old N7, 2012 version. I update recovery to TWRP 2.8.7.0, installed CM 12.1, realized this tablet crawls with any version of Android other than shipped version, so I went and got CM 10 and GApps for JB, wiped and flashed them back on. I didn't see any errors when flashing them, but when rebooting after, it just boot loops. I see the Google logo with the unlocked icon at bottom, then reboot and back to Google/unlocked again. So I wipe and reflash cm12.1 and it's GApps and all boots and works fine, other than being slow. I'm assuming the recovery is the problem as I've run into something similar before on another device, but in that case, the recovery was too old and needed updated, but it makes sense that a recovery could be too new as well.
Am I correct that the recovery is the problem? If so, what should I run for CM 10 to flash and work?
Try cwm recovery
iwjosi said:
Try cwm recovery
Click to expand...
Click to collapse
I don't' know if it was using CWM or that I also tried CM 10.2 at the same time, but it's working now. On CyanogenMod's own page, there was no MD5 for CM10, but there was for CM10.2, so it's possible my copy of CM10 was a bad download. Either way, it's working now, so thank you good sir, or madam, or person on no specific gender.