yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] matt4321:
You can also just press up after a few seconds and it'll go straight to bootloader, it says 'fastboot protocol started' or something along that line
[Xoom Android Development] shpitz461:
Oh yeah, good call. I thought it went to RSD and not fastboot, can't really remember as I hardly use the keys, I just issue an adb command or use the extended boot menu within the ROM :)
[Xoom Android Development] matt4321:
I do too, power menu all the way. Just thought it'd be easier for Alxoom33 in case he gets confused
[Xoom Android Development] Alxoom33:
Y

Thanks, I really appreciate your trying to help.

I know how to enter fastboot manually and using TWRP. Where I have issues is getting to the cmd or adb window in my PC. I know how to use terminal emulator on tablet or in twrp. But not how to access it on the PC. That's why I was trying to use Rsd lite.

Guidence on this point would be appreciated.

Thanks,

Edit, Dah, State menus, find, cmd. OK got it lol!

---------- Post added at 10:46 PM ---------- Previous post was at 10:02 PM ----------

cmd says 'fastboot' is not recognized as an internal or external command, operable program or batch file.
[Xoom Android Development] drewski_1:
Make sure the directory with Fastboot is in the Path or navigate to the directory in the CMD window.
[Xoom Android Development] Alxoom33:
not sure I understand you. The directory says, C:\users\my name

So what do I do to navigate to the directry in the cmd window?
[Xoom Android Development] drewski_1:
Use the 'cd' command (change directory)

Go where ever you Fastboot installed. It's not a stock Windows app.
[Xoom Android Development] kromoxs:
offcourse you can't..

on fastboot mode you can't adb comand.

and also on adb you can't fastboot comand

fastboot flash recovery yourrecoveyname.img

cmd says 'fastboot' is not recognized as an in
[Xoom Android Development] silbo:
Here not to spam with beginners ask.
[Xoom Android Development] shpitz461:
Easiest is to just right-click the folder where you have adb.exe and fastboot.exe installed, click while holding the shift key, you'll see a menu item 'Open command window here'. This will open a command (cmd.exe) window for you at the right location (path) automatically.

'C:\users\my name' is the default path cmd.exe opens up when you execute it, which is the root folder of your Windows profile.

---------- Post added at 09:39 AM ---------- Previous post was at 09:29 AM ----------

Even better solution to the path issue would be to add the adb/fastboot path to your system path permanently, as follows:

1. press Windows+Pause/Break, this will open 'Control Panel'>System

2. click 'advanced system settings' in the left-side menu

3. in System Properties click the 'Advanced' tab

4. click the 'Environment Variables' button

5. in the bottom section ('System Variables') click on PATH

6. while Path is highlighted click 'Edit' button

7. goto the end of the text and add

;<path to the location of adb.exe and fastboot.exe

in my case it is 'C:\android-sdk\platform-tools'

if the text doesn't end with a semi-colon, add it before you append your path

8. click OK all the way

Then, next time you open a cmd, adb.exe and fastboot.exe will be available from any folder/path :)

And yes, let's stop with noob questions and stay on topic, feel free to open another thread if you still can't get it to work...
[Xoom Android Development] CBDSonline:
would it not have been easier for someone to have posted a twrp flashable (4.3) boot with the fixed boot.img already in place. ???
[Xoom Android Development] shpitz461:
You can do it yourself, extract the ROM and the boot image, replace boot.img in the ROM with the img from the bigpart-boot, then zip is all up.
[Xoom Android Development] CBDSonline:
its easy to build the required boot files but it seems as a few users are struggling with the computer skills and need to follow word for word instructions. so for the few that can not follow the instructions then a flashable .zip would help..
[Xoom Android Development] uzi2:
Those who don't know what they're doing should leave well alone for now. This is a great step forward, but until we have a ROM that makes use of the extra System partition space, there is no point in doing it.
[Xoom Android Development] Asphyx:
Yes I have to agree with this....

This is not your straight forward Custom Rom Flash and a screw up can really screw up a device badly...Especially if you do not know what your doing and need your hand held!

The Issue here isn't about how to RePart or that you need a specialized skill to repart as THAT is petty straight forward!

The difficulty is due to those who wish to retain root on a ROM that doesn't include Busybox as many others do and those who are not that savy with ADB and it's use should really just WAIT till someone incorporates BusyBox into Dream's Rom or use the EOS flavors for now until such time as the Devs get around to making some roms specifically for the new partition system and with all the rooted goodness you have come to expect.

