Related
Am I missing something on this new WP7 ROM that's been leaked.
All this trouble trying to get the ROM working on a HD2, hasn't Tom Codon already shown a WP7 on HD2 and said it's running? If that the case then why isn't he sharing how he managed to do it without this Jtag thing.
Or has he now been proven a liar?
Logicalstep
Well, as far as I remember he did it using that JTAG thing and somewhere in the new thread it was mentioned that he used a different (older) ROM as a basis, so drivers, etc. might be different.
The reason for needing JTAG is, that until it flashes correctly we most likely will brick the device several times - using JTAG means we don't have to be a new HD2 for every attempt (which is indeed more cost effective).
If Tom managed to do it then or not is still to be seen.
How can somebody still think that it wasn`t fake? Tom is not active even on his forum /htcpedia/...
Alright, well since the 8gb version of the nook tablet just came out, If people use the same files, it could possibly brick the device and we can't have that. This is why I think the device will need it's own subsection under the the Nook Tablet forums. I just don't want to deal with the constant complaints of people bricking because they can't listen. :|
Indirect said:
Alright, well since the 8gb version of the nook tablet just came out, If people use the same files, it could possibly brick the device and we can't have that. This is why I think the device will need it's own subsection under the the Nook Tablet forums. I just don't want to deal with the constant complaints of people bricking because they can't listen. :|
Click to expand...
Click to collapse
Supposedly, they changed the hardware device ID, which means that despite looking the same as a Nook Tablet 16GB, and the Nook Color, it is in fact at least partially different hardware.
So, yeah, I don't see why it should be lumped in the same as the NT16...
-----
Looking through the source for 1.4.2, they appear to be running all the same software. So, I'm going to retract... it appears that everything will be functionally identical. Fortunately, the NT8 isn't booting with our current NT16 images, which is kind of a good thing, as it reduces the chances of bricking. This also means that supporting both with the same XDA codebase shouldn't be hard either... after all, they're going to both use identical 2nd uboots...
If the only changes are to RAM and Drive space, B&N will probably base future updates around flashing to both devices. Meaning that a subsection could just cause clutter. Until we know whether or not older updates are even flashable to the newer devices, causing an issue, we should perhaps hold off on a subsection.
Considering newer update methods compared to the older Nook Originals which the issue was seen on in the first place (they updated hardware, but didn't put in checks to stop an older version from being flashed). With different hardware IDs this may be a Moot Point until someone actually tries it.
Its well known that the D720 has a crappy radio. I'd like help researching radio images with the intent of developing replacement radio/baseband software. I'll keep this post updated with discoverys, insights and information about the radio.
Radio Description
The Radio firmware is actually a set of operating systems that runs on the phones physical processor. This includes a "Microvisor" (Think, Xen Dom0) and a set of Operating systems that run on it (Think Xen DomU). The microvisor for the D720 is NICTOKL4, The full version string is:
NICTOKL4 - (provider: Open Kernel Labs) built on May 19 2009 00:21:02 using gcc version 3.4.4.
The radio is loaded by NICTOKL4 as is androids boot code. The exact process is unknown, but I speculate that fastboot and the radio are started at the same time, and fastboot executes what needs to be run on the android side, while the radio waits to be initialized externally.
The radio can preempt Android, and has real time priority. The radio itself is a small part of radio.img
Theories
I've read in several places that Deep Idle really doesn't work, And I'd like to speculate as to why in the hopes it will help someone else.
Since the Radio requires real time priority, and halting a CPU and bringing it back up is an expensive process, it cannot be allowed. I speculate that the lack of savings from Deep Idle is because the radio keeps running while android (because of the microvisor) thinks the CPU is halted.
This apparently does not apply to GSM models.
Other Information
The radio appears to be unencrypted, which is strange considering its almost always encrypted.
Android is a Guest OS in a virtualized phone.
So is the radio.
The radio and baseband that most people think of, Is mostly software. Its no different than any other embedded device. Just because it does things with the hardware, doesn't mean that its implemented in hardware.
Recent Discoveries
GSM Models have a separate baseband processor that is responsible for handling AT Commands, phone calls, SIM interaction, etc.
What is the "baseband" software image responsible for on GSM Models? Why is it run as an OS, instead of being implemented in the RIL libs?
Thanks
Harbb - For the delightful discussion regarding the inner workings for the radio, You say you know less than you do, and your challenging my theories and pointing out errors helps me further not only this cause, but my own knowledge as well. I appreciate it.
Interesting. I'm going to be keeping an eye on this for sure
Sent from my Nexus S 4G using xda premium
plaguethenet said:
Its well known that the D720 has a crappy radio. I'd like help researching radio images with the intent of developing replacement radio/baseband software. I'll keep this post updated with discoverys, insights and information about the radio.
Radio Description
The Radio firmware is actually a set of operating systems that runs on the phones physical processor. This includes a "Microvisor" (Think, Xen Dom0) and a set of Operating systems that run on it (Think Xen DomU). The microvisor for the D720 is NICTOKL4, The full version string is:
NICTOKL4 - (provider: Open Kernel Labs) built on May 19 2009 00:21:02 using gcc version 3.4.4.
The radio is loaded by NICTOKL4 as is androids boot code. The exact process is unknown, but I speculate that fastboot and the radio are started at the same time, and fastboot executes what needs to be run on the android side, while the radio waits to be initialized externally.
The radio can preempt Android, and has real time priority. The radio itself is a small part of radio.img
Theories
I've read in several places that Deep Idle really doesn't work, And I'd like to speculate as to why in the hopes it will help someone else.
Since the Radio requires real time priority, and halting a CPU and bringing it back up is an expensive process, it cannot be allowed. I speculate that the lack of savings from Deep Idle is because the radio keeps running while android (because of the microvisor) thinks the CPU is halted.
Other Information
The radio appears to be unencrypted, which is strange considering its almost always encrypted.
Android is a Guest OS in a virtualized phone.
So is the radio.
The radio and baseband that most people think of, Is mostly software. Its no different than any other embedded device. Just because it does things with the hardware, doesn't mean that its implemented in hardware.
Click to expand...
Click to collapse
This is very interesting I hope you can get this up & going for us Nexus S4G users! & I live in Worcester myself
Sent from my Nexus S 4G using xda premium
Nice, MA FTW I am in Malden lol.
oh man id do ANYTHING to actually have reliable service with the phone hahah 1 bar inside maybe 2 outside... good luck guys! i hope its a smooth ride whatever this may be lol
Lol Salem. MA here baby
Sent from my Nexus S 4G using Tapatalk
adamw1101 said:
Lol Salem. MA here baby
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
rasengan82 said:
Nice, MA FTW I am in Malden lol.
Click to expand...
Click to collapse
Killasmoke said:
This is very interesting I hope you can get this up & going for us Nexus S4G users! & I live in Worcester myself
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Holy crap, Alot of MA Users. We should have a phone meetup someday
Also, Killasmoke:
It will be a rather tedious process, as this is like, trying to reverse engineer the NT Kernel. I'm not saying its impossible, but its highly complex, and nearly completely undocumented (Or in our case, COMPLETELY undocumented) I hope I can do something too, but I'll need more insight from other hardware hackers as well. There is alot to be reverse engineered here.
I was just thinking today about how my TMobile galaxy s handled data much more efficiently than sprint. I could talk while surfing the web over 3g and never any buffering or loading on Pandora (now it's between every song).
You without me is like Harold Melvin without the Blue Notes...
plaguethenet said:
The full version string is:
NICTOKL4 - (provider: Open Kernel Labs) built on May 19 2009 00:21:02 using gcc version 3.4.4.
The radio appears to be unencrypted, which is strange considering its almost always encrypted.
Android is a Guest OS in a virtualized phone.
So is the radio.
Click to expand...
Click to collapse
So, that message means it was compiled with gcc, is the radio itself open source? Are there other sample radios to base work off of? If it's unencrypted, can it be decompiled relatively easily?
At any rate, saying it can be built with gcc at least means it has the potential to be built by anyone with the proper environment and source.
Any updates yet?
Bruce lee roy said:
I was just thinking today about how my TMobile galaxy s handled data much more efficiently than sprint. I could talk while surfing the web over 3g and never any buffering or loading on Pandora (now it's between every song).
You without me is like Harold Melvin without the Blue Notes...
Click to expand...
Click to collapse
Different radio and technology. GSM Inherently supports simultaneous voice and data, CDMA does not. Thats merely a difference in the radio software and hardware.
A good way to think of the two is HTTP vs FTP.
Both work over TCP/IP, and both do similar (albeit different) things. (Serve files)
How they go about serving those files, and how the client gets those files is different. That's more or less the difference between CDMA and GSM (UMTS Really). They use different radio bands and a different protocol to accomplish the same thing. Just like how HTTP and FTP use different ports and different protocols to do the same thing.
Also, HSDPA and HSDPA+ Are much faster than 1xRTT and EvDo
mondokat said:
So, that message means it was compiled with gcc, is the radio itself open source? Are there other sample radios to base work off of? If it's unencrypted, can it be decompiled relatively easily?
At any rate, saying it can be built with gcc at least means it has the potential to be built by anyone with the proper environment and source.
Any updates yet?
Click to expand...
Click to collapse
Before disassembly, i'd have to split the binaries apart. (Extract OEMSBL, SBL, PBL and AMSS.BIN from Radio.img) then I could disassemble them. I wonder if ODIN Images are any different. It may be worth looking at and i'll see what I can dig up.
In hindsight, Some of the bootloaders may be in bootloader.img. I'm pretty sure bootloader.img is just fastboot and Samsung's boot software, Worth looking into.
It is and is not open source. K4 is a Microkernel (Very similar to, if not based on, MACH). It can be built with GCC. The radio itself is seperate from NICTOKL4, NICTOKL4 is just a hypervisor. The radio runs underneath that, and so does android. In short, think of it this way. The radio software, and Android are just programs running on an operating system. NICTOKL4 is that operating system.
I'll be following this, I've never had good reception at all with any radio...
Wow, nice. If I'll be able to contribute with my knowledge at any point, I'll be sure to pitch in. Good luck.
how about baseband ??
and last stories about this thread,are i lost somethings ?
thanks for this. ill keep an eye out
I was recently contacted by an old friend to help with an issue. He was a victim of privacy invasion on his S4, hidden instances of webcam and phone cameras, exporting of personal information, etc. Now he has come to me for help. I have looked at his logs and whatnots, but nothing really stands out. So, I am wondering if any of you have experienced the same problem? If yes, please provide me a complete list of all the apps you have installed on your device. Since I do not own an S4, it is hard for me to create the issue. The only answer is to get this community to pool together and get me the device (which would allow me to dev for the S4 and bring the greatness of the Lightning Zap! kernel), or for you guys that have experienced it, to help me find a common link.
thomas.raines said:
I was recently contacted by an old friend to help with an issue. He was a victim of privacy invasion on his S4, hidden instances of webcam and phone cameras, exporting of personal information, etc. Now he has come to me for help. I have looked at his logs and whatnots, but nothing really stands out. So, I am wondering if any of you have experienced the same problem? If yes, please provide me a complete list of all the apps you have installed on your device. Since I do not own an S4, it is hard for me to create the issue. The only answer is to get this community to pool together and get me the device (which would allow me to dev for the S4 and bring the greatness of the Lightning Zap! kernel), or for you guys that have experienced it, to help me find a common link.
Click to expand...
Click to collapse
Is there any more info you can give about it? I haven't noticed anything personally, but I also haven't been looking.
Would be nice to see you here on the S4 there, pal.
lordcheeto03 said:
Is there any more info you can give about it? I haven't noticed anything personally, but I also haven't been looking.
Would be nice to see you here on the S4 there, pal.
Click to expand...
Click to collapse
Hey man! How goes it? I would love to have an S4 but it's just not in my budget right now...but at about 600 bucks (with no contract) who can afford it...lol
Although, I am up for my new every 2 upgrade... but it is for AT&T, and I'm not sure of the compatibility between the i9500, and the AT&T model (not sure of the exact model number).
As for the invasion of privacy issue, I'm trying to get more details on it. But I'm really thinking the malicious code started on his PC and drifted to his phone. And if it's the trojan I am thinking, then it attacks usb devices by making all the contents of that device hidden and appearing as if everything was deleted. Easy to get rid of, and easy to fix provided you have admin level access. Oh, and it was specifically made to attack Windows 7, but can leak out to other versions of Windows. Reason #1 to switch to Linux: Hackers HATE Windows and Bill Gates! lol
thomas.raines said:
Hey man! How goes it? I would love to have an S4 but it's just not in my budget right now...but at about 600 bucks (with no contract) who can afford it...lol
Although, I am up for my new every 2 upgrade... but it is for AT&T, and I'm not sure of the compatibility between the i9500, and the AT&T model (not sure of the exact model number).
As for the invasion of privacy issue, I'm trying to get more details on it. But I'm really thinking the malicious code started on his PC and drifted to his phone. And if it's the trojan I am thinking, then it attacks usb devices by making all the contents of that device hidden and appearing as if everything was deleted. Easy to get rid of, and easy to fix provided you have admin level access. Oh, and it was specifically made to attack Windows 7, but can leak out to other versions of Windows. Reason #1 to switch to Linux: Hackers HATE Windows and Bill Gates! lol
Click to expand...
Click to collapse
I mean, what were the indications? Like, what made your friend say "Man, I do believe my privacy is being invaded." You say nothing suspicious showed up in logs, the instances of camera and data exports, etc were all hidden... what gave the indication that it was happening?
A friend of mine recently had a very similar problem with his iPhone.
We quicly determined that the answer was that his phone was cloned using a scanner, which gave the bad guy power to hack into the device at the ESN level. Very hard to trace in any kind of logs, especially since the bad guy would have the ability to purge logs.
Your buddy might have someone similar. My friend was in Russian when this happened though, much less common in the US.
Skipjacks said:
A friend of mine recently had a very similar problem with his iPhone.
We quicly determined that the answer was that his phone was cloned using a scanner, which gave the bad guy power to hack into the device at the ESN level. Very hard to trace in any kind of logs, especially since the bad guy would have the ability to purge logs.
Your buddy might have someone similar. My friend was in Russian when this happened though, much less common in the US.
Click to expand...
Click to collapse
I asked him for more info and specifically what led him to believe this has happened. I am waiting for his reply. Here is th main snippet from his initial email:
I have been the victim of a very discreet but maddening invasion of privacy through my phone and also my PC and laptop computers via key logging, hidden instances of webcam and phone cameras, exporting of personal information, etc. I believe it to be a reoccurring problem via persistent data, local and cloud based storage, and corruption of my MBRs on most of my storage media. I know enough to be dangerous, but have yet to find any significant marker that points to faulty reflash process at least on my telephone.
Click to expand...
Click to collapse
He gave me some good logs, but I really don't have much to go on. With the statement about his MBR's, I think his computer was actually attacked and subsequently, his phone and possibly other usb devices have been compromised...
He has MBRs on most of his storage devices?
But I think he probably got Ratted on his computer, the guy controlling the computer saw he had an android phone and installed an android rat onto it when he plugged it in next.
Sent from my SGH-M919 using xda app-developers app
Hello,
I have a SM-P600 with Android 4.4.2 (Note 10.1 2014 Edition) and would like to use my 3G USB Key (Huawei E1752) ; This 3G stick works fine on my old TF101.
I've tried to use it with my SM-P600 but infortunetely, it doesn't seem to work, even with the "PPP Widget" apps. PPP Widget displays the famous "No driver found" issue. Josh, "PPP Widget" developer, told me ther eis no way for the moment to make his apps working because there is no loading module (.ko file).
So I wonder if I could use a SM-P601 ROM (SM-P600 with 3G) on my SM-P600 to get the right modules or flashinf P601 ROM on P600 means "brick"?
Otherwise is there another way to make a 3G USB key working on this tablet?
Best regards.
Unfortunately...
Part of the problem is that a custom kernel module would need to be loaded with root, via insmod, and this would need to be coded and constantly reinjected on boot. As far as I know most of these fobs do not make their drivers open-source, specifically, although I could see a possibility in modifying one of the generic drivers from a typical linux full install (likely heavily modified). Even with a ko/kernel module, however, it's possible that the fob might not be able to get enough power from the tablet, itself; I'm not sure what the power draw is, but I have a few laying around; I could probably check that later on.
All of that said, while it may be possible to try to hack something up to work with OTG (for instance I know it CAN be done with external network devices in general (there have been successful drivers built for external Alfa wifi usb-based adapters, but that's wifi), my suspicion is that even if 1) and 2) here were fulfilled, there'd need to be support in other ways built into the ROM itself (I'm wondering if a bunch of the code for this could be pulled from the existent 605 ROM though, which is a consideration). I'm not sure if, for instance, even if JB/KK on the Galaxy Note 2014 were to be made to recognize it, you wouldn't have to disable other things to make it work; I know for the external USB wifi devices, a hack was needed to disable the onboard wifi within the device.
If I had the time or the money I'd certainly be willing to try to make something custom in general. That said, I'm wondering if linuxonandroid (search the forums, or check out linuxonandroid.org) might support it out of the box on the full system img's (given functionality, Kali's kernel probably has the best chance of any of the current available ones, but I don't really know; I'm grabbing the image later on tonight to see what happens if I try)...
In general, though, I suspect that even if this somehow partially works, there are going to be a lot of problems that only a real custom ROM would solve. Though frankly, I can't figure out why nobody has yet. Maybe, like me, people just don't have enough time, and the people who do have time and the skill don't really need a specialized ROM enough.
I'm still kicking myself in the butt for not getting the 3G version for development purposes, personally; hundreds of dollars more for what one could get in a USB fob for 20-30 bucks only sounded like a bad deal til I wanted the functionality; your best bet may be to get a crapper of an android phone for under a hundred dollars and just let it be a hotspot. It's what I finally just gave in to doing. The one upside is decent battery life; if the P600 could supply enough power for the USB 3G dongle to work, all USB-dongled devices, to the best of my knowledge, kill batteries faster than anything built-in would.
Good luck.
Yes... You're probabably right. Don't know.
And I could use an old phone to be a hotspot or something else like that, but it's not what I want :cyclops: Just one device for all will be better.
Kasimodo said:
Yes... You're probabably right. Don't know.
And I could use an old phone to be a hotspot or something else like that, but it's not what I want :cyclops: Just one device for all will be better.
Click to expand...
Click to collapse
I'd really prefer the same thing, myself. I generally carry around a phone with my other stuff anyway and don't use it for much in the way of voice calls, so it's not too much of a burden. There's also hostapd in linux, or any of a number of mobile routers you can boot up in vbox, if you're carrying a laptop around at the same time; I really hate that our devices, and android in general, won't do 'ad-hoc' networks. I think that's one of my biggest gripes.
I suspect once Ubuntu touch is fully stable it'll be our best option; at a minimum I'm pretty sure I could easily crank out a driver for that. Android, I'm not sure. I'll let you know if I find the time to dig around with with droid though; I've been meaning to learn more about device driver support in Android anyway, now that it's finally pretty much mature.