yashsingh1/xdaforums huggingface dataset:
[HTC EVO 3D] gjlowe:
So what do I do if I am on HBOOT 1.5 but not done via the official HTC unlock method? Early on, I rooted prior to the official method, but accidentally updated the HBOOT at the time. So I am on 1.5 but with S-OFF (though the top of the bootloader screen DOES say LOCKED). I was able to flash TWRP 1.0.3 later, but I haven't done anything since then.
[HTC EVO 3D] ira9700:
twrp

Totally awsome,finally able to get a working recovery you guys are the best
[HTC EVO 3D] Scott:
Very strange. WE will have to see if anyone else has this issue.

Well, make sure you have the MD5 ver turned off in the options!

Well, I am in the same boat you are except I am hboot 1.5 S-OFF Unlocked. I would just do the HTC method of unlocked and I can tell you that this will work without a hitch. You can also try it Locked but I dont know if it will let you flash. Nothing bad would happen so give it a try either way and let us know. I am very curious to find out!
[HTC EVO 3D] Scott:
Wow, 84 downloads of the file and 2 thanks!

I guess its so much harder to hit thanks than to download.
[HTC EVO 3D] selders59:
Yes scrosler, I checked and unchecked the md5 a few times and got the same results. Back on 1.03 and the very same rom d/l flashed fine without an issue. Wowed.

"From the Voices in my Head"
[HTC EVO 3D] Scott:
That stinks! Its been working as it should for me.
[HTC EVO 3D] mduber:
rad

sweet everything went great thanks guys!!
[HTC EVO 3D] THunDA:
Thanks man, worked perfect for me.. and I hit the thanks button :)
[HTC EVO 3D] Scott:
Thanks guys. Im not trying to be a cry baby, but how hard is it to hit the thanks button? Its not like I get paid (other thana few donations here and there that I really apprecaite) to do this nor do I need this tool. I did it for the community.

IM gonna do a script for ROM flashing with hboot 1.5 and I will need some testers.... If you are interested in helping me test please let me know by sending me a PM.
[HTC EVO 3D] THunDA:
I hear ya.. I could have done it the regular way but you made it much quicker and easier for me..lol

your time and work IS appreciated!

.. I just made a new nand and man is it quicker!!
[HTC EVO 3D] watzone69:
Thanks (and thanks button hit)!
[HTC EVO 3D] MikeC84:
So whats changed in twrp 1.1.0. Ther is no change log.

nm it was updated.
[HTC EVO 3D] predwing:
Thanks for the tool worked like a charm, I have been trying for a long time to get TWRP installed on my phone and never was able too since i had 1.5.

p.s I hit thanks
[HTC EVO 3D] blaz4me:
Any notes if it will run on eng hboot 1.04.2000?
[HTC EVO 3D] Scott:
Should but you try at your own risk! To be honest with you it should work on any. But once again, I can only test on so many devices.
[HTC EVO 3D] deedee305:
Hey scrosler is this 1.1.1
[HTC EVO 3D] Scott:
No, they have a new update already? This is 1.1
[HTC EVO 3D] Scott:
Just bumped to version 2

Change log includes twrp version 1.1.1!

Thanks for pointing that out!
[HTC EVO 3D] biggboii:
Thanks!
[HTC EVO 3D] Flak:
version 1.1 and 1.1.1 won't let me format my sdcard:

e:format_volume: fs_type "vfat" unsupported

It worked fine in 1.0.3 and works with clockwork recovery.
[HTC EVO 3D] EniGmA1987:
So does this now let people with hboot 1.5 flash roms and kernels easily without going through the normal complicated means of pushing files and all that? Like so now you can just install the zip through recovery and be done?
[HTC EVO 3D] FrickenFracken:
Will this replace clockwork if it is already installed?
[HTC EVO 3D] Scott:
Seems to be an issue with twrp 1.1.1. Maybe check in there thread and see what they say?

