Database Info

Q about cwm 3.0+ and 2.3.2

Out of sheer curiosity and wonder, I noticed after the OTA was installed, su was not working, duh, I knew that would happen, so I re rooted the device, I made a back up of the rom every single time it was updated, so I noticed when clicking "reboot into recovery" option in rom manager (keep in mind I am on 2.3.2) it boots me into stock android <3e> recovery and not CWM 3.0.x.x. Which is weird because after that I do a battery pull to jump into the bootloader to access recovery there, nope, still takes me to the damn stock recovery, so back to the bootloader and fastboot my way back. After that, I noticed once back booted in android I go into RM and "flash recovery" (3.0.x.x) and voila! I get back into CWM, but I have to flash it every single time.
Has anyone noticed this?
Feel free to hit me up on twitter since I try to stay outta forums, thank you.
I <3 Trolls.

b16a2smith said:
Out of sheer curiosity and wonder, I noticed after the OTA was installed, su was not working, duh, I knew that would happen, so I re rooted the device, I made a back up of the rom every single time it was updated, so I noticed when clicking "reboot into recovery" option in rom manager (keep in mind I am on 2.3.2) it boots me into stock android <3e> recovery and not CWM 3.0.x.x. Which is weird because after that I do a battery pull to jump into the bootloader to access recovery there, nope, still takes me to the damn stock recovery, so back to the bootloader and fastboot my way back. After that, I noticed once back booted in android I go into RM and "flash recovery" (3.0.x.x) and voila! I get back into CWM, but I have to flash it every single time.
Has anyone noticed this?
Feel free to hit me up on twitter since I try to stay outta forums, thank you.
I <3 Trolls.
Click to expand...
Click to collapse
Wow, I'm sorry to be cranky, but this is unreal.
Your question has been asked and answered a hundred times in this forum if you'd bothered to search, and you're not even willing to a monitor the forum for an answer, you want us to come search you out on Twitter?!?!?
Here's a hint to find the answer to your question, use the forum search button and search for the phrase /etc/install-recovery.sh.
You'll find dozens of posts telling you to rename that file, which Google added with the updates to overwrite any custom recoveries with the stock one on each boot of the phone... Rename the file and you won't have to flash cwm every time any more.

Okay, that last post was a bit more harsh than I meant it to be, perhaps, but I'm leaving it intact. Since you "try to stay outta forums" you probably don't know proper etiquette:
1) search before asking; your issue has most likely been asked before. It's annoying to forum regulars when people show up and ask the same thing over and over that's already been answered.
2) read the FAQ thread before asking; your issue has most likely been addressed in it. It's annoying to forum regulars when people show up and ask the same thing over and over that's already been answered in the FAQ.
3) if you're going to come to the forums and ask a question, then come back periodically and see if it's been answered. We're doing you a favor answering your question, at least show some effort by coming back and reading it instead of asking someone else to come find you in another forum and spoon feed it to you. If you're really just too important or time-challenged to do that, then subscribe to the thread you created and get an email notice when posts are made to it.[/I]

You'll need to rename install-recovery.sh to install-recovery.sh.old.
Its located in the /etc system folder. You can use root explorer or any another alternative. Refer to the rooting guides available as they include a more thorough explanation of how to do this. And please, no twitter.
Sent from my Nexus S using XDA App

it's actually enough just to fastboot push the renamed recovery.img
then it will stick without having to rename the install-recovery.sh

Hey huge thanks to @AllGamer.
The other guy, no idea what crawled up your ass and died, but didn't know that one simple question could hurt so badly. Have a nice day.
P.S. I am sure most of the people here know this, the search engine sucks on this site so yes I did use it and its garbage. I was just concerned about it so I could start my builds without any worry. Happy trolling.
Moderator delete this thread,
Thanks.

AllGamer said:
it's actually enough just to fastboot push the renamed recovery.img
then it will stick without having to rename the install-recovery.sh
Click to expand...
Click to collapse
I don't recall that working for me. I'm not even sure why that would work. Every boot up that script is ran unless you delete or rename it, isn't it? I guess I'll have to play with it when I get a chance.
EDIT: Do you mean renaming clockwork-3.0.0.5-crespo.img to just recovery.img when pushing it via fastboot? Never tried that here.
b16a2smith said:
Hey huge thanks to @AllGamer.
The other guy, no idea what crawled up your ass and died, but didn't know that one simple question could hurt so badly. Have a nice day.
Click to expand...
Click to collapse
I think it was the bit about I try to stay out of forums, so come find me on twitter coupled with the <3 trolls.
I was cranky this morning and I apologize, but it was all true, and don't forget that I did tell you how to find the answer (which search term to use) and even how to fix it (rename the file), so I think thanks are in order....You're welcome for that, and have a nice day as well..
Peace

