I have a question regarding recovery flashing because I am unable to flash any updated recoveries at all. I currently use TWRP and have been using Flashify for quite some to update anything.
However, whenever I go to update TWRP by hitting the "download TWRP" option, I always get the error that I am unable to write to the SD card, even after a number of reboots. I'm not really sure about how to fix this because I previously was able to flash recoveries to my device flawlessly, without issues. I have attached a screenshot for reference. Any help with this would be greatly appreciated!
I am also using DigitalHive's Lollipop ROM as well.
Thank you in advance!
I would just download the file to your computer and flash it in fastboot.
Related
Hi all,
I am stuck in a bootloop and I do not know how to get out.
Phone is on SlimROM 2.8 (i9000), wanted to install GAPPS.zip via CWM, for whatever reasons I ended up in "install via sideload" instead of "install ZIP",
powered off phone while it was prompting s.th. about "adb install" (forgot the exact wording)
Now phone is booting, showing Semaphore image for a while and reboots automatically. CWM (VolUP+Home+Power) not available anymore.
I tried to flash Semaphore_JB_2.4.4s.tar via ODIN and phone continued with ROM boot. The next reboot -> same things as described above. The "trick" with kernel flash unfortunately worked only ONCE. Re-flashing kernel with ODIN has no effect (anymore?) ???
What is the best way to continue, if possible without data loss? Install new CWM? I expected some kernel settings to be responsible for the bootloop, hence the kernel flash.
Help is highly appreciated. Thanks in advance.
Install recovery manually through fastboot. You can use Android Flash Recovery if you're not comfortable with using fastboot yourself.
post-mortem said:
Install recovery manually through fastboot. You can use Android Flash Recovery if you're not comfortable with using fastboot yourself.
Click to expand...
Click to collapse
Well... am not sure if fastboot is available for I9000 at all (after some search in this forum)? How do I get into fastboot mode with this phone?
Anyhow, thanks for your reply. Solved my problem by flashing Devil kernel via ODIN, then reflashing SlimBean2.8. System work again as before.:good:
BTW, Devil Kernel for SlimBean produced some strange errors for me: no audio, some FCs, no camera. Was just good to get back to recovery.
I've searched and found a few different solutions for each of my problems. However, nothing has resolved the issue.
I tried to flash CM 11.0 to my Galaxy Tab 2 (GT-P3110) and now I can't get anywhere but my CWM Recovery screen.
When I try to install the ROM, I get a "Status 7" error. I've attempted the steps found here but they have not worked.
So, I decided to just recovery what I had before - easy enough. But then when I attempt to recover, I get an error of "MD5 Mismatch".
I've looked up ways to resolve this issue, but I can't complete the steps for 2 reasons. Firstly, I can't get to my File Explorer because my tablet won't completely boot. Secondly, my laptop has stopped recognizing my tablet for some reason. So, I'm unable to edit the file from there.
Lastly, when I just try to reboot system, I get an error explaining that I "may" have lost root access. If I select to "fix" this, it does nothing - just reboots back to recovery. If I choose no, same thing.
I've cleared dalvik, cleared cache partition, cleared data/factory reset, and formatted system - nothing makes a difference.
Any help is greatly appreciated. Thanks everyone.
IS there kitkat update for tab 2. Please inform about That}.
chandru andriod said:
IS there kitkat update for tab 2. Please inform about That}.
Click to expand...
Click to collapse
I believe so, yes.
@ohhello update your recovery. your recovery needs to be up-to-date to flash KitKat Roms. Link in my signature, all my latest recoverys can handle KitKat-Roms.
Android-Andi said:
@ohhello update your recovery. your recovery needs to be up-to-date to flash KitKat Roms. Link in my signature, all my latest recoverys can handle KitKat-Roms.
Click to expand...
Click to collapse
Okay - easy enough.
If I'm unable to get to ROM Manager, is there a way to update my Recovery within Recovery Mode?
I've zipped the .img file for the update.
Should I just install the zip from Recovery Mode?
THANKS!
download a flashable zip for your device from my thread and flash it in recovery. after that reboot the recovery to see the new recovery.
I have a Moto G X1032 rooted with TWRP installed. I've been using the stock firmware for 4.4.2 without any issues for a while, but after June 6th's OTA update to 4.4.3, my phone has gotten stuck in a boot loop. It turns on and runs Android as usual, without any issues, for less than a minute and then shuts down. It then continues to boot back up and continue the process. The only way to stop the loop is to boot into the bootloader from TWRP and power off the phone from there. Luckily I have a backup to that reverts me back to 4.4.2, which successfully stops the loop. But after several attempts to update to 4.4.3, it has become quite clear that this boot loop is inevitable unless I stick with 4.4.2. I read an article that seems to address some conflict with rooted phones and 4.4.3, but I'm not quite sure what the conflict is. Can anyone explain to me why this boot loop is most likely happening, what I could do to fix it, or if it is even possible to have a rooted X1032 with 4.4.3 installed? Any help whatsoever would be greatly appreciated. Thank you.
Are you saying you tried to install the OTA with TWRP installed and not the stock recovery?
Just go into recovery clear all cache,kavik cache that should do
NerdNoob1210 said:
I have a Moto G X1032 rooted with TWRP installed. I've been using the stock firmware for 4.4.2 without any issues for a while, but after June 6th's OTA update to 4.4.3, my phone has gotten stuck in a boot loop. It turns on and runs Android as usual, without any issues, for less than a minute and then shuts down. It then continues to boot back up and continue the process. The only way to stop the loop is to boot into the bootloader from TWRP and power off the phone from there. Luckily I have a backup to that reverts me back to 4.4.2, which successfully stops the loop. But after several attempts to update to 4.4.3, it has become quite clear that this boot loop is inevitable unless I stick with 4.4.2. I read an article that seems to address some conflict with rooted phones and 4.4.3, but I'm not quite sure what the conflict is. Can anyone explain to me why this boot loop is most likely happening, what I could do to fix it, or if it is even possible to have a rooted X1032 with 4.4.3 installed? Any help whatsoever would be greatly appreciated. Thank you.
Click to expand...
Click to collapse
The bootloop is caused by the recovery. It can't update 4.4.3 and keeps trying. Start the update again and let the OTA file download, then copy it out of /cache and into the sdcard. If it's not in cache it won't bootloop. I suggest flashing PhilZ recovery and updating with that instead. Flash the file in the sdcard and post whatever errors are listed...
secretkloud said:
The bootloop is caused by the recovery. It can't update 4.4.3 and keeps trying. Start the update again and let the OTA file download, then copy it out of /cache and into the sdcard. If it's not in cache it won't bootloop. I suggest flashing PhilZ recovery and updating with that instead. Flash the file in the sdcard and post whatever errors are listed...
Click to expand...
Click to collapse
Thank you. I will try that. Before I do though, do you know of any places I could find 4.4.3 online, so I could just download it from my PC and flash it over via sideload? I usually prefer to flash things that way, rather than straight from the phone.
bozzykid said:
Are you saying you tried to install the OTA with TWRP installed and not the stock recovery?
Click to expand...
Click to collapse
Yes. This is my first time doing so, excuse my lack of knowledge on the subject. In retrospect, I suppose I should have known there must be a different method with which I install it. Secretkloud gave me a good suggestion though. Is there a reason in particular as to why I can't do OTA updates with custom recovery installed?
secretkloud said:
The bootloop is caused by the recovery. It can't update 4.4.3 and keeps trying. Start the update again and let the OTA file download, then copy it out of /cache and into the sdcard. If it's not in cache it won't bootloop. I suggest flashing PhilZ recovery and updating with that instead. Flash the file in the sdcard and post whatever errors are listed...
Click to expand...
Click to collapse
I just downloaded the zip from my phone and flashed it from Phillz recovery. It worked very well and the update was successful. Thanks for pointing me to Phillz recovery by the way. It's the only functional recovery image that allows me to mount the sdcard.
NerdNoob1210 said:
Thank you. I will try that. Before I do though, do you know of any places I could find 4.4.3 online, so I could just download it from my PC and flash it over via sideload? I usually prefer to flash things that way, rather than straight from the phone.
Click to expand...
Click to collapse
Copy the one you have in your phone onto your PC. Smallest chance of error if you do it that way...
it's not easy getting out of the loop.
I did a factory reload of a rooted phone with CWM.
Now for the CWM issue the Moto G loaded OK and then said there was an update for android to fix some bugs. This was 4.4.3. I loaded it and it gets half way and it then says
"Signature verification fail"
at the bottom of the screen and
" Install Untrusted Package"
The options are yes, no or go back
at the top....
whichever one I try it then tries to boot shows the Android / Motorola screen and starts up gets a txt message for 2-3 seconds... it then goes back to Android CWM recovery with the same options as above and repeats the process. again and again and again. No function keys will stop this cycle which just repeats again. This continues until the battery dies.
any ideas ? how can I override this action in CWM v6.0.4.6 and force it to do a factory reload ? any help or advice much appreciated.
If you can still power your phone, can you still access the boot loader? If so, I would suggest using adb from a computer to flash Phillz recovery. CWM always gave me a lot of random errors when flashing items. You could use PhillZ to flash the stock ROM for 4.4.2. After that, just follow the same process I did. Download the update zip via the OTA download when it prompts you. Once it's finished, DON'T boot back into Android. Boot into Phillz recovery from the boot loader, move the zip out of the cache and onto sdcard or your computer, and then flash it either straight from the phone or by sideloading it from your computer. Then you'll have a working version of vanilla 4.4.3, and you can flash over a custom ROM in the future if you so choose.
Sent from my XT1032 using XDA Premium 4 mobile app
NerdNoob1210 said:
If you can still power your phone, can you still access the boot loader? If so, I would suggest using adb from a computer to flash Phillz recovery. CWM always gave me a lot of random errors when flashing items. You could use PhillZ to flash the stock ROM for 4.4.2. After that, just follow the same process I did. Download the update zip via the OTA download when it prompts you. Once it's finished, DON'T boot back into Android. Boot into Phillz recovery from the boot loader, move the zip out of the cache and onto sdcard or your computer, and then flash it either straight from the phone or by sideloading it from your computer. Then you'll have a working version of vanilla 4.4.3, and you can flash over a custom ROM in the future if you so choose.
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
unfortunately I can't get into bootloader. I can connect usb and it makes no difference. therefore adb commands dont work. it just goes straight into screen described with those three options. I'm hoping that there is an override action in CWM which isn't power and volume down which do nothing.
thanks for the suggestion tho. it was a good idea.
Hm... Without access to the boot loader, I'm not sure there's much of anything you can do anymore... You've completely lost the ability to communicate any sort of commands to your phone save for the 3 options that menu provides. I assume that what CWM is trying to do is install the zip from your cache and is failing to do so. The only viable option would be to flash a new recovery image and install the zip manually, but that's impossible for you given your current circumstances. I would give up looking for an override command for CWM, your best hope is to find an alternative means with which you can access your boot loader. I suggest you start a thread dedicated to your issue and see if a more experienced user can provide you with the information you need. Sorry, I hope you get the help you need. :/
Sent from my XT1032 using XDA Premium 4 mobile app
Thanks for trying to help. I have followed your advice and opened a thread
NerdNoob1210 said:
Hm... Without access to the boot loader, I'm not sure there's much of anything you can do anymore... You've completely lost the ability to communicate any sort of commands to your phone save for the 3 options that menu provides. I assume that what CWM is trying to do is install the zip from your cache and is failing to do so. The only viable option would be to flash a new recovery image and install the zip manually, but that's impossible for you given your current circumstances. I would give up looking for an override command for CWM, your best hope is to find an alternative means with which you can access your boot loader. I suggest you start a thread dedicated to your issue and see if a more experienced user can provide you with the information you need. Sorry, I hope you get the help you need. :/
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry for off topic but what recovery is everyone using? I just made a switch from CWM to TWRP since development for CWM is dead but I can't get TWRP to sideload. It recognizes device until I go to Advance > ADB sideload, then it PC stops recognizing device. I've tried many different drivers, I just can't get it to work. Help, anyone using TWRP.
I use Philz cwm recovery .
How were you able to flash custom recovery? I am trying to do the same on a SCH-i925 version for Verizon but have not been able to tell if anyone was ever able to find a way in on the FW ending in MK1. Just wondering if that is what you were using. Thank you.
I hope someone reads this as I'm lost for ideas. First time trying to root a device, I'm using an s8+ and somehow managed to mess up installing twrp using Odin.
Now when I try to re flash twrp it comes up with error, 'only official released binaries are allowed to be flashed'. Also I think I managed to erase the recovery program that comes with the phone as when I try to boot in recovery it now comes up with error message 'No command'.
I have reinstalled the stock firmware using Odin but that hasn't fixed anything.
Anyone got any ideas or insite into this problem. Any advice would be very appreciated as I'm so keen to discover rooting!!
Philnicolls89 said:
I hope someone reads this as I'm lost for ideas. First time trying to root a device, I'm using an s8+ and somehow managed to mess up installing twrp using Odin.
Now when I try to re flash twrp it comes up with error, 'only official released binaries are allowed to be flashed'. Also I think I managed to erase the recovery program that comes with the phone as when I try to boot in recovery it now comes up with error message 'No command'.
I have reinstalled the stock firmware using Odin but that hasn't fixed anything.
Anyone got any ideas or insite into this problem. Any advice would be very appreciated as I'm so keen to discover rooting!!
Click to expand...
Click to collapse
Seeing No command is normal, with an icon of a dead android lol, thats stock recovery, blue screen, i got that all time, but after waiting about 30 seconds and pressing the buttons, i got the mnue to pop up to reset cache, reboot phone, wipe data etc.
As for TWRP, are you flashing the correct one, dream2lte??, download the latest one, the dream2lte.img .tar file, from the TWRP official website - - https://dl.twrp.me/dream2lte/twrp-3.3.1-0-dream2lte.img.tar.html.
I had this issue trying to flash TWRP with standard odin, i had to use a modded version of odin to flash it, even prince cosmy version didnt work for me.
I have attatched the ODIN i use, its a 7zip file.
Thank you, after trying a few more things the twrp file you gave me worked. I now have a fully rooted s8!!!! Your a legend.