Hey everyone, I have a potentially silly question, but searching here and google hasn't helped me.
I decided to try out two custom roms for the z3, Carbon and Lineage, but once I installed them using a recovery (TWRP specifically), I was unable to get back into it. When I started the phone, I'd see the purple led, doing nothing booted into the rom, pressing either vol+ or vol- would change it to orange and a few seconds later, the phone would reboot again and show the purple led again. If I flashed the recovery again, the rom would no longer boot.
I feel like there is something super simple I'm missing with the flashing, but possibly can't describe it well enough to search effectively.
P.S. The reason I'm trying to get into recovery again (otherwise it wouldn't be a problem) is to do things like flash gapps, superuser, etc.
First up I would always recommend flashing the rom, gapps and your superuser in one go.
Sometimes it get's really messy when doing it after booting the rom without anything.
So now I guess you didn't upgrade your bootloader, did you?
Because the older bootloader didn't have a partition for the recovery that would survive a new rom flash (sometimes), but the new one does. But if you lost your recovery, you can easily just boot into fastboot mode and fastboot flash your recovery and instantly boot into it.
It also could be a problem of the wrong recovery you're using. Which one did you use up until now?
You were correct. Because I had a pre-rooted stock firmware, I thought I was on the latest. Turns out I was one version behind, the one version that did as you described. Once I flashed that first, it was working again. Thanks
Related
so i recently got a HTC one S, wanted a custom skin, and followed this:
www[dot]theandroidsoul[dot]com/miui-4-one-s/
tutorial in order to get cwm installed so i could instal a custom rom.
each step worked perfectly until i had to reboot into recovery mode and when i was going to instal
the OS everytime i clicked down to select 'format', the screen did a half second blink and would simply restart cwm.
the only way to get out of it was hold the power and volume to force a restart.
i them attempted to flash back to the default htc recovery (if i cant have my cake, least let me have what i had before)
unfortunately it gave me the error in cmd that the .img was unable to be read.
so wonderful. now i am almost positive this is something i am doing wrong,
but i just can't pick out what and i'll admit i'm not familiar with flashing, ect.
i've tried to follow tutorials such as forum.xda-developers[dot]com/showthread[dot]php?t=1707550
but am unable to even flash anything rom or otherwise,
i just keep getting stuck at the cwm recovery.
edit:
i attempted the fix mentioned in another thread about using the all in one,
now my phone simply crashes at recovery and wont even start recovery.
I'm having issues getting recovery to work on a Verizon version xoom. I first flashed CWM version 4.0.0.4. The first time I tried to boot into it, it was stuck on the android with the red triangle for a long time before finally getting into it (coincidentally when I was hitting the volume key, don't know if that's related). Anyway, since then I haven't been able to get into it. It will be suck on the red triangle screen for a minute or two before rebooting into the stock rom (I'm running stock ICS). Since then, I've tried flashing the new TWRP 2.2.2 or whatever version it is and it has no effect. It's still doing the same thing. Any clue what's wrong?
So what I'm reading is suggesting that the android guy I'm seeing is the stock recovery. I'm not sure how that's happening. I'm installing the recovery using fastboot on my PC and being in the bootloader on my xoom. The prompts on both appear to confirm success.
I haven't tried this yet as I'm at work, but I think I've got the issue sorted. The following is what appears to be happening from what I've read.
1. I've still got the custom recovery stalled. When the Android guy pops up, one needs to press volume up to enter the options. Otherwise, it reboots.
2. The recovery flashes are taking because I'm booting back into the rom after a flash. The system's built in recovery protection is re-flashing the original recovery at that point.
3. To make my CWM/TWRP/whatever flash stick, I'll need to power down and then boot directly into the recovery.
I'll post again tonight to say if this works. Hopefully this thread can help out others who have the same issue.
If you don't get that to work fastboot img from link..
http://forum.xda-developers.com/showthread.php?t=1074979
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Hi,
just got time to update my 2nd XT925 to KK (RSD'd back from CM11 JBBL to stock SFR rom, let the phone find its update and apply it, everything went fine).
But whatever KK recovery I try to flash, it gives me an exclamation mark and nothing else (I'm unlocked, yes).
Don't know what's happening here. Can someone helps please ?
Poursinet said:
Hi,
just got time to update my 2nd XT925 to KK (RSD'd back from CM11 JBBL to stock SFR rom, let the phone find its update and apply it, everything went fine).
But whatever KK recovery I try to flash, it gives me an exclamation mark and nothing else (I'm unlocked, yes).
Don't know what's happening here. Can someone helps please ?
Click to expand...
Click to collapse
Are you saying you are trying to flash a recovery or are you trying to GET to the stock recovery? If you are trying to get to the stock recovery, the key presses to get to it have changed.
Your best bet is to power off your phone. Then, press and hold power+vol up for a few seconds until you see the menu come up. Then, press vol down to highlight Recovery and then press the vol up button.
Eventually, you'll see the "Dead Andy". From there, press and hold vol down+vol up+power. You might have to do it a couple of times. Eventually, you'll be in the recovery but for the XT926, it's kind of hard to read because for some reason, they decided to make it dim.
No (but thanks anyway). What I tried to was only to install a KK recovery for CM11.
I successed but I had 2 problems mixed: the 1st one was that the Linux version of fastboot (or mfastboot) did'nt work with the new bootloader. Both were complaining about "(bootloader) Variable not supported! ". Had to find some old laptop with Windows installed to use it to flash the recovery without error.
But even then if I just let the phone reboot, I would'nt get the new recovery (just the stock one after the keypress you speak about). I had to go straight from bootloader screen to the recovery (by manually rebooting) to get it work. Looks like the standard boot just restored the stock recovery each time I tried.
Thanks anyway, it's working now.
Poursinet said:
No (but thanks anyway). What I tried to was only to install a KK recovery for CM11.
I successed but I had 2 problems mixed: the 1st one was that the Linux version of fastboot (or mfastboot) did'nt work with the new bootloader. Both were complaining about "(bootloader) Variable not supported! ". Had to find some old laptop with Windows installed to use it to flash the recovery without error.
But even then if I just let the phone reboot, I would'nt get the new recovery (just the stock one after the keypress you speak about). I had to go straight from bootloader screen to the recovery (by manually rebooting) to get it work. Looks like the standard boot just restored the stock recovery each time I tried.
Thanks anyway, it's working now.
Click to expand...
Click to collapse
Variable not supported comes up under some Windows, but it usually still works.
You never go straight to the bootloader when you reboot. You have to reboot the phone (or turn it off first) and then press and hold vol up+power. Then, from there, you use vol down to select recovery and then press vol up.
It never boots directly into the recovery unless you tell it to via an ADB command or from within a custom ROM that allows it.
Keep in mind, the stock recovery will override the custom recovery if you don't immediately boot back into recovery. Flash recovery, when that's done, press power to shutdown, and use the method Bolski described to boot into recovery.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
Keep in mind, the stock recovery will override the custom recovery if you don't immediately boot back into recovery. Flash recovery, when that's done, press power to shutdown, and use the method Bolski described to boot into recovery.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Let me see if i undestood.
You say that if you don't boot right into recovery, the stock one will overwrite CWM/TWRP. So i understand that, after very reboot you must reflash recovery if you want to use it again.
Or am I missing something?
Caliburno said:
Let me see if i undestood.
You say that if you don't boot right into recovery, the stock one will overwrite CWM/TWRP. So i understand that, after very reboot you must reflash recovery if you want to use it again.
Or am I missing something?
Click to expand...
Click to collapse
It won't reflash every time. You only need to boot straight into recovery the first time, so that the update binary completes. After the first time, you'll be good.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
It won't reflash every time. You only need to boot straight into recovery the first time, so that the update binary completes. After the first time, you'll be good.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I think this may be the problem I am having. I cant get my 926 to boot to recovery from fastboot after I load CWM recovery. Is there some trick?
So Yeah I finally decided that I want to install a custom ROM for my M2. Theres a problem though (or not?), that my recovery doesn't work (as in, the recovery for 4.4.4 with disabled RIC), when I power up my phone I keep tapping and pressing the vol down and also tried different combo's but still, there's no way to get to recovery, I even tried with rebooting to recovery, no luck again. And heres my question, is it supposed to be like that or am I doing something wrong? and yeah if it is the case that it supposed to be like that, can I flash the rom using flashtool? I'm on 4.4.4 so let's say I will want to flash ericsas 4.4.4, am I safe to do it in flashtool? Or is there any way to make recovery working again? Thanks
Up
Do you have Unlocked Bootloader?
Are you using CWM ou TWRP?
Hi everyone!
First I am not so versed in the flashing game, so bear with my incompetence please.
I recently tried to update my note 3 on lineageos 15 to 18.1, however, doing so, unbeknownst to me, TWRP was replaced by lineageos recovery. Now I have 18.1 and I want to install the gapps, but to do so, I was told I needed to wipe 3 things, dalvik an two other things, ... anyway, I can't do anything now that I have lineage recovery. To get TWRP, I tried to follow this precedure : https://www.droidwin.com/replace-lineageos-recovery-with-twrp/ but in vain. I get stuck at Step 2. point 3, where my phone goes into ODIN MODE with a droid saying downloading, do not turn off. and nothing gives then. Do you have any idea of something I can do to get TWRP back?
Samsung devices don't use fastboot to interact with the bootloader, instead they use something called Download Mode and a tool called ODIN. You need that tool installed to flash anything on the bootloader level. Proper instruction for your device can be found HERE.
Also as a side note, Your device has a unique boot sequence. Your device's Boot partition (also called ramdisk) houses part of the recovery and the Bootloader will try to overwrite it with the ROM's pre-bundeled Recovery as soon as it boots up. There are ways around that such as:
Your ROM should pre-bundle TWRP as a recovery (LOS has opted to include their own).
You patch the boot partiton as soon as you change it, meaning you have to boot straight to TWRP using key combination after flashing using ODIN so it does that for you.
So don't get frustrated if it doesn't stick and try again.
Awesome!! I had to get other instructions for using odin, the missing part in the link you gave me was "push AP and get the .tar from here and click start" other than that, I did what you said, (missed the first time, got lineage recovery instead of twrp, did it again by removing the battery after it booted from odin, and did the volume up + home + power) and I got TWRP back ! Wohoo!!
Thanks a lot.
And to whomever working on lineageOS reading this, please consider leaving the recovery part to Team Win, there is no point for us users to have a recovery with no wipe so no updating a ROM, as far as I understand the process... but what do I know...
Ok I now installed mindthegapps, and my phone goes to download mode when it reboots. so... do I have to re-instal the lineageOS rom after or before the gapps?
Ok I got it somehow! thanks.