yashsingh1/xdaforums huggingface dataset:
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
That's an indication that you may have more serious problems. nvflash will be required. http://xdaforums.com/showthread.php?t=861950

Once done you will likely need to install ClockworkMod and repartition your internal storage.

If your tablet boots properly but you can't get into CWM then it probably isn't installed properly (or at all). http://xdaforums.com/showthread.php?t=865245

Keep in mind that CWM is NOT compatible with all ROMs. Make sure the developer for your chosen ROM recommends it before installing it.
[G Tablet Q&A, Help & Troubleshooting] lsu205:
Does your method in opening post have to be run from external micro sdcard?
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
Both methods are performed with an external MicroSD card. They will work from internal also but it is a little more difficult to get the files in place if your tablet is not booting properly.
[G Tablet Q&A, Help & Troubleshooting] lsu205:
so your method is a simple way to replace one of the main uses of Clockword MOD?--Plus you stay stock more or less.
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
That is correct. Method II can also be modified to be less intrusive (leave user apps installed) or embedded into update scripts to perform a wipe during new ROM installs.
[G Tablet Q&A, Help & Troubleshooting] lsu205:
Wipe data does what--remove the apps installed?
[G Tablet Q&A, Help & Troubleshooting] enigma0456:
And the partitions?

Your post is very interesting. It implies that you have a knowledge of the g-tabs partition structure. I have played with Linux off and on for the last 10+ years. When I began, I used Slackware and when you set it up you had to manually create partition tables using fdisk. You were only required to create two - the data partition and a swap partition but it was often recommended that you create several others - one to contain the home directory to prevent users from using all the disk space (in the days of small disks) for example. It appears that there are a lot of partition on the g-tab. Up to now, I have used various wiping tools like clockwork or calkulins wipe all on faith. I would really like to know what all the partitions are and what is in them. I have used terminal to get to the root folder and tried to do an fdisk to display the partitions but try as I might everything remains hidden. It would seem that a script like yours could be adapted to do many things but I would certainly want to understand the structure a little better before I did anything. I have searched and been unable to find that information. Can you point a way for the curious to learn more about the partition structure on the g-tab?
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
Wish I had a direction I could point you in. What I've found so far has mostly been stumbled upon while looking for something else. What I can tell you is this...

1) When using fdisk in Android you must specify the device to look at. Try something like: fdisk /dev/block/mccblk3 That should list the current partitions as defined by CWM or whatever was used originally.

2) Within one of those partitions in the list generated above are sub-partitions holding the bootloader, system, data, etc partitions. You can see how they're described in the .cfg files in the nvflash restores that are lying about.
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
Removes user apps and their associated data as well as system related data and settings.
[G Tablet Q&A, Help & Troubleshooting] CodeNamePapa:
K J Rad - any idea if the partition size can be set with these methods (2048 & 0) in case I can't get clockwork installed?
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
I'm looking for a solution to that problem. Unfortunately these methods still require the ability to get into recovery mode which likely won't work if you're having trouble getting CWM installed.

If, however, you can get into recovery... then it is theoretically possible to create a script that would accomplish that. As soon as I have one I'll be adding it to the mix ;-)

Edit: I've found something I think will work. Will do some testing tonight. It will still require access to recovery.
[G Tablet Q&A, Help & Troubleshooting] cyberpyr8:
I wasn't sure if you saw my other post but I am seeing no partition 0 when I NVFlash with a verifypartition.

http://xdaforums.com/showpost.php?p=13059520&postcount=57
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
I haven't yet but I will. Let's try to keep this thread on topic. Thanks.
[G Tablet Q&A, Help & Troubleshooting] CodeNamePapa:
More thoughts:

because I went w/ cyan7 is it possible i have a "bad" kernel and that the stock bekit-1105 or the roebeet-3588 files are crashing w/ the kernel in place already?

I know custom ROMs can have a custom kernel applied separately, but I have no idea whether cyan7 loads it's own kernel...

I have yet to try the nvflash_gtablet_46 version, as I see the img files w/in are different from the original 1105 .zip

Also:

read on another thread that part 2 and part 3 aren't loading for other users when doing nvflash - I did notice that it pauses, runs some stuff, then starts loading part 4 through to the last part, then success. - do part 2 and 3 run for you?

