yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] jeffcavicchi:
Sorry, sorry - that's not what I meant. I was just trying to keep the guy from trying to flash anything or use the work in progress as if it were a finished product. It didn't seem worth it, given that he seemed uninterested in reading through the posts to see where things stand, to try to explain where exactly you are in the process...I have to say, I think it is clear from my previous posts that I appreciate the work you and others have put in.

How about, "Nothing is going to work the way you want" - especially since he is trying to flash stock ICS from a nandroid?
[Xoom Android Development] runandhide05:
Sorry moment of weakness and massive frustration

I understand your response.

Someone with the dx2 or the other moto that has a charge hack tell me where your charging bin is located? On the root of the device or is it in the system
[Xoom Android Development] jeffcavicchi:
No worries - hard to always have things come across the way you want in forums like this.

;)
[Xoom Android Development] runandhide05:
Word!
[Xoom Android Development] tutabeier:
Sorry if I didn't read all the thread. My fault.

I wouldn't flash or try anything. I don't even have the Xoom 2 ME, because Motorola-Brazil didn't release the ICS update.

I'm just considering

if

,

when the recovery is finished

, may be possible to use a backup from a user from UK (for example) with ICS and use this backup to bring the ICS to brazilian users? I've done that with the CyanogenMod for Galaxy 5 and Mak-Droid for Galaxy Pocket.

And I'm asking because I want to buy the Xoom 2 ME, but as Motorola-Brazil didn't update for ICS, nor has a release date and I don't want to get stuck on HC, if, in the future, may be possible to use recovery to update to ICS.

I'm really sorry if my posts were the cause of yours discontent. I promise that I'll read before ask. :D
[Xoom Android Development] nitroglycerine33:
No, the kernel is different
[Xoom Android Development] weaver11b:
Verizon mz617 xyboard 10.1 the testinstall.zip seemed to work fine. Unable to, mount system when tried to backup. I went to go back and just change the default zip to a tar and it froze. Had to do hard reset. Tried 3 times with same results. Hope my log helps.
[Xoom Android Development] ForevermanRGPC:
When I get home I'll get my kids X2 and and find where the charge hijack is. If I put up a link to a ROM with it will it help.

Sent by my NO signal but Unlocked GS3
[Xoom Android Development] runandhide05:
No just want to know where the charge bin is on the device.
[Xoom Android Development] ForevermanRGPC:
Nitro, can't remember, but did you have the X2 recovery built into your Eclipse ROMs or was it a separate apk? I know I still have your ROMs somewhere just can't find them.

Sent by my NO signal but Unlocked GS3
[Xoom Android Development] runandhide05:
here try this one

and you know the deal clean up and test zip and backup and then post logs

xoom2recovery_v0.0.30.apk - 2.28 MB
[Xoom Android Development] jeffcavicchi:
Sorry - this one just hangs.

Do you need the login even though I never got into recovery?
[Xoom Android Development] mikeymike75:
I don't know if this makes a difference, but I have a Droid 3 and just went back to this stock rom. I found a charge only script at /system/preinstall/bin
[Xoom Android Development] runandhide05:
where did it hang and for how long?

isnt the /system/preinstall on there symlink to just /preinstall?

what is the script il look at it

try this one

xoom2recovery_v0.0.31.apk - 2.28 MB
[Xoom Android Development] jeffcavicchi:
At the "M" logo and for several minutes.

Trying next version now.
[Xoom Android Development] runandhide05:
ok i added a lot of code, let me know what 31 does, cause i commited out half of th enew stuff.
[Xoom Android Development] jeffcavicchi:
Zip applied, backup running right now. I'll let you know.
[Xoom Android Development] runandhide05:
ok then,when thats done post up that log then have at it with these three

these are small increments of code added at a time.

i want to see what part of the code was killing it

lets see which boot and which dont, if you get one that boots do the normal checks, zip, backup, and logs

xoom2recovery_v0.0.33.apk - 2.28 MB

xoom2recovery_v0.0.34.apk - 2.28 MB

xoom2recovery_v0.0.35.apk - 2.28 MB
[Xoom Android Development] mikeymike75:
There are no arrows shing it is symlinked like the others. Here is the script. May I ask what you use to read binay ?
[Xoom Android Development] runandhide05:
A bin is not a script. Script is plain English (well unix)