And me personally I would rather if the Devs were spending any of their precious time developing something that they would put it towards Kit Kat than on making older roms work under the new system.

If all you want to run are those old roms then there really is NO REASON to repart the unit at this time!

They were all developed for the smaller partition structure in the first place!

Sorry to the newbies who are just dying to use these things but if your not up to speed on ADB and the Developer SDK usage I suggest you just wait until there is a rom that actually REQUIRES ReParting before you get involved in using a ROm that gets you no true benefit and costs you the ROOT access you seem to need....
[Xoom Android Development] rmkenney12:
Asphyx, I agree with you for the most part, but I think that from my experiences(and

the complaints I've seen from others), CM10.1 on the Stingray is causing problems,

and there are a bunch of people out there with 10.1+GApps who are not

in an OK condition just right now.

I tracked down my issue using the CWM logs, which tipped me off to the fact that my

/system was used up, but just barely so. So I knew that the jig was up and had to

do something drastic.

This after thrashing around with 10.1+Gapps on my Xoom for about a month thinking

that it was just a bad config file, old cache, bad settings, etc.

They I assumed I had excess cruft on my Xoom, flashed back to factory and went

through the entire OTA update process - my backups didn't go back far enough :-/.

Only to find out that even a superclean CWM+10.1+Gapps was still big enough by

itself to make my device flake out. The thing failed during the Cyanogenmod

account registration/signup page at the very beginning.

The GAPPS install itself did NOT give adequate notification that it had run out of

space while installing from CWM - the progress bar simply went from ~60% installed

to done: that's all the feedback you received.

I've seen many forum messages from people who don't realize this, and are struggling with

the idea that the GAPPS package is somehow broken(or broken on 10.1) in some

way that can be fixed by flushing the caches, or deleting all app data, etc., etc.

When in fact GAPPs is probably missing 20-50% of itself and there is really nothing

they will ever be able to do to get it to work.

So considering that the CM devs kind of drove their users over the brink like this, I

think they(perhaps moreso than other ROM dev groups?) need to take charge

of the situation.

Sure, CM is distributed without Gapps, so they aren't necessarily responsible for

testing the interactions with GAPPs, but how many of their users actually run their

devices sans Gapps? Not many.

So they probably should at the very least:

a) take the Xoom 10.1 ROM out of distribution so nobody else can download it,

or at least have big red text next to the DL link saying that it can NOT be used in

conjunction with GAPPs, and/or

b) issue a widespread warning about this issue, so anybody still thrashing around

with 10.1+GApps will get it, and know that they should go back to 10 or do

something different, and/or

c) start testing their ROMs(whenever they do test them) with GAPPs installed.

My 5 cents worth. Not angry - we're all just fiddlin with this stuff anyways - I just

want to make sure that others still thrashing with this issue either get help, or get

the message(or both).

Thanks.
[Xoom Android Development] Alxoom33:
Easier would be nice. The OP seemed pretty straight forward

.

Hey! That's pretty cold! Loss of root was not in OP nor was fastboot contemplated. Let those who are gracious enough to help do so without such comment! Thanks.
[Xoom Android Development] drewski_1:
d) point people to BaNkS Core GApps (which is like 16MB) and tell them to install other Google Apps from the Play Store ;)
[Xoom Android Development] rmkenney12:
I guess I didn't make myself clear. I'm perfectly fine. I realized the problem and backed

off to CM10. I read the docs, and adjusted what I was doing. My Xoom is performing like

a champ again.

I'm still using the semi-full install of Gapps that the CM Wiki points you to,

although I would like the biggest f'ing Gapps package I could get my hands on. I -want- the

Full Google Experience, even if only to decide that I hate it 6 months from now and go to

something else. That's called wanting more choices in life, including in my personal

computing environment.

I -want- it on /system so there's a lower risk of borking it. That's my expectation. If that's

not what you want, or if you don't want Gapps at all, that's fine. From what I'm seeing on

the forums(messages from non-experimenters - from people who want to be able to use

their device as a tool mostly, rather than just an experimental toy), the latter does not

appear to be the commonly held sentiment.

This is a commodity, like anything else - the more people want something, the likelihood

