Related
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.
Hey guys,
I finally got 3G data working in Hashcode's port of ICS to the Droid 3/XT860. I'm currently using the isuacell (Mexico) revision on a Bell XT860; I wasn't able to get ICS to boot up on the current Bell update, although I'm sure it's something simple I've overlooked. I'm fairly certain it'll work on other software updates such as the ones from Argentina/Brazil, and possibly the ME863 but I don't have the time to test it myself, let me know if it works for you if you're running any of these updates.
Nevertheless, I got it working pretty easily. I don't have time to do a full writeup right now but it was exactly what I suspected earlier, a minor issue in the Android framework causing an exception that would disconnect 3G data a few seconds after a connection to the APN was successfully made. That, combined with Motorola's RIL library from the isuacell firmware and a few build.prop tweaks were all it took, and so far it is running pretty good.
Only major thing I've noticed so far is that the cell status indicator only seems to indicate either perfect reception or none, no in between, but for now I'm pretty stoked this is working as I can finally use ICS on a daily basis instead of switching back and forth a dozen times a day.
Here's a link to a .zip to be installed via Safestrap. Be sure to perform a factory reset and to be safe, mount system and format it in the "mounts and storage" area before installing the zip to ensure a clean install. Also, as Hashcode had mentioned in his release thread, don't let it restore your old settings when you run through the Setup Wizard on the first boot. Enjoy, and be sure to thank Hashcode for all the effort he's put into making our phones even better!
http://dl.dropbox.com/u/22632665/CM9_XT860.zip
md5=6302b1733777ad5d7e3d5483d9291591
176820984 bytes
---------------------------------------
EDIT: I was lazy earlier and just posted the link to the full update, I finally got around to releasing a significantly smaller, more sensible patch:
http://db.tt/HEbusNM3
xt860_ics_patch_01_30_2012-safe_system-signed.zip
md5=60dc2db347c7310d0f5e51b0e02b9952
4231015 bytes
I recommend flashing Hashcode's Alpha 5 release, then doing a factory reset before installing this update in Safestrap. I can make one for the non-safe system users out there too, just didn't bother but it'd take two seconds.
Also, check out my github repos for the changes I made to get 3G data working. (You'll probably laugh when you see the change to android_frameworks_base):
http://github.com/buddyrich
I've kind of mimicked Hashcode to keep things simple; my changes are in the branch "ics-xt860". The easiest way to compile it all from scratch is like this: (Assuming you're in your working directory)
1) repo init -u git://github.com/CyanogenMod/android.git -b ics
2) cd .repo
3) git clone git://github.com/buddyrich/android_local_solana.git
4) cd android_local_solana
5) git checkout ics-xt860
5) cp local_manifest.xml ../
6) rm -f -r android_local_solana
7) repo sync -j24
8) Place this file in the root of your working directory, eg: ~/android/system/ : http://db.tt/1HpM2m6r
9) vendor/cm/get-prebuilts
10) . build/envsetup.sh
11) brunch solana
nice, it works!
Rick#2 said:
Also, as Hashcode had mentioned in his release thread, don't let it restore your old settings when you run through the Setup Wizard on the first boot.
Click to expand...
Click to collapse
I see this mentioned everywhere, and now I just have to ask. What happens if you do let it restore your old settings?
funny....i got 3G, but i cant make a call nor receive a call......
is that my problem or known problem?
That is strange, I can make and receive calls without any issues. What software/baseband are you using?
albatorsk said:
I see this mentioned everywhere, and now I just have to ask. What happens if you do let it restore your old settings?
Click to expand...
Click to collapse
The world will explode.
No, to be honest I have never tried. I think the idea is that you don't want any settings from a completely different Android release (ie: Gingerbread vs. ICS) being restored. It will still sync up your contacts and everything, just not any wifi connections, system settings, etc.
Rick#2 said:
That is strange, I can make and receive calls without any issues. What software/baseband are you using?
Click to expand...
Click to collapse
kinda strange, i wipe and try now, sometimes clean install but got phone.apk freeze, my latest try is ok....
emprize said:
kinda strange, i wipe and try now, sometimes clean install but got phone.apk freeze, my latest try is ok....
Click to expand...
Click to collapse
Very nice man!! I was actually talking to this with Hashcode a while ago and we figured that the best way to get things working for xt860/me863 might be to release small patches to enable data etc. Is it possible to pop your modified files in a smaller patch that can be applied against the current and future cm9 builds? (With a list of what's modded I think most people can do this pretty easily and the patch should be easier to update than the ~175 meg cm9 zip as well when carriers release newer firmwares with updated libs etc).
I have this running against my bell 2.3.6 cwm rom that I flashed non-safe, only problem I have is that I have to boot the phone plugged into the computer with ICS, Hash has fixed and broke that a few times I think, not the most important thing. I notice with your build I don't need to have my phone plugged in to the computer to boot ics.
Edit: For some reason I have data and "Sim card not detected" in the status bar, everything is populated correctly in phone info, phone works for calling and data. Switching out the included libmoto_ril.so with the one from bell 2.3.6 took care of the "Sim card not detected" up top(srsly, maybe it was just the reboot) but when I try to make a call phone fc's lol.
nice ill try later
Enviado desde mi XT860 usando Tapatalk
goalando said:
nice ill try later
Enviado desde mi XT860 usando Tapatalk
Click to expand...
Click to collapse
It's worth trying now, with libertys dl site going down last night I flashed this knowing I wouldn't have data only to wake up and find that it's my every day rom now. Any hacking etc from this point might as well be done while using/on this (although I would still really like to see data working on cm7 as well personally, perhaps if Rick#2 makes this into a smaller patch we can test it on that as well). Only a few things that are holding us back now like camera/some codec/module issues.
So far so good. Thanks a lot
I'm using the stock Bell 2.3.4 rom and I installed this zip on my safe system enabled mode however it doesnt work. I wish someone could show me how to provide more meaningful logs but this is what I get from dmesg:
http://pastebin.com/jHhTiCC3
a longer dmesg:
http://pastebin.com/k5PMF3r4
and finally heres /proc/kmsg
http://pastebin.com/ygW2Fb4Y
if anyone could look through it and tell me why my xt860 is not booting this build of cm9 that'd be great thanks
Hey Congrats on setting this up Rick#2!
Get me a patch of just the changed files and I'll host it under the builds so that people can download both files at the same time as new updates happen.
You've single-handedly brought ICS to the XT860!
works awesome! i had to add some stuff to the ATT apn for data to work
and camera isnt working, but everything else is AWESOME.
THANK YOU to everyone who helped make this possible
From my xt860
Is anyone else finding that touch events take longer to register?
Sent from my XT862 using xda premium
Very nice man. Thanks
Has anyone tried to send an MMS picture message (on Rogers?) I double checked my apn's. It didn't seem to send. But data is nice!
Sent from my XT860
Edited the first post with a much smaller patch and some more info on what's going on.
Hi!
I put this patch up on the blog as well:
http://hash-of-codes.blogspot.com/p/android-downloads.html
(See XT860 sub-patch)
Rick#2: I can get that frameworks change into my build via a build.prop setting..
ro.ril.ignore.linkiperror=true
(add this to your build.prop and I'll get it in for the next release)
That you don't need to patch frameworks.jar each release.
And I might build in a prop check for disabling the GlobalNWStats trigger which causes a looping FC for non-VZW Droid 3 users. Not sure what to use tho.
Also in your update-script the mount command references:
mount("ext3", "EMMC", "/dev/block/mmcblk1p23", "/system");
That will only work for Safestrap users.
Let's change it to:
mount("ext3", "EMMC", "/dev/block/system", "/system");
Yeah, I was wondering what to do about that. Didn't think I could just use /dev/block/system, nice for compatibility!
Pretty funny how I spent countless hours sifting the radio logs, trying a billion permutations and combinations of proprietary binaries, libraries and build.prop settings when all that needed to be done was to comment out *one* line of code. I had an itch to try getting rid of that bit regarding the exception a few weeks ago but thought it couldn't possibly be that simple...
Rick#2 said:
Yeah, I was wondering what to do about that. Didn't think I could just use /dev/block/system, nice for compatibility!
Pretty funny how I spent countless hours sifting the radio logs, trying a billion permutations and combinations of proprietary binaries, libraries and build.prop settings when all that needed to be done was to comment out *one* line of code. I had an itch to try getting rid of that bit regarding the exception a few weeks ago but thought it couldn't possibly be that simple...
Click to expand...
Click to collapse
I sometimes get asked why development takes so long when they take a look at the commit changes and the code hasn't been edited much at all.
*cough* This is a fine example of just such a case.
I'm sure the entire XT860 community appreciates the hard work.
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
Info:
This is a custom stock rom that is only for sprint devices (Sprint/Vm/Boost). It was made using SuperR's Kitchen. It is rooted and I tried to removed as much as I could. This is just a work in progress so there will probably be more that I will remove and will replace some of the apps with updated and better versions based on user input. Also included for those that wish to make their own rom is an decrypted rooted stock. I have tested these extensively, but as always make a full backup before flashing and do a full wipe just in case. I am not responsible for any damages or loss of data that may occur from flashing these roms.
Apps that have been removed:
system/app/appmanager*
system/app/BasicDream*
system/app/CalculatorWidget*
system/app/Drive*
system/app/DriveActivator*
system/app/Exchange3Google*
system/app/facebook*
system/app/FaceLock*
system/app/FMRadioService*
system/app/Font_Helvetica*
system/app/Font_XinGothic*
system/app/Font_Yuen*
system/app/Gmail2*
system/app/GoogleTTS*
system/app/Hangouts*
system/app/HoloSpiralWallpaper*
system/app/HtcAutoRotateWidget*
system/app/HtcBackgroundDataWidget*
system/app/HTCBackup*
system/app/HtcBackupReset*
system/app/HtcCarGps*
system/app/HTC_Connect*
system/app/HtcGpsWidget*
system/app/HtcHotspotWidget*
system/app/HtcLogLevel*
system/app/HtcMessageProvider*
system/app/HtcPowerStripWidget*
system/app/HtcRingtoneWidget*
system/app/HtcScreenBrightnessWidget*
system/app/HtcScreenTimeoutWidget*
system/app/HtcSyncWidget*
system/app/IMEHWRPenPower*
system/app/IMEMurasuIndic*
system/app/IMEMurasuViet*
system/app/IME_TP_ValueAdd*
system/app/instagram*
system/app/KidMode-google*
system/app/Maps*
system/app/messenger*
system/app/Music2*
system/app/MyHTC*
system/app/News_Republic*
system/app/NewsWeather*
system/app/NoiseField*
system/app/pagesmanager*
system/app/PhaseBeam*
system/app/talkback*
system/app/Videos*
system/app/YouTube*
system/priv-app/DemoFLOPackageInstaller*
system/priv-app/Facebook*
system/priv-app/Frisbee*
system/priv-app/GooglePlusPlugin*
system/priv-app/GSD*
system/priv-app/HTCAdvantage*
system/priv-app/HtcBtWidget*
system/priv-app/HtcCalendarWidgets*
system/priv-app/HtcContactWidgets*
system/priv-app/HtcDataRoamingWidget*
system/priv-app/HtcDataStripWidget*
system/priv-app/HtcDLNAMiddleLayer*
system/priv-app/HtcDMS*
system/priv-app/HtcDotMatrix*
system/priv-app/HtcFileManager*
system/priv-app/HtcHotspotWidget*
system/priv-app/HtcMobileNetworkWidget*
system/priv-app/HtcMusicWidget*
system/priv-app/HtcRingtoneTrimmer*
system/priv-app/HtcSoundRecorder*
system/priv-app/HTCSpeakCyberon*
system/priv-app/HtcWeatherClockWidget*
system/priv-app/HtcWiFiWidget*
system/priv-app/HTCZero*
system/priv-app/iCloudTransfer*
system/priv-app/ID*
system/priv-app/installer*
system/priv-app/Instagram_SN_Plugin*
system/priv-app/LinkedIn_Fsplugin*
system/priv-app/LocationPicker*
system/priv-app/Lookout*
system/priv-app/Lucy*
system/priv-app/Mail*
system/priv-app/MirrorLink_MirrorLinkService*
system/priv-app/Photos*
system/priv-app/PolarisOffice*
system/priv-app/Sprint_Installer*
system/priv-app/Sprint_Sprint_VVM*
system/priv-app/Sprint_Sprint_Zone*
system/priv-app/TetheringGuard*
system/priv-app/Twitter*
system/priv-app/Velvet*
system/priv-app/WallpaperCropper*
system/priv-app/Weather*
De-Bloated MM (Updated: 9-2-16):
https://www.androidfilehost.com/?fid=24588232905724314, https://basketbuild.com/filedl/devs?dev=Nightbreed&dl=Nightbreed/HTC%20626s/Sprint_Stock_MMDB_2.27.651.6.zip (BB down)
Standard Stock MM (Updated: 6-23-16): https://www.androidfilehost.com/?fid=24686679545611466, https://basketbuild.com/filedl/devs?dev=Nightbreed&dl=Nightbreed/HTC%20626s/Sprint_Stock_MM_2.27.651.6.zip (BB down)
Debloated LP(Updated 1/23/16): https://drive.google.com/open?id=0BzHOZHL6ZwXhRWxZNG4zc3lDSWc
Standard Stock LP: https://drive.google.com/open?id=0BzHOZHL6ZwXhX0RoYnpxTUsyZnc
Let me know if there are any problems/request you have I'll try to do my best to fix them as quickly as possible.
I would like to thank @Captain_Throwback for all of his help in making this rom.
*updated links 9-2-16
Nice! I'm downloading now. Thanks for putting in the time. Can't wait to check it out.
thefuryofZ3US said:
Nice! I'm downloading now. Thanks for putting in the time. Can't wait to check it out.
Click to expand...
Click to collapse
Let me know how it goes. I still have some work to do on it. Wasn't really sure what some of the files were. I'll be running more test to see what else I can remove and still have it boot. Wan't to get this as small as possible. If I removed anything that breaks something important let me know. As I said I'm not a dev and this is my first attempt.
No doubt. I have no problem putting it through the wringer. I'll let you know if I find anything, as well as any fixes that may work. I'm stoked to get back to my 626 and get to flashing!
I'll keep an eye on this. Just got the phone in the mail and noticed the extreme amounts of bloatware. Can't wait to root Dx.
Everything seems to be functioning correctly so far. Nice, lite and responsive. Flashed well, maybe 3 minutes total to complete. Boot up took even less. As of this post, no FC's or hangups found.
Solid rom! Thanks again!
Finally a rom for the sprint variants! I'll be giving this a try, downloading now. I hope it solves the low memory problems....
Sinister Drake said:
Finally a rom for the sprint variants! I'll be giving this a try, downloading now. I hope it solves the low memory problems....
Click to expand...
Click to collapse
Removed most of the apps that were causing problems. Have another version that I am currently working on that will have the updates included and a few more apps removed. Only problem is this phone is very hard to make flashable roms for. Most attempts end with a boot loop. Still not giving up though.
A few things I have noticed: first is the HTC Account apk was missing so I couldn't sign in to install themes. I fixed that by downloading it from Google Play and making it a system app using rom toolbox pro.
Secondly I'm not sure if our phone has a magnetometer (compass) I would think it would have one. But it's not working.
Other than those 2 issues, this is a solid rom. Good job man. Keep up the good work.
I'm trying to get viper4Android to work but it keeps telling me my busybox installation is broken which it isn't.
Might wanna see if you can include busybox in future updates. Just a suggestion.
Oops, sorry noob here, got the 626s desire but connected to the bell network. if this is a sprint rom i guess i got to go back to rooted stock? The rom boots but hangs at activation. am i correct?
Unfortunately until someone comes up with a rom for your variant, you'll have to go back to your original rom. I hope you made a backup before you installed this rom.
I have the boost mobile variant and I still can't get twrp to work only Cyan recovery anyone know anything about getting two to work I used captainthrowback
Maybe I should learn how to read better. Is new so started off the bat with nothing on it so no backup I did with it. Worst case is I'm screwed lol.
kindlefire39 said:
Maybe I should learn how to read better. Is new so started off the bat with nothing on it so no backup I did with it. Worst case is I'm screwed lol.
Click to expand...
Click to collapse
You might not be screwed. Try searching the HTC website for an Ruu for your carrier. Once you find it lock your bootloader, then let it run its magic. Should return you back to stock.
@Sinister Drake I removed a lot of HTC stuff as I didn't think most people use it. If I do remove something you really need and can't find let me know and I'll re-add it.
As for busybox it does come pre-installed. Why some apps find it and others do not I can't really say. Doing a busybox check does show it's there.
Now as for the compass that is a issue that worries me. All my research says this phone has one, but it doesn't work even on my recovery. I need to know if it was something that worked on stock or if it was just false reporting by HTC, so I can narrow down the problem. It shouldn't be a problem with my rom as it is taken directly from the RUU, but I cannot be for certain until I get more feedback.
You know I screwed myself and went to quick because I had it rooted with twrp and oh look debloated firmware without paying attention to the Carrier, Doh! You know what silly, I called HTC Canada because bell is a Canadian outfit and they apparently don't supply ruu's like the states does. Oh well my bad 200 smackers later and a new phone. I guess on the bright side I can root it lol. Maybe one of the excellent developers will somehow create a bell version.
New version = https://drive.google.com/open?id=0BzHOZHL6ZwXhRWxZNG4zc3lDSWc Removed an extra 200mb now total over 600mb freed. Also, updated the OP with the list of apps that have been remove. As always if I removed something you want and can't find let me know I will add it back in. Been using this version for a few days and found no errors, but make a backup just in case. Report any error you find I'll do my best to fix them.
Working on updating the apps to free up even more space. After that I'll be replacing some apps with lighter versions. Once I get any significant build I'll post it.
@kindlefire39 hopefully you can find someone else that has this phone in your region to make a backup for you. Once you get that you can easily use suprr kitchen to make a debloated version.
Is it possible to backup my new phone and use super kitchen? Or am I out in left field? I could be the first one with a bell mobility variant.
kindlefire39 said:
Is it possible to backup my new phone and use super kitchen? Or am I out in left field? I could be the first one with a bell mobility variant.
Click to expand...
Click to collapse
Once you flash a rom it overwrites the one you currently have installed. That is why it is good to make a backup before you flash. Out of curiosity have you tried to flash Captain_Throwback's rom? Its for metropcs but if you can get your phone to boot you can call your phone company tell them your phone is on a different carrier and you need the codes for the phone to work on their network. If you do get it to boot some things might not work, like the wifi, but it can get you through until you can get a proper rom/backup. Try posting in the help section asking for someone to make a backup of their phone. Heck even try asking anyone you know that has the same phone if you can borrow it for a bit to fix yours.
nightbreed813 said:
You might not be screwed. Try searching the HTC website for an Ruu for your carrier. Once you find it lock your bootloader, then let it run its magic. Should return you back to stock.
@Sinister Drake I removed a lot of HTC stuff as I didn't think most people use it. If I do remove something you really need and can't find let me know and I'll re-add it.
As for busybox it does come pre-installed. Why some apps find it and others do not I can't really say. Doing a busybox check does show it's there.
Now as for the compass that is a issue that worries me. All my research says this phone has one, but it doesn't work even on my recovery. I need to know if it was something that worked on stock or if it was just false reporting by HTC, so I can narrow down the problem. It shouldn't be a problem with my rom as it is taken directly from the RUU, but I cannot be for certain until I get more feedback.
Click to expand...
Click to collapse
When I installed the rom I did not see Busybox, I installed it from google play. I'm still trying to figure out how to get viper4android to work to no avail. Maybe you can add it as a system app with the rom. With that being said, I've learned that another thing you have to do to get it to work is to use the selinux changer. with a quick google search you can find it elsewhere to download since it is not availble on google play anymore.
I do have to give you props though man, you're doing a fantastic job developing this rom whilst not being a developer. Kudos to you brother.
---------- Post added at 10:15 PM ---------- Previous post was at 10:10 PM ----------
Is it possible that you could provide the apk for the HTC clock widget? I really dig the flip clock style. I can install it myself, I just dont have the apk for it
Sorry what I meant is I got a second phone because HTC Canada couldn't help. I just bit the bullet. So with the new phone can I make a stock backup or through twrp than backup? If I have a stock backup, than I could custom it and delete apps that you did for yours in your list.
Hello! So, I've tried creating a device tree for the Leon LTE (H340n) based on ms345, and after some changes I've compiled TWRP for this specific model, with it identifying as c50n, which should allow for custom ROMs(I'm building LineageOS 13 right now, but don't get your hopes up) Also, there's a way to flash TWRP and get root on 6.0, here's a guide (https://forum.xda-developers.com/showpost.php?p=72501544&postcount=25) and you can flash my recovery instead.
Link: https://www.androidfilehost.com/?fid=961840155545578919
Sources: https://github.com/dadziokPL/android_.repo_local_manifests
Also, this recovery wouldn't work if it wasn't for Charles-IV's help on Github, a huuuuge thanks to him!
dadziokPL said:
Hello! So, I've tried creating a device tree for the Leon LTE (H340n) based on ms345, and after some changes I've compiled TWRP for this specific model, with it identifying as c50n, which should allow for custom ROMs(I'm building LineageOS 13 right now, but don't get your hopes up) Also, there's a way to flash TWRP and get root on 6.0, here's a guide (https://forum.xda-developers.com/showpost.php?p=72501544&postcount=25) and you can flash my recovery instead.
Link: https://www.androidfilehost.com/?fid=961840155545578919
Sources: https://github.com/dadziokPL/android_.repo_local_manifests
Also, this recovery wouldn't work if it wasn't for Charles-IV's help on Github, a huuuuge thanks to him!
Click to expand...
Click to collapse
Hi? The metro pcs version is what model? C50n? Also I found anoth4r version of twrp on 5he site twrp.me.. I saw twrp-3.1.1-0-c50.img... Is this appropriate? I hav the metro version and I'm confused what to use
jazzdglass said:
Hi? The metro pcs version is what model? C50n? Also I found anoth4r version of twrp on 5he site twrp.me.. I saw twrp-3.1.1-0-c50.img... Is this appropriate? I hav the metro version and I'm confused what to use
Click to expand...
Click to collapse
the official twrp one is for all c50 devices, but this one is specifically for the c50n, but im not sure how much of a difference it makes.
You can find out if yours is c50n or not in about phone.
Strange thing is its twrp 3.0.2 , and i cant find anything about this on the internet
Charles IV said:
the official twrp one is for all c50 devices, but this one is specifically for the c50n, but im not sure how much of a difference it makes.
You can find out if yours is c50n or not in about phone.
Strange thing is its twrp 3.0.2 , and i cant find anything about this on the internet
Click to expand...
Click to collapse
The difference is that the c50n did not have a device tree, there was no way to build custom ROMs, so I started working on a tree, and TWRP now compiles with it. It also identifies as c50n inside the recovery when checking compatibility with a ROM, so if I ever manage to get Lineage working, it will flash properly, being meant for THIS specific phone, the LG Leon 4G LTE aka H340n aka C50n. Previous TWRP was for all LG Leons, built on a common tree. With a specific tree, it allows for specific fixes for this device if needed in the future. The version is older since I used TWRP android6.0 branch, I could build an updated version, but right now I'm taking a break.
jazzdglass said:
Hi? The metro pcs version is what model? C50n? Also I found anoth4r version of twrp on 5he site twrp.me.. I saw twrp-3.1.1-0-c50.img... Is this appropriate? I hav the metro version and I'm confused what to use
Click to expand...
Click to collapse
MetroPCS is ms345, I just needed a base for C50n, the international LG Leon 4G LTE. The devices are similiar, so I thought I could use the existing ms345 tree to create a tree for the C50n. I don't know if there is a specific TWRP for the ms345, if there is, you should find it and use it. If not, the C50 from twrp.me should work. Also, my recovery for C50n should work too, just try flashing, if some **** goes sideways, just flash another one and try again. The difference is basically what TWRP thinks your device is, and if you flash a ROM for ms345 it would expect your recovery to be for ms345, and not anything else. Get it?
Hey, I'm from Brazil and I own a H342 model of this cellphone.
I was thinking about installing the v20b marshmallow kdz released for H340 because I'm done with the ***ty, ugly and laggy 5.0.1 build, but I know that even if the processor is the same for both devices the baseband will still differ.
You know how can I install 6.0 and flash the baseband from the H342 after?
Sorry for any concordances errors and thank u for your time
mateus.sc said:
Hey, I'm from Brazil and I own a H342 model of this cellphone.
I was thinking about installing the v20b marshmallow kdz released for H340 because I'm done with the ***ty, ugly and laggy 5.0.1 build, but I know that even if the processor is the same for both devices the baseband will still differ.
You know how can I install 6.0 and flash the baseband from the H342 after?
Sorry for any concordances errors and thank u for your time
Click to expand...
Click to collapse
Sorry about the lateness, but don't do it.
The baseband was built with code specifically for lollipop, flashing it on top of marshmallow will most likely lead to incompatibility.
What about LineageOS?
rusiu559 said:
What about LineageOS?
Click to expand...
Click to collapse
Any news ?
rusiu559 said:
Any news ?
Click to expand...
Click to collapse
None other than it might take a long time. @dadziokPL has a lead on what the current error is though.
Charles IV said:
None other than it might take a long time. @dadziokPL has a lead on what the current error is though.
Click to expand...
Click to collapse
It's all going so terribly wrong tho. I've managed to get it to compile, but it does not boot. Goes to "AP Watchdog bark" green screen, so probably can't even boot into the Linux kernel, since if it did we'd get some boot animation and logcats. I'm totally stuck.
Also, the recovery does not boot anymore, I'm gonna revert some commits up until you merged all the common trees, modular approach is much better
dadziokPL said:
It's all going so terribly wrong tho. I've managed to get it to compile, but it does not boot. Goes to "AP Watchdog bark" green screen, so probably can't even boot into the Linux kernel, since if it did we'd get some boot animation and logcats. I'm totally stuck.
Also, the recovery does not boot anymore, I'm gonna revert some commits up until you merged all the common trees, modular approach is much better
Click to expand...
Click to collapse
Yes, I was worried that I might break something with the merging, but we can re-merge when everything's working to see if it does break things.
The kernel might need to be modified - all I did is went onto lg leon's source code site and downloaded the H340N one. It contained two zips, one with the kernel in, and one supposedly with the rest in, but it was really messed up and I couldn't get it working.
I'll build the kernel in that tree using their instructions (not sure what I'll get!) and we'll see if we can use that as a prebuilt kernel.
Is your bootloader definitely unlocked? I remember getting a greenscreen when I was messing about with the partitions, trying to put the recovery on it etc.
Charles IV said:
Yes, I was worried that I might break something with the merging, but we can re-merge when everything's working to see if it does break things.
The kernel might need to be modified - all I did is went onto lg leon's source code site and downloaded the H340N one. It contained two zips, one with the kernel in, and one supposedly with the rest in, but it was really messed up and I couldn't get it working.
I'll build the kernel in that tree using their instructions (not sure what I'll get!) and we'll see if we can use that as a prebuilt kernel.
Is your bootloader definitely unlocked? I remember getting a greenscreen when I was messing about with the partitions, trying to put the recovery on it etc.
Click to expand...
Click to collapse
Yeah, the bootloader's got to be unlocked since old TWRP boots fine
dadziokPL said:
Yeah, the bootloader's got to be unlocked since old TWRP boots fine
Click to expand...
Click to collapse
I'm trying to figure out a way of how to unmerge, and restore the combined branch it was on - i spent so long on that! -_-
To me it looks like the error is to do with the bootloader rejecting it. Could it me something to do with the system.prop. Fingerprints, maybe?
Charles IV said:
I'm trying to figure out a way of how to unmerge, and restore the combined branch it was on - i spent so long on that! -_-
To me it looks like the error is to do with the bootloader rejecting it. Could it me something to do with the system.prop. Fingerprints, maybe?
Click to expand...
Click to collapse
I have completely no idea what the problem is. I'm gonna hard reset the repo to the last commit before the merge, but we'll lose all commit history after the merge. We'll have to start over from before you merged it all. Why'd you even do it? It was totally fine being modular
dadziokPL said:
I have completely no idea what the problem is. I'm gonna hard reset the repo to the last commit before the merge, but we'll lose all commit history after the merge. We'll have to start over from before you merged it all. Why'd you even do it? It was totally fine being modular
Click to expand...
Click to collapse
Well I'm used to a single device repo, so I tried merging it, to see if it worked. Personally I didn't like having 3 repos to look at, but three of each file is also hard!
Tbh I was surprised when you pulled it, I just did it as an experiment.
Charles IV said:
Well I'm used to a single device repo, so I tried merging it, to see if it worked. Personally I didn't like having 3 repos to look at, but three of each file is also hard!
Tbh I was surprised when you pulled it, I just did it as an experiment.
Click to expand...
Click to collapse
I thought maybe you did something important with the merge and just pulled it, but it seems like it broke it. Anyway, now I know how to revert commits, so I'll be building the recovery, and if it does not work, I'll just revert one commit back and gradually figure out at what point it broke.
dadziokPL said:
I thought maybe you did something important with the merge and just pulled it, but it seems like it broke it. Anyway, now I know how to revert commits, so I'll be building the recovery, and if it does not work, I'll just revert one commit back and gradually figure out at what point it broke.
Click to expand...
Click to collapse
When you've got recovery working, if booting still doesn't work, let me know, I've noticed a minor difference in fingerprints and build description (the same difference) in my build.prop compared to the build prop overrides. It is probably because they are different builds, and shouldn't make a difference, but if it's not working, I'll try it.
On a side note - if we change the overrides, in theory, with suhide, it should pass safetynet!
Charles IV said:
When you've got recovery working, if booting still doesn't work, let me know, I've noticed a minor difference in fingerprints and build description (the same difference) in my build.prop compared to the build prop overrides. It is probably because they are different builds, and shouldn't make a difference, but if it's not working, I'll try it.
On a side note - if we change the overrides, in theory, with suhide, it should pass safetynet!
Click to expand...
Click to collapse
Okay, so the merge must have screwed something up, since recovery works perfect now! I'll be back to building now. Also, I'm not building Lineage anymore, I switched over to RessurectionRemix, it's totally awesome.
Edit: You know what. I'm actually going to build the kernel itself for now and see if it works, since I'm on a CM12.1 ROM for ms345, it works but is quite bugged. I'll do an experiment and try to flash the kernel I'll build. Probably won't work, but I'll see what will happen
Edit 2: Okay, green screen again, I'll try to build the full ROM again, if that happens again, that is bad news, since I have no idea how to fix this thing.
Just another edit: I have an idea. I just downloaded the Qualcomm QPST tool, I might be able to debug this. No promises tho, we'll see.
dadziokPL said:
Okay, so the merge must have screwed something up, since recovery works perfect now! I'll be back to building now. Also, I'm not building Lineage anymore, I switched over to RessurectionRemix, it's totally awesome.
Edit: You know what. I'm actually going to build the kernel itself for now and see if it works, since I'm on a CM12.1 ROM for ms345, it works but is quite bugged. I'll do an experiment and try to flash the kernel I'll build. Probably won't work, but I'll see what will happen
Edit 2: Okay, green screen again, I'll try to build the full ROM again, if that happens again, that is bad news, since I have no idea how to fix this thing.
Just another edit: I have an idea. I just downloaded the Qualcomm QPST tool, I might be able to debug this. No promises tho, we'll see.
Click to expand...
Click to collapse
The kernel is probably originally for aosp 6.0.
Personally I think Lineage is better, but then I've never personally used RR.
I'll also make the fingerprint commits.
edit: trying to figure out how to only make a pr of one commit to your tree.