Database Develop

Dell Streak 2.2.2 update with FULL ROOT - Flashable via ClockworkMod..

I have taken the liberty of packing up the official update with Root access. Initially it will be available via PM only, after a few users have tested and verify that it works for them as well, I will release the link publicly.
I have removed a lot of the T-Mobile/Dell pre-installed junk. Also, I replaced the boot logo with a Blue Honeybee, if you don't like it I can provide an update.zip that will restore the Dell/T-Mobile logo.
MD5SUM (please verify before flashing, also make a Nandroid backup) - 971426ED95EA7CD564714EE5A29E61A1
Should be fixed now, uploading to my server, the link is the same as before - note the new MD5SUM. I left out a closing parenthesis in the updater-script, my apologies to everyone who already downloaded it. I will post a new post when the upload is complete, thanks for working with me on this.
Hope this helps some people out.
Alright, it would appear that I have this ready to go. So, without further ado, here is your link. If anyone (please) would like to mirror it for me, give a link and I will add it here as well.
By clicking here you acknowledge that you understand the risks you are taking flashing an update package from someone you do not know or trust (that would be me). If anything happens to your device, I'll try my best to help via PM or Email, but I take no responsibility. Only you are truly responsible for what you do to your property, ok... Here you go.

i would be happy to test it out.
i have not yet updated due to many bricks after yesterdays update...so instead i waited for this..i knew it would come...i wasnt gonna ruin my root and CWR for a meazly update such as this...now for GB or HC i might have tried...but anyways happy to test let me know how i can get it from you...im waiting on my device to charge now...soon as its done ill boot CWR and give it a go if you provide the file

Pm sent
sent from my Tbolt.

atrocityg1 said:
i have not yet updated due to many bricks after yesterdays update...so instead i waited for this..i knew it would come...i wasnt gonna ruin my root and CWR for a meazly update such as this...now for GB or HC i might have tried...but anyways happy to test let me know how i can get it from you...im waiting on my device to charge now...soon as its done ill boot CWR and give it a go if you provide the file
Click to expand...
Click to collapse
Hellzya said:
Pm sent
sent from my Tbolt.
Click to expand...
Click to collapse
PM's have been sent, please update me with the results and hopefully I can make this public.

ok tablet chargin will fire it up in a bit to give it a go
so just to be straight, the deal is, boot into clock work...and flash rom from zip on sd card correct? just making sure i got my steps right...do i gotta wipe or anything? i want this to go as smoothly as i can for everyone

atrocityg1 said:
so just to be straight, the deal is, boot into clock work...and flash rom from zip on sd card correct? just making sure i got my steps right...do i gotta wipe or anything? i want this to go as smoothly as i can for everyone
Click to expand...
Click to collapse
Ok, the deal is this...
Boot into recovery
NANDROID BACKUP - DO NOT SKIP!!!!!!!!!
Flash rom from zip
Reboot
Test for Superuser rights.
No wipe should be needed.
And just to be 100% on this, do not do this if you are the least bit concerned about something going wrong. Also, you should have a good working knowledge of Android and willingness to troubleshoot it. The Nandroid backup is your safety net, as this update.zip will NOT remove ClockworkMod recovery - meaning you can roll back to your backup if it is not to your liking). If you flash this and boot up and find you don't have root, you can either restore your backup, or seek some personal help from me. However, it is my birthday and I will be pretty busy today.

ohh not really concerned, i still have one day remaining to take this device back to tmo and if not i can call dell, make my wife cry at em a bit...ill get a new tablet...i work IT...when something breaks, i make it my personal duty to try to get the manufacturer to cover the expense. if not thats on me...i trusted the update. anyhow i thank you for this daveid, and i will let you know as soon as this light turns green. thanks agian. happy birthday...your generous on your b-day providing something usful to others in the community...i like that.

atrocityg1 said:
ohh not really concerned, i still have one day remaining to take this device back to tmo and if not i can call dell, make my wife cry at em a bit...ill get a new tablet...i work IT...when something breaks, i make it my personal duty to try to get the manufacturer to cover the expense. if not thats on me...i trusted the update. anyhow i thank you for this daveid, and i will let you know as soon as this light turns green. thanks agian. happy birthday...your generous on your b-day providing something usful to others in the community...i like that.
Click to expand...
Click to collapse
It's all about the community. Once the update was decrypted, I was all over it.
Besides, I wanted to update my tablet too (the process will help me decide if I want to keep the thing or not).