distortedloop said:
EDIT: Do you mean renaming clockwork-3.0.0.5-crespo.img to just recovery.img when pushing it via fastboot? Never tried that here.
Click to expand...
Click to collapse
yes, it is in my guide
yet people always misses to read it
most people reading it either assumes things, or doesn't follow it properly
that's how i do it every time and it works without fail

AllGamer said:
yes, it is in my guide
yet people always misses to read it
most people reading it either assumes things, or doesn't follow it properly
that's how i do it every time and it works without fail
Click to expand...
Click to collapse
Just to be clear, we're talking about having clockwork NOT overwritten by the stock each bootup. I'm a little confused because you say "that's how i do it every time..." If it sticks, why do you need to do it more than once?
Assuming you mean clockwork sticking without renaming the install-recovery.sh file, please read on. If that's not what you meant, skip the rest below...
I don't think people necessarily miss it, they assume things like you say
I didn't follow your guide to root mine (it wasn't out yet, and isn't Mac), but obviously I've read it. I did notice that you rename it, but assumed it's not necessary, since Koush's instructions don't have you do that and you get a successful flash without renaming.
Anyways, I just tested this out on my NS.
I was on stock recovery, and I have not renamed my /etc/install-recovery.sh file.
I booted the phone to fastboot mode, renamed my clockwork recovery to recovery.img.
I then "fastboot flash recovery recovery.img" and after a successful flash message, selected recovery from the fastboot menu.
The phone booted to clockwork recovery, which confirms a successful installation of it.
I then rebooted the phone, and after it was fully booted, rebooted it to fastboot mode. When I selected recovery, I then get the box with an arrow pointing into the android, so I hit the proper keys and I ended up in stock recovery (blue text).
The install-recovery.sh script still reflashed the stock recovery even though I flashed it per your instructions.
If I rename that script and then install clockwork, any attempt to boot recovery goes straight to clockwork recovery (orange text, extra features, etc).
Did I do something different than you're suggesting? Based on my test, I don't think you have any option other than to rename that script (or delete the backup image it uses to flash stock) if you want to remain on Clockwork.
Thoughts?

you should still have the CW recovery, if you pushed it into the phone as recovery.img
after i reboot the phone, i can go back into CW just by selecting Recovery
i just use those reboot software, or manually hold volume up + power
then i get into the fastboot mode
in fastboot mode i select Recovery
and that takes me back to CW recovery
i did not rename the install-recovery.sh, just in case i ever want to restore the phone back to stock
i do know that if i do not rename the recovery-clockwork-3.0.0.5-crespo.img to recovery.img, then i will lose CW right after the reboot

AllGamer said:
you should still have the CW recovery, if you pushed it into the phone as recovery.img
after i reboot the phone, i can go back into CW just by selecting Recovery
i just use those reboot software, or manually hold volume up + power
then i get into the fastboot mode
in fastboot mode i select Recovery
and that takes me back to CW recovery
i did not rename the install-recovery.sh, just in case i ever want to restore the phone back to stock
i do know that if i do not rename the recovery-clockwork-3.0.0.5-crespo.img to recovery.img, then i will lose CW right after the reboot
Click to expand...
Click to collapse
Well, that's a weird one. You didn't say I tested it wrong, but I am getting different results than you.
If I were ambitious I would make a youtube video of it to show my results, not as a challenge, just to see if I'm doing something wrong.
Are you stock ROM? If not, maybe that's a difference that would explain it.

i'm on Bionix 1.3 beta
perhaps that's the difference?

AllGamer said:
i'm on Bionix 1.3 beta
perhaps that's the difference?
Click to expand...
Click to collapse
Almost certainly the difference.
I'll wager that if you go to the /system/etc folder that Bionix has removed that script for you. That would explain why it's not running and restoring the stock.
Check that out and let me know; we may have solved the mystery here.
FYI, I just downloaded the bionix 1.3 files and checked inside, no install-recovery.sh in it...

