yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] runandhide05:
That's the same thing I get, you stated all working as far as backup restore so I wasn't sure if it was working for u or not
[Xoom Android Development] jeffcavicchi:
Hadn't thought of this - what if you activate the new ROM slot, and then restore? I have always just restored with the stock slot active, thinking that I could choose where to restore - but maybe the restore gets placed in whatever slot is active...?

Going to try it right now.
[Xoom Android Development] runandhide05:
The problem I have is once u do a backup, then create a romslot and try to restore there is no backups avaible to choose,

My thoughts.

Once in a romslot the /sdcard and /data/media are blank. Only /ss have the data/media content. So restore may need to readjust where it is looking for backups. Because its probably looking at /data/media/TWRP/.... And not /ss/TWRP/...
[Xoom Android Development] jeffcavicchi:
Yeah - I am coming to the same conclusion. I made a backup of the blank ROM slot and am trying to find it right now. If I can figure out where it is then I can copy the stock backup to that location...

Not sure that is even possible, though - would the new ROM slot be somewhere not accessible to Root Explorer when booted into the Stock slot? I am guessing yes...
[Xoom Android Development] runandhide05:
ROM slots are at sdcard/safestrap/rom-slot(1-4)/
[Xoom Android Development] jeffcavicchi:
I found that, but it doesn't show any backups. However, if I activate ROM slot 1, make a backup, and then go to restore, it shows the backup (which does not, of course, actually have anything in it - it is just a backup of a blank slot). I can't figure out where it is putting the backup, though - it must exist on the sd card somewhere, since TWRP can find it, but I can't.

My thought is, if I can find where the backups for ROM slot 1 are being written, I can copy the backup for the stock slot to that location, and then restore to ROM slot 1...

Not sure it will really work, but it's what I've got,
[Xoom Android Development] Hashcode:
That's a bug. You should see your stock backup and be able to restore it when a rom-slot is active.

I'll look at it here in a bit.

Question: Everything on the /sdcard works till you activate a rom-slot?

What happens if you reboot with it active and re-enter Safestrap? Can you see content on /sdcard then?

And what happens if you re-enable stock after having a rom-slot enabled and not able to see /sdcard content? Do the backups show up immediately?
[Xoom Android Development] jeffcavicchi:
Everything on the /sdcard works until I activate a ROM slot. I did activate a ROM slot, and rebooted to a blank screen, as to be expected. Once back in recovery, the only thing showing on /sdcard are the backups of the blank ROM slot I made. So, no access to the actual contents of /sdcard, if that makes sense. Once I switch back to the stock ROM, all contents of /sdcard are available again (including the backups of the stock ROM), and reboot to system works fine. So, the ROM slots are routing somewhere other than the actual /sdcard.

Need any logs or anything?
[Xoom Android Development] runandhide05:
booting into twrp from stock rom, i see all content on sdcard at /sdcard and at /data/media,

activate rom slot and /data is blank as well as /sdcard however all /data/media content is locatated at /ss

reboot from twrp on rom slot 1 into sytem, no system ( normal ) boot back into twrp from rom slot, no content at /data/media. restore stock rom slot and still no content at /data, only after i reboot into android, then back into twrp does content appear at /data

now, in theory,

create a rom slot and then reactivate stock rom, boot into android, dd the system and copy it to /sdcard/safestrap/rom-slot-1/

and then boot into twrp, activate rom slot 1 and do a factory reset "should" boot into android right? again in theory, if so then there is another problem because it does not boot.

dont know if that will help at all, but thought id give it a try, let me know if you need any other info

also how much work would it be to increase the size of the system on rom slots?

a stock deodex is over 600mg and im having issues symlinking this when there are alternate mounting locations for data
[Xoom Android Development] Hashcode:
Lol.. so the bug is kind of funny.

"/sdcard" is actually /data/media. So when you swap from stock to a rom-slot it's swapping the contents of /data/media to be the rom-slot's "/data" not the stock "/data/media". Looking at a fix.

How big is the stock system? I can set that to be whatever size is needed.
[Xoom Android Development] runandhide05:
OK stock partition is 590mb for system

But system dump the zip aligned deodex rooted busybox brings it around 650+ so to be safe and allow future growth I would say around 680-700mb that will also give some play room if other want to add things to a stock base.

When flashing a stock ROM the zip dies out at xbin around the P's so its close and I've trimmed it as much as it can be without killing too much
[Xoom Android Development] Hashcode:
NEW TEST:

*** WARNING UNTESTED CODE IN THIS BUILD -- IF YOU'RE NOT COMFORTABLE TESTING BLIND CODE, PLEASE DON'T LOAD THIS BUILD RIGHT AWAY