If its a bin then it just the stock charging bin.
[Xoom Android Development] mikeymike75:
here it is.
[Xoom Android Development] jeffcavicchi:
Here is the log for v31. Sorry, but I have to get up early for work, so no more testing until tomorrow night.

V31 backup ran fine, but no placeholder in /system or /system/app.
[Xoom Android Development] mikeymike75:
33

Does it make sense to you that I would have to keep updating Busybox? On some of these builds I have had my busybox drop to earlier versions. Ran 33 and it booted through. No log in cache.

---------- Post added at 10:29 PM ---------- Previous post was at 10:10 PM ----------

I am obviously doing something wrong. Every one of them booted. There was nothing in /cache or /preinstall. The four files were in /system/bin each time.
[Xoom Android Development] runandhide05:
Ran 33 and it booted does not help me.

Busy box included in the apk is just an older version

Booted into what? Recovery or android?

If they booted into recovery did u do as I asked and flash backup and log each one?

Have u cleaned up your files lately better yet between each of these four latest versions
[Xoom Android Development] taquion12:
Hi runandhide05, I been disconnected for a while, and I can see that you are making a huge progress into this, I know that you checked everything over a over again, but I was thinking that maybe could be the script (the one who tries to put the placeholder.txt) the problem with the zip install?

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

Its been verified by the guy with the unloacked bootloader he was able to flash zip successfully and if u look in the logs the system is/has been mounted as read only. That's why nothing is getting flashed
[Xoom Android Development] taquion12:
Sorry for the question....I was trying to be helpfull..

Enviado desde mi XT910 usando XDA Premium HD app
[Xoom Android Development] runandhide05:
No need to apologize. More questions the better
[Xoom Android Development] nitroglycerine33:
I do not think busybox is getting installed.
[Xoom Android Development] mikeymike75:
Sorry, they are booting up and running. Not recovery. I have deleted the files between tests.

---------- Post added at 10:56 PM ---------- Previous post was at 10:48 PM ----------

And again I uninstalled the previous, deleted /cache and /preinstall and charge only mode, recovery, load recovery, and pre recovery from /system/bin. Installed 33, ran it, pressed reboot, it shut down and restarted android. The preinstall and cache directory's were made but nothing in them. The four files were placed back into /system/bin.

Same thing with 34. And 35. ?????????? Is it me?
[Xoom Android Development] runandhide05:
stupid question alert. once off did u plug in your charger?

also u said 33, did u try 34 or 35?

its ok if one does not work at all, in 31 i added a lot of stuff, and it cause tab to hang at boot. so in 33 34 and 35 i added just a little at each point, so if 33 is a no go thats cool move on to 34 and then 35,

the way i added the code back in is i have bb do three different thinks all included in 31 which was a no go, so i added one back in 34, then took it out and added a different one in 35 and so on, so just cause one didnt work does not mean that 34 or 35 wont.

just trying differnt things here cause at this point im at a lose, and i think i have mad that clear..lol

edit

thanks on 34 lets see what 35 does

edit again~~~::

clean and go try 31, if that does not work then yes its you...lol 31 should known to work get into recovery, system is mounted but as read only and cant unmount.

if you dont experience that then yes problem on your side..lol

aslo u didnt answer this "stupid question alert. once off did u plug in your charger?"
[Xoom Android Development] Rennert:
Morning;) time for test, begins with 35.

Can you make a advanced backup in recovery? My data backup is too big and backup needs over 20 minutes. In advanced backup only backup /system and then .android_secure for test.

...Tapatalk
[Xoom Android Development] mikeymike75:
Yeah, I plugged in charger right after screen goes down. About to try 31.
[Xoom Android Development] runandhide05:
Not sure off the top of my head, but by the question it sounds like 35 got you into recovery? Yes?

If so let me know and you could also test 33 and 34 for me and pull the logs before u install and test each one.

Thanks I'm off to bed, would love to wake up to some good news.

Peace
[Xoom Android Development] Rennert:
35 boot into recovery, backup in progress, data so long:)

After this, test 34 and 33, logfiles i upload complete

...Tapatalk
[Xoom Android Development] runandhide05:
Make sure u upload before u test the next ones, other wise they will over write each other
[Xoom Android Development] Rennert:
I copy the logfile before install the new apk;)