edit: I see a 4349 downgrade.zip in another thread for those who got the OTA update but want to go back to stock 3588 prior to jumping off somewhere else - I can't expect that would help me as I can't do squat w/ recovery yet, but could that possibly "reset" any bad kernel problems? - again, I'm just thinking out loud.
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
This is well outside the scope of this thread but I find some of what you mention interesting so I'll address it and then end any further off topic discussions.

I did not build nor have I ever used Cyan7 so I have no basis for an opinion on the matter other than this... Each ROM comes with a kernel installed so if properly done an nvflash should overwrite any "bad" kernel.

Part2 and Part3 do indeed load, they are just displayed differently than the other Parts. Just minutes ago I flashed down from Mountain Laurel (4349 based with the new bootloader and recovery) with absolutely no trouble. I can, and have, read back those partitions after an nvflash to prove that point.

The 4349 downgrade will only work for you if recovery is working. Having never used it I don't know that it would "reset" the kernel but any subsequent flashing of a new ROM image would.

I am working on a stock recovery solution for partitioning but it isn't likely to help anyone who is stuck in an APX loop. I do have some ideas on what might help for that condition but I haven't been able to get my hands on one for testing and trying to help people here is like being a consulting mechanic for a car repair that's in someone else's shop having work done on it that you're not being told about.

I'll be happy to address any further comments or questions regarding your specific issue in an appropriate thread or via PM. Thanks.
[G Tablet Q&A, Help & Troubleshooting] lsu205:
wipe cache, wipe data root?

If you use either method 1 or 2 in your 1st post, to wipe cache and or data on a gtablet that is rooted, does it stay rooted? Thanks

PS, your method plus Roebeets TNT stuff are the best things since sliced bread:cool:
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
If rooting is done properly it puts SuperUser in system so it should survive a data wipe.
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
Glad to hear you got it going. Even just one in the win column makes it worthwhile ;-)
[G Tablet Q&A, Help & Troubleshooting] familiozo:
I try this on my ly 706 but nothing is stil dead..
[G Tablet Q&A, Help & Troubleshooting] patne83:
I brick my tablet trying to change the bird logo, cound"t pass the g tab logo. i started to look for a fix ,try multiple but nothing worked untill i stumbled in to your fix.and i could not belive how easy that was , thanks man
[G Tablet Q&A, Help & Troubleshooting] K0MM4ND3R:
YESS!

I cannot thank you enough!!! worked !!! i spent 2 days doing all kind´o´stuff...and nothing, luck u r here! hugs!!:victory::victory::victory:
[Thunderbolt Q&A, Help & Troubleshooting] Vaporsilver:
For the life of me I can't figure this out. I installed Handscent on my Thunderbolt and now it is sending the same text 2 - 3 times. I've tried uninstalling, clearing data, clearing cache and nothing works. I disabled every notification on the standard messaging app but it just keeps doing it.

Anyone have any ideas?
[Thunderbolt Q&A, Help & Troubleshooting] drweltman:
No ideas, but you're not alone...
[Thunderbolt Q&A, Help & Troubleshooting] Vaporsilver:
I just want to bump this and say that it is happening with GoSMS and the stock messaging app as well. I wonder if it's the network.
[Thunderbolt Q&A, Help & Troubleshooting] knave68:
I had to do clear data in messaging app in Manage Applications menu. Just make sure there are no messages you want to keep because you will lose them.
[Thunderbolt Q&A, Help & Troubleshooting] jett2314:
Had the same issue. I called Verizon to report it. I rebooted and have not had any issues. Well none that I know of. Not sure if it was the network or my phone.
[Thunderbolt Q&A, Help & Troubleshooting] Vaporsilver:
Yeah nothing is working. Using stock app and cleared data, still doing it. I'm beginning to think it has to do with the DasBAMF Rom because it didn't happen until I started using the rom.
[Thunderbolt Q&A, Help & Troubleshooting] DarwynZ:
Give it a day... its more than likely the network and not the ROM... ive used many different ROMs on my D1 and this problem would come and go from time to time... often without even changing ROMs.... give it 24 hours, if it doesnt stop, try a new ROM then, dont give up on it so fast.
[Thunderbolt Q&A, Help & Troubleshooting] tonyagee:
This was happening to me about two weeks ago. It worked itself out.
[Thunderbolt Q&A, Help & Troubleshooting] Smok3d:
Have you guys tried freezing the old msging app?
[Thunderbolt Q&A, Help & Troubleshooting] tflogic:
it's happening on my stock TB...pretty sure it's just the network considering my blackberry used to do this as well.
[Galaxy S I9000 General] losdrivare:
I recently bought a second-hand SGS, supposedly locked to 3. The firmware was from 3 UK, but when I punched in *#7465625# it showed all locks are OFF.

