yashsingh1/xdaforums huggingface dataset:
[HTC Sensation] Sverrebob:
So, where to start?

I'll start with my broken screen:

1 -new screen ordered (complete assembled LED+digitizer)

2 -installed the new screen, put phone back together and turned ON

3 -phone immidiately went into bootloop!

4 -did some google research and found this site and figured out how to get into bootloader (vol down+pwr)

5 -bootloader works fine, but left it on too long with phone not on charger (battery might have died?) phone not turning on and red LED blink while in charger

6 -ordered new battery, it arrived today. Phone got back on and into bootloader.

7 -unlocked bootloader by using the HTCDEV com site, and their method. worked fine!

8 -then turning phone back on after a failed restart after the bootloader unlock, and it wont turn on taking me back to stage 5 :(

The phone was connected via usb during the bootloader unlock and the restart after. But I never got it back on :(

There is one thing I am curious about aswell - the phone get very hot around the SD-card slot and it smells warm electronics. I dont know if this is normal but I cant say I noticed this before when the phone was working. I am very sure that I re-assembled the phone correctly after replacing the LED+digitizer as both these parts came to me already assembled.So only thing I did was removing the screen case with the LED and digitizer and replacing it with the new one.

I really hope anyone have ANY input on this as I would really like to get my phone back on and working so I can root it.
[HTC Sensation] ahsan64:
Pull out the battery then place again and after that try to go into bootloader ..

Also phone showing red light while charging ?
[HTC Sensation] Sverrebob:
I let the phone cool down (it get's very hot very fast!) and removed battery and replaced it again, phone ON and in bootloader now, thanks :)

The heat issue still remains tho, I wonder if this might be the source of this unstable situation with the phone not turning back on and then suddenly after a cooldown it does... any thoughts? :confused:

EDIT: Yes when this problem occurs the red LED blinks "on long" "off long" while the phone is in charger.
[HTC Sensation] ahsan64:
Are you using Stock Rom or Custom Rom ..

The heat issue is normal but sometime it's due to overclocking 2d/3d GPU ..
[HTC Sensation] Sverrebob:
The phone is completely stock except the replaced screen. I encountered the bootloop after replacing the screen and it's been like that since...
[HTC Sensation] ahsan64:
Two methods:

1: Follow this GUIDE if phone Hboot is 1.27 or 1.29 and flash any custom Rom .

NOTE: You can skip step 2(S-OFF PART) in above guide :)

2: Or just find official RUU and install it and see if phone boots ..
[HTC Sensation] Sverrebob:
Ok I will try this :) thanks!

Just got the phone back on and into bootloader, had to let it cool off again to get it on. I feel somewhat connected to the other thread in this forum - "Dead sensation" ...
[HTC Sensation] Sverrebob:
Update :

I cant seem to access the sd card when I have my phone in Fastboot usb mode and since my rom is f**ked I cant boot into the phone either.

Also recovery fails, probably due to fastboot still active, any way to turn that off when I cant get past bootloader?

And if anyone know how I can access the sd card from phone on my PC I would appreciate it :/

De-assembled my phone again just to recheck all connectors etc, all seems just fine... really confused on whats up with this phone now :/:confused:
[HTC Sensation] rzr86:
it would be better to use a ruu.exe and see how it goes then

http://xdaforums.com/showthread.php?t=1672425
[HTC Sensation] Sverrebob:
my bootloader reads as follows:

***relocked***

PYRAMID PVT SHIP S-ON RL

HBOOT-1.27.0000

eMMC-boot

Jan 13 2012,17:33:34

my cid is HTC__Y13 and my version-main is 3.33.401.53

using this info I can only find this RUU: RUU_PYRAMID_ICS_HTC_Europe_3.33.401.53_Radio_11.76A.3504.00U_11.24A.3504.31_M

I dont know if this is correct, I dont see anything resembling my cid in there.

note: bootloader is relocked using

fastboot oem lock

as the http://xdaforums.com/showthread.php?t=1672425 guide says. Following that guide now but is confused on the RUU to get. Gonna try with the RUU I have downloaded now and I'll let you know how it goes...
[HTC Sensation] Sverrebob:
Ok I completed the exe RUU file and it told me it was completed, STILL I only get green HTC logo and bootloop. Entering bootloader the pgone tells me the battery voltage is too low, will this prevent the phone from booting normally?

I have it on FASTBOOT AC now and hope it will charge, then I'll try to restart the phone and see if I can boot it.
[HTC Sensation] rzr86:
after charge use the command to reboot from bootloader if it fails normally

fastboot reboot
[HTC Sensation] Sverrebob:
Tried that several times already, same thing happens, white screen with green HTC , goes into the usual bootloop.

Recovery from bootloader menu also end up the same way as above.

Factory reset aswell.

Also, every time I get into bootloader it does this check you can see on this screenshot here

Any inputs on this, or is this normal when the SD card is empty?

During the white bootloop screen with green HTC the SD card does get recogniced by my PC and shows up in explorer briefly before phone reboots again, so it cant be the SD card reader can it?

I consider myself pretty much advanced when it comes to techology and I have been reading up on all this stuff around phones and what you can do with them. I feel I have gotten a pretty basic understanding so far, and from my point I really does not see why my phone wont behave normal.

It kinda cooks down to some hardware fail, atleast in my opinion? I'm really at my wits end here :mad:
[HTC Sensation] heavy_metal_man:
Hi, gonna try help out :)

