Here is a picture of my hboot and so far it's very stable, fastboot stable, fastboot usb stable, laptop recognizes my phone, hboot stable.
Lock your bootloader, next you'll need to downgrade the base with flashing THAT
You'll need to rename PN07IMG_M7_UL_JB_50_HTC_Europe_1.29.401.13_Radio_4A.14.3250.13_10.33.1150.01_release_316789_signed.zip
to rom.zip, then place it to directory where you keep fastboot & adb.
next put your phone in fastboot usb, then in windows cmd:
Code:fastboot oem rebootRUU
now your phone is in RUU mode and now you need to be really really really careful!
type:
Code:fastboot flash zip rom.zip
your phone will reboot in RUU mode by itself, do not be scared
You should see at the end of cmd saying:
some errors or error 99 or something like that
at it will say Flush Image Immediately!!!
retype:
Code:fastboot flash zip rom.zip
And NOW LEAVE AND DO NOT TOUCH your phone. It will take about 15-20 minutes.
When it's done the progress bar will be at very end showing like it stuck, do not be scared
In Windows CMD should say: SUCCESSFUL!!!
type in cmd:
Code:fastboot reboot
And your phone will be like out from the box
Be REALLY Careful with this procedure
Sorry sorry, my mistake, here it is:
~ # cat /proc/emmc
cat /proc/emmc
dev: size erasesize name
mmcblk0p19: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
mmcblk0p35: 73fffc00 00000200 "system"
mmcblk0p26: 00140200 00000200 "local"
mmcblk0p36: 27fffe00 00000200 "cache"
mmcblk0p37: 680000000 00000200 "userdata"
mmcblk0p22: 01400000 00000200 "devlog"
mmcblk0p24: 00040000 00000200 "pdata"
mmcblk0p27: 00010000 00000200 "extra"
mmcblk0p31: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p20: 00400000 00000200 "modem_st1"
mmcblk0p21: 00400000 00000200 "modem_st2"
mmcblk0p28: 00100000 00000200 "cdma_record"
mmcblk0p18: 02000000 00000200 "reserve_1"
mmcblk0p30: 034ffa00 00000200 "reserve_2"
mmcblk0p32: 05fffc00 00000200 "reserve_3"
mmcblk0p29: 06069e00 00000200 "reserve"
~ #
yep, missing spaces is no good, let's go ahead and check the partitions:
~# umount /data
~# e2fsck -n -v -f /dev/block/mmcblk0p35
~# e2fsck -n -v -f /dev/block/mmcblk0p36
~# e2fsck -n -v -f /dev/block/mmcblk0p37
just report back, nothing else
Holy Crap, you have lots or corrupt stuff, unfortunately at this stage I'm going to have to say it's most likely a hardware defect, I'm going to post back shortly with instructions on "real" formatting the partitions back to scratch, but if after the format, the filesystem doesn't hold, then it's a hardware problem.
@xavier_largeaux, how is he going to run a downgrade with S-On??
@enel_ I'll post back in a few minutes.....
Third:
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
Inodes that were part of a corrupted orphan linked list found. Fix? no
~ #
~# [B]/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37[/B]
Bad news, my phone was connected to my laptop, in cwm, suddenly it rebooted, rebooted twice, and booted back to my homescreen. And at my homescreen it rebooted again...
So I think we are again in the reboot horror story and it's going to reboot itself when he wants...
We are again in the same horror story as before. I can't boot my phone, as far as I can see I'm going to need like 50 attempts to boot it once.
If I should boot it, can I flash again the boot.img? Flashing it today gave as this time window when my phone was stable?
~#[B] /tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p36[/B]
~# [B]/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37[/B]
Holy Crap, you have lots or corrupt stuff, unfortunately at this stage I'm going to have to say it's most likely a hardware defect, I'm going to post back shortly with instructions on "real" formatting the partitions back to scratch, but if after the format, the filesystem doesn't hold, then it's a hardware problem.
@xavier_largeaux, how is he going to run a downgrade with S-On??
@enel_ I'll post back in a few minutes.....
Thank you very much nkk71, I'm just fu*king sad about this.
I'm going to do all your steps once I've booted into recovery and I hope this will solve my problem.
Just one more question, is unlocking my bootloader the reason for all this?
Or is it flashing TWRP? Or something else...?
The Link what I posted earlier is Signed RUU for HTC One Europe HTC__001 PN071000 There will be a signature check and it will reflash entire all partitions but bootloader must be locked otherwise it will fail on first stage. This is only 1 solution what I can think of if the partition table is corrupted and some blocks are not allocated properly. I'm just trying to help
Unlocking -> NO
Flashing anything -> NO
TWRP -> highly unlikely (though the two cases I was able to successfully help, had a version of TWRP installed, so there could have been something in one of the versions), but again HIGHLY unlikely, those devs are great and test their stuff to the limit.
if the "real format" doesnt work, then it's a hardware fault. not because you flashed anything!
I'm checking something with mike, and when he get's back to me, if the info has changed I'll let you know. try the steps and post back. wish you best of luck
---------- Post added at 08:10 PM ---------- Previous post was at 08:05 PM ----------
Salut Xavier, I wasn't trying to be disrespectful or anything really!! Sorry if I offended you, I apologize, and I know you are trying to help :good:
But even with a signed RUU, it will fail because it's an older version than the one on his phone. the only way to downgrade is if you have S-Off.
I was able to boot into recovery and I did all steps to
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37
In the middle of this step my phone rebooted. When I boot again into recovery, should I countinue from this step?
hold, were you able to format partition mmcblk0p36 properly?? copy/paste please
Here is a copy of cmd:
C:\Users\enel\AppData\Local\Android\android-sdk\platform-tools>adb push mkfs.ext
4 /tmp
3398 KB/s (3537143 bytes in 1.016s)
C:\Users\enel\AppData\Local\Android\android-sdk\platform-tools>adb shell
~ # chmod 777 /tmp/mkfs.ext4
chmod 777 /tmp/mkfs.ext4
~ # umount /data
umount /data
~ # umount /cache
umount /cache
umount: can't umount /cache: Invalid argument
~ # /tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext
ra_isize -m 0 /dev/block/mmcblk0p36
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext
ra_isize -m 0 /dev/block/mmcblk0p36
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
40960 inodes, 163839 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
5 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 28 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
~ # /tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext
ra_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
1703936 inodes, 6815744 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
208 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Writing inode tables: 171/208
C:\Users\enel\AppData\Local\Android\android-sdk\platform-tools>
fastboot erase cache
fastboot flash recovery <file_name>.img
adb push <file_name>.zip /data/media/0/
I managed to upload my logcat, here it is:
http://www14.zippyshare.com/v/26697521/file.html
I'm afraid xavier to flash a new rom because my phone is unstable in recovery, what if it freezes and shuts itself down in the middle of the flashing process?
What if I just flash the stock recovery and lock my bootloader again? Maybe my phone is so unstable because of the bootloader?
switch off your device and connect it to pc using cable, is it going into recovery?No no, I just unlocked my bootloader, flashed recovery and installed superSU.
Unfortunately I flashed TWRP also after I unlocker my bootloader...
10 min ago I wanted to flash stock recovery then clockworkmod and then the rest of your process. Somehow I booted my phone into fastboot, after a lot of attempts to boot it, connected it to my laptop, went into cmd, typed fastboot flash recovery recovery. img it started but suddenly my phone shut itself down, I got a failure in cmd and now after over 30 attempts I can't boot my device.
Is the interruption of this process something bad? Bricked device?
Ohhh man, it seems like partition table is corrupted ;/I've made some progress.
First a extracted boot.img from the latest stock sense rom. I flashed boot. img via cmd with the command fastboot flassh boot boot.img.
After that I typed fastboot erase cache and then fastboot flash recovery "clockworkmod.img" (the real name is too long).
After that I tried to boot into recovery but I only got the white screen with the HTC logo and on top "boot in revocery" or something like that, but I waited few minutes, it didn't changed and it didn't booted into recovery.
So I turned of my phone, turned it back again into hboot, then fastboot, erased cache again, flashed stock recovery and went to boot into stock recovery. But all I got there is a totally black screen and it was black for minutes, so I went to shut down my phone again but suddenly my back and home key went on and I got a picture on my display, it was like an HTC but with a red triangle.
After that it booted normally to my homescreen, now my phone is on and I connected it my charger because I'm running out of battery.
For now we have some progress, let wait for the battery to charge up so I can continue to boot into recovery.