yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] runandhide05:
ok looks like its mounting with the newer cwm ( or at least its not erroring when trying to mount) but no select is not being helpful... err.

i think i found it, expect another test soon.

in the mean time clean up your device to remove any and all old files

delete anything in

/preinstall/recovery

delete the two scripts in /system/bin pre_recovery and load_recovery

ok this is based off the cwm 6.0 and should now have power button working, this also should have all the mounts fix.

xoom2recovery_v0.0.6.apk - 2.29 MB
[Xoom Android Development] ERIFNOMI:
I'm looking forward to this. I haven't been messing with my Xyboard but I believe the official ICS update has been released so I'm going to find that and hope they fixed my deep sleep issue then I'll look into this. I doubt there are many (or any) devs out there working on anything for this thing.
[Xoom Android Development] runandhide05:
whats up ERIFNOMI, go figure i spend all that time a while ago attempting to get this working, sell both of mine and then we make a break thru.... my luck right? lol

and I doubt there are many (or any) devs out there working on anything for this thing what the hell am i chop liver?? just kidding
[Xoom Android Development] Rennert:
Xoom2recovery0.0.6 starts on german Xoom2:) control with volume up/down and power works.

But on start:

E: can't find misc

When backup: error while backup boot logo

...Tapatalk
[Xoom Android Development] nchantmnt:
i'm sad to say that i suppose youre right. even if it still is a very capable device, it's lacking the dev's interest.

and somehow it seems that there aren't that many people out there to get their hands dirty with development themselves.

very sad as this is a really nice device and still very capable.
[Xoom Android Development] runandhide05:
Log please. I can't say this enough... reread op please.
[Xoom Android Development] Rennert:
Where cwm saved the logfile? In cwm can show log and report error

...Tapatalk
[Xoom Android Development] runandhide05:
really? i said and you quoted me, if you can not read the OP then please just wait until its out of alpha and working.
[Xoom Android Development] nchantmnt:
just to have it here again, but please all helpers/testers, read first post;)
[Xoom Android Development] Rennert:
Sorry, now i read the first thread;)

Logfile http://db.tt/kmeibASx

...Tapatalk
[Xoom Android Development] nchantmnt:
first off thanks for your effort

i would really appreciate if you keep on testing, but do runandhide05 a favor and send him the full log file located at /cache/recover/last_log via email or post it here. all we can see here on the pictures is only a small exerpt of the complete log and is lacking useful informatin.
[Xoom Android Development] ERIFNOMI:
Mine is stuck at boot after trying to fastboot back to stock (I was on the ICS leak). I'm not sure where to go from here since we have so little for this thing.
[Xoom Android Development] nchantmnt:
i thought there were leaks out there for the most devices? if you are able to get to fastboot and rsd mode shouldnt you be able to recover from a softbrick?
[Xoom Android Development] Hashcode:
I'm not sure runandhide has put code into his CWM to support any sort of custom ROM yet. Even tho mine does have methods in place they can be adjusted and made compatible.
[Xoom Android Development] runandhide05:
Hash we would love safe strap on the xoom2/xyb..

More the better!

And ya I'll continue work til I get it 100% I'm not going anywhere. Lol

Thanks for all the support guys.

As of right now my goal is bootstrap for cwm.

As we all know safe strap is a much better user friendly and safer way to go. Hence the name. Safestrap.

Give a true fail proof option
[Xoom Android Development] chumboy:
+1
[Xoom Android Development] weaver11b:
I do prefer a safe side and non safe side and love the new safestrap for the droid razr especially...it is a full proof way. Either way the more the better and to each his own. Thank you both for putting in your personal time to help crack these awesome tablets.
[Xoom Android Development] runandhide05:
Need a tester

Install app click install hijack, then power off and boot into bptool mode

x2recovery_v0.0.24.apk - 3.31 MB

Make backups of whatever u feel u need to,
[Xoom Android Development] Trackz:
I'll test, but I haven't followed the whole thread. Honestly, I was about ready to ditch the Xyboard until I saw this thread and all the cool stuff you're doing.

Is there anything special I need to do (besides what you mentioned) in order to do this. I have a Xyboard 10.1 WiFi, and don't want to completely brick it if I don't have to.
[Xoom Android Development] Rennert:
After install hijack don't boot into recovery---normal boot on bp tools