HELP!! No Android Recovery option

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?

The officially unofficial Tiamat Moray ROM Q&A Thread

This thread is an attempt to help out the Tiamat Developers by answering the frequently asked questions in one consolidated thread. This thread should also be helpful to those who either cannot use the search feature or are having a hard time figuring out the correct search terms to find what they are looking for. If you have suggestions or added questions/answers feel free to reply and I will update the OP.
NOTE: I am not a developer. All of the information in this thread is from other members who have helped me out or information I found in the XDA forums. I do not take credit for any of the great work that has been done on this ROM and I will point back to the original answer when possible. I am only trying to help lessen the burden on the developers so they can spend more time getting us the best features. Hopefully you find this helpful as well.
I've flashed this ROM and now I get update notifications. Should I accept the update? How do I stop these notifications?
No, you should never accept an OTA upgrade when using any custom ROM/Kernel. This could result in severe problems. Your best bet is to be patient and give the developers time to react. If the update is worthwhile I am sure they will roll it out pretty quickly.
To get rid of the notifications flash Mod pack 3 as noted here.
OK I made the mistake of accepting the OTA update and now my Xoom won't boot. What can I do?
okantomi said:
Can you make it reboot by pressing volume up and power at the same time and holding? If it reboots, wait about 3 seconds once you see the dual core logo and then tap volume down you shoud see android recovery, then tap up to choose it. I hope you did a nandroid backup. If not, you can try and get fastboot by tapping volume down sooner after it reboots.
Click to expand...
Click to collapse
From this thread.
With this ROM certain websites don't load correctly or I can't get to the mobile version of a site.
This ROM by default sets the User Agent String to "desktop". If you want to revert to the stock settings flash either Mod pack 1 or 2 depending which version of Moray you are running. Look here.
I flashed this ROM and now when I click links in email or my file explorer the screen just dims and nothing happens.
This is a bug in Android 3.2 and not specific to this ROM. To solve this, simply ensure auto-rotate is enabled and rotate the device from landscape to portrait and back to landscape. The app chooser window should appear allowing you to choose which app to open the selected file.
I just flashed this ROM and the speed is amazing, so I OC'd it to 1.7GHz cuz I want more and I am now stuck in a boot loop. This worked for others why not me?
The Xoom was only specified to run at 1.0 GHz, anything beyond that is a gift. Due to part-to-part variation not everyone's Xoom will be stable at the same speed. Yes some people are able to run at 1.7 GHz, but many cannot. For your specific Xoom try out the various speeds, but do NOT click "Set on Boot". This way if it crashes it will revert back to stock speed and you will be able to boot. Once you are satisfied with a speed then feel free to enable "Set on Boot". Before you do so I would suggest making a nandroid backup so you can restore just in case.
How do you get out of this boot-loop? The only way I know of is to boot into recovery and restore a nandroid backup if you have one or perform a full wipe if you do not.
I updated to the latest CWM and I cannot find the zip card or I get "get error: E:failed to mount /sdcard (No such file or directory)."
Latest is not always the best, for the Xoom you need to either use ClockworkMod 3.2.0.0 (R4C) or CMW Rogue Recovery v1.1.1
After flashing this ROM the Motorola icon gets distorted during boot up, is that a problem?
Basically it is not a problem. This kernel has a patch provided by NVidia which causes the distortion during boot. It does not cause any problems after it boots.
Is there a way to get the stock WiFi and Battery icons?
Yes
How do I boot into recovery without ADB or my PC attached?
There are a couple methods.
1) The latest Tiamat ROM includes this if you press and hold the power button. Just pick what you want and hit OK.
2) Download and install "Quick Boot" from the market. It gives you the above options as well as others when you run the app.
3) Turn the Xoom on, wait ~2 seconds after your see the Dual Core logo, then press the volume down key. In the upper left corner it should say "Android Recovery", then press the volume up key to select it.
How do I get started? Any good guides?
There are several guides that are pretty good. The best one I have found and personally used is here.
The Xoom Heaven thread found here is also a good place to start for all sorts of information.
If you have another question please feel free to post to this thread. If you are having a problem or have a question it is likely that someone else along the lines will have the same problem or question. I will continue to update this OP with the list of F.A.Q.s.

