The Fascinate Development Platform AKA UnBrickable Mod - Fascinate Android Development

FIrst off I'd like to say Thanks to RootzWiki for the device. They gave me a Fascinate and told me to do what I want with it... So I made it into a development device. Thanks to RootzWiki for the device!
introduction
I'm not kidding when I say UnBrickable. Modifying the OM pins means you can boot from USB, UART or MMC. This makes the phone quite UNBRICKABLE. There is nothing you can do software wise to prevent the device from booting into this mode. We are communicating with the unrewritable, efused IROM on the processor. It's the thing that makes the system on a chip into a "system on a chip".I am here now to tell you how to turn your Samsung Fascinates into a KIT-S5PC110 development board. The KIT-S5PC110 development board is the platform used to develop our phones. There are some differences between this mod and the official development platform. The S5PC110 has a removable internal SDCard and no touchscreen.
Why would you want to do this? When you plug in the battery and connect it to the computer in "off" mode, then press and hold the power button, it will become an S5PC110 board awaiting download of a program to run. This occurs long before anything like software or firmware enters the processor. This is the IROM of the device awaiting commands or a power on signal.
Because it is accepting a memory flash, anything may be put onto the device to perform a boot sequence..... Apple iOS (iPhone4 has the same processor) WP7 (mango supports this processor).
This will be a replacement for JTAG once we are able to make some firmware. How could it possibly be better then JTAG? Let's count the ways....
1. The only part required is a wire.
2. No shipping time.
3. No cost for a box to interface the computer.
4. Permanent.
5. Can be done as a preventive measure.
6. Gives the ability to test new Bootloaders temporarily.
7. Allows development of the entire system.
8. Removes worry about flashing and acts as a backup.
After performing this mod:
Remove the battery, replace the battery, your phone will connect to the computer via USB and await commands. Otherwise it will pretty much act like a Fascinate. See the Special Instructions section.
Modification
You will need:
1. Get someone who knows what they're doing with a soldering iron. If they don't know what flux is, then they don't know what they're doing. You can send me a PM (or email my [email protected]) or Connexion2005(aka MobileTechVideos.com) NOTE: I do not work with MobileTechVideos.com.
2. soldering iron - make sure it's sharp, if it's not sharp, then sharpen it, flux it and retin it.
3. flux
4. solder
5. tweezers
6. A relay (possibly- for the wire within to use as a bridge)
performing the modification:
1. tear apart your phone... Make sure to take out your SIM and external SDCard before you do this.
1A. Remove the screws.
1B. Separate the top case from the bottom case
1C. disconnect the display connector and free the camera and button assemblies from the case.
1D. Remove the mainboard
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Perform the mod as follows: Replace the xOM5 resistor from the top position to the bottom position.
*OR: remove the xOM5 resistor and jumper the center pads of xOM5 to the center pads of xOM0 or xOM3.
3. reassemble the phone.
Special Instructions
This replaces the battery charging sequence. The normal battery charging sequence can be activated by holding power for 4 seconds.
To turn on the device, and operate in normal mode, you must hold the power button for 5 seconds.
3 button Download mode works as usual, however you must not have the S5PC110 drivers installed on the computer. You can use your custom rom menu option, adb reboot download, or use a terminal to "reboot download". 301Kohm Factory Mode JIGs work as well, but you must press power to bypass the S5PC110 mode.
To enter recovery mode, press and hold power for 3 seconds, then hold volume + and volume - until SAMSUNG is displayed on-screen.
Conclusion
Congratulations. You now have a device which works like a KIT-S5PC110 with an OM Value of 29. Now get to developing some serious custom software. See here for setting up the UART output http://forum.xda-developers.com/showthread.php?t=1235219
reading material
Creating your own Samsung Bootloaders: http://forum.xda-developers.com/showthread.php?t=1233273
KIT-S5PC110 manual: http://www.mediafire.com/?94krzvvxksvmuxh
how to use DNW: http://tinyurl.com/dnw-how-to
Flash using openOCD and DNW: http://www.arm9board.net/wiki/index.php?title=Flash_using_OpenOCD_and_DNW
another DNW example: http://www.boardset.com/products/mv6410.php
ODroid dev center: http://dev.odroid.com/projects/uboot/wiki/#s-7.2
drivers and utilities
This will be an ever expanding list
Windows Drivers http://forum.xda-developers.com/attachment.php?attachmentid=678937&d=1312590673
Windows Download Tool DNW: http://forum.xda-developers.com/attachment.php?attachmentid=678938&d=1312590673
Windows Command Line Download Tool: http://forum.xda-developers.com/showpost.php?p=17202523&postcount=27
Linux DNW Utility: http://dev.odroid.com/projects/uboot/wiki/#s-7.2
firmware
One-Click Resurrector: http://forum.xda-developers.com/attachment.php?attachmentid=712232&d=1315349672
Bootloader Hello World by Rebellos http://forum.xda-developers.com/attachment.php?attachmentid=698077&d=1314105521