Have a nice sleep and not a dream from recovery.

...Tapatalk
[Xoom Android Development] mikeymike75:
Ok. I got 31 to work. Tried 33 and it hung. No log file available.
[Xoom Android Development] gjnicholson:
Version 0.33 would not boot into recovery for me. It was stuck at the Motorola Dual Core Technology logo for 5 minutes before I rebooted.

Here are the logs for versions 0.34 and 0.35.

I could not mount /sdcard or system on version 0.34 and could not run a backup.

I was able to make a backup in version 0.35, but not able to mount /sdcard or unmount /system.

Both versions 0.34 and version 0.35 installed the test zip, but there are no placeholder.txt files.
[Xoom Android Development] mikeymike75:
This is 34. I flashed test file but could not find in system. Twice I tried selecting backup format and the system froze. Had to reboot. It said it couldn't backup but there was a folder created in clockworkmod. Cache was empty but luckily I created a log in recovery. I am done tonight.
[Xoom Android Development] mikeymike75:
35, the log has everthing.
[Xoom Android Development] Rennert:
So, all versions tested;)

Logfile 34/35 http://db.tt/0UTculuc

33: don't boot in recovery

34: backup-can't mount /system, no placeholder.txt in /system

35: backup-android_secure error, no placeholder.txt in /system

...Tapatalk
[Xoom Android Development] runandhide05:
You need to change backup type to tar not dedupe

Sorry I just saw u tried to and froze. My bad for not reading well enough.

Looking thru the longs and from feed back it looks like the killing if init was the cause for stall at boot logo "M"

And killing adbd was OK as well as unmounting partitions before entering recovery. Later tonight when I'm back at laptop I'll try both active as see where that gets us.
[Xoom Android Development] chumboy:
oh, boy!

i think i can smell it...
[Xoom Android Development] runandhide05:
Try this one out, make sure u uninstall the old one cause I signed it while mobile so its going to have a different signature on it and won't install over the old ones

http://db.tt/WC4cN1RW
[Xoom Android Development] weaver11b:
Mz617 changed backup to .tar installed.zip went to backup cant mount system when trying to backup.
[Xoom Android Development] nchantmnt:
Unable to mount /system
[Xoom Android Development] Rennert:
Logfile 36 http://db.tt/52UC4WR4

Can't mount system

Bedtime, alarm rings in 6 hours;)

...Tapatalk
[Xoom Android Development] jeffcavicchi:
Back from work and hoping for something to test tonight!
[Xoom Android Development] nchantmnt:
damn... it's less then 5 hours of sleep for me from now on... sorry mates, got to let it be for tonight...
[Xoom Android Development] Hashcode:
Hello.

I've been really busy over the last few weeks, and I'm sorry to jump in so late in the dev process, as it looks like runandhide05 is doing a great job with this. I've had a Xyboard owner getting on me about helping with this project for the better part of a month. :/

I do have a recommendation:

I wouldn't hijack on charge-only-mode. It's messy having to plug in and unnecessary. I believe some of the Tegra devices had to use it because their init.*.rc files didn't have any exec calls to something like "logwrapper", which I use for my own projects, and it's what Koush's original Bootstrap for the DX used.

You can see here where it's executed during the init.*.rc script on line 73:

(and again a couple times a few lines later to mount userdata, preinstall and cache)

This happens VERY early in the boot so that most of the services and other mounts never happen and the filesystem is easier to cleanup before 2nd-init (which is the goal here).

As an example logwrapper hijack, here's mine for Safestrap Recovery (a multi-rom bootstrap/recovery system which handles 2nd-init and kexec booting):

https://github.com/Hashcode/android...onic-razr-droid4/install-files/bin/logwrapper

One other thing is take a look near the top of the logwrapper (above):

That checks to see if the user was powered off and plugged the device into the wall ac. This normally brings up charge-only-mode and it *bypasses* the logwrapper hijack in this case. You really don't want to bother 2nd-initing to go to charge mode. Just let it happen like it would normally. This saves a lot of testers/users from having to use factory cables etc to fix their devices when they're stuck in 2nd-init loops and run the battery out.

Hopefully it helps.

If you're curious, this is more info about Safestrap (used on Droid 3, Bionic, RAZR and Droid 4):

