Database Info

[RECOVERY]CWM-Based Recovery 5.0.2.8 For P999(Internal & External SD)

The image was provided by Mr Rusty over on the P990 thread and i asked him if we can have an update..well he gladly helped out so don't forget to thank Mr Rusty over on his Thread..
I repacked and added a script that you will just run in order to flash this CWM version..(Thanks to Russ for the script)
From his Thread:
By request a quick explanation of the difference between the two recoveries:
Usually, your recovery image will look on the external SD card for ROMs to flash, and backups to restore, and the external version here is no different. For the most part that is fine and dandy (unless you don't have an SD card I guess), however the stock O2X mounts it's internal SD card as /sdcard, which confuses ROM Manager a fair bit.
The internal version of the recovery mounts the internal storage as /sdcard as well, so ROM Manager can find backups it's made etc.
NOTE: Backups made with v5 are not compatible with earlier versions.
Click to expand...
Click to collapse
BIG Credits goes to Koush as well for his great work for innovating the CWM..
Get it Here: CWM 5.0.2.8 For P999 or from Here
Instructions on HOW to use/WHAT to do:(For Windows)
- Once you have downloaded the Package from the link Above..extract it to a Folder..
- Inside the folder all you have to do is look for the flash-recovery_xp.bat file..
- now turn your G2x OFF..
- remove the BATTERY and make sure your G2x is not connected to the PC via USB
- Press the VOLUME DOWN button together with the VOLUME UP..
- now CONNECT the USB Cable..
- If by all means Windows prompts for a new DEVICE you have to install the APX drivers from here(extract the package and manually install from this source)..
- Else if windows does not prompt OR you are already done installing the APX drivers you can now proceed on Running the flash-recovery_xp.bat by double clicking it..
- Choose 1 and Then press Enter..Wait for a few seconds till it prompts you that the FLASH was successful..IMHO you ought to wait another 5 more seconds after the prompt for not to have issues..
- After that Reboot into CWM by Pressing Power Button together with VOLUME DOWN til you see the LG Logo with waves..upon seeing that now release the buttons and wait for the CWM menu..
For Linux/Ubuntu Users:
- Download the Package
- Extract the folder somewhere
- Now turn your Phone OFF and DO NOT plug the USB cable yet..
- Now while Phone is OFF press VOLUME UP and DOWN together and now PLUG the USB cable in..keep them held together throughout the process..
- Run the Terminal and locate the Directory on where the Files are located..
- Type the ff:
Code:
chmod +x flash-recovery.sh
./flash-recovery.sh
- Once DONE you can now reboot..
FAQ:
Q: I am getting NVflash errors?
A: You might be on a BAD Cable or either way upon installing the drivers do a reboot..also DO THIS ON WINDOWS XP..on Windows 7 there are circumstances that the device is not recognized properly..also make SURE your unit is a P999 or P999DW(my unit is P999DW and touch WORKS!!) and not P990 or SU660..
Q: My device is not Recognized?
A: You have to download the APX drivers from one of the instructions above
Changelog: Github Source
Thanks and also vote for the page..

Seems the Chinese are on to this files too..lolz..

Thank you!! It flashed perfectly, no issues here.
Troy.

thegreenfamily04 said:
Thank you!! It flashed perfectly, no issues here.
Troy.
Click to expand...
Click to collapse
Glad it worked??

So internal and external mounting are all fine with this one?
Sent from my LG-P999 using xda premium

Wow thanks man. I may have to ask a out posting the CWM touch to the G2x.
Sent from my LG-P999 using xda premium

Just flashed it with no problems , when are we getting the touch CWM? Now that will look sexy

thy for your work. coming from ClockworkMod 5.0.2.0 what are the differences / improvements? could someone explain please?
thanks in advance

Just an update: I flashed a MIUI rom (Look in my sig) used the "Nullifier 2.0" (Double wipe) and flashed the current Trinity Kernel all with no issues
Phone is running GREAT now! Thank you once again
Troy.

Волк said:
Wow thanks man. I may have to ask a out posting the CWM touch to the G2x.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I was thinking the exact same thing. Seems strange to me that Koush made it for the O2x and not for us.

Im getting a nvflash error when trying to install the new clockwork.
It says check apx driver and usb cable. The drivers are already installed so Im thinking its the usb cable, but not sure.

MWBehr said:
I was thinking the exact same thing. Seems strange to me that Koush made it for the O2x and not for us.
Click to expand...
Click to collapse
the recovery's on a different partition, might make it a pain in the ass to access the touch drivers...
or he might just like the o2x more (everyone likes those Europeans more than us anymore)

Touch Recovery
I'm just gonna throw this out there, just because I wanted to try, I flashed the O2x Touch Recovery to my G2x. Everything as far as the application goes worked, touch to select, ect. The only problem is when you ask it to do something, the mounts are wrong, naturally. What I'm getting at is that both devices use cwm 5020, obviously, mounts changed. How hard would it be to decompile both versions of 5020 and apply the differences to the new touch recovery app?
p.s. for those who wonder how I flashed touch to my G2x, I just swapped out the recovery images in the one-click nvflasher, pretty simple. when you're done, put back correct file, nvflash again.

mustangtim49 said:
I'm just gonna throw this out there, just because I wanted to try, I flashed the O2x Touch Recovery to my G2x. Everything as far as the application goes worked, touch to select, ect. The only problem is when you ask it to do something, the mounts are wrong, naturally. What I'm getting at is that both devices use cwm 5020, obviously, mounts changed. How hard would it be to decompile both versions of 5020 and apply the differences to the new touch recovery app?
p.s. for those who wonder how I flashed touch to my G2x, I just swapped out the recovery images in the one-click nvflasher, pretty simple. when you're done, put back correct file, nvflash again.
Click to expand...
Click to collapse
It's all in the ram disk. Just swap out the vold.fstab in the ram disk. Recovery images are simply boot.imgs.

Interesting, because the differences are only 1 partition. And using the O2x CWM to wipe /system (iirc) would just wipe our internal SD. Ours is partition 7 theirs is partition 8, our partition 8 is the internal SD. Since the phones are 99% the same, it should be that simple. and I need to get up early... I do have one untested tool for decompiling a boot.img....
@Kairi: Can you mirror this on Dropbox? Or somewhere not blocked by my work? Wifi at home is down and I am just chewing away at my data with having to tether.

Волк said:
Interesting, because the differences are only 1 partition. And using the O2x CWM to wipe /system (iirc) would just wipe our internal SD. Ours is partition 7 theirs is partition 8, our partition 8 is the internal SD. Since the phones are 99% the same, it should be that simple. and I need to get up early... I do have one untested tool for decompiling a boot.img....
@Kairi: Can you mirror this on Dropbox? Or somewhere not blocked by my work? Wifi at home is down and I am just chewing away at my data with having to tether.
Click to expand...
Click to collapse
http://db.tt/rEpbpRfA here you go. Really interested on what you can do with it
Sent from my LG-P999 using Tapatalk

Волк said:
Interesting, because the differences are only 1 partition. And using the O2x CWM to wipe /system (iirc) would just wipe our internal SD. Ours is partition 7 theirs is partition 8, our partition 8 is the internal SD. Since the phones are 99% the same, it should be that simple. and I need to get up early... I do have one untested tool for decompiling a boot.img....
@Kairi: Can you mirror this on Dropbox? Or somewhere not blocked by my work? Wifi at home is down and I am just chewing away at my data with having to tether.
Click to expand...
Click to collapse
that might work. Id try it out myself if i didn't f up my Linux install...
Nvidia graphics got the best of me there too
Sent from my LG-P999 using Tapatalk

Works as advertised! Thanks!

works great! thanks!

So, my idea worked? I'm not at home and since I'm a collision tech by trade, my boss don't like me playing with my phone. Volk, if you read this pm me and fill me in if you can. Thanks brother.
[email protected]

How to replace one file when failing to boot

Hey guys
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas

bluenote73 said:
Hey guys
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas
Click to expand...
Click to collapse
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM. (you can try dirty flashing but i dont think itll work)
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
EDIT: re read your post, if your feeling adventurous and want to give it a shot, boot into CWM and connect it via usb. you can now get into an ADB shell on your phone by typing 'adb shell' if you have adb all setup and working. (im working from memory here so dont quote me on any of this)
now, you should be able to access your /system folder from that shell. be very careful though, i dont have much experience right here, and if i remember correctly you might not be in the full root directory yet)
if you can get into it try replacing your vold.fstab with a stock one,
if you dont have a stock one lying around, make a nandroid of the current state of the rom, then flash another rom, pull the vold.fstab, then re-restore back to the broken one and restore it (id upload mine but my phone is OOC right now )
after that just reboot and hope it resolves itself, if not then just follow my advice above
and keep that guide i linked to handy, messing around in CWM has the ability to brick your phone, if it does, then just follow that guide.