Wow your really smart
Sent from my SCH-I500 using XDA App

Never mind, I didn't read the entire post.

Because it is accepting a memory flash, anything may be put onto the device to perform a boot sequence..... Apple iOS (iPhone4 has the same processor) WP7 (mango supports this processor).
Click to expand...
Click to collapse
are you saying you could possibly boot iOS or WP7 on the fassy?

lambi1982 said:
are you saying you could possibly boot iOS or WP7 on the fassy?
Click to expand...
Click to collapse
With appropriate gpio mapping, yes. It would take a lot of work, but yes.

Great work

that is absolutely incredible. now if only i had the time to actually mess with this.. damn. stupid work, wife and kid. lol. top score bro, no doubt. hopefully some wicked awesome person will pick this up and do some crazy **** to our phones. i'm game.

This is great work. I vote someone rolling up all of you links for UnBrickable Mod into a thread to be stickied.

nemesis2all said:
This is great work. I vote someone rolling up all of you links for UnBrickable Mod into a thread to be stickied.
Click to expand...
Click to collapse
+1 for sticky. These contributions and the work behind them are mind-boggling.
Sent from my SCH-I500 using xda premium

Wow, I know how to solder lol but i'd be too scared to do this haha. Its really impressive from what I've read lol and I would love to see results about the iOS being put on the fascninate.
Sent from my SCH-I500 using xda premium

Jazz848 said:
+1 for sticky. These contributions and the work behind them are mind-boggling.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
+1+1+1+1+1+1+1+1+1+1+1 haha
Sent from my SCH-I500 using xda premium

my mind = blown..now I just wish i knew someone skilled enough to perform this! You deserve a box of cookies bro! (Stashed with cash! Lol)

Very nice. Now if only I could solder such tiny things.

Which soldering iron would you suggest? Or it's better with a soldering station?

although the phone will be UNBRICKABLE ... this mod has a high chance of making the phone BREAKABLE.... GET IT?
But dang, what do you have to do to be this GENIUS.

amazing work man
question i have a incredible s that i brick flashing the eng-off software
how much would you charge me to unbricked this sucker?

elmanortega said:
amazing work man
question i have a incredible s that i brick flashing the eng-off software
how much would you charge me to unbricked this sucker?
Click to expand...
Click to collapse
I ask for $30 plus shipping via PayPal. Send me a PM.

Hey adam would it be possible for the samsung continuum to see this spec wise there almost exactly the same with the exception of screen size and that stupid ticker. Reason why im asking is I thought this could only be done with a snap dragon processor.
Sent from my SCH-I400 using XDA App

That's cool man. my 7 months bricked Galaxy Tab will be life again if i can find someone who can understand this. i'll pay him of course.
..//is the mobiletechvideos.com guys do this kind of method?

alisabki said:
That's cool man. my 7 months bricked Galaxy Tab will be life again if i can find someone who can understand this. i'll pay him of course.
..//is the mobiletechvideos.com guys do this kind of method?
Click to expand...
Click to collapse
I've not yet located the mod done on the Galaxy Tab. Send it to me and I can likely locate the proper modificaiton. This is the wrong thread though.. http://forum.xda-developers.com/showthread.php?t=1236273
Send me a PM.

Related

[APP](idea) New Webtop-CALL FOR DEVS