https://dl.dropbox.com/u/41149741/Safestrap/Xoom2-Safestrap-3.05.10.apk

CHANGES:

System partition in rom-slots will now be 700mb (need to delete/recreate rom-slots)

Massive work on /data/media == /sdcard handling. COULD BE BUGGY

I need the following steps run as a test:

1. Boot into recovery, check to see what files are on /sdcard

2. Activate a rom-slot, and check to see what files are on /sdcard

3. Are they the same?

** I need a /tmp/recovery.log from the above test (you can move it to the sdcard by "Advanced" -> "Copy Log to SD")

NOTE for future ROMs with custom init.*.rc files:

There is a line in the current init.mapphone_***.rc files:

service sdcard /system/bin/sdcard /data/media 1023 1023

This starts the sdcard daemon which mounts /data/media as /sdcard

Devs who add custom init.*.rc files (in /system/etc/rootfs of their ROMs) should set this line to read:

service sdcard /system/bin/sdcard /datamedia/media 1023 1023

This change will enable /sdcard to always show the same content no matter what ROM slot you are on.
[Xoom Android Development] mikeymike75:
Here you are. The files were the same in both rom slots. The touches were spot on and I did not come across any errors. It looks like you are there! The log is attached. Thanks for your work. All we need now is a rom!
[Xoom Android Development] Rennert:
-Data on sdcard are the same.

-Can't make a backup with v10 "E: Insufficient space"

-Restore backup of v9 (stockRom) in RomSlot1 and xoom2 boots, but bootloop on bootanimation. wipe data and cache, now xoom2 boots correctly.

Recovery.log http://db.tt/lF1CzfHb

...Tapatalk
[Xoom Android Development] jeffcavicchi:
Same thing here. Contents of /sdcard are the same in stock ROM slot and slot 1, but cannot create backup of stock ROM - E:insufficient room. I can't try restoring a previous backup because I deleted them prior to this test.

FWIW buttons on splashscreen not working for 8.2

Log attached.
[Xoom Android Development] runandhide05:
Without having tired this yet, just woke up and still a lot to do today... It sounds Luke recovery is trying to backup everything on data, including /media when on romslot, which would cause the insufficient memory error.

Easy way to tell is to run a factory reset and if it wipes your entire /media content then its not preserving /media then its probably trying to backup all of the /data.

DO NOT TRY IT IF YOU ARE NOT WILLING TO LOSE ALL DATA I'll try it if I get a sec
[Xoom Android Development] chumboy:
This progress is awesome!

Thanks hash.

thanks runandhide.

thanks to all the other brave testers.

is there a way to increase the size of the data partition relative to the size of my internal sd card when i'm creating a rom slot?

can twrp/safestrap display data partition sizes as a percentage of the sd card?

ie...those with a 16gb xyboard might get 3 data partition sizes to choose from....1gb, 2gb, 3gb.

i have a 64gb xyboard and will have more space. so i might get 3 data partition sizes to choose from....1gb, 5gb, 10gb.

don't know if you'd have to hard code these increased values or could a script determine the size of the sdcard and apply a percentage of that size in order to populate the 3 data size partition options.

don't want to derail the basics that you guys are trying to perfect...i just had this idea on my mind and wanted to get it in print. perhaps on a distant future update to safestrap.

thanks again for your work.
[Xoom Android Development] jeffcavicchi:
Thanks Runandhide! Since this isn't your primary device I'll let you have a go first... :D
[Xoom Android Development] Rennert:
On RomSlot1 the sdcard(internal memory) only have a size of 1,97GB. The real internal memory find in ss.

The stockRom works normal on RomSlot1;)

On Version9 backup works on stockrom, on romslot1 doesn't work (low memory, sdcard size only 1,97gb)

On version 10 in twice mode the backup doesn't work (sdcard size 1,97gb)

...Tapatalk
[Xoom Android Development] runandhide05:
OK here's my quick feed back.

Creating a new ROM slot and restoring a backup works perfect. No problems there.

Thanks for the 700mb bump

Preforming a backup while on romslot

As u can see it tries to backup everything. 11gb worth of stuff.

Preforming a factory reset while on romslot--- once booted into android there was no content on "sdcard" but there actually is content if u browser by file browser in Twrp.

So on ROM slot it looks as if it does not share the /data/media with the stock ROM. I say this because it showed only .59Gb avaible on "sdcard" while in android on ROM slot1

Reloaded stock slot and all media was present again.
[Xoom Android Development] Hashcode:
K, looks like I broke the code which skips the /data/media code while adjusting.