firstly, your screen shot. that will always happen when you boot into the bootloader with an sd card in the phone. doesnt matter whats on it, it will always check it for those files if it detects it. its not an issue :)

Second, when you try to boot into recovery, does it ever make it? or does it always sit at the splash screen. ( the white background with the green htc letters.)

thirdly, if you are willing to unlock your bootloader again can you place the attached recovery.img and place it into your adb/fastboot folder, and then when in fastboot usb issue the command fastboot boot recovery.img , hopefully it will boot into 4ext recovery temporarily, and allow you to try get some system information. (assuming your new touch screen works ;) ) you may get some warnings if/when 4ext boots up. make a note of all of them and reply to here please :)
[HTC Sensation] Sverrebob:
I appreciate the reply :)

It have never gotten into recovery, it always stuck at the "splash screen" and have done so with both 4EXT and CWM.

thirdly: I unlocked the bootloader and put your attached recovery.img into the fastboot folder, ran the command with phone in "fastboot usb" and ended up on splash screen as always, it stays there for a few seconds then it goes black. It seems like the phone is rebooting but the screen remains black. I do, however, get the well-known sound of an usb device beeing attached and removed again, with a few seconds silence in between. Screen remains black. To solve this mysterious "bootloop" I remove the USB cable, gives it half a minute and do the vol-down pwr button method and then I am back in the bootloader again.

Just for fun I have tried the recovery menu in bootloader with the phone not connected to usb, same splash screen here. It just seems that my phone really dont want the recovery to work :p :/
[HTC Sensation] Sverrebob:
extra info: figured out that the screen went black after one splash screen due to me pressing vol-down. It apparently does 3 reboots showing splash screen, then a couple mysterious black screen reboots and then another splash screen reboot three times... I have stopped this weird cycle now to save my poor battery, but it seems that it would just have continiued this behavior of 3 splash screen reboots - 2 black - 3 splash and so on...

weird!

ALSO; this is the response from fastboot command I get when trying to boot the recovery from there:

C:\android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.493s]
booting...
OKAY [ 0.002s]
finished. total time: 1.495s
[HTC Sensation] rzr86:
did you try to boot into safe mode?

once you will see the splash screen hold volume down until it gets you to the safe mode

see if it works
[HTC Sensation] Sverrebob:
Thank you for the tip, unfortunately it didnt seem to work :(

I pressed volume down as soon as the splash screen appeared after I executed the <fastboot boot recovery.img> and it just hang there for a few seconds then the phone rebooted and I ended up in the bootloader again.
[HTC Sensation] heavy_metal_man:
Hmmm. This is very strange indeed. My theory is that your internal partitioning may be messed up, so when the phone tries to boot things are not in the right place. But that doesn't explain why it won't fastboot boot, as fastboot boot should boot the .IMG into the ram and not attempt to flash it. It may well be down to a hardware fault. If your ruu ran without any errors then it should have fixed any partition errors. You could try extracting the boot.IMG from the ruu and use the fastboot boot boot.IMG command and see if that gets you any farther.

Also when your phone goes into the black after the splash screen, can you keep it connected to the PC and issue the command adb devices for me :) just a hunch I have :)
[HTC Sensation] Sverrebob:
So get this, tried to <fastboot boot recovery.img> again in order to obtain this black screen and do your <adb devices> and nothing! It's like the phone heard you and decided to "behave".....