This is an open call for devs who would like a challenge, and who would like to improve ths usability of our Atrix phones. I'm not a programmer at all, but I have an idea for a webtop replacement app, one that has the potential to be much faster and potentially more universal.
So, we all know that moto's webtop software kinda blows chunks. Its slow and buggy and absolutely not worth buying the lapdock for.
From what I understand, it's a customized, instant-on build of linux. This strikes me as a little stupid, because android already is linux (of sorts), and the limitations of the lapdock sound easier to overcome without a second OS. I don't know much about programming, but I imagine that this can't be the best way to do this.
After seeing an ASUS Transformer in action, I got to thinking. The multiple customized desktops and widgets from android translate pretty well to the bigger screen, and using them with a mouse and keyboard isn't half bad.
Rather than a whole second OS, I would love to see a new launcher, a second set of homescreens that appear when you plug the phone into the lapdock. I'm visualizing something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
One, three or five fully customizable homescreens for widgets and a customizable dock with some apps in it. It doesn't have to look exactly like this, this is just a mock-up. The standard notification curtain is probably good enough as a start, though somebody ambitious could probably do better.
rather than booting up, we could close the phone homescreen and open the laptop homescreen. There might be a bit of a wait when switching while your screen redraws, but after that, it should be very snappy. I don't know how easy it would be to do, but if you can tell apps about the bigger screen size/resolution, you could probably convince them to open in their tablet versions, furthering the bigg(er)-screen experience. Combine that with a tabbed browser (anything from the market) and you've got a solid netbook replacement. play games, or read your gmail on a real screen, without needing a second device. you know, what this lapdock was supposed to be!
I'm guessing this would need to be a root app because of the pixel density and screen size changes, but i have no idea. And i don't know if it'd be easier to do as a separate launcher or as one launcher that does double duty with both phone and laptop homescreens. The only other challenge that I can think of is getting the mouse and keyboard to play nice.
For controls, in adition to using the mouse as fake touch, I was thinking of using the left and right arrow keys to switch screens, and up and down to open the app drawer and notification curtain. Making this user customizable would be ideal.
This has the potential to be totally compatible with the Photon when it comes out, and it probably wouldn't be too much harder to use this to give webtop functionality to any ROM or even any phone with HDMI && usb. Does anyone know if this would work with MHL (ala Sensation and Galaxy S2)?
I really don't know where to start, and there's no way I can do this alone (or even at all, really) so if you have advice or would like to help make this happen, sound off!
so basically you want it to output a upscaled/honeycombed look when HDMI out is present/webtop enviro selected.
it's a nice notion, but i'm doubtful that this will get done. most likely it would involve opening up a second instance of Android from the boot address of the current linux installation. not really sure if that's possible.
This seems a bit steep of a feat, but definitely possible. Devs that are attached to webtop would not have to make sure that it is compatible when making new roms, because they would only need to add the separate launcher.
but again, this could be too steep. Instead, if the into mode is feeling a bit sluggish to you, I might suggest that someone figure out a better windowing manager than motorola's clunky version.
Sent from my MB860 using XDA Premium App
Before we get into anything... Explain how a little change to webtop is more important then an unlocked bootloader?
Sent from my GingerBlur'd, de-odex'd, modded Motorola Atrix 4G (ish.)
I'm not sure that a change in window manager would help any. Startup time seems pretty similar to what I see when starting the X Windowing System on any box with just a gig of ram. Maybe a lighter weight window manager, such as fluxbox, would help but I'm betting the issue is the same as it is on any other platform....the X window server itself is an inefficient memory hog.
jbrussee said:
Before we get into anything... Explain how a little change to webtop is more important then an unlocked bootloader?
Sent from my GingerBlur'd, de-odex'd, modded Motorola Atrix 4G (ish.)
Click to expand...
Click to collapse
This is a project that will outlive the atrix. Future phones with unlocked bootloader will have this webtop already complete, or less optimistically, available for porting.
cmcnabb said:
I'm not sure that a change in window manager would help any. Startup time seems pretty similar to what I see when starting the X Windowing System on any box with just a gig of ram. Maybe a lighter weight window manager, such as fluxbox, would help but I'm betting the issue is the same as it is on any other platform....the X window server itself is an inefficient memory hog.
Click to expand...
Click to collapse
then I guess somone out to port wayland to android....
good luck with that
first things first
does anyone know of an api public or private to write to the hdmi serial port???
Great idea, and interesting too - however, should be in [Themes and APPS]
Nal, I do not believe we want the Atrix devs working on other phones, basically. Defeats the purpose of modding our atrixs
Sent from my GingerBlur'd, de-odex'd, modded Motorola Atrix 4G (ish.)
moved to proper forum.
almost seems like it would be better to wait for the bootloader to be cracked, then dualboot with ubuntu (or some sort of arm-adapted desktop OS) and startup a gui. Now that's what im waiting for. Anything else just isnt native, and slows up the phone.
arexxk said:
almost seems like it would be better to wait for the bootloader to be cracked, then dualboot with ubuntu (or some sort of arm-adapted desktop OS) and startup a gui. Now that's what im waiting for. Anything else just isnt native, and slows up the phone.
Click to expand...
Click to collapse
Well no, that's the point, the reason its so bad is because its running two OS's. Booting up ubuntu is totally not necessary, we already have android, which for most purposes, is enough.
Mr. Clown said:
moved to proper forum.
Click to expand...
Click to collapse
Thanks, I wasn't sure where it went
jbrussee said:
Before we get into anything... Explain how a little change to webtop is more important then an unlocked bootloader?
Sent from my GingerBlur'd, de-odex'd, modded Motorola Atrix 4G (ish.)
Click to expand...
Click to collapse
This is definitely a different area of development. Every single developer that is interested in the Atrix probably isn't working on the bootloader. I certainly wouldn't want to steal away bootloader devs, as customs ROMs are really important for unleashing this phone. That said, webdock is definitely another weakness of this phone, it isn't as amazing as it could be. I'm sure someone wants to help improve this aspect of the UX.
Orangestrat said:
Well no, that's the point, the reason its so bad is because its running two OS's. Booting up ubuntu is totally not necessary, we already have android, which for most purposes, is enough.
Click to expand...
Click to collapse
It is not running two OS's. It is running a single Linux kernel (which is the O/S) plus a scaled down destop environment built from some of the Ubuntu packages (but not Ubuntu in any way, shape, or form) and the android gui environment.
Looking at some process stats, it appears that webtop runs at about half the priority of the Dalvik stuff. Maybe the answer to your perceived problem is just changing that.
There are already several projects in place to open up the webtop environment into a much more vanilla linux experience, without all the motorola lockdown. Check the dev forums.