...Tapatalk
[Xoom Android Development] Trackz:
Should I have rooted first? Based on the 'su' failure, I would guess so.

I'm just getting failure "Error running exec(). Command: [su -c, ./data/data/com.runandhide05.xoom2recovery/filessurunner.sh] Working Directory: null Environment: null"

I'll root and try again.
[Xoom Android Development] runandhide05:
yes you need root

right now i am trying to get the preinstall working again, i lost power lastnight and lost some of the code i added in java. i also changed the way the hijack works ( all that is not important at this time)

so all i need for the following test is,

uninstall old app

install new app

open app and click install hijack

allow SU permission

click power off

boot normally and ensure preinstall is mounted in android system ( not recovery)

if it is let me know if /preinstall/recovery/(more directories and some files) exists

if so you can try to boot into bptools mode and let me know the outcome of boot

i have version numbered the apps by name of app but also if you forgot which one u installed i have version numbered the app in the about app screen.

please report version number and the above results

Tahnks guy tab should be here within the next day or so

ALSO if you dont know how to fastboot back to stock dont test please we are in early development and to remind other i dont have this tablet ( although will soon) so things could easily go wrong

apk

x2recovery_v0.0.28.apk - 3.31 MB
[Xoom Android Development] nitroglycerine33:
Damn you guys. I am going to end up buying a xyboard after all this. Lol
[Xoom Android Development] jeffcavicchi:
Booted fine, but nothing in /pre install. Directory is empty.
[Xoom Android Development] weaver11b:
Same here MZ617 /preinstall/ folder there but empty.
[Xoom Android Development] runandhide05:
ok,

do this

uninstll old app.

reboot

install new app.

click hijack system

click power off

boot straight into bptools

let me know the outcome

x2recovery_v0.0.33.apk - 3.31 MB
[Xoom Android Development] jeffcavicchi:
Nope. Boots directly into Android, nothing in /preinstall.
[Xoom Android Development] weaver11b:
Same results. Booted normally and preinstall is empty
[Xoom Android Development] runandhide05:
ok i wonder if its my new method,

try this,

x2recovery_v0.0.34.apk - 3.31 MB

err cant wait to get this thing in my hands

ERRR: edit

you know im getting tired when i miss stupid crap

hold off on 34

try this 35

x2recovery_v0.0.35.apk - 3.31 MB
[Xoom Android Development] Rennert:
No boot into Recovery over BP Tools

...Tapatalk
[Xoom Android Development] runandhide05:
Try 34

Then try 13

http://d-h.st/ioi
[Xoom Android Development] taquion12:
Smell sooo close, thanks again runandhide05!

Enviado desde mi XT910 usando XDA Premium HD app
[Xoom Android Development] runandhide05:
Pulled

It works but the original log wrapper is not running so we have mount and WiFi issues on normal boot. That's why I was trying a new hijack method that allowed original log wrapper and hijack to run. But its not working.:'(
[Xoom Android Development] runandhide05:
Great News guys, for those that have not seen it already HashCode has got his safestrap working on the Xoom2/xyboard

Check the thread out here

http://xdaforums.com/showthread.php?t=1965686&page=2
[Xoom Android Development] taquion12:
Hi runandhide05, I was trying to test your releases but I think as I'm still in Honeycomb I won't be able to install those right?, you as hahscode worked the apks with Ics sdk?

Enviado desde mi XT910 usando XDA Premium HD app
[Xoom Android Development] chumboy:
should this thread be closed or at least redirect people to the above thread?
[Xoom Android Development] runandhide05:
No because I am still working on it.

No public testing because I have one now
[Xoom Android Development] runandhide05:
I'll look at dropping the api after I get everything working they way I want
[Xoom Android Development] sonjohn1:
runandhide05,

Any chance of a oc'able kernel when recovery is done? Thanks for all your hardwork. You are the reason I've held on to my Xboard.

John
[Xoom Android Development] runandhide05:
yes and no.

flash a overclocked kernel answer is no

flash a kexes kernel with oc possibilities answer is yes, google kexes

over clock stock kernel? its already do'able without recovery google will help ya out with that one

now do i know anything about kexes kernels, i know of the method, and proxess, just live swapping kernels, its possible in just about any linux based kernels systems

do i know anything about building kexes kernels, answer is a big fat no on that one. lol
[Xoom Android Development] nchantmnt:
for honeycomb it sure is possibe to oc the stock kernel. for ics: atm not possible, since the used kernel modules are compiled for the honeycomb-kernel. we will have to recompile the modules otherwise they will not work on ics so for now no oc ;)
[Xoom Android Development] runandhide05:
ok guys and gals