No, this is just an update to recovery. Has nothing to do with bootloader. I am working on a tool that will do what you want though.

It should.
[HTC EVO 3D] FrickenFracken:
Thanks man. Quick and painless
[HTC EVO 3D] subaochen:
I can not boot into recovery from HBOOT 1.5:-(
[HTC EVO 3D] Scott:
What do you mean? You should be able to just fine after running the script.
[HTC EVO 3D] dlbaker1179:
Thanks Worked Well For Me...
[HTC EVO 3D] Scott:
Good to hear. Figured I would try to make it as simple as possible. Some people get nervous when they flash recovery, lol. I used to anyways! lol
[HTC EVO 3D] Macropoutsis:
I'm on 1.4, worked great. Thanks. And I did hit the Thanks button.
[HTC EVO 3D] .:[K]!nG_D:.:
YUP!! im on 1.04.2000 and it works fine no problems here battery does work now happy about that ha
[HTC EVO 3D] Scott:
Thats good stuff!
[HTC EVO 3D] Leoisright:
im on 1.5 htc unlocked method with s-off and just sit's at the waiting for device screen
[HTC EVO 3D] P4THOG3N:
Handy script! Thanks a ton.
[HTC EVO 3D] Scott:
Thats exactly how I am set up too. Very strange it would do that for you. Did it boot to fast boot? I know it wont do anything if its not in fast boot. I will download the file again and take a look. But that is really strange?

You dont have any other adb servers going a the same time do you? Maybe reboot PC? But let me check right quick.....
[HTC EVO 3D] Scott:
I try to help when I can :cool:

Ok, I just tried it again and it was fine. I am not sure why you see that. I would reboot PC and make sure no other ADB servers have started first. This zip has the adb and fast boot files included for those that would not normally have access to them. Wonder if they are conflicting on your machine?
[HTC EVO 3D] Leoisright:
yeah, it boots to fastboot fine, just doesn't see the image or something

it's is weird
[HTC EVO 3D] ghost2133:
I hit the thanks button, but would like to see if anyone can help, I'm on a macbook pro and I'm not sure how to apply this using my computer and phone. Thanks in advance.
[HTC EVO 3D] Scott:
You aint gonna. I am sure someoen could make this work on a Mac but I dont have one. If you send me a mac I will write a script for it (yes I will send it back!).

Also, if I did the script in linux would that work on the mac? I dk much about macs, sorry man.
[HTC EVO 3D] Scott:
Have you rebooted the PC and made sure no other ADB server had previously started? Thats the only thing that I can possibly think of.
[HTC EVO 3D] Leoisright:
yeah, just rebooted. just sits on the fastbootusb screen and computer is waiting for device.

I will check a couple other things too

edit: isn't there an update or pg86img.zip we can use?
[HTC EVO 3D] Scott:
Aight man... Good luck. IM dropping off the net for a couple hours.
[HTC EVO 3D] ghost2133:
I'm new to macs myself and after 4 pc's broke I decided to go that route, although I'm having issues with things like this and SVN, thanks though.

Edit: I got this figured out, Leo over on shooter 357 posted a zip, thanks Leo, so I just downloaded, used astro to place on root of sd, went into bootloader and bam I'm all good, thanks everyone for your hard work.
[HTC EVO 3D] Worm1996:
I'm stock with the white htc very time i flash the rom? any help md5 ignoring

---------- Post added at 11:45 PM ---------- Previous post was at 11:44 PM ----------

im in hboot 1.5
[HTC EVO 3D] Kenjari:
Where did you find that zip?
[HTC EVO 3D] ch1naski:
Hey Scott, maybe you should point out that HTC sync should be completely off on the computer when doing this.
[HTC EVO 3D] Worm1996:
can you give me step by step on flashing a rom I'm always stuck on white screen it cannot read md5,I'm flashing cnayogen m7 in hboot 1.5 twrp I'm still working this out for 2 days thanks for any help
[HTC EVO 3D] Rydah:
Im running 1.1.1, and am getting the md5 error also. anybody know whats going on with that?

HBoot: 1.40

TWRP: 1.1.1
[HTC EVO 3D] Scott:
Good point!

Updated OP.
[HTC EVO 3D] krazyfukr:
I'm not familiar with twrp, but you don't have a lot of steps to go through to install a rom, including the kernel.

all you have to do is use fastboot to boot the phone into recovery, after that everything else is done normally and works fine.

fastboot boot <recovery image.img>

make sure the recovery is in the same folder on the pc.

once it boots into recovery, if you flash a rom as a zip file from the sdcard, it will load the kernel too. i use this method all the time and works fine with cwm 4.0.1.4, i can't see why it wouldn't work with twrp.
[HTC EVO 3D] gjlowe:
So this did not work. I also tried to unlock using the HTC method, and this does not work either. I get through to step 12, and when I run the "fastbook flash unlocktoken..." command, it just doesn't bring that unlock screen up. I fear that I am stuck in no-man's land, where I have S-OFF but the system still says it is locked. I was able to flash to TWRP 1.0.3 at some point using a zip I believe, so is there a way I can do that again?
[HTC EVO 3D] Scott:
Yes, it is the same thing.

Do you have hboot 1.5 or 1.4?
[HTC EVO 3D] gjlowe:
I have hboot 1.5
[HTC EVO 3D] krazyfukr:
The only twrp i've found that worked with hboot 1.5 s-on is v1.03, it's the one i'm using now.

The only clockwork recovery i could get to work was 4.0.1.4

So it seems we're limited to one of those specific versions.
[HTC EVO 3D] greeg32:
I use twrp 1.1.1 and I'm on 1.5
[HTC EVO 3D] krazyfukr:
Yessir, I just installed this one, about 10 minutes after I posted that... Great to see it works!
[HTC EVO 3D] hitman4274:
Finally switched from cwm to twrp its flawless

Shot from my shooter in 3D

cleanrom2.8

www.gplus.to/hitman4274
[HTC EVO 3D] vinc3stylez:
so with this you could get into recovery without adb? (hboot 1.5)
[HTC EVO 3D] Wally72:
Thx!!!

Sweet w/o problems!!!:cool:
[HTC EVO 3D] THADDIUS25:
I have a question, i just installed the twrp but i was using clockwork, but i can find my clockwork backups
[HTC EVO 3D] krazyfukr:
Clockwork folder on SD card. I doubt you can install those without clockwork though, any change to them will cause ms5 to fail. Probably have to install clockwork, restore, then install twrp, then create new backup.

3D Shooter
[HTC EVO 3D] stanglifemike:
Exactly! You can't restore Clockwork Backups with TWRP, and vice versa. Also worth nothing, for those unaware, TWRP v1.1.1 can NOT restore Backups from versions older than 1.1
[HTC EVO 3D] runner77:
How were you able to get hboot 1.5 with

S-OFF

?? Please share....
[HTC EVO 3D] jstn76rs:
he was most likely rooted before upgrading to Hboot 1.5...
[HTC EVO 3D] htcEVO9:
someone mind walking me thru on how to flash this? cant quite follow how op has it written on the first page

never mind, gave it a shot in the dark and it worked lol.... however got an error message before the recovery flashed.. is this a problem?
[HTC EVO 3D] krazyfukr:
Well, just in case.... here's the info:

Place twrp recovery image in same folder with fastboot.exe

open command prompt in that folder.

connect phone to computer

type command:

adb reboot bootloader

after phone reboots into bootloader, verify screen shows "fastboot usb"

type command:

fastboot flash recovery <twrp file name>.img

(i renamed mine twrp111.img for convenience.)

this is the steps i use because i'm on hboot 1.5 with s-on, if s-off, there may be a simpler way, but this one should also work.
[HTC EVO 3D] htcEVO9:
gonna try your method cuz when i went to do a nand it said the process was aborted... thanks for the write up
[HTC EVO 3D] krazyfukr:
Let us know if it works.
[HTC EVO 3D] vinc3stylez:
ive tried both methods and still cant get into recovery without adb..
[HTC EVO 3D] krazyfukr:
To get to recovery you power off phone, wait about ten seconds, hold vol down and press and hold power for about ten or more seconds.

But if you install a ROM with custom kernel you have to use fastboot to boot recovery or the kernel won't stick.

3D Shooter
[HTC EVO 3D] Darkmx2000:
I thought there was flasher tool that allowed us to flash kernels and Roms?
[HTC EVO 3D] krazyfukr:
I'm not sure, I think I've seen one too, but i haven't tried it. This method is so simple it didn't seem worth it to download an app to do something I can already do. So there may be one out there, but I haven't personally tested or used it.
[Galaxy S Plus I9001 Android Development] eidelen:
1) Get the stock kernel sources GT-I9001 from Samsung Open Source Release Center

