Hello,
i've found that somewhere in our ancient G1's is hidden partition where's stored stock firmware with stock radio, SPL and recovery. I wasn't using it and had it off about 2 months. When I've brought it back to life i was very surprised that it was derooted, stock. I had to do it again, everything. So it means that somewhere has to be partition with it. I think this could save bricked phones and it could be used as extended phone memory. Just an idea..
you sure its the same G1?
Maybe its your brother/sisters one
Removed...
kostnacsek said:
Hello,
i've found that somewhere in our ancient G1's is hidden partition where's stored stock firmware with stock radio, SPL and recovery. I wasn't using it and had it off about 2 months. When I've brought it back to life i was very surprised that it was derooted, stock. I had to do it again, everything. So it means that somewhere has to be partition with it. I think this could save bricked phones and it could be used as extended phone memory. Just an idea..
Click to expand...
Click to collapse
post tech detail or me think u = idiot
You'd be the first person it has happened to.
I see two options;
1. you're right and there's said "rootkit", it would bridge the gap between trout and sapphire boards by possibly bringing trout storage capacity closer to that of sapphire because, otherwise, they're identical.
2. the rooted build you were using was possibly using a build fingerprint that allowed the updater program to identify it as a legitimate device. if the new boot took longer than expected (or if for any reason during those two months the phone was turned on by somebody else without your knowledge and given access to a network) then there's the possibility that an OTA update was delivered and the phone updated, but I believe those updates require confirmation (unfortunately, my ADP1 doesn't receive OTAs, so I wouldn't know how the process works).
I'm more inclined to believe that the second option is the most likely, but the first option sounds tempting. Has anybody done a close inspection of the trout and sapphire boards? how different are they inside? is the nand inside the msm chip or outside on the pcb? if the nand is inside the msm, then it would make very little sense for qualcomm to make only one chip that was used exclusively for only the htc dream (is there any other device that uses msm7201A AND has only 256 MB internal storage?) and make an exactly identical one for wider use...
====edit====
After some wikipideaing, found out that there's only one another HTC device that uses the same layout as the dream, the touch diamond (msm7201A AND 256 nand). The majority of MSM7201As all have the sapphire's 512 nand. Oh, well, it was worth a shot.
So you're saying that patition maybe really could exist? I'm not a developer, i don't really understand it.
And ad 2. thougt - I can be really sure that no-one but me turned the phone on and boot was pretty fast opposed to CM 6 which i was using before this incident. And even if so, it wouldn't be 1.5 ...
kostnacsek said:
So you're saying that patition maybe really could exist? I'm not a developer, i don't really understand it.
And ad 2. thougt - I can be really sure that no-one but me turned the phone on and boot was pretty fast opposed to CM 6 which i was using before this incident. And even if so, it wouldn't be 1.5 ...
Click to expand...
Click to collapse
practically no developers on xda-developers
the question is why do you think there is a hidden partition
and I do hope you are not getting mixed up with French cache
we all know about cache
And where could be whole stock firmware stored if it isn't in partition which is hidden for us? BTW it has to be in ready-to-use state, something like a BART backup, the partition must be big enough.
I think that if we knew about it, we were using it now, in example as extension of phone memory. Or as i said to recover bricked phones. It just happened that way. If you have other phone you could use instead, try to power off your G1 for same time.
You wanted tech specs - i dunno what exactly you want, it's just general G1, not ADP, stock version was 1.5. And even if i had last SPL, radio, AmonRa's recovery, after two months off, everything was stock, 1.5. I tried to start recovery - stock,.. i had to do whole rooting process again.
BTW - what's French cache?
kostnacsek said:
And where could be whole stock firmware stored if it isn't in partition which is hidden for us? BTW it has to be in ready-to-use state, something like a BART backup, the partition must be big enough.
I think that if we knew about it, we were using it now, in example as extension of phone memory. Or as i said to recover bricked phones. It just happened that way. If you have other phone you could use instead, try to power off your G1 for same time.
You wanted tech specs - i dunno what exactly you want, it's just general G1, not ADP, stock version was 1.5. And even if i had last SPL, radio, AmonRa's recovery, after two months off, everything was stock, 1.5. I tried to start recovery - stock,.. i had to do whole rooting process again.
BTW - what's French cache?
Click to expand...
Click to collapse
http://www.answers.com/topic/cache
http://en.wikipedia.org/wiki/Caché_(2005_film)
Caché loosely translated is hide,conceal,mask
this is where cache comes from
Effdee said:
post tech detail or me think u = idiot
Click to expand...
Click to collapse
loll you always speak your mind
e334 said:
loll you always speak your mind
Click to expand...
Click to collapse
cruel to be kind
Related
No, not a ROM flash: I want to completely erase every last piece of data in my Tilt and install the SPL, OS, and radio from scratch.
As far as I can tell, FrankenKaiser will do that, but it (in theory) only works with the radio from hell... which I have, albeit the "_patched" version...
I am trying to work from a clean slate, rather than flash another ROM... trying to clear up a problem that I think can only be fixed by such a drastic move... and of all the posts I've seen, (unless I'm retarded - quite possible) none has addressed such a move. Is FrankenKaiser the solution? If so, do I need to put the radio from hell on first? If it's not the solution, what is? Or is there one at all?
Thank you
drunkbastard said:
No, not a ROM flash: I want to completely erase every last piece of data in my Tilt and install the SPL, OS, and radio from scratch.
As far as I can tell, FrankenKaiser will do that, but it (in theory) only works with the radio from hell... which I have, albeit the "_patched" version...
I am trying to work from a clean slate, rather than flash another ROM... trying to clear up a problem that I think can only be fixed by such a drastic move... and of all the posts I've seen, (unless I'm retarded - quite possible) none has addressed such a move. Is FrankenKaiser the solution? If so, do I need to put the radio from hell on first? If it's not the solution, what is? Or is there one at all?
Thank you
Click to expand...
Click to collapse
This is possible, but why?
After you wipe your phone you will be re-flashing the ROM / Radio and SPL anyway.
If you do do this, make sure you read and understand the process (and what the pre-requisites are first).
Ta
Dave
Install Sleuth's V_3.0 WM6.1. I have moddified a version with Jocky to work with that OEMSBL version.
I will PM you with a link for the moddified FrankenKaiser, hey that sounds familiar, ohh yeah, Jocky let me name it!
HOWEVER, I think I'd try a few other things first. Like check the Radio Protocol. On boot does the red protocol version end in H or W? W is not for US & can create issues with 3G. Also, you can try using MTTY with my G3SPL MFG_SPL to fomat a few thing & to flush out Nand blocks. Many things to try before venturing to FK. I know you PM'd me, but I've been a wee bit busy, I'll make a little time if I can help though. Try me on MSN/Live Messenger [email protected] (Even if it says "Offline" give it a try, I may just be lurking)
Protocol ends in H, currently using the Neon 1.58.25.17 radio, I have tried virtually every other 6.1 radio in existence, and about a dozen different ROMs, including the stock AT&T and letting the bloatware install just for poops and giggles. But not the one that you suggested GS, what the hell, one more ROM flash ain't gonna hurt...
I am reticent to think it's a hardware issue because the G and H icons do appear, I just can't get a connection, and it all happened while using the GPS (LiveSearch and HTC GPS Tool specifically). If it was hardware related I would imagine that I wouldn't get the icons, it would just show no service.
Also, the reason I wanted to do a complete whitewash is because, even when installing a new ROM, I have noticed that certain traces and settings remain from days gone by (certain registry settings, POP3 accounts, etc), which I find odd.
I would be interested in the MTTY approach, a link would be appreciated... running out the door now to go play bar manager...
Sorry GS, didn't wanna seem impatient, just trying to get a wider input as to a solution, so I can (a) fix mine and (b) maybe suggest to others (a bunch from what I've seen, here and elsewhere) with the same problem, rather than everyone sending them to AT&T / HTC for replacements.
Personally, I think that the 3G issue is some corruption somewhere in the phone's firmware that a ROM/radio/SPL change doesn't affect, and - as much as I hate to invoke such people - the guys at AT&T that looked at it believed the same, didn't think it was an antenna issue (although the widespread belief is that it IS, and furthermore that anyone working at AT&T is a dolt - which IS usually the case). Far be it from me to be naive, but one would think that if this was as widespread a problem as it is and was hardware related that there would be a recall, which there hasn't been.
Again, thanks to everyone for their assistance.
So, I guess the next question is... how do I use MTTY to, as GSLEON suggested, flush out the bad blocks?
Again, thanks in advance to anyone who can help me.
go ahead and read up on this post. It will explain everything for you...
http://forum.xda-developers.com/showthread.php?t=371154&highlight=MTTY
drunkbastard said:
No, not a ROM flash: I want to completely erase every last piece of data in my Tilt and install the SPL, OS, and radio from scratch.
...
Thank you
Click to expand...
Click to collapse
You could try this: http://en.wikipedia.org/wiki/Neutron_bomb
No seriously, which way do you flash a rom ?
Just flash and basta? Flash and HR after that ? Have tryed with a different computer /os ? From SD card ? I had some reminiscent traces of previous roms if I didn't hard resetted after the flash.
Dredd67 said:
You could try this: http://en.wikipedia.org/wiki/Neutron_bomb
No seriously, which way do you flash a rom ?
Just flash and basta? Flash and HR after that ? Have tryed with a different computer /os ? From SD card ? I had some reminiscent traces of previous roms if I didn't hard resetted after the flash.
Click to expand...
Click to collapse
Thought about it, but motherf*%$# Al-Qaida has made getting my hands on one so difficult.
I flash from a WinXP PC, have not tried another one because this is the only one I can get my grubby little hands on, flash / HR. Have not tried from SD card. I have had traces of old ROMs as well - I tired using PDAUltimate v6 and still had the splash screen from Garmin 4.4c... odd... that and other incidents of remnants of ROMs gone by.
You may want to check here and see if there is anything that may apply. (This is coming from someone that had a 3G failure.)
http://forum.xda-developers.com/showthread.php?t=400610&highlight=JohnJonsten
drunkbastard said:
I am reticent to think it's a hardware issue because the G and H icons do appear, I just can't get a connection
Click to expand...
Click to collapse
Well, that IS the usual behavior when the radio hardware goes poof, many people including myself experienced it. In the end GPS failed too on mine, as well as the GSM radio, and the phone was always running hot and draining batteries extremely quickly.
See the link posted by John.
The quick and dirty of it is....
1. The Icon lighting up means the radio and protocol is correct to talk on the correct 3G bands in your area
2. From what I have been able to gleen on how the 3G signaling works (not an expert here) it is basically GSM signaling for the UMTS/HSDPA Voice/data path buildup.
3. It is most interesting to go to an area that has non PCS band 3g, use field test to verify this if you want, you can lock your phone on edge and use voice and data 850, but will not be able to build up a UMTS/HSDPA connection on 3G. You need to go to a non PCS area as I have seen for the most part in Seattle they run the edge net on 850 and 3G on PCS frequencies.
kilrah said:
Well, that IS the usual behavior when the radio hardware goes poof, many people including myself experienced it. In the end GPS failed too on mine, as well as the GSM radio, and the phone was always running hot and draining batteries extremely quickly.
See the link posted by John.
Click to expand...
Click to collapse
When I boot up the phone, I get a message in my notification bar saying:
Damaged Internal SD Card.
Not an external memory card. My internal SD card. The one built into the phone. Anyone know if there's a way to fix this? Is there a way to reformat the built in SD card? My computer can't recognize it anymore. Am I pretty much screwed?
I posted this in androidforums as well.
EDIT: I found the "Format Card" option in settings. It's working fine, although the fact that this came up in the first place is very troublesome. Some further information: I did the GPS thing where you dial *#*# and some number, then rebooted my phone. My internal card was fine until I rebooted. That was the first time I got that message of a damaged internal sd card.
dude same thing happened to me today - any way to fix this ?
Format it, and hope you never see those dreadful words again.
norcal einstein said:
Format it, and hope you never see those dreadful words again.
Click to expand...
Click to collapse
This is a known fact that has been reported on some Galaxy S phones, it is coming from doing multiple Lag fixes of the phone internal SD from RFS to EXT. buyer be ware when flashing lag fixes over and over.
dpmurphy81 said:
This is a known fact that has been reported on some Galaxy S phones, it is coming from doing multiple Lag fixes of the phone internal SD from RFS to EXT. buyer be ware when flashing lag fixes over and over.
Click to expand...
Click to collapse
what about when you flash a ROM that comes with LAg fix by default ? and you Disable it all the time can that happen to you? cuz ive flashed but most roms r being gay now with Lag fix ... i disable always might i get that msg? :/
dpmurphy81 said:
This is a known fact that has been reported on some Galaxy S phones
Click to expand...
Click to collapse
This affects the bell vibrants only, the captivates never had this issue.
peachpuff said:
This affects the bell vibrants only, the captivates never had this issue.
Click to expand...
Click to collapse
One can assume that the captivate can have this problem also the hardware is no different really from the vibrant. And I feel in my opinion that it is related to the quality of the flash memory chip itself weather you have this problem. compound this with the relentless conversion of the RFS file system it is just a matter of time I believe. The trade off of speed is stability. But that is only my opinion...
dpmurphy81 said:
One can assume that the captivate can have this problem also the hardware is no different really from the vibrant. And I feel in my opinion that it is related to the quality of the flash memory chip itself weather you have this problem. compound this with the relentless conversion of the RFS file system it is just a matter of time I believe. The trade off of speed is stability. But that is only my opinion...
Click to expand...
Click to collapse
That actually is a pretty big assumption. Just because two phones appear "similar" based on the published specs doesn't mean their insides are at all related. We already know that from a strictly hardware standpoint, even the two GSM cousins in America (the Vibrant and the Captivate) have different physical hardware inside, and many other versions of the i9000 abroad vary quite a bit too. Samsung produces these phones in very large batches, and who knows exactly what the differences are in the individual components put onto each board.
And as far as I'm aware, there's not been a single case of repeated "lag fix" operations causing damage to the hardware. Which makes sense when you think about it too. If I load a single 720p movie onto my internal SD (OneNAND), that probably requires a lot more NAND cells to be touched than an entire system/data/dbdata/cache lag fix being applied. Since all those operations really do is backup the partition, delete the partition, format a new partition, and then restore the data back over. Not really the most intensive thing you can do with your internal SD...
The OP's problem probably lies somewhere in PEBKAC. Not unmounting storage cleanly from the PC, or accidentally unplugging during a file transfer, battery came out unexpectedly at some point, etc. I end up re-flashing my ROM so regularly that I never really have time for little problems to build into big problems, but that might have happened here. Just so many corrupt sectors before the OS finally gives up trying to deal with it. Either way, since formatting seems to have fixed the problem, and this storage is solid-state, not mechanical, the problem is probably not in the hardware.
I had this issue on my captivate, as did two others that I know of, with a certain release of voodoo lag fix. Haven't heard of complaints since, and although it was tricky to fix haven't had problems since
Its not just with Bell phones. But I agree I think its software not hardware (at least for us Cappy folks!)
Sent from my GT-I9000 using XDA App
fatttire said:
I had this issue on my captivate, as did two others that I know of, with a certain release of voodoo lag fix. Haven't heard of complaints since, and although it was tricky to fix haven't had problems since
Its not just with Bell phones. But I agree I think its software not hardware (at least for us Cappy folks!)
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
What was the fix you applied exactly? I'm interested to it. Thanks
I would like to know what else i can try. I am currently.experiencing the same damaged internal sd card issue and have tried reformatting to no avail. It just seems to skip the actual formating. My pc also cannot see the phone as a drive. Any help would be appreciated.
Bump. Having the same issue. Cant see any files in 'my files' (samsung galaxy s i9000), internal sd wont mount or format in clockworkmod recovery
Hi guys, Did you solve the problem somehow?
I just wanted to state that this may be correctable with JTAG. If you guys are interested in letting me try to correct this with JTAG please let me know. I have been able to fix, what I refer to as partition bricking on the i9000 and T959 Vibrant and this sounds similar.
Nah.... JTAG is fully unnecessary. See, the SDCard is a shared space. It's likely the cause of this problem was flashing an inappropriate PIT file after performing a lagfix. Try flashing the stock pit file... I'd attach it as it's really small, but i seem to have lost it . You're going to need to do a total reset on your phone. Use CWM to wipe and delete and format everything you can.
If this is an ACTUAL bad SDCard, then nothing will bring it back short of replacing the chip. JTAG would not be the way to go for this.
AdamOutler said:
Nah.... JTAG is fully unnecessary. See, the SDCard is a shared space. It's likely the cause of this problem was flashing an inappropriate PIT file after performing a lagfix. Try flashing the stock pit file... I'd attach it as it's really small, but i seem to have lost it . You're going to need to do a total reset on your phone. Use CWM to wipe and delete and format everything you can.
If this is an ACTUAL bad SDCard, then nothing will bring it back short of replacing the chip. JTAG would not be the way to go for this.
Click to expand...
Click to collapse
Not trying to butt heads with you but I've worked on many phones with what I refer to as "partition bricking" and they were not fixable with any method of flashing. I've gotten a few that were able to be fixed with PIT repartitioning but many have not been. Also see the other thread I replied to you in as JTAG could be a fully capable solution in this instance.
As stated, JTAG can address any portion of the NAND, not just the PBL and SBL blocks.
connexion2005 said:
Not trying to butt heads with you but I've worked on many phones with what I refer to as "partition bricking" and they were not fixable with any method of flashing. I've gotten a few that were able to be fixed with PIT repartitioning but many have not been. Also see the other thread I replied to you in as JTAG could be a fully capable solution in this instance.
As stated, JTAG can address any portion of the NAND, not just the PBL and SBL blocks.
Click to expand...
Click to collapse
Sure, it can. By default Riff does not. Also, JTAG is overkill for a bad partition flash. Just reformat from CWM and it should be fine.
AdamOutler said:
Sure, it can. By default Riff does not. Also, JTAG is overkill for a bad partition flash. Just reformat from CWM and it should be fine.
Click to expand...
Click to collapse
RIFF DOES SUPPORT THIS NATIVELY. Also, the phones I obtained were not fixable with CWM repartitioning. I spent hours on the first few to still have mount issue with DBDATA and /dev/block/mmcblk0p1 and /dev/block/mmcblk0p0 errors. I have found a few that were fixable with re-partitioning via ODIN but several that required JTAG to fix. I didn't spend days trying to find the perfect combo before turning to JTAG but I spent a lot of time on many of these phones.
Hi Connexion, I would be interested in trying this, can we do this to Korean Variant of Galaxy SHW M110 (anucall) let me know
Hi,
Unfortunately, that is not a supported model on the RIFF box right now. I sent you a PM I believe with some advice though to hopefully get through it.
We learned about this on the IRC tonight, so I wanted to pass it on. The v2 Malata devices have a different partition stucture, as well as 1GB of RAM and not 512. It seems that this device is actually showing up in the States, and at least one user here in XDA got one via a SEARS.COM order.
His model number is UPC-320-2.2, and 1GB RAM should actually show on the box, as well. If you happen to have one of these, consider yourselves lucky for the RAM bump, but also unlucky because using our nvflash batch scripts could bork your device. So beware. It's also possible that bekit had one of these, at one point.
Since most of us don't even have the device, there's really no way for us to support it. I would actually love to get my hands on one of these things, but the likelihood of getting one of these is probably very slim.
Also, be aware that having a 300 is still no guarantee that the nvflash tools will work. As far as we know, there could be 320's repackaged in 300 boxes. Just the fact that these v2's showed up in the States at all should something to keep in the back of your mind.
Wait, so this one is brickible?
I wonder if that model is ready for a SIM card???
bijan588 said:
Wait, so this one is brickible?
Click to expand...
Click to collapse
Not that I know of. The only couple people that did use the original restore on one of the 1GB models did get it back working with the restore built for them.
Darn! I got a 300-2.2 ...
jimcpl said:
Darn! I got a 300-2.2 ...
Click to expand...
Click to collapse
Me too
Well I guess its not all bad. Our device is actually supported, so
How's the viewing angle on that model? ( Got UPC300-2.2. ) meh is running perfectly so no complain.
roebeet said:
We learned about this on the IRC tonight, so I wanted to pass it on. The v2 Malata devices have a different partition stucture, as well as 1GB of RAM and not 512. It seems that this device is actually showing up in the States, and at least one user here in XDA got one via a SEARS.COM order.
His model number is UPC-320-2.2, and 1GB RAM should actually show on the box, as well. If you happen to have one of these, consider yourselves lucky for the RAM bump, but also unlucky because using our nvflash batch scripts could bork your device. So beware. It's also possible that bekit had one of these, at one point.
Since most of us don't even have the device, there's really no way for us to support it. I would actually love to get my hands on one of these things, but the likelihood of getting one of these is probably very slim.
Also, be aware that having a 300 is still no guarantee that the nvflash tools will work. As far as we know, there could be 320's repackaged in 300 boxes. Just the fact that these v2's showed up in the States at all should something to keep in the back of your mind.
Click to expand...
Click to collapse
This probably isn't really a different model, other than the ones that are supposed to be the gTab are just cost-reduced versions, i.e. half the RAM, no mini-PCIe slot for the SIM/3G support...
...but it would be nice to get the 1GB model simply for the extra RAM, AND if it had the miniPCIe to see if that could be swapped for GPS...
As to the flash problem... wasn't that just because it had a different partitioning of the internal flash? I never did hear what finally happened to that one, but I just thought that bekit had gotten one with a semi-borked partitioning of internal flash...
It's the same in the respect that it has an APX mode and it's hard to brick. But, if you didn't back up your partitions in advance, the scripts we use wouldn't work because they're designed for a device with a different partition structure. You could actually fix it by using a bekit script (if he still has it) or a script supplied by Malata.
Mrbobrowitz is the user, and he told me that the viewing angles are the same.
roebeet said:
It's the same in the respect that it has an APX mode and it's hard to brick. But, if you didn't back up your partitions in advance, the scripts we use wouldn't work because they're designed for a device with a different partition structure. You could actually fix it by using a bekit script (if he still has it) or a script supplied by Malata.
Mrbobrowitz is the user, and he told me that the viewing angles are the same.
Click to expand...
Click to collapse
I figured as much... they changed as little as possible, just removed some things so that they could get to a lower build cost for some customers...
[EDIT]
...and while we're on cost reduction, it's ALWAYS puzzled me that they left that hw reset button on the board, while providing no way to access it short of disassembling the gTab...
[/EDIT]
roebeet said:
It's the same in the respect that it has an APX mode and it's hard to brick. But, if you didn't back up your partitions in advance, the scripts we use wouldn't work because they're designed for a device with a different partition structure. You could actually fix it by using a bekit script (if he still has it) or a script supplied by Malata.
Mrbobrowitz is the user, and he told me that the viewing angles are the same.
Click to expand...
Click to collapse
I asked about something similar earlier, but if you used nvflash to pull the partitions, couldn't,t be used to restore from the same files? Is it just a matter of getpartitiontable, then using info from that to restore? BTW I notice when I did getpartitiontable, the output is binary, so how do you read that?
Jim
jimcpl said:
I asked about something similar earlier, but if you used nvflash to pull the partitions, couldn't,t be used to restore from the same files? Is it just a matter of getpartitiontable, then using info from that to restore? BTW I notice when I did getpartitiontable, the output is binary, so how do you read that?
Jim
Click to expand...
Click to collapse
That's interesting, because I was on IRC when I decided to try the custom fws and bekit had just gotten his oddball gTab at the time, so I dumped my partition table for him and it came out as ASCII text... while for other, like you apparently, it's a binary dump...
cutterjohn said:
That's interesting, because I was on IRC when I decided to try the custom fws and bekit had just gotten his oddball gTab at the time, so I dumped my partition table for him and it came out as ASCII text... while for other, like you apparently, it's a binary dump...
Click to expand...
Click to collapse
Thanks for that! I thought I was imagining it ...
jimcpl said:
Thanks for that! I thought I was imagining it ...
Click to expand...
Click to collapse
Any idea why the getpartitiontable returns binary?
I'm using:
nvflash --bl bootloader.bin --getpartitiontable
Jim
I'm looking into getting ag tab very soon and wondering if this means if I get one of the newer versions, 3.20, well I all be able to root and flash a ROM? Not really sure what nvflash does sorry :/
ellis125 said:
I'm looking into getting ag tab very soon and wondering if this means if I get one of the newer versions, 3.20, well I all be able to root and flash a ROM? Not really sure what nvflash does sorry :/
Click to expand...
Click to collapse
It's unlikely that you'd get a 320. But, if you did, update.zips should still work fine - this is what all the mods are.
nvflash is more of a low-level tool that a few of us, use. That's the one you have to be careful with, if you have a 320. The early bekit scripts are based on the 300, not the 320.
ellis125 said:
I'm looking into getting ag tab very soon and wondering if this means if I get one of the newer versions, 3.20, well I all be able to root and flash a ROM? Not really sure what nvflash does sorry :/
Click to expand...
Click to collapse
This is from a relative Gtab newbie, but nvflash is a low-level command line tool that Nvidia provided as part of their Tetra SDK, which allows you to do things like:
- retrieve and push partitions from/to the sdcard
- push a bootloader to the memory
So, it's a kind of 'bare metal' type tool, I.e., doesn't rely on an OS, and you need to know about partitions, etc. to not mess you system up. On the other hand, in some situations, it can be the only tool that can help.
There are other methods for flashing a Gtab. like stock recovery and CWM, which are more user-friendly and 'safer'
Jim
Alright as long as I can still flash everything and only have to use clockwork I don't mind. Thanks for the info!
ellis125 said:
Alright as long as I can still flash everything and only have to use clockwork I don't mind. Thanks for the info!
Click to expand...
Click to collapse
Actually IF you do get the 1GB version consider yourself VERY lucky. I'd almost kill to get that for the extra RAM alone, and if it has the mini-PCIe slot to boot, well... [EDIT] I mention the mini-PCIe because well, internal GPS would be so NICE to have instead of having to pair an external bluetooth GPS, which I still need to buy... [/EDIT]
If worse comes to worst and those start showing up more commonly, I'm sure that someone who has one will mod the scripts for others with the same variant that want to use nvflash...
cutterjohn said:
Actually IF you do get the 1GB version consider yourself VERY lucky. I'd almost kill to get that for the extra RAM alone, and if it has the mini-PCIe slot to boot, well... [EDIT] I mention the mini-PCIe because well, internal GPS would be so NICE to have instead of having to pair an external bluetooth GPS, which I still need to buy... [/EDIT]
If worse comes to worst and those start showing up more commonly, I'm sure that someone who has one will mod the scripts for others with the same variant that want to use nvflash...
Click to expand...
Click to collapse
If they start showing up more commonly, I might go out and buy another Gtab !
Having said that is there any easy way to tell? Roebeet said that it was labelled on the (outside?) box?
Jim
So I rooted my Samsung Infuse and installed Clockwork recovery using the appropriate method for flashing the - v3 or ve or what it might be called - recovery. So then using Clockwork I backed up my current ROM (Stock). It acted funny later after so I decided to just go back and restore from a previous ROM. It said there were problems mounting a few things. Don't remember what those were. However, here is the real kicker; I may have used update.zip from the previous phone (Which seemed to be a T-Mobile My touch 3G with a 32A something and a 32B something else, similar to the Fender) I had since all I did was switch out the external SD cards since they were both the same size and I had all of my music on the My Touch.
So, if it did flash the Update.zip, is my phone, for the most part, completely bricked? It's symptoms include:
- Static pictures
- Will not boot into recovery
- Will display 'Samsung' but then cuts to static afterwards.
- Shows Battery meter when plugged in and my computer still recognizes and installs the device drivers.
- It will boot into Download mode. Dunno if that actually will help at this point.
If it still turns on you're golden. Just look for the ultimate unbrick thread in the development section and follow the op instructions to go back to stock. The unbrick also is pre rooted and had the right recovery installed, so you're good to flash stuff after
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Cool, so somehow this fixed a phone which had a Fender radio flash. Since that's the case, what should I be worried about in the future that might permanently brick my phone?
Mr.Brosnan said:
Cool, so somehow this fixed a phone which had a Fender radio flash. Since that's the case, what should I be worried about in the future that might permanently brick my phone?
Click to expand...
Click to collapse
Trashing your partitions and bootloaders. Tho I'm not an expert on Samsung devices those seem to be the main causes of true bricks.
Sent from my HTC Thunderbolt
So if I change the partitions to like an ext3 filesystem is that considered trashing it? Yes, I'm fairly new to this entire in depth Android experience. I only took the Android over the iPhone because I am experienced with Linux and only touched a MAC (Referring to the Apple Operating System and not MAC cosmetics) three times.
Well, now I can't download anything in the market due to an 'Unknown error'. I mean, I can receive emails, I think I can call and text. I just can't use my smart phone to do dumb things now. This is a very disturbing complication and I will set off to find the cure for this ailment by posting here again.
Mr.Brosnan said:
Well, now I can't download anything in the market due to an 'Unknown error'. I mean, I can receive emails, I think I can call and text. I just can't use my smart phone to do dumb things now. This is a very disturbing complication and I will set off to find the cure for this ailment by posting here again.
Click to expand...
Click to collapse
you could try a factory reset or
you could just start over
http://forum.xda-developers.com/showthread.php?t=1116251
and or
http://forum.xda-developers.com/showthread.php?t=1092021
JBO1018 said:
Trashing your partitions and bootloaders. Tho I'm not an expert on Samsung devices those seem to be the main causes of true bricks.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
Mainly bootloaders, and ours have enough protection that it's difficult to trash them.
It's next to impossible to hardbrick our phone. Worst case you put it in a state where you need to Odin/Heimdall something to fix it.
Entropy512 said:
Mainly bootloaders, and ours have enough protection that it's difficult to trash them.
It's next to impossible to hardbrick our phone. Worst case you put it in a state where you need to Odin/Heimdall something to fix it.
Click to expand...
Click to collapse
Good stuff to know considering my next phone is a toss up at this point between the Prime and Vigor.
Sent from my HTC Thunderbolt
Hello. Since this is my 1st post as "M4TGS" few words about me: I'm new MT4GS owner and new Android user, coming from WinMo world (been using PocketPCs since WinMo 2003 SE) so if something sounds noobish please forgive me, I haven't had Android phone before (or linux on my PCs).
Please correct me if/where I'm wrong.
My phone is:
LOCKED
S-ON
HBOOT-1.45.0013
with T-Mobile's ROM full of useless junk (I knew that would be the case when I bought it, I had WinMo phones from T-Mo before and they always were loaded with garbage, which I always flashed with modded ROMs, I don't know why I just assumed all Android phones are easy to root and flash shouldve done some reading here first...)
So, after reading a lot of threads here today it seems that:
1 - I cannot change my ROM (due to S-ON and bootloader version that hasn't been cracked yet), is that correct?
2 - I cannot get rid of T-Mobile's junk from my stock rom either, because even if I use the "temp-perma-SuperUser" method, delete the "bloatware" apk, the bootloader will do crc check on next boot and restore them all again, is that correct?
3 - Assuming I understood 1 and 2 correctly, is there a way to stop the "bloatware" from starting at boot? For WinMo 6.x we had few different utilities that basically work on the phone similar to batch scripts on Windows, and a lot of automation could be achieved with those; if there is something like this for Android could it be automated to stop some of the bloatware and remove their shortcuts from menu at every boot?
(i.e. T-Mobile's-specific apps such as "My Account" or "Visual Voicemail", specially the latter bugs me the most because my canadian provider Wind doesn't have Visual voicemail and I can't just tap on "voicemail" without being nagged to enable visual voicemail every time I tap on voicemail in notifications, its so annoying)
4 - How on earth do I make videocalls with this phone and ROM? (yes I searched forum for that and found "Qik" which is not what I'm asking about - I can install i.e. Skype and it'll serve me better than this Qik)
On my last WinMo phone I just tapped the "camera" icon in the phone app and it did videocall using data connection. I can't find anything like it (nor anything pointing to videocall or datacall) on this phone, what am I missing?
Any answers appreciated, TIA!
Well ill just start by saying 1 is wrong so you might want to do some more reading chief, i didnt get through the rest of your post yet just wanted to say your first thought is wrong
Sent from my myTouch_4G_Slide using Tapatalk 2
Thanks. It seems like you're right, as I just found in post from yesterday:
http://forum.xda-developers.com/showthread.php?t=1657414
What about my question 4 (videocalls)?
MT4GS said:
Thanks. It seems like you're right, as I just found in post from yesterday:
http://forum.xda-developers.com/showthread.php?t=1657414
What about my question 4 (videocalls)?
Click to expand...
Click to collapse
Couldnt tell ya man, maybe it does it by gmail addresses? I never use my ffc, i have a iTurd for facetime thats it. My android is my pocket PC lol so mostly all text based things
Sent from my myTouch_4G_Slide using Tapatalk 2
"iTurd" lol certain Steve blowjobs must be screaming in his grave for such sacrilege!
MT4GS said:
"iTurd" lol certain Steve blowjobs must be screaming in his grave for such sacrilege!
Click to expand...
Click to collapse
I couldnt pass a pair of brand new 4th gens for 2 hundred man, only reason they were bought is because i dont live with my 2 year old daughter so we facetime when i dont see her
Sent from my myTouch_4G_Slide using Tapatalk 2
strapped365 said:
I couldnt pass a pair of brand new 4th gens for 2 hundred man, only reason they were bought is because i dont live with my 2 year old daughter so we facetime when i dont see her
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
Man, seems like same case here, my sonny is bit older than your dottie, but he too lives with his mother... that's my only reason for videocall need in this phone
MT4GS said:
Man, seems like same case here, my sonny is bit older than your dottie, but he too lives with his mother... that's my only reason for videocall need in this phone
Click to expand...
Click to collapse
Yeah hmm maybe find a friend that has a phone with a ffc and video call and see if once you add all the info to the address book it gives you the option to video call. I would say google talk has video call but its trash. Then again you might have to use a 3rd party app like qik, thats what comes stock right
Sent from my myTouch_4G_Slide using Tapatalk 2
I know exactly what you mean. I came over to this phone about 2 months ago from a Touch Pro 2. Boy the difference is figuring out how to get around the security on it.
Anyway, just use HTC's unlock tool assuming you are on the newest software version. If you're not, then update to the newest. This will allow you to flash custom ROMs. Flash Clockworkmod recovery. Then just flash superuser through it. This will give you root and the ability to delete the bloatware.
You'll still be S-on, but will be able to flash any custom ROM you want, you just have to push the kernel separately through ADB instead of in a nice neat package.
Yes HappyKhicken it seems much more work to customize it than it was with any Windows Mobile. Not that it would discourage me its just an observation.
I'm still reading around, I have just found out about the "wire trick" to make radio S-OFF, so I want to learn as much as possible before I do anything other than hard reset.
Since you also had TP2 can you explain to me how do you make a videocall here?
I can't figure out how to make videocall at all
If you remember in WinMo (well, depending on ROM and dialer canvas version you had of course) when you tap phone there was the icon that looked like one of those old Logitech round webcams, when you tap this icon it switched to "videocall" to the person you were dialing, and if this person didn't have video capability it switch back to "voice". Can't find anything like this here.
Also probably stupid question: is it possible to restore unlocked/s-off phone back to being locked with s-on and full of junk stock rom? (in case I would need to send it back to htc for warranty repair or replacement, I don't have T-Mobile's option with Asurion insurance since I'm not their customer and I'm in Canada)
thx
HappyKhicken said:
Anyway, just use HTC's unlock tool assuming you are on the newest software version. If you're not, then update to the newest. This will allow you to flash custom ROMs. Flash Clockworkmod recovery. Then just flash superuser through it. This will give you root and the ability to delete the bloatware..
Click to expand...
Click to collapse
OK. I bit the bullet, went to
http://forum.xda-developers.com/showthread.php?t=1532809
run the HTC unlock, and now my bootloader says ***UNLOCKED***
(this was easy-peasy, just somehow no one mentioned in htc unlock tool thread - or I didn't notice it - that an account on htcdev is needed, but I made some quick fake email acct and registered there with it, hopefully I won't need it again? I just realized I didn't save any info for these accts lol)
So, next step would be to flash recovery - either CWM or "Stock 1.55" as there are these 2 to choose from at fifth step on HTC Unlock Tool.
What are the difference between these two?
If I flash one of them now, can I flash the other one later?
I'm not going to flash any new ROM yet, I need to get accustomed to Android first, but I would want to get rid of some bloatware and T-Mobile-specific apps that came with stock ROM since I'm not on T-Mobile. I know I need to flash CWM or Stock Recovery to gain root access, but I don't know which one should I choose / what are the major difference / advantages / disadvantages ?
MT4GS said:
What about my question 4 (videocalls)?
Click to expand...
Click to collapse
Skype works very well on this phone. I've done videochat with a few friends, one of them using another Android, the other friend on an iPhone 4S. We were using Skype since that is a common software for us. Oh, I forgot, I also did Skype video chat using my MT4GS to another friend in Turkey, he was using his laptop. Great thing about Skype is it works on 4G or Wi-Fi (I have unlimited 4G data so I don't worry about it).
Fuzi0719 said:
Skype works very well on this phone. I've done videochat with a few friends, one of them using another Android, the other friend on an iPhone 4S. We were using Skype since that is a common software for us. Oh, I forgot, I also did Skype video chat using my MT4GS to another friend in Turkey, he was using his laptop. Great thing about Skype is it works on 4G or Wi-Fi (I have unlimited 4G data so I don't worry about it).
Click to expand...
Click to collapse
Thanks. Yeah, I installed Skype from Google Play (I think Android Market was better name) and indeed it works great. I think sound quality is way better than Skype for Window Mobile, maybe it is better than 'regular voicecall' too, or so it seems.
But it came to me clear now, and I can't believe it, but despite most of Android 'smartphones' having front cameras, the OS itself doesn't have videocall capability built-in, am I correct?
It's kinda let down if true? because AFAIR even my old TyTN II (thats ancient 2007 model) and every other WinMo smartphone with front camera I had after that also had videocall built-in right there in the dialer
Good god it took me two days to realize I needed to reenable usb debugging after the bootloader unlocked. AJSNFLASKDA
thenpaxtongoes said:
Good god it took me two days to realize I needed to reenable usb debugging after the bootloader unlocked. AJSNFLASKDA
Click to expand...
Click to collapse
OK... care to explain more, specially that you post the same comment in other thread (so I guess it is either important or spam)...
I'm sure I'm not the only noob to this phone and Android OS in general, so:
Why does the usb port need to be in debug mode and how do I start it if it is necessary?
MT4GS said:
OK... care to explain more, specially that you post the same comment in other thread (so I guess it is either important or spam)...
I'm sure I'm not the only noob to this phone and Android OS in general, so:
Why does the usb port need to be in debug mode and how do I start it if it is necessary?
Click to expand...
Click to collapse
To do many adb functions the device must be in debug mode.
The usb port itself isn't in debug mode, rather the whole device is.
In a very technical sense, a ROM is not 'polished' or 'finished' if it releases with usb debugging enabled - but I released mine that way because I use it so very often.
The setting is in:
Settings - Applications - Development
Sent from a digital distance.
Thank you Blue6IX for excellent explanation and thenpaxtongoes for the reminder
Now to root my unlocked phone:
volume down + power, to go into hboot, plug in usb, fire up HTC Unlocker Tool and install CWM or Stock recovery, but do I need to change on my phone's hboot menu screen down to Recovery first or do I keep it at default Fastboot to install one of the Recoveries?
Another question is which recovery to install? It seems CWM is the one to go with but what are the advantages/disadvantages of CWM vs Stock 1.55 recovery? TIA
RESURRECTING an old thread
I have just rooted my MT4GS and I want to get rid of some of the stock T-Mo apps.
There was a thread here I read half a year ago with a list of apps that can be safely deleted, but I just spend good 30min trying to find it... I guess it was a post in some unrelated thread or such.
I want all the T-Mobile-specific apps gone (and yes I did backup on SD card with clockwork recovery). :cyclops: Can someone point me in right direction?
MT4GS said:
RESURRECTING an old thread
I have just rooted my MT4GS and I want to get rid of some of the stock T-Mo apps.
There was a thread here I read half a year ago with a list of apps that can be safely deleted, but I just spend good 30min trying to find it... I guess it was a post in some unrelated thread or such.
I want all the T-Mobile-specific apps gone (and yes I did backup on SD card with clockwork recovery). :cyclops: Can someone point me in right direction?
Click to expand...
Click to collapse
What I find the easiest to do is just use something like My Backup Pro or Titanium Backup to "freeze" the things I don't want, usually those things from T-Mobile or HTC that startup in the background but I never use. Like the Group Messaging stuff (there are 3 processes associated with that, I freeze all 3), the SWM-C process, T-Mobile ID (a caller-ID type thing you have to pay for). Yes, they still take up storage space but that is negligible, by freezing them they no longer are taking up processing/battery time.
MT4GS said:
RESURRECTING an old thread
I have just rooted my MT4GS and I want to get rid of some of the stock T-Mo apps.
There was a thread here I read half a year ago with a list of apps that can be safely deleted, but I just spend good 30min trying to find it... I guess it was a post in some unrelated thread or such.
I want all the T-Mobile-specific apps gone (and yes I did backup on SD card with clockwork recovery). :cyclops: Can someone point me in right direction?
Click to expand...
Click to collapse
Here is the original thread that was started a long time ago. I have still found it useful on occassion. http://forum.xda-developers.com/showthread.php?t=1222672&highlight=bloat