i hear you, if i didnt own a g1 and mytouch 3g prior to this...i would have NEVER rooted this thing, and in doing so i would have never kept it. that g1 really opened up my eyes for possibilites to come on android, so i stuck with. the reason i asked for your full set of instructions is because i recall some roms being flashed with wipe and some not...i just want my experience to be great when i let the public know that you sir ARE THE MAN!

Pm sent sire!
Sent from my HTC Glacier using Tapatalk

Any word on if this works?
sent from my Tbolt.

Hellzya said:
Any word on if this works?
sent from my Tbolt.
Click to expand...
Click to collapse
No responses yet, don't think anyone has flashed yet.

ok here goes nothin...everyone pucker up for the moment of truth...
so i am backing up now as we speak...i was gonna do two posts...but we will make it one..
so...
backup complete...
mounting sd to load update onto it....stand by.....
copying.....complete
unmounting....done
install zip from sdcard...choose zip......
E: error in /sdcard/lg7_336_0_33_FULL_ROOT.zip
(STATUS 6)
installation aborted
tried twice

everything still works ok but update failed
so my phone boots fine...no problems...but the update did fail as stated in my last post...im awaitng instructions as we speak for further testing i am also searching what error 6 means

atrocityg1 said:
so i am backing up now as we speak...i was gonna do two posts...but we will make it one..
so...
backup complete...
mounting sd to load update onto it....stand by.....
copying.....complete
unmounting....done
install zip from sdcard...choose zip......
E: error in /sdcard/lg7_336_0_33_FULL_ROOT.zip
(STATUS 6)
installation aborted
tried twice
Click to expand...
Click to collapse
You have Clockworkmod recovery right? Did you verify the MD5Sum?
I am out doing birthday stuff now, but can be of more assistance later.
Might have a typo in my updater script, will check when I get home, sorry.

i did verify the md5 sum with fast sum...same md5 as the one you gave...still a noo goo...and yes i have clockwork...that is how i performed the steps in my previous post...i almost typed out the actual options word for word...but its still pretty close

no problem i do remember reading about it being an updater script error. let me know what you get...im going to lunch...gotta test my belly...then ill be back to test your greatness in progress

atrocityg1 said:
no problem i do remember reading about it being an updater script error. let me know what you get...im going to lunch...gotta test my belly...then ill be back to test your greatness in progress
Click to expand...
Click to collapse
Probably a typo I the line I had to add for su. When I get home I will check it and hopefully send an update out.
Found a typo, uploading new version now. Will post when it is up, please re-download... sorry everyone.

Ok, the new (hopefully fixed) update.zip is on my server, the link is the same as before, the MD5SUM is now - 971426ED95EA7CD564714EE5A29E61A1.

Will test when i get home
sent from my Tbolt.

[XT860 and ?me863?]Custom Roms(w/flashable data fix)