2) Go into the top kernel directory and execute

> make ARCH=arm CROSS_COMPILE="path-to-cross-compiler" ariesve_rev00_defconfig

> make ARCH=arm CROSS_COMPILE="path-to-cross-compiler" -j4

3) The resulting kernel is in arch/arm/boot/zImage

4) Use the following command to pack the boot image

> mkbootimg --kernel zImage --ramdisk boot.img-ramdisk.gz --cmdline "console=null androidboot.hardware=qcom androidboot.emmc=true hw=6" -o myBuiltBoot.img --base 0x00400000 --pagesize 4096

5) Copy myBuiltBoot.img to the sdcard. Then open a shell on the phone

# dd if=/sdcard/myBuiltBoot.img of=/dev/block/mmcblk0p8

# sync

6) With the next restart, your kernel will be booted.

Here you can find the original ramdisk + boot.img. I extracted it from a stock-rom smd package.

http://www.eidelen.ch/android/bootGTI9001.zip

Note I: It's possible that your device doesn't start anymore. In such a case I just used Odin for flashing a original stock-rom, which includes a boot.img.

Note II: During step 5) -> I'm not sure if the 'sync' is necessary. It no harm.

Note III: During step 5) -> I compared the memory blocks on the device against an extracted boot.img. Like that I found out which one is the boot-partition (/proc/emmc is empty). Possible that it could be different on your device.