let me run this out to all and see what the feedback is,

on a device that uses bootstrap ( not safestrap ) if you flash a rom that screws up your system your done anyways, you will need to fastboot your device back to stock, because of the way bootstrap in general works, it only hijacks the boot right after you run the app, ( although mine will allow cold boot via bptools ) but keep in mind that the hijack takes place once the system is already mounted, so no system or a REALLY screwed up system from a bad rom flash your not going to be able to re enter recovery, i say all this to ask.

we all know safestrap will be here soon enough,

we also know the inherent risks involved with bootstrap hijack,

that said do we really care about restoring a backup or do we just want to throw caution to the wind while we wait on safestrap??

i can not for the life of me get recovery to unmount the system, which really only needed for restoring a backup,
[Xoom Android Development] jeffcavicchi:
Personally, I have used restore on my phone often enough to feel that it is necessary, but that's just me. I'd rather wait and have a fully working backup/restore option, but...the real question is, are you getting tired of banging your head against this problem? There's no need to keep working on it for us if it is no longer fun or at least a rewarding challenge for you...
[Xoom Android Development] gjnicholson:
I also frequently back up my system and data and restore when needed (e.g. after theming framework-res.apk or SystemUI.apk and they cause a bootloop). I would prefer a recovery that enables me to back up and restore as wel as flash zips etc.

Edit: Apologies fir the double post; internet access is cr*p this morning:eek:
[Xoom Android Development] runandhide05:
ok, well im still working on it, just at the same place i was two weeks ago, plenty of different ways and methods to get into cwm, but the BI*CH wont toggle mount/unmout of the system.

i have tried the chage only mode hijack ( killed power off charging and quickly wore out some usb ports)

tried the logwrapper hijack but just let to too many issues when not booting into recovery, f*ed up some early inits which caused mounting issues as well as wifi issues.

lastly tried and currently using a new method, which involves adding to a stock script to look for boot mode, then process as normal if anything but bptools.

that was been working the best because there are no adverse effects.

so we have w/r on any mount in recovery, and system in mounted in recovery,

just cant unmount it which is needed for restore feature.

so here is what i have so far.

the apk

com.runandhide05.xoom2recovery.Bootstrap.apk - 3.37 MB

and my source if any one wants to see.

com.runandhide05.xoom2recovery.zip - 3.34 MB
[Xoom Android Development] jeffcavicchi:
Sincere thanks for your efforts, that's for sure! Hopefully either you will have a breakthrough, or someone will look at your work and add the missing component. I am good for nothing except testing, which I am always happy to do.
[Xoom Android Development] Hashcode:
One thing to take into account when doing a normal bootstrap is what I call the "endless hijack".

So if you're using logwrapper to hijack and drop new files into rootfs, what's to stop logwrapper from re-hijacking again when the new OS boots.

