Twrp not working - Verizon LG G3

I'm trying to safe my rom and twrp and the bar swipe to reboot is not there. I can't install nothing.

android-incredible said:
I'm trying to safe my rom and twrp and the bar swipe to reboot is not there. I can't install nothing.
Click to expand...
Click to collapse
boot up and use DD code to re flash twrp, something is corrupt.

Sorry but I don't know how to do it. I reboot in twrp and I don't know where to find the DD code...

I downloaded flashify and tried to reflash twrp 2.8.6.1 bumped. And when reboot said fail.

android-incredible said:
I downloaded flashify and tried to reflash twrp 2.8.6.1 bumped. And when reboot said fail.
Click to expand...
Click to collapse
the dd code is in the op of my reference thread.
seems like there may be more than a corrupt recovery, since flashify fails.
you may want to save whatever you need and go for the tot.

im trying to flash the ,tot and when start says cant change to download mode.i restared thye laptop and start with the process but now fail almost at the final. say usb Port Open Fail. and stay on the # 2 with blue screen
fixed....

Related

Recovery Image Messed Up..Launcher Crash..help please!

My recovery image seems to be messed up since I can't boot into it. My phone will boot but everytime it does ADW crashes over and over not allowing me to do anything. What can I do to go about getting the recovery fixed again and reflashing to try to smooth everything out?
*Edit*.I think I may have thought of a work around. I emailed my self the launcherpro.apk and installed it through gmail. Now I can access my phone. Now I just need to flash a working recovery..
I do appreciate your help though Riley.
You can try downloading ADW Launcher, putting it on your SD card and boot from recovery, then flash the launcher. It is a far shot, but if launcher is the only problem, maybe reflashing it will do the trick.
** EDIT ** My apologies. I misunderstood. I thought you were referring to a corrupted recovery image that you had made of your ROM!
You say you can't boot into recovery/ what's your phone do or say when trying to boo4 in recovery? You may have to push new recovery image via fastboot.
CGriffiths86 said:
My recovery image seems to be messed up since I can't boot into it. My phone will boot but everytime it does ADW crashes over and over not allowing me to do anything. What can I do to go about getting the recovery fixed again and reflashing to try to smooth everything out?
Click to expand...
Click to collapse
If you have USB debugging turned on you can flash Amon_RA via an adb shell using the flash_image tool - exactly the way the original Eris rooting process worked. With your phone looping, it will run very slowly, but will still succeed.
If you have the S-OFF bootloader installed, you can flash the recovery with fastboot.
I'll have an XDA admin move this thread to the Q&A forum.
Ok guys..I got launcher pro installed so I can actually access my phone now. I attempted to Flash a recovery with Rom Manager and it says it succeeds but it will never boot into it. I do have the bootloader with the "off". Is there a market app or something that can easily flash the recovery? I only ask because I am not at my PC with the android sdk stuff.
CGriffiths86 said:
Ok guys..I got launcher pro installed so I can actually access my phone now. I attempted to Flash a recovery with Rom Manager and it says it succeeds but it will never boot into it. I do have the bootloader with the "off". Is there a market app or something that can easily flash the recovery? I only ask because I am not at my PC with the android sdk stuff.
Click to expand...
Click to collapse
If you can't get to a PC to use adb, you could use a root shell in a terminal emulator to flash recovery using flash_image. That's kind of painful/tedious though - almost enough so to make it worth your while to just wait until you get back to your PC.
It is technically feasible to put together a flashable ROM to re-flash the recovery, but I'm not aware of anyone having done so for the Eris.
Oh ok..well I have RA Eris 1.6.2 recovery on my sd card. So I can just flash it via the termninal emulator, right?
** I tried to install via terminal and it says "header is the same, not flashing recovery". Do you think I could install the stock Eris recovery and reflash Amon's?
UPDATE!!: I got a recovery to flash..YAY..thanks guys
CGriffiths86 said:
Oh ok..well I have RA Eris 1.6.2 recovery on my sd card. So I can just flash it via the termninal emulator, right?
** I tried to install via terminal and it says "header is the same, not flashing recovery". Do you think I could install the stock Eris recovery and reflash Amon's?
Click to expand...
Click to collapse
are you using "flash_image"? If so, where is it from? To my knowledge (the statically linked version from Amon_RA - /sbin/flash_image) is a pretty simplistic program - it performs no checks, and will let you flash total garbage to any named partition on your phone. (Which is why you should verify the md5 of the recovery image before you flash it, BTW; you can use the AFV app for that)