Klathmon said:
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM.
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
Click to expand...
Click to collapse
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA

N00BY0815 said:
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA
Click to expand...
Click to collapse
re read your post and updated my last post right after you posted
after dealing with noobies all day, i forget sometimes people want to try big things

Thanks guys. The info I was missing was there's no special trick to attaching adb while in CWM! Just plug in!
My phone is back up and running and partitions are fine as far as I can see after just booting up.

Hi there! I messed up with the vold.fstab filfe on my tablet – I replaced it with a downloaded file with the intention to transfer apps to my external SD card.
Now my tablet is only showing the startup logo and won’t continue loading. I can access recovery mode. Now I want to restore the original vold.fstab file.
My questions:
1. Using the Android SDK, the file explorer does not show any files, though my tablet is recognized.
2. Using adb push, it yields an error: permission denied, how to successfully push the original vold.fstab and replace the existing vold.fstab?
3. If I dump an image of my tablet and edit the dumped image, would this be easier compared to the steps above?
Thanks!

http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.

TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.

BryanF said:
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.
Click to expand...
Click to collapse
You need to do an adb remount before you can push. Was it rooted before?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!

Mansa_noob, yes, my tablet is rooted. I followed some instructions about adb but had an error saying access denied, and also no files are displayed at file explorer. See my posts above. I also mounted it successfully. I will post some sreenshots later.
Please if you have some instructions, I am willing to try.
---------- Post added at 07:06 AM ---------- Previous post was at 07:02 AM ----------
TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Hi twitchyEye, it did not work. It attemps to install (using the install update from ext sd card) but then says installation aborted.
Any more suggestions? Thanks