Normally the init.*.rc scripts dropped into rootfs have the logwrapper command removed (at least from where it's triggered originally).

Safestrap doesn't have this issue because it doesn't boot using the same system partition if it hijacks.
[Xoom Android Development] Rennert:
After install your new bootstrap and boot up over BPtools don't boot into recovery.....only normal boot

...Tapatalk
[Xoom Android Development] nchantmnt:
on a device without the capability of using a sdcard i wouldn't use backups anyway...or at least not that often.

sure it is a truely comfortable way to go back after a bad flash and i used it a lot with my old atrix but 16gb (what the most of us are limited to) is nothing that i would want to shrink down in favor of backups or having the stock rom on my tab while using a different rom slot all the time anyway.

after all i will go with the methode that will work best, but i'd be glad for every possibility to save some space for apps, games, media, etc ;)

i really hope that you will be able to achieve a fully working bootstrap methode, but the ability to write to /system from recovery and flashing zip files is enough for me.

i have flashed stock fastboot files over and over again and really this is no problem for me, nor should it be for anyone who is up to messing around with any of the methodes for xyboard.

all in all i want to say thank you very much for your efforts. it is much appreciated.
[Xoom Android Development] chumboy:
I personally would always like to be able to flash back to my stock setup.

for most rom's, i've found that there's always something not working 100% (bluetooth phone calls, gps, etc.) that i really need.

then i flash back to stock and have all my hardware working as it should.

i hope i'm understanding what you're asking and answering correctly.

i guess i could always fastboot back, but then i'd need to setup all my apps, screens, customization, etc. so i can still use it in my car.

runandhide....i'm happy with whatever you decide. In short, i can make it work on my end no matter what you choose. i'm just appreciative that both you and hash are giving to us.
[Xoom Android Development] runandhide05:
Then u probably have too much leftover files laing around from previous methods/apks.

If you boot into bptool moderun this is terminal

getprop ro.bootmode

If its unknown your not in bpmode if returns bptools then u have files stopping the hijack. Or preventing it from running.

I see u have been using safe strap too. Unless u know what files to remove between tests I would kindly suggest just testing one or the other.

You can look in system/bin and see if your stock logwrapper ( which when opened should be a mess of symbols and letters and numbers, if not then u have something leftover.
[Xoom Android Development] Rennert:
Ok;) now have placed the original logwrapper in system/bin and install hijack and boot into recovery works.

Start backup and xoom2 reboot and all datas cleared (hardreset). Internal memory also deleted. Backup rules;)

Now flash the fastbootfiles:)

...Tapatalk
[Xoom Android Development] runandhide05:
I understand half of what you said, u were able to now boot into cwm,

What's the other part about wiping internal memory?
[Xoom Android Development] Rennert:
Ok;)

-Deinstalled bootstrapper, copied original logwrapper to system/bin

-reinstall bootstrapper, start and install hijack, power off

-boot to Recovery over BPTools

- start backup...."backing up /system.." after few seconds the xoom2 reboot and "prepare device" on bootup

-all data deleted and internal memory is clean

...Tapatalk
[Xoom Android Development] runandhide05:
OK mate I understand that, I'll look into it when I have a moment. That should DEFINITELY not happen.
[Xoom Android Development] runandhide05:
which backup format did u use?

.tar or dup?

i ask because i just got home and created a backup with tar and had no reboots.

and infact im restoring /data as we speak, ( note i said data not /system)

OP updated with latest checklist,

everything is now working minus the infamous mount/umount of system

Checklist:

BOOT INTO ClockWorkMod --- CHECK thatnks nchantmnt

https://www.youtube.com/watch?v=Hnz7...e_gdata_player

Verify proper directories are mounted (cache, data, system, and so on) --- CHECK

Verify proper handling of /data/media --- CHECK

Verify ability to flash zips --- CHECK

Verify proper factory reset while preserving /data/media --- CHECK

Verify backups --- check (formate must be set to .tar (dup has to umount system to create an img and umount is not working for the system as of yet)

Verify restores --- 50%-50% advance restore of cache and data works (restore of system is not working)

What is bootstrap?

bootstrap hijacks the boot sequence once you run the app and click install hijack

then press power off, once off press and hold volume up, volume down, and power to boot to menu,

select "BPTools"

this will boot you into clockwork recovery.

after you boot the device the hijack will have to be re installed each time you want to boot to recovery, ( this is the normal way bootstrap works, and its how it is going to work on here.)

Last issue to work out is the unmounting of the system partition, ( which is needed for restoring a backup for the system)

here is the app

xoom2recovery.0.0.68.apk - 3.37 MB
[Xoom Android Development] jeffcavicchi:
Very impressive - thanks! Been fun to watch the process unfold. Hopefully that final piece of the puzzle falls into place soon!
[Xoom Android Development] runandhide05:
Well... Ya about that...

Even if it did... I don't think it would be every useful,

Here's why,

We all know what dd if= to is.. If u don't its a way to put an IMG on a partition or make an IMG of a partition. Either way. Now way back when the first things we try is to simply dd and IMG of cwm to the recovery partition while booted in android, it works however on boot it checks the sig or hash of the partitions, and if they don't match or have moto sign you are greated with boot failure screen, only way past is to fast boot the stock IMG and all good.

Knowing that now.

I made a backup, booted back into android, changed my script to load recovery with system unmounted and I went back in and restored the backup. And booted back up to this wonderful screen...

So... It looks like safestrap ( because of the way it loops the "new system IMG" aka ROM slot ) is the only option.

But that's just my opinion,

I could be 100% wrong
[Xoom Android Development] jeffcavicchi:
It is incredibly lame how locked down these things are.
[Xoom Android Development] runandhide05:
so i think i was just proved wrong, and i have never been happier....lol

new build coming soon

DAMN i love hashcode.
[Xoom Android Development] taquion12:
Thanks runanhide05, those are impressive notices, it's almost done, it's the best thing I've heard since I'm still waiting for the infamous upgrade to ICS in my Xoom 2 me 8.2 brazilian version, thanks men maked my day

Enviado desde mi MZ607 usando XDA Premium HD app
[Xoom Android Development] runandhide05:
Just got android 4.2 keyboard the one with Swype gesture pulled from the n4 system dump working on the xyboard, flash if u want to.

4.2Keyboard_4.2-517167.zip - 9.44 MB
[Xoom Android Development] Rennert:
I use tar;) this effect by too many bootstrap installs. Now i have a clean system for test.

