Question is basic; can someone with experience please give me the low-down when it comes to TWRP? I am new to Android in the sense but consider myself somewhat tech savvy. I test software and provide technical support for a living so I completely understand that people can do some dumb stuff. Just yesterday I had a man on the phone trying to connect his Pidion PDA to a McDonalds Wi-Fi by standing in his front yard and pointing it in the direction of a McDonalds two miles away. Anyhow I got the device for X-mas and have spent every day since reading about constant issues using TWRP. I’m really just trying to figure out if the blame for these issues can be pinned down on either the recovery itself or the fact that Millions of these things are in the hands of people who should probably not be doing the things they are doing at their current levels of knowledge, or a combination of both? I have owned a Moto-Triumph for a few month and have flashed Roms & Kernels out the Wahoo using CWM and have become very comfortable with its reliability but had not heard of TWRP until a few weeks ago and the association I have goes with all the stuck on Yellow Triangle posts covering just about every forum. I have TWRP installed and running CM7 and if this was my phone I would have flashed 2 Roms by lunch but for the reasons above feel like I should have a day set aside for trouble shooting before considering doing a simple thing like restoring a stock Nandroid. I lucked out with the Phone having an unlocked loader and Sudo installed out the box. Sorry I tend to rant but am basically asking that if I know my way around Roms and CWR will I be OK using TWRP or should I expect that it will have the occasional hiccup or is unstable in any way?
chairshot215 said:
Question is basic; can someone with experience please give me the low-down when it comes to TWRP? I am new to Android in the sense but consider myself somewhat tech savvy. I test software and provide technical support for a living so I completely understand that people can do some dumb stuff. Just yesterday I had a man on the phone trying to connect his Pidion PDA to a McDonalds Wi-Fi by standing in his front yard and pointing it in the direction of a McDonalds two miles away. Anyhow I got the device for X-mas and have spent every day since reading about constant issues using TWRP. I’m really just trying to figure out if the blame for these issues can be pinned down on either the recovery itself or the fact that Millions of these things are in the hands of people who should probably not be doing the things they are doing at their current levels of knowledge, or a combination of both? I have owned a Moto-Triumph for a few month and have flashed Roms & Kernels out the Wahoo using CWM and have become very comfortable with its reliability but had not heard of TWRP until a few weeks ago and the association I have goes with all the stuck on Yellow Triangle posts covering just about every forum. I have TWRP installed and running CM7 and if this was my phone I would have flashed 2 Roms by lunch but for the reasons above feel like I should have a day set aside for trouble shooting before considering doing a simple thing like restoring a stock Nandroid. I lucked out with the Phone having an unlocked loader and Sudo installed out the box. Sorry I tend to rant but am basically asking that if I know my way around Roms and CWR will I be OK using TWRP or should I expect that it will have the occasional hiccup or is unstable in any way?
Click to expand...
Click to collapse
I have had no hiccups or any other problem, backing up. restoring or flashing.
TWRP is awesome, backups and restores work great. The main issues are people getting stuck in fastboot, which is not really a TWRP issue. As long as you follow directions, you should have no issues.
Sent from my Kindle Fire (CM7) using xda premium
borborpa said:
TWRP is awesome, backups and restores work great. The main issues are people getting stuck in fastboot, which is not really a TWRP issue. As long as you follow directions, you should have no issues.
Sent from my Kindle Fire (CM7) using xda premium
Click to expand...
Click to collapse
I feel the same way as the OP. I have cwr on my phone and I have never messed up anything. I have roms backed up and I can always get up and running quickly. I have tried half assed roms just for the heck of it and no problem.
I don't think that TWRP is the same kind of program as CWM. I think it's almost impossible to brick my phone using clockword mod but I don't think the same can be said for TWRP. I have read so many posts with people who have TWRP installed and yet they manage to "brick" their device. I don't know if it's a TWRP issue or that the kindle is very sensitive. Nevertheless, I am not rooting it because of these issues, besides, I like stock (I would love swype, that's about it).
Twrp works great. They forgot to set it to change bootmodes leaving recovery so don't use apps to force into recovery. Just firefirrfire.
Most issues, are user errors. I haven't had one issue, and I test everything!
Sent from my Kindle Fire using xda premium
although I havent had any issues (that I can think of) with twrp, the constant "cannot mount /misc !" really bothers me. twrp is on several devices and from what I understand about it... the dev responsible for twrp being on the kindle fire joined twrp, got it working for the fire, they rolled out twrp 2.0 then he quit the team to make a recovery + app he plans on being paid only. so with that said... who knows if twrp will be maintained for the fire?
I hate to bash on anyones work, I didnt have any problem flashing zips with it. I dont really backup/restore much but the few times I tried, it worked. I really like the fact it can be themed easily
foxdog66 said:
although I havent had any issues (that I can think of) with twrp, the constant "cannot mount /misc !" really bothers me. twrp is on several devices and from what I understand about it... the dev responsible for twrp being on the kindle fire joined twrp, got it working for the fire, they rolled out twrp 2.0 then he quit the team to make a recovery + app he plans on being paid only. so with that said... who knows if twrp will be maintained for the fire?
I hate to bash on anyones work, I didnt have any problem flashing zips with it. I dont really backup/restore much but the few times I tried, it worked. I really like the fact it can be themed easily
Click to expand...
Click to collapse
That's a great concern. Which is why I've been Working with doomlord to bring clockworkmod to our kindle fires. We need support. Twrp does not have that. But it works.
Sent from my Kindle Fire using xda premium
Thanks for the responses; I think my fears stem from unfamiliarity. Like I said above everything was easily with my Triumph, was able to install CWM without Rooting the stock Rom and outside of doing something dumb like frying the CPU always felt comfortable knowing I could easily get back up and running no matter how bad I messed things up. I’m sure I will be fine, just need to get used to doing things a little differently and school myself on ADB and Fastboot and as recommended above avoid any apps or options for rebooting into recovery.
I haven't had any issues with twrp so far. Installing was a little tricky when i got stuck at the yellow triangle but after that everything has been good so far.
I have TWRP on both my kindle fire and my wife's and neither has had a single issue with it. My brother, who is not what I would call tech savvy, installed it onto his just a couple days ago without issue by reading the instructions and multiple threads posted around here without issue. I think a lot of the issues come from people not reading as closely as they should or just from getting overly excited about being stuck in fastboot.
Sent from my MB860 using Tapatalk
I would like to put twrp on my phone. It works great. Half of what cwm does fails on my phone. Twrp works every time. People having issues likely can't follow instructions and don't have the knowledge if adb to fix their mistakes
Sent from my SGH-I897 using xda premium
all win
TWRP is all win. If you follow directions to a T and dont frustrated it will work fine. In alot of ways TWRP is better than CWM.
The TWRP team is maintaining TWRP. Even though the head developer left, If you would have read there tweets they are taking some time off. They Even Had announced a Twrp 3 for release, But for now everything is onhold until the team is better organised.If a developer would contact the team for the source, the xda community can keep it maintained.
Related
I come from Windows Mobile. I got all of them on SPrint and was flashing my phones on a weekly basis. It was pretty easy and simple.
Here I got the Epic on day one and have waited until the unofficial DK28 was released. That was an easy flash.
However when I look at the ROMS available (Viper, etc...) I see that it is way too complicated to flash. A hundreds of steps and stuff to get into. EXT4 looked like a hassle to install. Odin sounds like something crazy annoying.
When I see that whole list of stuff to go thru I just get lazy. Is it that complicated or I should give it a try? Is it worth it.
My battery is HORRIBLE with DK28. I get like 3 hours of battery. While with DI18 I hat like 20 hours. But I have put all my app to sd card so im basically stuck with froyo even if i wanted to go back....
don't be scared! we are right here if you need help>>>
Its not that its harder then winmo..its just there is more room for customization..the EXT 4 hack for example you would never be able to do on a winmo device..its an added bonus to optimize the device and make it better.
The use of Odin is mostly used for when you brick your phone, or to update to Froyo..
Otherwise most things are done via Clockwork..
I suggest to start simple, root, load a custom rom and etc..once you get used to that and feel like your ready for the next step do that..no reason to tackle everything at once..
Bro dont worry i new to this as well, coming from the windows mobile also. We also got youtube vids to help us out, it makes it that much easier.
Sent from my SPH-D700 using XDA App
Its you. Odin is simple as hell. EXT4 is unnecessary. Complaining about how hard it is to flash a beta build of froyo with a new filesystem ported less than a week ago is ridiculous. Of course that will be difficult. Wait for official froyo to drop sometime in the next couple of years, and then everything will get easier. Windows mobile was no treat. Activesync was a disaster and you couldn't flash anything without it.
Just ask for help, we got your back! Join the dark side. Hahahahahahahah
Sent from my SPH-D700 using XDA App
I used to have an HTC Touch Pro 2 and flashed my phones all the time.
Flashing on Android is *way* easier! including the Epic.
You don't need a PC
Your apps/data are preserved when you flash
It's not really as intimidating as it looks. I was pretty nervous too when I first flashed. With time, I realized that it is actually faster than installing Linux or another operating system onto my PC.
If you don't like a ROM or if there's a ROM that's giving you issues, just try another ROM. Try many and see which one is your favourite. The chances of your bricking your phone are pretty slim. Just remember to read instructions and comments carefully.
You can do it!
Everything except the EXT4 stuff is easy. EXT4 stuff isn't for the feint of heart, but if you're comfortable with shell commands, there's nothing to it!
chnzshyguy said:
Everything except the EXT4 stuff is easy. EXT4 stuff isn't for the feint of heart, but if you're comfortable with shell commands, there's nothing to it!
Click to expand...
Click to collapse
Not anymore - Daemon has a newer ext4 way of flashing. The only drawback is that it replaces the current CWM with CWM 3 which only supports Edify.
I was in the same boat at first coming from WinMo but Android is even simpler once you know what you are doing.
My recommendation is to first Flash a rom other than viper.
Once you are rooted, you can boot into clockwork recovery and flash a new rom directly from a zip file on your sd card. You can flash multiple roms without even having to be near a computer.
Some other popular forums have some stickies that provide dead simple walk-thrus too.
I'm on the viper ext4 and its simple to flash. All you do is flash 4 files in order and there you go your on ext4 and great rom. I've tried every rom on here and imho the most stable ones are epic experience and viper. But I've been running viper for a week or so and love it. Especially ext4, my phone is so much more snappier now.
If you think those are the most stable you havnt tried mine,Frankenstein FROYO.
Sent from my SPH-D700 using XDA App
Dude it's easy. If you're already on DK28 then half the job is done. Just root with with any of the oneclick, install cwm and that's it. Trust me, flashing with Android is easier than Win Mo (download a zip file and flash it..easy) . I can't count how many times I had problems with hard spl on Win Mo.
Don't let all that Odin/PDA/Pit/modem stuff intimidate you.
muyoso said:
Its you. Odin is simple as hell. EXT4 is unnecessary. Complaining about how hard it is to flash a beta build of froyo with a new filesystem ported less than a week ago is ridiculous. Of course that will be difficult. Wait for official froyo to drop sometime in the next couple of years, and then everything will get easier. Windows mobile was no treat. Activesync was a disaster and you couldn't flash anything without it.
Click to expand...
Click to collapse
dude why is it you find that you have to insult everytime you post?
I'm kinda in the same boat as the OP. I want to run a custom ROM on my Epic, but every time I get to the point where I decide to go for it I look at the laundry list of steps and the horror story posts from people who screwed them up and I chicken out LOL
Sent from my SPH-D700 using XDA App
themirthfulswami said:
I'm kinda in the same boat as the OP. I want to run a custom ROM on my Epic, but every time I get to the point where I decide to go for it I look at the laundry list of steps and the horror story posts from people who screwed them up and I chicken out LOL
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
What laundry list of steps?? Simple steps, root>clockwork>find rom of choice>d'load rom>boot into clockwork>flash zip file.
Definitely easier than doing laundry for me. (I never know when to use/pour fabric softner thingy).
What laundry list of steps?? Simple steps, root>clockwork>find rom of choice>d'load rom>boot into clockwork>flash zip file.
Click to expand...
Click to collapse
Well from what I see the current install instructions for Viper list 15 steps and that assumes you already have root access and clockwork/rom manager going. I'm very comfortable building/tweaking Windows boxes because I know what to do if I screw up and can fix it pretty quickly.. this ROM flashing stuff for someone who's been using Android for a couple months seems intimidating mostly because I'm not familiar with the tools or how to recover easily in a panic situation.
You can do it bro. I didn't even know what rooting was two months ago. Lol. Now after reading and trial and error and all the help from people on here I flashed every rom on 2.1 and almost all on 2.2. I have the new cwm3, a theme and the black market. Like they have been saying just start slow. Root first. Thank you to all who have helped me.
themirthfulswami said:
Well from what I see the current install instructions for Viper list 15 steps and that assumes you already have root access and clockwork/rom manager going. I'm very comfortable building/tweaking Windows boxes because I know what to do if I screw up and can fix it pretty quickly.. this ROM flashing stuff for someone who's been using Android for a couple months seems intimidating mostly because I'm not familiar with the tools or how to recover easily in a panic situation.
Click to expand...
Click to collapse
I came from WM too. Android seems very intimidating but it really isn't.
http://forum.xda-developers.com/showthread.php?t=770388
follow those steps to root and get Clockwork mod. which is just downloading samsung drivers, Putting your phone into debugging mode, and downloading and opening the bat file.
once you do that your rooted and you can flash some 2.1 roms. Once you feel comfortable with that you can use odin to flash your modem to froyo.
I'm new at Android (have jailbroken Iphones before) so these questions are probably basic.... I have a KF that has been rooted, but until ICS is stable, and maybe not even until it gets USB host mode (if ever), I will probably not be changing ROMs. I am mostly happy with the current state of the KF, but have been reading forums. I see that TWRP can save you later on if you mess something up, so that brings up quesitons. BTW, I followed the tutorial on androidpolice to get the root done. S, on to the Qs...
1) Should I install TWRP on my device if I don't plan to put on any ROMs?
2) How can TWRP help you?
3) Any concerns with installing TWRP at this point, when everything is working?
TWRP is working just fine. It allows you to make backups of the current setup in case you break things.
Sent from my Kindle Fire (CM7) using xda premium
Absolutely reccomended. ESPECIALLY if you are new. It alwows easy backups and recoveries in case you jack something up.
1 thing ur iphone never couod do, make a true backup of ur current state. it saves u down the road. i have a backup of completely stock and i make one of cm7 every now n than just incase
sent from my kindle fire
Thanks for all the advice. I did install TWRP last night. Simple to do, made a backup, and all is well. Thanks for all the advice.
TWRP Recovery is officially dead. I just tried to use it with the latest Kindle version and it is not working for me at all.
However I was able to use Custom CWM Beta 2 http://forum.xda-developers.com/showthread.php?t=1454241.
I was able to fast boot to its recovery mode and make a backup of my Kindle. Thank goodness! Now I feel confident trying out something else besides Amazon's underwhelming Android.
While development on TWRP 2.0 has been halted it still works just fine. I have it on my Wife's fire. There is no functional reason for it to stop working.
I have CWM-Touch modified by DooMLoRD on mine and it works as well.
From the OP's message it is not clear if he had problems loading it, or using it, though I can't think of why if it was loaded it wouldn't work.
I guess my point is ...
Its not worth using something that is dead and that the Custom CWM-Based Touch Recovery 5.0.2.7 for Kindle Fire works just fine and is in active development. I'd rather spend my energy testing and using CWM Touch than TWRP at this point.
Its install process was easier and actually worked for me while the TWRP install did not work for me at all. TWRP never showed an install or reboot screen like it was supposed to.
TWRP works fine. Just a matter of preference.
misleading subject line.
I think it a little misleading to say twrp is dead.
I've never used cwm, I suspect it works just as good.
If it ain't broke don't fix it. If you can give me a valid reason why I
should switch I will. And it being actively developed isn't good enough.
I was on 6.2.2, installed Burritoroot 3 via adb, downloaded twrp 2.0 manually and put it into the kindle utility folder (check the batch-file for correct name) and pressed "install twrp" in kindle utility.
For a "officially dead and not working software" it was pretty easy to install and works like a charm.
twrp works fine as long as you never "reboot to recovery". twrp never fixed the bootmode during system reboot.
I switched, because of no support. I love cwm, and I'm familiar with it. plus, reboot system properly sets the boot mode. which to me. is what's supposed to happen.
Sent from my HTC Glacier using XDA App
Sambena said:
I think it a little misleading to say twrp is dead.
I've never used cwm, I suspect it works just as good.
If it ain't broke don't fix it. If you can give me a valid reason why I
should switch I will. And it being actively developed isn't good enough.
Click to expand...
Click to collapse
Only it isn't misleading. TWRP is dead. It is no longer being developed.
See here http://teamw.in/blog/15 where they say "We will be abandoning twrp". They also state that they will be putting their efforts directly into ClockworkMod. Which I think is commendable and will actually help improve CWM Touch in the long run.
We should support and use active projects. As TWRP being abandoned is relatively new news I thought I would post about it because I only found out about it after researching how to get it installed properly. I abandoned trying to make it work when I realized it was no longer being developed and CWM Touch seemed to be the place to go given the news.
Well, I first of all was using TWRP 2.0 as my recovery. However, i did not know that it was known to cause bricks. Anyway, I was doing a routine clean flash of a new rom i wanted to try, the aokp build 22 rom. I wiped everything, making sure to hit wipe system as well in twrp, then i put my phone to mount the sd card, transfered the rom, flashed it and its gapps then i reboot. Now all my phone can do is reboot endlessly, So I got into the bootloader and selected recovery, still, just keeps bootlooping. So then I decide to find an RUU and flash it through fastboot. It flashed everything correctly but when it got to step 4, (system) the phone would say error and it would fail to flash the system. After this I was still at bootloop. I dont know what it is, I even tried flashing Amon_Ra through fastboot, and ive been able to get to recovery once or twice but just to find it completely unresponsive and it wont read/mount my SD card even though i checked and the sd card was fine. All in all, I took it over to sprint and since i have TEP they agreed to get me a new one, though it was backordered so now im a week without a phone. Anyway just wanted to share my story, if anyone else knows of a way to fix it, im all yours.
TWRP kills. Good luck. Sorry you didn't follow up regularly on the thread of the product you were using. If anyone can help you, it might be Captain Throwback, but I think he's been a bit busy lately (i.e. been absent). Good luck, but TWRP fncks you.
sent from AOKP heaven
TWRP2.0 is an evo killer as far as I know there is no fix for a TWRP brick I'm pretty sure it messes up something in the partitions possibly boot or system partition which is why it bootloops
We are legion, for we are many
Unfortunately your phone is toast. Had the same problem, and really there is no way to recover. You should have bit the bullet in used insurance instead of going through Sprint since the Evo is past EOL. You maybe waiting a long time to get a replacement where as going through Ausion (sp) you either would have gotten either a new Evo, a refurb'ed Evo, or a new Evo3D (most likely).
Sent from my ICS-less Transformer TF101 using Tapatalk
Art2Fly said:
Well, I first of all was using TWRP 2.0 as my recovery. However, i did not know that it was known to cause bricks. Anyway, I was doing a routine clean flash of a new rom i wanted to try, the aokp build 22 rom. I wiped everything, making sure to hit wipe system as well in twrp, then i put my phone to mount the sd card, transfered the rom, flashed it and its gapps then i reboot. Now all my phone can do is reboot endlessly, So I got into the bootloader and selected recovery, still, just keeps bootlooping. So then I decide to find an RUU and flash it through fastboot. It flashed everything correctly but when it got to step 4, (system) the phone would say error and it would fail to flash the system. After this I was still at bootloop. I dont know what it is, I even tried flashing Amon_Ra through fastboot, and ive been able to get to recovery once or twice but just to find it completely unresponsive and it wont read/mount my SD card even though i checked and the sd card was fine. All in all, I took it over to sprint and since i have TEP they agreed to get me a new one, though it was backordered so now im a week without a phone. Anyway just wanted to share my story, if anyone else knows of a way to fix it, im all yours.
Click to expand...
Click to collapse
scottspa74 said:
TWRP kills. Good luck. Sorry you didn't follow up regularly on the thread of the product you were using. If anyone can help you, it might be Captain Throwback, but I think he's been a bit busy lately (i.e. been absent). Good luck, but TWRP fncks you.
sent from AOKP heaven
Click to expand...
Click to collapse
It's been a busy week for me, but I am still alive, and still using my previously-soft-bricked device .
I can link you to what I was able to do to get mine working (HERE), but if you can't get the device to boot up at all, you might be in dire straits. What is your HBOOT status? (version, NAND status)
hey Cap'n, you need some kind of superhero shield in your user icon
sent from AOKP heaven
Well I'm coming over to the Xoom area now. Picked up two Xoom's (32 gb/WiFi) on Amazon for a good price and looking fwd to all the development you guys have going on over here. Currently been pretty hooked on my Razr w/ the latest round of soaks and OTA's for 4.0.4 along w/ the custom roms.
Right now just reading as much as I can so when both tabs get here on Tuesday I'll be ready to go, have all my files in place, etc.
I promise I won't ask any stupid questions in your guys' section w/ out searching, searching, searching!!!
Figure I'll run one stock 4.0.4 and the other w/ CM9 or EOS. Whichever I like better I'll put on the stock 4.0.4 and give to my g/f. As you can see I've had a variety of tabs/devices and always wanted a Xoom. Thought about getting some of the latest and greatest like the Excite or TF300 but I'm a sammy and moto fanboi and just can't bring myself to do it. I'd rather Moto give up on the Xyboard and release a front runner soon since Sammy looks like they have no intentions of going for performance, and instead focusing on price (ala Galaxy Tab 2, nothing wrong with that btw).
Hey young man
Nice to see another one coming to the dark... *cof**cof*... light side of the force lol
Just kidding... Anyway, if you want root I recommend my tool (LordAIOTool), as many people it's easy and good to do that kind of stuff on Xoom, one guy even mentioned it as "The Ultimate Xoom Tool". Hope you have fun here
Sent from my 3G Xoom using XDA HD - 1st Xoom Recognized Contributor
Well the first tab arrived and let my g/f have that one. Came from Amazon Warehouse and it was a used India Tab. Therefore got it to US 3.0 and then upgraded to 4.0.4 allowing system updates to run their course. I then unlocked and used your tool to root. Worked flawlessly. Thank you for that!
Then tried adb'ing both eos recovery and team rogue recovery. Both I'm having issues with. The issue is it will go to either recovery fine immediately after flashing. However if I let the tablet boot up or reboot and try to access recovery again, it goes back to the stock recovery. Either way I got EOS 2.0 Rom installed which is a lovely piece of work. Will probably run their nightlies when my Xoom gets here.
Just wish I could figure out that issue w/ returning to stock recovery. I've searched and searched and searched and no such luck. Doesn't matter much, I suppose, as my g/f doesn't like me messing with her devices and having to factory reset so I suppose I will leave it as is, for now.
got556 said:
Well the first tab arrived and let my g/f have that one. Came from Amazon Warehouse and it was a used India Tab. Therefore got it to US 3.0 and then upgraded to 4.0.4 allowing system updates to run their course. I then unlocked and used your tool to root. Worked flawlessly. Thank you for that!
Then tried adb'ing both eos recovery and team rogue recovery. Both I'm having issues with. The issue is it will go to either recovery fine immediately after flashing. However if I let the tablet boot up or reboot and try to access recovery again, it goes back to the stock recovery. Either way I got EOS 2.0 Rom installed which is a lovely piece of work. Will probably run their nightlies when my Xoom gets here.
Just wish I could figure out that issue w/ returning to stock recovery. I've searched and searched and searched and no such luck. Doesn't matter much, I suppose, as my g/f doesn't like me messing with her devices and having to factory reset so I suppose I will leave it as is, for now.
Click to expand...
Click to collapse
You don't want stock recovery on the Xoom...can't really do anything with it.
got556 said:
Well the first tab arrived and let my g/f have that one. Came from Amazon Warehouse and it was a used India Tab. Therefore got it to US 3.0 and then upgraded to 4.0.4 allowing system updates to run their course. I then unlocked and used your tool to root. Worked flawlessly. Thank you for that!
Then tried adb'ing both eos recovery and team rogue recovery. Both I'm having issues with. The issue is it will go to either recovery fine immediately after flashing. However if I let the tablet boot up or reboot and try to access recovery again, it goes back to the stock recovery. Either way I got EOS 2.0 Rom installed which is a lovely piece of work. Will probably run their nightlies when my Xoom gets here.
Just wish I could figure out that issue w/ returning to stock recovery. I've searched and searched and searched and no such luck. Doesn't matter much, I suppose, as my g/f doesn't like me messing with her devices and having to factory reset so I suppose I will leave it as is, for now.
Click to expand...
Click to collapse
adb'ing the recovery isn't the best way to go about it. Use fastboot (fastboot flash recovery recovery.img) should work fine.
What I'm saying is guys, I have added custom recoveries (by way of fastboot flashing the .img recovery file). Tried both Rogue and EOS recoveries. They work fine the first time I flash them, but then no matter if I try to use the hard buttons or just use commands to get into recovery it always reverts back to the stock recovery. (As in, dead android, red triangle, then I have to hit power + vol up which brings up stock recovery).
It's as if the custom recoveries aren't sticking.
With stock recovery, do you have the option , "install zip from sd card"?
If you do, I will send you a recovery zip, not image, to be installed from within recovery, not adb... let me know.
Sent from my MZ601 using Tapatalk 2
There you go, http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.zip
Just boot into your existing recovery,
Choose install zip from sd card and flash this.
If it doesn't work, I am afraid you need to to unlock your bootloader again and flash the recovery image again. If that is needed, will help you with steps. Try this first and let me know.
Good luck.
Sent from my MZ601 using Tapatalk 2
We're gtg all. Don't think I did anything different but Rogue recovery works every time now.
Thanks for all the help and suggestions! W/ being on EOS 2.0 my g/f has practically streamed Netflix non stop all day starting at 71% battery life and she just plugged the charger in a little bit ago. It was one of those lazy days and she's in the middle of a season on one of her shows.
Crazy good battery life.
got556 said:
We're gtg all. Don't think I did anything different but Rogue recovery works every time now.
Thanks for all the help and suggestions! W/ being on EOS 2.0 my g/f has practically streamed Netflix non stop all day starting at 71% battery life and she just plugged the charger in a little bit ago. It was one of those lazy days and she's in the middle of a season on one of her shows.
Crazy good battery life.
Click to expand...
Click to collapse
Oh yeah, and the wifi Xoom is slated to get the jelly bean os update next month! You really made a great choice!