Install TWRP Failing Through GooManager

I just completed S-off sucesfully and installed goomanger > selected install openrecovery script. It downloaded openrecovery-twrp-2.4.1.0-fireball.img. I than got a pop up saying recovery has been installed. I than selected reboot recovery and got a pop up saying, "by clicking yes, your phone will request root and reboot to recovery. I selected yes, it says "attempting to reboot recovery, if this fails you may want to perform the operation manually". Nothing happens after this, I just get taken back to the goomanger main menu. Am I missing something or does this not work?
Thanks for the help, as I am fairly new to android, just coming over from the iphone 5.
motionUS said:
I just completed S-off sucesfully and installed goomanger > selected install openrecovery script. It downloaded openrecovery-twrp-2.4.1.0-fireball.img. I than got a pop up saying recovery has been installed. I than selected reboot recovery and got a pop up saying, "by clicking yes, your phone will request root and reboot to recovery. I selected yes, it says "attempting to reboot recovery, if this fails you may want to perform the operation manually". Nothing happens after this, I just get taken back to the goomanger main menu. Am I missing something or does this not work?
Thanks for the help, as I am fairly new to android, just coming over from the iphone 5.
Click to expand...
Click to collapse
Did you root the phone after s-off? You will need to flash superuser after DirtyRacun. Once you have root installed, goo manager should be able to install the custom recovery.
Sent from my Fireball using Xparent Blue Tapatalk2
junkmail9 said:
Did you root the phone after s-off? You will need to flash superuser after DirtyRacun. Once you have root installed, goo manager should be able to install the custom recovery.
Sent from my Fireball using Xparent Blue Tapatalk2
Click to expand...
Click to collapse
If did not root after s-off. Didn't know I had to. Where can I find this superuser file to root? Still learning. Thanks for the help.
motionUS said:
If did not root after s-off. Didn't know I had to. Where can I find this superuser file to root? Still learning. Thanks for the help.
Click to expand...
Click to collapse
Flash one or the other of the following (but only one):
1. SuperSU (XDA Thread)
2. SuperUser (website)
Installing SuperSU from the Google Play/Market should be easiest.
If that doesn't work, you may need to install the custom recovery via fastboot first.
Once a superuser package is installed, goomanager should work for you.
junkmail9 said:
Flash one or the other of the following (but only one):
1. SuperSU (XDA Thread)
2. SuperUser (website)
Installing SuperSU from the Google Play/Market should be easiest.
If that doesn't work, you may need to install the custom recovery via fastboot first.
Once a superuser package is installed, goomanager should work for you.
Click to expand...
Click to collapse
I installed SuperSU and as soon as I open it I get the following message "There is no SU binary installed and SuperSU cannot install it. This is a problem". What should I do?
Thanks
Could always flash the image manually through fastboot if you have the drivers/knowledge. Rename the recovery to recovery.img and put it in the same folder as the fastboot executable. fastboot flash recovery recovery.img
Sent from my EVO using Tapatalk 2
There's an order of operations that need to be followed. 1) recovery 2) root or ROM.
You can't use an automated recovery installer unless you have root access, and you can't get root access until you flash the su binary or a ROM with su included (which requires a recovery... see the circle?). Thus, the automated installer is not an option for the very first recovery flash. Similarly, the superuser applications on Play require that you have an su binary already... they just manage access to that binary by other applications.
Follow the manual instructions to flash TWRP, they're really quite easy. If you performed S-OFF, you have the fastboot (and adb) binaries already.
Edit: I have updated the instructions in the TWRP post to reflect this. Thanks for bringing it to my attention.
Think I figured out, trying now. I think I downloaded the wrong recovery. Should have grabbed the fireball version.
Thanks for everyones help. I almost there. I just manually installed open recovery-tarp-2.4.1.0-inc.img and I got the following
sending recovery 93700kb)... OKAY
writing recover recovery ... OKAY
I than tried booting into the recover with the following command
fastboot boot recovery recovery-tarp-2.4.1.0-inc.img
I than got the message "cannot load 'recovery'
Anyone know where I should go from here?
Thanks
motionUS said:
Think I figured out, trying now. I think I downloaded the wrong recovery. Should have grabbed the fireball version.
Thanks for everyones help. I almost there. I just manually installed open recovery-tarp-2.4.1.0-inc.img and I got the following
sending recovery 93700kb)... OKAY
writing recover recovery ... OKAY
I than tried booting into the recover with the following command
fastboot boot recovery recovery-tarp-2.4.1.0-inc.img
I than got the message "cannot load 'recovery'
Anyone know where I should go from here?
Thanks
Click to expand...
Click to collapse
Follow the manual instructions more closely. You don't want to 'fastboot boot ...'
Also, recovery-tarp-2.4.1.0-inc.img is not the right recovery.
I've got it working. I realized I had the wrong recovery a few minutes later. Thanks for all your help.
motionUS said:
I've got it working. I realized I had the wrong recovery a few minutes later. Thanks for all your help.
Click to expand...
Click to collapse
Glad you got it working.
Sent from my Fireball using Xparent Blue Tapatalk2