-install recovery 0.0.68, start, install hijack, power off

-boot into recovery, select tar as default and bang

Restart and all data lost and internal memory clean

I don't know

...Tapatalk
[Xoom Android Development] gjnicholson:
On My Motorola Razr, which has a locked bootloader, the recovery does not format the system or data partitions, just "rm -r *" during the restore of tar backups.
[Xoom Android Development] chumboy:
Could you clarify?

you first said it seems Safestrap is the only option.

then you said you were proved wrong (i guess by some PM we didn't see, maybe from hashcode).

Will your method work or will only Safestrap work in the future?

Did hashcode give you a tip that could get your method working and you're going to release a new build?

or did hashcode show your method won't work and we need to rely on Safestrap?

sorry....just trying to get my head around which direction we are now taking.
[Xoom Android Development] runandhide05:
Life happens, in the middle of a move, I know what needs to happen, hash and I talked last night, I have dedicated HOURS each night for weeks to this, I know how it needs to work, I know how to change my recovery build, I made changes and it didn't work. And you all know I'll work on it some more later.

Just chill it will happen.

Remember I'm no developer and have never claimed to be. I do this **** cause its challenging and fun.
[Xoom Android Development] chumboy:
hang in there and enjoy life...you'll get it soon.

thanks again for all the selfless hours you've dedcated to this project.
[Xoom Android Development] gjnicholson:
Thanks for your hard work and long hours and good luck with the move:good:
[Xoom Android Development] runandhide05:
i just got twrp to boot, here we come, i have a good feeling about this....
[Xoom Android Development] cool_recep:
can't install the apk. error extracting.

and yes, MD5 intact
[Xoom Android Development] runandhide05:
ok guys, as some may see in their emails shortly;

i am going thru a move right now, and i truely thought that i would having a working recovery once device in hand, and i know that some of you have donated money, for what every reason, whether as a thanks for work so far or a good faith donations, however buy the time i get everything moved, and have time to strat wroking on this once again i beleive safestrap will be out and working.

So i have refunded those donations, i do not feel like i deserve them. if you feel otherwise you are free to do what you want, but as i said i dont "feel" i deserve them.

thank you for all your support, and i will let you guys know when i get back to able to work on this
[Xoom Android Development] jeffcavicchi:
And this is why people are willing to donate money to developers here in the first place - because they are for the most part stand-up guys who try their best to make this community better!

Good luck with the move - we'll be here when you get back!
[Xoom Android Development] taquion12:
Go ahead man I think, that most important that the material thing (program,whatever), it's been listened and work in a common way, and you gave that to us at least me

Enviado desde mi XT910 usando XDA Premium HD app
[Xoom Android Development] chumboy:
To show you how much of a stand-up guy RunandHide is, I donated to him to help with the development of this recovery program and to atleast buy a tablet to work on.

Because he went on hiatus and cooled the development of this recovery....

he refunded my donation b/c he didn't feel that he had earned it.

i beg to differ...he had already "earned" my donation for his current work.

there aren't many people left in this selfish world that would return a donation b/c he felt he didn't deserve it.

Runandhide is one of them!

he's helped renew my hope for us.

Runandhide...you're an honorable guy...wish you the best in your move and personal life and look forward to your return.

:laugh::laugh::laugh: