yashsingh1/xdaforums huggingface dataset:
[Epic 4G Themes] Zeinzu:
Did you fix the charge.xml?
[HD2 Android Q&A, Help & Troubleshooting and Genera] jmmmmm:
Hey guys in desperately looking for the wifirouter.apk that installs with the Desire builds. I have downloaded virtually every Desire rom to see if the file happens to contain the folder structure with the system/app folder. If someone can explain how to decompress a sqsh'ed file I could do that.

Can someone email me the wifirouter.apk?
[Vibrant Q&A, Help & Troubleshooting] Zjunk:
Can someone assist?

I was going from bionix V, and decided to Odin back to stock. I used pit 512 and a kernel here - the last one on the list (stock+froyo uvkb1) on this post - xdaforums.com/archive/index.php/t-870480.html

I flashed the kernel here as the pda in Odin. I thought this was the right way to go, but instead, I'm now stuck in an infinite recovery loop where I can't reboot and can't flash any thing else. I just boot into recovery over and over again. I've mounted the drive, deleted all the files, added back in backups, and tried to flash a ton of stuff, but I keep getting this error:

E: can't mount /dev/block/stl11 ( file exists)

E:cant mount CACHE: recovery/command

cant mount cache:recovery/log

cant open cache:recovery/log

re-partition, auto reboot, and f.reset time were all checked in odin, but nothing else.

Oh, and I can't just use odin to restore - I cannot get into download mode using either the three button method or the adb method.

Can anyone help? I seriously don't want to have to go buy another phone - mainly because I can't really afford that sort of thing.

EDIT: Appreciate people helping here - just to clarify, I don't need help with 3 button method or adb into download - those methods aren't working.

There are 4 ways to get into download that I know of and 3 are on the phone itself.

1. Power down. Insert USB. Hold down vol up / vol down, and hold power until phone starts to boot. Let go of power and hold down volume until download starts.

2. Using a command prompt and ADB, tell the device to reboot into download.

3. Reboot into download via the CWM recovery menu.

The 4th way is the homemade jig, which I don't have the tools to create at the moment. However, I may try it shortly here.

I've tried all 3 of the ways above, and I'm stuck in a boot loop. I'm also unable to disable voodoo.

Does anybody know anyway to do a full on clean reset of the phone with Odin, nandroid, etc? The issue is, all of these methods on the boards would work if I could get into download, BUT, the phone won't mount the proper files for whatever reason (error code in original post) and so I cannot get into download, the home screen, nothing but the cwm recovery menu.
[Vibrant Q&A, Help & Troubleshooting] hd2life:
You should get in to download mode and odin stock jdf, those files you flashed are froyo builds. I don't think it work's that way, you must flash jdf first.
[Vibrant Q&A, Help & Troubleshooting] Zjunk:
I know I need to do that - problem is, I can't get into download mode. That's step one - I'm stuck in the cwm recovery menu, over and over, and can't get anywhere else. Any ideas?
[Vibrant Q&A, Help & Troubleshooting] Romeo20:
Try this

how to put in download mode- sure fire way

1- phone off

2- open Odin

3- hold vol button and plug in USB.

I just posted a thread. My phone just keep going to DL when I switch battery.
[Vibrant Q&A, Help & Troubleshooting] Zjunk:
Thanks, but no - that method isn't working. There are 4 ways to get into download that I know of and 3 are on the phone itself.

1. Power down. Insert USB. Hold down vol up / vol down, and hold power until phone starts to boot. Let go of power and hold down volume until download starts.

2. Using a command prompt and ADB, tell the device to reboot into download.

3. Reboot into download via the CWM recovery menu.

The 4th way is the homemade jig, which I don't have the tools to create at the moment. However, I may try it shortly here.

I've tried all 3 of the ways above, and I'm stuck in a boot loop. I'm also unable to disable voodoo.

Does anybody know anyway to do a full on clean reset of the phone with Odin, nandroid, etc? The issue is, all of these methods on the boards would work, BUT, the phone won't mount the proper files for whatever reason (error code in original post).