Bugfix later.
[Xoom Android Development] jeffcavicchi:
Just want to say, once again, thanks for your (and Runandhide's) hard work on this!

:good:
[Xoom Android Development] Hashcode:
Wasn't the splashscreen working for 8.2 in previous versions?
[Xoom Android Development] Hashcode:
@chumboy

Would you really use a 10gb data partition tho? Most apps that need a lot of files will add them to /sdcard space anyway. I think in almost ANY case, the 3gb data size will be more than enough.

I wouldn't want to pre-allocate 10gb on the stock data/sdcard area that would be mostly wasted.
[Xoom Android Development] runandhide05:
splash screen has not worked on any verisons on the 8.2 thus far
[Xoom Android Development] jeffcavicchi:
Same here. Buttons on splashscreen have never worked on the 8.2. I have always had to access recovery via BPTools.
[Xoom Android Development] Hashcode:
Actually it's showing 1.1GB total backup size which *could* be correct. I checked the code where it's calculating the size on data to backup and it looks to be skipping "media".

The concerning error is right below that in the screenshot:

"Available space on the SD card, in KB: 0"
[Xoom Android Development] chumboy:
sound rationalization. didn't really think that far...doh!

i'll default to your experience.

thanks.
[Xoom Android Development] chumboy:
I guess that once Hashcode gets Safestrap working properly, we should get our own forum?

then the awesomeness can beging....roms, roms, roms!

ha....can't wait.

any word on and updated safestrap version?
[Xoom Android Development] weaver11b:
Lets work on one thing at a time here...and if you read the op title it says what version and date of release.
[Xoom Android Development] chumboy:
what in the world are you talking about???

are you sure you're responding in the right forum?

hash has not said he's perfected safestrap for xoom2/xyboard....afaik, it's still in alpha testing but very, very close to perfection.

please read all the posts before responding.

once safestrap is perfected and someone creates a rom, Xyboard/Xoom2 owners might get their own forum instead of sharing it with xoom1 owners.

thanks.
[Xoom Android Development] Influxvisions:
I'm willing to test, but the download link is broken, can you reload it? Thanks.
[Xoom Android Development] jeffcavicchi:
Hopefully we will get a new version with some bug fixes soon! Backup wasn't working in the last version...
[Xoom Android Development] Rennert:
Backup works in last version 3.05.10 on my Xoom2 32GB 10.1;)

Restore only tested cache and works. Install StockICS on RomSlot1 also works.

...Tapatalk
[Xoom Android Development] jeffcavicchi:
And you got version 10 from where? Directly from Hash, I assume.

---------- Post added at 06:45 AM ---------- Previous post was at 06:44 AM ----------

Never mind-forgot he put the link in a post.