Hot for tasty Froyo, first thing i did was to upgrade from the branded Eclair ROM the phone came with to an unbranded stock Froyo ROM. Kies gave me a hard time so I used ODIN. Then I inserted my SIM and realized I could not make calls or even register on my GSM network. (Had not tried the SIM before, so I don't know if the flash caused this)

I found out that the flash had changed my Product Code to KOR, but I managed to change it using THIS GUIDE. However, the step "rm -rf /efs/nv_data.bin.md5" did not work as it was write/read protected. After reboot, the SIM didn't work so I did the "busybox chown 1001:1001 /efs/nv_data.bin". The procedure changed the Pcode to H3G, which I think is the original code, although I was going for XEE.

IMEI has not changed (*#06# gets same no. as is printed below battery)

I live in Sweden, my present CSC is XEE, Product Code is H3G. Network Control Key is 00000000, could this be related?

I considering doing the Product Code change procedure again and see if I can change it too XEE hoping that will fix it, but I'm not even sure this is related to my problem.

Other than that, I'm running out of ideas. However, I'm new to the SGS scene. I'm reaching out for someone with more experience to give me some new ideas.

I've spent hours and hours at this and I've googled like possessed. If I'm being a noob or have overlooked something, let me know - just tell me what I should do to fix this phone. :)
[Galaxy S I9000 General] rschenck:
Go into Settings > Wireless and Network > Mobile Networks and check that Network Mode reads as auto mode. Then open Access Points Names and check that APNs are listed that suit your carrier.

If all of that checks out, go into an app like SGS Tools and use the secret code to check Band Selection.
[Galaxy S I9000 General] losdrivare:
Thanks for your reply! :)

I have inserted APN for data. Though, is this really necessary just for 2G calls and SMS?

When I choose "Select Automatically" in Settings/Wireless and network/Mobile Networks/Network Operators then I sometimes get "Registered on network". Then, when trying to call, I get "Data network not available". Band Selection (from SGS Tools secret codes) show:

= BAND SELECTION =

[1] AUTOMATIC []

[2] WSCDMA BAND []

[3] GSM BAND []

[4] COMBI BANDS []

When I select the network operator manually, I get "Unable to select network. Select automatically".
[Galaxy S I9000 General] JJEgan:
An alternative Go to Rom Kitchen build a rom with

XWJS8 > Hardcore Kernel >CSC CPW > Modem JPY and whatever else you require that should give all UK main networks .

http://romkitchen.org/sgs/?s=generator

jje
[Galaxy S I9000 General] rschenck:
I got Data Network not available when I was investigating my phone (that is, messing about) and changed my Network Mode. Go to Settings > Wireless and Network > Network Mode and choose GSM/WCDMA Auto mode. If you don't have connection, then try first GSM Only, then WCDMA Only...then back to both.

And yes, you need to have a data network connection to make calls. Not sure why. Must be something to do with billing.
[Galaxy S I9000 General] ross_ctr:
I would hate to be right but are you sure, as you've bought it second hand, that it hasn't been registered as stolen? Do you know any history of the phone?
[Galaxy S I9000 General] [Ramad]:
Product code should be GT-I9000HKDXXX, where XXX should be your CSC which is XEE that makes it: GT-I9000HKDXEE, you should not use H3G at all.
[Galaxy S I9000 General] [Ramad]:
double post...sorry
[Galaxy S I9000 General] losdrivare:
Thanks, but I would need the Swedish networks. The phone is from UK whereas I live in Sweden and have a Swedish operator (halebop).

Weird, I was sure APN is only required for MMS and Internet, not for calls and SMS. Anyway, I have APN so that's not it.

No, I don't and I can't be 100% sure it's not stolen. However, I have a bill of sale with all his information and I know where he lives so if that's the case, it can be sorted.

I think you are right, and I managed to change it so now both CSC and Product Code reads XEE, which should be correct for Sweden. However, the problem remains the same. :(
[Galaxy S I9000 General] losdrivare:
There is a possible solution from HERE, however it seems rather ...old. Having no other ideas I'll try it unless someone comes up with a better idea:
[Galaxy S I9000 General] sxi200:
Have you tried doing a factory reset? May not work but may be worth a try.

Could only be either apn related (doubtful), faulty sim or stolen/lost phone. Unless hardware related.
[Vibrant Themes and Apps] jellette:
As the title says, here is a new mms.apk for you guys to use on the 2.2.1 roms that IS NOT blurry.

Just adb push it to system/app or use root explorer to move it there and overwrite - you can also rename your old one to mms.apk.bak in case you want to switch back later.

I'm still working on the smilies..
[Vibrant Themes and Apps] xtone:
this is touch wiz yes?

edit: just pushed it, it is touch wiz and no blurry mms.

for those who like smiley on the keyboard this still doesn't have that.
[Vibrant Themes and Apps] jellette:
Yeah, still working on that - but at least it is a step closer.
[Vibrant Themes and Apps] xtone:
true, I used yours hoping you had that fixed coz I got the blurry mms taken care of myself, but we are getting closer! thx for all your contributions heathen.
[Vibrant Themes and Apps] december.underground:
Just look at my post on eugeens post and I posted a fix for it just change it to n95 on the custom user agent.

0bey <-_->
[Vibrant Themes and Apps] jellette:
Yes, but that assumes you are using the cyanogen mms or another mms modded with user changeable user agent and not a straight stock mms like this - which has been changed to an iphone user agent. This is for people who want a stock mms.
[Vibrant Themes and Apps] AgentFour20:
Thnx gonna give this a try
[Vibrant Themes and Apps] mytouchguy:
is this flashable via CWM if complied in a zip?
[Vibrant Themes and Apps] AgentFour20:
This can be pushed with RootExplorer
[Vibrant Themes and Apps] mytouchguy:
dont have root explorer... nor do i know how to do system pushes... if its CWM flashable i can compile a zip.. that much i know how to do.. lol
[Vibrant Themes and Apps] cpittman:
NM I'm an idiot.
[Vibrant Themes and Apps] jellette:
I can probably build the flash from my phone, brb.
[Vibrant Themes and Apps] jellette:
Built from my phone. Should work.

Flash:

http://db.tt/fEeC5OE
[Vibrant Themes and Apps] Nabeel10:
Want is "non-blurry mms"? Cause I've never really noticed anything "Blurry" in it.
[Vibrant Themes and Apps] starkiller86:
Thank you so much! I was looking for a fix for a few weeks and was afraid I would have to flash back to plain 2.2 roms. I didn't want to switch to an AOSP mms to fix this either didn't like the feel of it. I guess I got used to the tw mms. Thanks Again!! :D
[Vibrant Themes and Apps] leocreo:
You sir are the MAN!!!
[Vibrant Themes and Apps] LowDub:
I'm getting a message "the media content was not included due to a picture resolution or message size restriction" when receiving a message from anyone besides myself. Has anyone else seen this issue?
[Vibrant Themes and Apps] ericd07:
thanks a lot man!
[Vibrant Themes and Apps] mystycs:
Doesnt work on bi winning v2 i keep getting failed messages when i send texts.
[Vibrant Themes and Apps] Papote3:
Getting the same problem, is there any fix to it, or does it mean it just doesnt work?
[Vibrant Themes and Apps] ipnekgs:
Reboot the phone, it needs to populate the message centre in Settings
[Vibrant Themes and Apps] LowDub:
Out of curiosity, are you running overstock 2.x?
[Vibrant Themes and Apps] Crkr:
I'm getting the same error as both of y'all with MMS not working. Using the bullet kernel.
[Vibrant Themes and Apps] LowDub:
Details of my setup(s) that I've seen this error on:

Rom: SimplyGalaxy 2.7.2, SimplyArabic V1.0

Kernel: Overstock 2.X (current release), Tiger's Blood (current release).

I've tried everything from full wipe to full downgrade/re-root and install. Some dev support here would be helpful.
[Vibrant Themes and Apps] Papote3:
Using overstock 1.5.1

I used the cm6 mms apk and now it works.

Receiving mms in full clarity. And I always use handcent for msgs

Sent from my Vibrant
[Vibrant Themes and Apps] Crkr:
Did the same and it worked, non-blurry. But I had to change the APN too in order for it to work. Plus the CM6 mms apk has the smileys on the keyboard which I like a little better
[Vibrant Themes and Apps] mystycs:
Anything with smilies?
[HD2 General] airsoft_ben_1989:
Hi guys, in need of a bit of help here.

right, having not realised what i had done, i pulled the battery whilst on charge before i pulled the charger. my current situation is that now the phone is stuck on the loading bit. the version of android i have comes up with "droid" then goes to a red eye like thingy whilst loading. it keeps looping that screen over and over.

after a quick search i saw my problem could have been bent battery connector pins, but alas they are fine.

after another search i reasised what i had done (or at least what i think i have done). would i be right in thinking that the battery now does not have enough power to boot android and get to a point where it can charge the battery?

having seen the threads on here about using a USB lead to manually charge the battery i am at my wits end. i tried the USB fix and it didnt work.

i have now found this thread: http://xdaforums.com/showthread.php?t=978101

and am currently attempting to charge my phone using the "USB mass storage" setting on MAGLDR (v1.13 btw) but the bit that im wondering is the bit that says "you will NOT get a charging indicator in this mode"

does any one know for sure whether this is true? i am hoping that the thread is correct my only doubt has arisen due to the fact that the thread was based on a HD2 running WP7.

thanks in advance for any help

Ben
[HD2 General] pvii:
Try to measure voltage at pin +/- on battery. If there is more than 3,6V battery is able to boot up the phone if voltage is belov 3V it's bad. If You have an adjustable (for laboratory use) voltage source, connect it to pins of phone vhere normally must be connected +/- leads of battery (carefully check polarity), give it 3,7V and try to load the bootloaderon the phone (hold Vol.Down butt and power button together). If it doesn't work, you may have ruined the bootloader.
[HD2 General] T-Macgnolia:
I read some of the thread you linked. There is something that I think the OP of that thread and a whole lot of people using MAGLDR do not understand. I qoute this straight from the OP of the MAGLDR thread.

You have to have a functional OS installed for you to even be able to charge your battery using your HD2 when you have MAGLDR installed on your HD2. The simple fact that the OP of that thred has a WP7 ROM installed on their HD2 is the only reason option #4 USB Mass Stg even will slightly charge the battery, if it was no ROM on the phone, just MAGLDR, it will not charge at all just as when you are in bootloader and the USB connected it will not charge no matter if you have a ROM on the phone or not. I personally think the slight charge you get by using option #4 USB Mass Stg in MAGLDR is purely accidental and only a small amount of voltage as it takes so long to get any kind of substantial charge. Also if you have a completly dead battery you can not even boot into MAGLDR to try to charge using opyion #4 of MAGLDR.

I am a electrician and have been for a little over 15 years and in my oppinion if you have a dead battery and you are running Android from NAND or a WP7 ROM using MAGLDR. Your best bet is to use.

A: A external charging cradle.

B: Another HD2 that is running Win Mo.

C: Using a modified USN cable to get enough charge to boot into your ROM

Note: The last option I listed is only in a emergency situation as I do not advice you use this as a everyday charging technic. Also only long enough to boot your phone so you can finish charging normally. If you do use this option maintain a constant watch of the battery to insure it does not start to become warm, and only use your wall charger when using this method. The voltage is very low that the wall charger sends though the witres so there is no danger of shock.
[HD2 General] pvii:
Do You mean that when HD2 is POWER OFF state it doesn't charge battery? Even from wall charger? Mine does charging pretty well when turned OFF...

All phones I repaired or dizassembled had hardware automatic for charging battery, not depending of ROM or OS at all, it must have only 5V at charger inlet (USB or dedicated charger port i.e. for NOKIA), I doubt if HTC gone other way that all other developers ;)

Can You tell me more about this cable? Any schematics?
[HD2 General] T-Macgnolia:
Yes a HD2 can charge in a powered off state if you are still running a Windows Mobile ROM on it. If you have flashed MAGLDR to your HD2 you will not be able to charge your HD2 until you flash a Android or WP7 ROM to it as the charging is to quote the OP of the MAGLDR thread again, "Battery controller inside LEO needs runtime control during charge, it implemented in OS."

As for as a schematic no real need for a schematic. You take and cut the end off of a USB cable, the end you leave on needs to bt a standard USB male end. Next you strip back the outer insulation and the inner foil layer, then strip a little off the ends of the black and red wires. Finally connect the red wire to the positive terminal of the battery (marked on the battery), and connect the black wire to the negative terminal on the battery (marked on battery) and plug the USB male end of the cable into your wall charger, not any other power source. Yopui can use some tape to keep the ends connected to the battery.