It did 10 perfectly normal reboots with the splash screen every time, and the 4th and 5th time it even vibrated once...!

This whole charade is almost a little funny to me now, but clown phone or not, I'm not giving it up yet :p

I managed to google how-to extract the boot.img file from the RUU exe, it was a rather tidious operation :p

I found a very well explained guide on it here; https://sites.google.com/site/androidbyyorzua/home/tutorials/extracting-rom-files-from-htc-ruu

And not suprisingly all I got out of it was a error msg

C:\android>fastboot boot boot.img
creating boot image...
creating boot image - 3868672 bytes
downloading 'boot.img'...
OKAY [ 0.984s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 0.999s

Something wrong with my phones RAM maybe? :confused:

EDIT: I tried the fastboot command to flash the rom.zip and this is how it went.

C:\android>fastboot flash zip rom.zip
sending 'zip' (436283 KB)...
OKAY [ 57.499s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: not allowed)
finished. total time: 57.819s

Tried it again with bootloader RELOCKED and it took alot more time and was slightly different, but still same error msg

C:\android>fastboot flash zip rom.zip
sending 'zip' (436283 KB)...
OKAY [ 57.685s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: not allowed)
finished. total time: 134.679s
[HTC Sensation] heavy_metal_man:
Hey pal :) sorry ive taken so long ive been researching. i think it may be your internal partitions are messed up. since your s-on your pretty much stuck unless we can get a ruu to run for you. within the rom.zip you have extracted there should be a text file called android info i believe. check and see if your cid is within this txt file, also check and see if your hboot version is higher than the one within your rom.zip file. if your phones is higher it wont flash it. also, when you try to flash it, try issuing the commands

fastboot oem rebootRUU

fastboot flash zip rom.zip

fastboot flash zip rom.zip

fastboot reboot

assuming that the zip you have is still called rom.zip, your bootloader is locked and your bootloader is not higher than the one in the rom.zip

the second flash command is after the first one finishes saying it needs to be flushed, or reflushed. give this a bash and i will keep on hunting for you :) if on the other hand your hboot versions wont play ball or the cid is off we shall have to find you a newer/correct one :)
[HTC Sensation] Sverrebob:
Okay I really appreciate the help man :D

This is from the android_info.txt inside my rom.zip

modelid: PG5813000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__N34
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__016
mainver: 3.33.401.53
hbootpreupdate:12
DelCache:1

so the cid and mainver are the same as on my phone. It's says nothing about the hboot version as far as I can see. Unless you mean a file inside the rom.zip that is named < hboot_8x60_1.27.0000_20120113_signedbyaa.nb0 > ? This is the same as my hboot version (1.27)

I've run the fastboot commands you posted, got me into a black screen with silver "HTC" and then a large wall of text appeared also a green bar filling up on my phone's screen. Once the first < fastboot flash zip rom.zip > was done I issued the next one and fairly the same wall of text came, only with a few different changes... see below

(bootloader) [RUU]WP,system,96
(bootloader) [RUU]WP,system,98
(bootloader) [RUU]WP,system,100
(bootloader) start image[sp1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) start image[sbl2] unzipping & flushing...
this is just 5% of all the text btw!
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,73
(bootloader) [RUU]WP,radio,100
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]WP,rcdata,0
OKAY [416.100s]
finished. total time: 473.652s