I really appreciate you trying to help, it's the right answer for a lot of issues, but just not this one.
[Vibrant Q&A, Help & Troubleshooting] mrzhadow:
What if you can get in dl mode but odin won't read your phone? I have the correct drivers intalled. It was working fine til I upgrated to cm7. Now my phone is stuck at vibrant screen and can't get in recovery. The phone boots in dl mode but its not recognized by my pc. Any ideas if I'm screwed?
[Verizon Droid Incredible 2] dg4prez:
How does the wireless tethering in CM7 work? I'm guessing it's the same as the free workarounds, rather than using the verizon paid tethering method. can anyone confirm this?
[Verizon Droid Incredible 2] MJL99:
Same question here. I have tried that and the wireless tether app and neither work for me.
[Verizon Droid Incredible 2] Sic123:
i got wireless tether work by going in and setting it manually to adhoc mode or use barnacle tether
[Verizon Droid Incredible 2] dg4prez:
barnacle definitely works, i just want to know if the built in one will result in tethering charges.
[Verizon Droid Incredible 2] k_nivesout:
No, the built in tethering doesn't incur any charges.
[Android Software/Hacking General [Developers Only]] shabbypenguin:
for anyone that thinks this isnt worthwhile, imagine if your device had no source.. where would your kernels be? imagine if this became the trend, to give out crap source
[Android Software/Hacking General [Developers Only]] k0nane:
And on top of that, I have every reason to believe - though IANAL - their behavior is illegal.
[Android Software/Hacking General [Developers Only]] Darkshneider:
RT the thread.
[Android Software/Hacking General [Developers Only]] daddymikey1975:
I blew this up over on samsungs facebook page.. someone got pissed and deleted my post..

http://www.facebook.com/SamsungMobileUSA

I started to 'comment' on a bunch of their stuff w/ a link to this thread..

I might get my account suspended BWAHAHAHAHA..

bastards
[Android Software/Hacking General [Developers Only]] jeffyv2:
Let's call out @samsungjohn on twitter!
[Android Software/Hacking General [Developers Only]] zman519:
This is the vary reason i will NEVER BUY any thing sumsuck ever makes, EVER AGAIN!
[Android Software/Hacking General [Developers Only]] ptfdmedic:
.....and why are you not a recognized developer? You deserve it more than me. :-)
[Android Software/Hacking General [Developers Only]] k0nane:
mkasick, thanks for the reply, we will look into this. EDIT: Keep in mind that we are using the same toolchain as Samsung, specifically CodeSourcery 2009q3.
[Android Software/Hacking General [Developers Only]] Decad3nce:
You weed out toolchain, source, and what you have left is a defconfig that probably has more debugging active than the one that's shipped with the source.

No other way to explain size differential.

EDIT: Also, holy awesome on that analysis.
[Android Software/Hacking General [Developers Only]] mkasick:
Attached is a patch that should implement this. I've also attached a build of the kernel with it applied--given that we might be looking at funny race condition issues, it's probably worth seeing if the build environment has as much of an effect here.

Mind you, I don't have an Indulge and was unable to test. No idea if this actually works, but hopefully it's progress.

Now, if it does work, it's worth running a dmesg and looking for a "/dev/dpram1 does not exist yet, sleeping." just prior to "dpram_open successd !!!!". If that message isn't there, then it wasn't strictly the patch that contributed to a successful kernel, rather it's probably an artifact of the build.

Full disclosure:

The kernel sources are from SCH-R910_OpenSource.zip posted the Samsung open source page. The initramfs was extracted from this Odin repackage of the stock kernel, linked to from androidforums, although in retrospect I probably should've pulled it from k0nane's GitHub. It was compiled with CodeSourcery G++ Lite 2010q1-188 (EABI) on a Debian sid machine last updated sometime two weeks ago.

In additon to the aforementioned patch (indulge_multipdp_wait_for_dpram1.diff), I used another patch (indulge_no_ifdef_linux.diff) to get rid of the single "#ifdef linux" that trips up the eabi compiler and shouldn't be necessary with the gnueabi one. Otherwise, the only other source changes I made were to the CROSS_COMPILE variable in Kernel/Makefile and CONFIG_INITRAMFS_SOURCE in Kernel/arch/arm/configs/forte_01_defconfig to set the appropiate paths for those two.

I build the kernel once with the original initramfs, copied the newly-built modules/samsung/multipdp/multipdp.ko over the existing one in the initramfs, and rebuilt the kernel to link in the updated initramfs. That should be it.
[Android Software/Hacking General [Developers Only]] mkasick:
Yes you're right.

I know that for the Epic's DI18 Samsung used what looked to be an in-house build of GCC 4.3.1 for the stock kernel even though they were recommending CodeSourcery in the source README. Apparently they switched to 2009q3-67 for Froyo and I never noticed.
[Android Software/Hacking General [Developers Only]] k0nane:
The defconfig on my Github is identical to that of the package on opensource.samsung.com with the exception of LZMA compression being enabled and a path to the initramfs files being set.

