I have decided not to delay any longer getting these files to the dev community here. I expect these may be removed from Megaupload by Motorola very quickly so grab them while you can!
This is a dump of the complete system directory for a recent GRH55 2.3 Gingerbread development build for the Atrix dated 1/21/2011.
I extracted it from the CG60 SMG file which was split from the SBF file using SBF Recalc 1.2.9.1 and then opened as a disc image in WinHex 15.5 Specialist version.
We will also post an archive of the raw CGs which include a number of other partitions that may be of interest as well as the boot files that were packaged separately with the SBF.
Please be very careful when trying to use any of these files on your stock consumer phone. The system includes many debug features and binaries etc. for development that are not found in stock builds and are of little use to end users and in some cases decidedly unwanted on your phone.
Hopefully the developers here will quickly set to work finding out what is most useful and safe for end users and everyone can enjoy the fruits of their labor.
Have fun and remember that there is no custom recovery yet for these phones nor an SBF file to restore with. You are completely unable to recover your phone at this stage if anything goes wrong that prevents it from booting normally!
The reason we are not going to post the SBF file itself is twofold.
First, they are proprietary Motorola files and we have received C&D orders from Motorola in the past and don't wish to have that happen again here.
Second, these engineering builds are strictly for unsecured development devices and will brick a consumer device if you tried to flash it.
We obviously do not want to see anyone brick their phone especially at this early stage when their is no recourse or means of recovery.
USE AT YOUR OWN RISK! Nobody is responsible for what you do to your phone except you!
http://www.megaupload.com/?d=Y232E9J0
very interesting, thanks for the post and info. hope a developer can make uses of this
Not that I will know what to do with these files at all, but I am going to keep a copy just in case someone needs to re-upload the files once Moto takes them down.
cellzealot said:
I have decided not to delay any longer getting these files to the dev community here. I expect these may be removed from Megaupload by Motorola very quickly so grab them while you can!
This is a dump of the complete system directory for a recent GRH55 2.3 Gingerbread development build for the Atrix dated 1/21/2011.
I extracted it from the CG60 SMG file which was split from the SBF file using SBF Recalc 1.2.9.1 and then opened as a disc image in WinHex 15.5 Specialist version.
We will also post an archive of the raw CGs which include a number of other partitions that may be of interest as well as the boot files that were packaged separately with the SBF.
Please be very careful when trying to use any of these files on your stock consumer phone. The system includes many debug features and binaries etc. for development that are not found in stock builds and are of little use to end users and in some cases decidedly unwanted on your phone.
Hopefully the developers here will quickly set to work finding out what is most useful and safe for end users and everyone can enjoy the fruits of their labor.
Have fun and remember that there is no custom recovery yet for these phones nor an SBF file to restore with. You are completely unable to recover your phone at this stage if anything goes wrong that prevents it from booting normally!
The reason we are not going to post the SBF file itself is twofold.
First, they are proprietary Motorola files and we have received C&D orders from Motorola in the past and don't wish to have that happen again here.
Second, these engineering builds are strictly for unsecured development devices and will brick a consumer device if you tried to flash it.
We obviously do not want to see anyone brick their phone especially at this early stage when their is no recourse or means of recovery.
USE AT YOUR OWN RISK! Nobody is responsible for what you do to your phone except you!
http://www.megaupload.com/?d=Y232E9J0
Click to expand...
Click to collapse
thanks for sharing
cellzealot said:
I have decided not to delay any longer getting these files to the dev community here. I expect these may be removed from Megaupload by Motorola very quickly so grab them while you can!
This is a dump of the complete system directory for a recent GRH55 2.3 Gingerbread development build for the Atrix dated 1/21/2011.
I extracted it from the CG60 SMG file which was split from the SBF file using SBF Recalc 1.2.9.1 and then opened as a disc image in WinHex 15.5 Specialist version.
We will also post an archive of the raw CGs which include a number of other partitions that may be of interest as well as the boot files that were packaged separately with the SBF.
Please be very careful when trying to use any of these files on your stock consumer phone. The system includes many debug features and binaries etc. for development that are not found in stock builds and are of little use to end users and in some cases decidedly unwanted on your phone.
Hopefully the developers here will quickly set to work finding out what is most useful and safe for end users and everyone can enjoy the fruits of their labor.
Have fun and remember that there is no custom recovery yet for these phones nor an SBF file to restore with. You are completely unable to recover your phone at this stage if anything goes wrong that prevents it from booting normally!
The reason we are not going to post the SBF file itself is twofold.
First, they are proprietary Motorola files and we have received C&D orders from Motorola in the past and don't wish to have that happen again here.
Second, these engineering builds are strictly for unsecured development devices and will brick a consumer device if you tried to flash it.
We obviously do not want to see anyone brick their phone especially at this early stage when their is no recourse or means of recovery.
USE AT YOUR OWN RISK! Nobody is responsible for what you do to your phone except you!
http://www.megaupload.com/?d=Y232E9J0
Click to expand...
Click to collapse
I have no Idea also what to do with these files but just incase someone else need them I downloaded them, You never know.
Hopefully something with the modem firmware can be pulled from this to turn on HSUPA.
Do you guys have access to an engineering spl ?
Sent from my MB860 using XDA App
humancyborg said:
Do you guys have access to an engineering spl ?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
That is something that applies to HTC with a Nand lock from my understanding.
We don't have a complete picture of the boot process on this device but Motorola does things differently than HTC and on our OMAP/Qualcomm chipset devices there is no SPL involved in the bootchain.
hey i have a tester atrix from motorola. How would i go about installing this on that?
hassanjanjua2002 said:
hey i have a tester atrix from motorola. How would i go about installing this on that?
Click to expand...
Click to collapse
You would need the full sbf file and a program named rsdlite.
The test model I have is on 4.0.2340.MB860.Attt.en.us which trying to update to 4.0.2350 but keeps failing. With the ! screen showing up mid install. Is there any sbf file or update.zip that i can use at the moment because I don't know how to update it regularly. For either this ginderbread or any version thats newer than mine...
hassanjanjua2002 said:
The test model I have is on 4.0.2340.MB860.Attt.en.us which trying to update to 4.0.2350 but keeps failing. With the ! screen showing up mid install. Is there any sbf file or update.zip that i can use at the moment because I don't know how to update it regularly. For either this ginderbread or any version thats newer than mine...
Click to expand...
Click to collapse
You can not update that phone, you will be stuck on your version because your phone is not able to pass the hash checks in the update.zip. your hope lies in a released sbf file.
hassanjanjua2002 said:
The test model I have is on 4.0.2340.MB860.Attt.en.us which trying to update to 4.0.2350 but keeps failing. With the ! screen showing up mid install. Is there any sbf file or update.zip that i can use at the moment because I don't know how to update it regularly. For either this ginderbread or any version thats newer than mine...
Click to expand...
Click to collapse
do you have a sbf for your phone ? if so please upload so that i can split it and use to compare with other sbf from other dev unit build
Ok thanks for the responses. How do i grab the sbf from my phone? From android sdk?
hassanjanjua2002 said:
Ok thanks for the responses. How do i grab the sbf from my phone? From android sdk?
Click to expand...
Click to collapse
You don't grab it from your phone at all. An SBF file is a proprietary firmware file from Motorola that is flashed with a service ware utility called RSD Lite.
These files are only available to the public via leaks from unofficial sources.
Having a development test phone in this case is a difficult problem unless you have access to internal files for engineering devices.
On another note, I am very surprised that devs are not all over this dump pulling out the framework and libs and apks for use on consumer phones.
There is plenty here that should be able to be safely used.
I am sure that will change once recovery methods have been achieved.
cellzealot said:
On another note, I am very surprised that devs are not all over this dump pulling out the framework and libs and apks for use on consumer phones.
Click to expand...
Click to collapse
Well, what should we be pulling out? Transplanting 2.3 libs and frameworks into 2.2 isn't a good idea, and if it's just a stock MotoBLUR build for 2.3, then nothing's truly different besides it being Gingerbread. Correct me if I'm wrong, but unless there's something wildly new in this build, it's just another version of what we have?
(I'm newer to Android development, but I know multiple languages (Java, C, C++, Obj-C, etc) and have been hacking/dev'ing for the iPhone since 1.0. Just thought I'd state that so I don't like like a huge idiot if this is extremely useful haha)
Smith7018 said:
Well, what should we be pulling out? Transplanting 2.3 libs and frameworks into 2.2 isn't a good idea, and if it's just a stock MotoBLUR build for 2.3, then nothing's truly different besides it being Gingerbread. Correct me if I'm wrong, but unless there's something wildly new in this build, it's just another version of what we have?
(I'm newer to Android development, but I know multiple languages (Java, C, C++, Obj-C, etc) and have been hacking/dev'ing for the iPhone since 1.0. Just thought I'd state that so I don't like like a huge idiot if this is extremely useful haha)
Click to expand...
Click to collapse
It actually looks like stock android.
Smith7018 said:
Well, what should we be pulling out? Transplanting 2.3 libs and frameworks into 2.2 isn't a good idea, and if it's just a stock MotoBLUR build for 2.3, then nothing's truly different besides it being Gingerbread. Correct me if I'm wrong, but unless there's something wildly new in this build, it's just another version of what we have?
(I'm newer to Android development, but I know multiple languages (Java, C, C++, Obj-C, etc) and have been hacking/dev'ing for the iPhone since 1.0. Just thought I'd state that so I don't like like a huge idiot if this is extremely useful haha)
Click to expand...
Click to collapse
Yaotl said:
It actually looks like stock android.
Click to expand...
Click to collapse
you've been pwned sir.
Yup...this is a completely Blurless build and we have one like it for the Droid X as well.
I should caution that some primary functionality appears to be stripped out from the DX build regarding hardware sensors and some other things that are missing entirely.
It's fascinating because it is in many ways what everyone has been whining for since the DX came out with the locked bootloader. It is pure AOSP with virtually no amendments to the libs and very limited or no proprietary Motorola drivers.
There is no WebTop in this build and many other feature again appear to be missing entirely.
So, a very interesting challenge to the developers here to take this mythical beast and turn it into a useable build for consumer hardware by re adding the desired components and shoehorning them back into this build.
Pretty unique opportunity I would say!
Just knowing this file could potentially become a workable 2.3 build for my Atrix makes me VERY excited.
HOPE
Related
After munging about in the forums, lurking and trying to absorb your knowledge, I'm still mysified by how to non-destructively put android on my friend's phone.
It's ether I can't find the files/the info is outdated, or it simply doesn't work.
Here is the skinny -
I own a reflashed and rooted Motorola droid, so flashing a phone isn't that much of a mystery to me.
My friend has a U.S. Vogue CDMA, however it is ABSOLUTELY CRITICAL that we do not touch the nand. He uses it for development and has a few hundred dollars in apps that he has purchased for WiMo. We would like a stright boot directly from the flash card.
SO I guess, here is a run down of what I'm looking for
What files do I need to boot 2.1 off of a flash card? A file manifest with a decent description of what the files do would be helpful. I'll give an example..
Step one:
If you do not have dzo's latest nbh get it from here:
Click to expand...
Click to collapse
I don't think that sentence is in English. I just can't parse it. What is an nbh and what does it do. Is it a bootloader? What is it's payload? Now this is from the tutorial to flash the nand, which is not what I want to do, but it's giving an example of what I'm finding.
I'm under the instructions of "you can put android on my phone, just don't screw anything up", so clear and full explanations would be very helpful...
Any particular reason why you guys just don't package this? On my droid, the whole OS is on a simple update.zip file I have to run with a loader. Are not at that point yet?
There are plenty of guides for installing and running android from the sd card.
Just like on your 'droid' forums all you have to do is search
http://forum.xda-developers.com/showpost.php?p=5579562&postcount=15
And as for packaged compared to the update.zip's you use. It's apples and oranges man
You need to be looking at this post. There isn't a way to boot straight to Android on the Vogue without nuking your WinMo installation.
To install 2.1, you're going to need "haretinstall.zip" and "zImage-eclair" from the Sourceforge page linked in that post. Unzip haretinstall.aip to /sdcard/andboot and replace zImage with zImage-eclair.
Still at Sourceforge, you need to go down to the "2010-01-29" folder and download "eclair.zip". This should contain a file called "androidinstall.tar". Put that file in the andboot folder, but don't extract it. After this, you should be able to follow the instructions I linked.
Any particular reason why you guys just don't package this? On my droid, the whole OS is on a simple update.zip file I have to run with a loader. Are not at that point yet?
Click to expand...
Click to collapse
This is pretty much all you're doing - you just have to jump through a few hoops to get the loader installed since this phone came out about a year before Android was even announced.
Also, make sure he's not expecting this to work perfectly or be super-fast. Bluetooth doesn't fully work with Eclair yet and the Vogue is working with about 1/4th the processing power of the Droid and N1.
you can use y gen dual boot to bring you up to a nice gui to pick what u want to boot into on reset if you would like. Almost like a boot loader. Get it here http://forum.xda-developers.com/showthread.php?t=623792
Hey hey XDA! (ignore the account name, I was 13 years old when I first joined XDA in like '08)
My father bought a refurbished TPT from TigerDirect and literally nothing worked. I factory wiped it and tried to update it so I could get the cameras working and other such things - but no luck. I started to crawl my way through the internet but neither Lenovo nor anybody else seemed to have the answers. I thought that since I was failing the SHA1 hash checks that I might as well start replacing the files and see where it gets me. Five hours later:
First try to restore my ICS nandroid backup, but if not, follow the mini-guide below! Also look at the end of the post for all my files!
For those of you that can't update because you're failing assertion checks:
Root your current version with one of the root tools in my package. Go to your advanced properties and see which Lenovo internal version you're running "0089, 0075, 0060, etc". There are three toolkits that I included and they all work; use the one for your version.
Flash the Ventana CWM.
Do a nandroid restore through CWM by going to backup->restore. It's going to wipe and install a clean 0075 Honeycomb build.
Root again, the pre 0089 package should be a relatively easy root to do.
Restore the factory recovery. I have one fresh from my tablet and one that I found floating around on the internet. You could use either (the one floating around worked fine for me, but if you want something 'newer' just use mine).
Connect to a WiFi network and check for updates. This is the part where it might get tricky. Not all of the files in the 0075 build that I attached were original (it wasn't my build, not my fault). If you get an assertion check, look at your error and see which file has failed. I only had to replace three files, gps.conf, Generic.kl, and the busybox binary. This theoretically should be the same for you. Try to update without replacement, and as the updates start to fail replace the files that are causing failure. The ones you need are attached in my bundle, but I have others too - so let me know if you'll need them!
By this step you should be on the ICS update. Root using the debugfs kit (in the ICS folder for rootkits) and then flash Koshu's recovery (which only worked for me on ICS). Do a backup. Live a happy life.
This procedure isn't meant to be very 'easy'; I am just attempting to make your inconsistencies match mine so they can be fixed in the same manner. A quick Google search showed me that a lot of people are missing different files with barely any files available. Everything I have was extracted from official packages from previous versions. I think I managed to 'get lucky'.
You can find everything that you need on my website. I won't ever take this down save for a plane crashing into the datacenter where it's hosted. There are copies of all the files I mentioned in this tutorial and even copies of Lenovo's official updates since their servers go down more than Kim Kardashian.
Go to http//davidstancu.me/TPT
I'm also working on a small Android app to replace these files to the factory files (kind of like the way Windows has sfc /checknow or whatever that command is. I would also like to extend a massive thank you to everybody who made the tools that I used to get this done.
Since my account doesn't have 10 posts yet I can't post a link, so you'll have to manually include the colon. Sorry
What is your tablet version? US? ROW?
I am looking for 16 US version.
i have inadvertantly deleted my original ics files when upgrading to Koshu's JB. I need to restore the stock ics so would like to use your cwm restore files.I've downloaded the files but the md5 check doesn't work.I assume it's only because i need the actual name of the folder these files are saved in the cwm backup folder. can you please either post it or email it?
smiley1960 said:
i have inadvertantly deleted my original ics files when upgrading to Koshu's JB. I need to restore the stock ics so would like to use your cwm restore files.I've downloaded the files but the md5 check doesn't work.I assume it's only because i need the actual name of the folder these files are saved in the cwm backup folder. can you please either post it or email it?
Click to expand...
Click to collapse
'
don't worry. I just created a new blank nandroid.md5 file and it took.Unfortunately, my TPT would not boot up. It just stuck at the Lenovo logo. Any suggestions to get it working?
My guess is that a file was corrupted. Try redownloading?
Thank you so much for the detailed guide and the files! My TPT came with a strangely named bladenct...0037_0001 (US) firmware so I couldn't have updated to ICS otherwise.
In other words, confirmed working for a US 16GB TPT. :good:
BrazenRain said:
Thank you so much for the detailed guide and the files! My TPT came with a strangely named bladenct...0037_0001 (US) firmware so I couldn't have updated to ICS otherwise.
In other words, confirmed working for a US 16GB TPT. :good:
Click to expand...
Click to collapse
Based on that version number I'm curious... is that a TPT from Tigerdirect? Is the model number 1839AJ6 or 1839AD7?
US vs ROW
da_reeseboy said:
My guess is that a file was corrupted. Try redownloading?
Click to expand...
Click to collapse
Damn.I justchecked the build.prop and the ICS nandroid backup is for a US version. I've got a ROW version.
Anyone out there got an ICS nandroid ROW backup I can use? I'd really appreciate the help.
smiley1960 said:
Damn.I justchecked the build.prop and the ICS nandroid backup is for a US version. I've got a ROW version.
Anyone out there got an ICS nandroid ROW backup I can use? I'd really appreciate the help.
Click to expand...
Click to collapse
Maybe this can help you - http://forum.xda-developers.com/showthread.php?p=37330646#post37330646
da_reeseboy said:
Based on that version number I'm curious... is that a TPT from Tigerdirect? Is the model number 1839AJ6 or 1839AD7?
Click to expand...
Click to collapse
I bought it second-hand (and it seems to have had quite a rough life as is cut out for a ThinkPad), but it's an 1839AD7.
BrazenRain said:
I bought it second-hand (and it seems to have had quite a rough life as is cut out for a ThinkPad), but it's an 1839AD7.
Click to expand...
Click to collapse
Thanks for the reply. I am trying to help another member get his up to ICS, and he has the same weird software version. Did you restore the nandroid or follow the mini guide?
I used the mini guide. Unlike the original poster, I found nothing broken in the stock software. The rear camera has some serious magenta artifacts on the side but that remained in ICS and CM10 so I'm guessing that's hardware damage. (This tablet seems to have been through a lot. Thus I got it at a reasonable price from ebay.)
Awesome! Thanks again for replying.
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
Let me first say, despite what the title of this thread may lead some to believe, I am NOT a noob. I am very familiar with Android, rooting, recovery, Linux, CLI, etc. Excluding recent months, I've been a very active member of the XDA community providing support for the Amazon Kindle Fire and variants for quite some time, and as such, I have amassed a great deal of knowledge regarding Android and modification. Unfortunately, all of this knowledge is limited to wi-fi only devices and I have yet to have any experience with wireless (used prepaid phones for years).
My carrier is Cricket Wireless, and I know being a CDMA variant, that I can only install ROMs made for CDMA variant phones, but are there any CDMA based ROMs for this device? (at first glance, I didn't see any) If so, upon installing a new ROM, would it still be possible to use the same carrier? I know that may seem like a stupid question, but as mentioned before, my experience with wireless carriers is minimal, at best.
Also, I have seen the one-click unlock/root tool available for this device, which is great, but experience has shown me that without first educating yourself about the device being modified, putting faith in such tools' safety/effectiveness is never the best policy. I've read the guides and tutorials posted in the general section (without spending too much time searching through the entire forum), but they are very basic and do not touch much on the fundamentals of what I understand to be exclusive to HTC based phones such as S-Off, RUUs, Sense,etc., and I would much rather use a more reliable command line method (Linux preferably) than putting my trust in a tool in which I can't even view the source code.
And while I'm not a huge fan of XDA's dilapidated search function and will avoid it whenever possible, I am not in the least bit averse to reading provided I don't have to spend all day looking for the right information. I'm sure there are users that provide support for this device (much like myself with the Kindle Fire) that have a "laundry list" of bookmarked links for guides/tutorials/postings etc. for HTC device specific knowledge that can spare me the grueling task of wasting my time through endless, and sometimes pointless searching, only to find I am more confused/frustrated than when I first started. If there are such users willing to share links and the like to make the transition faster for me, I would be very appreciative.
TIA
For the time being there are no CDMA ROMs here, I can say that.
As to the guides, there are some on here. The only one that i can provide you is a kernel building one. It pretty much works for most devices.
Kernel building guide by nikhil
Im also gonna attach a txt file of my FB conversation/walkthrough of building aokp from source.
I hope you find this helpfull. If you ever have any questions you can go ahead and ask me over Facebook, and i will try to assist :3
Еdit: Questions like this make me feel good about humans. Glad to see that there are civilized individuals out there. Have a great time doing what you like (coding) and maybe visit our forums with a Desire C and lend us a hand :3
There is a lot to be done.
I have never Re-searched into the different variables of phones as i assume i have always used the GSM version of every phone, i am unaware of the difference of a CDMA Version and a GSM version of a phone, so what is the difference? and would it just be the RIL that needs to be changed for a ROM to work on the CDMA version of a phone?
me4488 said:
For the time being there are no CDMA ROMs here, I can say that.
As to the guides, there are some on here. The only one that i can provide you is a kernel building one. It pretty much works for most devices.
Kernel building guide by nikhil
Im also gonna attach a txt file of my FB conversation/walkthrough of building aokp from source.
I hope you find this helpfull. If you ever have any questions you can go ahead and ask me over Facebook, and i will try to assist :3
Click to expand...
Click to collapse
Thank you for your quick response. I was hoping to get rid of the stock Sense ROM and move to a CM based JB or even ICS if needed but it looks like that will have to wait for now. I must say, I am actually quite surprised there isn't any CDMA support in these forums. Is it due to lack of developer support here or is there a lot more involved to get a working CDMA ROM?
me4488 said:
Еdit: Questions like this make me feel good about humans. Glad to see that there are civilized individuals out there. Have a great time doing what you like (coding) and maybe visit our forums with a Desire C and lend us a hand :3
There is a lot to be done.
Click to expand...
Click to collapse
Believe me, I've paid my dues in this community (XDA) and I know all too well how frustrating the all too frequent ambiguous questions can be. I'm always willing to help where and when I can, but I was also hoping there were like-minded individuals willing to do the same for me so I can get up to speed as fast as possible.
penguin449 said:
I have never Re-searched into the different variables of phones as i assume i have always used the GSM version of every phone, i am unaware of the difference of a CDMA Version and a GSM version of a phone, so what is the difference? and would it just be the RIL that needs to be changed for a ROM to work on the CDMA version of a phone?
Click to expand...
Click to collapse
A CDMA phone, has a CDMA chip (radio) that stores information such as the carrier, MEID, phone number, network account information, what towers to connect to, etc. Whereas on GSM phones this is all stored on a removable SIM card. The CDMA is not removable and is intended to be (though not necessarily the case) permanently configured for that particular phone/user and that particular carrier.
That being said, this should theoretically be no "major" consequence in getting a ROM built that would work on a CDMA based device.
i see, so are you able to root/flash the same recoveries as us? or are they different for CDMA phones? i could try changing some stuff around with a ROM to make it work with a CDMA device but it will take a lot of testing because i have nothing done this before! the ratio of GSM:CDMA in this community is possibly 100000:1 so nobody has bothered to look into this as it is not needed. however me and Nick may work together to bring you this as he is a kernel developer and i am a ROM developer.
penguin449 said:
i see, so are you able to root/flash the same recoveries as us? or are they different for CDMAonhones? i could try changing some stuff around with a ROM to make it work with a CDMA device but it will take a lot of testing because i have nothing done this before! the ratio of GSM:CDMA in this community is possibly 100000:1 so nobody has bothered to look into this as it is not needed. however me and Nick may work together to bring you this as he is a kernel developer and i am a ROM developer.
Click to expand...
Click to collapse
After a bit of research, I've found that there is a CDMA to GSM patch made by a fellow Recognized Contributor that, as expected, allows certain CDMA ROMs to run on GSM phones. I can't see why the same couldn't be done the other way around. I've sent a PM to him already and I'm just waiting on a response. Considering the fact that there are so few of us CDMA users, I'm sure a patch would be the way to go rather than building a ROM from scratch. But, if nothing else, I'd just build my own based on an available source.
As for the root/recovery, I'm still looking into it...
soupmagnet said:
After a bit of research, I've found that there is a CDMA to GSM patch made by a fellow Recognized Contributor that, as expected, allows certain CDMA ROMs to run on GSM phones. I can't see why the same couldn't be done the other way around. I've sent a PM to him already and I'm just waiting on a response. Considering the fact that there are so few of us CDMA users, I'm sure a patch would be the way to go rather than building a ROM from scratch. But, if nothing else, I'd just build my own based on an available source.
As for the root/recovery, I'm still looking into it...
Click to expand...
Click to collapse
i have the most experience in building PAC from source, however i can offer you this as i wouldn't mind re-building it for CDMA (If i know how to) I too saw the patch and wondered how it would work however i think that when building this will need be inluded rather then GSM.
Code:
PRODUCT_COPY_FILES += \
vendor/cm/prebuilt/common/etc/apns-conf-cdma.xml:system/etc/apns-conf.xml
However i may be wrong in my naivete thinking that is all there is to the variations of GSM and CDMA Roms
If you could explain me how CDMA kernels differ from GSM ones, i could make one for the 2-3 people that need it :3
Go ahead and ask/share. We are open for ideas.
I assume it's just the RIL that needs to be changed, prehaps the kernel will only need to be changed from GSM to CDMA in the same way as a ROM, however i don't know anything about kernels, tonight i'll repo sync and try build a CDMA Rom, prehaps we could then extract a patch from it? Pico has no CDMA version so there is no hope of guidence from our older Brother /:
This is the response that was given to me...
In fact it's possible - BUT you might only have 3G maximum speed. If your device is an GSM device I guess there won't be any CDMA/4G baseband drivers available - which means you'll have to play with 3G max.
The most stuff can be done in the roms build.prop file. The best way is to comapare your file to a cdma build.prop file and edit/insert/remove the related entries.
In some cases you need the ril libs too. Those are only available in a cdma rom for your device. And as there's no cdma rom available this can be difficult.
Is the device/bootloader unlocked? In that case you might build cdma libs from source - depends on rom.
Click to expand...
Click to collapse
Luckily, HTC released the source for the Cricket Wireless Desire C and it should be as simple as compiling and pulling the necessary files.
http://dl4.htc.com/RomCode/Source_and_Binaries/golfc-ics-3.0.16-3d39477.zip
And I can't imagine why it would even make a difference, but here's the Cricket Wireless/Radio Shack Desire C source as well...
http://dl4.htc.com/RomCode/Source_and_Binaries/golfc-ics-3.0.16-3d39477.zip
soupmagnet said:
This is the response that was given to me...
Luckily, HTC released the source for the Cricket Wireless Desire C and it should be as simple as compiling and pulling the necessary files.
http://dl4.htc.com/RomCode/Source_and_Binaries/golfc-ics-3.0.16-3d39477.zip
And I can't imagine why it would even make a difference, but here's the Cricket Wireless/Radio Shack Desire C source as well...
http://dl4.htc.com/RomCode/Source_and_Binaries/golfc-ics-3.0.16-3d39477.zip
Click to expand...
Click to collapse
Well @me4488 you up for the challenge? I could try changing GSM to CDMA in build prop for @soupmagnet if you would like to test that way? if that doesn't work we may have to source build a CDMA Rom for you!
penguin449 said:
Well @me4488 you up for the challenge? I could try changing GSM to CDMA in build prop for @soupmagnet if you would like to test that way? if that doesn't work we may have to source build a CDMA Rom for you!
Click to expand...
Click to collapse
Let me get unlocked, rooted and recovery installed and I'll see what can be done. I might try to pull RIL libs from an original Desire ROM (assuming there is a CDMA version somewhere). Aside from CPUs, NANDs, cameras, etc., manufacturers generally don't like to stray too far from the hardware configurations between device variants.
Edit: BTW what are the udev rules for this device? Are there different rules for fastboot adb hboot and recovery ?
soupmagnet said:
Let me get unlocked, rooted and recovery installed and I'll see what can be done. I might try to pull RIL libs from an original Desire ROM (assuming there is a CDMA version somewhere). Aside from CPUs, NANDs, cameras, etc., manufacturers generally don't like to stray too far from the hardware configurations between device variants.
Edit: BTW what are the udev rules for this device? Are there different rules for fastboot adb hboot and recovery ?
Click to expand...
Click to collapse
Watch out for the recovery. The one person that flashed a custom one had his fail because we don't have a CDMA recovery.
At least that's what he said.
And i would gladly build you a kernel when i get the time.
I don't think there are a lot of udev rules that can differ from the kindle. But don't listen to me, as I am still a rookie.
me4488 said:
Watch out for the recovery. The one person that flashed a custom one had his fail because we don't have a CDMA recovery.
At least that's what he said.
And i would gladly build you a kernel when i get the time.
I don't think there are a lot of udev rules that can differ from the kindle. But don't listen to me, as I am still a rookie.
Click to expand...
Click to collapse
That's absolutely ridiculous. Recoveries like TWRP and CWM sit on a relatively small partition with minimal hardware support. Display, touchscreen, USB, battery, memory and storage are, generally speaking, all that gets initialized. Drivers for WiFi, Bluetooth, CDMA, etc., would likely take up more space than is available on the partition. I could be wrong, but if experience has shown me anything at all, it is you should rarely take what random XDA users says at face value. I'm sure if we take a look at the source code for whatever recovery is being used, well find that it's probably just a simple case of user inexperience playing a part.
Can someone post a partition layout so I can compare it with mine?
soupmagnet said:
That's absolutely ridiculous. Recoveries like TWRP and CWM sit on a relatively small partition with minimal hardware support. Display, touchscreen, USB, battery, memory and storage are, generally speaking, all that gets initialized. Drivers for WiFi, Bluetooth, CDMA, etc., would likely take up more space than is available on the partition. I could be wrong, but if experience has shown me anything at all, it is you should rarely take what random XDA users says at face value. I'm sure if we take a look at the source code for whatever recovery is being used, well find that it's probably just a simple case of user inexperience playing a part.
Can someone post a partition layout so I can compare it with mine?
Click to expand...
Click to collapse
I haven't partitioned my SD card or anything like that at all tbh :L i just flashed the recovery, as far as a CDMA Rom goes, i've got the CDMA in permissions and in the build.prop but not sure if the RIL correctly configured to CDMA and i am unsure of how to Check, however if you want to test i'll upload it and send you the link although we may have to wait for a CDMA kernel before we can do anything!
penguin449 said:
I haven't partitioned my SD card or anything like that at all tbh :L i just flashed the recovery, as far as a CDMA Rom goes, i've got the CDMA in permissions and in the build.prop but not sure if the RIL correctly configured to CDMA and i am unsure of how to Check, however if you want to test i'll upload it and send you the link although we may have to wait for a CDMA kernel before we can do anything!
Click to expand...
Click to collapse
I'll try it out when I can, but I have to figure out this recovery issue first. I was able to obtain root, but not with the "superboot". The superboot method gave me the same problems others here were having and it would never install Superuser.apk or the 'su' binary. However, I wrote a small script using Bin4ry's exploit and it worked flawlessly. I have root now, but I'm having trouble identifying each of the partitions.
Having root, I was able to make backups of each of the partitions listed under "/proc/emmc", and I attempted to 'dd' the TWRP recovery.img to the "recovery" partition, but the device would still always boot to the stock recovery. When I tried to install recovery via fastboot, I got the same "This build is for development purposes only" message as before and the stock recovery is gone. So apparently, the partition (mmcblk0p21) listed as recovery under "/proc/emmc", is either not the actual recovery partition, or I'm missing something.
Since you have recovery installed, does it have 'parted' included in the build? Do you know how to print a partition table? If so, would you mind posting one?
If you could explain how you do it, i could gladly give it a shot when i can (vacations up ahead dunno when i will be back)
me4488 said:
If you could explain how you do it, i could gladly give it a shot when i can (vacations up ahead dunno when i will be back)
Click to expand...
Click to collapse
Assuming the version of recovery you are running has 'parted' included, enter the following at your command prompt:
Code:
[COLOR=DimGray]$[/COLOR] adb shell
[COLOR=DimGray]~ #[/COLOR] parted /dev/block/mmcblk0
[COLOR=DimGray](parted)[/COLOR] print
If for some reason 'parted' isn't included in your version of recovery, you can temporarily install it for one session (since recovery is loaded into memory to run, nothing gets written to the actual recovery ramdisk and rebooting will erase any changes made):
1) Download 'parted': http://d-h.st/h81
2) Boot into recovery
3) Enter the following commands:
Code:
[COLOR=DimGray]$ [/COLOR]adb push /path/to/parted /sbin/parted
[COLOR=DimGray]$ [/COLOR]adb shell
[COLOR=DimGray]~ #[/COLOR] chown 0.0 /sbin/parted
[COLOR=DimGray]~ #[/COLOR] chmod 755 /sbin/parted
Ah that is pretty helpful, it should be implemented into the recovery source, if you don't mind me asking where is the main source which includes his function?
russell664 said:
Ah that is pretty helpful, it should be implemented into the recovery source, if you don't mind me asking where is the main source which includes his function?
Click to expand...
Click to collapse
I'm pretty sure it just needs to be added during the build. With the Kindle Fire, early versions of TWRP didn't include the 'parted' binary and it was added intermittently in subsequent versions. It wasn't until the developer was constantly bombarded with requests that it became a permanent addition.
I don't have much (any) experience building recoveries but I would think it'd be as simple as unpacking the ramdisk and just adding it to the filesystem.
I came here looking for root help with this device. I see the autoroot by chainfire is not listed for this. Can i get some direction on how to go about it?
Sm-t805 version should work
Kahun said:
Sm-t805 version should work
Click to expand...
Click to collapse
Ok i understand that you think it should work even though it is not the same nomenclature. Why should i believe that it should work when the nomenclature is different? What are my available options of in fact ir doesnt work and my device is bricked? I saw on other post in this forum on th 807p and it appears the person in that thread now has a bricked device that can not be recovered. So you see my reluctance to trust something that isnt clearly marked as for use with the nomenc.ature of my device. Thanks for your help with this.
liz.beth said:
Ok i understand that you think it should work even though it is not the same nomenclature. Why should i believe that it should work when the nomenclature is different? What are my available options of in fact ir doesnt work and my device is bricked? I saw on other post in this forum on th 807p and it appears the person in that thread now has a bricked device that can not be recovered. So you see my reluctance to trust something that isnt clearly marked as for use with the nomenc.ature of my device. Thanks for your help with this.
Click to expand...
Click to collapse
Could possibly brick try at your own risk if your desperate. Like you said I would just wait for it to get released.
In case it wasn't clear, I acknowledged that the device isn't listed in that thread, as such I am seeking other options for rooting my device. Are there other options available for rooting it?
This is the thread for you to ask:
http://forum.xda-developers.com/showthread.php?t=1980683
He'll need a copy of the recovery file that's inside the rom file. So you'll need access to the full file which I'm not sure it's even been released (try and get it so you have a copy for the future).
Sent from my SM-G900P using Tapatalk
Itchiee said:
This is the thread for you to ask:
http://forum.xda-developers.com/showthread.php?t=1980683
He'll need a copy of the recovery file that's inside the rom file. So you'll need access to the full file which I'm not sure it's even been released (try and get it so you have a copy for the future).
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
Thanks for the clue. I still have less than 10 posts so i cant ask a question there yet. Maybe if we post back and forth enough here ill get b my 10 post requirement met?
I tried to find a copy of the ROM your using (T807PVPU1ANH1) but its not available at the regular locations....
http://samsung-updates.com/
http://www.sammobile.com/
No downloads on the Sprint and Samsung sites...
Samsung tablets are fairly hard to destroy as long as you can access recovery (and use Odin to flash a stock ROM) or get this Kies program to work.
i considered trying to extract the recovery.img but after installing android studio and the Java jdk, there seems to be some issue with android studio not recognizing the jdk path so I quit. . If you have some ideas, I'd be glad to take in any assistance you have.