http://blog.hash-of-codes.com/how-to-safestrap/
[Xoom Android Development] jeffcavicchi:
Nice to see others chiming in and helping out!

I just want to say that all of the effort being put in here by Runandhide05 and others is very much appreciated - I will be super-psyched if a custom recovery gets fully ironed out for the Xoom 2. I bought the thing because I figured it would get a fair amount of developer attention - which it obviously hasn't, until now.

Thanks again - hopefully the frustration level isn't getting too high!
[Xoom Android Development] runandhide05:
Thanks hash! I'll look into it a bit deeper, I had a while back looked at the logwrapper hijack and was unable to get it to work at all. But at that time I had 0 info on how it worked.

Thanks again I really appreciate the info
[Xoom Android Development] weaver11b:
You are doing an awesome job and know you will get it figured in no time!!

Thanks Runandhide05
[Xoom Android Development] runandhide05:
hash,

hopefully you read this, but i have a few questions about this type of hijack ( we'll call it the logwrapper hijack)

after looking at a bunch of stuff let me see if i understand how this method works,

on boot the init.rc are basically what start the boot process, on early-fs the execution of the logwrapper is called. (which is a binary correct?) which starts mounting partitions as well as other precesses

from your logwrapper it looks as if you are ( via app) replacing the stock logwrapper with your executable logwrapper, which then sets up a few variables, checks to see if device was just powered on or plug in to charge while off, then setups you safe partitions, so on, and so on. if im correct let me know, cause basically it looks a lot like what i was doing, but from an int ( charge only mode) but i was doing it way to late on the boot process and by which time half of the init-.rc has already begun.

hope that makes sence, been a long day but i think i see where i need to go from here

this is starting to make more sense, it also explains why on some not so well make bootstraps you get booted into recovery every boot. ( if creater of scrips dont check to see how device powered up, either manual or to simple charge while off)

edit last question is what is bbx included in \install-files\install-files\etc\safestrap

it looks like a form of busybox but i could be way off
[Xoom Android Development] taquion12:
First of all! runandhide05, really thanks men you took and abstract idea (at least for me), and transformed it into a reality, and without the device (BRAVO MAN BRAVISSIMO), even right now some more dev as you ,are incorporating to this project(second goal started in some way , which was start more developing for xoom2/xyboard), well as I see.

but here my question, that's what you are pointing in your last post, was what nitro was trying to say with kill init processes?

Enviado desde mi XT910 usando XDA Premium HD app
[Xoom Android Development] jeffcavicchi:
Question for everyone - has anyone gotten the stock charge only to work again without fastbooting back to stock? I replaced the new charge only file with the original, but can't get into stock charge only made - what am I missing?
[Xoom Android Development] runandhide05:
I'm sorry I think I know what you are asking but at the same time I don't understand what you are asking.

But at any rate i did try to kill processes but it didn't work however its very likely because the hijack was too late in the init process.

Think of it like this.

Init. Is a count from 1-100

100 = android booting

With the charge hack we start at

45 so all of 1-44 has already started.

Logwrapper starts closer to 5-10 so less to kill, less to go wrong

So here we go...

Big few days at work next few day, and of course a lot of rewrites in the apk but we'll get there
[Xoom Android Development] taquion12:
Thanks man that's why you are the chosen one, that's exactly was I tried to ask , I'm really noob with all of this, but the process at itself ,started becoming really fascinating for me, I hope not boring you with my questions (and my english, jejeje), it's just to get a little more knowledge.

Enviado desde mi XT910 usando XDA Premium HD app
[Xoom Android Development] runandhide05:
first start of logwrapper

uninstall old apk

• delete /preinstall/recovery;

• delete /system/bin/pre_recovery;

• delete /system/bin/recovery;

• delete /system/bin/load_recovery;

replace charge-only-mode with the stock file

and make a backup of system/bin/logwrapper.

from here on out we will be droping the charge only mode hack

FYI the first few of these may not even boot to recovery,

we are starting from scratch guys.

really i just want to see if this boots into recovery, if there follow the same instructions and post any logs

Reminder! Get those faatboot files handy and if u don't have any then by all means don't test this!

]

FYI OP updated with the drop of charge only mode,

for two reason,

a) not getting anywere