< fastboot reboot > rebooted the phone and splash screen appeared, staying there for 20-30s then going black and repeating the same splash screen. this has been going on for 5 minutes now. I assume this means it didnt work :(
[HTC Sensation] heavy_metal_man:
well it means the update worked :( its very much looking like a hardware issue now :/
[HTC Sensation] Sverrebob:
I totally agree :(

btw I noticed something, if you look at my above post of the android_info.txt it says the hbootpreupdate is 12 , and this paste below is from my phone when I run a < fastboot getvar all > it seems my phone has the hbootpreupdate set to 11. Has this anything to say?

C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.53
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxx
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4114mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
[B](bootloader) hbootpreupdate: 11[/B]
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.495s
[HTC Sensation] heavy_metal_man:
its possible that the phone is ignoring the hboot pre update from the rom.zip as it may not need it. tbh we are starting to move out of my depth. did the phone definitely work bar the dead screen before you acquired it? do you know how it came to be broken? i mean like if it was ran over before you got it it may well be ram damage :/
[HTC Sensation] Sverrebob:
The phone was working just fine before I replaced the screen, and it was only the digitizer glass that was shattered. I ordered the LCD+digitizer because according to many it was far more easier to replace those two rather than just the digitizer. That was because I didnt have to disassemble that much. I should of just kept the phone as it was with a shattered digitizer glass, the touch was OK and I could see what was on the screen.

Now it seems like I have to try and get a new sensation, hopefully I can find one with a broken screen so I can get it cheap. :p
[HTC Sensation] heavy_metal_man:
Seems like it pal :/ sorry we couldnt get it going again like. always feels like a waste when they die like this eh?
[HTC Sensation] Sverrebob:
I know, it sucks :(

But the help I have recieved here have been outstanding tho. I will certainly come back here when I get a new phone :)
[HTC Sensation] heavy_metal_man:
I help when i can :) we all tend to share the love here, common goals and all that :) welcome to xda developers pal :cool:
[One (M7) Original Android Development] Cotulla:
Hello, hihihi

I am Cotulla, member of DFT team, probably some of you already know me by older projects related with famous HTC HD2 (Leo).

Nowdays HTC Leo become too old :(, while hardware abilties are growing very fast nowdays

(huh, already phones with 64 bit CPUs and 4 Gb RAM? Wtf my old PC from 2008 has 4 Gb ram too)

So I decided to switch hobby phone, finally I got HTC One 64Gb (thank all contributors),

so I am with you now :highfive:

I am not sure about developement goals,

I am doing it for fun, but probably it will be something like:

1)Oldschool WM61/65 port :laugh:

2)Windows RT and/or Windows Phone 8

3)Own bootloader

Ofcourse I no idea about port quality - things like ultrapixel camera can be impossible to bring up.

But it's hobby, not attempt to do a work instead of a big company.

I am already started to work on MAGLDR for HTC One.

Then I am planning to bring UEFI up.

Will keep community in sync about development status.

Releases are going to be more often.

About different models support: there are many different HTC One revisions around, I will try to support as much as possible of them.

It seems S-OFF is mandatory requirement.

As well as I have question to One Android developers and need some kind of support:

I am going to divide the biggest "userdata" partition to grab a space for another OS.

userdata it seems is EXT4 formatted.

I don't want to modify primary GPT (at eMMC sector 0) to minimize ability to brick device.

My current idea is a hack inside Linux GPT parser to replace userdata partition bounds.

In such scheme Linux kernel must be modifed to use MAGLDR / another OS.

But I don't know how Android will like unformatted userdata partition. Anyone knows?

Or maybe someone can suggest better scheme?
[One (M7) Original Android Development] HD2Owner:
very nice. looking forward to your impressive work. :highfive:

@ mods: reserved post for future modifications etc.
[One (M7) Original Android Development] -W_O_L_F-:
Maybe kexec can be used for kernel/BL start.
[One (M7) Original Android Development] Cotulla:
I am using fastboot boot now for testing MAGLDR. Later MAGLDR should be flashed as boot.img and android kernel will go to another place...
[One (M7) Original Android Development] Shan89:
All I can say is I'm proud to own same device as you do , for more info you're looking for i would suggest you to ask flar2 ( kernel dev ) , n3cortX ( also kernel dev ) or tbladen I'm sure they'll be happy to help you out with informations you seek for.

Anyway good luck with your development ! , looking forward to use it and hopefully one day load w8 as dual boot on the one !
[One (M7) Original Android Development] matt95:
That sounds good :) i trust your "Elite Recognized Developer" thing :D