Looks like custom roms might finally be here for the xt860 (and possibly me863, read Update4 below for more info). Thanks to Hashcode for all the work he's done for all of us building safestrap, porting cm7 and everything, daywalker04 for uploading the Brazil Retail sbf, Endroid for being the first to try it with a normal bootstrap and now I'm confirming it working with Hashcodes newest safestrap(as well as his old ones, I originally tested w/v0.92 and worked my way up to current). I Just booted cm7 off /preinstall.
As usualy, please keep in mind that neither I or anyone else will take any responsibility for anything that happens to your phone through use of these files.
IF/When you enable and disable safestrap remember to format data/cache, causes bootlooping for me if I don't.
Warning, if you do this the way things are now you will not be able to get back to your bell software!! Only do this is you are absolutely sure you know what you're doing!!!!!!!!
You may have to be on the brazillian retail rom for this to work! You can find it in This Thread. You're looking for Fastboot package for UMTS XT860 Retail Brasil. At this point in time you can't get back to bell stock so again, it's at you're own risk!!
UPDATE: Thanks Rick2 for the recovery fix that allows us to swap between safestrap on the fly. Now when I need data I can get it anywhere. Works with Hashcodes newest safestrap (1.06). Go here to thank him and get the patch!
Update2: I've attached a CWM flashable zip that I've used to successfully get 3g working on Liberty and Mavs Rom, it does not work on cm7 but will hopefully work on other verizon based roms. It pushes the stock libmoto_ril.so(from the brazil retail), a new apns-xml.conf and a slightly edited build.prop(just made it en/US). I've had it cause the phone to fc loop if I installed it on an existing rom and didn't factory reset.
Update3: Watching this thread for info about me863 I think but according to that thread a user has flashed the brazil retail to his me863 and is trying to get data working
Update4: I've reworked the data patch to make it more universal. It should work on me863 providing safestrap runs on your phone. The patch will now copy files from /systemorig so you'll be using matching kernel/libs etc rather than using generic xt860 files. It also makes backups of the original files in the same location (just adds a .bak extension). This new patch IS SAFESTRAP ONLY. Huge huge thanks to Adamogle!!! If it weren't for him I'd still be banging my head up against the wall and no one would be using this patch. You may have to format data/cache, I left it out of the patch so everyone can test (if you phone goes into a force-crash loop then reboot and clear data/cache). Once I get confirmation of this working (or not) on the me863 I'll fix the thread again. I've left the old data patch(renamed as fit) as well in case anyone runs into troubles. Still not a cm7/9 patch, if one comes about it will get it's own thread but it works on all other custom roms based on motorola firmware.
if you see this and you're like "yes, finally some progress on the xt860!! Where do I donate???!?!!" You do that on Hashcodes website, it's ALL his hard work, I just basically wrote you a little story and pooled some files together. He really deserves it, he's working around the clock right now on cm9, seriously around the clock. Of course you can feel free to click the "Thank" button on this post if you like using my data patch
1./ Flash Brazil retail sbf from this thread
2./ root with Zerg from this thread. For some reason v3 kept tossing errors, v2 worked first try.
3./ install safestrap or whatever bootstrap (safestrap from Hashcodes site http://hash-of-codes.blogspot.com/
4./ profit (follow the directions to install a safestrap rom
boot recovery
Enable safestrap in options
Factory reset (formats data & cache)
Mounts > format system
Install your rom
Install my 3gfix
Reboot and profit
)
Again, my patch doesn't work on cm7 at the moment. Sorry Hashcode and everyone but I figured we'd be better off shooting for a known working rom. I'll update the post as I and other users test more roms. Thx thing on a spring for providing the patch "template", every time I threw one together and put it on my phone it turned out to be corrupt somehow so I just removed the files from your data fix and shoved in my own.

does it work with me863?

Thanks Willis I'll try that fix tonight. I'll try some of the other custom roms too see if any work. Probably give safestrap a whirl too
Beamed by invisible waves from my rooted xt860

I gotta say after months of watching customs roms and dev for the xt862 this is pretty exciting. Does wifi data work on cm7? I would assume if the issue is just with apn. I know its not the intended purpose but I may use safestrap as a dual boot, run custom roms at home in safe mode and switch back to Brazil retail when I need 3g
Beamed by invisible waves from my rooted xt860

This is awesome.
Great work guys. As soon as this gets a little more stable I'm going to flash it onto my gf's phone, work around these bugs that came in the stock FW.

Awesome. Been looking forward to this day. Not jumping on the train just yet, but I'm sure that once the 3G bug is ironed out, I'll be flashing.

emprize said:
does it work with me863?
Click to expand...
Click to collapse
Try it out, you can always sbf back to stock if it doesn't work.
Endoroid said:
I gotta say after months of watching customs roms and dev for the xt862 this is pretty exciting. Does wifi data work on cm7? I would assume if the issue is just with apn. I know its not the intended purpose but I may use safestrap as a dual boot, run custom roms at home in safe mode and switch back to Brazil retail when I need 3g
Beamed by invisible waves from my rooted xt860
Click to expand...
Click to collapse
Wifi works, I'm pretty sure it is an apn issue. Think I need to find my old framework-res.

From the bell rom? I have that at home if you need
Beamed by invisible waves from my rooted xt860

Did you try this http://forum.xda-developers.com/showthread.php?p=19981520
Beamed by invisible waves from my rooted xt860

Endoroid said:
Did you try this http://forum.xda-developers.com/showthread.php?p=19981520
Beamed by invisible waves from my rooted xt860
Click to expand...
Click to collapse
Yeah, I tried that and the gsm data patch. I'm having trouble adding/editing apns etc, can't join networks because "Your SIM card does not allow a connection to this network" etc. This is with cm7 and liberty. I have liberty on my safestrap now, running. I can get sms, make calls etc, wifi works. I'll firgure the rest out. If I want to go back to stock for data or something I just turn safestrap off and do an advanced restore of my /data partition to my backup from after installing the brazil retail.

I can't seem to make this work willis, i adb pushed those files to /preinstall but i still get constant FC of com.android.phone the only thing that makes it not do that is removing the sim. i'm confused

Endoroid said:
I can't seem to make this work willis, i adb pushed those files to /preinstall but i still get constant FC of com.android.phone the only thing that makes it not do that is removing the sim. i'm confused
Click to expand...
Click to collapse
I was gonna put together a flashable patch earlier but had some things come up and ended up in a hospital waiting room all night(next time I'll bring my laptop >.<). I'll toss it together asap and update the first post as long as I can flash it/it works. I should have mentioned (this is the confusing part) I pushed those files before enabling safestrap so /preinstall was /system if you get what I mean.

For CM7 to work correctly on GSM, I need to edit the init.mapphone_umts.rc file to setup all of the services the right way.
TBH, I never even looked twice at that file because I thought there wasn't anyone using it.
*blush*
Glad to see the XT860 crowd finally get some fun. )

Thanks Hashcode for putting so much effort into it, it's highly appreciated.
We were feeling a little bit left out.

Well, if you can get a version of CM7 working before I start having to study for exams, would be greatly appreciated.
But, if not, I'm sure I'll just divert time from studying to testing.
Sent from my Nexus S using xda premium

Accophox said:
Well, if you can get a version of CM7 working before I start having to study for exams, would be greatly appreciated.
But, if not, I'm sure I'll just divert time from studying to testing.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Changing your phone's firmware before exams is a bad thing... Trust me, I know Mine are starting next week!

Willis, I wondered if such was the case, I had safe system enabled and tried adb push to both /preinstall and /system as I wasn't sure how adb would recognize them in safe system. I also was pushing while in recovery
Beamed by invisible waves from my rooted xt860

danifunker said:
Changing your phone's firmware before exams is a bad thing... Trust me, I know Mine are starting next week!
Click to expand...
Click to collapse
Which is why I have a trusty nexus s
Sent from my Nexus S using xda premium

Hashcode said:
For CM7 to work correctly on GSM, I need to edit the init.mapphone_umts.rc file to setup all of the services the right way.
TBH, I never even looked twice at that file because I thought there wasn't anyone using it.
*blush*
Glad to see the XT860 crowd finally get some fun. )
Click to expand...
Click to collapse
After the little bit of testing I've done over the last day or two with different custom roms it looks like we're(xt860 and me863 users I image) going to have to have (or really really want) a patch we can flash against any custom rom to get our data and sometimes maybe phone up(or to keep it from crashing). Haven't been able to get 3g up (though the 1 method I did not try was to crash the phone through the dev tools in cm7 as was mentioned in another thread) on any rom yet. Phone/text works right off the bat w/liberty, mavs etc etc.