Additional Q&As
After installing this ROM I am having issues with the market not finding all of my apps or apps are giving errors when trying to install them.
See this post for one possible solution.

One more for good measure...

HuckFinn, I think you have covered most of the hot issues. Great job!

Stickied. Thanks for posting this, and Solarnz for giving me the heads up to do so.

Sorry for the newb question, but what's "root"?

Psychokitty said:
Sorry for the newb question, but what's "root"?
Click to expand...
Click to collapse
oh kitty, you funny!

Psychokitty said:
Sorry for the newb question, but what's "root"?
Click to expand...
Click to collapse
It's what you pull your hair out by when something is not working properly!!

darn you... I earned 1/2 my posts responding to the "why does my screen dim" question... now I'll have nothing to say!

i performed a factory reset from the os-> settings and once again performed a wipe/factory reset from the cwm recovery but still can't get back to the initial setup screen (where you enter your google a/c, etc)
any idea?
Thanks!!

Here is one..
Why does Market show up in USD even though my locale is set to UK, my language is English British along with my keyboard layout?

Ive had boot loops twice. Both times i could get into recovery but could not get backup to restore . kept getting cant read /sdcard. also cant reinstall update .zip becuase the sd card wont mount. I have only gotten back in by letting it sit powered off for a bit.
any ideas?
should i adb a stock image and start again?
should i flash a different recovery?

madamimadam said:
Ive had boot loops twice. Both times i could get into recovery but could not get backup to restore . kept getting cant read /sdcard. also cant reinstall update .zip becuase the sd card wont mount. I have only gotten back in by letting it sit powered off for a bit.
any ideas?
should i adb a stock image and start again?
should i flash a different recovery?
Click to expand...
Click to collapse
What version of recovery is installed now? If you have the version that doesn't recognize your external sdcard you should certainly flash a compatible recovery version through fastboot.

okantomi said:
What version of recovery is installed now? If you have the version that doesn't recognize your external sdcard you should certainly flash a compatible recovery version through fastboot.
Click to expand...
Click to collapse
Is there a way to check version without booting into recovery? Which version would you suggest?
And thank you

madamimadam said:
Is there a way to check version without booting into recovery? Which version would you suggest?
And thank you
Click to expand...
Click to collapse
There are only two recoveries compatible..
you will find them in the Xoom Android Developmet Board in the sticky threads

LPHS said:
There are only two recoveries compatible..
you will find them in the Xoom Android Developmet Board in the sticky threads
Click to expand...
Click to collapse
OR here:http://forum.xda-developers.com/showthread.php?t=1209341

Links to both of these recoveries are also in the first post of this thread.

HuckFinn said:
Links to both of these recoveries are also in the first post of this thread.
Click to expand...
Click to collapse
Guess I should have read the thread before posting here, sorry for being a troll.

I tried this ROM on my 4G Xoom, but it left me without 4G or 3G (wifi only). Any way to get this working, or do I have to wait for an update?
I did try activating the network in settings, but it never connected even half an hour.

Thanks to steps mentioned by user 'LordDeath' in another thread and a bit of experimenting with a rooted 4G Xoom and a friends 3G Xoom running Moray, there seems to be a remedy for those who are having issues with the market compatibility issues as well as missing apps. I did not activate until attempting to sign in to the market and had missing apps and compatibility issues. I simply did a full wipe & reset and made sure the full activation went through in set up then let it automatically start restoring. I took a peek in the market after a a minute and all my apps were back with no compatibility issues. Here is a copy of his original post and mine but the last step was not needed for me.
Originally Posted by LordDeath
Something more about the market:
After I restored my backup of the official 3.1 ROM I still had some issues. On http://market.android.com I still saw that my Xoom is not compatible with some apps. The market app on the device did show these apps but upon installing I got the error message: "Fehler beim Verarbeiten des Kaufs". Translated into English it means "Error while processing the purchase". It was a free app, btw.
To solve this issue I did the following:
1. Wipe data/factory reset
2. Active the device during the wizard on the first boot with my Google account
3. Restore the nandroid backup of the official 3.1 ROM
Therefore it seems that the market servers check your device-compatibility only during the activation process at the first startup.
----------------------------------------------------------------------------
"This fixed everything for my friend running Moray and even corrected the issues on my 4G Xoom..."
I should add that though this fixes the issue, if you change your pixel density you may run into similar issues but can correct it by setting it back to 160 before going into the market.

