As I have posted before, I have a script that uses wget to regularly pull a gif file off a server to check its status. This script worked when I was running Eugene's Vibrant9 ROM, but stopped when I installed Bionix Fusion 1.2. I am now running Nero v3, and it still does not work.
I initially suspected that the problem was with the version of wget, and that guided my investigations. But I have tried several wgets with the same results. To demonstrate, I've posted a test gif here:
http://216.97.237.135/tmp/test.gif
The gif is 544 bytes, but if I wget it from my phone over 3g I only get 308 bytes.
Further inspection has revealed that if I wget it from my phone over wifi I get all 544 bytes. In addition, if I tether my laptop to the phone using Mobile AP and wget from the laptop, I get 308 bytes. The problem is thus isolated to my 3g connection.
Given that it worked under a prior ROM, I now suspect that the problem is either the modem or the modem settings. Can someone suggest where I can find model settings that I might play with, or what different modems I might try installing (if that is even possible)?
I'm afraid that I find this issue fascinating yet frustrating, and I'm am running out of avenues to pursue. If I don't get any interest here, could someone suggest a different forum where the question might be of more interest? I'm posting here because I read this forum and there are a lot of smart people here, but this is a pretty narrow question....
Related
Well I built a custom rom for myself the other day, using the latest stock htc rom (HTC Generic 2.73.405.66), and the kitchen floating around on these forums. It flashes fine, after a full wipe.
Then it freezes on the Hero boot screen.
I used adb logcat to find the issue. I cant post the exact output now, but here is the basic problem:
loading libandroid_servers.so 0x0
its unable to load since it cant find the file: libandroid_servers
System crashes, and restarts. It does it over and over again.
Now im not sure how to solve it, but ive checked that the file libandroid_servers.so is included in the right folder, and and is spelt correctly (including case-sensitive wise)
Anyone else have/had this problem? and a solution?
Also i will say that im not exactly a nub at this. Ive had years of flashing and modification experience on different os's and platforms.
Thanks for any assistance that anyone can give
a few lines more from the logcat might help. the last line is not always the problem indicator. best is probably to attach a complete logcat from the boot, please attach a textfile or use a pastebin service, do not paste the log in your post.
Hi all, I'm sorry if I posted this in the wrong place.
I have an Archos 32 and I have an ad-hoc wireless network at my home. I've been trying to get my Archos 32 to connect to it and the only way that I have done so is through UrukDroid 1.0. UrukDroid however won't allow me to run some applications such as Camera and WeatherBug that I really would like to be able to run (they just crash). So I downloaded the GPL Source Code from Archos and made the changes to the wpa_supplicant source code via the patch that is found online. I've followed the guide on CNXSoft (can't post the link) for compiling the entire source on Ubuntu 10.10 (although I'm running 11.04). I have successfully created a zImage and a cramfs file, as well as a squashfs file. What do I do now? Are there any more steps that I need to do as far as installing it on my device? I've searched high and low and can't find anything so I figured I would post here. If someone could help me I'd appreciate it.
Lol I can't believe this is such a hard question that nobody knows how to answer it.
Anyway, I got it sorted, sorta. With wifi on the device turned off, I deleted the wpa_supplicant.conf from /data/misc/wifi, and changed the WifiAdhoc value to 1 in /data/misc/wifi/tiwlan.ini, then pushed it over, as well as a patched wpa_supplicant file via ADB over to the device. Now I can connect to my adhoc network on 2.3.26, and still have WeatherBug and the Camera and all the other apps that crashed on UrukDroid. The only drawback is that the wpa_supplicant file gets replaced with the original one everytime I reboot the device. Not sure how to avoid that. So everytime I reboot the device I have to copy the patched wpa_supplicant file again. But other than that it works great.
Anyway thanks for reading.
[I would've posted this in the Development section. But I'm not 'qualified' to post there due to my low post number -- I'm still a noob on this site]
I've been the proud owner of a TB for almost 2 months now. Been holding off on rooting, mostly out of fear of bricking the thing. I 'rooted' an old WinMO6.5 device about a year and a half ago. But the process for rooting TB is significantly more involved than my last one. However, I'm also frothing at the mouth after seeing all of the various ROMs out there, not to mention being able to be rid of all the crapware.. So...3 quick questions.
1) I've installed SDK on my home PC (Windows XP). But, when I extracted the .zip file, I extracted it to: C:\Program Files\Android\android-sdk. Only after the fact did I see in the instructions that I should have extracted to: C:\AndroidSDK
Does this difference really matter? As long as I drive to the correct directory on my PC when I start to run ADB, will its current location work ok? Or do I need to uninstall/reinstall?
2) There are a couple of places in the root process where you need to stop and verify an output alphanumeric matches what it should be. If the alphanumeric DOES NOT match, can I simply unplug the phone at that point and stop the root process? Or is it a situation where once I've started, I'm committed?
3) Finally, once I'm rooted, does it matter if choose a 2.2 (Froyo) or 2.3 (GB) ROM? My stock phone is running 2.2.
Thanks in advance for any feedback.
[I would've posted this in the Development section. But I'm not 'qualified' to post there due to my low post number -- I'm still a noob on this site]
I've been the proud owner of a TB for almost 2 months now. Been holding off on rooting, mostly out of fear of bricking the thing. I 'rooted' an old WinMO6.5 device about a year and a half ago. But the process for rooting TB is significantly more involved than my last one. However, I'm also frothing at the mouth after seeing all of the various ROMs out there, not to mention being able to be rid of all the crapware.. So...3 quick questions.
1) I've installed SDK on my home PC (Windows XP). But, when I extracted the .zip file, I extracted it to: C:\Program Files\Android\android-sdk. Only after the fact did I see in the instructions that I should have extracted to: C:\AndroidSDK
Does this difference really matter? As long as I drive to the correct directory on my PC when I start to run ADB, will its current location work ok? Or do I need to uninstall/reinstall?
2) There are a couple of places in the root process where you need to stop and verify an output alphanumeric matches what it should be. If the alphanumeric DOES NOT match, can I simply unplug the phone at that point and stop the root process? Or is it a situation where once I've started, I'm committed?
3) Finally, once I'm rooted, does it matter if choose a 2.2 (Froyo) or 2.3 (GB) ROM? My stock phone is running 2.2.
Thanks in advance for any feedback.
Click to expand...
Click to collapse
1. Yes, just run the commands from the dir you installed them.
2. If the md5's don't match then just redownload the file. Personally I have never had an md5 not match, however I do check them. Everytime.
3. Nope, run what you think you will like. The GB roms require the GB radios. You can find everything you need in the roms and kernel list. Its a sticky in the dev section.
I'm running BAMF sense 3.0 rc4. It uses the mr2 radio. Good luck with it and welcome aboard.
sent from my BAMF'n thunderbolt.
idahonld said:
[I would've posted this in the Development section. But I'm not 'qualified' to post there due to my low post number -- I'm still a noob on this site]
I've been the proud owner of a TB for almost 2 months now. Been holding off on rooting, mostly out of fear of bricking the thing. I 'rooted' an old WinMO6.5 device about a year and a half ago. But the process for rooting TB is significantly more involved than my last one. However, I'm also frothing at the mouth after seeing all of the various ROMs out there, not to mention being able to be rid of all the crapware.. So...3 quick questions.
1) I've installed SDK on my home PC (Windows XP). But, when I extracted the .zip file, I extracted it to: C:\Program Files\Android\android-sdk. Only after the fact did I see in the instructions that I should have extracted to: C:\AndroidSDK
Does this difference really matter? As long as I drive to the correct directory on my PC when I start to run ADB, will its current location work ok? Or do I need to uninstall/reinstall?
2) There are a couple of places in the root process where you need to stop and verify an output alphanumeric matches what it should be. If the alphanumeric DOES NOT match, can I simply unplug the phone at that point and stop the root process? Or is it a situation where once I've started, I'm committed?
3) Finally, once I'm rooted, does it matter if choose a 2.2 (Froyo) or 2.3 (GB) ROM? My stock phone is running 2.2.
Thanks in advance for any feedback.
Click to expand...
Click to collapse
In relation to your second question, the alphanumeric matches you're asking about are called an MD5 check sum. It checks a files integrity, like a finger print. As long as the characters match the file is intact and you know it is safe to flash. If the characters don't match then you will download it again and replace the original file you downloaded. Then run the MD 5 check sum again to make sure its all there (characters match). I have never had a MD5 not match, so its uncommon. If you were to flash an incomplete file it most likely would brick your phone.
I would recommend a 2.3 ROM. Part of what makes rooting and nand unlocking (S off) so valuable is the ability to run the latest operating system. I would suggest you try Cyanogen once you're comfortable flashing ROMS.
Thanks for the prompt replies. This helps a lot.
I've got the 3 files downloaded to my PC for the root, and they all are good w.r.t. MD5 checksum. So I think I'm good to go/root.
One more noob question. And I could probably find the answer to this by searching around, but as long as I have your attention...you say that the GB roms require the GB radios. Do most/all of the GB roms already have the GB radios built into them? Or is this something totally separate?
idahonld said:
Thanks for the prompt replies. This helps a lot.
I've got the 3 files downloaded to my PC for the root, and they all are good w.r.t. MD5 checksum. So I think I'm good to go/root.
One more noob question. And I could probably find the answer to this by searching around, but as long as I have your attention...you say that the GB roms require the GB radios. Do most/all of the GB roms already have the GB radios built into them? Or is this something totally separate?
Click to expand...
Click to collapse
radios are separate. For GB, you need MR2 or MR2.5 radios. They are in the dev section as well. Flash the radio before you flash the GB ROM or you will not have any cell signal.
Also be aware that when you start the rooting process, you need to use the USB connections at the back of your computer. ADB only recognizes the main USB ports. Good luck with your rooting!
Sent from my ADR6400L BAMF 3.0 RC4 using XDA App
Hi,
I'm a dev working on Mozilla's Boot2Gecko project. We've run into an issue with heimdall, and I'm trying to get ahold of the dev to discuss this further.
One of my coworkers created an issue on github, and I've added some comments, but neither one of us has received any replies, so I'm posting here to see if that helps.
The problem that we've run into, is that I can use heimdall fine when our system.img file is 100Mb or less, but get failures or corruption when system.img is 100Mb or larger.
My phone is a Samsung GT-I9100 (Samsung Galaxy S II). I upgraded the firmware to ICS using the XXLPQ firmware (I used this page: www dot theandroidsoul dot com slash xxlpq (the form won't let me post the url since I've posted less than 8 times), so its possible that the problem is related to newer bootloaders.
I have a system.img file that is 115Mb, and the command line I use is:
heimdall flash --factoryfs system.img
Under 1.3.1, there is a noticable pause at 87%, then it continues on to 100% and reports success, but the image that is burned into flash is corrupted.
Under 1.3.2, it stops at 87% and reports a failure.
Running with --verbose, the 87% corresponds to 800 packets of 128K each (which is 100 Mb)
If I reduce system.img to under 100 Mb, then both 1.3.1 and 1.3.2 work fine.
My dev machine is running Ubuntu 12.04, and I have a Windows 7 VirtualBox. I see the same behaviour from the Windows 7 VM as I see from ubuntu.
If I use odin (v1.83) from the Windows 7 VM, then it burns it properly.
I took a quick look at the source code and tried increasing the 800 limit (kMaxSequenceLength) and the 128K limit (kDefaultPacketSize), but those both fail as well.
I have packet wireshark captures of the USB streams under linux, and I installed a trial version of USBlyser under windows and have packet captures from both odin and heimdall, should those prove useful.
From the packet captures, odin seems to be transferring 1Mb at a time.
I had the same problems with my ET4G. I posted a pull request on the project's github. I'd link you there but I am not allowed since I am a new user, it is pull request #47. Works for me... maybe it will help you out.
bleffij said:
I had the same problems with my ET4G. I posted a pull request on the project's github. I'd link you there but I am not allowed since I am a new user, it is pull request #47. Works for me... maybe it will help you out.
Click to expand...
Click to collapse
this is certainly not fixed for me for an SHW-M250K (korean SGS II and compatible with I9100 ROMS with minor caveats).
I get extremely similar symptoms(identical as far as I can tell): Consistent corruption where files don't diff against the loopback mounted ROM files and are reprodicibly corrupt for any particular ROM. I saw this on.. I think it was 1.3.2 and then grabbed the latest 1.4RC1 from git and still see the same thing. Flashes with odin on the same hardware in fact in a windows vm within the same host OS.. work just fine. This is really bad especially since, sometimes the corruption isn't that obvious.
It seems to be scattered bits or bytes. Often the system boots but encounters various amounts of bugginess (depending on the EXACT rom, just adding or removing a file from the rom not surprisingly changes which bits and bytes are corrup)t. I guess it's many small chunks that are corrupt because I see typically maybe 80% of files are corrupt but still things kind of work. That tells me it's like a bit byte or small chunk here or there for every few MB probably. Enough to get most files but little enough it doesn't get every file or break them entirely.
I don't have a github account. Maybe I need to make one.
For now simply follow the instructions and use the provided file download from the link posted below
http://forum.xda-developers.com/showpost.php?p=48392009&postcount=1
I have personaly tested this method in full on My AT&T Samsung Galaxy S4 ZOOM SM-C105AUCUAMJ2 (4.2.2 Jelly Bean)
although it should be safe to use on any AT&T Samsung Galaxy S4 ZOOM running an android version prior to Kit-Kat
All Credit for this, "exellent completely safe", Root method goes to its creator k1mu
And please Know that it is only being shared with you via his explicit permission.
EDIT:
Q&A for [ROOT] Saferoot: Root for AT&T Galaxy S4 ZOOM SM-C105AUCUAMJ2_On 4.2.2 JB
Please if you are not on an AT&T Galaxy S4 ZOOM C-150a, Feel Free to Read
but Do not seek help,instruction, or any other type of advice by posting in this thread as it is hard enough to find information about a specific device when the said device does not have a dedicated forum. Thank You for your Understanding in this.
Instructions & Advice
If ?'s arise
and time allows I will add device specific instruction as well as any advice, Please bear with me. Same as above Q&A Link
Will this same method also work on the SM-C105AUCUAMJ2?
kbracing6 said:
Will this same method also work on the SM-C105AUCUAMJ2?
Click to expand...
Click to collapse
Most Definitely as this was the reason for my post
Hey @Phatboyj420, as far as converting a raw OTA file to Odin files, here's what I can tell you. The OTA file should be filename.cfg, i.e. a cfg file. Believe it or not, this can be manipulated like an archive (like zip or rar or tar) so open that cfg file in 7zip, WinRar, or whatever. You're going to want to extract the files like (I can't guarantee this a full list, just the ones I can remember) modem.bin, NON-HLOS.bin, boot.img, recovery.img, aboot.mbn, rpm.mbn, sbl1.mbn, sbl2.mbn, sbl3.mbn (you might not have all 3, idk), and tz.mbn. Again, there may be others you need, and/or not all the ones I just listed might be necessary, they're just the ones I remember dealing with before. Oh, you're going to need to make sure the system, cache, and persdata partitions are all packed into .img.ext4 files, idk if they're like that in the OTA cfg archive.
Here's where it gets even hazier for me. So, I know from personal experience that you can take any of these files (I'll just use recovery.img for this example). In a linux terminal (I use Ubuntu for convenience's sake, my laptop has windows and ubuntu partitions) run this command:
Code:
tar -H ustar -c recovery.img > recovery.tar
So that's how you can take any one of those files I mentioned last paragraph and pack it into an Odin-flashable tar. I'm still a n00b when it comes to the linux terminal, so I can't really say the syntax for packing more than one at once.
So I guess I haven't really given you the complete process, but hopefully this is at least a decent starting point. Honestly I consider myself a hobbyist at best, not an expert. muniz_ri, who Devo7v mentioned earlier, did all the heavy work in this regard so he can probably help you much more, I just didn't want to volunteer him for the job
thisisapoorusernamechoice said:
Hey @Phatboyj420, as far as converting a raw OTA file to Odin files, here's what I can tell you. The OTA file should be filename.cfg, i.e. a cfg file. Believe it or not, this can be manipulated like an archive (like zip or rar or tar) so open that cfg file in 7zip, WinRar, or whatever. You're going to want to extract the files like (I can't guarantee this a full list, just the ones I can remember) modem.bin, NON-HLOS.bin, boot.img, recovery.img, aboot.mbn, rpm.mbn, sbl1.mbn, sbl2.mbn, sbl3.mbn (you might not have all 3, idk), and tz.mbn. Again, there may be others you need, and/or not all the ones I just listed might be necessary, they're just the ones I remember dealing with before. Oh, you're going to need to make sure the system, cache, and persdata partitions are all packed into .img.ext4 files, idk if they're like that in the OTA cfg archive.
Here's where it gets even hazier for me. So, I know from personal experience that you can take any of these files (I'll just use recovery.img for this example). In a linux terminal (I use Ubuntu for convenience's sake, my laptop has windows and ubuntu partitions) run this command:
Code:
tar -H ustar -c recovery.img > recovery.tar
So that's how you can take any one of those files I mentioned last paragraph and pack it into an Odin-flashable tar. I'm still a n00b when it comes to the linux terminal, so I can't really say the syntax for packing more than one at once.
So I guess I haven't really given you the complete process, but hopefully this is at least a decent starting point. Honestly I consider myself a hobbyist at best, not an expert. muniz_ri, who Devo7v mentioned earlier, did all the heavy work in this regard so he can probably help you much more, I just didn't want to volunteer him for the job
Click to expand...
Click to collapse
Thanks My guy,
This definately gives me a good jumping off point.
The phone shipped with JB-4.2.2 and I think there has been an AT&T OTA for KK so it would have to be a complete Firmware so thats good news.
I'm working on several projects at once so I don't know exactly when I'll get to this but when I do the first thing will be to verify whether the .img's for data/system/cache are img.ext4 or not and if not how to produce correctly.
Also I don't have a Linux Dev setup yet I'm running Windows On a 2011 Dell XPS-17_L702x with an intel 2720 quad core. So from your post I take it Ubuntu would be your suggestion for Linux Distro. and should I make a separate Linux Partition and run from it, or run from a VM-Box inside of windows? Which do you think would be most efficient?
Now that I think of it I'm going to start a dedicated thread for development discussion for this specific device. If I start the thread in the Development section for the general S$-ZOOM but title it specifically for the " AT&T-C105a_ZOOM " do you think the mods would want to move it to the general Q&A section?
" I would hope that, as it would pertain directly to the development of the specific device they would see fit to leave it in the development section.
Sorry for the randomness of my thoughts but I will link you to the thread when I get around to starting on it.
For now I'm going to get back to work on the S4_Active for My daughters B-day I intend to have it Rooted and rommed out for her. When I get that done I'll make my way back to this Project, and start the dedicated thread.
Thanks again,
" I look forward to future collaboration as it seem we share a similar Hobie at the least ",
Phatboyj
Unfortunately for the few lonely SM-C105a users still hanging on out there this does not appear to be a completely effective root. I get this in dmesg: <3>[ 2130.920856] c0 Restricted changing UID. PID = 11580(su) PPID = 11575(sh)
capt_planit said:
Unfortunately for the few lonely SM-C105a users still hanging on out there this does not appear to be a completely effective root. I get this in dmesg: <3>[ 2130.920856] c0 Restricted changing UID. PID = 11580(su) PPID = 11575(sh)
Click to expand...
Click to collapse
What is your build # because this is a fully effective root method for the ATT SM-C105a running build# SM-C105AUCUAMJ2
Please elaborate on where your dmesg is coming from.
Is it from running Saferoot to obtain Root?
Or is it from some other function you are attempting after obtaining root?
@Phatboyj420 Great to see you here--when I'm sure your S4 Zoom is long gone. Yeah, that's my build and I should point out that I get that in dmesg only for certain operations in the system folder (trying to copy modules I think). No biggie, for day to day this method works fine. I'm more interested in whatever happened with that unbrick image you were trying to make from dd. Did you ever test it? Was it effective? My current efforts are focused on developing a reliable unbrick method for our phones. Rather than the complete image I think we may need to extract and flash the original bootloader in many cases. Can you provide any feedback on this?
capt_planit said:
@Phatboyj420 Great to see you here--when I'm sure your S4 Zoom is long gone. Yeah, that's my build and I should point out that I get that in dmesg only for certain operations in the system folder (trying to copy modules I think). No biggie, for day to day this method works fine. I'm more interested in whatever happened with that unbrick image you were trying to make from dd. Did you ever test it? Was it effective? My current efforts are focused on developing a reliable unbrick method for our phones. Rather than the complete image I think we may need to extract and flash the original bootloader in many cases. Can you provide any feedback on this?
Click to expand...
Click to collapse
@ capt_planit
while I have moved on from using my [email protected] S4-Zoom, I do still have it and the dd dumps of it the problem with providing said dumps publicly is that some "idiot would inevitably flash the complete dd.image to there phone giving them an exact clone of my phone explicitly the IMEI via EFS parition are my concerns.
That being said if I know that the dd.images were to be used in a proper manner, by say a knowledgeable Dev. I would gladly supply them to further /Kickoff Development,
It sounds as if we are of like mind but I found myself at a stand still and did not recieve any response from the plea in my Sig.
But rest assured if there is something I can do to assist I will.
as far as an unbrick.img for the Zoom c105a
I did make one but have had no reason to use it to know if it works or if the SD unbrick method even works for the Zoom like it does on the Galaxy S3 that the method was originally discovered on.
Even if it does work the SD-Unbrick method only gets you to a state where Download
mode works SO unless I am mistaken and you can access adb through Download Mode witch I'm pretty sure you cant, we would still be at a stand still as there is no stock firmware publicly available for our device " Ludacris I know " but true none the less.
Edit:
1 thing we need is the OTA update from JB to KitKat available for our device we need some one to extract it before updating then and only then might we be able to create an install-able firmware for our device.
if I'm not mistaken after you download the OTA update you should be able to find it in /cache/fota just zip the entire fota folder move it to your sd-card and make it available to me and we'll make it happen from there.
If you don't want to except the update just delete it at this point and reboot.
...
...
I think this user @awwar describes an inability to access download mode>here. In anycase, I think that thread would be a great place to post your unbrick. image. I think your dd image seems too small. But if you still have it, that is what @moomoo was asking for when he started that thread. I can't provide mine, except as separate img files. My understanding is that flashing an efs image won't provide a real IMEI. I think flashing some combination of boot, system, cache (I'm surprised this would be necessary) and recovery should get the operator some kind of system. But so far it doesn't seem to work that way. Your help getting some working phone flash would be greatly appreciated. I believe, BTW that the OTA is dead...