OK, when I got my S4, the first thing I did was to install clockworkmod, and then CM12.1 nightly. Everything was hunky dory until mid December. The nightly build came in, and I downloaded. I haven't been able to update live for a while, but from recovery it hasn't been a problem. Suddenly, clockworkmod tried, but got stuck at "detected ext4 filesystem" and there it stayed. I assumed just the nightly build, but nada since.
After consideration that clockwork was old, and maybe that was it, I've replaced my bootloader with twrp (latest version), and tried to make the update again. Lo and behold, it gets stuck at the same point.
Now, I'd quite like a ROM that supports viper4android, and matches 12.1, but it seems I can't install anything from recovery now. Suggestions?
For info, I always remove the SD card if I update or install a recovery, so that isn't the problem. Possibly one issue is that my volume down no longer works, meaning I have to boot, and then reboot to recovery, but since that works, I assume it's not the problem.
To be honest, if there's a fully working marshmallow rom out there, I'd even give that a go.
Ideas? My phone is working just fine (apart from the 07:28 crash every work day, stopping my alarm going off. Oddly, it doesn't crash at weekend when I don't want the alarm. I'm guessing a problem with the clock app, although the alarm is set for 6am)
Have you tried go back to stock with odin and then re-rooting? It could work.
Related
Hi All,
I'm probably one of the few here who is still using HoneyComb instead of ICS on my Xoom. I've been on 3.2.4 for some time now, and started getting the 3.2.6 update notification which I blew off until the other day when I said screw it, I'll update and go through the trouble of re-rooting, etc.
However, I attempted to use Solarnz's universal root method which I've used numerous times before and never had an issue with until now. So after pushing the recovery.img via Fastboot, everything appears to have been completed just fine, except when I reboot into recovery I get the damn android with an error.
I've tried pushing a few versions of recovery and each time it seems to work just fine, but again on reboot, I can't get into recovery like it never got pushed or somehow has been erased. I can even revert back to 3.2.2 and update to 3.2.4 and root and re-install clockwork no problem. But I keep getting that damn update notification every 5 mins, and I'm sick of it, hence why I bothered to update in the first place.
I know most people have by-passed this altogether by jumping to ICS, but I've had too many issues with the beta ICS versions out there (WIFI handoffs and disconnects mostly) and need to reliable daily driver vice ICS goodness (fortunately I have a GNex for that).
Anyway, since I hadn't seen much on this, I decided to post and see if its just me, or if this really is an issue?
I can probably go old skool and use the manual root method of pushing the SU files via ADB, but something isn't right here, and I wanted to get some feedback.
Thanks
DANOinSD said:
Hi All,
I'm probably one of the few here who is still using HoneyComb instead of ICS on my Xoom. I've been on 3.2.4 for some time now, and started getting the 3.2.6 update notification which I blew off until the other day when I said screw it, I'll update and go through the trouble of re-rooting, etc.
However, I attempted to use Solarnz's universal root method which I've used numerous times before and never had an issue with until now. So after pushing the recovery.img via Fastboot, everything appears to have been completed just fine, except when I reboot into recovery I get the damn android with an error.
I've tried pushing a few versions of recovery and each time it seems to work just fine, but again on reboot, I can't get into recovery like it never got pushed or somehow has been erased. I can even revert back to 3.2.2 and update to 3.2.4 and root and re-install clockwork no problem. But I keep getting that damn update notification every 5 mins, and I'm sick of it, hence why I bothered to update in the first place.
I know most people have by-passed this altogether by jumping to ICS, but I've had too many issues with the beta ICS versions out there (WIFI handoffs and disconnects mostly) and need to reliable daily driver vice ICS goodness (fortunately I have a GNex for that).
Anyway, since I hadn't seen much on this, I decided to post and see if its just me, or if this really is an issue?
I can probably go old skool and use the manual root method of pushing the SU files via ADB, but something isn't right here, and I wanted to get some feedback.
Thanks
Click to expand...
Click to collapse
Depending on what ROM your flashing if your trying to do the update from OTA then you have to have a 100% no bloatware removed rom, my suggestion is to download the one @ motodev and then flash 3.1 and update all the way to ICS (if wanted) otherwise I believe that when you get the (!) in recovery you can press once pwr+up fast (don't hold) and it will display the recovery window with the error message that's preventing you from upgrading.
after flashing the recovery, did you reboot into android and then into recovery? if yes, don't!
you have to reboot into recovery right after flashing the recovery.
Hi All,
Thanks for the feedback, I finally got recovery pushed and booted, along with root on 3.2.6.
As llama points out you must reboot into recovery upon rebooting from fastboot. I don’t believe this was a requirement previously. But once I did that, all was fine.
I’ve done this a thousand times before and even in my old notes I couldn’t find any reference to booting into recovery immediately after pushing the recovery.img. Is this something new with this update or has it always been this way? Call me crazy, but I can’t ever recall scrambling to catch the reboot and get into recovery before re-launching Android. I always rebooted in Android and made sure it actually loaded to ensure something didn’t get hosed, then I would reboot into recovery and flash the root zip.
DANOinSD said:
Is this something new with this update or has it always been this way?
Click to expand...
Click to collapse
as far as I know, this is a 'feature' introduced with every ota-update. To my knowledge: get a xoom from a store and flash recovery right away-> everything is good; have the xoom install an ota-update and flash recovery afterwards -> do it this way
Alright, so here goes. I've searched the thread for the issue I'm having, but have come up empty handed. I'm not Droid noob, especially not when it comes to flashing roms. But, here are the details I have.
I had been following dragonzkiller's development on his ICS rom. I hadn't really put forth any effort looking lately until yesterday, and saw that he had the wifi and camera fixed, which were really my two biggest issues, so when I saw that, I was excited. I began working on getting it all running. I've had the x2 for about 5 months or so, and usually, the first thing I do, as soon as I get a new phone, is root it. Back in April, I rooted with GingerBreak. Worked good, no issues there. Back in June, apparently I still received the OTA update taking it to 2.3.5-418, which I found out last night had kinda broken my root. So, I went back to find a way to re-root. I did that, with a desktop .exe that went in, and was supposed to flash BSR to my phone also. After I ran that, all my root permissions started asking for options again, so I was relieved. Now, for the issues I'm having.
I downloaded an app in the play store called Online Nandroid Backup. For some reason, and I think this may be a dev issue with the app, it won't run a backup, and tells me that it wasn't able to be granted superuser permissions, even though it is prompting and I'm allowing. Issue number two is this. I've tried 3 different ways to get this working. I used ROM Toolbox Lite, selected the rom I wanted to flash, and wipe data and cache, no delvik. I've selected to run a backup of my current rom. When it boots into recovery, I only have 4 options. Reboot your phone, something about installing the rom from sdcard, wipe data, and wipe cache. I'm not given the backup option on the recovery. Furthermore, when I kinda just decided that since I hadn't had any trouble flashing a rom to any of my other phones I've had, I would just try to flash the rom, it gives me a prompt about 25% through the rom package saying E: signature could not be verified, or something to that extent.
Even though it has said not to use Rom Manager, I did download that and try that, and got pretty much the same outcome of no rom, just a bit different scenario going through. Rom Manager won't reboot into recovery, and when I select to do a backup, it reboots the phone straight up. I also used the manual entrance into recovery, volume up, but it tells me something about starting RSD protocol, and sticks at that forever.
My real questions are this... I've always ever used CWM. All of my previous phones have been supported by Rom Manager nicely, so when it came to downloading and flashing a rom on them, no problems at all. I have never used BSR, to my knowledge, so I'm not sure if the recovery screen I'm seeing is the actual BSR recovery, or if it's some other recovery. If it's not BSR, do I just flash it like I would a rom, then re-run into that? And does the signature issue that I'm running into mean that I have to wait for a signed version of the rom in order to work it? Is there any way to fix this issue, or am I basically SOL right this moment? Any information on how I can fix all of this would be greatly appreciated. Thank you.
Hi, today I got the notification on my G (India-Dual Sim version) that the 4.4.4 was available to download.
I tried to go back to stock recovery to do the upgrade but for some reason it didn´t work, I was able to flash but the stock recovery never came up. In the end I decided to give a shot and see what happened.
I have the CWM recovery, and it notified me that the file used for the update had not a correct signature, decided to continue, no problems so far. In the end it notified me that maybe root may have some issues (the same warning when you root the phone the first time), told it to fix it and it rebooted.
All smooth and so far no problems, but it did show a warning on the main screen (after being all loaded) that something went wrong, but the phone booted OK and the system version is 4.4.4, maybe something to do with the stock recovery or something, don´t know, but so far, is you have CWM, I believe you can do the OTA update withouth problem.
Will let you know if something comes up.
Okay I've got this weird problem since updated to awesome recovery/kernel. Whenever there is CM/Omni involved, my phone starts acting weird. Okay, listen to this.
First of all, everything seems normal after clean install. Then I install some of urgent apps (total commander, whatsapp - that's all). After a day or two my phone starts to act weird - it's rebooting itself and bootloops. I turn it off and on again - boots to os, then after a few minutes another reboot into bootloop. Okay... I thought it was because I didn't have the ext4 partition. Formatted into ext4 from recovery, installed Omniroom from 2 sept. and suprisingly it went good for two days! I installed some more apps and used it regularly - but it happend again. Reboot, bootloop, manualy reboot, worked fine for a minute, another reboot into bootloop. I thought that my SD card was damaged. h2testw claimed that it was perfectly fine. Now I wanted to install some stock 2.3.5 into it... I couldn't even pass the HTC screen because it keept rebooting itself...
Tell me what can I do to make this piece of... functional again? I ordered new phone, but it will arrive within next 14 days at best, and I still need the functioning android phone. Any advice, help is appreciate: links to a flashable stock roms, links to a fucntioning omni/cm rooms, any help on how to install them... thanks in advance
mclpl said:
Okay I've got this weird problem since updated to awesome recovery/kernel. Whenever there is CM/Omni involved, my phone starts acting weird. Okay, listen to this.
First of all, everything seems normal after clean install. Then I install some of urgent apps (total commander, whatsapp - that's all). After a day or two my phone starts to act weird - it's rebooting itself and bootloops. I turn it off and on again - boots to os, then after a few minutes another reboot into bootloop. Okay... I thought it was because I didn't have the ext4 partition. Formatted into ext4 from recovery, installed Omniroom from 2 sept. and suprisingly it went good for two days! I installed some more apps and used it regularly - but it happend again. Reboot, bootloop, manualy reboot, worked fine for a minute, another reboot into bootloop. I thought that my SD card was damaged. h2testw claimed that it was perfectly fine. Now I wanted to install some stock 2.3.5 into it... I couldn't even pass the HTC screen because it keept rebooting itself...
Tell me what can I do to make this piece of... functional again? I ordered new phone, but it will arrive within next 14 days at best, and I still need the functioning android phone. Any advice, help is appreciate: links to a flashable stock roms, links to a fucntioning omni/cm rooms, any help on how to install them... thanks in advance
Click to expand...
Click to collapse
if you want to install older roms or stock you`ll need to fastboot an older recovery check this out http://forum.xda-developers.com/showthread.php?t=1415223 you only need to do PART 3 : Add a Recovery section
now you should be able to flash non-aw3som3 roms cm10 RC2 and below/ICS/Jellybean/Stock jaggyjags roms either way will get a functioning phone back for you, remember to wipe everything apart from sdcard once in recovery then install whichever rom
Brief back story goes like this. Working TF300T running JB, was running slow and laggy so it seems a good time to flash something new. I'm no android/linux pro but I have a good base knowledge (you may question this statement later) . Successfully unlocked and flashed CM12 and TWRP. Tablet ran ok, sometimes significant lag, updated to a few different nightlies, then eventually decided to go back to stock. This is where it all went wrong. I followed the instructions here on XDA by d_crossfader. The flash seemed to go as expected, wiped cache/dalvik, rebooted. Loaded up to stock JB but no wifi, rebooted, all went bad. Stuck at the silver ASUS with spinning dots screen.
here's what working at this point.
I can load to fastboot, recovery etc, and have re-installed TWRP, the latest 2.8.1 failed install, but 2.6 is working (since I've read that this rev has issues).
I went back to the CM12.1 ROM I had working and it seems to flash fine but GAPPS fails, gives 'E: error updating binary in zip' for /boot and /recovery.
I think I've exhausted my abilities so it's time to call in people with actual skills.
What should my next move be? I'd be happy with stock or custom ROM's just like to get it back to functioning.
Thanks