Narrowed down why Safestrap Recovery would only boot if a USB cable was connected on the XT860; it had to do with a line in the init.rc file executed when booting into recovery:
Code:
write /dev/usb_device_mode msc_adb
As well as a line in the postbootrecovery.sh script which accomplishes essentially the same thing, except via an echo command.
Obviously, we could just comment those lines out, but then we're left without adb in recovery without messy changes each time we want it. So, I whipped up a little script that checks if there is a USB connection and if so, run the previous necessary commands to enable adb and if not, then leave them out. End result: Safestrap Recovery is working like a charm now. No more need to worry about tinkering with my phone without a computer nearby to get into the recovery...
I attached the modified recovery.zip, just replace the original one located at /system/etc/safestrap/recovery.zip with the attached one and you should be good to go.

[WIP] Building CM 10.1

Granted, it has been a while since I've built CM, and never ported it to a new device, but figure this might give some smarter people a head start or at least provide a place for others to collaborate.
I've not gotten very far past the initial vendor setup per http://wiki.cyanogenmod.org/w/Doc:_porting_intro.
A lot of the work is based off the similar ASUS TF700T, https://github.com/CyanogenMod/android_device_asus_tf700t.
I've not messed with the kernel at all at this point, https://github.com/ouya/ouya_1_1-kernel.
I've uploaded everything so far to github, https://github.com/vinny75/android_device_ouya_ouya_1_1

Packages included with official build:
OUYA Framework, Launcher, and Store
Code:
app\OUYAKeyboard.apk
app\OUYALauncher.apk
app\OUYAOOBE.apk
app\OUYAWallpaper.apk
app\ouya-framework.apk
note: some media files I haven't list
CWiid for Android: http://cvpcs.org/projects/android/cwiid4android and https://github.com/cvpcs/android_external_cwiid[.
Code:
bin\wminput
lib\libcwiid.so
etc\acc_led
etc\acc_ptr
etc\buttons
etc\gamepad
etc\ir_ptr
etc\neverball
etc\nunchuk_acc_ptr
etc\nunchuk_stick2btn
Sixpair for PS3 controllers http://www.blog.kaiserapps.com/2012/10/setting-up-sixaxis-controller-android.html.
Code:
/bin/ps3service
/bin/sixpair