[Q] droid dna twrp recovery rainbow screen!!!

Hello I'm not new to rooting but I am to the fastboot and cmd prompt but anyways
I'm on my way to rooting my DNA, I'm as far as flashing the recovery I flashed a twrp recovery for DNA and as I boot into recovery all I get is a screen with rainbow lines I wanted to flash cwm but I didn't know if flashing over recoverys was a good idea so I tried to flash another DNA twrp recovery 2.4.1.0 I believe but now everytine I go to flash a recovery I get a "cannot load recovery.img unknown error no matter what I do can anybody help me with this
c2a5nn1o4n said:
Hello I'm not new to rooting but I am to the fastboot and cmd prompt but anyways
I'm on my way to rooting my DNA, I'm as far as flashing the recovery I flashed a twrp recovery for DNA and as I boot into recovery all I get is a screen with rainbow lines I wanted to flash cwm but I didn't know if flashing over recoverys was a good idea so I tried to flash another DNA twrp recovery 2.4.1.0 I believe but now everytine I go to flash a recovery I get a "cannot load recovery.img unknown error no matter what I do can anybody help me with this
Click to expand...
Click to collapse
did you enter this command when you were in fastboot usb mode?
is the recovery.img file in the correct directory (so fastboot can find it to flash it)
did you download the correct version...
Code:
fastboot flash recovery recovery.img
.torrented said:
did you enter this command when you were in fastboot usb mode?
is the recovery.img file in the correct directory (so fastboot can find it to flash it)
did you download the correct version...
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Yes I got it to work the first time but now like I said it I get the can not load recovery.img unknown error
Yes all my pathing is right
c2a5nn1o4n said:
Yes I got it to work the first time but now like I said it I get the can not load recovery.img unknown error
Yes all my pathing is right
Click to expand...
Click to collapse
can you boot up into your ROM? if so download the GooManager app click the settings button and click install OpenRecovery and see if that works...
.torrented said:
can you boot up into your ROM? if so download the GooManager app click the settings button and click install OpenRecovery and see if that works...
Click to expand...
Click to collapse
I need to get into recovery to flash my superuser and busybox to obtain root unless there is another way.... Its the rainbow screen just a flaw in the display or would the entire recovery be messed up
c2a5nn1o4n said:
I need to get into recovery to flash my superuser and busybox to obtain root unless there is another way.... Its the rainbow screen just a flaw in the display or would the entire recovery be messed up
Click to expand...
Click to collapse
I've never heard of a "rainbow screen effect" when dealing with recoveries...
try downloading the CWM recovery found here http://tinyw.in/QGZG
or here is the TWRP recovery http://tinyw.in/8yFn
and last is the dlx-stock recovery pulled from the OTA (safe to use) http://dl.dropbox.com/u/10829584/stock_recovery_dlx.img
and try using a different usb port
c2a5nn1o4n said:
I need to get into recovery to flash my superuser and busybox to obtain root unless there is another way.... Its the rainbow screen just a flaw in the display or would the entire recovery be messed up
Click to expand...
Click to collapse
Cwm flashed fine and ran perfected I flashed my Su and busybox package and rebooted I still do not have root I went to the Su app and it said binary needs to be updated I accept and installation immediately failed
Edit: I tried again its rebooted my DNA I went back to supersu and it still says binary needs to b updated
SUCCESS you sir are a magical human being and I wish the best for u in life
c2a5nn1o4n said:
Cwm flashed fine and ran perfected I flashed my Su and busybox package and rebooted I still do not have root I went to the Su app and it said binary needs to be updated I accept and installation immediately failed
Edit: I tried again its rebooted my DNA I went back to supersu and it still says binary needs to b updated
SUCCESS you sir are a magical human being and I wish the best for u in life
Click to expand...
Click to collapse
I don't understand. Did you end up figuring it out again? If you are able to make it to recovery try flashing an already rooted rom, if not, you could just try to fasboot root again. It might help
I Have 2 more questions I was wondering if there is a WiFi hack yet and how is the its update going to effect my root
c2a5nn1o4n said:
Cwm flashed fine and ran perfected I flashed my Su and busybox package and rebooted I still do not have root I went to the Su app and it said binary needs to be updated I accept and installation immediately failed
Edit: I tried again its rebooted my DNA I went back to supersu and it still says binary needs to b updated
SUCCESS you sir are a magical human being and I wish the best for u in life
Click to expand...
Click to collapse
I read somewhere that if you flash the wrong model (dlxu) that you get messed up lines
c2a5nn1o4n said:
I Have 2 more questions I was wondering if there is a WiFi hack yet and how is the its update going to effect my root
Click to expand...
Click to collapse
I have not heard of a WiFi hack for the DNA... What kind of hack are you talking about... Like what does it do....
And I would just wait for a dev to make a flashable zip but you can flash the radio.img if you want to
Sent from my HTC6435LVW using XDA Premium HD app
.torrented said:
I read somewhere that if you flash the wrong model (dlxu) that you get messed up lines
I have not heard of a WiFi hack for the DNA... What kind of hack are you talking about... Like what does it do....
And I would just wait for a dev to make a flashable zip but you can flash the radio.img if you want to
Sent from my HTC6435LVW using XDA Premium HD app
Click to expand...
Click to collapse
I figured that out but now I'm losing root everytime I shut down even if I update binary in supersu
c2a5nn1o4n said:
I figured that out but now I'm losing root everytime I shut down even if I update binary in supersu
Click to expand...
Click to collapse
you need a kernel with system write enabled to be able to update binaries