What recovery are you using? I suck with adb so I got nothing on that front.

It was the stock recovery from my Tablet. I don't have it on hand right now, I will post later. The chipset is RK3066. My problem is my tablet has no official support on the internet (maybe becaue it's still new). Model is Skyworth S71(3G).

I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!

TwitchyEye said:
I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!
Click to expand...
Click to collapse
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!

mansa_noob said:
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
Yes, I did adb remount and still access denied

BryanF said:
Yes, I did adb remount and still access denied
Click to expand...
Click to collapse
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!

mansa_noob said:
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.

BryanF said:
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.
Click to expand...
Click to collapse
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!

mansa_noob said:
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I want to try, but the stock recovery is my last hold as I have no stock ROM. If I overwrite the stock ROM, I cannot reinstall it as I don't have a copy of it.

So why not flash cwm with nvflash and then make a backup of your current stock rom? I did exactly that.
Sent from my LG-P999 using xda premium

Backup raw sector-by-sector image of a partition

I have a non-rooted Galaxy Tab 2 7.0 P3113 that was factory reset, so I'm trying to dump the data partition sector-by-sector to microSD to try to recover data.
Since there is no way to mount the internal memory as a hard drive through USB, it makes the most sense to use an aftermarket recovery which can read the sectors and write them to an image file on the microSD.
But I don't know if CWM or TWRP can do this. Obviously they can back up to microSD, but I've never heard of someone having issues with the 4gb file size limit of FAT32. That means the backups are always smaller than the full size of the internal memory!! Somehow they have a way of distinguishing used space from empty space, but the empty space is exactly what I need to copy in order to recover files.
Which brings me to the next issue-- the size of the partition images. TWRP apparently supports exFAT so that shouldn't be a problem. CWM seems to require some hacks. So does anybody know how to force TWRP to backup ALL sectors of a partition to microSD?
Edit: The DD command would also work but I don't know if it's enabled when you ADB in to a Galaxy in TWRP. I can't just try it because I lost the USB cable.