that $$$$(or devel in this case) will go that route - no dev is going to put more than X man

hours into something that -nobody- else on the planet gives a damn about or wants to use.

So, do not piss off the majority of the stakeholders in this movement, even if they -are-

ignorant as babies, otherwise you'll be doing your development in the same desert-like

enviroment that Ubuntu is about to be in in about 3-4 years.

Not everybody is at your level of expertise, or has the time to be. There are a -lot- of those

people out there who are taking the plunge into experimental ROMs simply because the

carrier-provided ROMs are utter ****. They just need something they can use, and are

certainly not going to hunt down and read 10 miles of documentation just for the love of

it. Even assuming they have the time for that away from their jobs or families.

At best(and maybe at worst?), AOSP ROMs are or will be victims of their own success. This is

due to people like realjumy and BRD working on the problems, and trying to give people

more options that are also easier to use. Not by telling people what they can't have, and

why it's "good" for them to want less. Perhaps you would prefer that these ROMs are harder to

use, and have more pitfalls so that those "Lesser Folks" will be kept out? Kill the promise, and

the hope of a better experience? Is that really your attitude, or am I just reading too much

into your last comment?
[Xoom Android Development] sublimaze:
I think both of you read too much into each other's comments. I glanced at the OP (I am driving to work) and I saw no warning about losing root, which is important to a lot of people following this thread. Maybe I missed that warning, but it is definitely not obvious and it should be. Repartitioning is not something to be taken lightly. Everyone should thoroughly read the OP of any rom/mod before proceeding, but they don't. So I think a lot of drama could be avoided if the OP is amended to say this project is primarily for devs, and definitely not for people that cannot root manually. Just my $0.02
[Xoom Android Development] Asphyx:
Your Right Sub...It doesn't mention losing Root because this isn't a thread about Dreamcli's ROM it is about Repartitioning....

This loss of root is only affecting that ROM. Has little to do with this specific project.
[Xoom Android Development] matt4321:
Those who have lost root on 4.3, can you try flashing this in recovery: http://d-h.st/hk1

from what I recall it will say it's failed but should actually work.

No that's root, go talk in dreams thread about it
[Xoom Android Development] drewski_1:
I tried that. It didn't work.

Oddly, it worked for me months ago when I installed 4.3 on the stock partitions.
[Xoom Android Development] shpitz461:
Try my procedure from a few pages ago... Works for me...
[Xoom Android Development] buffalo_guy:
http://xdaforums.com/showthread.php?t=2506997&page=32

http://xdaforums.com/showthread.php?t=2506997&page=33

See posts 314 and 330. I used this to successfully root Dream's 4.3
[Xoom Android Development] drewski_1:
oh, I already used Mcfisch's process and am rooted. :)

was just pointing out that SuperSU zip didn't fix root for me.
[Xoom Android Development] NWinfuse:
I've been using the unified gapps from the CM10.1 thread for as long as I can recall with no issue. Have also used banks core gapps with no issues.

There are too many people flashing roms that don't even understand some of the most basic things. I believe that is the biggest cause of issues.
[Xoom Android Development] LOGMD:
Id love a 1GB FS =D might try that tonight! need to get this machine to autobuild 3 times a day i got 2TB to mess with :P
[Xoom Android Development] bigrushdog:
Just wanted to give an update on the status of affairs. 4.3 is done, finished, and cfx 4.3 will never run on Xoom. The reasons are complex. Just trust me on that. As I write, synergy is building our 4.4 master branch manifest. We ate taking a different approach to some things this time. There is no reason to believe I can't have a build soon after the project basics are proper. I do know this. Devices newer than xoom are having some graphics issues. Our kernel is a dinosaur. All that being the case, I'll be curious to see how things go. There will come a point where it will be time to retire the xoom. And that time is soon now. When or if I make thataassessment, I will return my loaner xoom to its owner and encourage people to upgrade. Just the scoop...
[Xoom Android Development] scottgti:
Blah, blah, blah... You have been saying this since honeycomb. Don't give up. :thumbup:
[Xoom Android Development] hawkstorm:
While our XOOMs maybe dinosaurs, it still hasn't done us wrong :)

Don't give up just yet... after all, you did manage to get the partition size going.

Keep up the good work!
[Xoom Android Development] drewski_1:
We need a Kernel-meister with a Xoom.

