android
Go Back   abi>>forums > MP3 Players By Brand > Samsung > Samsung Galaxy Player Series

Reply
 
Thread Tools Search this Thread Display Modes
  #241  
Old 05-05-2013, 07:13 AM
zacp2 zacp2 is offline
Member
 
Join Date: Aug 2011
Location: Montreal, QC
Posts: 239
Default

Quote:
Originally Posted by scowl View Post
Here's how you destroy your SGP 4.0 (US only).

The International recovery ROMs contain two interesting files: boot.bin and sbl.bin. I know sbl.bin is the secondary bootloader and I'm guessing the first is most likely the bootloader. Flash that ROM and you now have completely recovered your non-US SGP4.0.

Guess which two files are nowhere to be found on any of the US recovery ROMs. That's right, boot.bin and sbl.bin. That means if you want to recover your US SGP 4.0 after stupidly flashing an International version, it isn't going to happen. Ever. Your touchscreen and capacitive keys will never be initialized properly.

So don't do that. There is a thread on xda about this from a year ago with no solution.
Well this is to be used in case of extreme emergency like with a hard brick. The reason of why there's no bootloader for the us device is because they never received a full update via Kies, so they're stuck with the basic files...

Sent from my Nexus 7 using Tapatalk HD
Reply With Quote

Advertisement [Remove Advertisement]

  #242  
Old 05-05-2013, 11:19 AM
scowl scowl is offline
Member
 
Join Date: Oct 2006
Location: Portland, OR
Posts: 350
Default

Quote:
Originally Posted by zacp2 View Post
Well this is to be used in case of extreme emergency like with a hard brick. The reason of why there's no bootloader for the us device is because they never received a full update via Kies, so they're stuck with the basic files...
Yeah, the "[STOCK ROM] Full Recovery For Samsung Galaxy Player" thread at xda-developers is misleading because the US versions posted in it aren't really full recovery ROMs. I'd post something in the thread but I don't need a bunch of teenagers telling me how stupid I already know I am.

The only option is for me to try to reverse-engineer the initialzation of the US capacitive keys and the touchscreen and add this to a new kernel. Normal Linux kernels are completely responsible for initializing all devices. Android kernels obviously let the bootloader do this (it is probably propreitary to the manufacturer anyway) so they're stuck with whatever the devices do once the kernel starts executing.

I can see this with CWM recovery's key test function which simply doesn't see the capacitive key events at all which means the device is simply not enabled. If anyone happens to know which driver in the kernel the SGP 4.0 uses for these events, I could quickly attempt to make a kernel that works.

CWM recovery does use the power key for "Enter" so I did get something to work.
Reply With Quote

  #243  
Old 05-10-2013, 12:50 PM
scowl scowl is offline
Member
 
Join Date: Oct 2006
Location: Portland, OR
Posts: 350
Default

I complied Steve's kernel (very easy!) with some debugging prints and determined that the device driver for the touchscreen flashes firmware to a chip when it loads. Unfortunately it looks like it gets the firmware from somewhere in the bootloader area (it may be proprietary to Samsung). The data in this area is now wrong on my device for the U.S. kernel so the driver immediately fails and doesn't load. That's why my touchscreen on my device does nothing with U.S. kernels.

But it does work upside down with Euro kernels so if I have nothing better to do, I'll try to get the device driver in a Euro kernel to work right side up. I can't wreck the device any worse so I might as well learn some Android kernel development.

I don't understand the buttons yet. The buttons are the only define change between Steve's US and Euro kernels so it seems like they should work with a U.S. kernel assuming they're TOTALLY different from the touchscreen. It's possible that it doesn't bother activating the buttons when the U.S. driver fails to flash the touchscreen chip.
Reply With Quote

  #244  
Old 08-03-2013, 09:13 PM
maarij maarij is offline
Junior Member
 
Join Date: May 2007
Posts: 17
Default

Is this the best kernel still for the YP-G1? I'm gonna avoid the rom as I prefer just the hardware related boosts.
Reply With Quote

  #245  
Old 08-04-2013, 03:36 AM
Daniel644 Daniel644 is offline
Member
 
Join Date: Nov 2011
Posts: 475
Default

Quote:
Originally Posted by maarij View Post
Is this the best kernel still for the YP-G1? I'm gonna avoid the rom as I prefer just the hardware related boosts.
Not for well over a year now, infact we actually have a Cyanogen Mod 10.2 (android 4.3 Jellybean) available now, but even if you want to keep to gingerbread you'll want to get the Terrasilent kernel. Truthfully it was never "the best" just the First, don't get me wrong it was an important step and the second gen of stuff was based off it, but we are so much further along now.

CM 10.2: http://forum.xda-developers.com/show....php?t=2386992

Terrasilent: http://forum.xda-developers.com/show....php?t=1643384 Even Terrasilent is over a year old now, but it is much better then Steves and some people are reporting issues with flashing the newer ROMs using Steves but not having issues when using Terrasilent, it is considered the kernel to be on if on gingerbread, plus it has a cool Doctor Who splash screen.
__________________
Galaxy S 4.0 Wifi (USA)
Running STeVEs custom Kernel
and Klin's Klassic 2.3.6 ROM for Galaxy Player 4.0 USA
Reply With Quote

Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump



All times are GMT -5. The time now is 07:08 AM.