You can use Android Terminal Emulator on the phone and use the dd command providing you have Busybox installed.
Posted from my Fascinate using XDA Premium

MultipleMonomials said:
You can use Android Terminal Emulator on the phone and use the dd command providing you have Busybox installed.
Posted from my Fascinate using XDA Premium
Click to expand...
Click to collapse
The problem is that requires rooting and downloading/installing a big app, which will overwrite a bunch of data... Right? Unless you can keep the files confined to the system partition I guess.

Just found out that TWRP can split up the backup so it can even use a FAT32 microSD. Pretty cool.
I just wish I could find out if it backs up the "empty" sectors. I emailed Team Win and they didn't reply.

I imagine that you could write a CWM zip that would copy the terminal emulator apk to the /system partition, but if I were you I would just shell out for a stock USB cord to use with ADB shell. You can find them online cheaply, and if you plan on doing any sort of rooting/customizing, you'll need one.
Posted from my Fascinate using XDA Premium

MultipleMonomials said:
I imagine that you could write a CWM zip that would copy the terminal emulator apk to the /system partition, but if I were you I would just shell out for a stock USB cord to use with ADB shell. You can find them online cheaply, and if you plan on doing any sort of rooting/customizing, you'll need one.
Posted from my Fascinate using XDA Premium
Click to expand...
Click to collapse
Oh I ordered a cord. I just meant I couldn't try it right away.
I tried some ADB shell stuff before I lost the cord and I couldn't even get it to list partitions. They really lock it down I guess. As I understand, you do have ADB access from TWRP, but I don't know if all the commands work or if you have root access.
Edit: It turns out TWRP backs up the boot and system partition as IMG files using the DD command, but all the others are backed up as simple zip files. I guess they decided no one would want to get a raw image of the data partition. Seems strange because extracting files from raw sectors is a common method of recovering files from camera memory cards etc, so why not a tablet/phone?
http://www.icsforums.com/forum/showthread/13239

Try the adb root command.
Posted from my Fascinate using XDA Premium

MultipleMonomials said:
Try the adb root command.
Posted from my Fascinate using XDA Premium
Click to expand...
Click to collapse
That would give root access while you're connected to the Recovery with ADB shell? Just type "root"?

So long as the device is actually rooted... Oh. Darn. I just remembered that the stock ROM has a bug that stops this from working. There's a kernel (flashed with ODIN) that fixes this for p5xxx, but it's not for 3xxx tabs. Maybe that's because they don't have the bug, though. Try it and see, but it may or may not work.
Posted from my Fascinate using XDA Premium

MultipleMonomials said:
So long as the device is actually rooted... Oh. Darn. I just remembered that the stock ROM has a bug that stops this from working. There's a kernel (flashed with ODIN) that fixes this for p5xxx, but it's not for 3xxx tabs. Maybe that's because they don't have the bug, though. Try it and see, but it may or may not work.
Posted from my Fascinate using XDA Premium
Click to expand...
Click to collapse
Well it's not rooted to begin with.
I'd be happy to root IF I can root without writing anything to the data partition. So far that seems to be impossible.

What Android version are you using? I might be able to modify the standard root zip to use the /system partition exclusively.
Posted from my Fascinate using XDA Premium