I noticed that the recovery.fstab committed is from the Ouya stock recovery partition. When getting cwm to work properly with the internal sdcard, we ended up having to change the sdcard line.
I made the change and submitted a pull request.
Edit: I saw you merged the change.
Sent from my Nexus 7 using xda premium

mybook4 said:
I noticed that the recovery.fstab committed is from the Ouya stock recovery partition. When getting cwm to work properly with the internal sdcard, we ended up having to change the sdcard line.
I made the change and submitted a pull request.
Edit: I saw you merged the change.
Click to expand...
Click to collapse
Thanks, appreciate the help, hopefully, we'll have a working build soonish

If you need any help with kernel debugging/boot issues, I'll be happy to offer up the assistance of my bus pirate.
I was looking at building CM also, but there was always that step in every tut I looked at for "how to port CM to a new device" that basically said "select your device from the build tree"... well if it was in the device tree it wouldn't really be a "new" device then would it!
Also you may want to look at building 10 instead of 10.1, might have less kernel issues as its 4.1.2 jb... at least so we can get some alternative rom working then go for 10.1 after that.
Good luck!

Vinny75,
What method did you use to create the files?
"Method 1: Use mkvendor.sh to generate skeleton files"
"Method 2: Fork a similar device's git repository"
or "Method 3: create the directories and files manually"

mybook4 said:
Vinny75,
What method did you use to create the files?
"Method 1: Use mkvendor.sh to generate skeleton files"
"Method 2: Fork a similar device's git repository"
or "Method 3: create the directories and files manually"
Click to expand...
Click to collapse
I started out with Method 1 then moved over files and settings from the ASUS TF700T.

professorpoptart said:
If you need any help with kernel debugging/boot issues, I'll be happy to offer up the assistance of my bus pirate.
I was looking at building CM also, but there was always that step in every tut I looked at for "how to port CM to a new device" that basically said "select your device from the build tree"... well if it was in the device tree it wouldn't really be a "new" device then would it!
Also you may want to look at building 10 instead of 10.1, might have less kernel issues as its 4.1.2 jb... at least so we can get some alternative rom working then go for 10.1 after that.
Good luck!
Click to expand...
Click to collapse
Yes, building the new device tree has been... uhm... educational... and I am still learning. If I don't make any headway on 10.1, I might drop back to 10 - at least most of the legwork will be done.

Ok, so I'm in the middle of a build
Have a vendor tree on my git and I forked Vinny75's device tree, modified it some
Also a kernel tree up there, which is required for my device tree (prefer to build the kernel myself =) I've booted a custom-built kernel on it already, so that shouldn't be an issue)
I'm nervous to flash this though. I did a bit of searching but couldn't come up with a way to get back into recovery should this thing not boot. You guys know of anything?

Other than using adb to reboot to recovery, http://forums.ouya.tv/discussion/1380/recovery-mode is all I've seen so far to force into recovery mode.
Sent from my Nexus 7 using xda premium

mybook4 said:
Other than using adb to reboot to recovery, http://forums.ouya.tv/discussion/1380/recovery-mode is all I've seen so far to force into recovery mode.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Yea, that's what I'm seeing.
So here's my 'solution'
Since we have fastboot, we can boot a boot.img without having to worry about flashing it.
I've successfully booted my cm boot.img, with ro.secure=0 and ro.adb.secure=0, I can adb reboot it when it fails miserably to boot
Quick and dirty script to unsecure a boot.img:
http://pastie.org/8033076
It assume that unpackbootimg and mkbootimg are in your path, you can get them here: http://invisiblek.org/mkbootfs_tools.zip
Getting closer...

THere's a keyboard solution in the Ouya Questions forum in the thread, [Q] Is My Ouya Dead?

dibblebill said:
THere's a keyboard solution in the Ouya Questions forum in the thread, [Q] Is My Ouya Dead?
Click to expand...
Click to collapse
Yeah, I think that is the same solution posted earlier:
mybook4 said:
Other than using adb to reboot to recovery, http://forums.ouya.tv/discussion/1380/recovery-mode is all I've seen so far to force into recovery mode.
Click to expand...
Click to collapse
THis might be another option too:
tylerwhall said:
I started looking into bootloader-level recovery tonight before messing with the file system too much and potentially getting into a bad state. I couldn't find this information anywhere else.
Bootloader strap
On the back of the board in the center, there is an unpopulated button (U33). When jumped while the power button is pressed, this appears to put the bootloader into USB recovery mode. It enumerates with an nvidia vendor id. Presumably nvflash or tegrarcm could be used to unbrick the device.
I haven't done anything with the bootloader recovery since I haven't yet made a backup. I'm not sure how much of the functionality is allowed given the state of the production fuse, but I would think we could use this to at least get back to a stock state.
Click to expand...
Click to collapse

