Guest 90180360 Posted December 22, 2010 Report Posted December 22, 2010 So when I'm going to a T-Mobile shop, how do I know if I'm getting one with 256 MB or 512 MB?
Guest Sebastian404 Posted December 22, 2010 Report Posted December 22, 2010 So when I'm going to a T-Mobile shop, how do I know if I'm getting one with 256 MB or 512 MB? hmm, since they both have the same display build ID (TM_P729TV1.0.0B02) you cant tell from looking at the about device page... I assume they might be a different product code on the box, like there is with the Orange ones...... http://android.modaco.com/content/zte-blad...box-vs-lcd-box/
Guest Sebastian404 Posted December 22, 2010 Report Posted December 22, 2010 Not sure if this is a good idea considering the (semi) DOS attack Im having, but I uploaded a recovery zip here: http://android.podtwo.com/roms/stock/TM_P7...date_signed.zip I've used the INTERNAL version numbers to differentiate, the B05 version in the same directory is the older version, tho they both claim to be B02 from the DISPLAY version number..... nothing to make life simple..
Guest fonix232 Posted December 22, 2010 Report Posted December 22, 2010 hmm, since they both have the same display build ID (TM_P729TV1.0.0B02) you cant tell from looking at the about device page... I assume they might be a different product code on the box, like there is with the Orange ones...... http://android.modaco.com/content/zte-blad...box-vs-lcd-box/ Easier: Go to the Taskmanager app, Resources page, and at the bottom, it tells you the total RAM amount. If it is around 160MB, it is a 256MB version. If it is around 414MB, then you got the 512MB version. WARNING! Do not check the FREE RAM, but TOTAL RAM!
Guest Sebastian404 Posted December 22, 2010 Report Posted December 22, 2010 Easier: Go to the Taskmanager app, Resources page, and at the bottom, it tells you the total RAM amount. If it is around 160MB, it is a 256MB version. If it is around 414MB, then you got the 512MB version. WARNING! Do not check the FREE RAM, but TOTAL RAM! There is that, but you have to open the box and turn it on to find that out :)
Guest fonix232 Posted December 22, 2010 Report Posted December 22, 2010 There is that, but you have to open the box and turn it on to find that out :) Well yes, but most carriers lets you to test the device before accepting it!
Guest Sebastian404 Posted December 22, 2010 Report Posted December 22, 2010 Just as a note... I forgot to check last night in my rush to build a recovery zip, but the recovery partition on that dump is clockwork mod.... It would be GREAT if someone could dump the recovery partition of an unmolested device....
Guest fonix232 Posted December 22, 2010 Report Posted December 22, 2010 Just as a note... I forgot to check last night in my rush to build a recovery zip, but the recovery partition on that dump is clockwork mod.... It would be GREAT if someone could dump the recovery partition of an unmolested device.... Tomorrow I am going to swap my device, and if you can point me to a proper dump binary (tried koush's version, and some other, none worked), I would be glad to root, dump, and upload it for you. BTW, isn't boot.img enough for creating CWM? Also I guess the recovery is almost the same (but with the proper 512MB memory mapping).
Guest Sebastian404 Posted December 22, 2010 Report Posted December 22, 2010 Tomorrow I am going to swap my device, and if you can point me to a proper dump binary (tried koush's version, and some other, none worked), I would be glad to root, dump, and upload it for you. BTW, isn't boot.img enough for creating CWM? Also I guess the recovery is almost the same (but with the proper 512MB memory mapping). http://android.podtwo.com/romdump/ no need to root it, it comes with its own root escalation exploit, the less you do to the phone before you run it the better infact. Its not so much about creating CWM, more about having the 'correct' version of the recovery.img
Guest markusj Posted December 22, 2010 Report Posted December 22, 2010 (edited) I've got my new blade, w/ 512 Mb RAM. In the first store (Mammut) they didn't swap it for me, no threatening with consumer protection worked. I've got a tip, in the Europark T-pont they swap my device. The service man told me he can only swap it if it has a problem. I mentioned the greyscale and the pixel errors and the screen vibrating thing, and he swapped it! Also, my new blade has no grescale problem. I was kinda hoping that it's an OLED one, but not ;) It appears that I don't need to dump my ROM, so I'll flash cwm+FF ASAP :) ad: What the heck, Baseband version TM_P729TV1.0.0B01 Kernel version Bulid (sic!) TM_P729TV1.0.0B02 That's neither the old, nor the new one. Edited December 22, 2010 by markusj
Guest Sebastian404 Posted December 22, 2010 Report Posted December 22, 2010 It appears that I don't need to dump my ROM, so I'll flash cwm+FF ASAP :) WAIT!!!! We do need a recovery partition, if you could dump it and just upload the recovery.img file somewhere.....
Guest markusj Posted December 22, 2010 Report Posted December 22, 2010 WAIT!!!! We do need a recovery partition, if you could dump it and just upload the recovery.img file somewhere..... Hahaha, I knew that I shouldn't do anything so fast :) Check my update for my previous post, might be interesting.
Guest Sebastian404 Posted December 22, 2010 Report Posted December 22, 2010 Hahaha, I knew that I shouldn't do anything so fast :) Check my update for my previous post, might be interesting. if you read back, its the INTERNAL build id you should look at, its changed somewhat...
Guest Benoe Posted December 22, 2010 Report Posted December 22, 2010 (edited) http://android.podtwo.com/romdump/ no need to root it, it comes with its own root escalation exploit, the less you do to the phone before you run it the better infact. Its not so much about creating CWM, more about having the 'correct' version of the recovery.img Hi! Here you can find a recovery.img from a virgin 512M Hungarian ZTE Blade: recovery.img pass: zteblade md5 of the .img: 7e2def83758390309d81639c38790385 Edited December 22, 2010 by Benoe
Guest markusj Posted December 22, 2010 Report Posted December 22, 2010 It looks like I've got nothing to do then. I've got some problems with adb, so it's OK :)
Guest dmxpowa Posted December 22, 2010 Report Posted December 22, 2010 /* HUN */ az alabbi post egy igaz tortenetet dolgoz fel: szoval en is megkaptam az elso szerias kiraly 256MB ramos keszuleket amirol mar az elso percben tudtam nyilvan, hogy "szar" viszont ma volt idom bemenni csereltetni (plusz lattam forumon, hogy jott uj persze) elso ut a westendbe ahol megmondtam mi a problemam, 512 -nek van hirdetve viszont ez cska 256, erre jott a szervizes, hogy ismert problema a telefonnal es, hogy kicsereli, mert ezt nem lehet javitani. sajnos itt nem jartam sikerrel, mert mar nem volt nekik raktaron viszont megnezte, hogy a 11kerbe az eromunel van valami T-pont es ott van meg 4db, atmentem oda es nagyon keszsegesen 1 szo nelkul kicsereltek. gondolkodtam rajta, hogy osszehazudom a holnapot is, hogy ez meg az szar (egyebkent a ramon kivul a keszuleknek semmi baja nincs) de vegul igy is kijottem jol, hogy elmondtam ami valojaban a problemam. ugyhogy hajra meg maradt 4db ugyhogy lehet csereltetni :>
Guest fonix232 Posted December 22, 2010 Report Posted December 22, 2010 http://android.podtwo.com/romdump/ no need to root it, it comes with its own root escalation exploit, the less you do to the phone before you run it the better infact. Its not so much about creating CWM, more about having the 'correct' version of the recovery.img That binary drops me out with an access denied message, even in su mode. I can do nothing with it :S
Guest martea Posted December 22, 2010 Report Posted December 22, 2010 (edited) And what are you telling them, why you want to swap? I don't think they will just simply swap it because there's a new model I'm afraid. BUT, restoring stock rom, accessing system drive and changing hw_ui value in build.prop to 1 would do the job (actually, it will cause screen problems after restart, so you got a stock rom, while you have a buggy phone). How you do this? I pulled build.prop from the stock rom, opened in editor, but can't find hw_ui update: Found it, it really works Edited December 22, 2010 by martea
Guest vigyuzte Posted December 22, 2010 Report Posted December 22, 2010 How you do this? I pulled build.prop from the stock rom, opened in editor, but can't find hw_ui update: Found it, it really works I hope that the man at the service won't do a factory reset to solve the problem! (Does it solve it?)
Guest fonix232 Posted December 22, 2010 Report Posted December 22, 2010 I hope that the man at the service won't do a factory reset to solve the problem! (Does it solve it?) It won't, as it is on the /system partition -> data wipe can't remove it. Only way to do so is to flash a new/the same ROM: but apparently, T-Mobile HU has no proper device(s) to apply a new update. At least, when the guy at the T-Point asked me what do I know about updates implied this to me.
Guest Sebastian404 Posted December 22, 2010 Report Posted December 22, 2010 Hi! Here you can find a recovery.img from a virgin 512M Hungarian ZTE Blade: recovery.img pass: zteblade md5 of the .img: 7e2def83758390309d81639c38790385 Thanks Benoe :)
Guest markusj Posted December 22, 2010 Report Posted December 22, 2010 (edited) Triple damn and an extra damn, I dumped my ROM, I started uploading it, it took 1h to get it to 90%, and I closed the tab... Well, Benoe has already posted a recovery.img, so I won't upload it again :) Edited December 22, 2010 by markusj
Guest Sebastian404 Posted December 22, 2010 Report Posted December 22, 2010 (edited) That binary drops me out with an access denied message, even in su mode. I can do nothing with it :S when did you download the file, there was a bug in the 'old' version that stopped it working from the terminal, it should of been fixed in the current version tho... if you have got SU working, try the following chmod 04755 /system/bin/romdump and then try it. Edited December 22, 2010 by Sebastian404
Guest fonix232 Posted December 22, 2010 Report Posted December 22, 2010 when did you download the file, there was a bug in the 'old' version that stopped it working from the terminal, it should of been fixed in the current version tho... if you have got SU working, try the following chmod 04755 /system/bin/romdump and then try it. Okay then, tomorrow I'm going to swap it, based on this: (sorry, hungarian): [language=Hungarian] Ma megtudtam, hogy a ZTE gyártó Magyarországra 512 MB-os Bladeket szánt. Tehát, akinek 256 MB-os Blade-je van, az GYÁRI HIBÁS és egyből cserélik! Ezt nekem a szervizes srác mondta, aki felhívta a gyártót, mert valaki épp reklamált neki, hogy cseréljék ki. Tehát mindenki, akinek 256 MB-os Blade-je van, cserélje ki nyugodtan ezzel az indokkal! [/language] Rough translate: Today I was informed that ZTE dedicated to Hungary the 512MB RAM model Blade. So, who got a 256MB version, it is FACTORY DEFECT, and it should be swapped inmediately! I was told by a service guy who called ZTE Hungary, because someone was complaining about it, and to swap it. So, anybody, who got such version, can swap it! And also, some reviews and experiences with the new model: - More RAM (512MB instead of 256) - At some places, many screen defects (9 of 10 had pixel problems, and vibrating screen, but other places had 10/10 faultless devices) - The screen is a bit different, has warmer colors I will write my own experiences tomorrow!
Guest vigyuzte Posted December 23, 2010 Report Posted December 23, 2010 Kíváncsi vagyok hogy neked sikerült-e, egy srácnak ezzel dobták vissza (Miskolcon): http://i.imgur.com/aIwRJ.jpg http://prohardver.hu/tema/zte_blade/hsz_11323-11323.html
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now