MultipleMonomials said:
What Android version are you using? I might be able to modify the standard root zip to use the /system partition exclusively.
Posted from my Fascinate using XDA Premium
Click to expand...
Click to collapse
Wow, that's possible? I think that would be useful for a lot of people trying to recover data.
Oh and what about the cache partition? Does the camera app store pictures temporarily there? If so that would be another source to try to recover pics from. Or do apps ever store docs there? Or is it not worth trying to preserve?
I was planning to use CF Auto Root but I asked Chainfire about it and he said that it can format the data partition if it becomes unreadable, so I didn't want to risk it.
Android 4.0.3
Kernel version 3.0.8-378347-user
[email protected] #1
Build number IML74K.P3113UEALD3
Model number GT-P3113

Well I guess this is all moot because I can't even figure out how to flash TWRP for the P3113. I downloaded an the .img file, Odin recognizes my device, and I got it into Download Mode, but I don't know how to set up the img as a tar.md5. You would think whoever made that .img would have provided instructions on flashing it, or just uploaded it as a tar.md5 since that's what you need. That's something that really annoys me about the Android community-- folks assume everybody knows what they're doing.
But the worst is all the threads where people ask how to flash TWRP to a Galaxy Tab 2 7.0 with Odin, and the replies are all "Just use CWM".
I found a download for the TWRP 2.2 for some Galaxy phone but I can't even examine the format of the tar.md5 because the freaking download site requires registration. Even if I duplicated the format, no idea if it would work. http://forum.xda-developers.com/showthread.php?p=30694404

I think all you need to do is rename the file to "recovery. img" and use 7-zip to put it inside a tar archive, then flash the tar with ODIN.
Posted from my Galaxy Tab 2 with CM10.1

MultipleMonomials said:
I think all you need to do is rename the file to "recovery. img" and use 7-zip to put it inside a tar archive, then flash the tar with ODIN.
Posted from my Galaxy Tab 2 with CM10.1
Click to expand...
Click to collapse
Apparently it's not that simple. Somehow you have to integrate an MD5 checksum with Linux console commands http://androidadn.com/2012/09/how-to-convert-img-files-to-tar-md5-to-do-a-flash-with-odin3/
Edit: Better thread http://forum.xda-developers.com/showthread.php?t=1484304
This is the IMG file I'm talking about http://rootzwiki.com/topic/27140-recoverytouchtwrp211galaxy-tab-2-7-and-10662012/
Edit: I do have a Macbook running 10.6 Snow Leopard so I think this might work http://www.macupdate.com/app/mac/14503/gui-tar
Edit: It can create a .tar but I don't know how to turn it into a tar.md5

Also, I was reading about Heimdall. Anybody know if it will work with just the .img file? http://www.thepowerbase.com/2012/04/slay-odin-with-the-mighty-heimdall/

Yeah, if you can get Heimdall running, you should be able to flash TWRP with that.
Posted from my Fascinate using XDA Premium
---------- Post added at 07:01 AM ---------- Previous post was at 06:58 AM ----------
I will warn you, however, that I think that by default TWRP backs up to /sdcard, which is located in /data/media, so make sure to switch that.
Posted from my Fascinate using XDA Premium

MultipleMonomials said:
Yeah, if you can get Heimdall running, you should be able to flash TWRP with that.
Posted from my Fascinate using XDA Premium
---------- Post added at 07:01 AM ---------- Previous post was at 06:58 AM ----------
I will warn you, however, that I think that by default TWRP backs up to /sdcard, which is located in /data/media, so make sure to switch that.
Posted from my Fascinate using XDA Premium
Click to expand...
Click to collapse
There's now a TWRP for the Tab 2 7.0! http://forum.xda-developers.com/showthread.php?p=38809460&posted=1#post38809460
I installed TWRP and now I'm trying to use ADB to see if I have root access. But Windows fails to install drivers for the tablet while in recovery mode

Well I've tried every driver I can find but I can't install the tablet in TWRP Recovery mode. Windows sees it as "GT-P3113"

Wait... Can't I load a rooted system image onto the tablet from Odin? Wouldn't that leave the other partitions unaffected?

Multirom nexus 7; booting linux from usb?