I'll pass this on to an Indulge user, or test it myself if I find a working microUSB cable first. Thanks. EDIT: No such luck! Died within 15s like most kernel builds do. Unfortunate. I can have the user acquire a log, but I am 95% certain no new info will be presented.
[Android Software/Hacking General [Developers Only]] mkasick:
Crud.

I'd be curious if it contains any more statements about dpram_open, suggesting whether or not that patch had any effect. Or the built multipdp.ko even works.

Either way, if the device is automatically rebooting after 15 seconds, it's either hitting a kernel panic or something funny is going on with the watchdog. If we could get console output with a UART jig that would likely be helpful.

Can (stock) recovery be booted with a source-compiled kernel and survive for some length of time?
[Android Software/Hacking General [Developers Only]] k0nane:
I will acquire a log ASAP. A new copy of that kernel with adbd flipped to root on boot would be useful, as it's difficult to capture a full kmsg without it - I can generate it via your patch, or if you wish to substitute in the initramfs from my github, that's an option as well.

And unfortunately, building one is a bit beyond my skill level. I'd be willing to buy one. The jig should work for the Indulge, given it is essentially a Galaxy S device. I agree that it's most likely panicking - it would be helpful if there were some kind of output to the display as there is with Epic kernel panics.

That has not yet been tested. There's a /system/bin/recovery and a recovery partition; as with the Epic and other devices, the partition should be triggered by the button combination on boot. I'll have a user flash a built kernel to bml9.
[Android Software/Hacking General [Developers Only]] mkasick:
Attached is a build with your github initramfs.

I have to read through that thread again, but I believe the simple version of the JIG is a 3.3v USB-to-serial converter along with a single resistor to activate the UART. I have some FT232 converters lying around, but they're 5v. :(

I'll order some parts and see if I can build one for myself in a week or so, as it would be useful for Epic debugging. If it works, we can work something out to get one sent your way.

I'm thinking ~15 seconds is a somewhat strange time to die during boot. If recovery (with adb) runs stable, then the kernel works in a minimal environment. Perhaps some narrowing down of the boot sequence can be done from there?
[Android Software/Hacking General [Developers Only]] daddymikey1975:
Sorry to derail this but I'm cross posting here..

I sent an inquiry to the EFF to see if this is an issue that they can help with. Below is the response I received:
[Android Software/Hacking General [Developers Only]] k0nane:
mkasick, you are a god. :) You've done the work that Samsung completely neglected to do - whether deliberately or not.

I suppose this thread can be closed, now. The changes have been pushed to my Github.

Thanks everyone for your input, and mkasick for fixing an obscure problem on a device you don't own!
[Android Software/Hacking General [Developers Only]] Silvist:
Mkasick you are a kernel god! Thanks everyone at Xda for making this happen, and thanks again K0 for toughing this kernel and samsung out for months of testing!!
[Android Software/Hacking General [Developers Only]] mkasick:
So that fixed the problem then? If so, great!