[Q] Help with ClockworkMod 5.5.0.4

Can someone help please? I installed CWM Recovery thru ROM Manager. Rebooted in recovery to back up my ROM and now I can't get out of recovery. Every time I select Reboot System it reboots me into recovery.

Try here (if you can use NVFlash)
http://forum.xda-developers.com/showthread.php?t=1519635&highlight=boot+into+cwm

Like many others, When I saw the thread over in the Dev section about the 5.5.0.4 recovery, I jumped right in and fired up Rom Manager before reading any further in the thread.
Unlike many others, I don't get the same results. My TF101 reboots to the OS with no problem. However trying to reboot to recovery from recovery doesn't work. I have to hold the vol. down button just like a cold boot into recovery.
The only difference might be, that I had stock recovery prior to installing 5.5.0.4, due to having to recover from another soft brick condition after trying to install the CM9 Nightly that is now available over on the official Clockworkmod site. That one had failed miserably for my device.
Good luck with solving your problems with the new recovery. Wish I could explain exactly why mine seemed to work as advertised when most others didn't. But I don't know.
I do have the problem with the Removable MicroSD not being visible. Only the built in "Fake" SD Card.
Update:
I now have the reboot into recovery problem. I used the wipe data option from the VOL DWN/PWR button start up, and now have that annoying boots into recovery problem like everyone else. I hope that and the SD card problem gets fixed in the next version.

Thanks, got everything back to normal with NVFlash method I found by watching this :http://www.youtube.com/watch?feature=player_embedded&v=VMHXeYMgPy4
Lesson learned!! :/

Curious where the thread in the Dev section went to, I cant find it this morning...
Unfortunately, some of us cannot use NVFLash to fix this problem.
So, is it too much to ask that the Dev who wrote Rom Manager and CWM actually look in to this for us?
I too installed the newer CWM through Rom Manager and need to cold boot to get in to the OS otherwise it recovery boot loops.

sandiegopaneraiguy said:
Curious where the thread in the Dev section went to, I cant find it this morning...
Unfortunately, some of us cannot use NVFLash to fix this problem.
So, is it too much to ask that the Dev who wrote Rom Manager and CWM actually look in to this for us?
I too installed the newer CWM through Rom Manager and need to cold boot to get in to the OS otherwise it recovery boot loops.
Click to expand...
Click to collapse
Thread was closed. I was on it this morning and wanted to post a reply saying NV Flash work for me and I couldn't because it said the thread was closed.
I read the whole thing and apart from NV Flashing the was no other solution
How do you know you can't NVFlash?

yea , this morning the thread in the Dev section went to general , and now closed.
Perhaps we should follow this until everything is clarified.
the nvflash only work for b60 and some b70 tablets , most of b70 and b80 cant be flashed with this tool

I'm working on something to fix this, but I still need a little more testing.

gee one said:
I'm working on something to fix this, but I still need a little more testing.
Click to expand...
Click to collapse
ok, then waiting
any clue where to attack the problem?

Some people reported the new recovery worked when flashed over stock recovery.

any help you can supply on this would be greatly appreciated. it's very uncomfortable not being able to count on your recovery.
Sent from my Inspire 4G using XDA App

robb13 said:
Some people reported the new recovery worked when flashed over stock recovery.
Click to expand...
Click to collapse
too late for us

I was up until 1am following the thread and posting my process, specs.
I am even more curious as to how the thread which was still pretty calm turned in to something that deserved being deleted.
In any event, I think we all understand that what we do is at our own risk. But CWM and Rom Manager have been the gold standard of reliability for quite some time. Once something is a trusted means by which to do something its even more disappointing to see that it no longer works.

the first post was moved because it was not exactly a development post
then, in the general section, I do not know why it closed, there is no explanation

so if microsd is not recognized, i can install rom from internal, right?

gandda12 said:
so if microsd is not recognized, i can install rom from internal, right?
Click to expand...
Click to collapse
Install what??
Sent from my Transformer TF101 using XDA Premium HD app

yeah, check out the troubleshooting thread here
http://forum.xda-developers.com/showthread.php?t=1530337

[Q] Lg Ls620 (realm) custom recovery

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!