[DEV][WIP][PoC] ClockworkMod Touch for TouchPad

So, I've been working on getting the new version of CWM that has onscreen controls, a battery meter, and more to work on the TouchPad. So far, I've gotten it to boot, flash, and all that jazz, but the touchscreen still seems to be a WIP. Also, adb seems to be broken atm. Besides that, it seems to be working alright. I kind of want to gauge interest before I go out and fix the bugs/release a build.
Anyways, here are some pictures of the new CWM (and inadvertently me at 5 AM.. no judgements haha).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Notice the on-screen buttons (that don't work, yet...)
Finally, here's the battery meter
If I decide to keep going with this (hell, someone else should, too! I'm sure they could do it better, too heh), I'll start merging in some changes like USB notification and more. So..... any opinions?
larger text to fill the space ? make use of the space
i am afraid that i will make a mess of the setting by touching the screen, anyway thanks~
There's definitely interest. On the Touchpad my recovery of choice is TWRP, but since that's been discontinued and in its current state a little buggy I still use CWM. This would have the best of both worlds.
I'm going to go in the opposite direction of the other suggestion thus far and say shrink the buttons a bit, if possible.
Agreed I am certainly interested, much nicer then having to use the volume buttons....
Well, to finish this, I would have to tear apart TWRP's source hoping they have touch input in their code (the GUI code isn't public). Also, I would probably have to spend a few days bug fixing and actually fixing code instead of just commenting out stuff our device doesn't have (/datadata). It seems like it'd be a bit much, but once again, if more than 4 people say they'd want it, I'd do it haha. I'm just a CS college kid in midterms week so time is decently valuable, I guess heh.
EDIT: I felt bad because I feel like I sounded like I devalued the 4 responders; I don't and hope I didn't come off that way!
I wouldnt mind have a taste of cwm touch.
Is this the version of cwm that TWRP team helped with? (after they dropped their recovery project and started helping cwm's development).
I read they were planning to start help cwm with touch but i didnt see the implementation yet.
What do you think about using 4EXT Recovery instead?
http://forum.xda-developers.com/showthread.php?t=1402820
I'm definitely down for this.
CwM certainly does what it was design to do. I've been using it since I got hold of MyTouch3g and Donut. It hasn't changed. That said, it's time for a transformation. I think I read on another forum that there will be some changes to CwM soon. I don't know if you are part of that crew. Anyway, please move forward with this project.
Well I have midterns until next Monday, so I'll be busy, but if you want, I can release an alpha after testing it to see if basic functionality isn't broken? That means it'll have backup/restore, partition wipe, USB mounting, battery status, and zip installation. Anything else needed for an alpha?
Also, our touch screen drivers appear to be userland-based. To the average person, that means they're not in the kernel so I'll have to look into implementing that driver into CWM's source. Once that works, we should be golden. Also, I really want to add features like screen shut off if not touched for a minute or so. That should help with battery usage in CWM, I believe.
Thanks for the support and if you have anything to add/an idea/feature request/help, I'd love to hear it all!
DKMikey said:
What do you think about using 4EXT Recovery instead?
http://forum.xda-developers.com/showthread.php?t=1402820
Click to expand...
Click to collapse
+1 4ext is teh shizza
I think the aesthetics and additional functionality can follow. Getting touch to work with whatever is currently in CwM is more important.
I liked TeamWin's recovery, but since it's currently not being developed... oh well...
I have a fairly stable A0.5 and i don't plan on making any changes other than a kernel update or two. I have some time to test and give feed back.
Just a quick note (I'm currently in class and can't talk too much), but 4ext is closed source. Also, does anyone know if TWRP has been abandoned? As in, they'd probably be alright with open sourcing their GUI? Maybe? Bueller?
Smith7018 said:
Just a quick note (I'm currently in class and can't talk too much), but 4ext is closed source. Also, does anyone know if TWRP has been abandoned? As in, they'd probably be alright with open sourcing their GUI? Maybe? Bueller?
Click to expand...
Click to collapse
Didn't know 4ext was closed source, too bad. Twrp was abandoned but idk if its open source either... drop em a line
You could try talking to DooMLoRD or Napstar, they are working on touch based cwm for a few devices.
http://www.xda-developers.com/andro...abled-recovery-for-kindle-fire-and-htc-flyer/
http://www.xda-developers.com/andro...-touch-enabled-recovery-on-even-more-devices/
Is there an update on this? I see there is a release version on other devices.
- Sent from my TouchPad
you should make the navigation buttons bigger.
I'd love this. Please continue working on it
Sent from my HP Touchpad using XDA Premium
This would be amazing to have on my TP!!

New Nexus Program/Android 4.2

http://pulse.me/s/dVRNm
Looks like greatness is coming soon...
New Nexus with 4.2, Open Nexus Program Possible and Android 5.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Change we can depend on!! Lol jokes aside looks interesting, Idk about changing the home screens but who knows it may be better
Sent from my ADR6425LVW using xda app-developers app
Squirrel1620 said:
Change we can depend on!! Lol jokes aside looks interesting, Idk about changing the home screens but who knows it may be better
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
I like the part about better power management and the overall new Nexus Program.
Sounds good to me. There are definite GUI improvements that could be made. Not sure about "tabs" but anything is worth looking at.
Lastly, there is a chance that we see some sort of a “customization center” that allows you to choose from a stock Android experience or a custom skin from the manufacturer of the phone (Sense from HTC, Blur from Motorola, TouchWiz from Samsung, etc.).
Click to expand...
Click to collapse
Awesome. I REALLY like that part. Sounds like a move to address the fragmentation issue??
badogg said:
Awesome. I REALLY like that part. Sounds like a move to address the fragmentation issue??
Click to expand...
Click to collapse
Yes that idea sounds amazing but I wonder how they'll implement that.
Po1soNNN said:
Yes that idea sounds amazing but I wonder how they'll implement that.
Click to expand...
Click to collapse
Well, If they could make it cloud based where you can just download the skin you want and it will remove the existing it could work. Plus each manufacturer would be responsible for driver implementation on that hardware. It could work nicely I think.
badogg said:
Well, If they could make it cloud based where you can just download the skin you want and it will remove the existing it could work. Plus each manufacturer would be responsible for driver implementation on that hardware. It could work nicely I think.
Click to expand...
Click to collapse
Either that or they could use part of that 64gb required on all new Nexus phones.
It says 64mb not 64gb :-\
They must include a stock Android experience and 64MB of secure memory for media streaming.
Click to expand...
Click to collapse
I saw this yesterday and almost crapped my pants because it was so awesome. No longer will we be stuck with one phone as a nexus phone that has sub-par hardware or have to chose a device with a skin we hate because it has better hardware. I didn't see this but I'm assuming for it to be qualified as a Nexus device it has to have an unlocked bootloader.
Good things are coming soon guys
Po1soNNN said:
Either that or they could use part of that 64gb required on all new Nexus phones.
Click to expand...
Click to collapse
That's 64MB, not GB, and it's part of RAM. It's to be used for caching protected content like movies so you can't rip/save streaming content. And it's a bad thing, a lockdown mechanism, a concession to the phone and media companies and protection for Google Play's bottom line.
In fact, I see most of the aspects of this "Nexus Certification" concept as negative and have a very bad feeling about how this will turn out. True Nexus devices have all their hardware drivers and software written by Google, barring some binary pieces. Unfortunately they likely don't have the resources to handle such a differing hardware strata. This may put control back into the manufacturers' hands, meaning:
Poorly written software (and after seeing HTC's custom source, I'll never buy a device with HTC-written software again)
Slow updates or no updates
Delayed stock android. I wouldn't be surprised it it ends up as a "promised" or optional update to be delivered later, and phones end up shipping with proprietary frameworks.
MaulingDeOso said:
That's 64MB, not GB, and it's part of RAM. It's to be used for caching protected content like movies so you can't rip/save streaming content. And it's a bad thing, a lockdown mechanism, a concession to the phone and media companies and protection for Google Play's bottom line.
In fact, I see most of the aspects of this "Nexus Certification" concept as negative and have a very bad feeling about how this will turn out. True Nexus devices have all their hardware drivers and software written by Google, barring some binary pieces. Unfortunately they likely don't have the resources to handle such a differing hardware strata. This may put control back into the manufacturers' hands, meaning:
Poorly written software (and after seeing HTC's custom source, I'll never buy a device with HTC-written software again)
Slow updates or no updates
Delayed stock android. I wouldn't be surprised it it ends up as a "promised" or optional update to be delivered later, and phones end up shipping with proprietary frameworks.
Click to expand...
Click to collapse
Oh wow I totally misread that ram part. Sounds awful.
MaulingDeOso said:
Poorly written software (and after seeing HTC's custom source, I'll never buy a device with HTC-written software again)
Click to expand...
Click to collapse
You know, I take this back. By coincidence I just happened on an old newsgroup post: http://article.gmane.org/gmane.linux.ports.arm.omap/55060 where Linus blames everyone for just such a problem.
It's disheartening how these companies just slap together enough to get things working and leave it at that. I can't see any of them doing any more than the bare minimum to get their devices certified, and they'll lack the foresight and effort the Google programmers put towards a single device for certain.
If ownership does become each manufacturer's responsibility, I wonder if we'd lose more things that would be too much of an inconvenience for them, like the Nexus program's timely source code releases.
MaulingDeOso said:
You know, I take this back. By coincidence I just happened on an old newsgroup post: http://article.gmane.org/gmane.linux.ports.arm.omap/55060 where Linus blames everyone for just such a problem.
It's disheartening how these companies just slap together enough to get things working and leave it at that. I can't see any of them doing any more than the bare minimum to get their devices certified, and they'll lack the foresight and effort the Google programmers put towards a single device for certain.
If ownership does become each manufacturer's responsibility, I wonder if we'd lose more things that would be too much of an inconvenience for them, like the Nexus program's timely source code releases.
Click to expand...
Click to collapse
But really isn't that kind of how business works? Get people to pay as much as possible for something that you can produce as cheap and efficient as possible? Not making excuses for them, but I get the drive to feed the bottom line $$$
badogg said:
But really isn't that kind of how business works? Get people to pay as much as possible for something that you can produce as cheap and efficient as possible?
Click to expand...
Click to collapse
Of course. But up until this point we at least had a true Nexus device that we were sure at least had decent software on it (by virtue only of my opinion ). That was always a last bastion of properly written code. You could buy a device which ran it, or could look to it in order to see how things were intended to be done. It was written both for operation and for reference, and that made it higher quality than something written solely for profit.
MaulingDeOso said:
Of course. But up until this point we at least had a true Nexus device that we were sure at least had decent software on it (by virtue only of my opinion ). That was always a last bastion of properly written code. You could buy a device which ran it, or could look to it in order to see how things were intended to be done. It was written both for operation and for reference, and that made it higher quality than something written solely for profit.
Click to expand...
Click to collapse
Ah, got it. So if they did this with the next Nexus device, then the only way that it would be good is if it went through an approval process by Google to verify quality control? Sounds good to me!

HELP Cell Standby Drainig battery

Ok i have seen this topoc below bit lost it and mine case was different thats why i started a new thread
I have a i777 phone which has no imei and no baseband so sim doesnt work. So i usually have it in aeroplane mode to save battery but when i go to battery usage the cell standby has the highest battery usage . So its beyond me whh is the radio using up so mucb battery while m in ofline mode. So either someone tell me whats the problem or tell me how to shut down the cellstandby driver/service
I have stock 2.3.4 with root and entropys kernal
Thanks
Will post screen shot after an hour
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
Ok someone tell me how to completely remove the cell standy. I am gonna use this phone jst as an ipod
Any help will be appreciated thanks
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
Airplane mode.
If you want to go deeper than Airplane Mode, you will have to create a customized firmware for it. Here is a link to a thread in the Captivate (SGH-i897) forum about turning the captivate into something like an Ipod Touch. It may give you and idea of what would be involved.
creepyncrawly said:
If you want to go deeper than Airplane Mode, you will have to create a customized firmware for it. Here is a link to a thread in the Captivate (SGH-i897) forum about turning the captivate into something like an Ipod Touch. It may give you and idea of what would be involved.
Click to expand...
Click to collapse
I exactly wanted to do that, but I am no developer, I wish someone could do that
I would have done it myself if I had the knowledge
isn't there a simple way so that they cell standby wont even get started and just disappears
nomiko said:
I exactly wanted to do that, but I am no developer, I wish someone could do that
I would have done it myself if I had the knowledge
isn't there a simple way so that they cell standby wont even get started and just disappears
Click to expand...
Click to collapse
No, but if you have the time, following that thread would be a good way to get into light development. Essentially, all you have to do is take someone's existing firmware distribution, and do some relatively easy modifications. You would have to learn the tools and how to use them. If you can contact the author of that thread, he said he is willing to show someone what modifications to make. It may still apply on our phone.
Problem is that if someone doesn't have an interest, they are not going to do something for someone else. Maybe if you offered a bounty, someone might take it up.
creepyncrawly said:
No, but if you have the time, following that thread would be a good way to get into light development. Essentially, all you have to do is take someone's existing firmware distribution, and do some relatively easy modifications. You would have to learn the tools and how to use them. If you can contact the author of that thread, he said he is willing to show someone what modifications to make. It may still apply on our phone.
Problem is that if someone doesn't have an interest, they are not going to do something for someone else. Maybe if you offered a bounty, someone might take it up.
Click to expand...
Click to collapse
Hahahaha well said ,I agree, well if its easy then I might be able to do it, and if it was difficult then well thats that, well I have sent a pm to him let c what he has to say... I hope its a small modification. I will try to give it a shot
Sent from my LT26i using Tapatalk 2
nomiko said:
Hahahaha well said ,I agree, well if its easy then I might be able to do it, and if it was difficult then well thats that, well I have sent a pm to him let c what he has to say... I hope its a small modification. I will try to give it a shot
Sent from my LT26i using Tapatalk 2
Click to expand...
Click to collapse
I'll give whatever support I can. I don't know the tools real well, but I've played with some of them a little, and I do know some windows programming and some other stuff.
Edit: Did a little looking around. You probably will not hear back from the original poster as he appears to be inactive on xda for most of the last year. Here is his original thread which has basic instructions for removing the phone components on the Captivate. This might work on this phone. I think the second thread was to make the interface more pretty.
creepyncrawly said:
I'll give whatever support I can. I don't know the tools real well, but I've played with some of them a little, and I do know some windows programming and some other stuff.
Edit: Did a little looking around. You probably will not hear back from the original poster as he appears to be inactive on xda for most of the last year. Here is his original thread which has basic instructions for removing the phone components on the Captivate. This might work on this phone. I think the second thread was to make the interface more pretty.
Click to expand...
Click to collapse
I never did listen from him as u said. Hmmn but i did visit this thread and did as he did which was quite very simple to be honest. I deleted the phone and telephony apk and csc file. And all other files which were related to phone activities in one or other way.
And well with that the cell stand by went away...
Now i get yellow phone signals
Anyways their is mo cell standby in battery drain
But all is not well i get kernel wakelocks which are keeping my phone awake and draining battery like hell when in standby or screen off...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
How do i get rid of this svnet
Svnet i read this wakelock gets active for 6 secs when the phone is looking searching for signals.
And also do anyone know how to uninstall the modem in my phone thanks
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
Uninstall the modem or flash a new one? You can turn air plane mode on if you want to turn off signal and data when you're in a bad coverage area.
Airplane mode not an option...
How to uninstall the modem.....
Sent from my LT26i using Tapatalk 2
nomiko said:
Airplane mode not an option...
How to uninstall the modem.....
Sent from my LT26i using Tapatalk 2
Click to expand...
Click to collapse
Just flash the new one over it in cwm. It replaces the one currently there everytime you flash a new one.
Sent from my SGH-I777
r_diaz13 said:
Just flash the new one over it in cwm. It replaces the one currently there everytime you flash a new one.
Sent from my SGH-I777
Click to expand...
Click to collapse
It will also flash the modem which I dont want to install, In my i777 imei is null so modem does not do me any good. N one more thing if I dont install modem. Wifi will still work right
Sent from my LT26i using Tapatalk 2
On shostock3 i get boot_hsic kernel wakelock.... Which is drainig the battery . N not letting the device goto deep sleep. N making it constantly run at 200mhz -_- help
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2

[**ATTENTION DEVELOPERS**] Bootloader Unlock

We are over $2300 for a bootloader unlock. I am curious is there anyone out there who has attempted any work on this goal yet?
samg77 said:
We are over $2300 for a bootloader unlock. I am curious is there anyone out there who has attempted any work on this goal yet?
Click to expand...
Click to collapse
Samsung galaxy s5 hit 18k before an unlock but money shouldn't make to much of a difference I'm sure the people who brought us root are working on it though
They recently fixed some twrp stuff for the D851, just hoping they're next target is unlocking bootloaders but only time will tell
Following them on twitter you'll find more info and updates than asking for it on an xda post
Sent from my VS985 4G using XDA Premium 4 mobile app
bunchies said:
Samsung galaxy s5 hit 18k before an unlock but money shouldn't make to much of a difference I'm sure the people who brought us root are working on it though
They recently fixed some twrp stuff for the D851, just hoping they're next target is unlocking bootloaders but only time will tell
Following them on twitter you'll find more info and updates than asking for it on an xda post
Sent from my VS985 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ya I stopped buying Samsung, because it took 18k to root the damn thing, way to locked down, kills the fun. But being over $2300 in just over 11 days isn't too bad. That Samsung bounty went for a very long time. There were also a few people who individually pledged huge amounts of money. I really loved the specs for the S5, and the battery life.
That is until I heard about the LG G3. This phone is amazing. You know how a phone no matter how good it is, always has just one major fault? Sadly the only thing keeping the G3 from being the "perfect" phone is the QHD screen. Although I consider it a fault, this is also a plus, I would much rather have 1080p and the extra screen battery time, thank god for my extra batteries and charger, I swear I get total phone anxiety paranoia if I don't have a removable battery. However I am getting 35-40 hours between charges, but thats only when I have about 3 hours screen time in that span. I run at 50% brightness, and the screen gulps battery. Other than that the battery is amazing! This is without using ART too. This thing would last days without the QHD screen.
Did anyone ever figure out what apps needed to be freezed to get ART functioning?
I wonder if Adam Outler would be willing to look at this phone.
samg77 said:
Ya I stopped buying Samsung, because it took 18k to root the damn thing, way to locked down, kills the fun. But being over $2300 in just over 11 days isn't too bad. That Samsung bounty went for a very long time. There were also a few people who individually pledged huge amounts of money. I really loved the specs for the S5, and the battery life.
That is until I heard about the LG G3. This phone is amazing. You know how a phone no matter how good it is, always has just one major fault? Sadly the only thing keeping the G3 from being the "perfect" phone is the QHD screen. Although I consider it a fault, this is also a plus, I would much rather have 1080p and the extra screen battery time, thank god for my extra batteries and charger, I swear I get total phone anxiety paranoia if I don't have a removable battery. However I am getting 35-40 hours between charges, but thats only when I have about 3 hours screen time in that span. I run at 50% brightness, and the screen gulps battery. Other than that the battery is amazing! This is without using ART too. This thing would last days without the QHD screen.
Did anyone ever figure out what apps needed to be freezed to get ART functioning?
I wonder if Adam Outler would be willing to look at this phone.
Click to expand...
Click to collapse
Well I've heard it's only among Verizon variants so probably a Verizon app that's causing it, I wanna know what type of crash it is
And even if ART worked, I couldn't use it yet. I use apps that have compatability issues
It's easy to debug an error, if I had a recovery I would take the fall and see what's causing issues on ART for us but I've already had to factory reset once and I don't wanna do it again
Sent from my VS985 4G using XDA Premium 4 mobile app
Lets See What We Can Do
Ok well I have seen some posts from different people about various RE skills so lets get to work and do this thing. I have done this kind of thing before but have never pulled apart an android image. I know PBL boots SBL1 boots SBL2 and RPM but I do not know the addresses that these are loaded into and executed from. I have attached the SBL1.idc file that will create the IDA database for the SBL1. This needs to be base relocated to the correct address but that is an easy adjustment when we know where to put it.
One of the first things the SBL does is switch to various ARM modes (supervisor, fiq, irq, etc) and sets the stack pointer to 0xF8002000 from there is branches off to 0xF8041F00 (thumb) but since I do not know the memory map I cant track that down. Also it looks like there is some relocation code in there. Code that copies chucks to other locs. There also appears to be some signatures near the end of the file.
If anyone can help me flesh out the database that would awesome. Even loading addrs info would be great. By the way their are a ton of juicy strings in there , this makes the process of RE much easier.
N.B.
I did not create the Stack segment yet as I want make sure this is loaded to the correct address first. There may be some gaps in code still (like the very middle, but I think that is all supposed to be relocated) but it is mostly all disassembled.
Anyone seen this yet?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://twitter.com/utoprime
Colchiro said:
Anyone seen this yet?
https://twitter.com/utoprime
Click to expand...
Click to collapse
link please
oneandroidnut said:
link please
Click to expand...
Click to collapse
Just a pic on twitter so far. The link is there below the picture, look again.
Colchiro said:
Anyone seen this yet?
https://twitter.com/utoprime
Click to expand...
Click to collapse
This is amazing news, if real. Let the G3 custom ROMs flow!
giri0n said:
This is amazing news, if real. Let the G3 custom ROMs flow!
Click to expand...
Click to collapse
Considering Autoprime reposted it, I consider it good enough.
This is some very promising news! Fingers crossed!
I'll be the first to say.. My Body is Ready
me too man
I've read and re-read the Fast Boot method to TWRP for the International G3 and I'm ready for when this drops for us.
Hopefully the time that we all have waiting for this others on Verizon do the same since it's not as easy as just a button combo,!
- Sent From My G3
Mistertac said:
I've read and re-read the Fast Boot method to TWRP for the International G3 and I'm ready for when this drops for us.
Hopefully the time that we all have waiting for this others on Verizon do the same since it's not as easy as just a button combo,!
- Sent From My G3
Click to expand...
Click to collapse
I wonder if someone like Savoca could create a custom bootloader that we could replace the stock one with completely to just do whatever we want.
PWn3R said:
I wonder if someone like Savoca could create a custom bootloader that we could replace the stock one with completely to just do whatever we want.
Click to expand...
Click to collapse
LOL yeah good luck with that. it isnt that simple
OMG!!! So excited, the beta tester autoprime RTed said its coming very shortly
What is coming very shortly? Custom or tethered boot loader?
Sent from my VS985 4G using Tapatalk 2
WeThePeople13 said:
What is coming very shortly? Custom or tethered boot loader?
Sent from my VS985 4G using Tapatalk 2
Click to expand...
Click to collapse
I can't find what he was talking about, on twitter they were talking about unbricking an s3
Sent from my VS985 4G using XDA Premium 4 mobile app
WeThePeople13 said:
What is coming very shortly? Custom or tethered boot loader?
Sent from my VS985 4G using Tapatalk 2
Click to expand...
Click to collapse
Tethered I believe

Categories

Resources