Some NVidia devices lock access out at the nvflash level unless you've got the manufacturer's key. I believe you get locked out with a 0x4 (nvflash's way of saying "go away").
Using fastboot is probably the quickest, easiest, and safest way to test new kernels.
Sent from my SCH-I535 using xda premium

mybook4 said:
Some NVidia devices lock access out at the nvflash level unless you've got the manufacturer's key. I believe you get locked out with a 0x4 (nvflash's way of saying "go away").
Using fastboot is probably the quickest, easiest, and safest way to test new kernels.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
ah he makes it sound like it puts you in USB recovery mode fo you could ADB in to push an update.

Just wanted to say I'm totally stoked on this guys! Can't wait to see what you do with this. Wish I could help, but I'm really not a developer.

i agree with rebel! but when you guys have it readyish ill test flash it and tell you what happens!!

So, OUYA isn't really as interested in being an open console as they suggest.
I'm keeping a track of how many requests we get relating custom firmware, and from what I'm seeing the user base is not as interested in custom firmware as you might think, which is echoed by this thread (we've shipped 60,000+ units, and less than 10 people have commented in the last month in this thread about getting access to recovery mode).
That doesn't mean that we're shooting the idea down, you need to keep in mind that in terms of priorities this is way down the list as you'd expect from any feature where it's being requested by less than one tenth of one percent of the user-base.
I'm sure @Wajeemba is familiar with CM requests that a very small minority of the user-base are very passionate about, so hopefully you can understand why we're not rushing to work on this.
Click to expand...
Click to collapse
Go to this thread and let them know we want support:
http://forums.ouya.tv/discussion/1380/recovery-mode

That's not even slightly surprising. If every user demanded CM10 they still wouldn't comply, because then they'd lose their one means of profit (ouya store), the fact that "nobody is asking for it" is their excuse, and they'll think of another one if that ever changes.
This is why we just need to proceed without them. I'm on week two of who knows how many weeks away from home on work, so my efforts at porting CM have been put on hold. Have you been able to make any progress? I'd totally loan my Ouya to Fattire or Dalingrin, or another whiz porter if they'd be willing to work on it...

sonofskywalker3 said:
That's not even slightly surprising. If every user demanded CM10 they still wouldn't comply, because then they'd lose their one means of profit (ouya store), the fact that "nobody is asking for it" is their excuse, and they'll think of another one if that ever changes.
This is why we just need to proceed without them. I'm on week two of who knows how many weeks away from home on work, so my efforts at porting CM have been put on hold. Have you been able to make any progress? I'd totally loan my Ouya to Fattire or Dalingrin, or another whiz porter if they'd be willing to work on it...
Click to expand...
Click to collapse
I'd check with invisiblek about how to avoid bricking the OUYA. Apparently his is bricked. It's stuck in nvflash mode. I think it was a kernel written with a bad init.rc that did it. not sure though.
Sent from my Nexus 7 using xda premium

CM10.1 for the HTC Vivid/Holiday/Raider

This is my first Rom port/compile attempt.
Please be patient with me.
As with all other roms on XDA, I am not liable for bricked devices. Hopefully, I can get some real devs to help me get this working.
The port is from a stable build of the CM10.1 Rom for the HTC Sensation.
If a Dev sees this, just know that I will give full credit where it is due.
[UPDATE]Link down till major issues pointed out are fixed[/UPDATE]

Mihir1997 said:
This is my first Rom port/compile attempt.
Please be patient with me.
As with all other roms on XDA, I am not liable for bricked devices. Hopefully, I can get some real devs to help me get this working.
The port is from a stable build of the CM10.1 Rom for the HTC Sensation.
If a Dev sees this, just know that I will give full credit where it is due.
CM10.1_Holiday_Port_v1.zip
Click to expand...
Click to collapse
Link broken...
Updater script is bad... May I ask how you ported this? Like what steps did you take?

Just going to warn everyone reading this right now: as is, the .zip installer in the OP is broken and will not flash WHICH IS A VERY GOOD THING BECAUSE THE MOUNT POINTS IN THE UPDATER SCRIPT ARE ALL ALIGNED TO THE SENSATION'S PARTITION TABLE. You know how it's common knowledge not to flash something designed for one device onto another device? The reason why doing that can brick your device is because THE PARTITION MOUNT POINTS ARE DIFFERENT. The updater script in the OP's ROM flashes /system to the boot partition of the Vivid and it flashes the boot.img to the mmcblk0p20 partition; the boot partition for the Vivid is mmcblk0p22. I'm not sure what function the mmcblk0p20 partition serves on the Vivid, so flashing this ROM on your device could very well brick it. DON'T FIX THE ROM ZIP FILE AND FLASH IT! YOU HAVE BEEN WARNED!

android1234567 said:
Just going to warn everyone reading this right now: as is, the .zip installer in the OP is broken and will not flash WHICH IS A VERY GOOD THING BECAUSE THE MOUNT POINTS IN THE UPDATER-SCRIPT ARE ALL ALIGNED TO THE SENSATION'S PARTITION TABLE. You know how it's common knowledge not to flash something designed for one device onto another device? The reason why doing that can brick your device is because THE PARTITION MOUNT POINTS ARE DIFFERENT. The updater-script in the OP's ROM flashes /system to the boot partition of the Vivid and it flashes the boot.img to the mmcblk0p20 partition; the boot partition for the Vivid is mmcblk0p22. I'm not sure what function the mmcblk0p20 partition serves on the Vivid, so flashing this ROM on your device could very well brick it. DON'T FIX THE ROM ZIP FILE AND FLASH IT! YOU HAVE BEEN WARNED!
Click to expand...
Click to collapse
somebody get a mod to remove both of his ports links before someone actually bricks

ZeRo2o9 said:
somebody get a mod to remove both of his ports links before someone actually bricks
Click to expand...
Click to collapse
The OP's MIUI .zip file has the correct mount points in the updater-script but even if the OP ported vold and all that other stuff correctly there's no way in hell it's going to boot because it's uses the Sensation's boot.img, AKA it uses the Sensation's kernel and ramdisk. The MIUI .zip the OP made also won't flash because the directories inside aren't where they're supposed to be.
EDIT: The MIUI .zip might use a boot.img designed for the Vivid but the CM10.1 .zip file definitely uses the Sensation's boot.img (I just booted the boot.img up on my Sensation).

android1234567 said:
The OP's MIUI .zip file has the correct mount points in the updater-script but even if the OP ported vold and all that other stuff correctly there's no way in hell it's going to boot because it's uses the Sensation's boot.img, AKA it uses the Sensation's kernel and ramdisk. The MIUI .zip the OP made also won't flash because the directories inside aren't where they're supposed to be.
EDIT: The MIUI .zip might use a boot.img designed for the Vivid but the CM10.1 .zip file definitely uses the Sensation's boot.img (I just booted the boot.img up on my Sensation).
Click to expand...
Click to collapse
I kind of guessed that already that was why I was asking for him to post all info and source. He must not have followed porting correctly you need to use your base kernel and create modifications from there I know I did it myself

ZeRo2o9 said:
I kind of guessed that already that was why I was asking for him to post all info and source. He must not have followed porting correctly you need to use your base kernel and create modifications from there I know I did it myself
Click to expand...
Click to collapse
Yeah. The Linux kernel is covered under the GPL so whenever it is publicly distributed, the compiled binary's source code must be posted as well. Or on XDA if a person posts a ROM that uses a kernel that they did not build then they need to add a link to said kernel's XDA thread or source code.

android1234567 said:
Yeah. The Linux kernel is covered under the GPL so whenever it is publicly distributed, the compiled binary's source code must be posted as well. Or on XDA if a person posts a ROM that uses a kernel that they did not build then they need to add a link to said kernel's XDA thread or source code.
Click to expand...
Click to collapse
as far as his miui goes he could use parts from my port if he needs to might make it easier for him just always give credit to creator/source

Sorry.
ZeRo2o9 said:
as far as his miui goes he could use parts from my port if he needs to might make it easier for him just always give credit to creator/source
Click to expand...
Click to collapse
I am not sure how useful your MIUI Port would be to my little project. I have no idea how the MIUI V4 and V5 files corelate, so I don't know how to interchange them correctly. Thanks for the offer. I will keep it in mind
Believe me, I mean no disrespect or harm to anyone or their phones. Notice I have removed download links.

This post is veeery sketchy I've never heard of this guy and it seems like he doesn't know how to port properly :/. And no screenshots??
Sent from my Vivid 4G using xda premium

Mihir1997 said:
I am not sure how useful your MIUI Port would be to my little project. I have no idea how the MIUI V4 and V5 files corelate, so I don't know how to interchange them correctly. Thanks for the offer. I will keep it in mind
Believe me, I mean no disrespect or harm to anyone or their phones. Notice I have removed download links.
Click to expand...
Click to collapse
the updater script for one is set up right, you can see how the rom flashes and what points, and the boot.img is already edited for miui with the shelld so it starts on boot

ZeRo2o9 said:
the updater script for one is set up right, you can see how the rom flashes and what points, and the boot.img is already edited for miui with the shelld so it starts on boot
Click to expand...
Click to collapse
I see...
so. do i just use your updater script or edit my update points?

ZeRo2o9 said:
the updater script for one is set up right, you can see how the rom flashes and what points, and the boot.img is already edited for miui with the shelld so it starts on boot
Click to expand...
Click to collapse
I tried to flash my MIUI rom, and I noticed a weird type of bootloop. It works fine at first. MIUI logo... then it says optimizing apps. Goes through that. without any hiccups. Then it says starting Apps. Then it goes to the MIUI boot screen (orange MI on black screen.) after that it alternaties between "Starting apps", and the MIUI boot screen.
If someone advises me on how to use Zer0's boot.img and Updater, i think it will work.
UPDATE: I just replaced the boot.img with ZeRo's boot.img from his JB rom, and the issue still persists. Any help would be much appreciated.
Cheers,
Reminder: I am a newbie. this is my first attempt at porting. I realize that my CM10.1 won't work, coz I used a CM10.0 base while porting But I really think, with Zer0's help, I can get MIUI V5 up and running. Zer0, please do PM me if you think you would like to help me get this off the ground.

Try pulling a logcat while it's booting up and bootloops. Think I had this problem before can't remember what it was. You also need the AT&T ext.jar file instead of the sensation one
Sent from my HTC One X using Tapatalk 2

[Q] Anyone still working on these?

I was given a Dell Streak 7 (T-Mobile Branded) by a friend after the tablet would only start booting up in Fastboot mode.
The tablet says:
Code:
[COLOR="Red"]username: cmbuild hostname:QTHBuildPC-17 buildnumber : 14236
build on Jan 6 2011 19:35:54[/COLOR]
Starting Fastboot USB download protocol
I successfully flashed boot_orig.img, recovery_orig.img, and system_orig.img from another post, but I'm still having the same problem.
**EDIT**
I want to make it clear I did try hitting the reset button
giveen said:
Little hole next to SD card, press it with a paper clip
or
Or if you have 'fastboot' program and drivers are installed, at command prompt you would type 'fastboot reboot'
Click to expand...
Click to collapse
I really wanted to install a custom ROM on this thing and let the kids play around with it. I have plenty of experience with TWRP, CyanoMod, ADB, Fastboot, etc...
Anyone have any ideas?

Nobody is working on these anymore. The lack of source and not having an updated kernel to give us anything stable from any jb+ rom...... KK or LP would run much more efficiently on this device but nobody around to try to build kernel or ROM.
Device is old and under powered. Check the threads for instructions how to install back to stock Honeycomb ROM would be your best option at this point.
R.I.P. Streak 7 development

ElfinJNoty said:
Nobody is working on these anymore. The lack of source and not having an updated kernel to give us anything stable from any jb+ rom...... KK or LP would run much more efficiently on this device but nobody around to try to build kernel or ROM.
Device is old and under powered. Check the threads for instructions how to install back to stock Honeycomb ROM would be your best option at this point.
R.I.P. Streak 7 development
Click to expand...
Click to collapse
Thanks for the response.
I bought a couple of these on eBay, all with issues, for me to play around with and possibly, if I get working, to give to the kids to play with. I found another seller on eBay selling otter boxes for $5 and someone on Amazon selling ZAGG screen protectors for $.99.
I was able to boot the one stuck on Fastboot in to APX and try to run the Restore to 2.2.bat from TheManii but it keeps hanging up on various img files. I think I am going to part it out and try fixing another one with a broken charger port.
A second one was stuck on the DELL logo on boot. APG -> Restore to 2.2.bat fixed it up right away. I updated it, and now I'm playing around with CM on it.
Here's hoping I get the third one working by parting out the first. LOL

My sources are still available on github if anyone still wants to take a stab at it. Kernel needs to be brought up to at least a full generation newer (ie 2.6 -> 3.x), and thats just a starting point.

kernels not that bad and i dont think it needs updating myself

http://forum.xda-developers.com/showthread.php?t=3330564