Can´t reach Recovery

Hi all. Before i start i want to say, i read a lot of threaths and comments before i started to booting recovery and i followed Tutorial that you can find somewhere here on XDA for MotoE.
I unlocked Bootloader correctly and everything was right. Then i downloaded latest version of TWRP and CWM if something will be wrong.
So i booted into bootloader, connected to PC (windows 8.1) and using adb i installed TWRP (by command window). After instalation was complete, i used comand: "fastboot reboot" to get my mobile start normally. Everything worked fine so i started last step. Turned off mobile, booted into bootloader(or maybe fastboot? idk...) and by volumebuttons i choosed "Recovery" . Then a black screen for a minute. After that mobile stuck on screen that i attached down below. So i tried this but with CWM (same process way). But nothing new... Someone said me i had to try "Minimal ADB and Fastboot" but again, nothing happend.
Can you help me guys?
The recovery isn't installed! Reinstall the recovery and follow correct steps!
I tried it one more time. I´m attaching image that is from command window showing that .img was booted ... Strange is, immediately after booting was completed, mobile restarted... and after i turned off mobile again, still i can´t reach recovery. Isn´t that problem in .img file? maybe it´s broken, isn´t it?
Tried once again
Ok last try didnt worked. So i complettly followed this guide http://forum.xda-developers.com/moto-e/general/guide-one-moto-e-beginners-guide-t2807891 STEP-BY STEP!
Command window screen attached, Fastboot screen attached.
After reboot, turn off i tried to open recovery and again that image that i posted in first coment. (android figure with words: no command)
By that guide i downloaded recovery from here: https://goo.im/devs/OpenRecovery/condor/
and i downloaded just "openrecovery-twrp-2.7.1.0-condor.img" as i have to do it (written in guide)
Well, your recovery is flashing fine from cmd but its not detected by your phone.
Try re-downloading the recovery and check md5 before flashing.
I'll look into it and see if the issue can be pinpointed.
Btw, you might need the flash the stock ROM back if nothing works.
Tapatalk with RAZR HD
neo.ank said:
Well, your recovery is flashing fine from cmd but its not detected by your phone.
Try re-downloading the recovery and check md5 before flashing.
I'll look into it and see if the issue can be pinpointed.
Btw, you might need the flash the stock ROM back if nothing works.
Tapatalk with RAZR HD
Click to expand...
Click to collapse
Ok i will re-download recovery, is that file that i downloaded ok? i mean should i dowload same file as before?
+ sorry for that but i completly dont know what the "md5" is. can you send me link from where i can learn what it is? you can explain that too but i dont want take your free time.
Mondop said:
Ok i will re-download recovery, is that file that i downloaded ok? i mean should i dowload same file as before?
+ sorry for that but i completly dont know what the "md5" is. can you send me link from where i can learn what it is? you can explain that too but i dont want take your free time.
Click to expand...
Click to collapse
Okay try this.
Flash CWM
If flashing fails or you get any error, then try booting into recovery.
Code:
fastboot boot recovery.img
If you boot into recovery, flash the SuperSU package.
Reboot and then flash the recovery.
See if it works.
neo.ank said:
Okay try this.
Flash CWM
If flashing fails or you get any error, then try booting into recovery.
Code:
fastboot boot recovery.img
If you boot into recovery, flash the SuperSU package.
Reboot and then flash the recovery.
See if it works.
Click to expand...
Click to collapse
no
flashed CWM from here http://forum.xda-developers.com/showthread.php?t=2793625
concretly from here http://www.mediafire.com/download/6odyyqgodw15f1b/recovery.img
then i flashed it, then i rebooted phone then i shuted it off (to boot into fastboot) in fastboot i selected recovery and again, that screen with android figure (no command) so i pressed power button for long. mobile rebooted. again i went into fastboot to write command you said me to boot into recovery. but i stucked at starting screen (that blue big M in "water" cycle)
this all means, files i downloaded was OK but my phone isnt :/
any idea :/
Mondop said:
no
flashed CWM from here http://forum.xda-developers.com/showthread.php?t=2793625
concretly from here http://www.mediafire.com/download/6odyyqgodw15f1b/recovery.img
then i flashed it, then i rebooted phone then i shuted it off (to boot into fastboot) in fastboot i selected recovery and again, that screen with android figure (no command) so i pressed power button for long. mobile rebooted. again i went into fastboot to write command you said me to boot into recovery. but i stucked at starting screen (that blue big M in "water" cycle)
this all means, files i downloaded was OK but my phone isnt :/
any idea :/
Click to expand...
Click to collapse
Do not flash CWM, just boot into it by the command I posted above.
Then try and flash SuperSU, (if you get a root prompt from CWM, select NO.)
Reboot device.
Then again boot into fastboot and now flash recovery (twrp).
neo.ank said:
Do not flash CWM, just boot into it by the command I posted above.
Then try and flash SuperSU, (if you get a root prompt from CWM, select NO.)
Reboot device.
Then again boot into fastboot and now flash recovery (twrp).
Click to expand...
Click to collapse
so now what if i flashed that CWM before?
Now i tried go to fastboot and used just command that you said(to boot into recovery) and as i said, i stucked on motorola starting logo
+ you said i have to flash cwm
Mondop said:
so now what if i flashed that CWM before?
Now i tried go to fastboot and used just command that you said(to boot into recovery) and as i said, i stucked on motorola starting logo
+ you said i have to flash cwm
Click to expand...
Click to collapse
I said if flash is not successful, then boot into it. So you can't boot into recovery either.
Here's last resort, extract the stock recovery from stock ROM and flash it. Then we'll try flashing TWRP again.
If you don't have stock ROM, download it. as you might need it to recover.
neo.ank said:
I said if flash is not successful, then boot into it. So you can't boot into recovery either.
Here's last resort, extract the stock recovery from stock ROM and flash it. Then we'll try flashing TWRP again.
If you don't have stock ROM, download it. as you might need it to recover.
Click to expand...
Click to collapse
Okay, can you give me link with tutorial? i found just this one which restores whole system (and its 4.4.3 and i have now 4.4.4, i mean this will be maybe problem, wouldn´t it?)
i mean this one (tutorial how to restore moto E)
http://forum.xda-developers.com/showthread.php?t=2759495
did you try updating / reinstalling USB-driver on your computer?
magicw said:
did you try updating / reinstalling USB-driver on your computer?
Click to expand...
Click to collapse
no i didnt, think you it will help? i mean if i can connect my mobile into pc without any problem in normal mode and in fastboot too... i will unninstal drivers, intall them again and them i will try unninstal motorola device manager and then again intall him.
(i had newest drivers i can update them)
LOL?
OK im in recovery i already flashed superSU...
What did i do?
As you said, i reinstalled all drivers...
then i downloaded same TWRP again (but with mirror source)
I downloaded attached md5 file ( still dont know what should i do with it )
moved recovery and .md5 files into minimal adb and fastboot (both files i renamed to "recovery")
turned off devices
started fastboot
connected to PC
started command window and entered command "fastboot flash recovery recovery.img"
then i didnt wrote sommand "fastboot reboot" as i done before
i just unpluged usb and navigate to recovery button and launched it
and VUALA im in recovery
hurraaa
just installed superSU and then rebooted.
everything works (superSU too)
i have one more question...
i downloaded twrp manager from google play
first start: asked for root permission a allowed it
then message appeard:
"The only compatible version of busybox we support is Stericson. All other cause havoc on all operations in this app. Please click yes to install Stericson busybox"
what the heck is busybox?
+Should i download it or not?
Do not use TWRP Manager, ROM Manager, CWM Manager or any other of these Tools. They often do not really work good together with "exotic" fones. Why the heck do you need TWRP manager? You have TWRP installed
Anyway - Busybox you also can download and install from Playstore. Busybox is a collection of executable terminal commands helpful for any kind of script. There are a couple of rooted apps who will ask for busybox support - so don't hesitate to install busybox - but do it directly with busybox app from playstore.
After you have installed the binaries you can de-install the busybox-app. Because all necessary binaries then are copied into /system/bin/ folder and the app itself only will become active once a new version would be available (but this is not the case very often).
ok then
magicw said:
Do not use TWRP Manager, ROM Manager, CWM Manager or any other of these Tools. They often do not really work good together with "exotic" fones. Why the heck do you need TWRP manager? You have TWRP installed
Anyway - Busybox you also can download and install from Playstore. Busybox is a collection of executable terminal commands helpful for any kind of script. There are a couple of rooted apps who will ask for busybox support - so don't hesitate to install busybox - but do it directly with busybox app from playstore.
After you have installed the binaries you can de-install the busybox-app. Because all necessary binaries then are copied into /system/bin/ folder and the app itself only will become active once a new version would be available (but this is not the case very often).
Click to expand...
Click to collapse
i have no reason to want twrp manager, i just wanted to look at this app, and i found that busybox there so i wanted to ask here
thx for answer, now i undertand

