Related
Hi There
Diam140 - Olinex:1.93
Used to change ROMs almost everyday - flashoholic. And one bad day a flash failed and after that
Diamond is behaving strangely. Tried 'MTTY'- {task 29} and {task 28} as well. And here is the output
from both:
task 29
Format BINFS start
Fill RSVD information for block 288 to 321
CE start sector=0x14, total sector of CE and TFAT=0x14
CE start start block=321, total block=1727
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS end
task 28
Format start
Fill RSVD information for block 288 to 321
CorrectNandAddr detect error addr =0x3800F164
CorrectNandAddr detect error addr =0x3800F164
CorrectNandAddr detect error addr =0x38000000
CorrectNandAddr detect error addr =0x38000000
CorrectNandAddr detect error addr =0x38000000
bad=0x1D20
R:NO bad block reversed for block ID 0x1D20
CorrectNandAddr detect error addr =0x38000000
ERASE FAIL: 0x1D20
W:NO bad block reversed for block ID 0x1D20
Write NAND Faild
Now if the power button is pushed, after 10 minutes device vibrates and comes up with a greyish screen
and after half an hour or so it can be put bootloader. And some times the battery charges with ring
light animation. But flashing any ROM stops at '0%' without any progress and also Hard Reset not
happening - same no progress bar. Checked 'mtty - info 8' and this is what it gave:
info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_k9k2g08
DEVICE ID=0xAA
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x800
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 3 (0x3) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 12 (0xC) is reversed block
BLOCK 13 (0xD) is reversed block
BLOCK 14 (0xE) is reversed block
BLOCK 28 (0x1C) is reversed block
BLOCK 29 (0x1D) is reversed block
BLOCK 30 (0x1E) is reversed block
BLOCK 31 (0x1F) is reversed block
OS NOT FOUND !!!
So wanted to change the NAND as above 'samsung_k9k2g08', however Diamond does not use any such chip and
it uses a different combo Nand ROM Memory by the name 'Samsung NAND - KMXEE0A0CM-S600' which is not
possible to change since it is a BGA, atleast with what tools one normally have at home.
Now can someone help reviving the almost bricked Diamond (well some PMs did not do the trick). Any help
is highly appreciated and Thanks in advance
Hi there,
Still stuck with the Device in the same condition. However now this is the output of 'TASK 29 or 28' of late....(given is the end part since it scrolls from the first address)
Flash NAND DM internal transfer failed: dmov_transfer()bad=0x7FB
DMOV transfer: out of memory
Flash NAND DM internal transfer failed: dmov_transfer()bad=0x7FC
DMOV transfer: out of memory
Flash NAND DM internal transfer failed: dmov_transfer()bad=0x7FD
DMOV transfer: out of memory
Flash NAND DM internal transfer failed: dmov_transfer()bad=0x7FE
DMOV transfer: out of memory
Flash NAND DM internal transfer failed: dmov_transfer()bad=0x7FF
R:NO bad block reversed for block ID 0x7FF
Read sector fail!!!
And also attached the screens for grey screen and HardReset without the progress bar .. can someone help ?
Well, I guess your NAND is broken. Did you try to flash in bootloader mode ?
WBR
viperbjk said:
Well, I guess your NAND is broken. Did you try to flash in bootloader mode ?
Click to expand...
Click to collapse
Hi,
Thanks for the response
Yes, tried flashing from bootloader, with no success. Progress bar stops at 0%. And now 'mtty - info 8 and 9' also gives same scrolling output with read error. Any way out ?
viperbjk said:
Well, I guess your NAND is broken. Did you try to flash in bootloader mode ?
Click to expand...
Click to collapse
Was toying with QMAT and bootloader and since the NAND was broken tried 'Write partition to NAND' with 7200A hotfix and after that though the 'task 28 and 29' of mtty were giving the same out of memory errors, the bootloader screen is showing 'DIAM100' instead of 'DIAM140'. Does it give any hope of reviving NAND with some commands either in QMAT or mtty. Well not being a technical person, expecting some engineering inputs/tips.
Thanks in advance.
.... Was just revisiting this thread to see any progress on the query or any solution posted by other members stuck in similar situation, well No Luck... still holding the dead diamond. But then have moved on to a fully customised iPhone 3G 16GB (JB and Unlocked) and may never ever come back to a WinMo and specially an HTC device. Thanks to all those helped directly or indirectly, it was pleasant visiting these pages at 'xda-developers'. Will be visiting these pages to update on the developments in future as well.....
I read your problems. was not to fix this by using J-Tag? me also interested in that topic, I read somewhere that it would be just mentioned J-Tag fix these problems. Sorry but my English is poor.
Hi isaac12,
Glad you are interested in these things, well did not get any tips from the experts of J-Tag. And tried on my own and reported all the results here. Still want to revive the dead diamond, in fact went to the extent of replacing NAND chip but realised it will be a very costly affair and getting the equipment/expertise was also out of question. So it remains dead......
I am in the same situation. I also use flashaolic.
Have a beer, its time to get a new experimental subject.
Hi Guys,
some times ago i used mtty to clean the device to flash a new rom. After this i can't flash any file. No solution in the posts can help.
The device can start into bootloader (rgb-screen) with following message:
---------------------------------
DIAM100 64MB
SPL-1.93.OliNex
MicroP-Diam (LED) v11
PSOC-Diam STAGE_PVT v0x30
---------------------------------
all looks normal but when trying to flash a file it shows the gray flash-screen and stops at 0%. After a while it terminates with a communication error (error 262). Has someone an idea what i can do ? any tries with original shipped rom for example fails with the same problem. If some german guy can help my please contact me in icq (70582431) or msn ([email protected]) please !
Thanks guys !
try to reflash hardspl..
nothing is flashable ! i tried first to flash hard-spl again but nothing works... :-(
do you had h-spl before using mtty?if yes tell me what tasks did you used..
if no i think you have bricked your phone
hard-spl was on the device. the time before i flashed my own roms without problems till now.
i used the commands in the mtty-thread:
---------------------
MTTY OUTPUT:
---------------------
CMD>
---------------------
6b: type "set 14 0" without the quotes to tell bootloader to boot the OS after reset:
---------------------
MTTY OUTPUT:
---------------------
CMD>set 14 0
HTCST ÚÈHTCEUSB>
---------------------
6c: type "task 29" to get your device formatted:
---------------------
MTTY OUTPUT:
---------------------
Cmd>task 29
Format BINFS start
Fill RSVD information for block 288 to 321
CE start sector=0x14, total sector of CE and TFAT=0x14
CE start start block=321, total block=1727
ERASE block 1337 FAIL !!!
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS end
Cmd>
---------------------
6d: type "task 8" to ask your device reboot
uhmm strange i did mtty a lot of times using the same method and no problems...
Are you able to access your internal storage? i you can, try to get the ROM you want, then rename it to DIAMIMG.nbh and flash from internal storage, if you are flashing the 2.03 ROM from HTC, you might have problems too. Are you flashing that HTC Rom or is it a custom one?
Hi,
access to internel storage after clean with mtty ?? after clean there is no rom that can boot in the device to access it ! its fully naked
both is testet orginial shipped rom´s and custom rom's.
do you was having diamimg.nbh in your internal memory?
no, internal storage was cleared by hardreset - "restore manufacturer defaults and format movienand"
here are the outputs from mtty:
------------------------------------------
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_k9k2g08
DEVICE ID=0xAA
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x800
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 3 (0x3) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 12 (0xC) is reversed block
BLOCK 13 (0xD) is reversed block
BLOCK 14 (0xE) is reversed block
BLOCK 28 (0x1C) is reversed block
BLOCK 29 (0x1D) is reversed block
BLOCK 30 (0x1E) is reversed block
BLOCK 31 (0x1F) is reversed block
BLOCK 306 (0x132) is bad block
BLOCK 414 (0x19E) is bad block
BLOCK 873 (0x369) is bad block
BLOCK 1605 (0x645) is bad block
OS NOT FOUND !!!
------------------------------------------
Cmd>set 14 0
HTCST ÚÈÒHTCE
Cmd>task 29
Format BINFS start
Fill RSVD information for block 288 to 321
CE start sector=0x14, total sector of CE and TFAT=0x14
CE start start block=321, total block=1727
ERASE block 306 FAIL !!!
ERASE block 414 FAIL !!!
ERASE block 873 FAIL !!!
ERASE block 1605 FAIL !!!
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS end
Cmd>task 8
hawkeyexp said:
no, internal storage was cleared by hardreset - "restore manufacturer defaults and format movienand"
here are the outputs from mtty:
------------------------------------------
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_k9k2g08
DEVICE ID=0xAA
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x800
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 3 (0x3) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 12 (0xC) is reversed block
BLOCK 13 (0xD) is reversed block
BLOCK 14 (0xE) is reversed block
BLOCK 28 (0x1C) is reversed block
BLOCK 29 (0x1D) is reversed block
BLOCK 30 (0x1E) is reversed block
BLOCK 31 (0x1F) is reversed block
BLOCK 306 (0x132) is bad block
BLOCK 414 (0x19E) is bad block
BLOCK 873 (0x369) is bad block
BLOCK 1605 (0x645) is bad block
OS NOT FOUND !!!
------------------------------------------
Cmd>set 14 0
HTCST ÚÈÒHTCE
Cmd>task 29
Format BINFS start
Fill RSVD information for block 288 to 321
CE start sector=0x14, total sector of CE and TFAT=0x14
CE start start block=321, total block=1727
ERASE block 306 FAIL !!!
ERASE block 414 FAIL !!!
ERASE block 873 FAIL !!!
ERASE block 1605 FAIL !!!
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS end
Cmd>task 8
Click to expand...
Click to collapse
Did you try flashing a stock ROM? Try one that isnt newer than 2.03 (note: im not sure about vodafone Diamond ROMs, I have the unlocked version) use the .exe file, try to get the official one from their website.
I think that this is the reason why your flashes fail: http://forum.xda-developers.com/showthread.php?t=409425
hello,
I solve my error 226 by format MTTY with command task 28 55aa.
Perhaps that help you !
hi, also tested but didn´t help !
It seems if you have damaged Blocks in NAND, its harder to play with full flash... full erase...
I have 1 in my S8500...
You know the address first, if you play with erase or full flashes in JTAG...
BUT if you ever seen Blue Screen on your handset. If Debug Level was Mid or High.
Then handset report damaged blocks...
I'll search some Pics... for better understanding.
I have no idea, how many damaged blocks are "normal"...
Best Regards
Edit 1.
Message looks like this on handset, if Blue Screen appears... scroll to page...
Then you can read:
Code:
Bad Block information:
nNumBMP : 0
nAge : 0
Run Time Bad Block Occured :
Init BMPs = 1, Current BMPs = 0
This is taken from my S8530... this is alive and seems no damaged Blocks...
On my S8500 I can remember nNumBMP : 1
With RIFF Box (JTAG) you see for instance address...
http://forum.gsmhosting.com/vbb/f634/solved-s8500-error-pls-help-1089879/
My Block is damaged at 0x07100000
Edit 2.
size of 1 Block is 256 KB (Length 0x40000)
http://forum.xda-developers.com/showpost.php?p=13935305&postcount=23
So 256 KB is loosing/missing/unusable/unrestoreable
I'll check what 0x0710 0000 could contain...
Code:
Bad Block Information:
nNumBMPs : 0
nAge : 0
Run Time Bad Block Occurred :
Init BMPs = [B][COLOR="Red"]7[/COLOR][/B], Current BMPs =
0
Uuupsi, one of my "new" damaged test Wave 2 devices has 7 damaged Block from 512 MB OneNAND...
7 x 256 KB = 1792 KB
Nearly 2 MB seems damaged...
Device not long enough tested...
Will check again my other devices...
Best Regards
My JTAG S8500 shows me today this:
Code:
Bad Block Information:
nNumBMPs : 0
nAge : 0
Run Time Bad Block Occurred :
Init BMPs = [COLOR="Red"]4[/COLOR], Current BMPs =
0
Maybe not OneNAND but maybe moviNAND ?
Will check later again...
Best Regards
Now I am 95,7 % sure, this means 512 MB OneNAND.
Code:
Bad Block Information:
nNumBMPs : 0
nAge : 0
Run Time Bad Block Occurred :
Init BMPs = [B]2[/B], Current BMPs =
0
My S8530 shows me 2 damaged Blocks with RIFF JTAG, if I erase NAND...
My S8500 shows me 1 Block, if I play with RIFF and 1 Block, via Bluescreen:
Code:
Bad Block Information:
nNumBMPs : 0
nAge : 0
Run Time Bad Block Occurred :
Init BMPs = [B]1[/B], Current BMPs =
0
My prior post with 4... seems during my tests... this was temporary.
I have tested something stupid...
Hmmm. I have 3 devices used with RIFF JTAG...
First S8500 with broken Display
Second S8500 without visible damages... and without damaged blocks.
Third S8530 with broken Display + 50 % unusable Touchscreen + many visible scratches...
Strange, both devices with broken Display have damaged Blocks...
Maybe hard landings can damage OneNAND also...
Best Regards
Bad block management (BBM) is a critical component of NAND flash drivers to improve the reliability and endurance of the flash. NAND is shipped from the factory with “mostly good” cells, meaning there are some cells that are non-functional even when the flash is new. Blocks can also go bad over time, causing loss of data stored in the flash memory or even a bricked device. To prevent flash memory corruption, the Datalight line of FlashFX products employs patented bad block management technology to map bad sectors and avoid storing data in those areas. Using Datalight FlashFX flash memory drivers makes bad block management worry-free, making NAND flash reliable and reducing warranty returns.
Click to expand...
Click to collapse
http://www.datalight.com/solutions/technologies/bad-block-management
Interesting, found it here:
http://forum.xda-developers.com/showpost.php?p=33359041&postcount=6
Also interesting...
eMMC seems also moviNAND...
Best Regards
Has anyone created a clockworkmod for this? This phone can be rooted, thru two apps, poot, and ministro(Qt). It still has gingerbread 2.3.6, and I need clockworkmod, or the source code, to use clockworkmod's builder. It is the cdma variant of the alcatel 995(which is gsm). can anyone point me in the right direction?
Source Code
I have it rooted, with adb insecure running, to see everything. My bootloader seems to be locked, and the recovery is unknown, with limited options. I can do most things, except change roms, wipe data, or cache in recovery. I would like to be directed to good repository.
reggjoo said:
I have it rooted, with adb insecure running, to see everything. My bootloader seems to be locked, and the recovery is unknown, with limited options. I can do most things, except change roms, wipe data, or cache in recovery. I would like to be directed to good repository.
Click to expand...
Click to collapse
how did you get it rooted?
rooting alcatel authority (960c)
squidbutt said:
how did you get it rooted?
Click to expand...
Click to collapse
First make sure you have USB Debugging checked and your allowing instalation of unknown sources
DL these from the play store:
Minstro2
Superuser
DL poot.apk: View attachment poot.zip
Run poot, click yes to download the extra librarys, click "click here to poot" you will need to restart the phone when it prompts. You should be rooted now :good:
You can DL ES File Explorer(from play store) and in the settings check: Root Explorer, Up to Root and Mount File System. Now you can manage all the files on your phone but be careful of what you delete, some of the stock apk's are very hard to recover if you delete them.
Hope this helps
Download superuser first
Download superuser first, you won't be able to run it until the phone's rooted. after it's rooted, it will work. This way, seems to stop a problem, when you go thru the steps to root. Some people had a error. If you plan to open the /data, /system, or dalvik cache, on your computer, install chainfire's adb insecure. These folders don't open without this, on a computer.
I have the kernel source here, they have it released on SourceForge I'm guessing you're right saying the bootloader is locked.
Here's some information I've found on the partitions:
mmcblk0 Internal Memory
mmcblk0p1 Mounted using VFAT Contains files pertaining to FOTA (FOTA partition?)
mmcblk0p2 500 blocks ?
mmcblk0p3 1500 blocks ?
mmcblk0p4 1 BLOCK ?
mmcblk0p5 1000 blocks ?
mmcblk0p6 2000 blocks ?
mmcblk0p7 3072 blocks ?
mmcblk0p8 5120 blocks Possible Recovery*
mmcblk0p9 7000 blocks ?
mmcblk0p10 3027 blocks ?
mmcblk0p11 3072 blocks ?
mmcblk0p12 5120 blocks ?
mmcblk0p13 1500 blocks ?
mmcblk0p14 8192 blocks Mounts to /persist
mmcblk0p15 5120 blocks?
mmcblk0p16 1024 blocks?
mmcblk0p17 409600 blocks, Mounts to /system
mmcblk0p18 307200 blocks, Mounts to /cache
mmcblk0p19 892928 blocks, Mounts to /data
mmcblk0p20 122880 blocks, partition appears empty with a sting at the bottom of it reading ANDROID-BOOT!
mmcblk1 SD Card
mmcblk1p1 SD Card Partition
build.prop (Alltel phone):
build.prop
Source Code:
SourceForge Download Link
* In a recent patch I have found, the following code was in the install-recovery.sh file:
Code:
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/mmcblk0p15:2048:afbffa74556cd8e77ef7e1a9d0964d9a2bd446b8; then
log -t recovery "Installing new recovery image"
applypatch EMMC:/dev/block/mmcblk0p8:4055040:9411e1fd06dfb3d8da4d1924162caf9e292ea652 EMMC:/dev/block/mmcblk0p15 20270fc8f6c8fca7dae0af5ce0928b589bd6b405 4296704 9411e1fd06dfb3d8da4d1924162caf9e292ea652:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Any other information needed?
I'll look into getting a recovery working, but this is by no means a promise.
EDIT:
Something interesting:
The build.prop says the phone has a MSM7630_SURF board, and the Huawei U8800 has the same board, but not quite the same specs:
960C:
480x800
Multitouch
1400 Mhz CPU Sapdragon
512 MB RAM / 2048 MB ROM
Micro SD, 32 GB
3G
U8800:
480x800
Multitouch
800 Mhz CPU Snapdragon
512 MB RAM / 2048 MB ROM
Micro SD, 32 GB
AT&T has a 3g version
I'm betting these two are compatible, and the files I found contain some boot information.
Update:
I found the recovery.fstab for the U8800, doesn't look quite right does it:
Code:
# mount point fstype device [device2]
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
I'm not sure how exactly to make this resemble the above partition table...
Update:
More information:
U-boot seems to support this board? Maybe this is good?
http://lists.denx.de/pipermail/u-boot/2012-February/118168.html
Also if anyone else wants to take a stab at this, by all means. I'm having trouble getting the tools set up, but if someone with a little more experince wants to that would be great.
Haven't seen this
aldude999 said:
I have the kernel source here, they have it released on SourceForge I'm guessing you're right saying the bootloader is locked.
Here's some information I've found on the partitions:
mmcblk0 Internal Memory
mmcblk0p1 Mounted using VFAT Contains files pertaining to FOTA (FOTA partition?)
mmcblk0p2 500 blocks ?
mmcblk0p3 1500 blocks ?
mmcblk0p4 1 BLOCK ?
mmcblk0p5 1000 blocks ?
mmcblk0p6 2000 blocks ?
mmcblk0p7 3072 blocks ?
mmcblk0p8 5120 blocks Possible Recovery*
mmcblk0p9 7000 blocks ?
mmcblk0p10 3027 blocks ?
mmcblk0p11 3072 blocks ?
mmcblk0p12 5120 blocks ?
mmcblk0p13 1500 blocks ?
mmcblk0p14 8192 blocks Mounts to /persist
mmcblk0p15 5120 blocks?
mmcblk0p16 1024 blocks?
mmcblk0p17 409600 blocks, Mounts to /system
mmcblk0p18 307200 blocks, Mounts to /cache
mmcblk0p19 892928 blocks, Mounts to /data
mmcblk0p20 122880 blocks, partition appears empty with a sting at the bottom of it reading ANDROID-BOOT!
mmcblk1 SD Card
mmcblk1p1 SD Card Partition
build.prop (Alltel phone):
build.prop
Source Code:
SourceForge Download Link
* In a recent patch I have found, the following code was in the install-recovery.sh file:
Code:
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/mmcblk0p15:2048:afbffa74556cd8e77ef7e1a9d0964d9a2bd446b8; then
log -t recovery "Installing new recovery image"
applypatch EMMC:/dev/block/mmcblk0p8:4055040:9411e1fd06dfb3d8da4d1924162caf9e292ea652 EMMC:/dev/block/mmcblk0p15 20270fc8f6c8fca7dae0af5ce0928b589bd6b405 4296704 9411e1fd06dfb3d8da4d1924162caf9e292ea652:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Any other information needed?
I'll look into getting a recovery working, but this is by no means a promise.
EDIT:
Something interesting:
The build.prop says the phone has a MSM7630_SURF board, and the Huawei U8800 has the same board, but not quite the same specs:
960C:
480x800
Multitouch
1400 Mhz CPU Sapdragon
512 MB RAM / 2048 MB ROM
Micro SD, 32 GB
3G
U8800:
480x800
Multitouch
800 Mhz CPU Snapdragon
512 MB RAM / 2048 MB ROM
Micro SD, 32 GB
AT&T has a 3g version
I'm betting these two are compatible, and the files I found contain some boot information.
Update:
I found the recovery.fstab for the U8800, doesn't look quite right does it:
Code:
# mount point fstype device [device2]
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
I'm not sure how exactly to make this resemble the above partition table...
Update:
More information:
U-boot seems to support this board? Maybe this is good?
http://lists.denx.de/pipermail/u-boot/2012-February/118168.html
Also if anyone else wants to take a stab at this, by all means. I'm having trouble getting the tools set up, but if someone with a little more experince wants to that would be great.
Click to expand...
Click to collapse
Hello, I haven't looked into this thread for a while. I see that you have some info for these blocks. that I couldn't get. I tried using root explorer, to look into some files, and they couldn't load, and tried to use too much memory, just to attempt to open, which, my phone said it was low on memory. Hate gingerbread, and kwansi choi( maker of this rom), This phone could easily handle a later os.
The usb ID's, are "Device 007: ID 1bbb:9018" .
USB ID's
The usb ID's are 1bbb/9018 . I built a clockworkmod File, and the status is ok, but it still won't flash, because of the bootloader.
reggjoo said:
The usb ID's are 1bbb/9018 . I built a clockworkmod File, and the status is ok, but it still won't flash, because of the bootloader.
Click to expand...
Click to collapse
I noticed that:
mmcblk0p15
mmcblk0p12
mmcblk0p8
all have the same number of blocks.
The FOTA code shows
applypatch EMMC:/dev/block/mmcblk0p8:4055040:9411e1fd06dfb3d8da4d1924162caf9e292ea652 EMMC:/dev/block/mmcblk0p15 20270fc8f6c8fca7dae0af5ce0928b589bd6b405 4296704 9411e1fd06dfb3d8da4d1924162caf9e292ea652:/system/recovery-from-boot.p
Click to expand...
Click to collapse
applypatch useage is as follows:
applypatch [-b <bonus-file>] <src-file> <tgt-file> <tgt-sha1> <tgt-size> [<src-sha1>:<patch> ...]
or applypatch -c <file> [<sha1> ...]
or applypatch -s <bytes>
or applypatch -l
Click to expand...
Click to collapse
Apply patch from blk8 to blk15.
So maybe I was mistaken with what I thought was the partition. Blk8 seems to be where fota grabs it's updated partition from?
This shows that blk15 may actually be the recovery partition. Still useless unless the bootloader can be worked on.
Battery terminals
As we know, if the battery is out, the phone will do nothing( unlike my old huawei, it didn't matter). I wondered if that was the reason why, it's so hard to unlock it. I think the bootloader has been set up to not respond to attempts. The bootloader condition treats the phone as if there's no power to it(?) . I found out that the middle terminals, of the battery contacts, will power the phone, if they're connected, but only for a few seconds.
Maybe there's some code that's unknown, or procedure. The phone doesn't respond to fastboot commands, and I can't enable it(function), on it. In the default.prop file, I see that ro.secure, is 1. Whenever I try to change it to 0( in rewritable mode), it never takes. So this is a little info.
reggjoo said:
The bootloader condition treats the phone as if there's no power to it(?)
Click to expand...
Click to collapse
You know, it's interesting that you mention that. I remember watching a Ben Heck episode, and on an Xbox 360 controller keypad, he had to open it up and connect power to the PIC chip manually. It almost makes me wonder if there's possibly a jumper of some sort on the motherboard somewhere that when connected allows writing? It would be an extremely long shot, I'm even pretty sure that it's the exact board in the Huawei but it's weird that fastboot can't be entered. I've heard that their drivers might be messed up (maybe even on purpose) that could keep you from using fastboot.
aldude999 said:
You know, it's interesting that you mention that. I remember watching a Ben Heck episode, and on an Xbox 360 controller keypad, he had to open it up and connect power to the PIC chip manually. It almost makes me wonder if there's possibly a jumper of some sort on the motherboard somewhere that when connected allows writing? It would be an extremely long shot, I'm even pretty sure that it's the exact board in the Huawei but it's weird that fastboot can't be entered. I've heard that their drivers might be messed up (maybe even on purpose) that could keep you from using fastboot.
Click to expand...
Click to collapse
Yes, I think alcatel's a little shady. I use a dual boot pc, and I found out, using the lsusb command, that the usb id's were different, than what the id's were for the supposedly official usb drivers. Sent them a msg, and they said I was wrong( can't be wrong if everything works!). They take no responsibility for their hardware, and I let people know, every chance I get, whenever I see a review of a phone from them. I found out the id's were wrong, when, before I even rooted it, I installed their onetouchmanager, and it couldn't find my phone( what! out the box!). That's not the way you do things.
Bringing 960C Back To Life!!!
Did anyone ever find a ROM that's compatible with the 960C? I recently found one floating around a storage unit and, naturally, I immediately rooted it only to find out that no one ever bothered developing a custom ROM.
I'm sure if an official ROM was never created specifically for the 960C, it's definitely not gonna happen at this point. I'm thinking that the only hope for the 960C is if it was similar enough to a more popular phone that HAS a custom ROM, maybe someone, somewhere, was successful in modding it just enough to make it compatible with the 960C...
During my research/investigation into a ROM, there was at least one (*HERE*) forum post mentioning someone attempting to mod an existing ROM (for a more popular phone) to make it compatible but it seems that everyone lost interest back in 2013...
thealexday said:
Did anyone ever find a ROM that's compatible with the 960C? I recently found one floating around a storage unit and, naturally, I immediately rooted it only to find out that no one ever bothered developing a custom ROM.
I'm sure if an official ROM was never created specifically for the 960C, it's definitely not gonna happen at this point. I'm thinking that the only hope for the 960C is if it was similar enough to a more popular phone that HAS a custom ROM, maybe someone, somewhere, was successful in modding it just enough to make it compatible with the 960C...
During my research/investigation into a ROM, there was at least one (*HERE*) forum post mentioning someone attempting to mod an existing ROM (for a more popular phone) to make it compatible but it seems that everyone lost interest back in 2013...
Click to expand...
Click to collapse
I still am using my 960c. I wouldn't mind finding the original stock rom or finding out how to upgrade to a newer android version. Currently running version 2.3.6
Too bad I don't know much about modding save for rooting and flashing. I gather there are still some of us here who really like our 960c phones otherwise.
Hello.
I bought an M9, that is stuck on bootloader, but also can boot to recovery, willing to fix it, but haven't checked recovery before paying and this is what I got:
wiping, formatting, adb sideload error - unable to mount /data, /cache/, /system and it shows that cache is 0mb, ok this is one is maybe ok, but system is 0mb, data 0mb, android secure 0mb. I'm using twrp v2.8.7.0, tried flashing stock recovery or other version though fastboot, no errors, but recovery won't change and boots to same twrp recovery.
Tried to fix this using corrupted data partition fix method > http://android-revolution-hd.blogspot.lt/2013/10/fix-data-htc-one.html
but this is what I got:
C:\adb>adb push mkfs.ext4 /tmp
2604 KB/s (3537143 bytes in 1.326s)
C:\adb>adb shell
~ # ←[6nchmod 777 /tmp/mkfs.ext4
chmod 777 /tmp/mkfs.ext4
~ # ←[6n/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,
^extra_isize -m 0 /dev/block/mmcblk0p37
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext
ra_isize -m 0 /dev/block/mmcblk0p37
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
32 inodes, 64 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
1 block group
32768 blocks per group, 32768 fragments per group
32 inodes per group
Writing inode tables: done
Filesystem too small for a journal
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 21 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
~ # ←[6n
Click to expand...
Click to collapse
I don't think it should be 32 inodes, 64 blocks, same as others in bold.
I don't know what to do, if someone could help me fix this I could transfer to PP let's say 20$, as, in my opinion, this problem could take some time to sort out and at least I would be lazy to help someone that much.
That looks to me like a borked nand and no spare blocks to use. Ive seen software lying around on the web that is the same software htc use to flash the nand in its raw state. Although this could be worth trying I'm quite sure the nand is beyond repair.
Solid state drives die if they go corrupt due to their design. One block dies, they all die.
Beamed in by telepathy.
shivadow said:
That looks to me like a borked nand and no spare blocks to use. Ive seen software lying around on the web that is the same software htc use to flash the nand in its raw state. Although this could be worth trying I'm quite sure the nand is beyond repair.
Solid state drives die if they go corrupt due to their design. One block dies, they all die.
Beamed in by telepathy.
Click to expand...
Click to collapse
Thank you, good to know that I don't need to play around with it anymore as it won't help. What about M9 Sprint parts, are they interchangeable with 0PJA100? I know that on other models there might be slight difference (comparing to Sprint) in form, even specs, but in M9 they look, at least, same.
Sorry, can't help you with the destruction of devices. I'm not allowed to be loose in public with a screwdriver of any description. If you think war is bad, just let me loose with power tools and the planet is in REAL danger!.
Beamed in by telepathy.
shivadow said:
Sorry, can't help you with the destruction of devices. I'm not allowed to be loose in public with a screwdriver of any description. If you think war is bad, just let me loose with power tools and the planet is in REAL danger!.
Beamed in by telepathy.
Click to expand...
Click to collapse
Got it. Bought wrong item on Ebay and though about miracle that it would work, thank god seller noticed my message about canceling order before shipping it.