You're welcome. It was a strange riddle, just had to be solved.
[Android Software/Hacking General [Developers Only]] Calbha:
i have been scouring the net for 5 days now for some sort of support other than cricket for the samsung indulge. (I AM COMPLETELY NEW TO ANDRIOD i came upon this thread and was about to exchange my phone as it appeared the source code for this phone wasn't understood) I understand no technical support question should go in this thread but it seems you people have fixed the issue of it being impossible to mod this kernal? and since i cant find support elsewhere for this rare phone, and if you guys have fixed it where can i go to figure out what to do with this phone. Dont read further if i have already pissed you off! :P

ALL ATTEMPTS TO FACTORY RESET THE PHONE have done nothing but erase contacts and programs, all boots of any kind, (r+power, yol down + power etc...do nothing but freeze the phone on an android icon) all files on the phones system settings are still the same and includes files downloaded to the phone. (EVERYTHING) basically I was trying to get my indulge to see ad-hocs so i could use my computers connection for my phone, changed the wpa_supplicant file not realizing/reading how phone specific it is, tried all recovery instructions ive found but i cant seem to find an update.zip wpa_supplicant or anything to recover the phone to its original from the store state so wifi works at lest. My apologies again for the incorrect placing of this post. (sweat)
[Desire HD General] mighty34:
When I installed LeeDroid 3.21 I followed instructions and I formatted SD and made partition.

Today I downgraded my phone to stock 1.32 in order to use easy radio tool and to det super cid, sim unlock and radio s-off

i did it

now i wanna give a try to revolutionary hd 5.21 and decide should i use it or continue with leedroid.

In clockworkmod i formatted sd card and when I mount it on my PC I se external disk with 6.44GB capacity.

Does it should be like that?

I doubt that partition which I made before has not been deleted when I format sd

i have no sd-ext option in clockwordmod

thanks
[Desire HD General] mighty34:
can anybody tell me do you see 6,44gb from windows 7 on your dhd or more?
[Desire HD General] mighty34:
solved

i formatted card in my photo camera and it's ok now. I see 7.40GB

thanks to everybody
[Galaxy S II Q&A, Help & Troubleshooting] nraudigy2:
Has any website done analysis on this phone? I only heard it uses all the latest components.
[Galaxy S II Q&A, Help & Troubleshooting] expertzone.ro:
On the gsmarena site look for: Samsung I9100 Galaxy S II review: Brightest star

it's a good review, including some hardware benchmarks ;)
[G2 and Desire Z General] philicibine:
Hello all...

I just stumbled upon this in another forum...

Don't know if it could help anyone with bricks??

Quote :

This phone use an msm7230 cpu and the voltage used by it I guess that is 2,6Vcc. You can search it by probe function in riffbox or by multimetter in comparation with another known jtag like is for example wildfire,desire and for other that use logical i/o 2,6Vcc. In many phones that I found the jtag pins without desolder the cpu this was the nearly value that was the same at all:

trst-0

tdi-2,6

tms-2,6

tck-2,6

rtck-0,04

tdo-0.04

View attachment 650945
[Nexus S Q&A, Help & Troubleshooting] Windst:
So my Nexus S 4g been mighty stable, til this morning. i check my bank account on my phone then all the sudden, the back button starts blinking like crazy, and everything goes back if i open anything, and the vibrate feedback can be felt like rapid fire. So I hold the button so I can actually power off the phone into recovery.

Its still blinking, so I hold it down so it sends only one signal, so i can change my kernel back from Netarchy 1.3.7 to 1.3.6 where it still does it. Repeat to Mathkids. I also wiped the cache partition, and dalvik cache for this one. havent tried stock yet.

Anyone ever have this problem. Its still doing it. Thinking about going to stock and returning phone.

And if I do return it, do I have to unroot, and relock the bootloader?
[Nexus S Q&A, Help & Troubleshooting] Windst:
tried stock kernel, did a few backups, formatted everything agian, turned back to stock and it hasnt stopped.

did notice tho if my hand or thumb got close to the back button, but didnt touch it, it would stop blinking. maybe it needs a heat sensative calibration? it wont stop flickering no matter what
[Nexus S Q&A, Help & Troubleshooting] jottosson:
It seems to be related to this issue: www.google.com/support/forum/p/Google+Mobile/thread?tid=49e8ca84071d51a4&hl=en

Im having exactly the same problem, but with the searh button. In the Google thread a Google employee has replied, and according to him they're working on a fix (software related). This was posted a couple of weeks ago, i bet the fix is issued in 2.3.5, set to rls in the upcoming days.

For me the search button flickering seems to be related to how long the screen has been on, i.e. how warm it is. I can use it perfectly for 20-30min, but then its unusable for the next five. I discovered the relationship between screen on time and the flickering like a day ago and it may be incorrect. The Google employee says it is a software issue, but i dont hold my hopes high.
[Nexus S Q&A, Help & Troubleshooting] iboj007:
I was having this problem with the search button.

I goofed up something on the phone and ended up reflashing it back to stock like 5-6 times in the course of a night.

Ever since then, I havent had the issue pop up even once.

I also have read that it has to do with the NFC contacts on the battery cover. Someone was able to supposedly fix this by preventing the contacts from touching their corresponding contacts on the phone.
[LG Revolution] AndroidCraig:
Okay This is the 2nd phone of mine this has happened to. It was working fine, then I plugged it in to recharge and now it won't boot again.

I'm rooted, ROMed and have CWR loaded.

I've tried getting it into CWR by pressing and holding the Vol DOWN and Power button, but it keeps starting the normal boot process.

How can I get my phone back. I'm starting to lose faith in the Revo and am about to press VZW for a replacement to the Charge.
[LG Revolution] Squiz0329:
Have you tried the QuickBoot app? That ortta help.
[LG Revolution] majorpay:
I can't figure this out - so you are bricked, or you are just trying to access recovery?
[LG Revolution] AndroidCraig:
It seems bricked. It has been running fine since I received it and rooted and loaded the Cubed ROM. I plug it in to recharge over night and in the morning it was dead. Would not boot to CWR.

I took it into VZW and they put me on with tech support. Bottom line I'm giving up on the Revo even though I prefer it to the Charge or TB. VZW is upgrading me to a Charge. I had the option of any of the three existing 4g handsets. As There are too many issues with the TB and I don't want to go through this again with another Revo (2x of this in less than 2 months of the phone being out is too much for me.)

Hopefully the Charge is more reliable. I guess I'll find out.

This is a great group who has done amazing things with this phone. Just wish I could rely on it.

take care.
[LG Revolution] Haxcid:
No offense but the only common denominator between your first and second phone is you.

Odds are you are doing something, or there is something environmental where you are that is causing this to happen.

Are you using the same charger that came with the first phone?

Are you plugged in a power strip?
[LG Revolution] AndroidCraig:
No offense taken. I did think of that. But if it was something I've done, I think it would happen immediately and not run great for over two weeks then just die.

I did not install any new SW, I'm using the same charger that came with the phone. it is not plugged into a powerstrip.

I could understand if I had been adding new programs etc... But none of that was going on. It was running great on the de-crapified ROM I was able to get 6+ hours on the battery most of the time.

Then I plugged in the phone to recharge after using it all day (had about 20% left) Went to be and woke up and dead.

Same exact thing that happened the 1st time.
[LG Revolution] thermal_tim:
Weird... I hope it gets better for you with the new phone. I just wish everyone could be as happy as I with their revo...
[LG Revolution] Squiz0329:
You wouldn't happen to be plugging it into an outlet that requires a light switch to be turned on by any chance?
[LG Revolution] AndroidCraig:
Nope. Outlet is not connected to any switch. I've used this out let for the past 18 months with no problems with other phones.
[LG Revolution] thecubed:
by "dead" what do you mean? any explanation?

Trust me, there's almost NO way to kill this phone by normal means.

If there was, I'd have found it by now.

Things to try:

remove battery, plug in USB to PC, hold volume UP, put in battery, hold power (while holding volume up).

That'll put you in firmware download mode.

Unplug it from usb in PC, and plug back in wall charger. Let device sit for an hour or so to charge the battery.

Once that's done, unplug battery+usb. Hold volume DOWN and power until device vibrates once.

Tada! You're in clockwork.

Hope that helps!
[LG Revolution] AndroidCraig:
I'm game to give it a try, I did get the replacement Charge today and have not yet activated it.

I'm not sure of the last step however. Are saying after the battery is charged, I take out the battery and plug it into the USB on the PC then hold Power/Vol down?
[LG Revolution] AndroidCraig:
Cubed, I tried exactly what you wrote and no go. I can not get this thing into recovery no matter what I try. Please help.
[HTC Sensation] farufas:
Hello All,

Just as the subject describes Bell Canada has released this phone and a few cases with it. I'm trying to figure out if anyone has used the above case since it comes with a heavy duty silicone case. Check bell.ca and select ontario and check out the accessories they have.
[HTC Sensation] Solidus_n313:
I went to 6 Bell mobility stores in etobicoke and Toronto, and NONE of them had any accessories for the S4G...most of the staff didn't even know what the phone was :/ way to drop the ball again Bell :P

I ended up getting a soft plastic case from future shop (the only one they had) and it was 2 for 1 for $30 after tax. One is black, which I'm using (its quite nice), and the other was opaque white.

The worst part is that all cases sold by FS and the source DO NOT have the noise cancellation holes, I had to drill them myself

Oh, Canada...
[HTC Sensation] farufas:
wow that sucks, i'm out of the country and want my cuz to buy a case DAMN....but checking on the website it shows THE PHONE BOOTH carrying the Incipio NGP Cases
[HTC Flyer, EVO View 4G] bucklee:
Hi I have been following a great little drawing program called Fresco. Currently it does not support scribe pen but the developer is waiting on HTC SDK for the scribe pen. As soon as HTC releases the SDK I am hoping the developer will implement the pen to the program. On its own merit the program is quite robust with many options not available on other drawing apps yet. Thought those artist who bought the HTC in hopes of using it as a sketch pad could find this interesting.

http://xdaforums.com/showthread.php?t=1132869