Can't get onto latest TWRP

So I am stuck on TWRP 2.7.1.0 and i am running slimrom 4.4.4 on a c6833 and the reason for this is because it's the only thing that will boot on my phone. There was some intense trial and error a few months ago and a few days with a bricked phone but I finally got it running again, and I am nervous about messing things up again.
I am wanting to move to a more up to date ROM either scrubber port 5.1 or remix 5.1.1, but they both ask for updated TWRP to install. And I can't update TWRP using the TWRP tool from the store. It downloads but when it tries to install it says there is a problem. Previously, trying to update TWRP would result in SONY bootloops. I was about to try the dd method but just wanted to make sure it was safe.
I am a bit of an idiot (I got rid of my encrypted keys on day 2 of owning the phone) so any help would be appreciated.
Thanks!
walkingagh said:
...
Click to expand...
Click to collapse
The easiest way is to use Rashr. It should set everything up automatically. You may then reboot to recovery from the ROM, or by holding Vol- when the LED turns purple on boot-up.
If that doesn't work, for whatever reason, try dd or Flashtool. Using Flashtool, you can flash openrecovery-twrp-2.8.5.0-togari.img with the phone in Fastboot mode.
Let me know if you have any further questions!
Used Rashr...and now I can't get into recovery. I can still boot into my phone, but booting into recovery just fails with a yellow LED?
So Rashr still says I have 2.7.1.0 installed. :/
walkingagh said:
Used Rashr...and now I can't get into recovery. I can still boot into my phone, but booting into recovery just fails with a yellow LED?
Click to expand...
Click to collapse
Alright, you likely need a newer kernel first. Using Flashtool, you can flash this boot.img (newest AICP kernel) to the boot partition using the Fastboot mode (or use fastboot manually from the Flashtool/x10flasher_lib folder with "fastboot flash boot boot.img"). At this moment, you'll no longer be able to boot into the ROM, so make sure you've done all necessary backups and are ready to install a newer ROM. Then use Flashtool/Fastboot to flash the openrecovery-twrp-2.8.5.0-togari.img file to your recovery/FOTAKernel partition ("fastboot flash recovery openrecovery-twrp-2.8.5.0-togari.img"). You should be able to enter recovery now.
Awesome thanks! Will I need to do this each time I flash a ROM? Or can I just jump from something like scrubber to something else?
I know this is an old thread but is that the boot image I need to run TWRP 3? If so, can I do this via dd?
Triflot said:
Alright, you likely need a newer kernel first. Using Flashtool, you can flash this boot.img (newest AICP kernel) to the boot partition using the Fastboot mode (or use fastboot manually from the Flashtool/x10flasher_lib folder with "fastboot flash boot boot.img"). At this moment, you'll no longer be able to boot into the ROM, so make sure you've done all necessary backups and are ready to install a newer ROM. Then use Flashtool/Fastboot to flash the openrecovery-twrp-2.8.5.0-togari.img file to your recovery/FOTAKernel partition ("fastboot flash recovery openrecovery-twrp-2.8.5.0-togari.img"). You should be able to enter recovery now.
Click to expand...
Click to collapse
That file has expired, any chance you can re-post it?

Categories

Resources