Good Luck,

eidelen

Adds:

Building modules

> make ARCH=arm CROSS_COMPILE="path-to-cross-compiler" modules_prepare

> make ARCH=arm CROSS_COMPILE="path-to-cross-compiler" modules
[Galaxy S Plus I9001 Android Development] larry200ro:
What is the advantage of doing all this?
[Galaxy S Plus I9001 Android Development] eidelen:
It's only required if you want to modify the kernels source code. For example enabling overclocking or something else.
[Galaxy S Plus I9001 Android Development] sakindia123:
thanks........are the sources complete?or u face the same problems as 19003?

also,does i9001 have bln?and what is the minimum freq?

also,how do u pack a tar?
[Galaxy S Plus I9001 Android Development] eidelen:
The kernel sources are complete, but the 4 modules are not built. It doesn't seem to be a problem, since module version check is off.

I'm not experienced with other Samsung devices; I don't know about bln & freq. I didn't pack a tar (for odin?), I'm flashing the boot.img with the shell command "dd".
[Galaxy S Plus I9001 Android Development] sakindia123:
i have a noob query....

1)What do i type in "path to cross compiler'?where is it found?

2)how do i install codesoucery toolchain?

sorry this is my first time!
[Galaxy S Plus I9001 Android Development] eidelen:
On following page, codesoucery installation is quickly mentioned

http://developer.sonyericsson.com/wp/2011/05/06/how-to-build-a-linux-kernel/

I'm using the cross-compiler from the Android Open Source project. There is a good manual from cyanogenmod:

http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source

Br,

adrian
[Galaxy S Plus I9001 Android Development] netchip:
Thank you mate!

