Related
Hey Everyone,
Im new to android, and having a small issue, I am attempting to root my wifi xoom, I get up to the part where its time to select android recovery so that I can select the root zip, however when I use the volume down key to scroll the options the only 3 available are NVflash, RSD and Fastboot, theres no android recovery option I have searched the forums and googled it, but I seem to be the only one with this issue, my xoom is running 3.1 and bought in Aus, dont know if this makes a difference? any help would be greatly appreciated, I have got an OTG cable and would like to mount my external HDD so I need to get it rooted. Should probably mention I have unlocked it too.
Cheers
ha i just posted a thread with exactly the same issue. Hopefully one of us will get an answer!
djleez82 said:
ha i just posted a thread with exactly the same issue. Hopefully one of us will get an answer!
Click to expand...
Click to collapse
Your post was already answered in the General section. No need to post twice.
The answer did not fix my problem however. Still stuck at the same place as before just like terreboo. Possibly theres an issue with this type of xoom? I bought mine in australia as well. According to my about tablet info it says this:
Firmware Configuration Version: GAS_ASIA_UCAHUBLWFRTIRD_P006 so im assuming this is an asian tab? Just wondering terreboo what does yours say under firmware configuration?
yeah sorry didnt mean to post it in the general section, I alerted it to the mods to delete they just havent got around to it yet, yeah mate I have the same version as you, although I doubt this is the reason, we cant be the only two in Aus trying to root them? I think the problem probably lies else where, it has been suggested I'm getting the timing wrong, so I'll try again and post back my progress or lack of.
---------- Post added at 10:01 PM ---------- Previous post was at 09:45 PM ----------
I have tried it 10+ times now, I'm confident its not the timing of pressing the down key on reboot having varied the length of time everytime I tried, possibly its because of the firmware version? Im at a loss, I have followed the instructions of the root guide to the letter and seem to be one of the only ones with this problem!
this is the guide im using
http://forum.xda-developers.com/showthread.php?t=1078019
Same problem here!
I have the same problem guys.. Any solution?? The developers some help??
Im using the same guide btw....
I've freaked out im trying this for 8 hours now and no results....
im having a similar problem that my factory reset is corrupt or something because it doesnt actually DO anything.
I did the long root method as opposed to the supposedly easier method and thank heavens I got through it unharmed. I was ****ting my pants the whole way through. I wish I were more savvy with this so I can offer help. If I were u guys I would PM the devs from TIAMAT. They are probably the most knowledgeable ppl here to ask.
solution
OK guys i have a solution a guy from #xoom channel told me to write in windows command line
abd recovery reboot
And it worked!
I'm currently posting this from my costum rommed xoom
DrGreem said:
OK guys i have a solution a guy from #xoom channel told me to write in windows command line
abd recovery reboot
And it worked!
I'm currently posting this from my costum rommed xoom
Click to expand...
Click to collapse
Would that be adb recovery reboot? Can you give more information?
assuming you have adb setup on your computer already. Plug your xoom into your comp and make sure its in debug mode. Settings-applications-development. Open a command prompt and type in "adb reboot recovery" without quotes. Your device will then reboot into recovery mode.
I will say I'm having the same issue. I flash the new recovery and I don't see it in the menu. I'm running a US wifi xoom.
okantomi said:
Would that be adb recovery reboot? Can you give more information?
Click to expand...
Click to collapse
Yes that's right. I followed the guide and i waited 3 seconds but i never had the option 'android recovery so i turned on the device and this guy told me to run this command from cmd.
So after that xoom rebooted into clockwork recovery state and i flashed thecostum rom.
According to the guide that were using, if you allow the xoom to boot fully into honeycomb it reinstalls the stock recovery, and you need to redo the process all over. Also, you need to be in honeycomb to use the ADB command, if your in fastboot it won't detect the xoom. This did not work for me. Anyone else try it?
no luck for me here either. I can flash recovery successfully (according to the prompt) no problems there. I just have the exact same trouble booting into it as above.
Vol Down key combo doesn't work and if you leave the OS to boot straight after install, CWM is replaced by stock recovery. No fun at all.
Any further news or suggestions on this?
autodc5 said:
im having a similar problem that my factory reset is corrupt or something because it doesnt actually DO anything.
Click to expand...
Click to collapse
Same as my Xoom, opened a thread just for it, but no one can help
much easier... download rom manager and click boot to recovery haha ...
If not rooted,
adb reboot recovery via a cmdline window works a treat _
fkofilee said:
much easier... download rom manager and click boot to recovery haha ...
If not rooted,
adb reboot recovery via a cmdline window works a treat _
Click to expand...
Click to collapse
Just make sure that Rom Manager doesn't trick you into flashing a non-compatible updated recovery version.
In my experience it doesn't play well with the Xoom.
If all you want is a non manual way to boot into recovery from the OS, download Quick Boot (if rooted) or if you're already on the Tiamat Moray Rom, it's something you can choose when you press the power button on the back.
the problem is that for me and others with this issue, you can't use adb to boot recovery. If you install recovery from fastboot then boot into the regular OS without booting to recovery and rooting, the OS replaces CWM with the stock recovery. This means if you use adb or another app to reboot into recovery, you just get stock recovery which is totally useless. I can't load recovery or root using anay of the universal methods I have come accross. We need a way to boot into recovery without having it replaced with stock or another rooting method or something. Any other ideas?
aussiechris said:
the problem is that for me and others with this issue, you can't use adb to boot recovery. If you install recovery from fastboot then boot into the regular OS without booting to recovery and rooting, the OS replaces CWM with the stock recovery. This means if you use adb or another app to reboot into recovery, you just get stock recovery which is totally useless. I can't load recovery or root using anay of the universal methods I have come accross. We need a way to boot into recovery without having it replaced with stock or another rooting method or something. Any other ideas?
Click to expand...
Click to collapse
Look, this is how I had to flash CWM image file- through adb,/fastboot just like you. No matter what you say, it comes down to a question of timing.
I'm not sure about everyone else with the no recovery option, but timing just isnt the issue for me. Without a lie i've tried to enter recovery over 50 times at various points, 95% of those attempts were at the 3 second mark that is stated in the xda guide we've been using. I'm aware of one other person here whos tried it MUCH more than me with exactly the same result.
However theres one thing that we could narrow it down with. Thus far the people having this issue are using the asian firmware xoom's. Could everyone else having this problem on this thread say whether or not theyre using the asian firmware too? Maybe the asian firmware can't be rooted this way?
ok i have a 32 gb hp tablet
ive went through and done the whole cyanogenmod thing and it was highly succesful
then i get to the part for installing the android market
for some reason no matter what i do or redo i cant get clockwork recovery period cant reboot into it nothing its not a option i went used a few things off here specifcially for clockwork failure and its just not working any suggestions?
ive looked every where and tried everything this is getting pretty frustrating tbh
im following the direstions specifically on here for rooting it and everything ive redone it twice now with the same resuslts please give me some ideas why i cant seem to get clockwork to work
you can flash clockworkmod through your pc by downloading it on your pc,booting your phone into bootloader mod and run the setup.Then you will have clockworkmod again
[email protected] said:
you can flash clockworkmod through your pc by downloading it on your pc,booting your phone into bootloader mod and run the setup.Then you will have clockworkmod again
Click to expand...
Click to collapse
is there a specific link or such i could go to maybe on here or what not to walk me through this lol
and this is a first time instal on my tablet and i just flat out havent gotten clockwork to work yet lol
I am relatively new at ROMs and I installed CyanogenMod 10 on my AT&T HTC One X (US) a couple of months ago. Recently, I tried upgrading to the M2 release of CM10.1 using the evita package which I understand is the US version of the ROM. I followed the same instructions I used to install 10.0 for 10.1. However, the installation froze and did nothing for a few minutes and gave me the message "no MD5 file found". I shut the phone down and restarted, but the phone would no longer start. I did a "system wipe" to get ride of the OS so I could re-install it, but now, my computer won't recognize my phone when I connect them and I can't move the CM10.1 zip file from my desktop to my phone. I have nothing already on the phone I can flash besides Team Win Recovery Project which is what I use for Recovery. I have no recovery files.
Did I just paperweight my phone, or is there a way to salvage this situation.
sliceroo said:
I am relatively new at ROMs and I installed CyanogenMod 10 on my AT&T HTC One X (US) a couple of months ago. Recently, I tried upgrading to the M2 release of CM10.1 using the evita package which I understand is the US version of the ROM. I followed the same instructions I used to install 10.0 for 10.1. However, the installation froze and did nothing for a few minutes and gave me the message "no MD5 file found". I shut the phone down and restarted, but the phone would no longer start. I did a "system wipe" to get ride of the OS so I could re-install it, but now, my computer won't recognize my phone when I connect them and I can't move the CM10.1 zip file from my desktop to my phone. I have nothing already on the phone I can flash besides Team Win Recovery Project which is what I use for Recovery. I have no recovery files.
Did I just paperweight my phone, or is there a way to salvage this situation.
Click to expand...
Click to collapse
Are you able to get into recovery?
joelrwise said:
Are you able to get into recovery?
Click to expand...
Click to collapse
Yes. I can get into recovery and the screen that tells you the root status of the phone.
sliceroo said:
Yes. I can get into recovery and the screen that tells you the root status of the phone.
Click to expand...
Click to collapse
If you can get into recovery then you aren't bricked just yet! If you have an sd card reader on your computer or know somebody who does thats one way you could get a new rom on your phone to flash. Most recoveries have a way to let you connect your phone to your computer for file transfer while in recovery. I believe in TWRP the option is in the Mount are. I could be wrong though. You just need to figure out how to get a new Rom on your phone. If none of the above work, one trick that has always worked for me, would be to put your sd card into someone elses phone, and download a known working rom onto your sd card via theyre phone, and just put it back into your phone. Hope i helped. Let me know how it goes man. I've been here before haha
joelrwise said:
If you can get into recovery then you aren't bricked just yet! If you have an sd card reader on your computer or know somebody who does thats one way you could get a new rom on your phone to flash. Most recoveries have a way to let you connect your phone to your computer for file transfer while in recovery. I believe in TWRP the option is in the Mount are. I could be wrong though. You just need to figure out how to get a new Rom on your phone. If none of the above work, one trick that has always worked for me, would be to put your sd card into someone elses phone, and download a known working rom onto your sd card via theyre phone, and just put it back into your phone. Hope i helped. Let me know how it goes man. I've been here before haha
Click to expand...
Click to collapse
I went into TWRP Mount and it allowed me to mount the phone. I went ahead and did that, but Windows told me that I had to format the disk. I agreed and Windows formatted it. Afterwards, I successfully copied over the CM10.1 Evita M2 zip file and the lates Gapps zip file. I then went to TWRP's install section and flashed both zips. TWRP told me both happened succesfully. However, while flashing over the CM10.1 file, it told me that no MD5 file was found and that it was just going to skip that. Then, it formatted some mke5 partition and then went ahead and finished. I wiped the Dalvik cache and the system Cache and restarted the phone. It is currently stuck at the "HTC Quietly Beautiful" intro screen and won't boot past that. Is there something I missed?
If that 10.1 already failed because of an MD5 problem, I wouldn't have tried to flash it again - the file probably has some problems in itself and either needs to be re-downloaded or just won't work.
Just flash the stock firmware or something - and use an MD5 checking program.
Pennycake said:
If that 10.1 already failed because of an MD5 problem, I wouldn't have tried to flash it again - the file probably has some problems in itself and either needs to be re-downloaded or just won't work.
Just flash the stock firmware or something - and use an MD5 checking program.
Click to expand...
Click to collapse
The thing is TWRP returned the status as successful despite missing the MD5 file. I'll try flashing over another package and if that doesn't work, I'll try flashing over CM10. If that still doesn't work, I'll just do stock firmware if I can find it somewhere, I guess.
In the future, making a backup is really awesome. Not saying that like "I told ya so" - but I've used them so many times myself, it's really great to say, "oops, I overlooked something" and then be able to just go back to a perfect snapshot of how things were before.
Also, how long did you let the phone sit at the boot screen ? It can hang for quite a while on the first boot.
Pennycake said:
In the future, making a backup is really awesome. Not saying that like "I told ya so" - but I've used them so many times myself, it's really great to say, "oops, I overlooked something" and then be able to just go back to a perfect snapshot of how things were before.
Also, how long did you let the phone sit at the boot screen ? It can hang for quite a while on the first boot.
Click to expand...
Click to collapse
Yeah I would just reflash a ROM that you've used before and that you know works. Chances are if the cm10.1 didn't work the first time its probably not going to the second time. And he has a point. First boot always takes forever. I've flashed a couple ROMs and thought I was bootlooped but I let it sit for a good 5-10 minutes and the setup screen finally came up.
joelrwise said:
Yeah I would just reflash a ROM that you've used before and that you know works. Chances are if the cm10.1 didn't work the first time its probably not going to the second time. And he has a point. First boot always takes forever. I've flashed a couple ROMs and thought I was bootlooped but I let it sit for a good 5-10 minutes and the setup screen finally came up.
Click to expand...
Click to collapse
I had no idea that it could take that long. I guess I'll just turn my phone on and see if it wants to start. I'll leave it going for a good five to ten minutes this time. Shutting the phone down while its still in the intro screen doesn't damage the OS, does it? Thanks for the advice so far guys, I really appreciate it.
UPDATE: See post #5 for the fix. It's really simple!
Hi,
First of all, I've been using this website as a resource for the last couple years. THANK YOU to all of you who dedicate your free time to helping the Android community!!!
K, now on to the issue:
This isn't my first rodeo. I'm not a dev, but I have a lot of experience with the Verizon S3. This is the second one I've owned, and I bought it off of craigslist. I'm starting to wonder if there's something wrong with the internal memory.
Stock recovery works perfectly, but both ClockworkMod and TWRP cannot mount anything -- cache, data, internal/external SD, etc.
My only computer is a MacBook Pro, and I have been using Odin 3.07 running inside a VMWare Fusion virtual machine running Windows 8.1. Luckily, Odin gets me back to stock every time, but I really need to get a custom recovery so I can get away from Touch Wiz.
I have tried 2 different versions of Casual as well as manually pushing everything through Odin.
jmsclbwmn said:
Hi,
First of all, I've been using this website as a resource for the last couple years. THANK YOU to all of you who dedicate your free time to helping the Android community!!!
K, now on to the issue:
This isn't my first rodeo. I'm not a dev, but I have a lot of experience with the Verizon S3. This is the second one I've owned, and I bought it off of craigslist. I'm starting to wonder if there's something wrong with the internal memory.
Stock recovery works perfectly, but both ClockworkMod and TWRP cannot mount anything -- cache, data, internal/external SD, etc.
My only computer is a MacBook Pro, and I have been using Odin 3.07 running inside a VMWare Fusion virtual machine running Windows 8.1. Luckily, Odin gets me back to stock every time, but I really need to get a custom recovery so I can get away from Touch Wiz.
I have tried 2 different versions of Casual as well as manually pushing everything through Odin.
Click to expand...
Click to collapse
It should work. Once latest version of casual is done try upgrading to latest version of whichever recovery you are gonna use. All the recoveries in casual are out of date and may just need to reflash recovery. Sounds like gonna use AOSP base so might as well stick with CWM as that is what you are going to end up with and what the AOSP devs support. While on TW can try upgrading it also as it the dev preferred recovery on TW. Shouldn't be the Mac if everything is actually unlocked, rooted and is flashing a recovery.
prdog1 said:
While on TW can try upgrading it also as it the dev preferred recovery on TW.
Click to expand...
Click to collapse
Can you please clarify this particular thought for me? I understood everything else.
jmsclbwmn said:
Hi,
First of all, I've been using this website as a resource for the last couple years. THANK YOU to all of you who dedicate your free time to helping the Android community!!!
K, now on to the issue:
This isn't my first rodeo. I'm not a dev, but I have a lot of experience with the Verizon S3. This is the second one I've owned, and I bought it off of craigslist. I'm starting to wonder if there's something wrong with the internal memory.
Stock recovery works perfectly, but both ClockworkMod and TWRP cannot mount anything -- cache, data, internal/external SD, etc.
My only computer is a MacBook Pro, and I have been using Odin 3.07 running inside a VMWare Fusion virtual machine running Windows 8.1. Luckily, Odin gets me back to stock every time, but I really need to get a custom recovery so I can get away from Touch Wiz.
I have tried 2 different versions of Casual as well as manually pushing everything through Odin.
Click to expand...
Click to collapse
You must have a newer GS3, the newer devices (made within the past few months) have a higher revision internal card reader that breaks some recoveries. (I know because I flashed a sprint gs3 that had the same exact issue).
The fix for this is to have a recovery built with the fix in it, which is upstream in the cm-10.2 kernel, but not in any official recoveries yet.
Let me see if I can find the exact commit for you... I know invisiblek fixed it
EDIT: heres the sprint thread of info (DO NOT FLASH THE FILES THO THEY WILL MESS UP THE VZW GS3)
http://forum.xda-developers.com/showthread.php?t=2391616&page=31
I found another thread on here with a guy having the exact same issue. That thread combined with the above information about outdated recovery images guided me to my solution. Here's how simple it was:
1) Use Casual to root/unlock.
2) Download Flashify
3) Download most recent ClockworkMod Recovery image
4) Use Flashify to flash said image
I really hope this info helps someone else!
jmsclbwmn said:
I found another thread on here with a guy having the exact same issue. That thread combined with the above information about outdated recovery images guided me to my solution. Here's how simple it was:
1) Use Casual to root/unlock.
2) Download Flashify
3) Download most recent ClockworkMod Recovery image
4) Use Flashify to flash said image
I really hope this info helps someone else!
Click to expand...
Click to collapse
Oh man! Thanks for posting how you got it to work. I've been trying to figure out what to do for almost 2 days.
I would of probably still be googling away if I hadn't found this. Thanks!
I was trying to find a custom recovery, or any recovery that will work on my lg realm. I boot recovery and it gives me a error message so im guessing its either wiped out or blocked...any ideas out there on how to correct or replace it
twtoned said:
I was trying to find a custom recovery, or any recovery that will work on my lg realm. I boot recovery and it gives me a error message so im guessing its either wiped out or blocked...any ideas out there on how to correct or replace it
Click to expand...
Click to collapse
Looking for one as well. I have not found one.
Recovery is actually preinstalled
I found this just tooling around. Use your favorite file browser, I used
Total commander. /system/vender/itson
The zip file is there. Hope this helps. (Rooted LG ls620)
Could you explain in a little better detail on what you mean Enigmatic177... I'm pulling my hair out Hehe
If anyone makes or finds a working recovery please post it.
Itson is a zip file that was installed after last update it has the basics to unlock the boot loader. I unpacked it used Rom toolbox pro rebooted to RECOVERY did regular reboot system upgraded.
A couple if bit mapp errors 11111. Then I basically flashed CWM.
Before you do this the partitions change from ext2-ext4. I'd advise
Backing them up.
LG Realm & exceed 2 TWRP recovery/fastboot files
No computer needed!!!
Lg realm & exceed 2 twrp custom recovery/fastboot downloade
All you need to do is follow the steps in the read me and you will have the recovery or fast boot to do as you please! Make sure u do a backup!!!!!!
I spent countless hours trying to do this and i finaly got it to work
Now all we need is them roms please make some if you can wold like cm12!
Sorry for not spacing the link im a newb so i cant post links yethttps://mega.co.nz/#!FVQ0GSaI!525LBPtwo696CvZrjY032tKkfS7aaURG-xATm2uzWhw
TWRP recovery help L620 LG Realm
hello I followed the steps in the read me file and i succeeded in installing twrp although im having troubles booting up to my system os. when i power on my device it takes me straight to twrp. i have a feeling i might of missed a step. i tried creating a backup but i cant because i noticed my screen turns off fast. do you think you might know what might be the problem why i cant boot up to my os? thanks!
I think i know what seems to be the problem. I think i might have accidentally replaced the boot img with the twrp recovery img. i did not make a backup before this happened. is there anything i can do to make my phone boot up to its normal image? thanks
Nope. It is officially a paperweight and no one I know of has access to the stock ROM either.
Sent from my LGLS620 using XDA Premium 4 mobile app
Hey
Has anybody found a custom rom?
Finally. Easy as pie
Ok, I downloaded an image (w5c_twrp_bumped.img)
put that img on the root of my sd card
downloaded Rashr from the google play store
opened rashr and tapped 'recovery from storage', navigated to external sd and tapped the image and tapped
ýes please'
flashed it. after the flash the phone rebooted into the twrp recovery.
then just rebooted back into the system
worked perfectly.
im new here im not allowed to post outside links yet, just google "w5c_twrp_bumped.img" should take you to a link for a download of that recovery
i got twrp now as a custom recovery. on my lg realm.
That_One_Person760 said:
hello I followed the steps in the read me file and i succeeded in installing twrp although im having troubles booting up to my system os. when i power on my device it takes me straight to twrp. i have a feeling i might of missed a step. i tried creating a backup but i cant because i noticed my screen turns off fast. do you think you might know what might be the problem why i cant boot up to my os? thanks!
Click to expand...
Click to collapse
You have the bumped recovery so all i can say if u messed up is to flash a stock rom u can find on google i had to re flash mine a few times messing with root
right on, thanks for the info. I had no problems at all. it all fell in place like i was hoping. The Realm is the easiest device Iv ever rooted, flashed, and messed with. Well, as far as rooting and flashing a custom recovery. dunno bout roms though. Im sure its simple?
The_android_Modder said:
No computer needed!!!
Lg realm & exceed 2 twrp custom recovery/fastboot downloade
All you need to do is follow the steps in the read me and you will have the recovery or fast boot to do as you please! Make sure u do a backup!!!!!!
I spent countless hours trying to do this and i finaly got it to work
Now all we need is them roms please make some if you can wold like cm12!
Sorry for not spacing the link im a newb so i cant post links yethttps://mega.co.nz/#!FVQ0GSaI!525LBPtwo696CvZrjY032tKkfS7aaURG-xATm2uzWhw
Click to expand...
Click to collapse
OK, I grabbed and extracted this. I used Flashify to simply flash the recovery (w5c_twrp_bumped.img) and it works like a dream on my LG Realm.
OTOH, trying the same on an Exceed 2 gets me TWRP, but it cannot mount much of anything and the backup fails. After failing, it tells me "No OS found, continue?" I continue and get the message "Appears your device has no Root, install now?' I am absolutely certain I have root, or wouldn't even be able to run Flashify, so I continue and it simply boots into the OS just fine. Perhaps the readme isn't complete, as I see the following file in the extracted folder (resources.zip) with no explanation of why it's there. It "appears" to be a flash-able zip that installs "itson" (whatever THAT is). Note that the Realm has this in the /system/vendor/itson, yet the Exceed 2 doesn't.
Have you actually used this on an Exceed 2? And if so, what am I missing here?
The_android_Modder said:
No computer needed!!!
Lg realm & exceed 2 twrp custom recovery/fastboot downloade
All you need to do is follow the steps in the read me and you will have the recovery or fast boot to do as you please! Make sure u do a backup!!!!!!
I spent countless hours trying to do this and i finaly got it to work
Now all we need is them roms please make some if you can wold like cm12!
Sorry for not spacing the link im a newb so i cant post links yethttps://mega.co.nz/#!FVQ0GSaI!525LBPtwo696CvZrjY032tKkfS7aaURG-xATm2uzWhw
Click to expand...
Click to collapse
Link is DEAD. Any chance you can reupload this file? I can't make heads or tails of some of this thread and I don't want to destroy this phone. Thanks!!!
petermg said:
Link is DEAD. Any chance you can reupload this file? I can't make heads or tails of some of this thread and I don't want to destroy this phone. Thanks!!!
Click to expand...
Click to collapse
I'll do you one better. Just forget about the post you replied to, as it's convoluted as hell. Install TWRP 2.8.6 from here. Ignore the big red warning about the Realm, as he evidently hasn't updated the OP. You can view my notes regarding the Realm in this reply. Tested several times and verified working better than anything else available. Easiest recovery to install I've ever dealt with (all done with an .apk). The option to access via cold boot (battery pull procedure) is something to behold
Be sure to thank the developer, even if you need to create an account to do so. Very VERY nice work!
fathergweedo said:
I'll do you one better. Just forget about the post you replied to, as it's convoluted as hell. Install TWRP 2.8.6 from here. Ignore the big red warning about the Realm, as he evidently hasn't updated the OP. You can view my notes regarding the Realm in this reply. Tested several times and verified working better than anything else available. Easiest recovery to install I've ever dealt with (all done with an .apk). The option to access via cold boot (battery pull procedure) is something to behold
Be sure to thank the developer, even if you need to create an account to do so. Very VERY nice work!
Click to expand...
Click to collapse
THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Before you replied I installed the version 2.8.5 from here:
http://androidforums.com/threads/twrp-2-8-5-0-for-realm-ls620-and-exceed-2-vs450pp.908704/
Is 2.8.6 better? Looks like the 2.8.5 can't be booted into via key combo from power off? Are there any other differences? I just used the Rashr flash tool from the market to flash 2.8.5. Worked flawlessly. This is actually my mom's phone and it wanted to do a system upgrade but I wanted to back it up first so that's the reason I wanted a recovery.
Pretty cool though, this recovery installs just via an APK!!!? That's amazing!
I'm tempted to install this on her phone next time she comes over... it should be fine right?
Thanks again!!!!!!!!!!
petermg said:
THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Before you replied I installed the version 2.8.5 from here:
http://androidforums.com/threads/twrp-2-8-5-0-for-realm-ls620-and-exceed-2-vs450pp.908704/
Is 2.8.6 better? Looks like the 2.8.5 can't be booted into via key combo from power off? Are there any other differences? I just used the Rashr flash tool from the market to flash 2.8.5. Worked flawlessly. This is actually my mom's phone and it wanted to do a system upgrade but I wanted to back it up first so that's the reason I wanted a recovery.
Pretty cool though, this recovery installs just via an APK!!!? That's amazing!
I'm tempted to install this on her phone next time she comes over... it should be fine right?
Thanks again!!!!!!!!!!
Click to expand...
Click to collapse
That one will cold boot with the battery pull procedure too. A little further down that thread you'll see I modded it to work correctly with the Exceed 2 in addition to the Realm. I like the 2.8.6 better if only that the dates of the backup are correct now. The 286.apk will work fine and overwrite your current recovery. If you leave it installed, you can always open it and reboot to recovery from within the app. If I have more time I'll post a screenshot, but running late for work. I think the screen dimming/timeout issue was fixed as well, but I haven't verified that. I normally disable that in TWRP anyway, as I like to monitor what it's doing during a backup/restore in case of errors.
fathergweedo said:
That one will cold boot with the battery pull procedure too. A little further down that thread you'll see I modded it to work correctly with the Exceed 2 in addition to the Realm. I like the 2.8.6 better if only that the dates of the backup are correct now. The 286.apk will work fine and overwrite your current recovery. If you leave it installed, you can always open it and reboot to recovery from within the app. If I have more time I'll post a screenshot, but running late for work. I think the screen dimming/timeout issue was fixed as well, but I haven't verified that. I normally disable that in TWRP anyway, as I like to monitor what it's doing during a backup/restore in case of errors.
Click to expand...
Click to collapse
THANKS!!!! I'll make it a point to flash that to my mom's phone next time I get the chance!