b) logwrapper is a proven method, stick with what works :)
[Xoom Android Development] runandhide05:
no problem mate,
[Xoom Android Development] taquion12:
In my Xoom2 me 8.2 brazilian version, at the begining black screen, tried pwr+volume down , and got into recovery, the bad news stuck in recovery, tomorrow I'll fastboot and be ready for new tests

Enviado desde mi XT910 usando XDA Premium HD app
[Xoom Android Development] runandhide05:
Stock recovery or custom recovery?
[Xoom Android Development] taquion12:
Custom one

Enviado desde mi XT910 usando XDA Premium HD app
[Xoom Android Development] runandhide05:
OK try the norm

Backup

Flash zip

Restore backup

Since your in there test away please

I know u won't be able to access log so keep an eye on the read outs please.

And post what u can

Go into mounts and try to mount and unmount recovery
[Xoom Android Development] mikeymike75:
Did you post the apk?
[Xoom Android Development] taquion12:
Backup seems ok

Restore partially, can't mount /system, but tried with boot an data and actually restoring data (thing that I gonna do after fastboot, just to try ,with the last recovery based in charge hijack)

Install zip seems ok, but I can't check if exist placeholder.txt

Enviado desde mi XT910 usando XDA Premium HD app
[Xoom Android Development] runandhide05:
I did from the sound of it it booted recovery....but only recovery. Email me if u want to test but I garentee u will need to fast boot to restore, or at least that's what the Brazilian guy said. But I still want to know what all is working once in recovery
[Xoom Android Development] runandhide05:
When your done in recovery try to reboot and let me know what happens

Also guys I may take the first few test apks to a private status because odds are until we done have to fast boot to restore each time I think it would be safer to keep unsuspecting users from a real brick if they don't read and notice u absolutely need fast boot files because I know that all models don't have fast boot files avaible
[Xoom Android Development] taquion12:
I'll fastboot but after that if I install, the old hijack charge and just restore data would be probably to have the apps installed before?

Enviado desde mi XT910 usando XDA Premium HD app
[Xoom Android Development] runandhide05:
If u fast boot using the flash all script u will loose everything.

U can try to manually just flash the system.
[Xoom Android Development] taquion12:
Great country Brazil, sorry I'm from Venezuela but my Xoom it's from Brazil, at least the software,jejeje.

Enviado desde mi XT910 usando XDA Premium HD app

---------- Post added at 11:31 PM ---------- Previous post was at 11:24 PM ----------

Thanks again man, good solution, but I'll try that tomorrow, backup says done, tried reboot and pwr+volume down but still boots in custom recovery.

Enviado desde mi XT910 usando XDA Premium HD app
[Xoom Android Development] Hashcode:
Correct, it's a binary which forks the init process to let it continue while some other process happens (in this case the device mount)

Actually when the Bootstrap installs, the real logwrapper is renamed to logwrapper.bin which is called at the end of the logwrapper shell script if it should pass through.

Correct :)

You're spot on. It's slightly modified version of the "recovery" binary created for CWM (static linked) and it has a huge portion of the busybox lib included which helps provide all of the shell commands I use in my early boot logwrapper script, because no /system will be mounted yet. I named it bbx so that it doesn't conflict with TWRP's busybox or any other multi-use binary which could come into play.
[Xoom Android Development] taquion12:
I forget to say after restoring data showed:".android_secure.img not found, skipping restore of /sdcard/.android_secure."

Enviado desde mi XT910 usando XDA Premium HD app
[Xoom Android Development] gjnicholson:
Since upgrading to ICS my .android_secure folder is located on my external sdcard (/mnt/external1)
[Xoom Android Development] Rennert:
I have on twice sdcard (sdcard/external1) an .android_secure.

...Tapatalk
[Xoom Android Development] gjnicholson:
Before upgrading to ICS I formatted my internal and external sdcards and did a factory reset.:)
[Xoom Android Development] Rennert:
Any apps use the internal .android_secure. I've in twice .android_secure other files (mostly of installed games)

...Tapatalk
[Xoom Android Development] lambergio:
you must change the permissions: with root explorer or other file manager with root hold charge_only_mode and change the permissions as in the screenshot ... and works again
[Xoom Android Development] jeffcavicchi:
Perfect - thanks!
[Xoom Android Development] runandhide05:
also the gentleman with the unlocked boot loader please email me, i need to see if you have tested TWRP img i gave you, still waiting to hear back form you.

thanks