Neither Runandhide05 nor I could get backup to work on that version on the 8.2.
[Xoom Android Development] Rennert:
Sorry i mean 3.05.9 (v10 don't work) downloaded from Link on This thread.

Can new upload on Dropbox http://db.tt/uWDXfijz

On 10.1er xoom2 works backup perfectly of stock slot (romslot1 backup doesn't work) and also create RomSlot1 and restore /system to RomSlot1----boot correctly:)

...Tapatalk
[Xoom Android Development] jeffcavicchi:
Can you restore a backup of the stock ROM to ROM Slot 1? On the 8.2 you cannot see the contents of /sdcard from ROM Slot 1, so you cannot restore a backup.

Hopefully we will see a new version soon - I am confident Hashcode will get all of these final issues straightened out!
[Xoom Android Development] Rennert:
Yes, have activate Romslot1, restore a backup of StockICS and it works, must only make a factory wipe (without wipe bootloop). But on romslot1 the internal sdcard only have a size of 1,97GB. The original internal memory found in SS of root filesystem.

...Tapatalk
[Xoom Android Development] jeffcavicchi:
I can't see the backup at all - there is nothing on the /sdcard directory of ROM Slot 1...
[Xoom Android Development] Rennert:
I remember me, going another way;)

Here the steps to create romslot:

-install Safestrap V9 http://db.tt/uWDXfijz

-open Safestrap V9 and install Recovery, reboot into Recovery

-make Backup of StockICS

-Reboot on StockICS

-open Safestrap V9, uninstall Recovery, uninstall Safestrap V9

-install Safestrap V10 http://db.tt/0sozy2za

-open Safestrap V10 and install Recovery, reboot in Recovery

-create RomSlot1, Activate and restore StockICS Backup on RomSlot1

-Reboot. If Bootloop: go to Recovery and wipe Data and Cache (Factory Reset)

-Reboot and have Fun with StockICS on RomSlot1.

At this time the internal memory have only a size of 1,97gb.

In V9 only can make backup of Stock Slot.

In V10 only can restore to RomSlot and Stock (only tested cache)

...Tapatalk
[Xoom Android Development] jeffcavicchi:
AHA! A fancy work-around!

Thanks!
[Xoom Android Development] edulimajunior:
The "INSTALL" button on the safestrap MENU are not working for me. They look disabled.

i already test the v9 and v10.

i'm trying install a .zip package.

Someone can help me?
[Xoom Android Development] jeffcavicchi:
If I am correct, you cannot install a zip on the stock ROM slot. You would need to restore a backup of the stock ROM to a new ROM slot, and then install the zip - but right now you cannot restore a backup of the stock ROM to a new ROM slot because of a bug. I think Hashcode built this into this version of Safestrap to keep people from screwing up their stock ROM - a sort of fail safe.
[Xoom Android Development] chumboy:
so, if i install v9, then v10 (according to above proceedure), then backup and restore work on romslot1?

i know restore won't work on stockrom slot....and that's a good thing for crackflashers when drunk.

are you saying that safestrap on the xyboard is now working?

backup/restore work on romslot1?

if this is true, the you've finally done it !!!!

wahooooo!

Now...who's going to crack out our first rom for this badboy?

do we now deserve our own forum for xyboard/xoom2?

this might signal other devs that backup/restore work on our tablet and they can now start creating roms.
[Xoom Android Development] jeffcavicchi:
It's more complicated than that. You have to install v9, make a backup, uninstall v9, install v10, and then restore the backup to ROM slot 1. Then, if you want to make another backup, you have to uninstall v10, reinstall v9, make a backup, etc. Right now, v9 will make a backup, but it will not allow you to restore to a different ROM slot. V10 will allow you to install to a different ROM slot, but it will not allow you to make a backup.

I am sure Hashcode will get this straightened out when he has time - we just need to be patient.
[Xoom Android Development] chumboy:
ahhh......got it.

not very useable at this stage, but like you said....paitence.

it's awesome it's gotten this far.

thanks, again, hash for taking on this challange.
[Xoom Android Development] jeffcavicchi:
Anyone heard from Hashcode recently? Been a while...
[Xoom Android Development] chumboy:
nope.

hopefully he's perfecting this project.

safestrap is the keystone to future rom developement.

once safestrap is perfected, rom's should start flowing in.
[Xoom Android Development] jeffcavicchi:
I know. And I hate to be the guy who bugs the dev incessantly, but I would hate to see this project just die out.
[Xoom Android Development] jeffcavicchi:
Saw that Hashcode released a new RC candidate for the Atrix today. Hopefully we will get an update soon as well!
[Xoom Android Development] Hashcode:
New Build: 3.05.13 for Xoom2

https://dl.dropbox.com/u/41149741/Safestrap/Xoom2-Safestrap-3.05.13.apk

md5sum 4efd47b8ea160a66729b32e737f11d92

Mainly this build fixes /data/media handling in rom-slots.
[Xoom Android Development] jeffcavicchi:
So, I hate to be the bearer of bad news, but unless I am missing something I still cannot create a backup with this version (maybe you already know this, Hash). I can see the contents of the entire sdcard on both the stock ROM slot and Slot 1, but when I go to run a backup of the stock ROM I get the insufficient space on E error. Also, the backup screen shows the system as around 500MB, but data at 0, which I assume is not correct.

I can't try restore, because I don't have a working backup to restore.

Log attached - please let me know if there is anything else I can do to help!
[Xoom Android Development] jeffcavicchi:
Oh yeah - on the plus side the splashscreen buttons on this version work perfectly on the 8.2!
[Xoom Android Development] Rennert:
Thanks;)

-Backup don't work on StockSlot and RomSlot1

-Restore works on twice Slots, but only tested with cache Partition

-on Romslot1 System boot the internal memory now have the correctly size.

Now can i fully use the StockICS on RomSlot1, all 100% works

...Tapatalk
[Xoom Android Development] jeffcavicchi:
So the splashscreen buttons and internal memory on the ROM slots have both been fixed! Now Hashcode just needs to get the backup working and everything will be working!

:thumbup:
[Xoom Android Development] Rennert:
Backup to external storage (for Xoom2 32gb with sd slot) would be good;)

...Tapatalk
[Xoom Android Development] chumboy:
my test produced the same results.

