Hi to all. yesterday i was tried to flash the new radio 2.22.23.02 on my old 26I.
I have 32B HTC G1.
with default hboot version: 1.42.0000
when i tried to flash new radio, it was all fine, but after trying to reboot into recovery again (after flashing) i got some error about There is not enough free space tra-la-la. And after reboot there is no changes and there is no some effect. After this i have a problem while restoring old rom's back up (ezterry's 2.2.1 ota)... Than i installed CM6 RC3. All fine, but a quality of my calls is like a fck ****!
Sometimes i speak with my friends like usual, but sometimes my friends and me hear crazy noise!
I know that its because my failed trying to flash another radio...
Hboot says to me that my version of radio is my oldest one - 26I.
What i can do now?
I can't flash any radio (26I and 23.02) always have the same trouble with the space (i think?)
Before the flashing i tried to 'fastboot erase system -w'
and after - wipe all... there is no effect.
How to fix? Thx for attention.
recovery.log in attach!
and via fastboot i have a:
Code:
Arthur-Malachevski:ota-radio-2_22_19_26I antihazard$ fastboot-mac flash radio radio.img
sending 'radio' (21504 KB)... OKAY
writing 'radio'... INFOsignature checking...
FAILED (remote: signature verify fail)
Arthur-Malachevski:ota-radio-2_22_19_26I antihazard$
maybe somebody have any suggestion?
SO ... here is more info:
Code:
Arthur-Malachevski:~ antihazard$ adb shell cat /proc/meminfo
MemTotal: 98700 kB
MemFree: 3332 kB
Buffers: 8 kB
Cached: 15248 kB
SwapCached: 5884 kB
Active: 40492 kB
Inactive: 33888 kB
Active(anon): 29008 kB
Inactive(anon): 30624 kB
Active(file): 11484 kB
Inactive(file): 3264 kB
Unevictable: 292 kB
Mlocked: 0 kB
SwapTotal: 17760 kB
SwapFree: 1556 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 54772 kB
Mapped: 14108 kB
Shmem: 204 kB
Slab: 5524 kB
SReclaimable: 1184 kB
SUnreclaim: 4340 kB
KernelStack: 2016 kB
PageTables: 4540 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 67108 kB
Committed_AS: 1177444 kB
VmallocTotal: 802816 kB
VmallocUsed: 54976 kB
VmallocChunk: 721924 kB
and mtd partitions:
Code:
Arthur-Malachevski:~ antihazard$ adb shell cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00020000 "misc"
mtd1: 00500000 00020000 "recovery"
mtd2: 00280000 00020000 "boot"
mtd3: 09100000 00020000 "system"
mtd4: 00800000 00020000 "cache"
mtd5: 038c0000 00020000 "userdata"
help...guys...
yesterday i was tried to erase radio via fastboot... no result...
ANtiHazarD said:
when i tried to flash new radio, it was all fine, but after trying to reboot into recovery again (after flashing) i got some error about There is not enough free space tra-la-la. And after reboot there is no changes and there is no some effect. After this i have a problem while restoring old rom's back up (ezterry's 2.2.1 ota)... Than i installed CM6 RC3. All fine, but a quality of my calls is like a fck ****!
Click to expand...
Click to collapse
I hope you have Test2 (test1 on the dream I didn't test calls but I'd not be socked to hear it sounded like **** (forgot the dream Audio settings.. I've heard the phone operate like that before it quite crappy)
However I believe you needed to use CustomMTD to install in that way; so what you really need to do is:
* nandroid backup;
* Uninstall custom MTD (use flash_image from recovery to re-flash your current recovery without the customMTD command line changes);
* then flash the an eng SPL (SPL 1.33.2003 will work fine as long as you have a 2.22 radio);
* then you can use fastboot to flash the new radio and
* 'fastboot erase system -w' to clean anything else up;
* last restore CustomMTD if needed and restore nandroid and boot normal.
yes, i used test2
okey, thx to you very much! I will try this way...
i hope thats my strange hboot 1.42.0000 will be reflashed by 1.33.2003 very fine.
Anyway i will have a possibility to change the 1.33.2003 spl without any fail and brick while a bad flashing (in case when i will try to flash 2003 spl and it will be, for example, with error) ?
i asked this questions because it's very strange for me - my version of phone. It's from South Africa (), yeap... I use customMTD, i flashed all ROM's, gained the root (The method with RC29, RC7 - NOT working with my phone) and all fine... but this phone have very strange default spl. Thats why i have a some fear about it
ezterry, thx you god.
Related
Hello world,
I have a new HTC Magic, here in India. The specs on the rear side of the packaging box reads as 'RAM : 288 MB'. But today when using adb shell, I was surprised to see 'MemTotal: 197144 kB' reported in cat /proc/meminfo. I'm utterly confused! Can anyone please explain what's wrong and where ?
$cat /proc/meminfo
MemTotal: 197144 kB
MemFree: 81836 kB
Buffers: 372 kB
Cached: 66180 kB
SwapCached: 0 kB
Active: 59600 kB
Inactive: 44528 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 37600 kB
Mapped: 24908 kB
Slab: 5000 kB
SReclaimable: 1180 kB
SUnreclaim: 3820 kB
PageTables: 3228 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 98572 kB
Committed_AS: 877976 kB
VmallocTotal: 319488 kB
VmallocUsed: 62800 kB
VmallocChunk: 229372 kB
I check this with my ubuntu.
Yeah, TotalMem is total size of your device
Yes you have a 288 MB
The rest of the memory, around 94-95MB for most ROMs goes to your radio, framebuffer and other hardware and is not accessible from the OS directly...
antonram said:
Yes you have a 288 MB
The rest of the memory, around 94-95MB for most ROMs goes to your radio, framebuffer and other hardware and is not accessible from the OS directly...
Click to expand...
Click to collapse
Ah, that explains it. Thank you very much!
Hello
I have problem with fastboot flash userdata because the flashed content is wrong.
Is it a fastboot/hboot issue?
when i flashed 97910784bytes long userdata.img and check the first 97910784bytes of userdata partitions, the contents are differ. anyone knows why?
fastboot erase userdata
erasing 'userdata'... OKAY
fastboot flash userdata userdata.img
sending 'userdata' (95616 KB)... OKAY
writing 'userdata'... OKAY
md5sum userdata.img
d83a6f62c48628f76796bc6129e48c5c *userdata.img
--- now i'm booting into cwm recovery 3.2.0.0 ---
/sdcard # cat /proc/mtd
dev: size erasesize name
mtd0: 000a0000 00020000 "misc"
mtd1: 00420000 00020000 "recovery"
mtd2: 002c0000 00020000 "boot"
mtd3: 0fa00000 00020000 "system"
mtd4: 02800000 00020000 "cache"
mtd5: 0af20000 00020000 "userdata"
/sdcard # dd if=/dev/mtd/mtd5 of=mtd5.bin bs=131072 count=747
747+0 records in
747+0 records out
97910784 bytes (93.4MB) copied, 25.451782 seconds, 3.7MB/s
/sdcard # md5sum mtd5.bin
03d6daafa42cd9b315d4c440a3ce483f mtd5.bin
--- md5sums differ so the image is corrupted. now i'll testing flash_write tool ---
/sdcard # md5sum userdata.img
d83a6f62c48628f76796bc6129e48c5c userdata.img
/sdcard # flash_image userdata userdata.img
flashing userdata from userdata.img
mtd: successfully wrote block at c1a5800000000
mtd: successfully wrote block at c1a5800020000
mtd: successfully wrote block at c1a5800040000
.
.
.
mtd: successfully wrote block at c1a5805d20000
mtd: successfully wrote block at c1a5805d40000
mtd: successfully wrote block at c1a5800000000
/sdcard # dd if=/dev/mtd/mtd5 of=mtd5.bin bs=131072 count=747
747+0 records in
747+0 records out
97910784 bytes (93.4MB) copied, 22.993714 seconds, 4.1MB/s
/sdcard # md5sum mtd5.bin
d83a6f62c48628f76796bc6129e48c5c mtd5.bin
--- flash_write works well, use this. ---
In case this info is of use to someone...
Trying to understand what goes where,
Here is the partition table of a U8800:
#######################################
Disk /dev/sdb: 3959 MB, 3959422976 bytes
1 heads, 62 sectors/track, 124729 cylinders, total 7733248 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 1 491520 245760 b W95 FAT32
/dev/sdb2 * 491521 492520 500 4d QNX4.x
/dev/sdb3 492521 498520 3000 46 Unknown
/dev/sdb4 498521 7733247 3617363+ 5 Extended
/dev/sdb5 524288 548863 12288 59 Unknown
/dev/sdb6 655360 921599 133120 4c Unknown
/dev/sdb7 1048576 1049575 500 5a Unknown
/dev/sdb8 1179648 1185791 3072 58 Unknown
/dev/sdb9 1310720 1324719 7000 50 OnTrack DM
/dev/sdb10 1441792 1447935 3072 4a Unknown
/dev/sdb11 1572864 1579007 3072 4b Unknown
/dev/sdb12 1703936 2154495 225280 83 Linux
/dev/sdb13 2228224 3457023 614400 83 Linux
/dev/sdb14 3538944 7733247 2097152 69 Unknown
#############################################
sdb1: This is the FAT32 partition that gets mounted when we boot into pink screen;
It holds, among other files, EMMCBOOT.MBN, which, if not present and as far as I've experimented, will get the phone straight into a blue screen and initiate a flash procedure if a 'dload' folder with a ROM is found in the sdcard. The contens of this partition are changed when a ROM is flashed.
sdb2: Is flagged as bootable, and holds an (so far) unknown filesystem (if any; could hold a raw binary image, for instance);
sdb3: Holds an unknown filesystem, if any. This partition is changed whenever you flash a ROM. dumping this partition back, from any 2.3BETA, to a 2.3 (B522) running phone, will get the USB pink screen mode working again, allowing acces to sdb1.
sdb5: holds an unknown filesystem if any; dumping this one back gets us the original "IDEOS" logo and, probably, whatever is needed to make previous CWM backups work again.
sdb6: ext3 filesystem with a directory called "recovery".
sdb7: Unknown filessytem, if any.
sdb8: Unknown filesystem, if any.
sdb9: Unknown filesystem, if any.
sdb10: Unknown filesystem, if any.
sdb11: Unknown filesystem, if any.
sdb12: ext3 filesystem; gets mounted at "/system".
sdb13: ext3 filesystem; gets mounted at "/data".
sdb14: vfat filesystem; represents the internal sdcard.
I'm trying to find out what needs to be restored in order to perform a clean, reliable downgrade. sdb5 is a must, but not the only one. I've flashed 2.2 and dumped it back right after. The result is an almost downgraded U8800. I say almost because charging the battery while the phone is off shows a different image (the one that comes with 2.3) and I can't power up the phone unless I take the cable out; this means there are still remnants of 2.3 somewhere...
UPDATE: Not being able to power up the phone was to due to the CWM recovery; restoring original recovery.img solved that one.
After I flashed CLK (did not use the Task 39 first) after using bootloader HSPL 2.08,
every time the phone boots it stucks at below;
codesmith's LK (CLK) v1.4.0.1
[200] ptn 0 name ='misc' start=0000219 len = 00000008 end=000000221
[210] ptn 1 name = 'recovery' start = 000000221 len = 0000000028 end= 0000000249
[210] ptn 2 name = 'boot' start= 000000249 len= 0000000028 end=0000000271
[210] ptn 3 name = 'system ' start= 00000271 len=000004b0 end=000000721
[210] ptn 4 name = 'cache' start= 000000721 len=000000028 end=000000749
[210] ptn 5 name = 'user data' start=000000749 len=00000007f8 end=000000f41
[210] USB init ept @ 02x28023000
[250] fastboot_init()
[250] udc_start()
[250] -- suspend --
[380] -- reset --
[380] -- portchange --
[420] -- reset --
[420] -- portchange --
[520] STALL GET_DESCRIPTOR 128 6 1006 0 18
I still can go to bootloader 2.08 (screens with three color) but I try to re install back magldr after messed up the CLK but now it stucks at 0% progress. Tried to reinstall CLK but still the same result. Is there a way to solve this problem like uninstall that CLK and revert back to MAGLDR?] I am using windows 7 64 bit btw
I tried hard reset to factory setting and even after I did that it still boots the same error above. Pls help.
First of all I'd try to revert to stock WinMo Rom...
If everything's OK, retry procedure to install Android.
yuugi99 said:
After I flashed CLK (did not use the Task 39 first) after using bootloader HSPL 2.08,
every time the phone boots it stucks at below;
codesmith's LK (CLK) v1.4.0.1
[200] ptn 0 name ='misc' start=0000219 len = 00000008 end=000000221
[210] ptn 1 name = 'recovery' start = 000000221 len = 0000000028 end= 0000000249
[210] ptn 2 name = 'boot' start= 000000249 len= 0000000028 end=0000000271
[210] ptn 3 name = 'system ' start= 00000271 len=000004b0 end=000000721
[210] ptn 4 name = 'cache' start= 000000721 len=000000028 end=000000749
[210] ptn 5 name = 'user data' start=000000749 len=00000007f8 end=000000f41
[210] USB init ept @ 02x28023000
[250] fastboot_init()
[250] udc_start()
[250] -- suspend --
[380] -- reset --
[380] -- portchange --
[420] -- reset --
[420] -- portchange --
[520] STALL GET_DESCRIPTOR 128 6 1006 0 18
I still can go to bootloader 2.08 (screens with three color) but I try to re install back magldr after messed up the CLK but now it stucks at 0% progress. Tried to reinstall CLK but still the same result. Is there a way to solve this problem like uninstall that CLK and revert back to MAGLDR?] I am using windows 7 64 bit btw
I tried hard reset to factory setting and even after I did that it still boots the same error above. Pls help.
Click to expand...
Click to collapse
What you have posted looks perfectly normal. If I remember right this is what clk spits out when you boot into clk by holding the home button down or if you do not have a ROM for clk to boot. In your case you do not have a ROM for clk to boot. You must have flashed a older version of clk as the latest version does not do this, it has a actual Hoot screen that appears. Click on the HD2 guide linked in my Sig and go to post 3 and you can either follow the steps to flash Clockwork Mod Recovery via the fastboot commands or you can just click on the link to the newest clk with the Hboot screen and Clockwork Mod Recovery built into it.
Here is the long version.
My phone a U8800 Pro was running the official B928 version downloaded from Huawei
I wanted to install the latest version Cyanogen 11. That needed me to install the latest version of TWRP which led me to the mistake that I needed to update the bootloader as well.
And then I did another mistake where I installed what is obviously the wrong bootloader from here (http://forum.xda-developers.com/showthread.php?t=1800045) using
Code:
dd if=/tmp/bootloader.bin of=/dev/block/mmcblk0p3
The phone since then just boot cycles continously and cannot even login to recovery mode.
I attempted to re-install B928 from the SD card but always fails at about 1/4 of the way through with a
Code:
dload_sd_ram_data_proc->(retry >= DLOAD_RETRY) failed!
msg.
Now interestingly if I remove the battery and just use the USB I get an empty pink screen and I can see at least the partitions of the internal drive
Code:
Disk /dev/sdg: 3.7 GiB, 3959422976 bytes, 7733248 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdg1 1 524287 262143+ c W95 FAT32 (LBA)
/dev/sdg2 * 524288 525287 500 4d QNX4.x
/dev/sdg3 525288 531287 3000 46 Unknown
/dev/sdg4 531288 7733247 3600980 5 Extended
/dev/sdg5 655360 679935 12288 59 Unknown
/dev/sdg6 786432 1052671 133120 4c Unknown
/dev/sdg7 1179648 1183743 2048 5a Unknown
/dev/sdg8 1310720 1316863 3072 58 Unknown
/dev/sdg9 1441792 1455791 7000 50 OnTrack DM
/dev/sdg10 1572864 1579007 3072 4a Unknown
/dev/sdg11 1703936 1710079 3072 4b Unknown
/dev/sdg12 1835008 2621439 393216 83 Linux
/dev/sdg13 2621440 4456447 917504 83 Linux
/dev/sdg14 4456448 7733247 1638400 69 Unknown
and can mount some of them.
Now where can I find an appropriate bootloader and which partition should I attempt to copy it on .
And secondly if that works out, how do I install TWRP 2.8.0.0 . Using TWRP manager fails which led to this whole mess really.
On /dev/sdg1 I can see a dir called image and it contains
Code:
amss.mbn boot.img cust.img EMMCBOOT.MBN recovery.img
but don't want to touch anything before I know more since I can do more dmg.
Thanks for all the help in advance
Edit: I managed to copy the bootloader from a friend and copy it back on my phone so that problem was solved. It needed to go to the /dev/sdg3 partition if anyone is wandering. Now pink screen seems locked and can't access the internal storage through USB so back to square 1.
Glad you got the problem solved out. When you unlock your bootloader (like I said in here), boot your phone to pink screen and plug it to your computer. You're using linux? If so, there probably is going to be four difference device's to be shown, the one which you're interested is the device containing "image" folder, in there replace the recovery.img with appropriate one.