This provides A LOT OF INFO for CWM :D
[Galaxy S Plus I9001 Android Development] sakindia123:
yet other n00b query!

arm-2011.03-42-arm-none-eabi.bin.......how do i install this cross-compiler? :P
[Galaxy S Plus I9001 Android Development] manveru0:
here's the readme from samsung:

1. How to Build

- get Toolchain

From Codesourcery site( http://www.codesourcery.com )

Ex) Download : http://www.codesourcery.com/sgpp/li...09-51-arm-none-eabi-i686-pc-linux-gnu.tar.bz2

recommand :

Feature : ARM

Target OS : "EABI"

package : "IA32 GNU/Linux TAR"

- edit Makefile

edit "CROSS_COMPILE" to right toolchain path(You downloaded).

Ex) ARCH ?= arm

CROSS_COMPILE ?= /opt/toolchains/arm-2009q3/bin/arm-none-linux-gnueabi- // You have to check compiler path

- command

$ cd kernel

$ make ariesve_rev00_defconfig

$ make

2. Output files

- Kernel : kernel/arch/arm/boot/zImage

just unpack the toolchain and you're good to go!
[Galaxy S Plus I9001 Android Development] eBug:
To pack a tar, use

tar

;) For details on how it works

man tar
[Galaxy S Plus I9001 Android Development] sakindia123:
thanks..i had already got that working...

i am just unable to sync repo android source :(
[Galaxy S Plus I9001 Android Development] sakindia123:
i edited the makefile acc. to my toolchain location,but i get error"not found"

could anyone tell me an exact path (where u placed it) to place the toolchain bin?its called arm-2011.03-42-arm-none-eabi.bin

last of all,how to unpack boot.img?
[Galaxy S Plus I9001 Android Development] netchip:
Install tje toolchain

Figure out yourself how.

Sent from my GT-I9100
[Galaxy S Plus I9001 Android Development] eidelen:
I learned from following page about android images. http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images

It's the first search result for "unpack boot.img". But boycotting google is kind of rebelling :)

You have to be careful when packing the boot.img - the arguments have to be right. That works for S+

mkbootimg --kernel zImage --ramdisk boot.img-ramdisk.gz --cmdline "console=null androidboot.hardware=qcom androidboot.emmc=true hw=6" -o myBuiltBoot.img --base 0x00400000 --pagesize 4096

If you work with a different Kernel, the base-address might be different. You can find that value in your Kernels .config file. I wasted a lot of time by watching none booting kernels because of that :)
[Galaxy S Plus I9001 Android Development] adfree:
Noob question...

GT-I9001_Kernel.tar.gz contain over 35 000 files...

All files involved in creating zImage ?

:confused:

Or is it possible to reduce only for mandatory involved/included files?

For GT-I9001...

:confused:

Thanx in advance.

Best Regards
[Galaxy S Plus I9001 Android Development] educk:
Yes, you'll need all those. All kernel drivers are there including touchscreen, touch keys, GPU, i2c, CPU, board and many many more. It's cross-compiling ;)

The zImage will basically be a combination of all the kernel modules.
[Galaxy S Plus I9001 Android Development] adfree:
Thanx.

For my "Porting" journey... it's Copy & Paste Action... :o

http://xdaforums.com/showthread.php?t=2116846

But, how to identify files mandatory for:

1.

Hardware Keys like:

Volume +
Volume -
Home
Power

2.

Touch keys

Menu
Back

3.

Touchscreen input generally...

My idea is to use existing "drivers" from similar devices... and test if my S8600 explode or by luck do something...

I9001 Touch drivers from I9001 do nothing on my S8600...

No event... via ADB getevent visible.

http://xdaforums.com/showpost.php?p=54929846&postcount=698