wow...we're almost there....almost...there...
[Xoom Android Development] jeffcavicchi:
Really trying to be patient - but I am very excited to have a fully functional Recovery for this device!
[Xoom Android Development] jeffcavicchi:
Hope this project is still going....
[Xoom Android Development] panosx:
Same here..
[Xoom Android Development] spidertop:
Any news???

Inviato dal mio XOOM 2 con Tapatalk 2
[Xoom Android Development] lucasarran:
Hashcode seems to be very busy for a while, he's working on 4.2 with other safetrap devices. So I'm guessing once he's finished there he should return. He's a very busy dev. :D
[Xoom Android Development] jeffcavicchi:
He definitely has a lot of irons in the fire!

We probably seem a bit paranoid about falling through the cracks, but the XOOM2 is a little bit the red-headed stepchild of the tablet world...
[Xoom Android Development] jeffcavicchi:
Now I am getting nervous.

This recovery is so close...
[Xoom Android Development] panosx:
Maybe we should start a donation thread for the recovery and rom development. But I believe the participation would be low..
[Xoom Android Development] Rennert:
at least it works with limitations. anyone have tested the Restore with version13? I only tested restore with cache partition and it works. Restore in romSlot should be work, restore in Stock only cache tested.

...Tapatalk
[Xoom Android Development] jeffcavicchi:
Can't make a backup, though.
[Xoom Android Development] Rennert:
With version9 can make a backup of stock rom, with version10 or 13 can restore to stock and romslot. Must install v9 for backup, deinstall v9 and install v13 for restore.

http://xdaforums.com/showthread.php?p=34229407

V13 http://db.tt/guCFXRVt

...Tapatalk
[Xoom Android Development] jeffcavicchi:
Yeah. All we need now is to combine the two versions.
[Xoom Android Development] allsalvati:
One question:

With this can i do a dual boot?

I ask because more than one person uses the tablet.

Thanks
[Xoom Android Development] jeffcavicchi:
Theoretically yes, but it isn't working quite right just yet.
[Xoom Android Development] Rennert:
With detours works with 5 roms, 1 stock and 4 romslots.

...Tapatalk
[Xoom Android Development] Jiggity Janx:
AFAIK there are no custom roms to install into any of the rom slots. There is just stock and rom slots available. I tried using version 9 and 10 and whatever the trick was multiple times without success. Also still can't restore anything to my knowledge. So basically right now all that can be done successfully is installing "tweaks" you find elsewhere in twrp. I do appreciate that but hope this project reaches it's full potential.
[Xoom Android Development] Rennert:
Yes;) but the stock rom can be restore to romslot1 and it boots correctly. Good for testing:)

...Tapatalk
[Xoom Android Development] mikeymike75:
Would anyone want a systemUI with a battery mod to flash? I have one I have been working on and flashing. I am trying to get 1% working, but this will give you something different for now.
[Xoom Android Development] gjnicholson:
I edited my services.jar to enable 1% battery display and used the UOT kitchen to mod my systemui.apk.
[Xoom Android Development] jeffcavicchi:
I would definitely like to have something to flash!
[Xoom Android Development] NWKENT:
+1 me..I'd like to try your battery mod..

Thank YOU..

Sent by my Motorola MZ617-32_Droid XYBoard 10.1_ICS 4.04
[Xoom Android Development] mikeymike75:
Xyboard Xoom2 Battery Mod Flash

Ok. Here is a flashable zip for a battery mod. It has all of the images for a 1% battery incriment, when I figure that out I will post how to do that. Make sure you have made a backup with version 9 Safestrap and created a rom slot. You will have to reboot into the stock rom , open Safestrap and uninstall recovery. Now install Safestrap 10 or 13 and overwrite existing app. Open it and install recovery. Reboot and go into recovery. You should be able to select the rom slot that was made and see a restore file. Restore your backup here. You can then install the zip file. I found this great tool that lets you make these files, and pakage them in a flash file. If you use this tool you will have to edit the folder names. Here is the link, http://xdaforums.com/showthread.php?t=1918500.

Make sure you place the zip in the download folder prior to rebooting. Otherwise you may have a hard time finding it.

The flash also has an edit for the lock button, but it is not working yet. I will post more as I get them. Enjoy!
[Xoom Android Development] jeffcavicchi:
Thanks! Will let you know how it goes!
[Xoom Android Development] Rennert:
In the batterymod.zip are only png's, no services.jar

For users with xoom2 32gb and external sdcard is version 13 better. The external sdcard has the correct file size (on version10 only 1,97gb)

...Tapatalk
[Xoom Android Development] mikeymike75:
Which smali file is it in? I have looked through all of battery services and didn't see it.