Wait but, UEFI? also here on phones?

By the way HTC will hate you, they have big economic issues and from now on nobody will buy new HTCs again LoL :D
[One (M7) Original Android Development] Samuelgames:
This is awesome, I know it's too early to ask this but do you plan to port this to the HTC MSM8960 series devices (One S, One XL, Evo 4G LTE)? Hardware wise they are almost indentical to the One
[One (M7) Original Android Development] Guich:
Mate, he need a device for this.

And, personally, the hardware isn't the same, the partition aren't the same so it's a bit impossible port it, above all without device...

Finally, this project require time :)
[One (M7) Original Android Development] YamazakiRobert:
[MENTION=600525]Cotulla[/MENTION]

in the partition layout why not start from mmcblk0p34 to mmcblk0p37?
[One (M7) Original Android Development] the_scotsman:
This is fantastic news! I used your work on the HD2 for a LONG time! very excited to see what can be done! WP8 on the HTC One would be excellent! :good:
[One (M7) Original Android Development] Cotulla:
mmcblk0p34: 00fffe00 00000200 "recovery"

mmcblk0p35: 73fffc00 00000200 "system"

mmcblk0p36: 27fffe00 00000200 "cache"

mmcblk0p37: dc8000000 00000200 "userdata"

I am want to grab space from mmcblk0p37 partition,

put MAGLDR into

mmcblk0p33: 01000000 00000200 "boot"

and probably put Linux kernel to one of unused partitions:

mmcblk0p30: 034ffa00 00000200 "reserve_2"

mmcblk0p32: 05fffc00 00000200 "reserve_3"

mmcblk0p29: 06069e00 00000200 "reserve"

Probably by same method by before :laugh:

Hardware is not really same, ever newest linux kernel ports sometimes are very complicated.
[One (M7) Original Android Development] Cotulla:
I got small progress already.

Initial MAGLDR is working, initial UEFI is working,

bootarm.efi boots from USB stick with WRT installation files.

USB stick is connected via USB host.

But it halts in such state - more stuff must be done to continue with installation (like eMMC access, ACPI support and etc).

For now it's double pixeled - works as 960x540 instead of 1920x1080.
[One (M7) Original Android Development] csoulr666:
A small thought occurred to me...........Is this by any chance inspired by this
[One (M7) Original Android Development] Drakknar:
Hey @Cotulla, do you have any plan to support the One 802w (GSM/WCDMA dual sim) variant? :)
[One (M7) Original Android Development] MemoryController:
[MENTION=600525]Cotulla[/MENTION] are you using LK as a base for MAGLDR? Really interested in UEFI for my S4 :)
[One (M7) Original Android Development] poyensa:
Just in case any has doubts about what means Cotulla to HTC One ... have a look here ... and admire the achivements of a 4 years old HD2. Good luck! Awaiting for the WM6.5 on SD :)
[One (M7) Original Android Development] jotha:
Thread cleaned

I am cleaning this thread from all that OT junk atm.

There is no benefit for the community to know how much you look forward to this, whether you will buy a One for this or whatever you feel about this development effort.

This will be a development thread and is meant to provide information about the work cotulla does here.

So it will be best if you all stay out of it if you don't have anything to commit to that development.

Don't get me wrong, we all are amazed that Team DFT/Cotulla will work on this device. It just isn't the purpose of a development thread to voice all that non-development stuff. All the useful information would get lost among that crap.

The thread will end up in "Original Development" the moment anything flashable exists. And there the posting rules are even stricter. So let's live up to that level already now.

We will have this at close guard as it is destined to become a trollfest before even one line of code is released.

Thanks for your understanding.
[One (M7) Original Android Development] theq86:
OK, just some thoughts of mine:

Do you already have something running? As far as I know, the m7's hboot runs a kernel from /boot partition (boot,img). If you want to put the kernel away to a different location, maybe hboot won't like it and reboot into the bootloader screen permanently.

So it might be you have to struggle with the hboot bootloader (or even SBL) to boot up MAGLDR.

Or, you could completely replace hboot by MAGLDR.

Do you already have an idea about the whole architecture ?
[One (M7) Original Android Development] MemoryController:
He does hboot->magldr->kernel

most likely