Hi, just been playing with multirom on my nexus 7, I would like to post this question in the appropriate threads but as a noob I can't so here goes:
It all is working fine, I can add extra ROMs using the extra Advanced>Multirom section in modified TWRP, this will let you install them to Sdcard or a USB drive. I also have been able to install Bohdi Linux to the Sdcard by flashing a multirom packed zip in recovery the normal way. What I can't figure out how to do is how to install Bodhi to USB so I can boot it from there. On this page:
http://forum.xda-developers.com/showthread.php?t=2093797
There are only instructions on how to flash the zip in recovery,
It seems I need a different version of Bohdi to flash it to the USB otg.
Can anyone advise, thanks?
Multirom is a truly magnificent piece of work incidently!

philipkdick said:
Hi, just been playing with multirom on my nexus 7, I would like to post this question in the appropriate threads but as a noob I can't so here goes:
It all is working fine, I can add extra ROMs using the extra Advanced>Multirom section in modified TWRP, this will let you install them to Sdcard or a USB drive. I also have been able to install Bohdi Linux to the Sdcard by flashing a multirom packed zip in recovery the normal way. What I can't figure out how to do is how to install Bodhi to USB so I can boot it from there. On this page:
http://forum.xda-developers.com/showthread.php?t=2093797
There are only instructions on how to flash the zip in recovery,
It seems I need a different version of Bohdi to flash it to the USB otg.
Can anyone advise, thanks?
Multirom is a truly magnificent piece of work incidently!
Click to expand...
Click to collapse
Have you tried to contact by PM the OP of this thread ?
Maybe he can help you or give you some answers
The OP is => @xela92

OK, thanks, that's a good idea,

philipkdick said:
Hi, just been playing with multirom on my nexus 7, I would like to post this question in the appropriate threads but as a noob I can't so here goes:
It all is working fine, I can add extra ROMs using the extra Advanced>Multirom section in modified TWRP, this will let you install them to Sdcard or a USB drive. I also have been able to install Bohdi Linux to the Sdcard by flashing a multirom packed zip in recovery the normal way. What I can't figure out how to do is how to install Bodhi to USB so I can boot it from there. On this page:
http://forum.xda-developers.com/showthread.php?t=2093797
There are only instructions on how to flash the zip in recovery,
It seems I need a different version of Bohdi to flash it to the USB otg.
Can anyone advise, thanks?
Multirom is a truly magnificent piece of work incidently!
Click to expand...
Click to collapse
Hi! Just wondering if you got any answer about this? I managed to install Ubuntu Desktop 13.04 on my Nexus 7 and everything was running fine until due to a power failure it won't boot anymore. I would like to boot from a Live USB to see if i can recover the installation. I tried using the USB option with an OTG from Multirom but i guess it's not intended for that. Thanks!

TWRP 2.7 Issues

Hi,
I am unable to mount the SD card in TWRP 2.7.0 on my Evita.
Anyone else is having this issue?

+1
doesn't work for me too
only way is to use usb-otg or adb push to push a rom, or be back to an older version .
You can use Recovery switcher

Could someone tell me or post a link to twrp 2.7.0 and how do i install. Thanks

openrecovery-twrp-2.7.0.0-evita.img
Size: 8.9 MB
MD5: 0eb7f3d14d75a019b19757836a1ec805
but better to use recovery switcher (flash in recovery like a rom and choose the recovery you want to install)...

Why are you claiming it's better to use recovery switcher? What's wrong with flashing it the normal way with fastboot?
Code:
fastboot flash recovery openrecovery-twrp-2.7.0.0-evita.img
Simple. This is the standard method for flashing a recovery to an Android device, it always has been and always will be.
Sent from my Evita

With the switcher you don't need a Pc to switch the recovery and no drivers problems.
Of course for me (and you ) fastboot commands are not a problem...
but for the one who did all the wipes before transferring the zip of the rom and is on TWRP 2.7 and without an usb otg cable ...

Well you'd have to be stupid to perform a wipe before having the ROM zip on your phone, lol. I wasn't trying to diss the recovery switcher, it's great work by Flashalot. I just firmly believe that anyone who is modifying their Android device should be comfortable with using adb & fastboot.
Sent from my Evita