Even Google is behind the times. For KitKat my N7 (2012) is on 3.1 and my N10 is on 3.4
[Xoom Android Development] logitechor:
Thanks for all the effort on the Xoom. It is still my go to device but I know it is old technology. I like ke 4.3 on it from Dream. It works well. If it is in the end the last ROM so be it. Thanks again.
[Xoom Android Development] marmo:
What if we write Motorola to publish the source code for the community?

Crazy idea, too much naive?
[Xoom Android Development] realjumy:
An idea is a responsibility. You have q great idea... So you should begin to write and ask for support ;)
[Xoom Android Development] matt4321:
there is no official source code for 4.2/4.3/4.4 for the xoom from motorola so there is nothing to publish
[Xoom Android Development] LOGMD:
Rom Build Help

:good:Hey Guys almost build 4.4 (have no idea of the outcome like FC etc) keep getting this error though! feeling so close:

Creating filesystem with parameters:
Size: 1006632960
Block size: 4096
Blocks per group: 32768
Inodes per group: 7680
Inode size: 256
Journal blocks: 3840
Label:
Blocks: 245760
Block groups: 8
Reserved block group size: 63
Created filesystem with 1149/61440 inodes and 68320/245760 blocks
Running: mkuserimg.sh -s out/target/product/wingray/system out/target/product/wingray/obj/PACKAGING/systemimage_intermediates/system.img ext4 system 1006632960 out/target/product/wingray/root/file_contexts
Install system fs image: out/target/product/wingray/system.img
out/target/product/wingray/system.img+out/target/product/wingray/obj/PACKAGING/recovery_patch_intermediates/recovery_from_boot.p maxsize=1027707648 blocksize=8448 total=265582346 reserve=10382592
Package target files: out/target/product/wingray/obj/PACKAGING/target_files_intermediates/full_wingray-target_files-eng.logmd.zip
Package OTA: out/target/product/wingray/full_wingray-ota-eng.logmd.zip
unzipping target target-files...
running: unzip -o -q out/target/product/wingray/obj/PACKAGING/target_files_intermediates/full_wingray-target_files-eng.logmd.zip -d /tmp/targetfiles-HxvIMx

NOTE the system.img built! so tonight i will try and flash it... i havnt made the falshable zip yet however! :'(

RESULTS SO FAR:

-System, Kernel etc have built as .img

- i have repartitioned and confirmed with df -h that partitions are bigger.

- when flashing a bigger system.img (258MB) fastboot complains that the image file is bigger than the partition!??
[Xoom Android Development] realjumy:
Done. I hope in a couple of days I will release some useful... I ran out time and I have A LOT to study...
[Xoom Android Development] dreamcwli:
I think fastboot has a pre-defined partition table so even if you are using BigPart kernel in recovery and system you are still unable to flash it through fastboot.

It is still possible to build using original partition layout by removing some unnecessary packages from the build. I have successfully built a flashable zip of Android 4.4 but the EGL compatibility is broken for Tegra 2 devices. Currently I don't have time to fix the problem so just give some findings here.
[Xoom Android Development] LOGMD:
Cheers, I managed to extract the system.img and make a flashable zip I think I've removed a fair bit leaving the system at 258MB. I know that the kernel is going to be a bit of a problem. I got 4.4 system installed but maybe the EGL compatibility could be a reason it doesn't boot

Although when I used the 4.2 boot img I get a response from adb with the 4.4 system but it's unauthorized.. And I think I have not updated permissions properly
[Xoom Android Development] michie:
Contact Timundru (tf101), he is working on kitkat tegra 2 compatibility and is prob facing the same problems. Better bundle forces rather than working individually on the same problem ;)
[Xoom Android Development] LOGMD:
Thanks! i was thinking the same thing, i think we need to start a new team to replace EOS lol
[Xoom Android Development] pots22:
New Team

Very good idea [MENTION=2680726]LOGMD[/MENTION], after the dissolution of EOS it's a long time every people work on her own corner with no correct result for 4.3 4.4

Enjoy your idea :laugh:
[Xoom Android Development] Asphyx:
Replace EOS TEAM? As I see it BRD is the only member left and what he needs is someone like Solarnz who knows Kernels enough to make them work and some source reference to draw from.

And even if we found the best Kernel Guru on the Planet with all the source reference you could ask for...