GT-I8150B_GB_Opensource.zip
GT-I8150T_Opensource.zip
GT-I8150_CHN_CHN(1).zip
GT-I8150_CHN_CHN.zip
GT-I8150_HK.zip
GT-I8150_Opensource(1).zip
GT-I8150_Opensource(2).zip
GT-I8150_Opensource.zip
SGH-I847_ATT_Opensource.zip
SGH-I847_Opensource_Update1.zip
SPH-M840_BST_JB_Opensource.zip
SPH-M840_NA_JB_Opensource.zip
SPH-M950_ICS_Opensource(1).zip
SPH-M950_ICS_Opensource.zip
SPH-M950_ICS_Opensource_Update1.zip
SPH-M950_JB_Opensource.zip
SPH-M950_NA_JB_Opensource.zip

Any help is welcome.

Thanx in advance.

Best Regards
[Galaxy S Plus I9001 Android Development] alireza7991:
Not all of them are compiled ; The kernel source contains drivers for many hardwares and support of architectures which aren't really needed for I9001.so only some thousands of them are compiled. If sb compile all of those drivers (not arch files) it will be a +200mb zimage :) .
[Galaxy S Plus I9001 Android Development] adfree:
Please, I need help to fix "few" problems on GT-S8600... with I9001 Firmware

Because not supported Hardware...

Maybe I can start with "easier" task...

Volume + key on S8600 do nothing...

But I can see result of getevent:

# getevent
getevent
add device 1: /dev/input/event2
name: "ariesve_keypad"
add device 2: /dev/input/event8
name: "melfas_touchkey"
add device 3: /dev/input/event7
name: "7k_handset"
add device 4: /dev/input/event6
name: "light"
add device 5: /dev/input/event5
name: "proximity"
add device 6: /dev/input/event4
name: "orientation"
add device 7: /dev/input/event3
name: "quantom-touchscreen"
add device 8: /dev/input/event1
name: "dock"
add device 9: /dev/input/event0
name: "sec_jack"

/dev/input/event2: 0004 0004 00000000
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000008
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000010
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000018
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000020
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000000
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000008
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000010
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000018
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000020
/dev/input/event2: 0000 0000 00000000

I9001 Android detect that Volume + is pressed... on my S8600...

But 000 seems have no function or is wrong...

Volume - is same like I9001

/dev/input/event2: 0004 0004 00000001
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000009
/dev/input/event2: 0001 [B]0072[/B] 00000001
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000011
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000019
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000021
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000001
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000009
/dev/input/event2: 0001 [B]0072[/B] 00000000
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000011
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000019
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0004 0004 00000021
/dev/input/event2: 0000 0000 00000000
/dev/input/event6: 0003 0006 000000c8

HEX Value 0072 in DEC is 114...

Volume + if I remember correct is 115... so:

0x73

Logged key event on bada leads to my theory...

That maybe 113 could work, if defined...

Taken from bada... Volume + has lower Value...

Volume +
CAppSndKey::IsMutedKeytone: iKeyType ([B]42[/B]) cause by AUI

Volume -
CAppSndKey::IsMutedKeytone: iKeyType ([B]43[/B]) cause by AUI

Any help or suggestion is welcome.

Thanx in advance.

Best Regards
[Galaxy S Plus I9001 Android Development] adfree:
No idea if I am blind...

Samsung removed I9001 sources ?

http://opensource.samsung.com/reception.do

:confused: :eek:

I have attached 400 Kb here:

GT-I9001_CHN_OpenSource_HKTW.tar

http://xdaforums.com/showpost.php?p=55112546&postcount=733

From package

GT-I9001_OpenSource.tar.gz

I have only uploaded untouched Kernel sources...

GT-I9001_Kernel.tar.gz

http://www.mediafire.com/download/curv7cv1y8glpbp/GT-I9001_Kernel.tar.gz

I will add next days the platform part too... in this post:

http://xdaforums.com/showpost.php?p=55120354&postcount=737

Maybe someone need for study...

Alternate Links for whole packages, like this... not really free...

http://chomikuj.pl/PJ666/i9001

... are welcome...

Best Regards