Should be, but in reality

I always had problems with 2.7, I've stuck with 2.6.3 for a while.

sathish804 said:
Hi,
I am unable to mount the SD card in TWRP 2.7.0 on my Evita.
Anyone else is having this issue?
Click to expand...
Click to collapse
bzhmobile said:
+1
doesn't work for me too
only way is to use usb-otg or adb push to push a rom, or be back to an older version .
You can use Recovery switcher
Click to expand...
Click to collapse
Are you guys trying to mount in windows or linux or mac? Also you are hitting "mount > mount Usb storage" correct?
Sent from my SCH-i705 using Tapatalk

hitting "mount > mount Usb storage" with a Pc Win7 32 or 64 bits does'nt work for 2.7 version
Works with your version 4.4 compatible ...

bzhmobile said:
hitting "mount > mount Usb storage" with a Pc Win7 32 or 64 bits does'nt work for 2.7 version
Works with your version 4.4 compatible ...
Click to expand...
Click to collapse
OK...I'll play with it tonight if I can, I only confirmed on Linux.
Sent from my One X using Tapatalk

bzhmobile said:
hitting "mount > mount Usb storage" with a Pc Win7 32 or 64 bits does'nt work for 2.7 version
Works with your version 4.4 compatible ...
Click to expand...
Click to collapse
Same problem on XP x64 and x86. It seems to also affect the new version of CWM and Philz touch. All of them work fine on linux for me though. Good thing I hate windows.

Yep. Confirmed. Pretty glitchy too. I have windows 8 installed on my computer. I noticed when I entered recovery (2.7.0.0) the tray icons in the lower right of my computer screen started "jumping" left and right when I chose to mount the internal storage. The tray icons continued this until I put the phone into bootloader. I flashed 2.6.3.0 and everything was back to normal and working fine. Looks like there are a few kinks to work out.

When trying to wipe USB-OTG, it wouldn't work. So I'm pretty sure it's a general implementation problem
Sent from my HTC One XL using Tapatalk

pandasa123 said:
When trying to wipe USB-OTG, it wouldn't work. So I'm pretty sure it's a general implementation problem
Sent from my HTC One XL using Tapatalk
Click to expand...
Click to collapse
You actually had a OTG drive or device attached ? If so that may be by design but i can test and talk it over with the twrp folks if needed
Sent from my One X using Tapatalk

jrior001 said:
You actually had a OTG drive or device attached ? If so that may be by design but i can test and talk it over with the twrp folks if needed
Sent from my One X using Tapatalk
Click to expand...
Click to collapse
Yup. I just bought it to see how it is. Total waste of money in retrospect because I can't really see myself using it.
Sent from my HTC One XL using Tapatalk

OK folks, i can confirm i had issues in both win 7 and win 8.1, but removing the device via device manager, and letting it re-install it self on the next plug in i was able to mount with out any more issues.
On the topic of OTG, I was able to Mount OTG and then both flash a ROM from it and wipe it once it was mounted. The big thing with OTG is that you have to manually mount it if you want to utilize it.
Edit: fwiw I was using a 2GB thumb drive formated to NTFS

@jrior001 : is the recovery kernel compiled by you? Could you tell me if it is possible to use the sources of the 3.4.10 kernel that HTC has released, enable SElinux and produce a custom image of the recovery?

AlxMAX said:
@jrior001 : is the recovery kernel compiled by you? Could you tell me if it is possible to use the sources of the 3.4.10 kernel that HTC has released, enable SElinux and produce a custom image of the recovery?
Click to expand...
Click to collapse
For the official 2.7 all device work was done mainly by mdmower ( CM guy for the VZW HTC devices). The kernel is just the base cm11 kernel and the trees are hosted on his github. I only helped with a few things and testing for this.
What you are talking about is twrp based off the last HTC source release...which is exactly what I did on the 4.4 comparable version I posted previously. Stock HTC kernel source modified for selinux built with TWRP 2.6 sources at that time. My thread has the links for kernel source and trees if you want to play with it
Sent from my One X using Tapatalk