There is still going to be that point where the Xoom just CAN NOT run the latest/greatest and needs to be retired!

Considering the fact that the Xoom was the PROTOTYPE DEVELOPMENT PLATFORM for Android Tablet I think we should all be very happy we got as much as we have out of it and BRD needs to be thanked an applauded for that in regards to Stingray and the rest of the EOS family of ROMS.

SO Please show some respect!

I'm sure he would welcome any help you guys can give him....But you can never replace his knowledge base of our Unit...NEVER!
[Xoom Android Development] marmo:
Totally agreed. We're here becaouse of them.
[Xoom Android Development] Geeba:
4.4 running on the HD2...

http://www.xda-developers.com/android/kitkat-more-or-less-working-on-legendary-hd2/

2 years older than the Xoom... half the RAM and a slower CPU... the xoom is capable... its whether the right people with the know how still think its a viable option.
[Xoom Android Development] shpitz461:
I don't think the 'oldness' is the issue, but the cpu/gpu platform. Looks like the HD2 is running a snapdragon with Adreno 200, our XOOM is running Tegra 2.

Are you aware of any Tegra 2 devices running KitKat?
[Xoom Android Development] realjumy:
Quick update:

Hi folks.

I write to let you know that some tools for making BP easier are coming, BUT as I'm in my exams period, you will need to wait.

In the meantime, please, let's keep this thread clean and tidy, and let's avoid offtopics. This thread was created with the intention of researching and improve the partition structure of our Xoom to allow the improvement of the roms (specially from 4.2 and beyond). A first and very valid approach has been made, and with all this the doors are open to 4.4 if the other issues (Tegra, etc.) are solved.

Anyway, a lot of further research must be done (we played with the kernel but we need something better), so you are kindly invited to keep on trying new things. I gave too much time to this last month and now the exams are coming like a herd of raging bulls...

Sorry for the delay.

Thanks.
[Xoom Android Development] logitechor:
Good Luck on your exams. May you ace them all.
[Xoom Android Development] pots22:
26/11/2013

One question,

Team EOS is finish, So what this update in GOO im from the 26/11/2013 for stingray-wingray-umts-everest ?
[Xoom Android Development] shpitz461:
looks at the filename, it is from June... the file-date is newer probably because of the restore goo.im did...
[Xoom Android Development] LOGMD:
No one is disrespecting them? EOS made great roms which i used everyday... I'm simply saying lets get a team together to build 4.4 for this device and get as good as EOS... You dont see the words saying that what EOS did was pointless? what they done was great work!

I think you should show some respect to this community for being so active on getting 4.4 to work... rather then complaining at developers who are trying to build the next gen of xoom roms!

The reason im working on this is because of the lower memory requirements on the xoom and im learnng to develop roms, its not about retiring its about not giving up or hating on other teams! ;)

I'm not done with the Xoom yet and neither are many other people... whether its getting 4.4 working or bulding new features on 4.2 and making it faster and more efficient... my tablet still lasts 2 days outlasting an iPad we can breathe life into this tablet ;)
[Xoom Android Development] notbrodie:
remember that last two builds that EOS pushed didn't boot on Xoom. either goo is messing up, or BRD pushed the last stable build to Goo to stem the tide of people downloading borked builds
[Xoom Android Development] Asphyx:
I meant no disrespect to you either there LOGMD....

But the issue with making ROMS better these days all stem from the ancient Kernel not the Rom code!

I have no doubt someone will get 4.4 working for Xoom...How stable it will be is the only question there. And the reason why we can't just run an AOSP build of the newest flavors is all about the Kernel.

The Partition space issue has been solved....Solve the Kernel issues and you might even be able to run Android 5.0 whenever it hits the SDK!

I bet if you fixed the Kernel the EGL issues would go away!
[Xoom Android Development] SgtTeabag:
I know i won't part with my Xoom until its dead or I am :) .
[Xoom Android Development] Alxoom33:
OK, so someone contact Ktoonez

---------- Post added at 01:22 PM ---------- Previous post was at 01:20 PM ----------

Yeah, last stable EOS 4 build was 203. 205 was uploaded later.
[Xoom Android Development] LOGMD:
Glad we cleared that up ;) yeah that kernel is holding us back! Ive been reading into Linux kernels so I'm gonna test on devices I know work I have the nexus 5